WO2018171892A1 - Gestion de porteuse mbms dans un système de communications de groupe - Google Patents

Gestion de porteuse mbms dans un système de communications de groupe Download PDF

Info

Publication number
WO2018171892A1
WO2018171892A1 PCT/EP2017/057049 EP2017057049W WO2018171892A1 WO 2018171892 A1 WO2018171892 A1 WO 2018171892A1 EP 2017057049 W EP2017057049 W EP 2017057049W WO 2018171892 A1 WO2018171892 A1 WO 2018171892A1
Authority
WO
WIPO (PCT)
Prior art keywords
mbms bearer
communications system
group communications
mbms
bearer
Prior art date
Application number
PCT/EP2017/057049
Other languages
English (en)
Inventor
Magnus TRÄNK
Joakim ÅKESSON
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/EP2017/057049 priority Critical patent/WO2018171892A1/fr
Publication of WO2018171892A1 publication Critical patent/WO2018171892A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/40—Connection management for selective distribution or broadcast
    • 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
    • H04W72/00—Local resource management
    • H04W72/30—Resource management for broadcast services

Definitions

  • Embodiments presented herein relate to methods, a control node, a client node, computer programs, and a computer program product for MBMS bearer handling in a group communications system.
  • 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
  • PTT Push-To-Talk
  • 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.
  • MBMS Multicast-Broadcast Multimedia Services
  • an MBMS bearer must be activated. This will enable media to be sent over the network and be broadcasted to wireless devices hosting the client nodes.
  • 3GPP 3rd Generation Partnership Project
  • LTE Long Term Evolution
  • BMSC Broadcast Multicast Service Center
  • the client nodes must be informed of the service being broadcasted over the MBMS bearer. This is required so that the client nodes know how to receive the media over the MBMS bearer.
  • This procedure is commonly known as a service announcement procedure and is defined in 3GPP TS 26.346
  • the information sent in the service announcement message includes several aspects of the service that shall be broadcasted. For example, it includes a reference to the MBMS bearer, it includes Internet protocol (IP) address, ports, protocols and codecs used to receive the media that shall broadcasted. This type of information is currently essential in order for the client node to, via its hosting wireless device, receive anything on the MBMS bearer, and is therefore currently mandatory.
  • the service announcement may contain several other type of information, such as service area, scheduling information, reception reporting procedures, error correction information, etc.
  • both of the above mandatory activities must be performed before a group call over MBMS may start.
  • the reason for this is that, at least currently, both bearer activation and service announcement is too time consuming to be performed at the start of the group call.
  • An object of embodiments herein is to provide efficient use of MBMS capacity in a group communications system.
  • a method for MBMS bearer handling in a group communications system is performed by a control node.
  • the method comprises activating a second MBMS bearer using Single Cell Point to Multipoint (SC-PTM) transmission in the group communications system upon need.
  • SC-PTM Single Cell Point to Multipoint
  • the method comprises announcing the second MBMS bearer on an already activated and announced first MBMS bearer to client nodes of the group communications system.
  • control node for MBMS bearer handling in a group communications system.
  • the control node comprises processing circuitry.
  • the processing circuitry is configured to cause the control node to activate a second MBMS bearer using SC-PTM transmission in the group communications system upon need.
  • processing circuitry is configured to cause the control node to announce the second MBMS bearer on an already activated and announced first MBMS bearer to client nodes of the group communications system.
  • control node for MBMS bearer handling in a group communications system.
  • the control node comprises processing circuitry and a storage medium.
  • the storage medium stores instructions that, when executed by the processing circuitry, cause the control node to perform operations, or steps.
  • the operations, or steps, cause the control node to activate a second MBMS bearer using SC-PTM
  • control node causes the control node to announce the second MBMS bearer on an already activated and announced first MBMS bearer to client nodes of the group communications system.
  • a control node for MBMS bearer handling in a group communications system comprises an activate module configured to activate a second MBMS bearer using SC-PTM transmission in the group communications system upon need.
  • the control node comprises an announce module configured to announce the second MBMS bearer on an already activated and announced first MBMS bearer to client nodes of the group communications system.
  • a computer program for MBMS bearer handling in a group communications system comprises 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.
  • a method for MBMS bearer handling in a group communications system is performed by a client node.
  • the method comprises obtaining announcement of a second MBMS bearer on an already announced first MBMS bearer from a control node of the group communications system, wherein the second MBMS bearer uses SC-PTM transmission.
  • a client node for MBMS bearer handling in a group communications system comprises processing circuitry.
  • the processing circuitry is configured to cause the client node to obtain announcement of a second MBMS bearer on an already announced first MBMS bearer from a control node of the group communications system, wherein the second MBMS bearer uses SC-PTM transmission.
  • the client node comprises processing circuitry and a storage medium.
  • the storage medium stores instructions that, when executed by the processing circuitry, cause the client node to obtain announcement of a second MBMS bearer on an already announced first MBMS bearer from a control node of the group
  • the second MBMS bearer uses SC-PTM transmission.
  • a client node for MBMS bearer handling in a group communications system comprises an obtain module configured to obtain announcement of a second MBMS bearer on an already announced first MBMS bearer from a control node of the group communications system, wherein the second MBMS bearer uses SC-PTM transmission.
  • a computer program for MBMS bearer handling 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.
  • 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 could be a non-transitory computer readable storage medium.
  • MMSFN Multicast-Broadcast Single Frequency Network
  • SIR Signal-to-Interference Ratio
  • SC-PTM Signal-to-Interference Ratio
  • FIG. 1 is a schematic diagram illustrating a communications system wherein according to embodiments can be applied;
  • Fig. 2 is a signalling diagram
  • Figs. 3, 4, 5, and 6 are flowcharts of methods according to embodiments
  • Fig. 7 is a signalling diagram according to an embodiment
  • Fig. 8 is a schematic diagram showing functional units of a control node according to an embodiment
  • Fig. 9 is a schematic diagram showing functional modules of a control node according to an embodiment
  • Fig. 10 is a schematic diagram showing functional units of a client node according to an embodiment
  • Fig. 11 is a schematic diagram showing functional modules of a client node according to an embodiment
  • Fig. 12 shows one example of a computer program product comprising computer readable means according to an embodiment.
  • Fig. l 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 communications 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 group communications system provides group
  • Each client node 300a, 300b, 300c, 30od could implement the functionality of a mission critical (MC) service client.
  • MC mission critical
  • Each client node 300a, 300b, 300c, 30od may be provided in, or installed on, a respective wireless device 160a, 160b, 160c, i6od.
  • any operation, step, action, or similar as performed by a client node 300a, 300b, 300c, 30od can be seen as performed by the corresponding wireless device 160a, 160b, 160c, i6od.
  • the communications system 100 comprises a radio access network 120, a core network 130, and a service network 140.
  • the communications system 100 further comprises at least one control node 200.
  • the at least one control node 200 may be provided in, or installed on, a radio access network node 110a, 110b, 110c providing network access in cells 150a, 150c, lsod or in another entity or device in the radio access network 120, in an entity or device of the core network 130, or in an entity or device of the service network 140.
  • the at least one control node 200 could implement the functionality of a group communication service application server (GCS AS) or an MC service server or a Broadcast Multicast Service Center (BMSC).
  • GCS AS group communication service application server
  • BMSC Broadcast Multicast Service Center
  • the nodes indicated herein may be seen as functions, where each function may be implemented in one or more physical entities.
  • 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 160a, 160b, 160c, i6od, and hence the client nodes 300a, 300b, 300c, 30od, to access services and exchange data as provided by the service network 140.
  • the client nodes 300a, 300b, 300c, 30od are thereby enabled to communicate with the control node 200.
  • wireless devices 160a, 160b, 160c, i6od 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 110a, 110b, 100c, lood include, but are not limited to, radio base stations, base transceiver stations, Node Bs, evolved Node Bs, gigabit Node Bs and access points.
  • the communications system 100 may comprise a plurality of radio access network nodes 110a, 110b, 110c, each providing network access in cells 150a, 150b, 150c to a plurality of wireless devices 160a, 160b, 160c, i6od.
  • the herein disclosed embodiments are not limited to any particular number of radio access network nodes 110a, 110b, 110c, client nodes 300a, 300b, 300c, 30od or wireless devices 160a, 160b, 160c, i6od.
  • the first transmission mode is a transmission mode where a group of adjacent radio access network nodes 110a, 110b, 110c sends the same signal simultaneously on the same frequency.
  • MBSFN is a transmission mode where a group of adjacent radio access network nodes 110a, 110b, 110c sends the same signal simultaneously on the same frequency.
  • this makes the MBSFN transmission appears to a wireless device 160a, 160b, 160c, i6od as a transmission from a single large cell 150a, 150b, 150c, which dramatically increase the SIR due to the absence of inter-cell interference.
  • SC-PTM A second transmission mode, SC-PTM, was introduced for E-UTRAN
  • SC-PTM transmission can be used with finer geographically granularity since SC-PTM transmission could be used only in cells 150a, 150b, 150c where the wireless devices 160a, 160b, 160c, i6od are located.
  • MBSFN transmission is an MBMS Control Channel (MCCH) is used to inform the wireless devices 160a, 160b, 160c, i6od in which subframe data will be transmitted.
  • MCCH MBMS Control Channel
  • the MCCH can be transmitted every 320 ms and modified only every 5120 ms.
  • SC-MCCH corresponding channel
  • MBMS bearer handling in a group communications system 100 will now be disclosed in detail with reference to the signalling diagram of Fig. 2.
  • 3GPP Third generation partnership project
  • LTE Long Term Evolution
  • BMSC Broadcast Multicast Service Center
  • the second part of the preparation is to inform the client nodes 300a, 300b, 300c, 30od of the service being broadcasted over the MBMS bearer.
  • step S301 This is required so that the client nodes 300a, 300b, 300c, 30od knows how to, via the wireless devices 160a, 160b, 160c, i6od, receive the media over the MBMS bearer.
  • This procedure is commonly known as an MBMS bearer announcement and is defined in 3GPP TS 23.280 V14.1.0.
  • the control node 200 activates and announces an MBMS bearer for group communications to the client nodes 300a, 300b, 300c, 30od in the group communications system 100.
  • Group calls are typically short with long periods of silence between the calls.
  • the announcement as well as group calls may thus be followed by periods of silence.
  • the client nodes 300a, 300b, 300c, 30od via its wireless devices 160a, 160b, 160c, i6od, monitors the MBMS bearer and waits for group call setup messages.
  • One of the client nodes 300b sends a group call setup message to the control node 200 and the control node sets up the group call for the client nodes 300a, 300b, 300c, 30od.
  • Step S302 illustrates a new group call setup message initiated by client node 300b.
  • the group call setup message is first sent to the control node 200 which forwards the setup message of the group call on the MBMS bearer to the remaining client nodes 300a, 300c, 30od.
  • the client node 300b sends group call media to the control node 200 and the control node 200 forwards the media on the MBMS bearer to the remaining client nodes 300b, 300c, 30od.
  • the group call media is thus sent in step S303 from client node 300b to the the control node 200 which broadcast the media on the MBMS bearer
  • the performance requirements for a call setup is typically ⁇ 300 ms.
  • MBSFN transmission this implies that the MBSFN transmission must be pre-activated in the network and announced to the client nodes 300a, 300b, 300c, 30od prior the call setup, in accordance with the signalling diagram of Fig. 2.
  • the announcement of the MBMS bearer is followed by a period of silence and the client nodes 300a, 300b, 300c, 30od need to monitor the MBMS bearer on the MBSFN transmission to listen for any call setup message.
  • the constant monitoring of the MBMS bearer is power consuming.
  • the MBMS bearer when using SC-PTM transmission the MBMS bearer can be started by the call setup requests, and it is still possible to reach the call setup performance requirements.
  • SC-PTM transmission instead of MBSFN transmission in the signalling diagram of Fig. 2 would mitigate latency issues but would increase the risk of inter-cell interference, especially for wireless devices located at cell borders.
  • the MBMS bearer using SC-PTM transmission could be activated only in the cells in which it is needed.
  • the embodiments disclosed herein therefore relate to mechanisms for MBMS bearer handling in a group communications system 100.
  • a control node 200 In order to obtain such mechanisms there is provided 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.
  • a client node 300a, 300b, 300c, 30od a method performed by the client node 300a, 300b, 300c, 30od
  • 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, 300b, 300c, 30od, causes the client node 300a, 300b, 300c, 30od to perform the method.
  • Figs. 3 and 4 are flowcharts illustrating embodiments of methods for MBMS bearer handling in a group communications system 100 as performed by the control node 200.
  • Figs. 5 and 6 are flowcharts illustrating embodiments of methods for MBMS bearer handling in a group communications system 100 as performed by the client node 300a, 300b, 300c, 30od.
  • the methods are advantageously provided as computer programs 1220a, 1220b.
  • Fig. 3 illustrating a method for MBMS bearer handling in a group communications system 100 as performed by the control node 200 according to an embodiment.
  • the control node 200 is configured to activate a second MBMS only when needed. Hence the control node 200 is configured to perform step S106:
  • the control node 200 activates the second MBMS bearer using SC- PTM transmission in the group communications system 100 upon need.
  • Different examples of needs upon which the second MBMS bearer is activated (and thus reasons for the control node 200 to activate the MBMS bearer) will be disclosed below.
  • the second MBMS bearer is announced on an already existing MBMS bearer.
  • the control node 200 is configured to perform step S108: S108: The control node 200 announces the second MBMS bearer on an already activated and announced first MBMS bearer to client nodes 300a, 300b, 300c, 30od of the group communications system 100.
  • Fig. 4 illustrating methods for MBMS bearer handling in a group communications system 100 as performed by the control node 200 according to further embodiments. It is assumed that steps S106, S108 are performed as described above with reference to Fig. 3 and a thus repeated description thereof is therefore omitted. As disclosed above, the first MBMS bearer is already activated and announced when the second MBMS bearer is announced. Hence, according to an embodiment the control node 200 is configured to perform step S102:
  • the control node 200 activates and announces the first MBMS bearer for announcing the second MBMS bearer.
  • the first MBMS bearer may be activated and announced as in step S301 above.
  • the second MBMS bearer is activated upon need. There may be different examples of such needs. Embodiments relating thereto will now be disclosed in turn. In some aspects the second MBMS bearer is activated in response to a new group call being started by one of the client nodes 300a, 300b, 300c, 30od.
  • control node 200 is configured to perform step Si04a:
  • the control node 200 obtains an indication of a group call in the group communications system 100 being started by one of the client nodes 300a, 300b, 300c, 30od. According to this embodiment the obtained indication defines the need in step S106.
  • the second MBMS bearer is thus activated and announced in response thereto (i.e., in response to the indication being obtained in step Si04a).
  • the control node 200 could thus activate the second MBMS bearer upon detecting that a new group call is started.
  • the second MBMS bearer is activated in response to a capacity need during an ongoing call.
  • the control node 200 is configured to perform step Si04b: Si04b:
  • the control node 200 obtains an indication of modified payload capacity need during an ongoing group call in the group communications system 100.
  • the obtained indication defines the need in step S106.
  • the second MBMS bearer is thus activated and announced in response thereto (i.e., in response to the indication being obtained in step Si04b).
  • the modified payload capacity need represents an increase in payload capacity need.
  • An example is that transmission of a video stream is added to an ongoing group call only using audio.
  • the control node 200 could thus activate the second MBMS bearer upon detecting that a video stream is added to an ongoing group call.
  • the second MBMS bearer is activated in response to an increased number of client nodes 300a, 300b, 300c, 30od taking part in an ongoing group call.
  • the control node 200 is configured to perform step S104C:
  • the control node 200 obtains an indication of increasing number of client nodes 300a, 300b, 300c, 30od taking part in an ongoing group call in the group communications system 100. According to this embodiment the obtained indication defines the need in step S106.
  • the second MBMS bearer is thus activated and announced in response thereto (i.e., in response to the indication being obtained in step S104C).
  • control node 200 could thus activate the second MBMS bearer upon detecting that the number of client nodes 300a, 300b, 300c, 30od participating in the ongoing group call has increased.
  • the second MBMS bearer is not activated in all cells 150a, 150b, 150c of the group communication system 100. Therefore, the control node 200 could evaluate in which cells to activate the second MBMS bearer.
  • control node 200 is configured to perform step Sio6a as part of step S106:
  • Sio6a The control node 200 determines to activate the second MBMS bearer in a subset 150a, 150b of all cells 150a, 150b, 150c of the group communication system 100.
  • the second MBMS bearer is activated only in this subset of cells 150a, 150b.
  • control node 200 could be different ways for the control node 200 to determine in which cells 150a, 150b to activate the second MBMS bearer.
  • One example is for the control node 200 to activate the second MBMS only in those cells in which comparatively many client nodes are located.
  • the determination could be based on subjecting the number of client nodes in each cell to a threshold.
  • the second MBMS bearer could be activated only in the cells 150a, 150b where client nodes 300a, 300b, 300c interested in the group call are located. There might be other client nodes in the same area which are monitoring the first MBMS bearer but are not interested in the specific group call.
  • the announcement of the second MBMS bearer comprises a list of those cells 150a, 150b in which the second MBMS bearer is activated. That is, according to an embodiment the announcement of the second MBMS bearer comprises information of the subset of cells 150a, 150b in which the second MBMS bearer is activated.
  • control node 200 is notified about any client nodes 30od located outside those cells in which the second MBMS bearer is activated and for which unicast is needed, see also step S204 below.
  • control node 200 is configured to perform step S110:
  • the control node 200 obtains, from a client node 30od located outside the subset of cells 150a, 150b in which the second MBMS bearer is activated, a request for unicast transmission of media of a group call of the group communications system 100.
  • the control node 200 could use unicast transmission for transmitting media of the group call for those client nodes located outside the cells in which the second MBMS bearer is activated.
  • the control node 200 is configured to perform step Sii2b: Sii2b: The control node 200 transmits the media using unicast transmission to the client node 30od located outside the subset of cells 150a, 150b in which the second MBMS bearer is activated.
  • control node 200 is configured to perform step Sii2a: Sii2a: The control node 200 transmits media of a group call of the group communications system 100 using the second MBMS bearer.
  • Steps Sii2a and Sii2b could be performed in parallel.
  • Fig. 5 illustrating a method for MBMS bearer handling in a group communications system 100 as performed by the client node 300a, 300b, 300c, 30od according to an embodiment.
  • control node 200 in step 108 announces the second MBMS bearer.
  • the client node 300a, 300b, 300c, 30od is therefore configured to perform step S202:
  • the client node 300a, 300b, 300c, 30od obtains announcement of the second MBMS bearer on an already announced first MBMS bearer from the control node 200 of the group communications system 100.
  • the second MBMS bearer uses SC-PTM transmission.
  • Fig. 6 illustrating methods for MBMS bearer handling in a group communications system 100 as performed by the client node 300a, 300b, 300c, 30od according to further embodiments. It is assumed that step S202 is performed as described above with reference to Fig. 5 and a thus repeated description thereof is therefore omitted.
  • the announcement of the second MBMS bearer comprises a list of cells in which the second MBMS bearer is activated.
  • communications system 100 comprises cells 150a, 150b, 150c served by radio access network nodes 110a, 110b, 110c, and the second MBMS bearer is activated only in a subset of cells 150a, 150b, and the announcement of the second MBMS bearer comprises information of the subset of cells 150a, 150b in which the second MBMS bearer is activated.
  • control node 200 is notified about client nodes 30od located outside the cells 150a, 150b in which the second MBMS bearer is activated and thus for which unicast transmission is needed.
  • the client node 30od is configured to perform step S204:
  • the client node 30od provides, to the control node 200, a request for unicast transmission of media of a group call of the group communications system 100.
  • unicast transmission of the media of the group call could be used for those client nodes 30od being outside the cells 150a, 150b in which the second MBMS bearer is activated.
  • the client node 30od is configured to perform step S2o6b: l8
  • the client node 30od receives the media (of the group call) on a unicast bearer from the control node 200.
  • the media is broadcasted using the second MBMS bearer inside the subset of cells 150a, 150b in which the second MBMS bearer is activated.
  • the client node 300a, 300b, 300c is configured to perform step S2o6a:
  • the client node 300a, 300b, 300c receives media of a group call of the group communications system (100) on the second MBMS bearer.
  • control node 200 and the client nodes 300a, 300b, 300c, 30od Aspects and embodiments equally applicable to the control node 200 and the client nodes 300a, 300b, 300c, 30od and the methods performed by the control node 200 and the client nodes 300a, 300b, 300c, 30od will now be disclosed.
  • first MBMS bearer is using MBSFN transmission.
  • MBSFN transmission is efficient when the same media is to be transmitted in many cells 150a, 150b.
  • the announcement of the second MBMS bearer comprises identity information of the second MBMS bearer.
  • identity information is a
  • Temporary Mobile Group Identity This enables the client nodes 300a, 300b, 300c, 30od to identify the second MBMS bearer.
  • a group call setup message is broadcasted on the first MBMS bearer. Therefore, according to an embodiment the
  • announcement of the second MBMS bearer is sent in a call setup message broadcasted on the first MBMS bearer. This is an efficient way to announce the second MBMS bearer.
  • the control node 200 could be different purposes for the control node 200 to activate and use the first MBMS bearer.
  • the first MBMS bearer is mostly used for application level control signalling. That is, according to an embodiment the already activated and announced MBMS bearer is used for application level control signalling in the group communications system 100. This enables efficient transmission of application level control signalling in the group communications system 100.
  • the control node 200 could be different purposes for the control node 200 to activate and use the second MBMS bearer.
  • the second MBMS bearer is mostly used for media transmission (i.e., for transmission of the group communication data). That is, according to an embodiment the second MBMS bearer is activated for supporting media transmission in a group call of the group communications system 100. This enables efficient transmission of media in the group communications system 100.
  • step S401 The control node 200 activates and announces a first MBMS bearer for group communications to the client nodes 300a, 300b, 300c, 30od in the group communications system 100.
  • the MBMS bearer is activated with a quality of service and bandwidth that is suitable and dimensioned for group communication signaling messages (also known as application level control signaling in 3GPP TS 23.280 ⁇ ⁇ . ⁇ ).
  • One way to implement step S401 is to perform step S102.
  • the capacity of the first MBMS bearer could be low (such as lower than the capacity of the second MBMS bearer) and one main purpose of the first MBMS bearer is for application level control signalling messages, e.g. call setup messages, floor control messages. Typically, the first MBMS bearer is not intended for media.
  • S402 The client nodes 300a, 300b, 300c, 30od start to monitor the MBMS bearer and acknowledge reception of the MBMS bearer to the control node 200.
  • Step S403 Client node 300b starts a new group call by sending a group call setup message to the control node 200.
  • One way to implement step S403 is to perform step Si 04 a.
  • step S404 The control node 200 evaluates in which of the cells 150a, 150b, 150c it is efficient to use MBMS transmission.
  • the control node 200 could decide to start a new, second, MBMS bearer with SC-PTM transmission in all cells 150a, 150b, 150c that the first MBMS bearer is started in or a subset of these cells.
  • One way to implement step S404 is to perform step Sio6a.
  • Step S405 and S406 could then be performed in parallel.
  • step S405 The control node 200 activates the second MBMS bearer for SC-PTM transmission.
  • This second MBMS bearer may be started with a different quality of service and bandwidth compared to the first MBMS bearer, with the objective to carry the media of the group call.
  • One way to implement step S405 is to perform step S106.
  • the second MBMS bearer is only activated in the cells where client nodes 300a, 300b, 300c, 30od interested to take part in the group call are located. There may be other client nodes 300a, 300b, 300c, 30od in other cells that are monitoring the first MBMS bearer but are not interested in the specific group call. Activation of the second MBMS bearer in less than all cells gives improved utilization of network resources . Also, activating the second MBMS bearer for SC-PTM
  • step S406 The control node 200 broadcasts the group call setup message on the first MBMS bearer.
  • the group call setup message includes an announcement message for the second MBMS bearer.
  • the control node 200 thus announces the second MBMS bearer on the first MBMS bearer.
  • This announcement message comprises at least the TMGI of the second MBMS bearer.
  • the TMGI is acting as the identity of the second MBMS bearer.
  • the message may further comprise a list of the cells 150a, 150b in which the second MBMS bearer is activated.
  • One way to implement step S406 is to perform step S108 and step S202.
  • step S407 Client node 30od located in a cell 150c, in which the second MBMS bearer is not activated in, requests the control node 200 to transmit the group call using unicast transmission to this client node 30od. This will improve call setup time since paging for this client node 30od is not required.
  • step S407 One way to implement step S407 is to perform step S110 and step S204.
  • step S408 The control node 200 broadcasts the media of the group call over the second MBMS bearer to client nodes 300a, 300b, 300c and/or over unicast transmission to client node 300b not in cells 150a, 150b in which the second MBMS bearer has been activated.
  • step S408 is to perform any of step Sii2a and/or step Sii2b, and step S2o6a and/or step S2o6b.
  • Fig. 8 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 1210a (as in Fig. 12), 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, Si02-Sii2b, 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 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 with other entities, nodes, and devices of the group communications system 100 and particularly the client nodes 300a, 300b, 300c, 30od.
  • the communications interface 220 may comprise one or more transmitters and receivers, comprising analogue and digital
  • 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. 9 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. 9 comprises a number of functional modules; an activate module 2ioe configured to perform step S106, and an announce module 2iog configured to perform step S108.
  • the control node 200 of Fig. 9 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. 9 comprises a number of functional modules; an activate module 2ioe configured to perform step S106, and an announce module 2iog configured to perform step S108.
  • 9 may further comprise a number of optional functional modules, such as any of an activate and announce module 210a configured to perform step S102, a first obtain module 210b configured to perform step Si04a, a second obtain module 210c configured to perform step Si04b, a third obtain module 2iod configured to perform step S104C, a determine module 2iof configured to perform step Sio6a, a fourth obtain module 2ioh configured to perform step S110, a first transmit module 2101 configured to perform step Sii2a, and a second transmit module 2ioj configured to perform step Sii2b.
  • optional functional modules such as any of an activate and announce module 210a configured to perform step S102, a first obtain module 210b configured to perform step Si04a, a second obtain module 210c configured to perform step Si04b, a third obtain module 2iod configured to perform step S104C, a determine module 2iof configured to perform step Sio6a, a fourth obtain module 2ioh configured to perform step S110, a
  • each functional module 2ioa-2ioj may be implemented in hardware or in software.
  • one or more or all functional modules 2ioa-2ioj 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 2ioa-2ioj and to execute these instructions, thereby performing any steps of the control node 200 as disclosed herein.
  • 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 120 or in a node of the core network 130 or in a node of the service network 140.
  • 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 the service network) or may be spread between at least two such network parts.
  • 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 120 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 120, such as in the radio access network node 110a, 110b, 100c, lood, 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. 8 the processing circuitry 210 may be distributed among a plurality of devices, or nodes. The same applies to the functional modules 2ioa-2ioj of Fig. 9 and the computer program 1210a of Fig. 12 (see below).
  • Fig. 10 schematically illustrates, in terms of a number of functional units, the components of a client node 300a, 300b, 300c, 30od 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 1210b (as in Fig. 12), 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, 300b, 300c, 30od to perform a set of operations, or steps, S202- S2o6b, 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 client node 300a, 300b, 300c, 30od 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, 300b, 300c, 30od may further comprise a
  • the communications interface 320 for communications with other entities, nodes, and devices of the group communications system 100 and particularly the control node 200.
  • the communications interface 320 may comprise one or more transmitters and receivers, comprising analogue and digital components.
  • the processing circuitry 310 controls the general operation of the client node 300a, 300b, 300c, 30od 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, 300b, 300c, 30od are omitted in order not to obscure the concepts presented herein.
  • Fig. 11 schematically illustrates, in terms of a number of functional modules, the components of a client node 300a, 300b, 300c, 30od according to an embodiment.
  • the client node 300a, 300b, 300c, 30od of Fig. 11 comprises an obtain module 310a configured to perform step S202.
  • the client node 300a, 300b, 300c, 30od of Fig. 11 may further comprise a number of optional functional modules, such as any of a provide module 310b configured to perform step S204, a first receive module 310c configured to perform step S2o6a, and a second receive module 3iod configured to perform step S2o6b.
  • each functional module 3ioa-3iod may be implemented in hardware or in software.
  • one or more or all functional modules 3ioa-3iod may be implemented by the processing circuitry 310, 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 3ioa-3iod and to execute these instructions, thereby performing any steps of the client node 300a, 300b, 300c, 30od as disclosed herein.
  • the client node 300a, 300b, 300c, 30od may be provided as a standalone device or as a part of at least one further device.
  • the client node 300a, 300b, 300c, 30od may be provided in a wireless device 160a, 160b, 160c, i6od.
  • Fig. 12 shows one example of a computer program product 1210a, 1210b comprising computer readable means 1230.
  • a computer program 1220a can be stored, which computer program 1220a 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 1220a and/or computer program product 1210a may thus provide means for performing any steps of the control node 200 as herein disclosed.
  • a computer program 1220b can be stored, which computer program 1220b 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 1220b and/or computer program product 1210b may thus provide means for performing any steps of the client node 300a, 300b, 300c, 30od as herein disclosed.
  • the computer program product 1210a, 1210b 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 1210a, 1210b 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 1220a, 1220b is here schematically shown as a track on the depicted optical disk, the computer program 1220a,

Landscapes

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

Abstract

L'invention concerne des mécanismes de gestion de porteuse MBMS dans un système de communications de groupe. Un procédé est mis en œuvre par un nœud de commande. Le procédé comprend l'activation d'une seconde porteuse MBMS à l'aide d'une transmission SC-PTM dans le système de communications de groupe en cas de besoin. Le procédé consiste à annoncer la seconde porteuse MBMS sur une première porteuse MBMS déjà activée et annoncée à des nœuds clients du système de communications de groupe.
PCT/EP2017/057049 2017-03-24 2017-03-24 Gestion de porteuse mbms dans un système de communications de groupe WO2018171892A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/EP2017/057049 WO2018171892A1 (fr) 2017-03-24 2017-03-24 Gestion de porteuse mbms dans un système de communications de groupe

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2017/057049 WO2018171892A1 (fr) 2017-03-24 2017-03-24 Gestion de porteuse mbms dans un système de communications de groupe

Publications (1)

Publication Number Publication Date
WO2018171892A1 true WO2018171892A1 (fr) 2018-09-27

Family

ID=58461283

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2017/057049 WO2018171892A1 (fr) 2017-03-24 2017-03-24 Gestion de porteuse mbms dans un système de communications de groupe

Country Status (1)

Country Link
WO (1) WO2018171892A1 (fr)

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Common functional architecture to support mission critical services; Stage 2 (Release 14)", 3GPP STANDARD; 3GPP TS 23.280, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG6, no. V14.1.0, 16 March 2017 (2017-03-16), pages 1 - 141, XP051290517 *
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on Multimedia Broadcast and Multicast Service (MBMS) usage for mission critical communication services (Release 14)", 3GPP STANDARD; 3GPP TR 23.780, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG6, no. V14.0.0, 19 December 2016 (2016-12-19), pages 1 - 93, XP051230179 *

Similar Documents

Publication Publication Date Title
US9936504B2 (en) Multimedia broadcast multicast service (MBMS) frequency prioritization
JP2015500578A (ja) マルチメディア・ブロードキャスト・マルチキャスト・サービス（ｍｂｍｓ）アイドルモードカウント手順
US20210127235A1 (en) Mbms bearer setup in a group communications system
EP4072170A1 (fr) Procédé de gestion de porteuses de diffusion et dispositif correspondant
US20210044938A1 (en) Mbms bearer handling in a group communications system
EP3453193B1 (fr) Établissement d'appel de groupe dans un système de communication de groupe
US20220295236A1 (en) Method and apparatus for transmitting and receiving data in wireless communication system
US11026056B2 (en) MBMS bearer handling
US20190104499A1 (en) Paging of a client node in a group communications system
US11140656B2 (en) Paging in a group communications system
WO2018171892A1 (fr) Gestion de porteuse mbms dans un système de communications de groupe
CN116325817A (zh) 用于无线电通信的方法和装置
US20180302756A1 (en) Group Metadata In A Group Communications System

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

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

Country of ref document: EP

Kind code of ref document: A1