WO2019088886A1 - Group communications during iops - Google Patents

Group communications during iops Download PDF

Info

Publication number
WO2019088886A1
WO2019088886A1 PCT/SE2017/051077 SE2017051077W WO2019088886A1 WO 2019088886 A1 WO2019088886 A1 WO 2019088886A1 SE 2017051077 W SE2017051077 W SE 2017051077W WO 2019088886 A1 WO2019088886 A1 WO 2019088886A1
Authority
WO
WIPO (PCT)
Prior art keywords
client node
server
local
group
communications system
Prior art date
Application number
PCT/SE2017/051077
Other languages
French (fr)
Inventor
Magnus TRÄNK
Daniel GULDBRAND
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
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 Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Priority to PCT/SE2017/051077 priority Critical patent/WO2019088886A1/en
Publication of WO2019088886A1 publication Critical patent/WO2019088886A1/en

Links

Classifications

    • 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/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H04W4/08—User group management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/40—Connection management for selective distribution or broadcast
    • H04W76/45—Connection management for selective distribution or broadcast for Push-to-Talk [PTT] or Push-to-Talk over cellular [PoC] 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]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/04—Large scale networks; Deep hierarchical networks
    • H04W84/08—Trunked mobile radio systems

Definitions

  • Embodiments presented herein relate to methods, a client node, a local group communications server, a computer program, and a computer program product for operation in a group communications system during Isolated E- UTRAN Operations for Public Safety.
  • MC mission critical
  • communications services generally require preferential handling compared to traditional telecommunication services, including handling of prioritized MC calls for emergency and imminent threats. Furthermore, MC
  • communications services might require several resilience features that provide a guaranteed service level, even if part of the network or backhaul infrastructure fails.
  • group communications So-called group communications (GC) system can be used to facilitate MC communications services.
  • group communication means that the same information or media is delivered to multiple client nodes.
  • group communication systems e.g., Push-To-Talk (PTT) systems, or Mission Critical Push-To-Talk (MCPTT) systems
  • PTT Push-To-Talk
  • MCPTT Mission Critical Push-To-Talk
  • client nodes receiving the same media constitute a group of client nodes.
  • a GC system might be designed with a centralized architecture approach, in which a centralized GC server provides full control of all the group data, e.g. group identities, group membership, policies, user authorities, group call control attributes, such as affiliation statues and prioritizations.
  • group data e.g. group identities, group membership, policies, user authorities, group call control attributes, such as affiliation statues and prioritizations.
  • group call control attributes such as affiliation statues and prioritizations.
  • TMO Trunked Mode Operation
  • a GC system might, alternatively, be designed with a decentralized architecture approach, in which a centralized GC server provides full control of all the group data, e.g. group identities, group membership, policies, user authorities, group call control attributes, such as affiliation statues and prioritizations.
  • TMO Trunked Mode Operation
  • a GC system might, alternatively, be designed with a decentralized GC server
  • DMO Direct Mode Operation
  • incumbent GC systems might provide a resilience feature that allows a local radio access network to provide local connectivity and GC services to the client nodes within the network coverage of the local radio access network even if the radio access network loses its operational connection to other parts of the network, such as to the packet core network of the public land mobile network (PLMN). This type of operation is sometimes referred to as Local Site Trunking.
  • PLMN public land mobile network
  • IOPS Isolated E-UTRAN Operations for Public Safety
  • UMTS Evolved Universal Mobile Telecommunications System
  • the IOPS functionality provides local connectivity to public safety client nodes that are within the communication range of the E-UTRAN radio access network node; the so-called evolved Node B (eNB) that supports IOPS operation.
  • eNB evolved Node B
  • the IOPS functionality can be used in different types of
  • Radio access network node located on a remote location (e.g. an island), where the radio access network node is operatively connected to the packet core network via e.g. a satellite link. If there is a satellite link failure, it is critical for user of MC
  • communications services to be able to at least have local connectivity for the communication between the users in the coverage of the radio access network node.
  • One way to provide IOPS operation is to deploy a GC system and a local packet core network in each radio access network node. This also includes deploying a local user database with group data as defined above, together with user identities and authentication keys.
  • the local user database can be provided in a local GC system having a local GC server.
  • the local GC server typically resides in the radio access network node that will provide the IOPS operation. In this respect, in order to provide a GC service with an acceptable service level in IOPS, it is then required that the GC service data is
  • synchronization is challenging, not only because of the amount of group data that needs to be synchronized, but also because of the dynamic aspect of the group data, and the pure number of radio access network nodes (and local GC servers) that are involved in the synchronization.
  • An object of embodiments herein is to provide efficient operation in a group communications system during IOPS.
  • a method for operation in a group communications system during IOPS mode is performed by a client node.
  • the method comprises obtaining an indication of operation in IOPS mode being entered.
  • the method comprises registering, in response to obtaining the indication, with a local GC server located in a radio access network of the group communications system.
  • the method comprises providing information to the local GC server regarding off-network group configuration of the client node.
  • a client node for operation in a group communications system during IOPS mode The client node comprises processing circuitry.
  • the processing circuitry is configured to cause the client node to obtain an indication of operation in IOPS mode being entered.
  • the processing circuitry is configured to cause the client node to register, in response to obtaining the indication, with a local GC server located in a radio access network of the group communications system.
  • the processing circuitry is configured to cause the client node to provide information to the local GC server regarding off-network group configuration of the client node.
  • a client node for operation in a group communications system during IOPS mode.
  • the client node comprises an obtain module configured to obtain an indication of operation in IOPS mode being entered.
  • the client node comprises a register module configured to register, in response to obtaining the indication, with a local GC server located in a radio access network of the group communications system.
  • the client node comprises a provide module configured to provide information to the local GC server regarding off-network group configuration of the client node.
  • a computer program for operation in a group communications system during IOPS mode The computer program comprises computer program code which, when run on processing circuitry of a client node, causes the client node to perform a method according to the first aspect.
  • a method for operation in a group communications system during IOPS mode is performed by a local GC server.
  • the local GC server is located in a radio access network of the group communications system.
  • the method comprises registering the client node upon operation in IOPS mode is entered.
  • the method comprises obtaining information from the client node regarding off-network group configuration of the client node.
  • a local GC server for operation in a group communications system during IOPS mode The local GC server is located in a radio access network of the group communications system.
  • the local GC server comprises processing circuitry.
  • the processing circuitry is configured to cause the local GC server to register the client node upon operation in IOPS mode is entered.
  • the processing circuitry is configured to cause the local GC server to obtain information from the client node regarding off-network group configuration of the client node.
  • a local GC server for operation in a group communications system during IOPS mode.
  • the local GC server is located in a radio access network of the group communications system.
  • the local GC server comprises a register module configured to register the client node upon operation in IOPS mode is entered.
  • the local GC server comprises an obtain module configured to obtain information from the client node regarding off-network group configuration of the client node.
  • a computer program for operation in a group communications system during IOPS mode comprising computer program code which, when run on processing circuitry of a local GC server, causes the local GC server to perform a method according to the fifth aspect.
  • a computer program product comprising a computer program according to at least one of the fourth aspect and the eight aspect and a computer readable storage medium on which the computer program is stored.
  • the computer readable storage medium could be a non-transitory computer readable storage medium.
  • these client nodes, these local GC servers, and these computer programs provide efficient operation in a group communications system during IOPS.
  • these client nodes, these local GC servers, and these computer programs enable improved, with respect to traditional IOPS operation, data synchronization of the local GC server that enables group communications during IOPS operation .
  • these client nodes, these local GC servers, and these computer programs provide a significantly reduction in complexity for synchronizing the group data between a centralized GC server and the local GC server in the case of IOPS.
  • these client nodes, these local GC servers, and these computer programs enable synchronization only to be performed based on need, and hence not all radio access network nodes in a network are required to be synchronized in terms of group data.
  • any feature of the first, second, third, fourth, fifth, sixth seventh, eight, and ninth aspects may be applied to any other aspect, wherever appropriate.
  • any advantage of the first aspect may equally apply to the second, third, fourth, fifth, sixth, seventh, eight, and/ or ninth aspect, respectively, and vice versa.
  • FIG. 1 is a schematic diagram illustrating a communications system according to embodiments
  • FIGS. 2 and 3 are flowcharts of methods according to embodiments
  • Fig. 4 is a signalling diagram according to an embodiment
  • Fig. 5 is a schematic diagram showing functional units of a client node according to an embodiment
  • Fig. 6 is a schematic diagram showing functional modules of a client node according to an embodiment
  • Fig. 7 is a schematic diagram showing functional units of a local GC server according to an embodiment
  • Fig. 8 is a schematic diagram showing functional modules of a local GC server according to an embodiment.
  • Fig. 9 shows one example of a computer program product comprising computer readable means according to an embodiment.
  • FIG. 1 is a schematic diagram illustrating a communications system 100 where embodiments presented herein can be applied.
  • the communications system 100 may be regarded as a wireless communications system.
  • the group communications system 100 is a MC system.
  • the group communications system 100 is a MC PTT system.
  • the wireless communications system provides services to client nodes 200a, 200b, 200c.
  • client nodes 200a and 200b are assumed to be group affiliated, thus belonging to the same group 150 of clients within the group communications system.
  • Each client node 200a, 200b, 200c may be provided in, or installed on, a respective wireless device 160a, 160b, 160c.
  • a step, action, or similar that is performed by a client node 200a, 200b, 200c is, in some aspects, also performed by the wireless device 160a, 160b, 160c in which the client node 200a, 200b, 200c is provided.
  • the communications system 100 comprises a radio access network 120, a packet core network (PCN) 130 of a PLMN, and a service network 140.
  • the communications system 100 further comprises centralized GC server 170 as provided in the service network 140 and at least one local GC server 300.
  • the at least one local GC server 300 may be provided in, or installed on, a radio access network node 110 or in another entity or device in the radio access network 120.
  • Each of the centralized GC server 170 and the at least one local GC server 300 might be a MC service server, such as a MC video server, a MC data server, and/ or a MC PTT server.
  • the radio access network 120 is operatively connected to the packet core network 130 which in turn is operatively connected to the service network 140.
  • the radio access network node 110 thereby enables the wireless devices 160a, 160b, 160c, and hence the client nodes 200a, 200b, 200c in the wireless device 160a, 160b, 160c, respectively, to access services and exchange data as provided by the service network 140.
  • the client nodes 200a, 200b, 200c are thereby enabled to communicate with the centralized GC server 170.
  • wireless devices 160a, 160b, 160c include, but are not limited to, mobile stations, mobile phones, handsets, wireless local loop phones, user equipment (UE), smartphones, laptop computers, and tablet computers.
  • radio access network nodes 110 include, but are not limited to, radio base stations, base transceiver stations, node Bs, evolved node Bs, and access points.
  • the communications system 100 may comprise a plurality of radio access network nodes 110 , each providing network access to a plurality of wireless devices 160a, 160b, 160c.
  • the herein disclosed embodiments are not limited to any particular number of radio access network nodes 110, client nodes 200a, 200b, 200c, or wireless devices 160a, 160b, 160c. Any of the nodes indicated herein may be seen as functions, where each function may be implemented in one or more physical entities.
  • the at least one local GC server 300 could in such situations provide a GC service for the client nodes 200a, 200b, 200c. As further disclosed above, traditionally, this requires extensive data synchronization between the at least one local GC server 300 in each radio access network node 110 that enables group communications during IOPS operation and the centralized GC server 170.
  • the embodiments disclosed herein therefore relate to mechanisms for operation in a group communications system during IOPS not suffering from the issues noted above, or at least where these issues are mitigated or reduced.
  • a client node 200a In order to obtain such mechanisms there is provided a client node 200a, a method performed by the client node 200a, a computer program product comprising code, for example in the form of a computer program, that when run on processing circuitry of the client node 200a, causes the client node 200a to perform the method.
  • a local GC server 300 In order to obtain such mechanisms there is further provided a local GC server 300, a method performed by the local GC server 300, and a computer program product comprising code, for example in the form of a computer program, that when run on processing circuitry of the local GC server 300 , causes the local GC server 300 to perform the method.
  • the at least one local GC server 300 is not required to permanently store user and group
  • each client node 200a, 200b, 200c is pre-provisioned with configuration information, such as off-network group configuration information, for opera tion during IOPS mode.
  • the group configuration information is provided to the local GC server 300 when needed, i.e. when the radio access network node 110 needs to provide local connectivity by using IOPS.
  • the off-network group configuration information might be a subset of the complete group configuration information in a traditional GC system. This subset comprises at least group identity, group memberships and group call processing attributes for off-network operations.
  • FIG. 2 illustrating a method for operation in a group communications system during IOPS mode as performed by the client node 200a according to an embodiment.
  • the radio access network node 110 enters operation in IOPS mode.
  • the client node 200a is configured to perform step S 102:
  • the client node 200a obtains an indication of operation in IOPS mode being entered. Different ways for the client node 200a to obtain the indication will be disclose below.
  • the client node 200a first registers with the local GC server 300. Particularly, the client node 200a is configured to perform step S 104 :
  • S 104 The client node 200a registers, in response to obtaining the indication, with the local GC server 300 located in a radio access network 120 of the group communications system 100. Different ways for the client node 200a to perform the registration will be disclose below.
  • the client node 200a then provides information to the local GC server 300 that enables the local GC server 300 to be informed in terms of off-network group configuration.
  • the client node 200a is configured to perform step S 106 :
  • S 106 The client node 200a provides information to the local GC server 300 regarding off-network group configuration of the client node 200 a. In this respect, the information provided to the local GC server 300 is thus the off- network group configuration itself.
  • Different ways for the client node 200a to provide the information to the local GC server 300 will be disclose below. This enables efficient handling of group configuration data inthe local GC server 300 enabling group communications during IOPS operation.
  • the client node 200a may obtain the indication in step S 102.
  • the indication is obtained in a message from a wireless device 160a.
  • the client node 200a is hosted by a wireless device 160a, and the indication is obtained in a message from the wireless device 160a.
  • the message is indicative of a network node 110 serving the wireless device 160a in the radio access network 120 having entered IOPS mode. That is, the message could inform the client node 200a that the radio access network node 110 has entered IOPS mode.
  • the indication is obtained by means of the client node 200a noticing a loss of connection to the centralized GC server 170.
  • the indication is defined by a loss of connection to the centralized GC server 170.
  • One way for the client node 200a to notice such a loss of connection is the absence of an expected transmission from the centralized GC server 170. Examples of such expected transmissions are acknowledgement (ACK) messages or negative acknowledgement (NACK) messages, or data transmissions in an ongoing communications session with the centralized GC server 170.
  • ACK acknowledgement
  • NACK negative acknowledgement
  • the centralized GC server 170 might be located in the service network 140 of the group communications system 100.
  • the client node 200a may perform the registering with the local GC server 300 in step S 104.
  • the registering requires the client node 200a to provide its identity.
  • the registering comprises providing an identity of the client node 200a to the local GC server 300.
  • the client node 200a performs a conventional user authentication and service authorization procedure towards the local GC server 300. That is, according to an embodiment the registering comprises performing user authentication and service authorization with the local GC server 300.
  • the client node 200a may provide the information to the local GC server 300 in step S 106.
  • the off- network group configuration indicates at least one group 150 of client nodes 200a, 200b to which the client node 200a belongs in the group
  • the information is provided in a group affiliation request message or a group configuration message.
  • the information is provided in an off-network group configuration message sent to the local GC server 300.
  • the off-network group configuration message might comprise group affiliation status information .
  • the off-network group configuration information might be a subset of the complete group
  • the subset comprises at least group identity, group memberships and group call processing attributes for off-network operations.
  • the off-network group configuration message comprises at least group identity, group memberships and group call processing attributes for off-network operations.
  • the client node 200a may act once having provided the information to the local GC server 300 in step S 106.
  • the client node 200a takes part in group communications with another client node 200b with same group affiliation (i.e. showing interest in participating in group communication of the same group 150), where the local GC server 300 relays the traffic.
  • the client node 200a is configured to perform (optional) step S 108 upon having provided the information to the local GC server 300 :
  • the communications system 100 with at least one other client node 200b with which the client node 200a is group affiliated.
  • the group call is served by the local GC server 300 relaying group call media packets between the client node 200a and the at least one other client node 200b.
  • the local GC server 300 will take the role as the floor control arbitrator and thus performs the floor control functionality.
  • the local GC server 300 acts as floor control arbitrator for the group call. This gives a centralized floor control function for the client nodes that are within communication range to the radio access network node 110 and part of the group 150.
  • any client node in the group 150 might act as floor control arbitrator.
  • one of the client node 200a or the at least one other client node 200b acts as floor control arbitrator for the group call.
  • Each client node 200a, 200b in the group 150 might thus take the role as floor control arbitrator, which is the normal scenario in DMO.
  • the client node 200a may be different ways for the client node 200a to know how to act once obtaining the indication in step S 102. That is, that the client node 200a is to perform steps S 104 and S 106.
  • the client node 200a is pre- provisioned with group data.
  • the client node 200a prior to obtaining the indication, is pre-provisioned with group configuration information pertaining to off-network mode operations.
  • the group configuration information might be defined as in 3 GPP TS 23.179 v 13.5.0 or as in 3 GPP TS 23.280 v 15.1.0.
  • the off-network mode operations might follow procedures disclosed in 3 GPP TS 23.179 v 13.5.0 or in 3 GPP TS 23.379 vl5.1.0.
  • the client node 200a may be pre-provisioned. Particularly, according to an embodiment the client node 200a is pre- provisioned in accordance with DMO.
  • the client node 200a may operate before obtaining the indication in step S 102.
  • the client node 200a may operate according to trunked mode operation or on-network operation .
  • the client node 200a prior to obtaining the indication, is engaged in a group call in the group
  • the communications system 100 with at least one other client node 200b with which the client node 200a is group affiliated.
  • the group call is handled according to trunked mode operation or on-network operation .
  • Fig. 3 illustrating a method for operation in a group communications system during IOPS mode as performed by the local GC server 300 according to an embodiment.
  • the local GC server 300 is located in a radio access network 120 of the group communications system 100.
  • the client node 200a in step S 104 registers with the local GC server 300. Therefore, the local GC server 300 is configured to perform step S202: S202: The local GC server 300 registers the client node 200a upon operation in IOPS mode being entered.
  • the client node 200a in step S 106 provides information to the local GC server 300. Therefore, the local GC server 300 is configured to perform step S204:
  • the local GC server 300 obtains information from the client node 200a regarding off-network group configuration of the client node 200a.
  • the registering requires the client node 200a to provide its identity to the local GC server 300.
  • the registering comprises obtaining an identity of the client node 200a from the client node 200a.
  • the client node 200a performs a conventional user authentication and service authorization procedure towards the local GC server 300. That is, according to an embodiment the registering comprises performing user authentication and service
  • the information is provided from the client node 200a to the local GC server 300 in a group affiliation request message or a group configuration message. That is, according to an
  • the local GC server 300 relays the traffic when the client node 200a takes part in group communications with another client node 200b with same group affiliation (i.e. showing interest in participating in group communication of the same group 150).
  • the local GC server 300 is configured to perform step S206 upon having obtained the information from the client node 200a:
  • the local GC server 300 serves, in a group call in the group
  • the local GC server 300 thus relays the group communication traffic.
  • One of the client nodes 200a, 200b transmits data towards the radio access network node 110 , and the local GC server 300 relays this traffic to all other client nodes 200a, 200b that have registered to the local GC server 300 and have notified group configuration and membership for the specific group 150.
  • the local GC server 300 will take the role as the floor control arbitrator and thus performs the floor control
  • the local GC server 300 acts as floor control arbitrator for the group call.
  • any client node in the group 150 might act as floor control arbitrator.
  • one of the client node 200a and the at least one other client node 200b acts as floor control arbitrator for the group call.
  • FIG. 4 One particular embodiment for operation in a group communications system during IOPS mode as performed by the client node 200a and the local GC server 300 based on at least some of the above disclosed embodiments will now be disclosed in detail with reference to the signalling diagram of Fig. 4.
  • a local GC server 300 is provided in the radio access network node 110 together with radio connectivity functionality and local packet core network (PCN) functionality.
  • PCN packet core network
  • the wireless device 160a detects that the radio access network node 110 has entered IOPS mode and that the radio access network node 110 therefore attaches to the local packet core network. This detection is performed as described in 3 GPP TS 23.40 1 vl5.1.0 Annex K.
  • step S30 1 The client node 200a obtains an indication that the radio access network node 110 has entered IOPS mode. This identification can be obtained in a message from the wireless device 160a as part of step S300 or by the client node 200a noticing a loss of connection to the centralized GC server 170.
  • One way to implement step S30 1 is to perform step S 102.
  • the client node 200a sends a registration request to the local GC server 300, which registration request at minimum comprises an identity of the client node 200a.
  • One way to achieve this is for the client node 200a to perform a conventional user authentication and service authorization procedure towards the local GC server 300.
  • One way to implement step S302 is to perform step S 104 and step S202.
  • the client node 200a sends group data, such as group affiliation status information, for all off-network groups that are configured in the client node 200a and in which groups the client node 200a wants to transmit or receive group communication messages.
  • group data such as group affiliation status information
  • One way to achieve this is for the client node 200a to send a Group Affiliation request message or Group
  • step S303 One way to implement step S303 is to perform step S 106 and step S204. With the information that the local GC server 300 has received in step S302 and step S303 , the local GC server 300 can relay any group communication messages for a specific group 150 of client nodes to all client nodes that have performed step S302 and step S303.
  • S304 Group communication is ongoing, and the local GC server 300 is relaying the traffic to the correct client nodes.
  • step S304 One way to implement step S304 is to perform step S 108 and step S206.
  • Fig. 5 schematically illustrates, in terms of a number of functional units, the components of a client node 200a according to an embodiment.
  • Processing circuitry 210 is provided using any combination of one or more of a suitable central processing unit (CPU), multiprocessor, microcontroller, digital signal processor (DSP), etc., capable of executing software instructions stored in a computer program product 910a (as in Fig. 9), e.g. in the form of a storage medium 230.
  • the processing circuitry 210 may further be provided as at least one application specific integrated circuit (ASIC), or field programmable gate array (FPGA).
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • the processing circuitry 210 is configured to cause the client node 200a to perform a set of operations, or steps, S 102-S 108 , S30 1-S304, as disclosed above.
  • the storage medium 230 may store the set of operations
  • the processing circuitry 210 may be configured to retrieve the set of operations from the storage medium 230 to cause the client node 200a to perform the set of operations.
  • the set of operations may be provided as a set of executable instructions.
  • the processing circuitry 210 is thereby arranged to execute methods as herein disclosed.
  • the storage medium 230 may also comprise persistent storage, which, for example, can be any single one or combination of magnetic memory, optical memory, solid state memory or even remotely mounted memory.
  • the client node 200a may further comprise a communications interface 220 for communications with entities, nodes, devices, and functions of the communications system 100, and especially the local GC server 300.
  • the communications interface 220 may comprise one or more transmitters and receivers, comprising analogue and digital components.
  • the processing circuitry 210 controls the general operation of the client node 200a e.g. by sending data and control signals to the communications interface 220 and the storage medium 230, by receiving data and reports from the communications interface 220, and by retrieving data and
  • Fig. 6 schematically illustrates, in terms of a number of functional modules, the components of a client node 200a according to an embodiment.
  • the client node 200a of Fig. 6 comprises a number of functional modules; an obtain module 210a configured to perform step S 102, a register module 210b configured to perform step S 104, and a provide module 210c configured to perform step S 106.
  • the client node 200a of Fig. 6 may further comprise a number of optional functional modules, such as an engage module 210d configured to perform step S 108.
  • each functional module 210a-210d may be implemented in hardware or in software.
  • one or more or all functional modules 210a-210d may be implemented by the processing circuitry 210, possibly in cooperation with the communications interface 220 and/ or the storage medium 230.
  • the processing circuitry 210 may thus be arranged to from the storage medium 230 fetch instructions as provided by a functional module 210a-210d and to execute these instructions, thereby performing any steps of the client node 200a as disclosed herein .
  • the client node 200a may be provided as a standalone device or as a part of at least one further device.
  • the client node 200 may be provided in a wireless device 160a.
  • Fig. 7 schematically illustrates, in terms of a number of functional units, the components of a local GC server 300 according to an embodiment.
  • Processing circuitry 3 10 is provided using any combination of one or more of a suitable central processing unit (CPU), multiprocessor, microcontroller, digital signal processor (DSP), etc., capable of executing software instructions stored in a computer program product 910b (as in Fig. 9), e.g. in the form of a storage medium 330.
  • the processing circuitry 3 10 may further be provided as at least one application specific integrated circuit (ASIC), or field
  • FPGA programmable gate array
  • the processing circuitry 3 10 is configured to cause the local GC server 300 to perform a set of operations, or steps, S202-S206, S302-S304, as disclosed above.
  • the storage medium 330 may store the set of operations
  • the processing circuitry 310 may be configured to retrieve the set of operations from the storage medium 330 to cause the local GC server 300 to perform the set of operations.
  • the set of operations may be provided as a set of executable instructions.
  • the processing circuitry 3 10 is thereby arranged to execute methods as herein disclosed.
  • the storage medium 330 may also comprise persistent storage, which, for example, can be any single one or combination of magnetic memory, optical memory, solid state memory or even remotely mounted memory.
  • the local GC server 300 may further comprise a communications interface 320 for communications with other entities, nodes, devices, and functions of the communications system 100 , and especially the client nodes 200a-200c.
  • the communications interface 320 may comprise one or more transmitters and receivers, comprising analogue and digital components.
  • the processing circuitry 3 10 controls the general operation of the local GC server 300 e.g. by sending data and control signals to the communications interface 320 and the storage medium 330 , by receiving data and reports from the communications interface 320 , and by retrieving data and
  • Fig. 8 schematically illustrates, in terms of a number of functional modules, the components of a local GC server 300 according to an embodiment.
  • the local GC server 300 of Fig. 8 comprises a number of functional modules; a register module 310a configured to perform step S202 and an obtain module 310b configured to perform step S204.
  • the local GC server 300 of Fig. 8 may further comprise a number of optional functional modules, such as a serve module 3 10c configured to perform step S206.
  • each functional module 310a-3 10c may be implemented in hardware or in software.
  • one or more or all functional modules 310a-310c may be implemented by the processing circuitry 3 10 , possibly in cooperation with the communications interface 320 and/ or the storage medium 330.
  • the processing circuitry 310 may thus be arranged to from the storage medium 330 fetch instructions as provided by a functional module 310a-3 10c and to execute these instructions, thereby performing any steps of the local GC server 300 as disclosed herein.
  • the local GC server 300 is located in the radio access network 120 of the group communications system 100.
  • the local GC server 300 may be provided as a standalone device or as a part of at least one further device.
  • the local GC server 300 may be provided in a node of the radio access network 120 , such as in a radio access network node 110.
  • functionality of the local GC server 300 may be distributed between at least two devices, or nodes.
  • One example of where in the communications system 100 the local GC server 300 may be provided is illustrated in Fig. 1. Functionality of the local GC server 300 may be implemented at the service layer of the protocol stack.
  • instructions that are required to be performed in real time may be performed in a device, or node, operatively closer to the radio access network 120 than instructions that are not required to be performed in real time.
  • at least part of the local GC server 300 may reside in the radio access network 120 , such as in the radio access network node 110.
  • a first portion of the instructions performed by the local GC server 300 may be executed in a first device, and a second portion of the of the instructions performed by the local GC server 300 may be executed in a second device; the herein disclosed embodiments are not limited to any particular number of devices on which the instructions performed by the local GC server 300 may be executed.
  • the methods according to the herein disclosed embodiments are suitable to be performed by a local GC server 300 residing in a cloud computational environment. Therefore, although a single processing circuitry 3 10 is illustrated in Fig. 7 the processing circuitry 3 10 may be distributed among a plurality of devices, or nodes. The same applies to the functional modules 3 10a-310c of Fig. 8 and the computer program 920b of Fig. 9.
  • Fig. 9 shows one example of a computer program product 910a, 910b comprising computer readable means 930.
  • a computer program 920a can be stored, which computer program 920a can cause the processing circuitry 210 and thereto operatively coupled entities and devices, such as the communications interface 220 and the storage medium 230, to execute methods according to embodiments described herein .
  • the computer program 920a and/ or computer program product 910a may thus provide means for performing any steps of the client node 200a as herein disclosed.
  • a computer program 920b can be stored, which computer program 920b can cause the processing circuitry 310 and thereto operatively coupled entities and devices, such as the communications interface 320 and the storage medium 330 , to execute methods according to embodiments described herein .
  • the computer program 920b and/ or computer program product 910b may thus provide means for performing any steps of the local GC server 300 as herein disclosed.
  • the computer program product 910a, 910b is illustrated as an optical disc, such as a CD (compact disc) or a DVD (digital versatile disc) or a Blu-Ray disc.
  • the computer program product 910a, 910b could also be embodied as a memory, such as a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), or an electrically erasable programmable read-only memory (EEPROM) and more particularly as a non-volatile storage medium of a device in an external memory such as a USB (Universal Serial Bus) memory or a Flash memory, such as a compact Flash memory.
  • RAM random access memory
  • ROM read-only memory
  • EPROM erasable programmable read-only memory
  • EEPROM electrically erasable programmable read-only memory
  • the computer program 920a, 920b is here schematically shown as a track on the depicted optical disk, the computer program 920a,

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

There is provided mechanisms for operation in a group communications system during Isolated E-UTRAN Operations for Public Safety (IOPS) mode. A method is performed by a client node. The method comprises obtaining an indication of operation in IOPS mode being entered. The method comprises registering, in response to obtaining the indication, with a local GC server located in a radio access network of the group communications system. The method comprises providing information to the local GC server regarding off- network group configuration of the client node.

Description

GROUP COMMUNICATIONS DURING IOPS
TECHNICAL FIELD
Embodiments presented herein relate to methods, a client node, a local group communications server, a computer program, and a computer program product for operation in a group communications system during Isolated E- UTRAN Operations for Public Safety.
BACKGROUND
So-called mission critical (MC) communications services could be used for public safety users, such as the police and the fire brigade. MC
communications services generally require preferential handling compared to traditional telecommunication services, including handling of prioritized MC calls for emergency and imminent threats. Furthermore, MC
communications services might require several resilience features that provide a guaranteed service level, even if part of the network or backhaul infrastructure fails.
So-called group communications (GC) system can be used to facilitate MC communications services. In general terms, group communication means that the same information or media is delivered to multiple client nodes. In group communication systems (e.g., Push-To-Talk (PTT) systems, or Mission Critical Push-To-Talk (MCPTT) systems) the client nodes receiving the same media constitute a group of client nodes.
A GC system might be designed with a centralized architecture approach, in which a centralized GC server provides full control of all the group data, e.g. group identities, group membership, policies, user authorities, group call control attributes, such as affiliation statues and prioritizations. Such approach requires a network infrastructure that provides high network availability. This type of operation is sometimes referred to as Trunked Mode Operation (TMO), or on-network operation. A GC system might, alternatively, be designed with a decentralized
architecture approach where each client node takes part in controlling the group communication . In this case the group data (which is similar to, but normally only a subset of, the group data for the centralized architecture approach) must be pre-provisioned to each client node. This type of operation is sometimes referred to as Direct Mode Operation (DMO), or off- network operation, which means that the group communications can be implemented without any network infrastructure support.
In incumbent GC systems both the aforementioned architecture approaches are supported. Furthermore, incumbent GC systems might provide a resilience feature that allows a local radio access network to provide local connectivity and GC services to the client nodes within the network coverage of the local radio access network even if the radio access network loses its operational connection to other parts of the network, such as to the packet core network of the public land mobile network (PLMN). This type of operation is sometimes referred to as Local Site Trunking.
In further detail, in some networks that provides GC services such as MCPTT the service can be guaranteed even in the case of backhaul failure by using Isolated E-UTRAN Operations for Public Safety (IOPS; where E-UTRAN is short for Evolved Universal Mobile Telecommunications System (UMTS)
Terrestrial Radio Access, also referred to as the 3GPP work item on the Long Term Evolution (LTE) also known as the Evolved Universal Terrestrial Radio Access (E-UTRA)), with reference to the 3 GPP TS 23.40 1 vl5.1.0 and Annex K. The IOPS functionality provides local connectivity to public safety client nodes that are within the communication range of the E-UTRAN radio access network node; the so-called evolved Node B (eNB) that supports IOPS operation. The IOPS functionality can be used in different types of
deployments. One common scenario is for a radio access network node located on a remote location (e.g. an island), where the radio access network node is operatively connected to the packet core network via e.g. a satellite link. If there is a satellite link failure, it is critical for user of MC
communications services to be able to at least have local connectivity for the communication between the users in the coverage of the radio access network node.
One way to provide IOPS operation is to deploy a GC system and a local packet core network in each radio access network node. This also includes deploying a local user database with group data as defined above, together with user identities and authentication keys. The local user database can be provided in a local GC system having a local GC server. The local GC server typically resides in the radio access network node that will provide the IOPS operation. In this respect, in order to provide a GC service with an acceptable service level in IOPS, it is then required that the GC service data is
synchronized between the centralized GC server and the local GC server. Additionally, the group data must be synchronized between the centralized GC server and the local GC server. To perform and manage such
synchronization is challenging, not only because of the amount of group data that needs to be synchronized, but also because of the dynamic aspect of the group data, and the pure number of radio access network nodes (and local GC servers) that are involved in the synchronization.
Hence, there is still a need for improved data synchronization of the local GC server that enables group communications during IOPS operation . SUMMARY
An object of embodiments herein is to provide efficient operation in a group communications system during IOPS.
According to a first aspect there is presented a method for operation in a group communications system during IOPS mode. The method is performed by a client node. The method comprises obtaining an indication of operation in IOPS mode being entered. The method comprises registering, in response to obtaining the indication, with a local GC server located in a radio access network of the group communications system. The method comprises providing information to the local GC server regarding off-network group configuration of the client node. According to a second aspect there is presented a client node for operation in a group communications system during IOPS mode. The client node comprises processing circuitry. The processing circuitry is configured to cause the client node to obtain an indication of operation in IOPS mode being entered. The processing circuitry is configured to cause the client node to register, in response to obtaining the indication, with a local GC server located in a radio access network of the group communications system. The processing circuitry is configured to cause the client node to provide information to the local GC server regarding off-network group configuration of the client node.
According to a third aspect there is presented a client node for operation in a group communications system during IOPS mode. The client node comprises an obtain module configured to obtain an indication of operation in IOPS mode being entered. The client node comprises a register module configured to register, in response to obtaining the indication, with a local GC server located in a radio access network of the group communications system. The client node comprises a provide module configured to provide information to the local GC server regarding off-network group configuration of the client node. According to a fourth aspect there is presented a computer program for operation in a group communications system during IOPS mode. The computer program comprises computer program code which, when run on processing circuitry of a client node, causes the client node to perform a method according to the first aspect. According to a fifth aspect there is presented a method for operation in a group communications system during IOPS mode. The method is performed by a local GC server. The local GC server is located in a radio access network of the group communications system. The method comprises registering the client node upon operation in IOPS mode is entered. The method comprises obtaining information from the client node regarding off-network group configuration of the client node. According to a sixth aspect there is presented a local GC server for operation in a group communications system during IOPS mode. The local GC server is located in a radio access network of the group communications system. The local GC server comprises processing circuitry. The processing circuitry is configured to cause the local GC server to register the client node upon operation in IOPS mode is entered. The processing circuitry is configured to cause the local GC server to obtain information from the client node regarding off-network group configuration of the client node.
According to a seventh aspect there is presented a local GC server for operation in a group communications system during IOPS mode. The local GC server is located in a radio access network of the group communications system. The local GC server comprises a register module configured to register the client node upon operation in IOPS mode is entered. The local GC server comprises an obtain module configured to obtain information from the client node regarding off-network group configuration of the client node.
According to an eight aspect there is presented a computer program for operation in a group communications system during IOPS mode, the computer program comprising computer program code which, when run on processing circuitry of a local GC server, causes the local GC server to perform a method according to the fifth aspect.
According to a ninth aspect there is presented a computer program product comprising a computer program according to at least one of the fourth aspect and the eight aspect and a computer readable storage medium on which the computer program is stored. The computer readable storage medium could be a non-transitory computer readable storage medium.
Advantageously these methods, these client nodes, these local GC servers, and these computer programs provide efficient operation in a group communications system during IOPS.
Advantageously these methods, these client nodes, these local GC servers, and these computer programs enable improved, with respect to traditional IOPS operation, data synchronization of the local GC server that enables group communications during IOPS operation .
Advantageously these methods, these client nodes, these local GC servers, and these computer programs provide a significantly reduction in complexity for synchronizing the group data between a centralized GC server and the local GC server in the case of IOPS.
Advantageously these methods, these client nodes, these local GC servers, and these computer programs enable synchronization only to be performed based on need, and hence not all radio access network nodes in a network are required to be synchronized in terms of group data.
It is to be noted that any feature of the first, second, third, fourth, fifth, sixth seventh, eight, and ninth aspects may be applied to any other aspect, wherever appropriate. Likewise, any advantage of the first aspect may equally apply to the second, third, fourth, fifth, sixth, seventh, eight, and/ or ninth aspect, respectively, and vice versa. Other objectives, features and advantages of the enclosed embodiments will be apparent from the following detailed disclosure, from the attached dependent claims as well as from the drawings.
Generally, all terms used in the claims are to be interpreted according to their ordinary meaning in the technical field, unless explicitly defined otherwise herein . All references to "a/ an/ the element, apparatus, component, means, module, step, etc." are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, module, step, etc., unless explicitly stated otherwise. The steps of any method disclosed herein do not have to be performed in the exact order disclosed, unless explicitly stated.
BRIEF DES CRIPTION OF THE DRAWINGS
The inventive concept is now described, by way of example, with reference to the accompanying drawings, in which: Fig. 1 is a schematic diagram illustrating a communications system according to embodiments;
Figs. 2 and 3 are flowcharts of methods according to embodiments;
Fig. 4 is a signalling diagram according to an embodiment; Fig. 5 is a schematic diagram showing functional units of a client node according to an embodiment;
Fig. 6 is a schematic diagram showing functional modules of a client node according to an embodiment;
Fig. 7 is a schematic diagram showing functional units of a local GC server according to an embodiment;
Fig. 8 is a schematic diagram showing functional modules of a local GC server according to an embodiment; and
Fig. 9 shows one example of a computer program product comprising computer readable means according to an embodiment. DETAILED DES CRIPTION
The inventive concept will now be described more fully hereinafter with reference to the accompanying drawings, in which certain embodiments of the inventive concept are shown . This inventive concept may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided by way of example so that this disclosure will be thorough and complete, and will fully convey the scope of the inventive concept to those skilled in the art. Like numbers refer to like elements throughout the description . Any step or feature illustrated by dashed lines should be regarded as optional. Fig. 1 is a schematic diagram illustrating a communications system 100 where embodiments presented herein can be applied. The communications system 100 may be regarded as a wireless communications system. In some aspects the group communications system 100 is a MC system. In some aspects the group communications system 100 is a MC PTT system.
The wireless communications system provides services to client nodes 200a, 200b, 200c. For illustrative purposes, client nodes 200a and 200b are assumed to be group affiliated, thus belonging to the same group 150 of clients within the group communications system. Each client node 200a, 200b, 200c may be provided in, or installed on, a respective wireless device 160a, 160b, 160c. In other words, a step, action, or similar that is performed by a client node 200a, 200b, 200c is, in some aspects, also performed by the wireless device 160a, 160b, 160c in which the client node 200a, 200b, 200c is provided.
The communications system 100 comprises a radio access network 120, a packet core network (PCN) 130 of a PLMN, and a service network 140. The communications system 100 further comprises centralized GC server 170 as provided in the service network 140 and at least one local GC server 300. The at least one local GC server 300 may be provided in, or installed on, a radio access network node 110 or in another entity or device in the radio access network 120. Each of the centralized GC server 170 and the at least one local GC server 300 might be a MC service server, such as a MC video server, a MC data server, and/ or a MC PTT server.
The radio access network 120 is operatively connected to the packet core network 130 which in turn is operatively connected to the service network 140. The radio access network node 110 thereby enables the wireless devices 160a, 160b, 160c, and hence the client nodes 200a, 200b, 200c in the wireless device 160a, 160b, 160c, respectively, to access services and exchange data as provided by the service network 140. Particularly, the client nodes 200a, 200b, 200c are thereby enabled to communicate with the centralized GC server 170.
Examples of wireless devices 160a, 160b, 160c include, but are not limited to, mobile stations, mobile phones, handsets, wireless local loop phones, user equipment (UE), smartphones, laptop computers, and tablet computers. Examples of radio access network nodes 110 include, but are not limited to, radio base stations, base transceiver stations, node Bs, evolved node Bs, and access points. As the skilled person understands, the communications system 100 may comprise a plurality of radio access network nodes 110 , each providing network access to a plurality of wireless devices 160a, 160b, 160c. The herein disclosed embodiments are not limited to any particular number of radio access network nodes 110, client nodes 200a, 200b, 200c, or wireless devices 160a, 160b, 160c. Any of the nodes indicated herein may be seen as functions, where each function may be implemented in one or more physical entities.
For illustrative purposes it is assumed that there is a link failure between the radio access network nod 110 and the packet core network 130. As disclosed above, the at least one local GC server 300 could in such situations provide a GC service for the client nodes 200a, 200b, 200c. As further disclosed above, traditionally, this requires extensive data synchronization between the at least one local GC server 300 in each radio access network node 110 that enables group communications during IOPS operation and the centralized GC server 170. The embodiments disclosed herein therefore relate to mechanisms for operation in a group communications system during IOPS not suffering from the issues noted above, or at least where these issues are mitigated or reduced. In order to obtain such mechanisms there is provided a client node 200a, a method performed by the client node 200a, a computer program product comprising code, for example in the form of a computer program, that when run on processing circuitry of the client node 200a, causes the client node 200a to perform the method. In order to obtain such mechanisms there is further provided a local GC server 300, a method performed by the local GC server 300, and a computer program product comprising code, for example in the form of a computer program, that when run on processing circuitry of the local GC server 300 , causes the local GC server 300 to perform the method. According to the herein disclosed embodiments there are provided
mechanisms that enable the data synchronization to be simplified as well as simplifying the functionality of the at least one local GC server 300. In more detail, according to the herein disclosed embodiments the at least one local GC server 300 is not required to permanently store user and group
information, such as the above defined group data. In order to achieve this, each client node 200a, 200b, 200c is pre-provisioned with configuration information, such as off-network group configuration information, for opera tion during IOPS mode. The group configuration information is provided to the local GC server 300 when needed, i.e. when the radio access network node 110 needs to provide local connectivity by using IOPS. The off-network group configuration information might be a subset of the complete group configuration information in a traditional GC system. This subset comprises at least group identity, group memberships and group call processing attributes for off-network operations.
Reference is now made to Fig. 2 illustrating a method for operation in a group communications system during IOPS mode as performed by the client node 200a according to an embodiment.
It is assumed that the radio access network node 110 enters operation in IOPS mode. Hence, the client node 200a is configured to perform step S 102:
S 102: The client node 200a obtains an indication of operation in IOPS mode being entered. Different ways for the client node 200a to obtain the indication will be disclose below.
The client node 200a first registers with the local GC server 300. Particularly, the client node 200a is configured to perform step S 104 :
S 104: The client node 200a registers, in response to obtaining the indication, with the local GC server 300 located in a radio access network 120 of the group communications system 100. Different ways for the client node 200a to perform the registration will be disclose below. The client node 200a then provides information to the local GC server 300 that enables the local GC server 300 to be informed in terms of off-network group configuration. Particularly, the client node 200a is configured to perform step S 106 : S 106: The client node 200a provides information to the local GC server 300 regarding off-network group configuration of the client node 200 a. In this respect, the information provided to the local GC server 300 is thus the off- network group configuration itself. Different ways for the client node 200a to provide the information to the local GC server 300 will be disclose below. This enables efficient handling of group configuration data inthe local GC server 300 enabling group communications during IOPS operation.
Embodiments relating to further details of operation in a group
communications system during IOPS mode as performed by the client node 200a will now be disclosed. There may be different ways for the client node 200a to obtain the indication in step S 102. In some aspects the indication is obtained in a message from a wireless device 160a. Particularly, according to an embodiment the client node 200a is hosted by a wireless device 160a, and the indication is obtained in a message from the wireless device 160a. There could be different messages received from the wireless device 160a. Particularly, according to an embodiment the message is indicative of a network node 110 serving the wireless device 160a in the radio access network 120 having entered IOPS mode. That is, the message could inform the client node 200a that the radio access network node 110 has entered IOPS mode.
In other aspects the indication is obtained by means of the client node 200a noticing a loss of connection to the centralized GC server 170. Particularly, according to an embodiment the indication is defined by a loss of connection to the centralized GC server 170. One way for the client node 200a to notice such a loss of connection is the absence of an expected transmission from the centralized GC server 170. Examples of such expected transmissions are acknowledgement (ACK) messages or negative acknowledgement (NACK) messages, or data transmissions in an ongoing communications session with the centralized GC server 170. As in the illustrative example of Fig. 1, the centralized GC server 170 might be located in the service network 140 of the group communications system 100.
There may be different ways for the client node 200a to perform the registering with the local GC server 300 in step S 104. In some aspects the registering requires the client node 200a to provide its identity. Particularly, according to an embodiment the registering comprises providing an identity of the client node 200a to the local GC server 300.
In some aspects the client node 200a performs a conventional user authentication and service authorization procedure towards the local GC server 300. That is, according to an embodiment the registering comprises performing user authentication and service authorization with the local GC server 300.
There may be different ways for the client node 200a to provide the information to the local GC server 300 in step S 106. In some aspects the off- network group configuration indicates at least one group 150 of client nodes 200a, 200b to which the client node 200a belongs in the group
communications system 100. In some aspects the information is provided in a group affiliation request message or a group configuration message.
Particularly, according to an embodiment the information is provided in an off-network group configuration message sent to the local GC server 300. The off-network group configuration message might comprise group affiliation status information . Further, as disclosed above, the off-network group configuration information might be a subset of the complete group
configuration information in a traditional GC system. The subset comprises at least group identity, group memberships and group call processing attributes for off-network operations. Thus in some aspects the off-network group configuration message comprises at least group identity, group memberships and group call processing attributes for off-network operations.
There may be different ways for the client node 200a to act once having provided the information to the local GC server 300 in step S 106. In some aspects the client node 200a takes part in group communications with another client node 200b with same group affiliation (i.e. showing interest in participating in group communication of the same group 150), where the local GC server 300 relays the traffic.
Particularly, according to an embodiment, the client node 200a is configured to perform (optional) step S 108 upon having provided the information to the local GC server 300 :
S 108 : The client node 200a engages in a group call in the group
communications system 100 with at least one other client node 200b with which the client node 200a is group affiliated. The group call is served by the local GC server 300 relaying group call media packets between the client node 200a and the at least one other client node 200b.
There may be different ways to handle control of the group call in the group communications system 100.
In some aspects the local GC server 300 will take the role as the floor control arbitrator and thus performs the floor control functionality. Particularly, according to an embodiment the local GC server 300 acts as floor control arbitrator for the group call. This gives a centralized floor control function for the client nodes that are within communication range to the radio access network node 110 and part of the group 150. In other aspects any client node in the group 150 might act as floor control arbitrator. Particularly, according to an embodiment one of the client node 200a or the at least one other client node 200b acts as floor control arbitrator for the group call. Each client node 200a, 200b in the group 150 might thus take the role as floor control arbitrator, which is the normal scenario in DMO. There may be different ways for the client node 200a to know how to act once obtaining the indication in step S 102. That is, that the client node 200a is to perform steps S 104 and S 106. In some aspects the client node 200a is pre- provisioned with group data. Particularly, according to an embodiment the client node 200a, prior to obtaining the indication, is pre-provisioned with group configuration information pertaining to off-network mode operations. The group configuration information might be defined as in 3 GPP TS 23.179 v 13.5.0 or as in 3 GPP TS 23.280 v 15.1.0. The off-network mode operations might follow procedures disclosed in 3 GPP TS 23.179 v 13.5.0 or in 3 GPP TS 23.379 vl5.1.0.
There may be different ways for the client node 200a to be pre-provisioned. Particularly, according to an embodiment the client node 200a is pre- provisioned in accordance with DMO.
There may be different ways for the client node 200a to operate before obtaining the indication in step S 102. In some aspects the client node 200a to operates according to trunked mode operation or on-network operation . Particularly, according to an embodiment the client node 200a, prior to obtaining the indication, is engaged in a group call in the group
communications system 100 with at least one other client node 200b with which the client node 200a is group affiliated. The group call is handled according to trunked mode operation or on-network operation .
Reference is now made to Fig. 3 illustrating a method for operation in a group communications system during IOPS mode as performed by the local GC server 300 according to an embodiment. The local GC server 300 is located in a radio access network 120 of the group communications system 100.
As disclosed above, the client node 200a in step S 104 registers with the local GC server 300. Therefore, the local GC server 300 is configured to perform step S202: S202: The local GC server 300 registers the client node 200a upon operation in IOPS mode being entered.
As disclosed above, the client node 200a in step S 106 provides information to the local GC server 300. Therefore, the local GC server 300 is configured to perform step S204:
S204: The local GC server 300 obtains information from the client node 200a regarding off-network group configuration of the client node 200a.
Embodiments relating to further details of operation in a group
communications system during IOPS as performed by the local GC server 300 will now be disclosed.
As disclosed above, in some aspects the registering requires the client node 200a to provide its identity to the local GC server 300. Thus, according to an embodiment the registering comprises obtaining an identity of the client node 200a from the client node 200a. As disclosed above, in some aspects the client node 200a performs a conventional user authentication and service authorization procedure towards the local GC server 300. That is, according to an embodiment the registering comprises performing user authentication and service
authorization with the client node 200a. As disclosed above, in some aspects the information is provided from the client node 200a to the local GC server 300 in a group affiliation request message or a group configuration message. That is, according to an
embodiment the information is obtained in an off-network group
configuration message from the client node 200a. As disclosed above, in some aspects the local GC server 300 relays the traffic when the client node 200a takes part in group communications with another client node 200b with same group affiliation (i.e. showing interest in participating in group communication of the same group 150). Particularly, according to an embodiment, the local GC server 300 is configured to perform step S206 upon having obtained the information from the client node 200a:
S206 : The local GC server 300 serves, in a group call in the group
communications system 100, the client node 200a and at least one other client node 200b with which the client node 200a is group affiliated by relaying group call media packets between the client node 200a and the at least one other client node 200b.
The local GC server 300 thus relays the group communication traffic. One of the client nodes 200a, 200b transmits data towards the radio access network node 110 , and the local GC server 300 relays this traffic to all other client nodes 200a, 200b that have registered to the local GC server 300 and have notified group configuration and membership for the specific group 150.
As disclosed above, in some aspects the local GC server 300 will take the role as the floor control arbitrator and thus performs the floor control
functionality. Thus, according to an embodiment the local GC server 300 acts as floor control arbitrator for the group call.
As disclosed above, in other aspects any client node in the group 150 might act as floor control arbitrator. Thus, according to an embodiment one of the client node 200a and the at least one other client node 200b acts as floor control arbitrator for the group call.
One particular embodiment for operation in a group communications system during IOPS mode as performed by the client node 200a and the local GC server 300 based on at least some of the above disclosed embodiments will now be disclosed in detail with reference to the signalling diagram of Fig. 4. In the embodiment of Fig. 4 it is assumed that there is link failure between the radio access network node 110 and the packet core network 130. A local GC server 300 is provided in the radio access network node 110 together with radio connectivity functionality and local packet core network (PCN) functionality. It is further assumed that the client node 200a is pre- provisioned with group information that is used in off-network mode of operations.
S300 : The wireless device 160a detects that the radio access network node 110 has entered IOPS mode and that the radio access network node 110 therefore attaches to the local packet core network. This detection is performed as described in 3 GPP TS 23.40 1 vl5.1.0 Annex K.
S30 1: The client node 200a obtains an indication that the radio access network node 110 has entered IOPS mode. This identification can be obtained in a message from the wireless device 160a as part of step S300 or by the client node 200a noticing a loss of connection to the centralized GC server 170. One way to implement step S30 1 is to perform step S 102.
S302: The client node 200a sends a registration request to the local GC server 300, which registration request at minimum comprises an identity of the client node 200a. One way to achieve this is for the client node 200a to perform a conventional user authentication and service authorization procedure towards the local GC server 300. One way to implement step S302 is to perform step S 104 and step S202.
S303 : The client node 200a sends group data, such as group affiliation status information, for all off-network groups that are configured in the client node 200a and in which groups the client node 200a wants to transmit or receive group communication messages. One way to achieve this is for the client node 200a to send a Group Affiliation request message or Group
configuration message towards the local GC server 300. One way to implement step S303 is to perform step S 106 and step S204. With the information that the local GC server 300 has received in step S302 and step S303 , the local GC server 300 can relay any group communication messages for a specific group 150 of client nodes to all client nodes that have performed step S302 and step S303. S304: Group communication is ongoing, and the local GC server 300 is relaying the traffic to the correct client nodes. One way to implement step S304 is to perform step S 108 and step S206.
Fig. 5 schematically illustrates, in terms of a number of functional units, the components of a client node 200a according to an embodiment. Processing circuitry 210 is provided using any combination of one or more of a suitable central processing unit (CPU), multiprocessor, microcontroller, digital signal processor (DSP), etc., capable of executing software instructions stored in a computer program product 910a (as in Fig. 9), e.g. in the form of a storage medium 230. The processing circuitry 210 may further be provided as at least one application specific integrated circuit (ASIC), or field programmable gate array (FPGA).
Particularly, the processing circuitry 210 is configured to cause the client node 200a to perform a set of operations, or steps, S 102-S 108 , S30 1-S304, as disclosed above. For example, the storage medium 230 may store the set of operations, and the processing circuitry 210 may be configured to retrieve the set of operations from the storage medium 230 to cause the client node 200a to perform the set of operations. The set of operations may be provided as a set of executable instructions. Thus the processing circuitry 210 is thereby arranged to execute methods as herein disclosed.
The storage medium 230 may also comprise persistent storage, which, for example, can be any single one or combination of magnetic memory, optical memory, solid state memory or even remotely mounted memory.
The client node 200a may further comprise a communications interface 220 for communications with entities, nodes, devices, and functions of the communications system 100, and especially the local GC server 300. As such the communications interface 220 may comprise one or more transmitters and receivers, comprising analogue and digital components.
The processing circuitry 210 controls the general operation of the client node 200a e.g. by sending data and control signals to the communications interface 220 and the storage medium 230, by receiving data and reports from the communications interface 220, and by retrieving data and
instructions from the storage medium 230. Other components, as well as the related functionality, of the client node 200a are omitted in order not to obscure the concepts presented herein.
Fig. 6 schematically illustrates, in terms of a number of functional modules, the components of a client node 200a according to an embodiment. The client node 200a of Fig. 6 comprises a number of functional modules; an obtain module 210a configured to perform step S 102, a register module 210b configured to perform step S 104, and a provide module 210c configured to perform step S 106. The client node 200a of Fig. 6 may further comprise a number of optional functional modules, such as an engage module 210d configured to perform step S 108. In general terms, each functional module 210a-210d may be implemented in hardware or in software. Preferably, one or more or all functional modules 210a-210d may be implemented by the processing circuitry 210, possibly in cooperation with the communications interface 220 and/ or the storage medium 230. The processing circuitry 210 may thus be arranged to from the storage medium 230 fetch instructions as provided by a functional module 210a-210d and to execute these instructions, thereby performing any steps of the client node 200a as disclosed herein .
The client node 200a may be provided as a standalone device or as a part of at least one further device. For example, the client node 200 may be provided in a wireless device 160a.
Fig. 7 schematically illustrates, in terms of a number of functional units, the components of a local GC server 300 according to an embodiment.
Processing circuitry 3 10 is provided using any combination of one or more of a suitable central processing unit (CPU), multiprocessor, microcontroller, digital signal processor (DSP), etc., capable of executing software instructions stored in a computer program product 910b (as in Fig. 9), e.g. in the form of a storage medium 330. The processing circuitry 3 10 may further be provided as at least one application specific integrated circuit (ASIC), or field
programmable gate array (FPGA).
Particularly, the processing circuitry 3 10 is configured to cause the local GC server 300 to perform a set of operations, or steps, S202-S206, S302-S304, as disclosed above. For example, the storage medium 330 may store the set of operations, and the processing circuitry 310 may be configured to retrieve the set of operations from the storage medium 330 to cause the local GC server 300 to perform the set of operations. The set of operations may be provided as a set of executable instructions. Thus the processing circuitry 3 10 is thereby arranged to execute methods as herein disclosed.
The storage medium 330 may also comprise persistent storage, which, for example, can be any single one or combination of magnetic memory, optical memory, solid state memory or even remotely mounted memory.
The local GC server 300 may further comprise a communications interface 320 for communications with other entities, nodes, devices, and functions of the communications system 100 , and especially the client nodes 200a-200c. As such the communications interface 320 may comprise one or more transmitters and receivers, comprising analogue and digital components.
The processing circuitry 3 10 controls the general operation of the local GC server 300 e.g. by sending data and control signals to the communications interface 320 and the storage medium 330 , by receiving data and reports from the communications interface 320 , and by retrieving data and
instructions from the storage medium 330. Other components, as well as the related functionality, of the local GC server 300 are omitted in order not to obscure the concepts presented herein.
Fig. 8 schematically illustrates, in terms of a number of functional modules, the components of a local GC server 300 according to an embodiment. The local GC server 300 of Fig. 8 comprises a number of functional modules; a register module 310a configured to perform step S202 and an obtain module 310b configured to perform step S204. The local GC server 300 of Fig. 8 may further comprise a number of optional functional modules, such as a serve module 3 10c configured to perform step S206. In general terms, each functional module 310a-3 10c may be implemented in hardware or in software. Preferably, one or more or all functional modules 310a-310c may be implemented by the processing circuitry 3 10 , possibly in cooperation with the communications interface 320 and/ or the storage medium 330. The processing circuitry 310 may thus be arranged to from the storage medium 330 fetch instructions as provided by a functional module 310a-3 10c and to execute these instructions, thereby performing any steps of the local GC server 300 as disclosed herein.
As disclosed above, the local GC server 300 is located in the radio access network 120 of the group communications system 100. The local GC server 300 may be provided as a standalone device or as a part of at least one further device. For example, the local GC server 300 may be provided in a node of the radio access network 120 , such as in a radio access network node 110. Alternatively, functionality of the local GC server 300 may be distributed between at least two devices, or nodes. One example of where in the communications system 100 the local GC server 300 may be provided is illustrated in Fig. 1. Functionality of the local GC server 300 may be implemented at the service layer of the protocol stack. In general terms, instructions that are required to be performed in real time may be performed in a device, or node, operatively closer to the radio access network 120 than instructions that are not required to be performed in real time. In this respect, at least part of the local GC server 300 may reside in the radio access network 120 , such as in the radio access network node 110.
Thus, a first portion of the instructions performed by the local GC server 300 may be executed in a first device, and a second portion of the of the instructions performed by the local GC server 300 may be executed in a second device; the herein disclosed embodiments are not limited to any particular number of devices on which the instructions performed by the local GC server 300 may be executed. Hence, the methods according to the herein disclosed embodiments are suitable to be performed by a local GC server 300 residing in a cloud computational environment. Therefore, although a single processing circuitry 3 10 is illustrated in Fig. 7 the processing circuitry 3 10 may be distributed among a plurality of devices, or nodes. The same applies to the functional modules 3 10a-310c of Fig. 8 and the computer program 920b of Fig. 9.
Fig. 9 shows one example of a computer program product 910a, 910b comprising computer readable means 930. On this computer readable means 930 , a computer program 920a can be stored, which computer program 920a can cause the processing circuitry 210 and thereto operatively coupled entities and devices, such as the communications interface 220 and the storage medium 230, to execute methods according to embodiments described herein . The computer program 920a and/ or computer program product 910a may thus provide means for performing any steps of the client node 200a as herein disclosed. On this computer readable means 930, a computer program 920b can be stored, which computer program 920b can cause the processing circuitry 310 and thereto operatively coupled entities and devices, such as the communications interface 320 and the storage medium 330 , to execute methods according to embodiments described herein . The computer program 920b and/ or computer program product 910b may thus provide means for performing any steps of the local GC server 300 as herein disclosed.
In the example of Fig. 9, the computer program product 910a, 910b is illustrated as an optical disc, such as a CD (compact disc) or a DVD (digital versatile disc) or a Blu-Ray disc. The computer program product 910a, 910b could also be embodied as a memory, such as a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), or an electrically erasable programmable read-only memory (EEPROM) and more particularly as a non-volatile storage medium of a device in an external memory such as a USB (Universal Serial Bus) memory or a Flash memory, such as a compact Flash memory. Thus, while the computer program 920a, 920b is here schematically shown as a track on the depicted optical disk, the computer program 920a, 920b can be stored in any way which is suitable for the computer program product 910a, 910b.
The inventive concept has mainly been described above with reference to a few embodiments. However, as is readily appreciated by a person skilled in the art, other embodiments than the ones disclosed above are equally possible within the scope of the inventive concept, as defined by the appended patent claims.

Claims

1. A method for operation in a group communications system ( 100) during Isolated E-UTRAN Operations for Public Safety, IOPS, mode, the method being performed by a client node (200a), the method comprising:
obtaining (S 102, S30 1) an indication of operation in IOPS mode being entered;
registering (S 104, S302), in response to obtaining the indication, with a local GC server (300) located in a radio access network ( 120) of the group communications system ( 100); and
providing (S 106, S303) information to the local GC server (300) regarding off-network group configuration of the client node (200a).
2. The method according to claim 1, wherein the client node (200a) is hosted by a wireless device ( 160a), and wherein the indication is obtained in a message from the wireless device ( 160a).
3. The method according to claim 2, wherein the message is indicative of a network node ( 110) serving the wireless device ( 160a) in the radio access network (120) having entered IOPS mode.
4. The method according to any of the preceding claims, wherein the indication is defined by a loss of connection to a centralized GC server (170), the centralized GC server (170) being located in a service network ( 140) of the group communications system ( 100).
5. The method according to any of the preceding claims, wherein the registering comprises providing an identity of the client node (200a) to the local GC server (300).
6. The method according to any of the preceding claims, wherein the registering comprises performing user authentication and service
authorization with the local GC server (300).
7. The method according to any of the preceding claims, wherein the information is provided in an off-network group configuration message sent to the local GC server (300).
8. The method according to claim 7, wherein the off-network group configuration message comprises group affiliation status information.
9. The method according to any of the preceding claims, further
comprising, upon having provided the information to the local GC server (300):
engaging (S 108 , S304) in a group call in the group communications system (100) with at least one other client node (200b) with which the client node (200a) is group affiliated, wherein the group call is served by the local GC server (300) relaying group call media packets between the client node (200a) and the at least one other client node (200b).
10. The method according to claim 9, wherein the local GC server (300) acts as floor control arbitrator for the group call.
11. The method according to claim 9, wherein one of the client node (200a) or the at least one other client node (200b) acts as floor control arbitrator for the group call.
12. The method according to any of the preceding claims, wherein the client node (200a), prior to obtaining the indication, is pre-provisioned with group configuration information pertaining to off-network mode operations.
13. The method according to claim 12, wherein the client node (200a) is pre-provisioned in accordance with Direct Mode Operation, DMO.
14. The method according to any of the preceding claims, wherein the client node (200a), prior to obtaining the indication, is engaged in a group call in the group communications system ( 100) with at least one other client node (200b) with which the client node (200a) is group affiliated, the group call being handled according to trunked mode operation or on-network
operation.
15. A method for operation in a group communications system ( 100) during Isolated E-UTRAN Operations for Public Safety, IOPS, mode, the method being performed by a local GC server (300), the local GC server (300) being located in a radio access network ( 120) of the group communications system (100), the method comprising:
registering (S202, S302) the client node (200a) upon operation in IOPS mode being entered; and
obtaining (S204, S303) information from the client node (200a) regarding off-network group configuration of the client node (200a).
16. The method according to claim 15, wherein the registering comprises obtaining an identity of the client node (200a) from the client node (200a).
17. The method according to any of claims 15 to 16, wherein the registering comprises performing user authentication and service authorization with the client node (200a).
18. The method according to any of claims 15 to 17, wherein the information is obtained in an off-network group configuration message from the client node (200a).
19. The method according to any of claims 15 to 18 , further comprising, upon having obtained the information from the client node (200a):
serving (S206, S304), in a group call in the group communications system ( 100), the client node (200a) and at least one other client node (200b) with which the client node (200a) is group affiliated by relaying group call media packets between the client node (200a) and the at least one other client node (200b).
20. The method according to claim 19, wherein the local GC server (300) acts as floor control arbitrator for the group call.
21. The method according to claim 19, wherein one of the client node (200a) and the at least one other client node (200b) acts as floor control arbitrator for the group call.
22. The method according to any of the preceding items, wherein the local GC server (300) is a mission critical, MC, service server.
23. The method according to any of the preceding items, wherein the group communications system ( 100) is a mission critical, MC, push to talk, PTT, system.
24. The method according to any of the preceding items, wherein the group communications system (100) is a mission critical, MC, system.
25. A client node (200a) for operation in a group communications system (100) during Isolated E-UTRAN Operations for Public Safety, IOPS, mode, the client node (200a) comprising processing circuitry (210), the processing circuitry being configured to cause the client node (200a) to:
obtain an indication of operation in IOPS mode being entered;
register, in response to obtaining the indication, with a local GC server (300) located in a radio access network ( 120) of the group communications system ( 100); and
provide information to the local GC server (300) regarding off-network group configuration of the client node (200a).
26. A client node (200a) for operation in a group communications system (100) during Isolated E-UTRAN Operations for Public Safety, IOPS, mode, the client node (200a) comprising:
an obtain module (210 a) configured to obtain an indication of operation in IOPS mode being entered;
a register module (210b) configured to register, in response to obtaining the indication, with a local GC server (300) located in a radio access network (120) of the group communications system ( 100); and
a provide module (210c) configured to provide information to the local GC server (300) regarding off-network group configuration of the client node (200a).
27. A local GC server (300) for operation in a group communications system (100) during Isolated E-UTRAN Operations for Public Safety, IOPS, mode, the local GC server (300) being located in a radio access network ( 120) of the group communications system ( 100), the local GC server (300) comprising processing circuitry (310), the processing circuitry being configured to cause the local GC server (300) to:
register the client node (200a) upon operation in IOPS mode being entered; and
obtain information from the client node (200a) regarding off-network group configuration of the client node (200a).
28. A local GC server (300) for operation in a group communications system (100) during Isolated E-UTRAN Operations for Public Safety, IOPS, mode, the local GC server (300) being located in a radio access network ( 120) of the group communications system ( 100), the local GC server (300) comprising:
a register module (3 10a) configured to register the client node (200a) upon operation in IOPS mode being entered; and
an obtain module (310b) configured to obtain information from the client node (200a) regarding off-network group configuration of the client node (200a).
29. A computer program (920a) for operation in a group communications system (100) during Isolated E-UTRAN Operations for Public Safety, IOPS, mode, the computer program comprising computer code which, when run on processing circuitry (210) of a client node (200a), causes the client node (200a) to:
obtain (S 102, S301) an indication of operation in IOPS mode being entered;
register (S 104, S302), in response to obtaining the indication, with a local GC server (300) located in a radio access network ( 120) of the group communications system ( 100); and
provide (S 106, S303) information to the local GC server (300) regarding off-network group configuration of the client node (200a).
30. A computer program (920b) for operation in a group communications system (100) during Isolated E-UTRAN Operations for Public Safety, IOPS, mode, the computer program comprising computer code which, when run on processing circuitry (3 10) of a local GC server (300) located in a radio access network (120) of the group communications system (100), causes the local GC server (300) to:
register (S202, S302) the client node (200a) upon operation in IOPS mode being entered; and
obtain (S204, S303) information from the client node (200a) regarding off-network group configuration of the client node (200 a).
31. A computer program product (910a, 910b) comprising a computer program (920a, 920b) according to at least one of claims 29 and 30 , and a computer readable storage medium (930 ) on which the computer program is stored.
PCT/SE2017/051077 2017-11-01 2017-11-01 Group communications during iops WO2019088886A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/SE2017/051077 WO2019088886A1 (en) 2017-11-01 2017-11-01 Group communications during iops

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/SE2017/051077 WO2019088886A1 (en) 2017-11-01 2017-11-01 Group communications during iops

Publications (1)

Publication Number Publication Date
WO2019088886A1 true WO2019088886A1 (en) 2019-05-09

Family

ID=66332282

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2017/051077 WO2019088886A1 (en) 2017-11-01 2017-11-01 Group communications during iops

Country Status (1)

Country Link
WO (1) WO2019088886A1 (en)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016114762A1 (en) * 2015-01-13 2016-07-21 Nokia Solutions And Networks Oy Isolated e-utran operation
WO2016119488A1 (en) * 2015-01-28 2016-08-04 中兴通讯股份有限公司 Public safety communication implementation method and apparatus, and storage medium
WO2017001452A1 (en) * 2015-07-02 2017-01-05 Nokia Solutions And Networks Oy Apparatus and method for requesting/providing capability information for specific networks
KR101779477B1 (en) * 2017-01-23 2017-09-18 임혜영 The apparatus of digital signage

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016114762A1 (en) * 2015-01-13 2016-07-21 Nokia Solutions And Networks Oy Isolated e-utran operation
WO2016119488A1 (en) * 2015-01-28 2016-08-04 中兴通讯股份有限公司 Public safety communication implementation method and apparatus, and storage medium
WO2017001452A1 (en) * 2015-07-02 2017-01-05 Nokia Solutions And Networks Oy Apparatus and method for requesting/providing capability information for specific networks
KR101779477B1 (en) * 2017-01-23 2017-09-18 임혜영 The apparatus of digital signage

Similar Documents

Publication Publication Date Title
AU2012301417B2 (en) Method and apparatus for providing a group communications follow mode
EP3058693B1 (en) Selection and use of a security agent for device-to-device (d2d) wireless communications
CN112753234A (en) 3GPP private LAN
US10951670B2 (en) System, method, and apparatus for floor control during push to talk
JP2013537757A (en) Processing method and base station for fail soft processing based on digital trunking system
KR20160010520A (en) Network nodes and methods
US9781582B2 (en) Method, device, and system for transmitting short data during a call hang time hold off period
US11516645B2 (en) Cross-agency communication through an ad-hoc network slice
EP3310108B1 (en) Method and apparatus for changing association relationship between mcptt user and mcptt group
US9420425B1 (en) Methods and systems for determining a change in location of a portable wireless access point
US20220240108A1 (en) Mixed mode wireless communication system operational environment
WO2019088886A1 (en) Group communications during iops
JP7399263B2 (en) MBMS support in IOPS
US20200128364A1 (en) Improved Isolated Group Communications
US20200120621A1 (en) Pre-Provisioned Group Communications
WO2016162047A1 (en) Facilitating effective isolated wireless network operation
JP2017523715A (en) Method of providing communication service of mobile communication network to a plurality of communication devices, mobile communication network, communication device, system, program and computer program product
CN112889300B (en) Isolated E-UTRAN public safety operation IOPS awareness with MBMS
US9930702B2 (en) Method, device, and system for transmitting short data during an active TDMA call
US20190141548A1 (en) Mechanism for determining if a server pod malfunctions and electing a new server pod
KR101920488B1 (en) Method for relaying of base station and method for communication of terminal
US20240137907A1 (en) Determining random-access resources for group paging
US20240236937A9 (en) Determining random-access resources for group paging
WO2020164859A1 (en) Discovery procedure for mission critical services over isolated ran operations for public safety (iops)
KR20190056586A (en) Apparatus and method for packet processing

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: 17930962

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: 17930962

Country of ref document: EP

Kind code of ref document: A1