EP3354089B1 - Radiorecherche dans un système de communications de groupe - Google Patents

Radiorecherche dans un système de communications de groupe Download PDF

Info

Publication number
EP3354089B1
EP3354089B1 EP16766921.7A EP16766921A EP3354089B1 EP 3354089 B1 EP3354089 B1 EP 3354089B1 EP 16766921 A EP16766921 A EP 16766921A EP 3354089 B1 EP3354089 B1 EP 3354089B1
Authority
EP
European Patent Office
Prior art keywords
client node
communications system
node
paging message
paging
Prior art date
Legal status (The legal status 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 status listed.)
Active
Application number
EP16766921.7A
Other languages
German (de)
English (en)
Other versions
EP3354089A1 (fr
Inventor
Joakim ÅKESSON
Magnus TRÄNK
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Telefonaktiebolaget LM Ericsson AB
Original Assignee
Telefonaktiebolaget LM Ericsson AB
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 AB filed Critical Telefonaktiebolaget LM Ericsson AB
Priority to EP20159583.2A priority Critical patent/EP3681219B1/fr
Priority to DK20159583.2T priority patent/DK3681219T3/da
Publication of EP3354089A1 publication Critical patent/EP3354089A1/fr
Application granted granted Critical
Publication of EP3354089B1 publication Critical patent/EP3354089B1/fr
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • H04W68/02—Arrangements for increasing efficiency of notification or paging channel
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment
    • 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
    • H04W76/00—Connection management
    • H04W76/40—Connection management for selective distribution or broadcast

Definitions

  • Embodiments presented herein relate to a method, a control node, a computer program, and a computer program product for paging at least one client node in a group communications system. Embodiments presented herein further relate to a method, a client node, a computer program, and a computer program product for receiving paging in a group communications system.
  • communications networks there may be a challenge to obtain good performance and capacity for a given communications protocol, its parameters and the physical environment in which the communications network is deployed.
  • 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
  • the client nodes receiving the same media constitute a group of client nodes.
  • These client nodes may be located at different locations. If many client nodes are located within the same area, multicast or broadcast based transmission using e.g., Multicast-Broadcast Multimedia Services (MBMS) is efficient for communications to the group of client nodes, because communications resources such as time and frequency resources are shared among client nodes. If client nodes are spread out over a large geographical area it can be more efficient to use unicast transmission for communications to the group of client nodes. However, even if MBMS-based transmission is preferred, there may not be sufficient MBMS resources available to serve all groups of client nodes. Some client nodes and groups thereof may then be served using unicast transmission.
  • MBMS Multicast-Broadcast Multimedia Services
  • the transmitting client node uses unicast transmission to transmit the media to the group communications system, and a control node in the group communications system uses broadcast-based transmission to send the media to client nodes participating in the group communication.
  • MT Mobile Terminated
  • MT Mobile Terminated
  • RRC radio resource control
  • LTE Long Term Evolution
  • the client node is normally asleep and only listens periodically for paging information (e.g. to the Physical Downlink Control Channel (PDCCH) in LTE). If there is a paging message the client node would demodulate the paging channel (denoted PCH in LTE).
  • the paging cycle can be set to between 320 to 2560 ms.
  • the average wake up time for the client node is 160 ms depending on when the traffic arrives in relation to the paging cycle. On top of this it takes approximately 100 ms to change state on the client node from idle mode to connected mode.
  • Such delay is an issue in some communication scenarios, for instance when broadcast-based transmission is used in delay-critical applications.
  • WO2012/166893 A1 discloses a scheme for efficient paging of a wireless terminal (UE) in a high-performance radio group communications service such as Push-to-Talk (PTT), allowing to reduce latency in establishing the PTT connection.
  • a control node in the system transmits a paging message for the intended recipient terminal on an MBMS (Multimedia Broadcast Multicast Service) bearer.
  • MBMS Multimedia Broadcast Multicast Service
  • An object of embodiments herein is to provide efficient handling of real time critical services, such as PTT, in a group communications system.
  • a method for paging at least one client node in a group communications system is performed by a control node of the group communications system.
  • the method comprises obtaining a need for paging the at least one client node in the group communications system.
  • the method comprises transmitting a paging message for the at least one client node on a multimedia broadcast multicast service (MBMS) bearer to the at least one client node.
  • MBMS multimedia broadcast multicast service
  • this method provides efficient paging of client nodes in a group communications system, which enables efficient handling of real time critical services, such as PTT, in a group communications system.
  • a control node for paging at least one client node in a group communications system.
  • the control node comprises processing circuitry.
  • the processing circuitry is configured to cause the control node to obtain a need for paging the at least one client node in the group communications system.
  • the processing circuitry is configured to cause the control node to transmit a paging message for the at least one client node on an MBMS bearer to the at least one client node.
  • this control node provides efficient paging of client nodes in a group communications system, which enables efficient handling of real time critical services, such as PTT, in a group communications system.
  • a control node for paging at least one client node in a group communications system.
  • the control node comprises processing circuitry.
  • the control node comprises a computer program product storing instructions that, when executed by the processing circuitry, causes the control node to perform a set of operations, or steps.
  • the set of operations, or steps involves the control node to obtain a need for paging the at least one client node in the group communications system.
  • the set of operations, or steps involves the control node to transmit a paging message for the at least one client node on an MBMS bearer to the at least one client node.
  • this control node provides efficient paging of client nodes in a group communications system, which enables efficient handling of real time critical services, such as PTT, in a group communications system.
  • a control node for paging at least one client node in a group communications system.
  • the control node comprises an obtain module configured to obtain a need for paging the at least one client node in the group communications system.
  • the control node comprises a transmit module configured to transmit a paging message for the at least one client node on an MBMS bearer to the at least one client node.
  • this control node provides efficient paging of client nodes in a group communications system, which enables efficient handling of real time critical services, such as PTT, in a group communications system.
  • a computer program for paging at least one client node in a group communications system comprising computer program code which, when run on processing circuitry of a control node, causes the control node to perform a method according to the first aspect.
  • this computer program provides efficient paging of client nodes in a group communications system, which enables efficient handling of real time critical services, such as PTT, in a group communications system.
  • a method for receiving paging in a group communications system is performed by a client node.
  • the method comprises receiving a paging message for the client node on an MBMS bearer from a control node of the group communications system.
  • this method enables efficient paging of the client node in a group communications system, which enables efficient handling of real time critical services, such as PTT, in a group communications system.
  • a client node for receiving paging in a group communications system.
  • the client node comprises processing circuitry.
  • the processing circuitry is configured to cause the client node to receive a paging message for the client node on an MBMS bearer from a control node of the group communications system.
  • this client node enables efficient paging of the client node in a group communications system, which enables efficient handling of real time critical services, such as PTT, in a group communications system.
  • a client node for receiving paging in a group communications system.
  • the client node comprises processing circuitry.
  • the client node comprises a computer program product storing instructions that, when executed by the processing circuitry, causes the client node to perform a set of operations, or steps.
  • the set of operations, or steps involves the client node to receive a paging message for the client node on an MBMS bearer from a control node of the group communications system.
  • this client node enables efficient paging of the client node in a group communications system, which enables efficient handling of real time critical services, such as PTT, in a group communications system.
  • a client node for receiving paging in a group communications system.
  • the client node comprises a receive module configured to receive a paging message for the client node on an MBMS bearer from a control node of the group communications system.
  • this client node enables efficient paging of the client node in a group communications system, which enables efficient handling of real time critical services, such as PTT, in a group communications system.
  • a computer program for receiving paging in a group communications system comprising computer program code which, when run on processing circuitry of a client node, causes the client node to perform a method according to the sixth aspect.
  • this computer program provides efficient paging of the client node in a group communications system, which enables efficient handling of real time critical services, such as PTT, in a group communications system.
  • a computer program product comprising a computer program according to at least one of the fifth aspect and the tenth aspect and a computer readable storage medium on which the computer program is stored.
  • the computer readable storage medium can be a non-transitory computer readable storage medium.
  • this computer program product provides efficient paging of client nodes in a group communications system, which enables efficient handling of real time critical services, such as PTT, in a group communications system.
  • this control node, this client node, and these computer programs enable real time critical services to be set up in a manner that minimizes the latency to set up a radio bearer to enable downlink delivery of packets to a client node.
  • any feature of the first, second, third, fourth, fifth, sixth seventh, eight, ninth, tenth and eleventh 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, ninth, tenth, and/or eleventh aspect, respectively, and vice versa.
  • Fig. 1 is a schematic diagram illustrating a communications system 100 where embodiments presented herein can be applied.
  • the communications system 100 is assumed to provide services for group communication and may hence be regarded as a group communications system.
  • the group communications system 100 is, according to some aspects, a push to talk (PTT) system.
  • PTT push to talk
  • the communications system 100 comprises a radio access network 120, a core network 130, and a service network 140.
  • the communications system 100 comprises at least one control node 200 and at least one client node 300a, 300b.
  • the at least one control node 200 may be provided in, or installed on, a radio access network node 110 or in another entity or device in a radio access network 120, in an entity or device of a core network 130, or in an entity or device of a service network 140.
  • Each client node 300a, 300b may be provided in, or installed on, a respective wireless device 150a, 150b.
  • the radio access network 120 is operatively connected to the 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 150a, 150b, and hence the client nodes 300a, 300b, to access services and exchange data as provided by the service network 140.
  • wireless devices 150a, 150b 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 150a, 150b.
  • radio access network nodes 110 client nodes 300a, 300b, or wireless devices 150a, 150b.
  • a client node 300a denoted a first client node
  • the group communications system 100 One example of paging a client node 300a, denoted a first client node, in the group communications system 100 will now be disclosed in detail with reference to the signalling diagram of Fig. 9 .
  • a client node 300b denoted a second client node, transmits data intended to be received by the first client node 300a.
  • the control node 200 obtains an indication that the second client node 300b transmits data intended to be received by the first client node 300a. In response thereto the control node 200 transmits the data to the core network 130.
  • S303 The core network 130 pages the first client node 300a over the radio access network 120.
  • S304 The first client node 300a, in response to having received the paging, makes a service request to the core network 130 over the radio access network 120.
  • S305 A unicast radio access bearer is established for the first client node 300a in response to the service request. This causes the first client node 300a to enter connected mode.
  • the core network 130 delivers the data to the first client node 300a using unicast transmission over the established radio access bearer.
  • the currently used procedure of paging the client nodes 300a, 300b can impact the call setup and mouth-to-ear delay if the PTT system is using unicast transmission and some of the receiving client nodes are in idle mode. Potentially packets may also be dropped until the client nodes 300a, 300b reach connected mode and re-establishes a radio bearer (RAB).
  • RAB radio bearer
  • the core network 130 comprises a packet data network gateway (PGW) 131, a serving gateway (SGW) 132, a mobility management entity (MME) 133, a multicell coordination entity (MCE) 134, a broadcast multicast service centre (BM-SC) 135, and an MBMS gateway (MBMS GW) 136.
  • PGW packet data network gateway
  • SGW serving gateway
  • MME mobility management entity
  • MCE multicell coordination entity
  • BM-SC broadcast multicast service centre
  • MBMS GW MBMS gateway
  • paging of client node 300a is according to state of the art performed along a signalling flow defined by arrow 160 (from MME 133) whereas paging of client node 300a according to embodiments as will been disclosed below is performed along a signalling flow defined by arrow 170 (from control node 200 via BM-SC 135, and MBMS GW136).
  • the embodiments disclosed herein therefore relate to mechanisms for paging at least one client node 300a, 300b, 300c, 300d, 300e in a group communications system 100, 1100a, 1100b, 1100c.
  • a control node 200 a method performed by the control node 200, a computer program product comprising code, for example in the form of a computer program, that when run on processing circuitry of the control node 200, causes the control node 200 to perform the method.
  • the embodiments disclosed herein further relate to mechanisms for receiving paging in a group communications system 100, 1100a, 1100b, 1100c.
  • a client node 300a In order to obtain such mechanisms there is further provided a client node 300a, a method performed by the client node 300a, and 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 300a, causes the client node 300a to perform the method.
  • Fig. 2a schematically illustrates, in terms of a number of functional units, the components of a control node 200 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 410a (as in Fig. 4 ), 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 control node 200 to perform a set of operations, or steps, S102-S106, S402, S403. These operations, or steps, S102-S106, S402, S403 will be disclosed below.
  • 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 control node 200 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 control node 200 may further comprise a communications interface 220 for communications at least with a client node 300a.
  • the communications interface 220 may comprise one or more transmitters and receivers, comprising analogue and digital components and a suitable number of antennas for wireless communications and ports for wireline communications.
  • the processing circuitry 210 controls the general operation of the control node 200 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 control node 200 are omitted in order not to obscure the concepts presented herein.
  • Fig. 2b schematically illustrates, in terms of a number of functional modules, the components of a control node 200 according to an embodiment.
  • the control node 200 of Fig. 2b comprises a number of functional modules; a first obtain module 210a configured to perform below step S102, and a transmit module 210b configured to perform below steps S106, S403.
  • the control node 200 of Fig. 2b may further comprise a number of optional functional modules, such as any of a second obtain module 210c configured to perform below steps S102a, S402, a third obtain module 210d configured to perform below step S102b, and a fourth obtain module 210e configured to perform below step S104.
  • each functional module 210a-210e may be implemented in hardware or in software.
  • one or more or all functional modules 210a-210e may be implemented by the processing circuitry 210, possibly in cooperation with functional units 220 and/or 230.
  • the processing circuitry 210 may thus be arranged to from the storage medium 230 fetch instructions as provided by a functional module 210a-210e and to execute these instructions, thereby performing any steps as will be disclosed hereinafter.
  • the control node 200 may be provided as a standalone device or as a part of at least one further device.
  • the control node 200 may be provided in a node of the radio access network or in a node of the core network.
  • functionality of the control node 200 may be distributed between at least two devices, or nodes. These at least two nodes, or devices, may either be part of the same network part (such as the radio access network or the core network) or may be spread between at least two such network parts.
  • Some examples of where in the communications system 100 the control node 200 may be provided are illustrated in Fig. 1 . Functionality of the control node 200 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 than instructions that are not required to be performed in real time.
  • at least part of the control node 200 may reside in the radio access network, such as in the radio access network node, for cases when embodiments as disclosed herein are performed in real time.
  • a first portion of the instructions performed by the control node 200 may be executed in a first device, and a second portion of the of the instructions performed by the control node 200 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 control node 200 may be executed.
  • the methods according to the herein disclosed embodiments are suitable to be performed by a control node 200 residing in a cloud computational environment. Therefore, although a single processing circuitry 210 is illustrated in Fig. 2a the processing circuitry 210 may be distributed among a plurality of devices, or nodes. The same applies to the functional modules 210a-210e of Fig. 2b and the computer program 420a of Fig. 4 (see below).
  • Fig. 3a schematically illustrates, in terms of a number of functional units, the components of a client node 300a according to an embodiment.
  • Processing circuitry 310 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 410b (as in Fig. 4 ), e.g. in the form of a storage medium 330.
  • the processing circuitry 310 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 310 is configured to cause the client node 300a to perform a set of operations, or steps, S202-S208, S404, S405, S406. These operations, or steps, S202-S208, S404, S405, S406 will be disclosed below.
  • 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 client node 300a to perform the set of operations.
  • the set of operations may be provided as a set of executable instructions.
  • the processing circuitry 310 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 client node 300a may further comprise a communications interface 320 for communications at least with a control node 200.
  • the communications interface 320 may comprise one or more transmitters and receivers, comprising analogue and digital components and a suitable number of antennas for wireless communications and ports for wireline communications.
  • the processing circuitry 310 controls the general operation of the client node 300a 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 client node 300a are omitted in order not to obscure the concepts presented herein.
  • Fig. 3b schematically illustrates, in terms of a number of functional modules, the components of a client node 300a according to an embodiment.
  • the client node 300a of Fig. 3b comprises a receive module 310a configured to perform below steps S204, S404.
  • the client node 300a of Fig. 3b may further comprises a number of optional functional modules, such as any of a monitor module 310b configured to perform below step S202, an initiate module 310c configured to perform below steps S206, S405, and an enter module 310d configured to perform below step S208, S406.
  • the functionality of each functional module 310a-310d will be further disclosed below in the context of which the functional modules 310a-310d may be used.
  • each functional module 310a-310d may be implemented in hardware or in software.
  • one or more or all functional modules 310a-310d may be implemented by the processing circuitry 310, possibly in cooperation with functional units 320 and/or 330.
  • the processing circuitry 310 may thus be arranged to from the storage medium 330 fetch instructions as provided by a functional module 310a-310d and to execute these instructions, thereby performing any steps as will be disclosed hereinafter.
  • the client node 300a may be provided as a standalone device or as a part of at least one further device.
  • the client node 300a may be provided in a wireless device 150a.
  • any processing circuitry, communications interface and storage medium of the wireless device 150a may be shared with the processing circuitry 310, communications interface 320 and storage medium 330 of the client node 300a. It is thus not necessary for the client node 300a to have its own processing circuitry 310, communications interface 320 and storage medium 330 as long as the processing circuitry, communications interface and storage medium of the wireless device 150a is configured to implement the functionality of the herein disclosed client node 300a.
  • Fig. 4 shows one example of a computer program product 410a, 410b comprising computer readable means 430.
  • a computer program 420a can be stored, which computer program 420a 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 420a and/or computer program product 410a may thus provide means for performing any steps of the control node 200 as herein disclosed.
  • a computer program 420b can be stored, which computer program 420b 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 420b and/or computer program product 410b may thus provide means for performing any steps of the client node 300a as herein disclosed.
  • the computer program product 410a, 410b 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 410a, 410b 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
  • EEPROM electrically erasable programmable read-only memory
  • the computer program 420a, 420b is here schematically shown as
  • Figs. 5 and 6 are flow charts illustrating embodiments of methods for paging at least one client node 300a, 300b, 300c, 300d, 300e in a group communications system 100, 1100a, 1100b, 1100c as performed by the control node 200.
  • Figs. 7 and 8 are flow charts illustrating embodiments of methods for receiving paging in a group communications system 100, 1100a, 1100b, 1100c as performed by the client node 300a.
  • the methods are advantageously provided as computer programs 420a, 420b.
  • FIG. 5 illustrating a method for paging at least one client node 300a, 300b, 300c, 300d, 300e in a group communications system 100, 1100a, 1100b, 1100c as performed by the control node 200 according to an embodiment.
  • control node 200 It is assumed that there is a need for paging the at least one client node 300a, 300b, 300c, 300d, 300e in the group communications system 100, 1100a, 1100b, 1100c.
  • the control node 200 is therefore configured to obtain such a need by performing step S102: S102: The control node 200 obtains a need for paging the at least one client node 300a, 300b, 300c, 300d, 300e in the group communications system 100, 1100a, 1100b, 1100c. Different ways for how the control node 200 can obtain this need for paging will be disclosed below.
  • the first obtain module 210a comprises instructions that when executed by the control node 200 causes the processing circuitry 210, possibly in conjunction with the communications interface 220 and the storage medium 230, to obtain the need for paging in order for the control node 200 to perform step S102.
  • Transmission of the paging is combined with application level paging over MBMS, thereby enabling the at least one client node 300a, 300b, 300c, 300d, 300e being paged to speed up its switch to connected mode, and thereby allowing the at least one client node 300a, 300b, 300c, 300d, 300e being paged to receive packets in a fast and efficient manner.
  • the control node 200 is configured to transmit a paging message 1120 as in step S106: S106: The control node 200 transmits a paging message 1120 for the at least one client node 300a, 300b, 300c, 300d, 300e.
  • the paging message 1120 is transmitted on an MBMS bearer to the at least one client node 300a, 300b, 300c, 300d, 300e.
  • the transmit module 210b comprises instructions that when executed by the control node 200 causes the processing circuitry 210, possibly in conjunction with the communications interface 220 and the storage medium 230, to transmit the paging message 1120 in order for the control node 200 to perform step S106.
  • Embodiments relating to further details of paging the at least one client node 300a, 300b, 300c, 300d, 300e in the group communications system 100, 1100a, 1100b, 1100c will now be disclosed.
  • the at least one client node 300a, 300b, 300c, 300d, 300e can be in idle mode when the paging message 1120 is broadcasted. Hence, according to an embodiment the paging message 1120 is intended to be received by client node 300a, 300b, 300c, 300d, 300e in idle mode.
  • paging messages 1120 There may be different kinds of paging messages 1120 that can be transmitted in step S106. Different embodiments relating thereto will now be disclosed in turn.
  • the paging message 1120 is an individual paging message 1120.
  • the paging message 1120 can represent an individual paging message 1120.
  • This individual paging message 1120 is transmitted to at least one client node 300a, 300b, 300c, 300d, 300e.
  • the individual paging message therefore comprises an identifier of this one of the at least one client node 300a, 300b, 300c, 300d, 300e.
  • the paging message 1120 is a group paging message 1120.
  • the paging message 1120 can represent one common group paging message 1120.
  • This common group paging message 1120 is transmitted to a group 1110a, 1110b of client nodes 300a, 300b, 300c, 300d, 300e.
  • the group paging message 1120 therefore comprises an identifier of the group 1110a, 1110b of the at least one client node 300a, 300b, 300c, 300d, 300e.
  • MBMS bearers on which the paging message 1120 can be transmitted, as in step S106. Different embodiments relating thereto will now be disclosed in turn.
  • the MBMS bearer is a Service Announcement MBMS bearer.
  • the MBMS bearer on which the paging message 1120 can be transmitted can be used for Service Announcement in the group communications system 100, 1100a, 1100b, 1100c.
  • the MBMS bearer is a for Floor Control MBMS bearer.
  • the MBMS bearer on which the paging message 1120 can be transmitted can be used for Floor Control in the group communications system 100, 1100a, 1100b, 1100c.
  • the MBMS bearer is a Group communication control message MBMS bearer.
  • the MBMS bearer on which the paging message 1120 can be transmitted can be used for Control messages in the group communications system 100, 1100a, 1100b, 1100c.
  • the MBMS bearer is a general Group communication MBMS bearer, for example an MBMS bearer used for media transmission, in the group communications system 100, 1100a, 1100b, 1100c.
  • Steps S102 and S106 are performed as disclosed above.
  • control node 200 may obtain the need for paging. Different embodiments relating thereto will now be described in turn.
  • control node 200 is configured to obtain the need as a result of a packet being destined for the at least one client node 300a, 300b, 300c, 300d, 300e, as in step S102a: S102a: The control node 200 obtains an indication that at least one packet is destined for the at least one client node 300a, 300b, 300c, 300d, 300e. Step S102a may be performed in conjunction with, or as part of, step S102. This indication can be obtained from the node (such as another client node 300a, 300b, 300c, 300d, 300e) or device from which the at least one packet is originating. Alternatively the indication can be obtained from another control node or from a management node.
  • the second obtain module 210c comprises instructions that when executed by the control node 200 causes the processing circuitry 210, possibly in conjunction with the communications interface 220 and the storage medium 230, to obtain the indication in order for the control node 200 to perform step S102a.
  • the paging message 1120 can indicate that the at least one packet is to be transmitted to the at least one client node 300a, 300b, 300c, 300d, 300e over a unicast bearer.
  • the at least one client node 300a, 300b, 300c, 300d, 300e participates in a group call on an MBMS bearer in the group communications system 100, 1100a, 1100b, 1100c.
  • the control node 200 is configured to obtain the need as a result of the at least one client node 300a, 300b, 300c, 300d, 300e being moved to a unicast bearer as in step S102b: S102b: The control node 200 obtains an indication that the group call is to be moved to a unicast bearer. Step S102b may be performed in conjunction with, or as part of, step S102.
  • the third obtain module 210d comprises instructions that when executed by the control node 200 causes the processing circuitry 210, possibly in conjunction with the communications interface 220 and the storage medium 230, to obtains the indication in order for the control node 200 to perform step S102b.
  • each client node 300a, 300b, 300c, 300d, 300e reports its location whilst physically being moved in the group communications system 100, 1100a, 1100b, 1100c. This reporting can be performed as specified according to document 3GPP TS 23.179 v1.2.0.
  • This location information is, according to some aspects, used when the at least one client node 300a, 300b, 300c, 300d, 300e is to be paged.
  • the at least one client node 300a, 300b, 300c, 300d, 300e can then be paged over a bearer active in the current service area identifier (SAI) area and optionally also over a bearer active in at least one neighbor SAI.
  • SAI current service area identifier
  • the MBMS bearer used for transmitting the paging message 1120 can be active in a first area defined by a current SAI of the at least one client node 300a, 300b, 300c, 300d, 300e or in at least one second area defined by a SAI neighbouring the current SAI. Therefore, according to an embodiment the control node 200 is configured to perform step S104: S104: The control node 200 obtains a current location of the at least one client node 300a, 300b, 300c, 300d, 300e. The current location can then define the current SAI. By means of the location information the at least one client node 300a, 300b, 300c, 300d, 300e does not need to be paged over a large area.
  • Step S104 may be performed after step S102 but before step S106.
  • the fourth obtain module 210e comprises instructions that when executed by the control node 200 causes the processing circuitry 210, possibly in conjunction with the communications interface 220 and the storage medium 230, to obtains the current location in order for the control node 200 to perform step S104.
  • FIG. 7 illustrating a method for receiving paging in a group communications system 100, 1100a, 1100b, 1100c as performed by the client node 300a according to an embodiment.
  • the client node 300a receives a paging message 1120 for the client node 300a on an MBMS bearer.
  • the paging message 1120 is received from a control node 200 of the group communications system 100, 1100a, 1100b, 1100c.
  • the receive module 310a comprises instructions that when executed by the client node 300a causes the processing circuitry 310, possibly in conjunction with the communications interface 320 and the storage medium 330, to receive the paging message 1120 in order for the client node 300a to perform step S204.
  • Embodiments relating to further details of receiving paging in a group communications system 100, 1100a, 1100b, 1100c as performed by the client node 300a will now be disclosed.
  • the client node 300a can be in idle mode when the paging message 1120 is broadcasted, and thus received by the client node 300a in step S204.
  • the client node 300a is in idle mode when receiving the paging message 1120 in step S204.
  • paging messages 1120 that can be transmitted in step S106, and thus received by the client node 300a in step S204. These embodiments thus apply also to the client node 300a.
  • the paging message 1120 is an individual paging message 1120.
  • the paging message 1120 can represent an individual paging message 1120 and comprise an individual identifier of the client node 300a.
  • the paging message 1120 is a group paging message 1120.
  • the paging message 1120 can represent one common group paging message 1120 and comprise a group identifier of a group 1110a, 1110b of client nodes 300a, 300b, 300c, 300d, 300e, and wherein the client node 300a is a member of the group 1110a, 1110b.
  • the paging message 1120 can indicate that at least one packet destined for the client node 300a is to be transmitted to the client node 300a over a unicast bearer. Additionally or alternatively, the paging message 1120 can indicates that the client node 300a shall acquire a unicast radio bearer. The paging message 1120, according to some aspects, thus serves as to wake up the client node 300a for packets that will be transmitted on unicast. The MBMS bearer might still be monitored by the client node 300a.
  • the MBMS bearer is used for Service Announcement in the group communications system 100, 1100a, 1100b, 1100c.
  • the MBMS bearer is used for Floor Control in the group communications system 100, 1100a, 1100b, 1100c.
  • the MBMS bearer is used for Control messages in the group communications system 100, 1100a, 1100b, 1100c.
  • the MBMS bearer is a general Group communication MBMS bearer, for example an MBMS bearer used for media transmission, in the group communications system 100, 1100a, 1100b, 1100c.
  • Step S204 is performed as disclosed above.
  • the paging message 1120 could be sent over a bearer that the client node 300a is monitoring.
  • the client node 300a can thus already be monitoring the the MBMS bearer when receiving the paging message 1120.
  • the client node 300a can be configured to perform step S202:
  • S202: The client node 300a monitors the MBMS bearer prior to receiving the paging message 1120.
  • the monitor module 310b comprises instructions that when executed by the client node 300a causes the processing circuitry 310, possibly in conjunction with the communications interface 320 and the storage medium 330, to monitor the MBMS bearer in order for the client node 300a to perform step S202.
  • the client node 300a can be configured to perform steps S206 and S208:
  • An MBMS bearer may thereby be used to speed up the notification to the client node 300a that there is incoming packets over unicast and that the client node 300a therefore should initiate a service request, enter connected mode and re-establish a RAB. This is particularly applicable to client nodes 300a that are in idle mode and that are monitoring an MBMS bearer.
  • the multicast channel (MCH) Scheduling Period (MSP) can thereby be configured down to 40 ms intervals. This will allow the client node 300a to initiate a state transfer to connected mode before the state of the art MME initiated paging will reach the client node 300a.
  • the latency to set up a radio bearer to enable downlink delivery of packets (e.g. media) to the client node 300a will thus be reduced.
  • One particular embodiment for paging at least one client node 300a, 300b, 300c, 300d, 300e in a group communications system 100, 1100a, 1100b, 1100c based on at least some of the above disclosed embodiments will now be disclosed in detail with reference to the signalling diagram of Fig. 10 .
  • the group communications system 1100a comprises a first group 1110a of client nodes 300a, 300b, where the first group 1110a of client nodes 300a, 300b are engaged in a group call on an MBMS bearer.
  • the control node 200 might in near real time determine that another group of client nodes shall use the MBMS resource.
  • the group communications system 1100b of Fig. 11(b) In relation to the group communications system 1100a of Fig. 11(a) the group communications system 1100b of Fig.
  • 11(b) further comprises a second group 1110b of client nodes 300c, 300d, 300e, where a group call is started for the second group 1110b of client nodes 300c, 300d, 300e. If there are not sufficient MBMS resources to serve both groups over MBMS, one of the groups must be moved to unicast transmission. Assume that there is a higher number of client nodes 300c, 300d, 300e in the second group 1110b than client nodes 300a, 300b in the first group 1110a.
  • the control node 200 therefore determines the first group 1110a of client nodes 300a, 300b to be moved to unicast and therefore transmits a paging message 1120 to the first group 1110a of client nodes 300a, 300b, as in step S106. It is assumed that this paging message is received by the first group 1110a of client nodes 300a, 300b, as in step S204.
  • the control node 200 can thus page the the first group 1110a of client nodes 300a, 300b and then (much faster than state of the prior art) move the group call to unicast transmission to let the second group 1110b of client nodes 300c, 300d, 300e use the MBMS bearer for the new group call.
  • the first group 1110a of client nodes 300a, 300b are moved to unicast and hence the group call previously conducted on the MBMS bearer is now conducted on unicast.
  • the group call for the second group 1110b of client nodes 300c, 300d, 300e can then be started on the MBMS bearer. This situation is illustrated in the group communications system 1100c of Fig. 11(c) . This improves the resource efficiency compared to if the group call of the second group 1110b of client nodes 300c, 300d, 300e would have been be started on unicast. Using currently existing paging procedure will result in delay and possibly packet loss.

Landscapes

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

Claims (34)

  1. Procédé de radiomessagerie d'au moins un nœud client (300a, 300b, 300c, 300d, 300e) dans un système de communications de groupe (100, 1100a, 1100b, 1100c), le procédé étant mis en œuvre par un nœud de commande (200) du système de communications de groupe (100, 1100a, 1100b, 1100c), le procédé comprenant :
    l'obtention (S102) d'un besoin de radiomessagerie de l'au moins un nœud client (300a, 300b, 300c, 300d, 300e) dans le système de communications de groupe (100, 1100a, 1100b, 1100c) ; et
    la transmission (S106) d'un message de radiomessagerie (1120) pour l'au moins un nœud client (300a, 300b, 300c, 300d, 300e) sur une porteuse MBMS vers l'au moins un nœud client (300a, 300b, 300c, 300d, 300e), dans lequel le message de radiomessagerie (1120) indique que l'au moins un paquet doit être transmis à l'au moins un nœud client (300a, 300b, 300c, 300d, 300e) sur une porteuse de monodiffusion.
  2. Procédé selon la revendication 1, dans lequel l'obtention du besoin de radiomessagerie comprend :
    l'obtention (S102a) d'une indication indiquant qu'au moins un paquet est destiné à l'au moins un nœud client (300a, 300b, 300c, 300d, 300e).
  3. Procédé selon la revendication 1, dans lequel l'au moins un nœud client (300a, 300b, 300c, 300d, 300e) participe à un appel de groupe sur une porteuse MBMS dans le système de communications de groupe (100, 1100a, 1100b, 1100c), et dans lequel l'obtention du besoin de radiomessagerie comprend :
    l'obtention (S102b) d'une indication indiquant que l'appel de groupe doit être déplacé vers une porteuse de monodiffusion.
  4. Procédé selon la revendication 1, dans lequel le message de radiomessagerie (1120) représente un message de radiomessagerie individuel (1120) qui est transmis à au moins un nœud client (300a, 300b, 300c, 300d, 300e).
  5. Procédé selon la revendication 4, dans lequel le message de radiomessagerie individuel (1120) comprend un identificateur d'un parmi l'au moins un nœud client (300a, 300b, 300c, 300d, 300e).
  6. Procédé selon la revendication 1, dans lequel le message de radiomessagerie (1120) représente un message de radiomessagerie de groupe commun (1120) qui est transmis à un groupe (1110a, 1110b) de nœuds clients (300a, 300b, 300c, 300d, 300e).
  7. Procédé selon la revendication 6, dans lequel le message de radiomessagerie de groupe (1120) comprend un identificateur du groupe (1110a, 1110b) de l'au moins un nœud client (300a, 300b, 300c, 300d, 300e).
  8. Procédé selon la revendication 1, dans lequel la porteuse MBMS est utilisée pour une annonce de service dans le système de communications de groupe (100, 1100a, 1100b, 1100c).
  9. Procédé selon la revendication 1, dans lequel la porteuse MBMS est utilisée pour une commande de prise de parole dans le système de communications de groupe (100, 1100a, 1100b, 1100c).
  10. Procédé selon la revendication 1, dans lequel la porteuse MBMS est utilisée pour des messages de commande dans le système de communications de groupe (100, 1100a, 1100b, 1100c).
  11. Procédé selon la revendication 1, dans lequel la porteuse MBMS est une porteuse MBMS de communication de groupe générale dans le système de communications de groupe (100, 1100a, 1100b, 1100c).
  12. Procédé selon la revendication 1, dans lequel la porteuse MBMS utilisée pour transmettre le message de radiomessagerie (1120) est active dans une première zone définie par un identificateur de zone de service, SAI, actuel de l'au moins un nœud client (300a, 300b, 300c, 300d, 300e) ou dans au moins une deuxième zone définie par un voisinage SAI du SAI actuel.
  13. Procédé selon la revendication 12, comprenant en outre :
    l'obtention (S104) d'une localisation actuelle de l'au moins un nœud client (300a, 300b, 300c, 300d, 300e), dans lequel la localisation actuelle définit le SAI actuel.
  14. Procédé selon la revendication 1, dans lequel l'au moins un nœud client (300a, 300b, 300c, 300d, 300e) est en mode inactif lorsque le message de radiomessagerie (1120) est diffusé.
  15. Procédé de réception de radiomessagerie dans un système de communications de groupe (100, 1100a, 1100b, 1100c), le procédé étant mis en œuvre par un nœud client (300a), le procédé comprenant :
    la réception (S204) d'un message de radiomessagerie (1120) pour le nœud client (300a) sur une porteuse MBMS depuis un nœud de commande (200) du système de communications de groupe (100, 1100a, 1100b, 1100c), dans lequel le message de radiomessagerie (1120) indique qu'au moins un paquet destiné au nœud client (300a) doit être transmis au nœud client (300a) sur une porteuse de monodiffusion.
  16. Procédé selon la revendication 15, dans lequel le nœud client (300a) est en mode inactif lors de la réception du message de radiomessagerie (1120).
  17. Procédé selon la revendication 15, dans lequel le message de radiomessagerie (1120) indique que le nœud client (300a) doit acquérir une porteuse radio de monodiffusion.
  18. Procédé selon la revendication 15, comprenant en outre :
    la surveillance (S202) de la porteuse MBMS avant réception du message de radiomessagerie (1120).
  19. Procédé selon la revendication 15, comprenant en outre, après avoir reçu le message de radiomessagerie (1120) :
    le déclenchement (S206) d'une demande de service avec un nœud de réseau central ;
    l'entrée (S208) en mode connecté par rétablissement d'une porteuse d'accès radio, RAB.
  20. Procédé selon la revendication 15, dans lequel le message de radiomessagerie (1120) comprend un identificateur individuel du nœud client (300a).
  21. Procédé selon la revendication 15, dans lequel le message de radiomessagerie (1120) comprend un identificateur de groupe d'un groupe (1110a, 1110b) de nœuds clients (300a, 300b, 300c, 300d, 300e), et dans lequel le nœud client (300a) est un membre du groupe (1110a, 1110b).
  22. Procédé selon la revendication 15, dans lequel la porteuse MBMS est utilisée pour une annonce de service dans le système de communications de groupe (100, 1100a, 1100b, 1100c).
  23. Procédé selon la revendication 15, dans lequel la porteuse MBMS est utilisée pour une commande de prise de parole dans le système de communications de groupe (100, 1100a, 1100b, 1100c).
  24. Procédé selon la revendication 15, dans lequel la porteuse MBMS est utilisée pour des messages de commande dans le système de communications de groupe (100, 1100a, 1100b, 1100c).
  25. Procédé selon la revendication 15, dans lequel la porteuse MBMS est une porteuse MBMS de communication de groupe générale dans le système de communications de groupe (100, 1100a, 1100b, 1100c).
  26. Nœud de commande (200) de radiomessagerie d'au moins un nœud client (300a, 300b, 300c, 300d, 300e) dans un système de communications de groupe (100, 1100a, 1100b, 1100c), le nœud de commande (200) comprenant un circuit de traitement (210), le circuit de traitement étant configuré pour amener le nœud de commande (200) à :
    obtenir un besoin de radiomessagerie de l'au moins un nœud client (300a, 300b, 300c, 300d, 300e) dans le système de communications de groupe (100, 1100a, 1100b, 1100c) ; et
    transmettre un message de radiomessagerie (1120) pour l'au moins un nœud client (300a, 300b, 300c, 300d, 300e) sur une porteuse MBMS vers l'au moins un nœud client (300a, 300b, 300c, 300d, 300e), dans lequel le message de radiomessagerie indique que l'au moins un paquet doit être transmis à l'au moins un nœud client (300a, 300b, 300c, 300d, 300e) sur une porteuse de monodiffusion.
  27. Nœud de commande (200) de radiomessagerie d'au moins un nœud client (300a, 300b, 300c, 300d, 300e) dans un système de communications de groupe (100, 1100a, 1100b, 1100c), le nœud de commande (200) comprenant :
    un circuit de traitement (210) ; et
    un produit programme informatique (410a) stockant des instructions qui, lorsqu'elles sont exécutées par le circuit de traitement (210), amènent le nœud de commande (200) à :
    obtenir un besoin de radiomessagerie de l'au moins un nœud client (300a, 300b, 300c, 300d, 300e) dans le système de communications de groupe (100, 1100a, 1100b, 1100c) ; et
    transmettre un message de radiomessagerie (1120) pour l'au moins un nœud client (300a, 300b, 300c, 300d, 300e) sur une porteuse MBMS vers l'au moins un nœud client (300a, 300b, 300c, 300d, 300e), dans lequel le message de radiomessagerie indique que l'au moins un paquet doit être transmis à l'au moins un nœud client (300a, 300b, 300c, 300d, 300e) sur une porteuse de monodiffusion.
  28. Nœud de commande (200) de radiomessagerie d'au moins un nœud client (300a, 300b, 300c, 300d, 300e) dans un système de communications de groupe (100, 1100a, 1100b, 1100c), le nœud de commande (200) comprenant :
    un module d'obtention (210a) configuré pour obtenir un besoin de radiomessagerie de l'au moins un nœud client (300a, 300b, 300c, 300d, 300e) dans le système de communications de groupe (100, 1100a, 1100b, 1100c) ; et
    un module de transmission (210b) configuré pour transmettre un message de radiomessagerie (1120) pour l'au moins un nœud client (300a, 300b, 300c, 300d, 300e) sur une porteuse MBMS vers l'au moins un nœud client (300a, 300b, 300c, 300d, 300e), dans lequel le message de radiomessagerie indique que l'au moins un paquet doit être transmis à l'au moins un nœud client (300a, 300b, 300c, 300d, 300e) sur une porteuse de monodiffusion.
  29. Nœud client (300a) pour recevoir une radiomessagerie dans un système de communications de groupe (100, 1100a, 1100b, 1100c), le nœud client (300a) comprenant un circuit de traitement (310), le circuit de traitement étant configuré pour amener le nœud client (300a) à :
    recevoir un message de radiomessagerie (1120) pour le nœud client (300a) sur une porteuse MBMS depuis un nœud de commande (200) du système de communications de groupe (100, 1100a, 1100b, 1100c), dans lequel le message de radiomessagerie indique que l'au moins un paquet doit être transmis à l'au moins un nœud client (300a, 300b, 300c, 300d, 300e) sur une porteuse de monodiffusion.
  30. Nœud client (300a) pour recevoir une radiomessagerie dans un système de communications de groupe (100, 1100a, 1100b, 1100c), le nœud client (300a) comprenant :
    un circuit de traitement (310) ; et
    un produit programme informatique (410b) stockant des instructions qui, lorsqu'elles sont exécutées par le circuit de traitement (310), amènent le nœud client (300a) à :
    recevoir un message de radiomessagerie (1120) pour le nœud client (300a) sur une porteuse MBMS depuis un nœud de commande (200) du système de communications de groupe (100, 1100a, 1100b, 1100c), dans lequel le message de radiomessagerie indique que l'au moins un paquet doit être transmis à l'au moins un nœud client (300a, 300b, 300c, 300d, 300e) sur une porteuse de monodiffusion.
  31. Nœud client (300a) pour recevoir une radiomessagerie dans un système de communications de groupe (100, 1100a, 1100b, 1100c), le nœud client (300a) comprenant :
    un module de réception (310a) configuré pour recevoir un message de radiomessagerie (1120) pour le nœud client (300a) sur une porteuse MBMS depuis un nœud de commande (200) du système de communications de groupe (100, 1100a, 1100b, 1100c), dans lequel le message de radiomessagerie indique que l'au moins un paquet doit être transmis à l'au moins un nœud client (300a, 300b, 300c, 300d, 300e) sur une porteuse de monodiffusion.
  32. Programme informatique (420a) de radiomessagerie d'au moins un nœud client (300a, 300b, 300c, 300d, 300e) dans un système de communications de groupe (100, 1100a, 1100b, 1100c), le programme informatique comprenant un code informatique qui, lorsqu'il est exécuté sur un circuit de traitement (210) d'un nœud de commande (200), amène le nœud de commande (200) à :
    obtenir (S102) un besoin de radiomessagerie de l'au moins un nœud client (300a, 300b, 300c, 300d, 300e) dans le système de communications de groupe (100, 1100a, 1100b, 1100c) ; et
    transmettre (S106) un message de radiomessagerie (1120) pour l'au moins un nœud client (300a, 300b, 300c, 300d, 300e) sur une porteuse MBMS vers l'au moins un nœud client (300a, 300b, 300c, 300d, 300e), dans lequel le message de radiomessagerie indique que l'au moins un paquet doit être transmis à l'au moins un nœud client (300a, 300b, 300c, 300d, 300e) sur une porteuse de monodiffusion.
  33. Programme informatique (420b) pour recevoir une radiomessagerie dans un système de communications de groupe (100, 1100a, 1100b, 1100c), le programme informatique comprenant un code informatique qui, lorsqu'il est exécuté sur un circuit de traitement (310) d'un nœud client (300a), amène le nœud client (300a) à :
    recevoir (S204) un message de radiomessagerie (1120) pour le nœud client (300a) sur une porteuse MBMS depuis un nœud de commande (200) du système de communications de groupe (100, 1100a, 1100b, 1100c), dans lequel le message de radiomessagerie (1120) indique que l'au moins un paquet doit être transmis à l'au moins un nœud client (300a, 300b, 300c, 300d, 300e) sur une porteuse de monodiffusion.
  34. Produit programme informatique (410a, 410b) comprenant un programme informatique (420a, 420b) selon au moins l'une des revendications 32 et 33, et un support de stockage lisible par ordinateur (430) sur lequel est stocké le programme informatique.
EP16766921.7A 2015-12-15 2016-09-13 Radiorecherche dans un système de communications de groupe Active EP3354089B1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP20159583.2A EP3681219B1 (fr) 2015-12-15 2016-09-13 Radiorecherche dans un système de communications de groupe
DK20159583.2T DK3681219T3 (da) 2015-12-15 2016-09-13 Paging i et gruppekommunikationssystem

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201562267454P 2015-12-15 2015-12-15
PCT/EP2016/071604 WO2017102114A1 (fr) 2015-12-15 2016-09-13 Radiorecherche dans un système de communications de groupe

Related Child Applications (2)

Application Number Title Priority Date Filing Date
EP20159583.2A Division EP3681219B1 (fr) 2015-12-15 2016-09-13 Radiorecherche dans un système de communications de groupe
EP20159583.2A Division-Into EP3681219B1 (fr) 2015-12-15 2016-09-13 Radiorecherche dans un système de communications de groupe

Publications (2)

Publication Number Publication Date
EP3354089A1 EP3354089A1 (fr) 2018-08-01
EP3354089B1 true EP3354089B1 (fr) 2020-04-08

Family

ID=56943515

Family Applications (2)

Application Number Title Priority Date Filing Date
EP16766921.7A Active EP3354089B1 (fr) 2015-12-15 2016-09-13 Radiorecherche dans un système de communications de groupe
EP20159583.2A Active EP3681219B1 (fr) 2015-12-15 2016-09-13 Radiorecherche dans un système de communications de groupe

Family Applications After (1)

Application Number Title Priority Date Filing Date
EP20159583.2A Active EP3681219B1 (fr) 2015-12-15 2016-09-13 Radiorecherche dans un système de communications de groupe

Country Status (9)

Country Link
US (2) US10506551B2 (fr)
EP (2) EP3354089B1 (fr)
JP (2) JP6672460B2 (fr)
CN (1) CN108432306B (fr)
AR (1) AR106993A1 (fr)
DK (1) DK3681219T3 (fr)
ES (1) ES2914424T3 (fr)
WO (1) WO2017102114A1 (fr)
ZA (1) ZA201803008B (fr)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110383863A (zh) * 2017-03-16 2019-10-25 瑞典爱立信有限公司 使用mbms的公共警告消息
WO2022128100A1 (fr) * 2020-12-17 2022-06-23 Nokia Technologies Oy Réception efficace des mesures de capteurs

Family Cites Families (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20040061705A (ko) * 2002-12-31 2004-07-07 삼성전자주식회사 멀티캐스트 멀티미디어 방송 서비스를 위한 이동통신시스템에서 서비스 개시를 위한 정보 전송 방법
US20080090593A1 (en) * 2006-10-12 2008-04-17 Innovative Sonic Limited Method and related apparatus for enhancing paging efficiency in a wireless communications system
JP5040665B2 (ja) * 2008-01-11 2012-10-03 三菱電機株式会社 移動体通信システム
CN102057743B (zh) 2008-07-08 2014-10-01 夏普株式会社 通信系统、接收装置和通信方法
EP2346292B1 (fr) 2008-11-06 2020-12-16 Sharp Kabushiki Kaisha Système de communication, dispositif de station de base, dispositif de station mobile et procédé de communication
US8675553B2 (en) * 2009-03-26 2014-03-18 Qualcomm Incorporated Regulating the scope of service geographically in wireless networks based on priority
US9491590B2 (en) * 2011-05-31 2016-11-08 Qualcomm Incorporated Group communications over evolved multimedia broadcast/multicast services
CN103108285A (zh) * 2011-11-10 2013-05-15 中兴通讯股份有限公司 一种集群业务的实现方法及基于eMBMS的集群系统
US9294886B2 (en) * 2012-08-31 2016-03-22 Qualcomm Incorporated Evolved multimedia broadcast/multicast services (eMBMS) geo-location based group call
CN104247470B (zh) * 2013-04-09 2020-06-02 华为技术有限公司 数据传输方法、装置及系统
WO2014183279A1 (fr) * 2013-05-15 2014-11-20 Qualcomm Incorporated Support de groupe et selection de support pour transmissions de donnees en diffusion groupee/diffusion generale
CN104254054B (zh) * 2013-06-25 2018-05-15 电信科学技术研究院 一种集群通信方法及装置和系统
WO2015066844A1 (fr) * 2013-11-05 2015-05-14 华为技术有限公司 Procédé et appareil pour transmettre et obtenir des informations, serveur d'applications, station de base, et terminal
US9474047B2 (en) * 2013-11-13 2016-10-18 Motorola Solutions, Inc. Apparatus and method for dynamically selecting unicast or broadcast resources for a push-to-talk call
MX2016008948A (es) * 2014-01-08 2016-12-09 Kodiak Networks Inc Metodos optimizados para llamadas de grupo grande utilizando portadoras de transporte de difusion unidireccional y multidireccional para servicios de pulsa y habla a traves de celular (poc).
US20160150590A1 (en) * 2014-11-21 2016-05-26 Samsung Electronics Co., Ltd. Method and system for indicating a multicast session to user equipment (ue) in an idle mode
US10820162B2 (en) * 2015-12-08 2020-10-27 At&T Intellectual Property I, L.P. Method and system for mobile user-initiated LTE broadcast
US9913249B2 (en) * 2015-12-09 2018-03-06 At&T Intellectual Property I, L.P. Method and system for selective paging of wireless devices using a cellular broadcast service

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
None *

Also Published As

Publication number Publication date
US20180368102A1 (en) 2018-12-20
ZA201803008B (en) 2019-07-31
EP3681219A1 (fr) 2020-07-15
US20200077363A1 (en) 2020-03-05
US10506551B2 (en) 2019-12-10
US11140656B2 (en) 2021-10-05
JP2019503132A (ja) 2019-01-31
WO2017102114A1 (fr) 2017-06-22
JP6672460B2 (ja) 2020-03-25
CN108432306B (zh) 2021-12-07
ES2914424T3 (es) 2022-06-10
AR106993A1 (es) 2018-03-07
CN108432306A (zh) 2018-08-21
JP2020109981A (ja) 2020-07-16
JP7100077B2 (ja) 2022-07-12
EP3681219B1 (fr) 2022-03-23
DK3681219T3 (da) 2022-04-04
EP3354089A1 (fr) 2018-08-01

Similar Documents

Publication Publication Date Title
US20220248184A1 (en) Communication Method And Apparatus
EP3051848B1 (fr) Méthode de transmission single-cell point-to-multipoint
EP3409035B1 (fr) Commutation dynamique de service de transmission en continu entre une distribution en mode diffusion et en mode unidiffusion
WO2015017188A1 (fr) Gestion d'un service de diffusion multidiffusion multimédia à l'aide d'un dispositif de relais mbms
JP2011061591A (ja) 無線通信システム、基地局装置、移動局装置および通信方法
AU2019266800A1 (en) Communication method and apparatus
US11140656B2 (en) Paging in a group communications system
EP3087764B1 (fr) Procédés, noeud utilisateur et noeud réseau dans un réseau de service de diffusion multidiffusion multimédia (mbms)
EP3453193B1 (fr) Établissement d'appel de groupe dans un système de communication de groupe
EP3703397B1 (fr) Gestion de porteuses mbms dans un système de communications de groupe
EP3434032B1 (fr) Radiomessagerie d'un noeud client dans un système de communications de groupe
EP3241305B1 (fr) Rapports d'interruption de service
WO2022205570A1 (fr) Procédé de communication sans fil, dispositif terminal et dispositif de réseau
CN105682127B (zh) 一种d2d发现资源冲突的解决方法
EP3206417B1 (fr) Procédé et appareil de communication de groupe
CN114846825A (zh) 一种数据转发方法及装置、通信设备

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20180426

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)
GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

INTG Intention to grant announced

Effective date: 20191113

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

Ref country code: AT

Ref legal event code: REF

Ref document number: 1256098

Country of ref document: AT

Kind code of ref document: T

Effective date: 20200415

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602016033659

Country of ref document: DE

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20200408

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200408

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200408

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200408

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200808

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200817

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200408

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200709

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200708

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1256098

Country of ref document: AT

Kind code of ref document: T

Effective date: 20200408

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: RS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200408

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200708

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200408

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200408

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: AL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200408

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602016033659

Country of ref document: DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200408

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200408

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200408

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200408

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200408

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200408

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200408

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200408

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200408

26N No opposition filed

Effective date: 20210112

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200408

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20200930

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200913

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200930

Ref country code: BE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200930

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200930

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200408

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200408

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200408

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200408

P01 Opt-out of the competence of the unified patent court (upc) registered

Effective date: 20230523

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: TR

Payment date: 20230823

Year of fee payment: 8

Ref country code: IT

Payment date: 20230921

Year of fee payment: 8

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20240927

Year of fee payment: 9

Ref country code: IE

Payment date: 20240927

Year of fee payment: 9

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20240927

Year of fee payment: 9

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20240925

Year of fee payment: 9