WO2022003400A1 - Call participant migration between mission critical push-to-talk (mcptt) servers - Google Patents

Call participant migration between mission critical push-to-talk (mcptt) servers Download PDF

Info

Publication number
WO2022003400A1
WO2022003400A1 PCT/IB2020/056204 IB2020056204W WO2022003400A1 WO 2022003400 A1 WO2022003400 A1 WO 2022003400A1 IB 2020056204 W IB2020056204 W IB 2020056204W WO 2022003400 A1 WO2022003400 A1 WO 2022003400A1
Authority
WO
WIPO (PCT)
Prior art keywords
mission critical
user
partner
ongoing
primary
Prior art date
Application number
PCT/IB2020/056204
Other languages
French (fr)
Inventor
Gábor ZSIGMOND
Szabolcs ZÁBÓ
Original Assignee
Nokia Technologies Oy
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nokia Technologies Oy filed Critical Nokia Technologies Oy
Priority to PCT/IB2020/056204 priority Critical patent/WO2022003400A1/en
Publication of WO2022003400A1 publication Critical patent/WO2022003400A1/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H04W8/20—Transfer of user or subscriber data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H04W4/10—Push-to-Talk [PTT] or Push-On-Call services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/90—Services for handling of emergency or hazardous situations, e.g. earthquake and tsunami warning systems [ETWS]

Abstract

Systems and/or methods for call participant migration between mission critical systems are provided. One method includes receiving a request for a mission critical (MC) user profile of a user migrating between a primary mission critical (MC) system and a partner mission critical (MC) system, retrieving the mission critical (MC) user profile for the migrating mission critical (MC) user, collecting one or more ongoing calls having the migrating mission critical (MC) user as a participant at the primary mission critical (MC) system, and transmitting, to the partner mission critical (MC) system, information or identifiers of the one or more ongoing calls that the migrating mission critical (MC) user is a participant.

Description

CALL PARTICIPANT MIGRATION BETWEEN MISSION CRITICAL PUSH-TO-TALK
(MCPTT) SERVERS FIELD:
[0001] Some example embodiments may generally relate to mobile or wireless telecommunication systems, such as Long Term Evolution (LTE) or fifth generation (5G) radio access technology or new radio (NR) access technology, or other communications systems. For example, certain embodiments may relate to systems and/or methods for call participant migration between mission critical systems.
BACKGROUND:
[0002] Examples of mobile or wireless telecommunication systems may include the Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN), Long Term Evolution (LTE) Evolved UTRAN (E-UTRAN), LTE- Advanced (LTE- A), MulteFire, LTE- A Pro, and/or fifth generation (5G) radio access technology or new radio (NR) access technology. 5G wireless systems refer to the next generation (NG) of radio systems and network architecture. A 5G system is mostly built on a 5G new radio (NR), but a 5G (or NG) network can also build on the E-UTRA radio. It is estimated that NR provides bitrates on the order of 10-20 Gbit/s or higher, and can support at least service categories such as enhanced mobile broadband (eMBB) and ultra-reliable low-latency-communication (URLLC) as well as massive machine type communication (mMTC). NR is expected to deliver extreme broadband and ultra-robust, low latency connectivity and massive networking to support the Internet of Things (IoT). With IoT and machine-to-machine (M2M) communication becoming more widespread, there will be a growing need for networks that meet the needs of lower power, low data rate, and long battery life. The next generation radio access network (NG-RAN) represents the RAN for 5G, which can provide both NR and LTE (and LTE- Advanced) radio accesses. It is noted that, in 5G, the nodes that can provide radio access functionality to a user equipment (i.e., similar to the Node B, NB, in UTRAN or the evolved NB, eNB, in LTE) may be named next-generation NB (gNB) when built on NR radio and may be named next-generation eNB (NG-eNB) when built on E-UTRA radio.
SUMMARY:
[0003] One embodiment is directed to an apparatus that may include at least one processor and at least one memory comprising computer program code. The at least one memory and computer program code configured, with the at least one processor, to cause the apparatus at least to receive a request for a mission critical (MC) user profile of a user migrating between a primary mission critical (MC) system and a partner mission critical (MC) system, to retrieve the mission critical (MC) user profile for the migrating mission critical (MC) user, to collect one or more ongoing calls having the migrating mission critical (MC) user as a participant at the primary mission critical (MC) system, and to transmit, to the partner mission critical (MC) system, information or identifiers of the one or more ongoing calls that the migrating mission critical (MC) user is a participant. [0004] Another embodiment is directed to a method that may include receiving a request for a mission critical (MC) user profile of a user migrating between a primary mission critical (MC) system and a partner mission critical (MC) system, retrieving the mission critical (MC) user profile for the migrating mission critical (MC) user, collecting one or more ongoing calls having the migrating mission critical (MC) user as a participant at the primary mission critical (MC) system, and transmitting, to the partner mission critical (MC) system, information or identifiers of the one or more ongoing calls that the migrating mission critical (MC) user is a participant.
[0005] Another embodiment is directed to an apparatus that may include means for receiving a request for a mission critical (MC) user profile of a user migrating between a primary mission critical (MC) system and a partner mission critical (MC) system, means for retrieving the mission critical (MC) user profile for the migrating mission critical (MC) user, means for collecting one or more ongoing calls having the migrating mission critical (MC) user as a participant at the primary mission critical (MC) system, and means for transmitting, to the partner mission critical (MC) system, information or identifiers of the one or more ongoing calls that the migrating mission critical (MC) user is a participant. [0006] Another embodiment is directed to an apparatus, which may include at least one processor and at least one memory comprising computer program code. The at least one memory and computer program code configured, with the at least one processor, to cause the apparatus at least to transmit a request for a mission critical (MC) user profile of a user migrating between a primary mission critical (MC) system and a partner mission critical (MC) system, to receive information or identifier(s) of one or more ongoing calls that the migrating mission critical (MC) user is a participant at the primary MC system, to retrieve ongoing calls in which the migrating mission critical (MC) user is a participant at the partner mission critical (MC) system and, when one or more of the received ongoing call(s) are ongoing in the partner mission critical (MC) system, to initiate a late entry procedure towards a mission critical (MC) client. [0007] Another embodiment is directed to a method that may include transmitting a request for a mission critical (MC) user profile of a user migrating between a primary mission critical (MC) system and a partner mission critical (MC) system, receiving information or identifier(s) of one or more ongoing calls that the migrating mission critical (MC) user is a participant at the primary MC system, retrieving ongoing calls in which the migrating mission critical (MC) user is a participant at the partner mission critical (MC) system and, when one or more of the received ongoing call(s) are ongoing in the partner mission critical (MC) system, initiating a late entry procedure towards a mission critical (MC) client. [0008] Another embodiment is directed to an apparatus that may include means for transmitting a request for a mission critical (MC) user profile of a user migrating between a primary mission critical (MC) system and a partner mission critical (MC) system, means for receiving information or identifier(s) of one or more ongoing calls that the migrating mission critical (MC) user is a participant at the primary MC system, means for retrieving ongoing calls in which the migrating mission critical (MC) user is a participant at the partner mission critical (MC) system and, when one or more of the received ongoing call(s) are ongoing in the partner mission critical (MC) system, means for initiating a late entry procedure towards a mission critical (MC) client.
[0009] Another embodiment is directed to an apparatus, which may include at least one processor and at least one memory comprising computer program code. The at least one memory and computer program code configured, with the at least one processor, to cause the apparatus at least to receive a call leave request, from a primary mission critical (MC) system, indicating that a mission critical (MC) user is being de-affiliated from one or more ongoing calls provided by the primary mission critical (MC) system, wherein the call leave request further comprises an indication that the de- affiliation of the mission critical (MC) user is due to migration of the mission critical (MC) user to a partner mission critical (MC) system, to receive a call request from the partner mission critical (MC) system indicating initiation of the late entry procedure, to perform the de-affiliation and the late entry for the ongoing calls with the migrated mission critical (MC) user as a participant, and to indicate the migration to the mission critical (MC) user. [0010] Another embodiment is directed to a method that may include receiving a call leave request, from a primary mission critical (MC) system, indicating that a mission critical (MC) user is being de-affiliated from one or more ongoing calls provided by the primary mission critical (MC) system, wherein the call leave request further comprises an indication that the de-affiliation of the mission critical (MC) user is due to migration of the mission critical (MC) user to a partner mission critical (MC) system, receiving a call request from the partner mission critical (MC) system indicating initiation of the late entry procedure, performing the de-affiliation and the late entry for the ongoing calls with the migrated mission critical (MC) user as a participant, and indicating the migration to the mission critical (MC) user.
[0011] Another embodiment is directed to an apparatus that may include means for receiving a call leave request, from a primary mission critical (MC) system, indicating that a mission critical (MC) user is being de-affiliated from one or more ongoing calls provided by the primary mission critical (MC) system, wherein the call leave request further comprises an indication that the de affiliation of the mission critical (MC) user is due to migration of the mission critical (MC) user to a partner mission critical (MC) system, means for receiving a call request from the partner mission critical (MC) system indicating initiation of the late entry procedure, means for performing the de affiliation and the late entry for the ongoing calls with the migrated mission critical (MC) user as a participant, and means for indicating the migration to the mission critical (MC) user. BRIEF DESCRIPTION OF THE DRAWINGS:
[0012] For proper understanding of example embodiments, reference should be made to the accompanying drawings, wherein: [0013] Fig. la illustrates an example signaling diagram, according to an embodiment;
[0014] Fig. lb illustrates the continuation of the example signaling diagram of Fig. la, according to an embodiment;
[0015] Fig. 2a illustrates an example signaling diagram, according to an embodiment;
[0016] Fig. 2b illustrates the continuation of the example signaling diagram of Fig. la, according to an embodiment;
[0017] Fig. 3a illustrates an example flow diagram of a method, according to an embodiment;
[0018] Fig. 3b illustrates an example flow diagram of a method, according to an embodiment;
[0019] Fig. 4a illustrates an example flow diagram of a method, according to an embodiment;
[0020] Fig. 4b illustrates an example flow diagram of a method, according to an embodiment; [0021] Fig. 5 illustrates an example flow diagram of a method, according to an embodiment;
[0022] Fig. 6a illustrates an example block diagram of an apparatus, according to an embodiment;
[0023] Fig. 6b illustrates an example block diagram of an apparatus, according to an embodiment; and
[0024] Fig. 6c illustrates an example block diagram of an apparatus, according to an embodiment.
DETAILED DESCRIPTION:
[0025] It will be readily understood that the components of certain example embodiments, as generally described and illustrated in the figures herein, may be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of some example embodiments of systems, methods, apparatuses, and computer program products for call participant migration between mission critical systems, is not intended to limit the scope of certain embodiments but is representative of selected example embodiments.
[0026] The features, structures, or characteristics of example embodiments described throughout this specification may be combined in any suitable manner in one or more example embodiments. For example, the usage of the phrases “certain embodiments,” “some embodiments,” or other similar language, throughout this specification refers to the fact that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment. Thus, appearances of the phrases “in certain embodiments,” “in some embodiments,” “in other embodiments,” or other similar language, throughout this specification do not necessarily all refer to the same group of embodiments, and the described features, structures, or characteristics may be combined in any suitable manner in one or more example embodiments. [0027] Additionally, if desired, the different functions or procedures discussed below may be performed in a different order and/or concurrently with each other. Furthermore, if desired, one or more of the described functions or procedures may be optional or may be combined. As such, the following description should be considered as illustrative of the principles and teachings of certain example embodiments, and not in limitation thereof.
[0028] Currently, 3GPP specifies some mission critical (MC) user migration between mission critical push-to-talk (MCPTT) systems (e.g., primary MC and partner MC), but only when the user equipment (UE) is in idle mode, not when having any ongoing peer-to-peer (P2P) or group calls. [0029] A primary MC system may refer to a MCPTT system where the MCPTT user profile of an MCPTT user is defined. A MCPTT user is a user of an MCPTT service, who has a device with the capability to participate in MCPTT services. A MCPTT UE is a UE that enables an MCPTT user to participate in MCPTT service. A partner MCPTT system may refer to an allied MCPTT system that provides MCPTT services to an MCPTT user based on the MCPTT user profile that is defined in the primary MCPTT system of that MCPTT user. [0030] In case of interconnecting group calls (i.e., those group calls which are provided by more than one MCPTT server/group management server), an MC user or UE can move from the service area of the primary MC system to the service area of the partner MC system. In this case, the UE is migrated from the primary MC system to the partner MC system. It is noted that a group call may refer to a mechanism by which an MCPTT user can make a one-to-many MCPTT transmission to other MCPTT users that are members of MCPTT group(s).
[0031] For example, in a railway environment, long group calls (e.g., 8-12 hours long) are quite normal, so it may occur that an MC user is migrated when they are a participant of a group call, which is served by the primary and the partner MC systems (e.g., group call covering the border area between two neighbouring countries). [0032] Therefore, certain embodiments are configured to provide seamless call continuity, e.g., in a case where an MC user is migrating between the primary MC system and the partner MC system, when it is participating in ongoing group call(s) provided by primary MC system and partner MC system (interconnection group call). Additionally, an embodiment may provide for synchronization between the de-affiliation from the leaving group and the late-entry (join) to the approaching group. As discussed herein, some embodiments may apply to ongoing group calls; however, certain embodiments can also be applied for ongoing private calls as well.
[0033] As will be discussed in more detail below, certain example embodiments may provide a system for providing call continuity when an MC user is migrating between a primary MC system and partner MC system. According to one embodiment, a partner MC system may receive a request for a MC user profile of a user migrating between the primary MC system and the partner MC system. In an embodiment, the partner MC system may send a request, to the primary MC system, for the MC user profile of the migrating user. According to certain embodiments, the primary MC system may retrieve the MC user profile for the migrating user. In some embodiments, the primary MC system may also collect one or more ongoing calls having the migrating user as a participant at the primary MC system. According to an embodiment, the primary MC system may transmit, to the partner MC system, information or identifiers of the one or more ongoing calls in which the migrating user is a participant.
[0034] In one embodiment, when there are one or more ongoing calls in which the migrating user is a participant, the primary MC system may transmit a call leave request to a MC client to indicate that the de-affiliation of the migrating user is occurring due to migration. According to an embodiment, the MC client does not provide a notification towards the migrating user upon receipt of the call leave request. In certain embodiments, the MC client may transmit a call leave response to the primary MC system to indicate that the de-affiliation will occur together with late entry of the ongoing calls that the migrating user is a participant.
[0035] According to an embodiment, the partner MC system may retrieve ongoing calls in which the migrating user is a participant at the partner MC system and, when one or more of the received ongoing call(s) are ongoing in the partner mission critical (MC) system, the partner MC system may initiate a late entry procedure towards the MC client. For example, in an embodiment, the MC client may receive a call request from the partner MC system indicating initiation of the late entry procedure. The MC client may then perform the de-affiliation and the late entry for the ongoing calls with the migrating user as a participant, and the MC client may then indicate the migration to the user. Thus, according to certain embodiments, the MC client does not provide a notification to the user of the de-affiliation request until after receiving the indication of the late entry procedure from the partner MC system.
[0036] In some other embodiments, the primary MC system may store an indication that the de affiliation will occur after a user migration synchronization request is received. According to this embodiment, when one or more of the ongoing calls are ongoing in the partner MC system, the primary MC system may receive a user migration synchronization request from the partner MC system. Furthermore, in this embodiment, after receiving the user migration synchronization request, the primary MC system may transmit a call leave request to a MC client to indicate that the de affiliation of the user is occurring due to migration, and may receive a call leave response from the MC client to indicate that the de-affiliation will occur together with late entry of the ongoing calls that the user is a participant. In this embodiment, the primary MC system may then transmit a user synchronization response to the partner MC system. The partner MC system may then transmit the call request to the MC client, as discussed above, to indicate initiation of the late entry procedure. [0037] Fig. la and Fig. lb illustrate an example signaling diagram of a migration procedure, according to an embodiment. The example diagram of Figs la and lb depicts signaling between a MCPTT client, a configuration management client, a partner MC system, and a primary MC system. It is noted that, for purposes of clarity, Fig. la depicts the MCPTT client, the configuration management client, and the partner MC system; while Fig. lb illustrates the continuation of the signaling diagram depicting the primary MC system. In some embodiments, the partner MC system and primary MC system may respectively include a configuration management server, MC service user database, and group management server. [0038] As illustrated in the example of Figs la and lb, at 101, a configuration management client may transmit a MC service user profile for migration request to a configuration management server of the partner MC system. The configuration management server of the partner MC system may transmit, at 102, a migrated MC user profile request to the configuration management server of the primary MC system. The primary MC system, at 103, may retrieve the user profile for migration. After the primary MC system retrieves MC user profile for migration at 103, the primary MC system may also collect, at 105, all the ongoing group calls in which the migrating user is a participant. For example, in an embodiment, the configuration management server of the primary MC system may send, at 104, a migrated MC user group configuration request to the group management server. The group management server may, at 105, retrieve the ongoing group calls with migrated MC user as a member and, at 106, send a migrated MC user group configuration response to the configuration management server.
[0039] In an embodiment, if there is an ongoing group call in which the migrating MC user is a participant, then the primary MC system may send, at 107, a group call leave request to the MCPTT client to indicate that the MC user is de-affiliated from the ongoing group call(s) provided by the primary MC system. The group call leave request may also indicate that the de-affiliation occurs due to MC user migration, so the MCPTT client does not de-affiliate the MC user suddenly, but waits for the late-entry and/or join request from the partner MC system and performs the de affiliation and late-entry substantially after each other. According to one embodiment, at 108, the MCPTT client does not indicate the de-affiliation request to the MCPTT user. According to certain embodiments, the MCPTT client may transmit, at 109, a group call leave response indicating that the de-affiliation will occur together with late entry. Therefore, in the example of Figs la and lb, an extra indication may be used to indicate to the MCPTT client that the de-affiliation happens because of user migration and the MCPTT client may hide the de-affiliation and late entry from the MC user. [0040] The primary MC system may send, at 110, the ongoing group call IDs in which the migrated user is a participant to the partner MC system in a migrated MC user profile response message. The partner MC system may interrogate those group calls in its database, whether they are ongoing in the partner MC system as well or not. In an embodiment, the partner MC system may, at 111, modify user profile according to the partner MC system policy and store it in the MC service user database. According to certain embodiments, the partner MC system may optionally, at 112, transmit a validate modified MC service user profile request to the primary MC system. In this case, the primary MC system may, at 113, validate the modified MC user profile for migration and, at 114, may transmit a validate modified MC service user profile response to the partner MC system. [0041] In an embodiment, the configuration management server of the partner MC system may, at 115, transmit a migrated MC user group configuration request to its group management server. The group management server may, at 116, retrieve the ongoing group calls with the migrated MC user as a participant and, at 117, transmit a migrated MC user group configuration response to the configuration management server. According to an embodiment, the configuration management server of the partner MC system may, at 118, transmit a migrated MC user join request to its group management server. [0042] If any of the received group calls is ongoing in the partner MC system, then the partner MC system may initiate a late-entry procedure towards the MCPTT client. For example, as illustrated in the example of Figs la and lb, at 119, the group management server may transmit a group call request to the MCPTT client. The MCPTT client may perform the de-affiliation and the late-entry (for the ongoing group calls with the migrated user as a participant) and may, at 120, indicate the group call migration to the MC user. In an embodiment, the MCPTT client may, at 121, transmit a group call response to the group management server of the partner MC system. According to certain embodiments, the group management server may, at 122, transmit a migrated MC user join response to the configuration management server of the partner MC system. The configuration management server may then provide, at 123, a MC service user profile for migration response to the configuration management client.
[0043] It is noted that, if there is not an ongoing group call in the primary MC system with the migrating MC user as a participant, then the primary MC system would not send back any group identifier (ID) to Partner MC system and a conventional MC user profile migration approach can be used. [0044] Fig. 2a and Fig. 2b illustrate an example signaling diagram of a migration procedure, according to a further embodiment. Similar to Figs la and lb, the example diagram of Figs. 2a and 2b depicts signaling between a MCPTT client, a configuration management client, a partner MC system, and a primary MC system. However, in the example of Figs. 2a and 2b, a new synchronization message may be provided between the primary MC system and the partner MC system. It is noted that, for purposes of clarity, Fig. 2a depicts the MCPTT client, the configuration management client, and the partner MC system; while Fig. 2b illustrates the continuation of the signaling diagram depicting the primary MC system.
[0045] As illustrated in the example of Figs. 2a and 2b, at 201 , a configuration management client may transmit a MC service user profile for migration request to a configuration management server of the partner MC system. The configuration management server of the partner MC system may transmit, at 202, a migrated MC user profile request to the configuration management server of the primary MC system. The primary MC system, at 203, may retrieve the user profile for migration. After the primary MC system retrieves MC user profile for migration at 203, the primary MC system may also collect, at 205, all the ongoing group calls in which the migrating user is a participant. For example, in an embodiment, the configuration management server of the primary MC system may send, at 204, a migrated MC user group configuration request to the group management server. The group management server may, at 205, retrieve the ongoing group calls with migrated MC user as a member and, at 206, send a migrated MC user group configuration response to the configuration management server. As illustrated at 207, if there is any ongoing group call in which the migrating MC user is a participant, then primary MC system does not send a group call leave request to the MCPTT client. However, the primary MC system may store the indication that de-affiliation occurs after the MC user migration synchronization request is received.
[0046] The primary MC system may send, at 210, the ongoing group call identifiers (IDs) in which the migrated user is a participant to the partner MC system in a migrated MC user profile response message. The partner MC system may interrogate those group calls in its database, whether they are ongoing in the partner MC system as well or not. In an embodiment, the partner MC system may, at 211, modify user profile according to the partner MC system policy and store it in the MC service user database. According to certain embodiments, the partner MC system may optionally, at 212, transmit a validate modified MC service user profile request to the primary MC system. In this case, the primary MC system may, at 213, validate the modified MC user profile for migration and, at 214, may transmit a validate modified MC service user profile response to the partner MC system. [0047] In an embodiment, the configuration management server of the partner MC system may, at 215, transmit a migrated MC user group configuration request to its group management server. The group management server may, at 216, retrieve the ongoing group calls with the migrated MC user as a participant and, at 217, transmit a migrated MC user group configuration response to the configuration management server.
[0048] According to an embodiment, if one or more of the received group calls is ongoing in the partner MC system, the configuration management server may, at 230, transmit a MC user migration synchronization request to the primary MC system. In an embodiment, if there is an ongoing group call in which the migrating MC user is a participant, then the primary MC system may send, at 232, a group call leave request to the MCPTT client to indicate that the MC user is de-affiliated from the ongoing group call(s) provided by the primary MC system. The group call leave request may also indicate that the de-affiliation occurs due to MC user migration, so the MCPTT client does not de affiliate the MC user suddenly, but waits for the late-entry and/or join request from the partner MC system and performs the de-affiliation and late-entry substantially after each other. According to one embodiment, at 234, the MCPTT client does not indicate the de-affiliation request to the MCPTT user. According to certain embodiments, the MCPTT client may transmit, at 236, a group call leave response indicating that the de-affiliation will occur together with late entry. Then, at 240, the primary MC system may transmit a MC user migration synchronization response to the partner MC system.
[0049] After the MC user migration synchronization response is received, the partner MC system may initiate a late-entry procedure towards the MCPTT client. For example, according to an embodiment, the configuration management server of the partner MC system may, at 238, transmit a migrated MC user join request to its group management server. The group management server may, at 249, transmit a group call request to the MCPTT client. The MCPTT client may perform the de-affiliation and the late-entry (for the ongoing group calls with the migrated user as a participant) and may, at 250, indicate the migration between MC systems to the MC user. In an embodiment, the MCPTT client may, at 251, transmit a group call response to the group management server of the partner MC system. According to certain embodiments, the group management server may, at 252, transmit a migrated MC user join response to the configuration management server of the partner MC system. The configuration management server may then provide, at 253, a MC service user profile for migration response to the configuration management client. [0050] Fig. 3a illustrates an example flow diagram of a method for call participant migration between MC systems, according to one example embodiment. In certain example embodiments, the flow diagram of Fig. 3a may be performed by a network entity or network node in a 3GPP system, such as LTE or 5G NR. For instance, in some example embodiments, the method of Fig. 3a may be performed by a primary MC system. For instance, in some embodiments, the method of Fig. 3a may be performed by one or more of a configuration management server, MC service user database, and/or group management server of a primary MC system. Therefore, in certain embodiments, the method may include any of the procedures performed by the primary MC system in Figs la and lb, for example.
[0051] As illustrated in the example of Fig. 3a, the method may include, at 300, receiving a request for a MC user profile of a user migrating between a primary MC system and a partner MC system. In an embodiment, the method may include, at 305, retrieving the MC user profile for the migrating user. According to certain embodiments, the method may also include, at 310, collecting ongoing calls having the migrating MC user as a member or participant. In some embodiments, the ongoing calls may be ongoing group calls or ongoing private calls. According to an embodiment, when there are one or more ongoing calls in which the migrating MC user is a participant, the method may further include, at 315, transmitting a call leave request to a MCPTT client to indicate that the de-affiliation of the MC user occurs due to migration and, at 320, receiving a call leave response from the MCPTT client to indicate that the de-affiliation will occur together with late entry.
[0052] In an embodiment, the method of Fig. 3a may include, at 325, transmitting a response, to the partner MC system, including the information or identifier(s) of the ongoing call(s) that the migrating MC user is participating in. According to some embodiments, the method may also include receiving a request to validate a modified MC service user profile, validating the modified MC user profile for migration, and transmitting a response with the validated modified MC service user profile.
[0053] Fig. 3b illustrates an example flow diagram of a method for call participant migration between MC systems, according to one example embodiment. In certain example embodiments, the flow diagram of Fig. 3b may be performed by a network entity or network node in a 3GPP system, such as LTE or 5G NR. For instance, in some example embodiments, the method of Fig. 3b may be performed by a primary MC system. For instance, in some embodiments, the method of Fig. 3b may be performed by one or more of a configuration management server, MC service user database, and/or group management server of a primary MC system. Therefore, in certain embodiments, the method may include any of the procedures performed by the primary MC system in Figs. 2a and 2b, for example.
[0054] As illustrated in the example of Fig. 3b, the method may include, at 350, receiving a request for a MC user profile of a user migrating between a primary MC system and a partner MC system. In an embodiment, the method may include, at 355, retrieving the MC user profile for the migrating user. According to certain embodiments, the method may also include, at 360, collecting ongoing calls having the migrating MC user as a member or participant. In some embodiments, the ongoing calls may be ongoing group calls or ongoing private calls. According to an embodiment, if there is one or more ongoing calls in which the migrating MC user is a participant, the method may further include, at 365, storing an indication that the de-affiliation will occur after a MC user migration synchronization request is received.
[0055] In an embodiment, the method may then include, at 370, transmitting a response, to the partner MC system, including the information or identifier(s) of the ongoing call(s) that the migrating MC user is participating in. According to certain embodiments, when one or more of the call(s) are ongoing in the partner MC system, the method may include, at 375, receiving a MC user migration synchronization request from the partner MC system. Then, in an embodiment, the method may include, at 380, transmitting a call leave request to a MCPTT client to indicate that the de affiliation of the MC user occurs due to migration and, at 385, receiving a call leave response from the MCPTT client to indicate that the de-affiliation will occur together with late entry. In an embodiment, the method may include, at 390, transmitting a MC user synchronization response to the partner MC system.
[0056] Fig. 4a illustrates an example flow diagram of a method for call participant migration between MC systems, according to one example embodiment. In certain example embodiments, the flow diagram of Fig. 4a may be performed by a network entity or network node in a 3GPP system, such as LTE or 5G NR. For instance, in some example embodiments, the method of Fig. 4a may be performed by a partner MC system. For instance, in some embodiments, the method of Fig. 4a may be performed by one or more of a configuration management server, MC service user database, and/or group management server of a partner MC system. Therefore, in certain embodiments, the method may include any of the procedures performed by the partner MC system in Figs la and lb, for example.
[0057] As illustrated in the example of Fig. 4a, the method may include, at 400, transmitting a request for a MC user profile of a user migrating between a primary MC system and a partner MC system. In an embodiment, the method may include, at 405, receiving a response, from the primary MC system, including the information or identifier(s) of the ongoing call(s) that the migrating MC user is participating in at the primary MC system. In some embodiments, the method may include modifying the user profile according to the partner MC system policy and storing it in the MC service user database. According to some embodiments, the method may also optionally include transmitting a validate modified MC service user profile request to the primary MC system. In this example case, the method may include receiving a validate modified MC service user profile response from the primary MC system.
[0058] According to certain embodiments, as further illustrated in the example of Fig. 4a, the method may include, at 410, retrieving ongoing calls in which the migrating MC user is a participant at the partner MC system. When one or more of the received ongoing call(s) are ongoing in the partner MC system, the method may include, at 415, initiating a late entry procedure towards a MCPTT client.
[0059] Fig. 4b illustrates an example flow diagram of a method for call participant migration between MC systems, according to one example embodiment. In certain example embodiments, the flow diagram of Fig. 4b may be performed by a network entity or network node in a 3GPP system, such as LTE or 5G NR. For instance, in some example embodiments, the method of Fig. 4b may be performed by a partner MC system. For instance, in some embodiments, the method of Fig. 4b may be performed by one or more of a configuration management server, MC service user database, and/or group management server of a partner MC system. Therefore, in certain embodiments, the method may include any of the procedures performed by the partner MC system in Figs. 2a and 2b, for example.
[0060] As illustrated in the example of Fig. 4b, the method may include, at 450, transmitting a request for a MC user profile of a user migrating between a primary MC system and a partner MC system. In an embodiment, the method may include, at 455, receiving a response, from the primary MC system, including the information or identifier(s) of the ongoing call(s) that the migrating MC user is participating in at the primary MC system. In some embodiments, the method may include modifying the user profile according to the partner MC system policy and storing it in the MC service user database. According to some embodiments, the method may also optionally include transmitting a validate modified MC service user profile request to the primary MC system. In this example case, the method may include receiving a validate modified MC service user profile response from the primary MC system. [0061] According to certain embodiments, the method may include, at 460, retrieving ongoing calls in which the migrating MC user is a participant at the partner MC system. When one or more of the received ongoing call(s) are ongoing in the partner MC system, the method may include, at 465, transmitting a MC user migration synchronization request to the primary MC system and, at 470, receiving a MC user synchronization response from the primary MC system. The method may then include, at 475, initiating a late entry procedure towards a MCPTT client.
[0062] Fig. 5 illustrates an example flow diagram of a method for call participant migration between MC systems, according to another example embodiment. In certain example embodiments, the flow diagram of Fig. 5 may be performed by a network entity or network node in a communications system, such as LTE or 5G NR. For instance, in some example embodiments, the network entity performing the method of Fig. 5 may include a MCPTT client, UE, mobile station, user device, IoT device, or the like.
[0063] In an embodiment, the method of Fig. 5 may include, at 500, receiving a call leave request, from a primary MC system, indicating that a MC user is being de-affiliated from ongoing call(s) provided by the primary MC system. The call leave request may also indicate that the de-affiliation of the MC user is due to migration of the MC user, so that the MCPTT client does not immediately de-affiliate the MC user but waits to receive a late entry or join request from a partner MC system. According to certain embodiments, the MCPTT client does not provide a notification to the MCPTT user of the de-affiliation request. In an embodiment, the method may then include, at 510, transmitting a call leave response to the primary MC system indicating that the de-affiliation will occur together with late entry.
[0064] According to certain embodiments, the method of Fig. 5 may also include, at 520, receiving a call request from the partner MC system indicating initiation of the late entry procedure. The method may then include, at 530, performing the de-affiliation and the late entry for the ongoing calls with the migrated MC user as a participant and, at 540, indicating the migration to the MC user. [0065] Figs. 3-5 include flow diagrams that illustrate certain embodiments of the present disclosure. The procedures described in these figures may be performed, for example, by a network entity, network node, base station, MCPTT system, or other processing device. Some of the procedures illustrated may be performed sequentially, in parallel or in an order other than which is described. Some of the procedures described may also be repeated. In addition, one or more of the example embodiments illustrated respectively in Figs. 3-5 may be combined according to certain embodiments. It should be appreciated that not all of the techniques described are required to be performed, that additional techniques may be added, and that some of the illustrated techniques may be substituted with other techniques. [0066] Fig. 6a illustrates an example of an apparatus 10 according to an embodiment. In an embodiment, apparatus 10 may be a node, host, or server in a communications network or serving such a network. For example, apparatus 10 may be or may include a base station, a Node B, an evolved Node B (eNB), 5G Node B or access point, next generation Node B (NG-NB or gNB), CU of a gNB, WLAN access point, and/or other entity associated with a radio access network, such as 5G or NR. In one example, apparatus 10 may represent a primary MC system as depicted in Figs. 1 or 2. For instance, apparatus 10 may represent one or more of a configuration management server, MC service user database, and/or group management server of a primary MC system.
[0067] As illustrated in the example of Fig. 6a, apparatus 10 may include a processor 12 for processing information and executing instructions or operations. Processor 12 may be any type of general or specific purpose processor. In fact, processor 12 may include one or more of general- purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), and processors based on a multi-core processor architecture, as examples. While a single processor 12 is shown in Fig. 6a, multiple processors may be utilized according to other embodiments. For example, it should be understood that, in certain embodiments, apparatus 10 may include two or more processors that may form a multiprocessor system (e.g., in this case processor 12 may represent a multiprocessor) that may support multiprocessing. In certain embodiments, the multiprocessor system may be tightly coupled or loosely coupled (e.g., to form a computer cluster).
[0068] Processor 12 may perform functions associated with the operation of apparatus 10, which may include, for example, precoding of antenna gain/phase parameters, encoding and decoding of individual bits forming a communication message, formatting of information, and overall control of the apparatus 10, including processes related to management of communication resources.
[0069] Apparatus 10 may further include or be coupled to a memory 14 (internal or external), which may be coupled to processor 12, for storing information and instructions that may be executed by processor 12. Memory 14 may be one or more memories and of any type suitable to the local application environment, and may be implemented using any suitable volatile or nonvolatile data storage technology such as a semiconductor-based memory device, a magnetic memory device and system, an optical memory device and system, fixed memory, and/or removable memory. For example, memory 14 can be comprised of any combination of random access memory (RAM), read only memory (ROM), static storage such as a magnetic or optical disk, hard disk drive (FiDD), or any other type of non-transitory machine or computer readable media. The instructions stored in memory 14 may include program instructions or computer program code that, when executed by processor 12, enable the apparatus 10 to perform tasks as described herein.
[0070] In an embodiment, apparatus 10 may further include or be coupled to (internal or external) a drive or port that is configured to accept and read an external computer readable storage medium, such as an optical disc, USB drive, flash drive, or any other storage medium. For example, the external computer readable storage medium may store a computer program or software for execution by processor 12 and/or apparatus 10. [0071] In some embodiments, apparatus 10 may also include or be coupled to one or more antennas 15 for transmitting and receiving signals and/or data to and from apparatus 10. Apparatus 10 may further include or be coupled to a transceiver 18 configured to transmit and receive information. The transceiver 18 may include, for example, a plurality of radio interfaces that may be coupled to the antenna(s) 15. The radio interfaces may correspond to a plurality of radio access technologies including one or more of GSM, NB-IoT, LTE, 5G, WLAN, Bluetooth, BT-LE, NFC, radio frequency identifier (RFID), ultrawideband (UWB), MulteFire, and the like. The radio interface may include components, such as filters, converters (for example, digital-to-analog converters and the like), mappers, a Fast Fourier Transform (FFT) module, and the like, to generate symbols for a transmission via one or more downlinks and to receive symbols (for example, via an uplink).
[0072] As such, transceiver 18 may be configured to modulate information on to a carrier waveform for transmission by the antenna(s) 15 and demodulate information received via the antenna(s) 15 for further processing by other elements of apparatus 10. In other embodiments, transceiver 18 may be capable of transmitting and receiving signals or data directly. Additionally or alternatively, in some embodiments, apparatus 10 may include an input and/or output device (I/O device).
[0073] In an embodiment, memory 14 may store software modules that provide functionality when executed by processor 12. The modules may include, for example, an operating system that provides operating system functionality for apparatus 10. The memory may also store one or more functional modules, such as an application or program, to provide additional functionality for apparatus 10. The components of apparatus 10 may be implemented in hardware, or as any suitable combination of hardware and software.
[0074] According to some embodiments, processor 12 and memory 14 may be included in or may form a part of processing circuitry or control circuitry. In addition, in some embodiments, transceiver 18 may be included in or may form a part of transceiving circuitry.
[0075] As used herein, the term “circuitry” may refer to hardware-only circuitry implementations (e.g., analog and/or digital circuitry), combinations of hardware circuits and software, combinations of analog and/or digital hardware circuits with software/firmware, any portions of hardware processor(s) with software (including digital signal processors) that work together to case an apparatus (e.g., apparatus 10) to perform various functions, and/or hardware circuit(s) and/or processor(s), or portions thereof, that use software for operation but where the software may not be present when it is not needed for operation. As a further example, as used herein, the term “circuitry” may also cover an implementation of merely a hardware circuit or processor (or multiple processors), or portion of a hardware circuit or processor, and its accompanying software and/or firmware. The term circuitry may also cover, for example, a baseband integrated circuit in a server, cellular network node or device, or other computing or network device. [0076] As introduced above, in certain embodiments, apparatus 10 may be a network node or entity, such as a configuration management server, MC service user database, and/or group management server of a primary MC system, or the like. According to certain embodiments, apparatus 10 may be controlled by memory 14 and processor 12 to perform the functions associated with any of the embodiments described herein. For example, in some embodiments, apparatus 10 may be configured to perform one or more of the processes depicted in any of the flow charts or signaling diagrams described herein, such as the signaling diagram illustrated in Figs. 1 or 2 or flow chart of Figs. 3a or 3b. For instance, in some examples, apparatus 10 may correspond to or represent the primary MC system depicted in Figs. 1 or 2. In certain embodiments, apparatus 10 may be configured to perform a procedure for call participant migration between MC systems.
[0077] In one embodiment, apparatus 10 may be controlled by memory 14 and processor 12 to receive a request for a MC user profile of a user migrating between a primary MC system and a partner MC system. Apparatus 10 may then be controlled by memory 14 and processor 12 to retrieve the MC user profile for the migrating user. According to certain embodiments, apparatus 10 may be controlled by memory 14 and processor 12 to collect ongoing calls having the migrating MC user as a member or participant. In some embodiments, the ongoing calls may be ongoing group calls or ongoing private calls. According to an embodiment, when there are one or more ongoing calls in which the migrating MC user is a participant, apparatus 10 may be controlled by memory 14 and processor 12 to transmit a call leave request to a MCPTT client to indicate that the de-affiliation of the MC user occurs due to migration and to receive a call leave response from the MCPTT client to indicate that the de-affiliation will occur together with late entry.
[0078] In an embodiment, apparatus 10 may be controlled by memory 14 and processor 12 to transmit a response, to the partner MC system, including the information or identifier(s) of the ongoing call(s) that the migrating MC user is participating in. According to some embodiments, apparatus 10 may be controlled by memory 14 and processor 12 to receive a request to validate a modified MC service user profile, to validate the modified MC user profile for migration, and to transmit a response with the validated modified MC service user profile.
[0079] According to another embodiment, apparatus 10 may be controlled by memory 14 and processor 12 to receive a request for a MC user profile of a user migrating between a primary MC system and a partner MC system. In an embodiment, apparatus 10 may be controlled by memory 14 and processor 12 to retrieve the MC user profile for the migrating user. According to certain embodiments, apparatus 10 may be controlled by memory 14 and processor 12 to collect ongoing calls having the migrating MC user as a member or participant. In some embodiments, the ongoing calls may be ongoing group calls or ongoing private calls. According to an embodiment, if there is one or more ongoing calls in which the migrating MC user is a participant, apparatus 10 may be controlled by memory 14 and processor 12 to store an indication that the de-affiliation will occur after a MC user migration synchronization request is received. In an embodiment, apparatus 10 may be controlled by memory 14 and processor 12 to transmit a response, to the partner MC system, including the information or identifier(s) of the ongoing call(s) that the migrating MC user is participating in. According to certain embodiments, when one or more of the call(s) are ongoing in the partner MC system, apparatus 10 may be controlled by memory 14 and processor 12 to receive a MC user migration synchronization request from the partner MC system. Then, in an embodiment, apparatus 10 may be controlled by memory 14 and processor 12 to transmit a call leave request to a MCPTT client to indicate that the de-affiliation of the MC user occurs due to migration and to receive a call leave response from the MCPTT client to indicate that the de-affiliation will occur together with late entry. In an embodiment, apparatus 10 may be controlled by memory 14 and processor 12 to transmit a MC user synchronization response to the partner MC system.
[0080] Fig. 6b illustrates an example of an apparatus 20 according to another example embodiment. In example embodiments, apparatus 20 may be a node or server associated with a radio access network, such as a LTE network, 5G or NR or other radio systems which might benefit from an equivalent procedure. For example, apparatus 20 may be or may include a base station, a Node B, an evolved Node B (eNB), 5G Node B or access point, next generation Node B (NG-NB or gNB), CU of a gNB, WLAN access point, and/or other entity associated with a radio access network, such as 5G or NR. In one example, apparatus 20 may represent a partner MC system as depicted in Figs. 1 or 2. For instance, apparatus 20 may represent one or more of a configuration management server, MC service user database, and/or group management server of a partner MC system. [0081] It should be understood that, in some example embodiments, apparatus 20 may be comprised of an edge cloud server as a distributed computing system where the server and the radio node may be stand-alone apparatuses communicating with each other via a radio path or via a wired connection, or they may be located in a same entity communicating via a wired connection. For instance, in certain example embodiments where apparatus 20 represents a gNB, it may be configured in a central unit (CU) and distributed unit (DU) architecture that divides the gNB functionality. In such an architecture, the CU may be a logical node that includes gNB functions such as transfer of user data, mobility control, radio access network sharing, positioning, and/or session management, etc. The CU may control the operation of DU(s) over a front-haul interface. The DU may be a logical node that includes a subset of the gNB functions, depending on the functional split option. It should be noted that one of ordinary skill in the art would understand that apparatus 20 may include components or features not shown in Fig. 6b.
[0082] In some example embodiments, apparatus 20 may include one or more processors, one or more computer-readable storage medium (for example, memory, storage, or the like), one or more radio access components (for example, a modem, a transceiver, or the like), and/or a user interface. In some example embodiments, apparatus 20 may be configured to operate using one or more radio access technologies, such as GSM, LTE, LTE-A, NR, 5G, WLAN, WiFi, NB-IoT, MuIteFire, and/or any other radio access technologies. It should be noted that one of ordinary skill in the art would understand that apparatus 20 may include components or features not shown in Fig. 6b.
[0083] As illustrated in the example of Fig. 6b, apparatus 20 may include or be coupled to a processor 22 for processing information and executing instructions or operations. Processor 22 may be any type of general or specific purpose processor. In fact, processor 22 may include one or more of general-purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), and processors based on a multi-core processor architecture, as examples. While a single processor 22 is shown in Fig. 6b, multiple processors may be utilized according to other example embodiments. For example, it should be understood that, in certain example embodiments, apparatus 20 may include two or more processors that may form a multiprocessor system (e.g., in this case processor 22 may represent a multiprocessor) that may support multiprocessing. In certain example embodiments, the multiprocessor system may be tightly coupled or loosely coupled (e.g., to form a computer cluster). [0084] Processor 22 may perform functions associated with the operation of apparatus 20 including, as some examples, precoding of antenna gain/phase parameters, encoding and decoding of individual bits forming a communication message, formatting of information, and overall control of the apparatus 20, including processes related to management of communication resources.
[0085] Apparatus 20 may further include or be coupled to a memory 24 (internal or external), which may be coupled to processor 22, for storing information and instructions that may be executed by processor 22. Memory 24 may be one or more memories and of any type suitable to the local application environment, and may be implemented using any suitable volatile or nonvolatile data storage technology such as a semiconductor-based memory device, a magnetic memory device and system, an optical memory device and system, fixed memory, and/or removable memory. For example, memory 24 can be comprised of any combination of random access memory (RAM), read only memory (ROM), static storage such as a magnetic or optical disk, hard disk drive (F1DD), or any other type of non-transitory machine or computer readable media. The instructions stored in memory 24 may include program instructions or computer program code that, when executed by processor 22, enable the apparatus 20 to perform tasks as described herein. [0086] In an example embodiment, apparatus 20 may further include or be coupled to (internal or external) a drive or port that is configured to accept and read an external computer readable storage medium, such as an optical disc, USB drive, flash drive, or any other storage medium. For example, the external computer readable storage medium may store a computer program or software for execution by processor 22 and/or apparatus 20. [0087] In example embodiments, apparatus 20 may also include or be coupled to one or more antennas 25 for receiving a downlink signal and for transmitting via an uplink from apparatus 20. Apparatus 20 may further include a transceiver 28 configured to transmit and receive information. The transceiver 28 may also include a radio interface (e.g., a modem) coupled to the antenna 25. The radio interface may correspond to a plurality of radio access technologies including one or more of GSM, LTE, LTE-A, 5G, NR, WLAN, NB-IoT, BT-LE, RFID, UWB, and the like. The radio interface may include other components, such as filters, converters (for example, digital-to-analog converters and the like), symbol demappers, signal shaping components, an Inverse Fast Fourier Transform (IFFT) module, and the like, to process symbols, such as OFDMA symbols, carried by a downlink or an uplink.
[0088] For instance, in one example embodiment, transceiver 28 may be configured to modulate information on to a carrier waveform for transmission by the antenna(s) 25 and demodulate information received via the antenna(s) 25 for further processing by other elements of apparatus 20. In other example embodiments, transceiver 28 may be capable of transmitting and receiving signals or data directly. Additionally or alternatively, in some example embodiments, apparatus 10 may include an input and/or output device (I/O device). In certain examples, apparatus 20 may further include a user interface, such as a graphical user interface or touchscreen. [0089] In an example embodiment, memory 24 stores software modules that provide functionality when executed by processor 22. The modules may include, for example, an operating system that provides operating system functionality for apparatus 20. The memory may also store one or more functional modules, such as an application or program, to provide additional functionality for apparatus 20. The components of apparatus 20 may be implemented in hardware, or as any suitable combination of hardware and software. According to an example embodiment, apparatus 20 may optionally be configured to communicate with apparatus 10 via a wireless or wired communications link 70 according to any radio access technology, such as NR. For instance, in an example embodiment, link 70 may represent the Xn interface.
[0090] According to some example embodiments, processor 22 and memory 24 may be included in or may form a part of processing circuitry or control circuitry. In addition, in some example embodiments, transceiver 28 may be included in or may form a part of transceiving circuitry.
[0091] As discussed above, according to example embodiments, apparatus 20 may be a network node or entity, such as a configuration management server, MC service user database, and/or group management server of a primary MC system, or the like. According to certain embodiments, apparatus 20 may be controlled by memory 14 and processor 12 to perform the functions associated with any of the embodiments described herein. For example, in some embodiments, apparatus 20 may be configured to perform one or more of the processes depicted in any of the flow charts or signaling diagrams described herein, such as the signaling diagram illustrated in Figs. 1 or 2 or flow chart of Figs. 4a or 4b. For instance, in some examples, apparatus 20 may correspond to or represent the partner MC system depicted in Figs. 1 or 2. In certain embodiments, apparatus 20 may be configured to perform a procedure for call participant migration between MC systems. [0092] According to certain embodiments, apparatus 20 may be controlled by memory 24 and processor 22 to transmit a request for a MC user profile of a user migrating between a primary MC system and a partner MC system. In an embodiment, apparatus 20 may be controlled by memory 24 and processor 22 to receive a response, from the primary MC system, including the information or identifier(s) of the ongoing call(s) that the migrating MC user is a participant at the primary MC system. According to certain embodiments, apparatus 20 may be controlled by memory 24 and processor 22 to retrieve ongoing calls in which the migrating MC user is a participant at the partner MC system. When one or more of the received ongoing call(s) are ongoing in the partner MC system, apparatus 20 may be controlled by memory 24 and processor 22 to initiate a late entry procedure towards a MCPTT client.
[0093] According to another embodiment, apparatus 20 may be controlled by memory 24 and processor 22 to transmit a request for a MC user profile of a user migrating between a primary MC system and a partner MC system. In an embodiment, apparatus 20 may be controlled by memory 24 and processor 22 to receive a response, from the primary MC system, including the information or identifier(s) of the ongoing call(s) that the migrating MC user is a participant at the primary MC system. According to certain embodiments, apparatus 20 may be controlled by memory 24 and processor 22 to retrieve ongoing calls in which the migrating MC user is a participant at the partner MC system. When one or more of the received ongoing call(s) are ongoing in the partner MC system, apparatus 20 may be controlled by memory 24 and processor 22 to transmit a MC user migration synchronization request to the primary MC system and to receive a MC user synchronization response from the primary MC system. In an embodiment, apparatus 20 may be controlled by memory 24 and processor 22 to initiate a late entry procedure towards a MCPTT client.
[0094] Fig. 6c illustrates an example of an apparatus 30 according to another example embodiment. In an example embodiment, apparatus 30 may be a node or element in a communications network or associated with such a network, such as a UE, mobile equipment (ME), mobile station, mobile device, stationary device, IoT device, or other device. As described herein, UE may alternatively be referred to as, for example, a mobile station, mobile equipment, mobile unit, mobile device, user device, subscriber station, wireless terminal, tablet, smart phone, IoT device or NB-IoT device, a connected car, or the like. As one example, apparatus 30 may be implemented in, for instance, a wireless handheld device, a wireless plug-in accessory, or the like. In one embodiment, apparatus 30 may represent or include a MCPTT client, as illustrated in the examples of Figs. 1 or 2.
[0095] In some example embodiments, apparatus 30 may include one or more processors, one or more computer-readable storage medium (for example, memory, storage, or the like), one or more radio access components (for example, a modem, a transceiver, or the like), and/or a user interface. In some example embodiments, apparatus 30 may be configured to operate using one or more radio access technologies, such as GSM, LTE, LTE-A, NR, 5G, WLAN, WiFi, NB-IoT, MulteFire, and/or any other radio access technologies. It should be noted that one of ordinary skill in the art would understand that apparatus 30 may include components or features not shown in Fig. 6c.
[0096] As illustrated in the example of Fig. 6c, apparatus 30 may include or be coupled to a processor 32 for processing information and executing instructions or operations. Processor 32 may be any type of general or specific purpose processor. In fact, processor 32 may include one or more of general-purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), and processors based on a multi-core processor architecture, as examples. While a single processor 32 is shown in Fig. 6c, multiple processors may be utilized according to other example embodiments. For example, it should be understood that, in certain example embodiments, apparatus 30 may include two or more processors that may form a multiprocessor system (e.g., in this case processor 32 may represent a multiprocessor) that may support multiprocessing. In certain example embodiments, the multiprocessor system may be tightly coupled or loosely coupled (e.g., to form a computer cluster). [0097] Processor 32 may perform functions associated with the operation of apparatus 30 including, as some examples, precoding of antenna gain/phase parameters, encoding and decoding of individual bits forming a communication message, formatting of information, and overall control of the apparatus 30, including processes related to management of communication resources.
[0098] Apparatus 30 may further include or be coupled to a memory 34 (internal or external), which may be coupled to processor 32, for storing information and instructions that may be executed by processor 32. Memory 34 may be one or more memories and of any type suitable to the local application environment, and may be implemented using any suitable volatile or nonvolatile data storage technology such as a semiconductor-based memory device, a magnetic memory device and system, an optical memory device and system, fixed memory, and/or removable memory. For example, memory 34 can be comprised of any combination of random access memory (RAM), read only memory (ROM), static storage such as a magnetic or optical disk, hard disk drive (F1DD), or any other type of non-transitory machine or computer readable media. The instructions stored in memory 34 may include program instructions or computer program code that, when executed by processor 32, enable the apparatus 30 to perform tasks as described herein. [0099] In an example embodiment, apparatus 30 may further include or be coupled to (internal or external) a drive or port that is configured to accept and read an external computer readable storage medium, such as an optical disc, USB drive, flash drive, or any other storage medium. For example, the external computer readable storage medium may store a computer program or software for execution by processor 32 and/or apparatus 30. [00100] In some example embodiments, apparatus 30 may also include or be coupled to one or more antennas 35 for receiving a downlink signal and for transmitting via an uplink from apparatus 30. Apparatus 30 may further include a transceiver 38 configured to transmit and receive information. The transceiver 38 may also include a radio interface (e.g., a modem) coupled to the antenna 35. The radio interface may correspond to a plurality of radio access technologies including one or more of GSM, LTE, LTE-A, 5G, NR, WLAN, NB-IoT, BT-LE, RFID, UWB, and the like. The radio interface may include other components, such as filters, converters (for example, digital- to-analog converters and the like), symbol demappers, signal shaping components, an Inverse Fast Fourier Transform (IFFT) module, and the like, to process symbols, such as OFDMA symbols, carried by a downlink or an uplink.
[00101] For instance, transceiver 38 may be configured to modulate information on to a carrier waveform for transmission by the antenna(s) 35 and demodulate information received via the antenna(s) 35 for further processing by other elements of apparatus 30. In other example embodiments, transceiver 38 may be capable of transmitting and receiving signals or data directly. Additionally or alternatively, in some example embodiments, apparatus 30 may include an input and/or output device (I/O device). In certain example embodiments, apparatus 30 may further include a user interface, such as a graphical user interface or touchscreen. [00102] In an example embodiment, memory 34 stores software modules that provide functionality when executed by processor 32. The modules may include, for example, an operating system that provides operating system functionality for apparatus 30. The memory may also store one or more functional modules, such as an application or program, to provide additional functionality for apparatus 30. The components of apparatus 30 may be implemented in hardware, or as any suitable combination of hardware and software. According to an example embodiment, apparatus 30 may optionally be configured to communicate with apparatus 10 via a wireless or wired communications link 71 and/or to communicate with apparatus 20 via a wireless or wired communications link 72, according to any radio access technology, such as NR.
[00103] According to some example embodiments, processor 32 and memory 34 may be included in or may form a part of processing circuitry or control circuitry. In addition, in some example embodiments, transceiver 38 may be included in or may form a part of transceiving circuitry. [00104] As discussed above, according to some example embodiments, apparatus 30 may be a MCPTT client, UE, mobile device, mobile station, ME, IoT device and/or NB-IoT device, for example. According to certain example embodiments, apparatus 30 may be controlled by memory 34 and processor 32 to perform the functions associated with example embodiments described herein. For instance, in some embodiments, apparatus 30 may be configured to perform one or more of the processes depicted in any of the diagrams or signaling flow diagrams described herein, such as those illustrated in Figs. 1, 2 or 5. As an example, apparatus 30 may correspond to the MCPTT client in Figs. 1 or 2. [00105] In on embodiment, apparatus 30 may be controlled by memory 34 and processor 32 to receive a call leave request, from a primary MC system, indicating that a MC user is being de- affiliated from ongoing call(s) provided by the primary MC system. The call leave request may also indicate that the de-affiliation of the MC user is due to migration of the MC user, so that apparatus 30 does not immediately de-affiliate the MC user but waits to receive a late entry or join request from a partner MC system. According to certain embodiments, apparatus 30 does not provide a notification to the MCPTT user of the de-affiliation request. In an embodiment, apparatus 30 may be controlled by memory 34 and processor 32 to transmit a call leave response to the primary MC system indicating that the de-affiliation will occur together with late entry.
[00106] According to certain embodiments, apparatus 30 may be controlled by memory 34 and processor 32 to receive a call request from the partner MC system indicating initiation of the late entry procedure. In an embodiment, apparatus 30 may then be controlled by memory 34 and processor 32 to perform the de-affiliation and the late entry for the ongoing calls with the migrated MC user as a participant and to indicate the migration to the MC user.
[00107] Therefore, certain example embodiments provide several technological improvements, enhancements, and/or advantages over existing technological processes and constitute an improvement at least to the technological field of wireless network control and management. For example, certain embodiments provide a system and method for efficient MC user migration between MCPTT systems, for example, in the case of interconnecting group calls. Currently, if an MC user is migrated then they need to reinitiate or rejoin to the previous call under the partner MCPTT system. However, as discussed in detail above, example embodiments are able to provide seamless call continuity and quality. Example embodiments described herein, in addition to defining the possibility of MC user migration during ongoing call, provide for the migration in a seamless and automatic way. In certain embodiments, migration can occur without MC user interaction or even without any notifiable interruption in the call during the migration. As a result, example embodiments may at least improve throughput, latency, and/or processing speed of network nodes and/or UEs. Accordingly, the use of certain example embodiments results in improved functioning of communications networks and their nodes, such as base stations, eNBs, gNBs, and/or UEs or mobile stations.
[00108] In some example embodiments, the functionality of any of the methods, processes, signaling diagrams, algorithms or flow charts described herein may be implemented by software and/or computer program code or portions of code stored in memory or other computer readable or tangible media, and executed by a processor.
[00109] In some example embodiments, an apparatus may be included or be associated with at least one software application, module, unit or entity configured as arithmetic operation(s), or as a program or portions of it (including an added or updated software routine), executed by at least one operation processor. Programs, also called program products or computer programs, including software routines, applets and macros, may be stored in any apparatus-readable data storage medium and may include program instructions to perform particular tasks. [00110] A computer program product may include one or more computer-executable components which, when the program is run, are configured to carry out some example embodiments. The one or more computer-executable components may be at least one software code or portions of code. Modifications and configurations required for implementing functionality of an example embodiment may be performed as routine(s), which may be implemented as added or updated software routine(s). In one example, software routine(s) may be downloaded into the apparatus. [00111] As an example, software or computer program code or portions of code may be in source code form, object code form, or in some intermediate form, and it may be stored in some sort of carrier, distribution medium, or computer readable medium, which may be any entity or device capable of carrying the program. Such carriers may include a record medium, computer memory, read-only memory, photoelectrical and/or electrical carrier signal, telecommunications signal, and/or software distribution package, for example. Depending on the processing power needed, the computer program may be executed in a single electronic digital computer or it may be distributed amongst a number of computers. The computer readable medium or computer readable storage medium may be a non-transitory medium.
[00112] In other example embodiments, the functionality may be performed by hardware or circuitry included in an apparatus (e.g., apparatus 10 or apparatus 20 or apparatus 30), for example through the use of an application specific integrated circuit (ASIC), a programmable gate array (PGA), a field programmable gate array (FPGA), or any other combination of hardware and software. In yet another example embodiment, the functionality may be implemented as a signal, such as a non-tangible means, that can be carried by an electromagnetic signal downloaded from the Internet or other network.
[00113] According to an example embodiment, an apparatus, such as a node, device, or a corresponding component, may be configured as circuitry, a computer or a microprocessor, such as single-chip computer element, or as a chipset, which may include at least a memory for providing storage capacity used for arithmetic operation(s) and/or an operation processor for executing the arithmetic operation(s).
[00114] One having ordinary skill in the art will readily understand that the example embodiments as discussed above may be practiced with procedures in a different order, and/or with hardware elements in configurations which are different than those which are disclosed. Therefore, although some embodiments have been described based upon these example embodiments, it would be apparent to those of skill in the art that certain modifications, variations, and alternative constructions would be apparent, while remaining within the spirit and scope of example embodiments.

Claims

CLAIMS We Claim:
1. An apparatus, comprising: at least one processor; and at least one memory comprising computer program code, the at least one memory and computer program code configured, with the at least one processor, to cause the apparatus at least to receive a request for a mission critical (MC) user profile of a user migrating between a primary mission critical (MC) system and a partner mission critical (MC) system; retrieve the mission critical (MC) user profile for the migrating mission critical (MC) user; collect one or more ongoing calls having the migrating mission critical (MC) user as a participant at the primary mission critical (MC) system; and transmit, to the partner mission critical (MC) system, information or identifiers of the one or more ongoing calls that the migrating mission critical (MC) user is a participant.
2. The apparatus according to claim 1, wherein, when there are one or more ongoing calls in which the migrating mission critical (MC) user is a participant, the at least one memory and computer program code are configured, with the at least one processor, to cause the apparatus at least to: transmit a call leave request to a mission critical (MC) client to indicate that the de-affiliation of the mission critical (MC) user is occurring due to migration; and receive a call leave response from the mission critical (MC) client to indicate that the de affiliation will occur together with late entry of the ongoing calls that the mission critical (MC) user is a participant.
3. The apparatus according to claim 1, wherein, when there are one or more ongoing calls in which the migrating mission critical (MC) user is a participant, the at least one memory and computer program code are configured, with the at least one processor, to cause the apparatus at least to: store an indication that the de-affiliation will occur after a mission critical (MC) user migration synchronization request is received.
4. The apparatus according to claim 3, wherein, when one or more of the ongoing calls are ongoing in the partner mission critical system, the at least one memory and computer program code are configured, with the at least one processor, to cause the apparatus at least to: receive a mission critical (MC) user migration synchronization request from the partner MC system.
5. The apparatus according to claim 4, wherein the at least one memory and computer program code are configured, with the at least one processor, to cause the apparatus at least to: transmit a call leave request to a mission critical (MC) client to indicate that the de-affiliation of the mission critical user is occurring due to migration; and receive a call leave response from the mission critical (MC) client to indicate that the de affiliation will occur together with late entry of the ongoing calls that the mission critical (MC) user is a participant.
6. The apparatus according to claim 5, wherein the at least one memory and computer program code are configured, with the at least one processor, to cause the apparatus at least to: transmit a mission critical (MC) user synchronization response to the partner mission critical (MC) system.
7. The apparatus according to any of claims 1-6, wherein the one or more ongoing calls comprise at least one of ongoing group calls or ongoing private calls.
8. A method, comprising: receiving a request for a mission critical (MC) user profile of a user migrating between a primary mission critical (MC) system and a partner mission critical (MC) system; retrieving the mission critical (MC) user profile for the migrating mission critical (MC) user; collecting one or more ongoing calls having the migrating mission critical (MC) user as a participant at the primary mission critical (MC) system; and transmitting, to the partner mission critical (MC) system, information or identifiers of the one or more ongoing calls that the migrating mission critical (MC) user is a participant.
9. The method according to claim 8, wherein, when there are one or more ongoing calls in which the migrating mission critical (MC) user is a participant, the method comprises: transmitting a call leave request to a mission critical (MC) client to indicate that the de affiliation of the mission critical (MC) user is occurring due to migration; and receiving a call leave response from the mission critical (MC) client to indicate that the de affiliation will occur together with late entry of the ongoing calls that the mission critical (MC) user is a participant.
10. The method according to claim 8, wherein, when there are one or more ongoing calls in which the migrating mission critical (MC) user is a participant, the method comprises: storing an indication that the de-affiliation will occur after a mission critical (MC) user migration synchronization request is received.
11. The method according to claim 10, wherein, when one or more of the ongoing calls are ongoing in the partner mission critical system, the method comprises: receiving a mission critical (MC) user migration synchronization request from the partner MC system.
12. The method according to claim 11, further comprising: transmitting a call leave request to a mission critical (MC) client to indicate that the de affiliation of the mission critical user is occurring due to migration; and receiving a call leave response from the mission critical (MC) client to indicate that the de affiliation will occur together with late entry of the ongoing calls that the mission critical (MC) user is a participant.
13. The method according to claim 12, further comprising: transmitting a mission critical (MC) user synchronization response to the partner mission critical (MC) system.
14. The method according to any of claims 8-13, wherein the one or more ongoing calls comprise at least one of ongoing group calls or ongoing private calls.
15. An apparatus, comprising: means for receiving a request for a mission critical (MC) user profile of a user migrating between a primary mission critical (MC) system and a partner mission critical (MC) system; means for retrieving the mission critical (MC) user profile for the migrating mission critical (MC) user; means for collecting one or more ongoing calls having the migrating mission critical (MC) user as a participant at the primary mission critical (MC) system; and means for transmitting, to the partner mission critical (MC) system, information or identifiers of the one or more ongoing calls that the migrating mission critical (MC) user is a participant.
16. The apparatus according to claim 15, wherein, when there are one or more ongoing calls in which the migrating mission critical (MC) user is a participant, the apparatus comprises: means for transmitting a call leave request to a mission critical (MC) client to indicate that the de-affiliation of the mission critical (MC) user is occurring due to migration; and means for receiving a call leave response from the mission critical (MC) client to indicate that the de-affiliation will occur together with late entry of the ongoing calls that the mission critical (MC) user is a participant.
17. The apparatus according to claim 15, wherein, when there are one or more ongoing calls in which the migrating mission critical (MC) user is a participant, the apparatus comprises: means for storing an indication that the de-affiliation will occur after a mission critical (MC) user migration synchronization request is received.
18. The apparatus according to claim 17, wherein, when one or more of the ongoing calls are ongoing in the partner mission critical system, the apparatus comprises: means for receiving a mission critical (MC) user migration synchronization request from the partner MC system.
19. The apparatus according to claim 18, further comprising: means for transmitting a call leave request to a mission critical (MC) client to indicate that the de-affiliation of the mission critical user is occurring due to migration; and means for receiving a call leave response from the mission critical (MC) client to indicate that the de-affiliation will occur together with late entry of the ongoing calls that the mission critical (MC) user is a participant.
20. The apparatus according to claim 19, further comprising: means for transmitting a mission critical (MC) user synchronization response to the partner mission critical (MC) system.
21. An apparatus, comprising: at least one processor; and at least one memory comprising computer program code, the at least one memory and computer program code configured, with the at least one processor, to cause the apparatus at least to transmit a request for a mission critical (MC) user profile of a user migrating between a primary mission critical (MC) system and a partner mission critical (MC) system; receive information or identifier(s) of one or more ongoing calls that the migrating mission critical (MC) user is a participant at the primary MC system; retrieve ongoing calls in which the migrating mission critical (MC) user is a participant at the partner mission critical (MC) system; and when one or more of the received ongoing call(s) are ongoing in the partner mission critical (MC) system, initiate a late entry procedure towards a mission critical (MC) client.
22. The apparatus according to claim 21, wherein, prior to the initiating of the late entry procedure, the at least one memory and computer program code are configured, with the at least one processor, to cause the apparatus at least to: transmit a mission critical (MC) user migration synchronization request to the primary mission critical (MC) system; and receive a mission critical (MC) user synchronization response from the primary mission critical (MC) system.
23. A method, comprising: transmitting a request for a mission critical (MC) user profile of a user migrating between a primary mission critical (MC) system and a partner mission critical (MC) system; receiving information or identifier(s) of one or more ongoing calls that the migrating mission critical (MC) user is a participant at the primary MC system; retrieving ongoing calls in which the migrating mission critical (MC) user is a participant at the partner mission critical (MC) system; and when one or more of the received ongoing call(s) are ongoing in the partner mission critical (MC) system, initiating a late entry procedure towards a mission critical (MC) client.
24. The method according to claim 23, wherein, prior to the initiating of the late entry procedure, the method comprises: transmitting a mission critical (MC) user migration synchronization request to the primary mission critical (MC) system; and receiving a mission critical (MC) user synchronization response from the primary mission critical (MC) system.
25. An apparatus, comprising: means for transmitting a request for a mission critical (MC) user profile of a user migrating between a primary mission critical (MC) system and a partner mission critical (MC) system; means for receiving information or identifier(s) of one or more ongoing calls that the migrating mission critical (MC) user is a participant at the primary MC system; means for retrieving ongoing calls in which the migrating mission critical (MC) user is a participant at the partner mission critical (MC) system; and when one or more of the received ongoing call(s) are ongoing in the partner mission critical (MC) system, means for initiating a late entry procedure towards a mission critical (MC) client.
26. The apparatus according to claim 25, wherein, prior to the initiating of the late entry procedure, the apparatus comprises: means for transmitting a mission critical (MC) user migration synchronization request to the primary mission critical (MC) system; and means for receiving a mission critical (MC) user synchronization response from the primary mission critical (MC) system.
27. An apparatus, comprising: at least one processor; and at least one memory comprising computer program code, the at least one memory and computer program code configured, with the at least one processor, to cause the apparatus at least to receive a call leave request, from a primary mission critical (MC) system, indicating that a mission critical (MC) user is being de-affiliated from one or more ongoing calls provided by the primary mission critical (MC) system, wherein the call leave request further comprises an indication that the de-affiliation of the mission critical (MC) user is due to migration of the mission critical (MC) user to a partner mission critical (MC) system; receive a call request from the partner mission critical (MC) system indicating initiation of the late entry procedure; perform the de-affiliation and the late entry for the ongoing calls with the migrated mission critical (MC) user as a participant; and indicate the migration to the mission critical (MC) user.
28. The apparatus according to claim 27, wherein the apparatus does not provide a notification to the mission critical (MC) user of the de-affiliation request until after receiving the indication of the late entry procedure from the partner mission critical (MC) system.
29. The apparatus according to claims 27 or 28, the at least one memory and computer program code configured, with the at least one processor, to cause the apparatus at least to transmit a call leave response to the primary mission critical (MC) system indicating that the de-affiliation will occur together with late entry.
30. A method, comprising: receiving a call leave request, from a primary mission critical (MC) system, indicating that a mission critical (MC) user is being de-affiliated from one or more ongoing calls provided by the primary mission critical (MC) system, wherein the call leave request further comprises an indication that the de-affiliation of the mission critical (MC) user is due to migration of the mission critical (MC) user to a partner mission critical (MC) system; receiving a call request from the partner mission critical (MC) system indicating initiation of the late entry procedure; performing the de-affiliation and the late entry for the ongoing calls with the migrated mission critical (MC) user as a participant; and indicating the migration to the mission critical (MC) user.
31. The method according to claim 30, wherein the partner mission critical (MC) system does not provide a notification to the mission critical (MC) user of the de-affiliation request until after receiving the indication of the late entry procedure from the partner mission critical (MC) system.
32. The method according to claims 30 or 31, further comprising transmitting a call leave response to the primary mission critical (MC) system indicating that the de-affiliation will occur together with late entry.
33. An apparatus, comprising: means for receiving a call leave request, from a primary mission critical (MC) system, indicating that a mission critical (MC) user is being de-affiliated from one or more ongoing calls provided by the primary mission critical (MC) system, wherein the call leave request further comprises an indication that the de-affiliation of the mission critical (MC) user is due to migration of the mission critical (MC) user to a partner mission critical (MC) system; means for receiving a call request from the partner mission critical (MC) system indicating initiation of the late entry procedure; means for performing the de-affiliation and the late entry for the ongoing calls with the migrated mission critical (MC) user as a participant; and means for indicating the migration to the mission critical (MC) user.
34. The apparatus according to claim 33, wherein the partner mission critical (MC) system does not provide a notification to the mission critical (MC) user of the de-affiliation request until after receiving the indication of the late entry procedure from the partner mission critical (MC) system.
35. The apparatus according to claims 33 or 34, further comprising means for transmitting a call leave response to the primary mission critical (MC) system indicating that the de-affiliation will occur together with late entry.
36. A non-transitory computer readable medium comprising program instructions stored thereon for performing at least the method according to any of claims 8-14, 23-24, or 30-32.
PCT/IB2020/056204 2020-07-01 2020-07-01 Call participant migration between mission critical push-to-talk (mcptt) servers WO2022003400A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/IB2020/056204 WO2022003400A1 (en) 2020-07-01 2020-07-01 Call participant migration between mission critical push-to-talk (mcptt) servers

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/IB2020/056204 WO2022003400A1 (en) 2020-07-01 2020-07-01 Call participant migration between mission critical push-to-talk (mcptt) servers

Publications (1)

Publication Number Publication Date
WO2022003400A1 true WO2022003400A1 (en) 2022-01-06

Family

ID=71465394

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2020/056204 WO2022003400A1 (en) 2020-07-01 2020-07-01 Call participant migration between mission critical push-to-talk (mcptt) servers

Country Status (1)

Country Link
WO (1) WO2022003400A1 (en)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020015606A1 (en) * 2018-07-16 2020-01-23 华为技术有限公司 Communication method, device and system

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020015606A1 (en) * 2018-07-16 2020-01-23 华为技术有限公司 Communication method, device and system

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Functional architecture and information flows to support Mission Critical Push To Talk (MCPTT); Stage 2 (Release 17)", vol. SA WG6, no. V17.2.0, 24 March 2020 (2020-03-24), pages 1 - 245, XP051861428, Retrieved from the Internet <URL:ftp://ftp.3gpp.org/Specs/archive/23_series/23.379/23379-h20.zip> [retrieved on 20200324] *
ERICSSON: "Functional model and procedure for switching between primary and IOPS MC system", vol. SA WG6, no. Sophia Antipolis, France; 20180723 - 20180727, 16 July 2018 (2018-07-16), XP051503899, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg%5Fsa/WG6%5FMissionCritical/TSGS6%5F025%5FSophia%5FAntipolis/docs/S6%2D181045%2Ezip> [retrieved on 20180716] *
MOTOROLA SOLUTIONS: "User profile retrieval for migration", vol. SA WG6, no. Malmö, Sweden; 20170717 - 20170721, 11 September 2017 (2017-09-11), XP051326311, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings_3GPP_SYNC/SA/Docs/> [retrieved on 20170911] *

Similar Documents

Publication Publication Date Title
US10841816B2 (en) Configuration of failure detection reference signals
WO2020002507A1 (en) Methods and apparatuses for discovering a network function acting as network function service consumer
US20240015044A1 (en) Separate session start request indication
US11190928B2 (en) Data storage function selection
US10581495B2 (en) Physical layer configuration continuity during radio resource control restoration
EP3735086A1 (en) Buffer status report for sidelink resource allocation
EP3979680A1 (en) Enhanced location services in 5g
WO2022234458A1 (en) Efficient registration in an area where a slice service is supported partially
WO2022148627A1 (en) Methods and apparatuses for multicast-broadcast service (mbs) activation and deactivation
US11849358B2 (en) Handover of a coordinated multi-point connection
US20230319511A1 (en) Policy control for 5g multicast-broadcast services (5mbs)
US20220322214A1 (en) Filtered authorization list for private networks
WO2022003400A1 (en) Call participant migration between mission critical push-to-talk (mcptt) servers
US11812322B2 (en) Channel state information reference signal configuration for inter-cell mobility
US11653368B2 (en) Selective over the air reconfiguration of unicast multimedia broadcast single frequency network (MBSFN)
US20230068412A1 (en) Ad hoc group based services to support 5g system (5gs) scenarios
US20230328578A1 (en) Selection of shared central unit user plane by central unit control plane
US11228960B2 (en) Efficient signaling in multi-connectivity scenarios
US11943812B2 (en) Determining random access channel (RACH) resources or parameters based on network slice-based resource allocation classes (RACs)
US11849355B2 (en) Handover optimization using time sensitive communication assistance information

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20736792

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20736792

Country of ref document: EP

Kind code of ref document: A1