[go: up one dir, main page]

WO2018058692A1 - 一种广播承载管理的方法及其设备 - Google Patents

一种广播承载管理的方法及其设备 Download PDF

Info

Publication number
WO2018058692A1
WO2018058692A1 PCT/CN2016/101417 CN2016101417W WO2018058692A1 WO 2018058692 A1 WO2018058692 A1 WO 2018058692A1 CN 2016101417 W CN2016101417 W CN 2016101417W WO 2018058692 A1 WO2018058692 A1 WO 2018058692A1
Authority
WO
WIPO (PCT)
Prior art keywords
broadcast
broadcast bearer
bearer
service
message
Prior art date
Application number
PCT/CN2016/101417
Other languages
English (en)
French (fr)
Inventor
杨艳梅
葛翠丽
吴义壮
Original Assignee
华为技术有限公司
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 华为技术有限公司 filed Critical 华为技术有限公司
Priority to CN201680089442.5A priority Critical patent/CN109716798B/zh
Priority to PCT/CN2016/101417 priority patent/WO2018058692A1/zh
Priority to EP16917442.2A priority patent/EP3512222B1/en
Priority to CN202011617653.6A priority patent/CN113163347B/zh
Priority to EP22161501.6A priority patent/EP4072170B1/en
Publication of WO2018058692A1 publication Critical patent/WO2018058692A1/zh
Priority to US16/371,778 priority patent/US10757542B2/en
Priority to US16/988,177 priority patent/US11337040B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H04W4/10—Push-to-Talk [PTT] or Push-On-Call services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H04W4/08—User group management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02—Services making use of location information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/12—Messaging; Mailboxes; Announcements
    • 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
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • 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

Definitions

  • the present invention relates to the field of communication networks, and in particular, to a multimedia broadcast/multicast service (MBMS) bearer management method and device thereof.
  • MBMS multimedia broadcast/multicast service
  • the Mission Critical Push-to-talk (MCPTT) system supports two media transmission modes: Unicast bearer transmission and MBMS bearer. transmission.
  • MCPTT Group Communication System Enablers for LTE (GCSE_LTE) network structure, as shown in FIG.
  • the emergency critical service server (MCS server) is an instance of the GCS AS, and implements management and use of the broadcast bearer.
  • the existing MCPTT server is a type of MCS server, which integrates the functions of the Group Communication System Application Server (GCS AS), as shown in FIG. 2, and FIG. 2 shows the MCPTT network architecture and function model.
  • GCS AS Group Communication System Application Server
  • the broadcast bearer service is an underlying transport service that is independent of the specific application layer service.
  • the GCS AS function for managing and using the broadcast bearer service is bound to the application layer service server, such as the MCPTT server, so that every new service that needs to use the broadcast bearer service is introduced.
  • the need to re-implement the GCS AS function, resulting in the duplication and coupling of the entire public safety network architecture function, is also not conducive to the rapid deployment of new services.
  • the same broadcast bearer transmission cannot be guaranteed for each service of the same group because the servers are deployed separately.
  • FIG. 3 is a flow chart of a method for pre-establishing a broadcast bearer based on the MCPTT architecture.
  • 4 is a flow chart of a method for dynamically establishing a broadcast bearer based on an MCPTT architecture.
  • the activation, management, and call control of the broadcast bearer are tightly coupled in the MCPTT server, which may result in a broadcast bearer.
  • the efficiency of resource usage is relatively low; multiple MCPTT servers can be served in one MCPTT system, and the MCPTT server (or GCS AS) needs to decide whether to use broadcast according to the group member in the group call.
  • Bearer in the existing MCPTT architecture, each MCPTT server is independent of the management and use of broadcast bearers, and lacks a system-level centralized broadcast bearer control node.
  • the invention provides a broadcast bearer management method and a device thereof, which realize decoupling of a broadcast bearer management function and an application service layer control function. .
  • an embodiment of the present invention provides a method for managing broadcast bearers, where the method includes:
  • the first bearer management server BMS receives the first message sent by the service server, where the first message includes the group identifier of the service group;
  • the first BMS sends a second message to the service server, where the second message carries the first broadcast bearer.
  • User face information User face information.
  • the message is sent to the service server, so that the service server can use the broadcast bearer to transmit data for the group, and the decoupling between the broadcast bearer management function and the application service layer control function is realized, and the management of the broadcast bearer is compared with the prior art.
  • the use of centralized control on one control point completes the centralized scheduling of broadcast bearers.
  • the first BMS sends the transmission mode indication information to the service server, which may also be referred to as indication information.
  • the name of the indication information is used for limiting, and the indication information is used to indicate that the service server transmits data to the service group by using the transmission mode determined by the first BMS.
  • the transmission mode indication information is used to indicate that the service server uses the broadcast transmission mode for the service group, or
  • the transmission mode indication information is used to indicate that the service server uses the broadcast transmission mode or uses the unicast transmission mode for all members or some members of the service group; or
  • the transmission mode indication information is used to indicate that the service server switches the service group from the unicast transmission mode to the broadcast transmission mode, or switches from the broadcast transmission mode to the unicast transmission mode, or uses only the unicast transmission mode, or uses only the broadcast transmission mode. , or stop using unicast transmission, or stop using broadcast transmission mode.
  • the second message includes the transmission mode indication information.
  • the first BMS determines, according to the first message, the first broadcast bearer for the service group, including:
  • the first BMS determines the first broadcast bearer for the service group according to the first message and the receiving state information of the at least one broadcast bearer sent by the at least one terminal.
  • the first message further includes service description information
  • the first BMS sends the at least one message according to the first message and the at least one terminal
  • the receiving status information of a broadcast bearer determines the first broadcast bearer for the service group, including:
  • the at least one broadcast bearer satisfies the service description information, and the receiving state information of the at least one broadcast bearer sent by the at least one terminal satisfies the first preset condition, determining the first broadcast bearer for the service group.
  • the first BMS determines, according to the first message, the first broadcast bearer for the service group, including:
  • the first BMS establishes a first broadcast bearer according to the first message
  • the first BMS sends a broadcast bearer notification message to the at least one terminal, where the broadcast bearer notification message carries the bearer information of the first broadcast bearer;
  • the method before the first BMS establishes the first broadcast bearer according to the first message, the method further includes:
  • the first BMS performs to establish the first broadcast bearer according to the first message.
  • the first message includes the service description information
  • the first BMS establishes the first broadcast bearer according to the first message, including:
  • the first BMS performs the first message according to the first message. Establish a first broadcast bearer.
  • the first BMS establishes the first broadcast bearer according to the first message, including:
  • the first BMS acquires location information of the terminal in the service group
  • the first BMS establishes a first broadcast bearer according to the service description information and the location information of the terminal in the service group.
  • the first BMS obtains the location information of the terminal in the service group, including:
  • the first BMS acquires location information of the terminal in the service group from at least one of the service server, the group management server, the terminal location management server, and the second BMS; or
  • the first BMS receives location information sent by the terminal in the service group.
  • the method further includes:
  • the first BMS sends a broadcast bearer synchronization message to the second BMS, where the broadcast bearer synchronization message includes bearer information and user plane information of the first broadcast bearer.
  • the broadcast synchronization message may also include a group identity.
  • the method further includes:
  • the first BMS sends a third message to the service server, where the third message carries the identifier of the terminal, and the third message is used to request the service server to use the unicast bearer. Send media data to the terminal.
  • an embodiment of the present invention provides a device for managing broadcast bearers, where the device includes:
  • a receiving unit configured to receive a first message sent by the service server, where the first message includes a group identifier of the service group;
  • a determining unit configured to determine, according to the first message, a first broadcast bearer for the service group
  • a sending unit configured to send a second message to the service server, where the second message carries user plane information of the first broadcast bearer.
  • the message is sent to the service server, so that the service server can use the broadcast bearer to transmit data for the group, and the decoupling between the broadcast bearer management function and the application service layer control function is realized, and the management of the broadcast bearer is compared with the prior art.
  • the use of centralized control on one control point completes the centralized scheduling of broadcast bearers.
  • the first BMS sends the transmission mode indication information to the service server, which may also be referred to as indication information.
  • the name of the indication information is not limited, and the indication information is used to instruct the service server to transmit data to the service group by using the transmission mode determined by the first BMS.
  • the transmission mode indication information is used to indicate that the service server uses the broadcast transmission mode for the service group, or
  • the transmission mode indication information is used to indicate that the service server uses the broadcast transmission mode or uses the unicast transmission mode for all members or some members of the service group; or
  • the transmission mode indication information is used to indicate that the service server switches the service group from the unicast transmission mode to the broadcast transmission mode, or switches from the broadcast transmission mode to the unicast transmission mode, or uses only the unicast transmission mode, or uses only the broadcast transmission mode. , or stop using unicast transmission, or stop using broadcast transmission mode.
  • the second message includes transmission mode indication information.
  • the device further includes an acquiring unit,
  • an obtaining unit configured to acquire, by the at least one terminal, the receiving status information of the at least one broadcast bearer
  • the determining unit is configured to determine, according to the first message and the receiving state information of the at least one broadcast bearer sent by the at least one terminal, the first broadcast bearer for the service group.
  • the determining unit is specifically configured to:
  • the at least one broadcast bearer satisfies the service description information, and the receiving state information of the at least one broadcast bearer sent by the at least one terminal satisfies the first preset condition, determining the first broadcast bearer for the service group.
  • the device further includes an establishing unit,
  • the sending unit is further configured to send a broadcast bearer notification message to the at least one terminal, where the broadcast bearer notification message carries the bearer information of the first broadcast bearer;
  • the receiving unit is further configured to receive, by the at least one terminal, receiving state information of the first broadcast bearer
  • the determining unit is specifically configured to: if the receiving state information of the first broadcast bearer sent by the at least one terminal meets the first preset condition, determine the first broadcast bearer for the service group.
  • the device further includes an acquiring unit,
  • an obtaining unit configured to acquire, by the at least one terminal, the receiving status information of the at least one broadcast bearer
  • the establishing unit establishes the first broadcast bearer according to the first message.
  • the first message includes service description information
  • the establishing unit is specifically configured to:
  • the first broadcast bearer is established according to the first message.
  • the acquiring unit is further configured to acquire location information of the terminal in the service group;
  • the establishing unit is specifically configured to establish a first broadcast bearer according to the service description information and the location information of the terminal in the service group.
  • the obtaining unit is specifically configured to: obtain, by using at least one of the service server, the group management server, the terminal location management server, and the second BMS, location information of the terminal in the service group; or
  • the sending unit is further configured to send a broadcast bearer synchronization message to the second BMS, where the broadcast bearer synchronization message includes bearer information and user plane information of the first broadcast bearer.
  • the broadcast bearer synchronization message also includes a group identity.
  • the receiving unit is further configured to receive the receiving state information of the first broadcast bearer sent by the terminal in the service group;
  • the sending unit is further configured to send a third message to the service server, where the third message carries the identifier of the terminal, and the third message is used to request the service server to use the single The broadcast bearer sends media data to the terminal.
  • an embodiment of the present invention provides a device for managing broadcast bearers.
  • the device includes a processor and a memory.
  • the memory is used to store programs.
  • the program in the processor running memory is used,
  • an embodiment of the present invention provides a computer storage medium for storing computer software instructions, and the computer runs the instruction for:
  • the method and device for broadcast bearer management by receiving a first message sent by a service server, and determining, according to the group identifier of the service group included in the first message, a broadcast that can be used for the service group.
  • the bearer carries the determined user plane information of the broadcast bearer in the second message and sends the information to the service server, so that the service server can use the broadcast bearer to transmit data for the group, and implements the broadcast bearer management function and the application service layer control. Decoupling of functions, while centralizing the management and use of broadcast bearers on one control point relative to the prior art, completes centralized scheduling of broadcast bearers.
  • 1 is a network architecture of a MCPTT service based on GCSE_LTE in the prior art
  • FIG. 2 is a schematic diagram of a MCPTT network architecture and function model in the prior art
  • FIG. 3 is a flowchart of a method for pre-establishing a broadcast bearer based on an MCPTT architecture
  • FIG. 4 is a flowchart of a method for dynamically establishing a broadcast bearer based on an MCPTT architecture
  • FIG. 5 is a network architecture of separating broadcast bearer management from application service control according to an embodiment of the present disclosure
  • FIG. 6 is a network architecture of another separation of broadcast bearer management and application service control according to an embodiment of the present invention.
  • FIG. 7 is a device for managing broadcast bearer according to an embodiment of the present invention.
  • FIG. 8 is a flowchart of a method for managing broadcast bearer according to an embodiment of the present invention.
  • FIG. 9 is a flowchart of another method for managing broadcast bearers according to an embodiment of the present invention.
  • FIG. 10 is a flowchart of still another method for managing broadcast bearers according to an embodiment of the present invention.
  • FIG. 11 is a flowchart of still another method for MBS bearer management according to an embodiment of the present invention.
  • FIG. 12 is a flowchart of still another method for managing a broadcast bearer according to an embodiment of the present invention.
  • FIG. 13 is a flowchart of still another method for MBS bearer management according to an embodiment of the present invention.
  • FIG. 14 is a flowchart of still another method for managing a broadcast bearer according to an embodiment of the present invention.
  • FIG. 15 is a flowchart of still another method for managing broadcast bearers according to an embodiment of the present invention.
  • FIG. 16 is a flowchart of still another method for broadcast bearer management according to an embodiment of the present invention.
  • FIG. 17 is a schematic structural diagram of a broadcast bearer management device according to an embodiment of the present invention.
  • the embodiment of the present invention provides a broadcast bearer management method and a device thereof, which are applicable to an Emergency Critical Service System architecture, such as MCPTT, MCVID, MCDATA, etc.
  • An Emergency Critical Service System architecture such as MCPTT, MCVID, MCDATA, etc.
  • the architecture of the system is shown in FIG. 5 and FIG. 6 . Shown.
  • FIG. 5 is a network architecture for separating broadcast bearer management from application service control.
  • BMS Bearer Management Server
  • MC Service server Mission Critical Service Server
  • CSC-N1 emergency mission service
  • emergency mission service uses The interface CSC-N2 between the MC Service UE and the bearer management server, the interface CSC-N3 between the group management server and the bearer management server, and the bearer between the management server and the bearer management server Interface CSC-N4.
  • the control plane MB2-C and the user plane MB2-U interface from the emergency call server (MCPTT server) are replaced by the bearer management server BMS.
  • Figure 6 The main difference between Figure 6 and Figure 5 is whether the user plane (MB2-U) of the broadcast bearer moves down. As shown in FIG. 6, only the control panel MB2-C of the broadcast bearer moves down, and the user plane MB2-U does not change.
  • the emergency task service server MC Service Server is mainly responsible for call control and media control, and is a logical entity.
  • the MC Service Server may be an MCPTT server, an MCVideo server, or an MCData server.
  • the emergency task service user equipment MC Service UE may also be referred to as a Mission Critical Service Client (MC Service Client).
  • the MC Service UE is an application layer entity that is equivalent to the MC Service server and is mainly used to handle the processing of application layer transactions.
  • the bearer management server BMS is mainly responsible for activation, handover, and centralized scheduling of broadcast bearers.
  • the location information and the broadcast bearer receiving status information reported by the MC service UE may be received.
  • FIG. 7 is a device for managing broadcast bearer according to an embodiment of the present invention.
  • the device may be a bearer management server BMS.
  • the broadcast bearer managed device 100 includes a receiver 110, a transmitter 120, a memory 130, a processor 140, a communication interface 150, and a communication bus 160.
  • the receiver 110, the transmitter 120, the memory 130, the processor 140, the communication interface 150, and the communication bus 160 are connected to complete communication with each other.
  • the receiver 110 is configured to receive, by the communication interface 150, data sent by a service server (for example, an MC Sservice Sserver) and other devices such as a terminal.
  • Transmitter 120 for communicating through a communication interface 150 transmits data to a service server (for example, an MC service server) and other devices, such as a terminal, wherein the processor 140 and the transmitter 120 can implement the following embodiment and the service server shown in FIG. 8 to FIG. And the interaction of data between terminals.
  • the memory 130 is used to store instructions and data.
  • the processor 140 is configured to invoke an instruction in the memory 130 for performing the steps performed by the first bearer management server BMS in the embodiment shown in FIGS. 8 to 16 described below.
  • the processor 140 may be a central processing unit (CPU), and the processor 330 may be another general-purpose processor or a digital signal processor (Digital Signal Processor). , DSP), Application Specific Integrated Circuit (ASIC), Field-Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, etc.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the communication bus 160 may include a power bus, a control bus, a status signal bus, and the like in addition to the data bus. However, for clarity of description, various buses are labeled as communication bus 160 in the figure.
  • Memory 130 can include read only memory and random access memory and provides instructions and data to processor 140. A portion of the memory may also include a non-volatile random access memory.
  • the terminal involved in the present invention may be an MC service client in the emergency mission service system. This is only an example for explaining the technical solution of the embodiment of the present invention, and does not constitute any limitation on the embodiment of the present invention. .
  • FIG. 8 is a flowchart of a method for managing broadcast bearer according to an embodiment of the present invention.
  • the execution body of the method may be the device 100 for broadcast bearer management shown in FIG.
  • the method 200 can include the following steps:
  • the first bearer management server BMS receives the first message sent by the service server, where A message includes a group identity of a service group.
  • a network system separated from broadcast application management and application service control may include one or more bearer management server BMSs.
  • the first BMS can be one or more BMSs.
  • the first message is used to trigger the BMS to determine the available broadcast bearers for the service group (or group).
  • the first message may be referred to as a broadcast bearer request message, to request the BMS to determine an available broadcast bearer for the service group, or to determine that there is a broadcast bearer that can be used for the service group, so as to facilitate the service server.
  • the available broadcast bearers provided by the BMS transmit data for terminals in the group.
  • the transmitted data may be media plane data or media plane signaling messages.
  • the first message may be used as the other name message, and the broadcast bearer that is determined to be used by the BMS indication is determined.
  • the first BMS determines, according to the first message, a first broadcast bearer for the service group.
  • one or more broadcast bearers may be pre-established before the service group performs group communication, and each broadcast bearer corresponds to a specific service area, and each broadcast bearer has The unique identifier may be a Temporary Mobile Group Identity (TMGI), and each broadcast bearer has service description information corresponding to the broadcast bearer, and the service description information may include a quality of service (QoS);
  • TMGI Temporary Mobile Group Identity
  • QoS quality of service
  • the bearer information of the broadcast bearer includes TMGI, radio frequency, broadcast service area, user plane information, and the IP address and port number of the user plane BM-SC of the broadcast bearer.
  • the BMS when the BMS has an available broadcast bearer that satisfies the service group in the stored one or more broadcast bearers, it is determined that the broadcast bearer is a broadcast bearer available to the service group.
  • the broadcast bearer stored in the BMS may be pre-established by the BMS, or may be obtained and saved from other BMSs.
  • the BMS may establish a broadcast bearer for the service group to determine whether the established broadcast bearer is a broadcast bearer that can be used by the service group.
  • the established broadcast bearer is a broadcast bearer that can be used by the call group, it is determined that the established broadcast bearer is a broadcast bearer used by the service group.
  • the communication of the foregoing service group may use other transmission modes for data transmission, for example, a unicast bearer for data transmission.
  • the first BMS sends a second message to the service server, where the second message carries user plane information of the first broadcast bearer.
  • the second message is used to notify the service server which broadcast bearer the data group can use to transmit data.
  • the second message may be referred to as a broadcast bearer binding message.
  • the user plane information of the first broadcast bearer may be an IP address and a port number of a Broadcast Multicast-Service Centre (BM-SC). If the service server transmits data using the first broadcast bearer, the service server sends the data to the IP address and port number of the BM-SC corresponding to the first broadcast bearer.
  • BM-SC Broadcast Multicast-Service Centre
  • the broadcast bearer management method determines the broadcast bearer that can be used for the service group by receiving the first message sent by the service server and according to the group identifier of the service group included in the first message. And the user plane information of the broadcast bearer is carried in the second message and sent to the service server, so that the service server obtains the data of the group communication that can use the broadcast bearer transmission service group, and implements the broadcast bearer management function and the application service. Decoupling of layer control functions, while centralizing the management and use of broadcast bearers on one control point relative to the prior art, completes centralized scheduling of broadcast bearers.
  • the first message may include a group identifier of multiple service groups, that is, one service server may simultaneously request broadcast bearers for multiple service groups, and the BMS may use each method 200 according to FIG.
  • the call group determines if an available broadcast bearer can be provided.
  • the foregoing method further includes:
  • the first BMS sends the transmission mode indication information to the service server.
  • the S231 may be implemented in step S230 or may be implemented after or before S230, and the present invention is not limited thereto.
  • the transmission mode indication information may be used to indicate that the service server uses a broadcast transmission mode for the service group, or
  • the transmission mode indication information may be used to indicate that the service server uses a broadcast transmission mode or a unicast transmission mode for all members or some members of the service group; or
  • the transmission mode indication information may be used to indicate that the service server switches the unicast transmission mode to a broadcast transmission mode, or switches from a broadcast transmission mode to a unicast transmission mode, or only uses a unicast transmission mode. , or use only the broadcast transmission mode, or stop using the unicast transmission method, or stop using the broadcast transmission mode.
  • the transmission mode indication information may be a display indicating which transmission mode the service server uses for the service group, such as the display indication uses the unicast transmission mode, or the display indication uses the broadcast transmission mode. It may also implicitly indicate which transmission mode the service server uses for the service group, such as not using or stopping the unicast transmission mode, and not using or stopping the use of the broadcast mode.
  • the transmission mode indication information may be an independent message, and specifically, the name of the message or the type of the message may be configured to function as the foregoing transmission mode indication information.
  • the second message may be the above transmission mode indication information.
  • the service server transmits the data to the terminal of the service group by using the broadcast bearer determined by the BMS.
  • the transmission mode indication information may be one of the cells in the message.
  • unicast transmission enable/disable broadcast transmission mode enable/disable. It is assumed that the transmission mode indication information is a broadcast transmission mode enabling cell, and the broadcast transmission mode enabling cell can be placed in the second message to be sent to the service server, or can be sent to the service server in other messages, and further, the service server After receiving the transmission mode indication information, the broadcast bearer determined by the BMS is used to transmit data to the terminal of the service group.
  • the cell may be the user plane information of the first broadcast bearer.
  • the service server uses the first broadcast bearer determined by the BMS to transmit data to the terminal of the service group.
  • the transmission mode indication information when used to indicate that the service server uses a broadcast transmission mode or a unicast transmission mode for some members of the service group, the transmission mode indication information may further include a partial terminal of the service group. List. If the object used by the broadcast transmission mode or the unicast transmission mode is a part of the terminal of the service group, then the transmission mode indication information further includes a list including one or more terminals in the service group, indicating the service server in the list. The terminal uses a broadcast transmission mode or a unicast transmission mode.
  • the transmission mode indication information may include the user plane information of the first broadcast bearer and the terminal list, and after receiving the user plane information and the terminal list of the first broadcast bearer, the service server uses the unicast bearer transmission for the terminal in the terminal list. , using broadcast bearer transmission for only his business group.
  • the broadcast transmission mode may be referred to as a broadcast bearer mode
  • the unicast transmission mode may be referred to as a broadcast bearer mode
  • the transmission mode indication information when used to indicate that the service server uses a broadcast transmission mode or uses a unicast transmission mode for all members in the service group, the transmission mode indication information may also be The list includes all the terminals in the service group, for example, the identifier list. Obviously, the transmission mode indication information may also not carry the terminal identifier, and is used to imply all terminals of the service group.
  • the first BMS determines, according to the first message, a first broadcast bearer for the service group, including:
  • the first BMS acquires receiving state information of the at least one broadcast bearer sent by the at least one terminal.
  • the BMS After the BMS obtains the broadcast bearer from other BMSs and saves it, the BMS broadcasts the bearer information of the broadcast bearer to the at least one terminal, and the terminals may come from the BMS system or all BMS systems, or a specific physical location. Area, or a specific broadcast service area, The terminal that receives the bearer information of the broadcast bearer monitors the channel quality of the broadcast bearer, determines whether the data can be received on the broadcast bearer, and sends the received status information of the broadcast bearer to the BMS.
  • the BMS receives reception status information received by one or more pre-established broadcast bearers transmitted by at least one terminal.
  • the BMS obtains the receiving state information of the at least one broadcast bearer sent by the at least one terminal before the BMS receives the first message sent by the service server, that is, before S210.
  • the receiving status information of the broadcast bearer received by the BMS is a status indication. If it can be received, it cannot be received. If it is listening, there is no monitoring; such as “good” and “not good”, etc. Received, "listening”, “good” means that the channel quality of the broadcast bearer meets the preset threshold, and the user can receive data on the broadcast bearer; “not good” means that the signal quality of the broadcast bearer does not meet the preset threshold. The user is not able to receive data on the broadcast bearer.
  • the terminal determines whether it can receive the data of the broadcast bearer.
  • the terminal does not depend on the service server to transmit data on the broadcast bearer.
  • the terminal can make a judgment by using the periodic scheduling information on the broadcast bearer, where the scheduling information is not sent by the service server.
  • the terminal may also be determined by other methods, which are not limited in the present invention.
  • the first BMS determines a first broadcast bearer for the service group according to the first message and the receiving state information of the at least one broadcast bearer sent by the at least one terminal.
  • the first message may further include service description information, where the service description information may be quality of service QoS information.
  • the determining, by the first BMS, the first broadcast bearer for the service group according to the first message and the receiving state information of the at least one broadcast bearer sent by the at least one terminal, may include:
  • the first BMS After receiving the receiving status information of the at least one broadcast bearer sent by the at least one terminal, the first BMS performs statistics, and for each broadcast bearer, each group sends a broadcast indicating that the broadcast bearer data can be received (for example, “can receive "or "monitoring” or "good”, etc.) statistics.
  • the number of statistics which can be a percentage of all terminals in the group.
  • the statistics for one implementation are shown in the following table.
  • the BMS now receives the reception status of three broadcast bearers reported by multiple terminals.
  • At least one broadcast bearer, and the terminal that cannot receive the broadcast bearer data in each group may be counted, or both of them perform statistics, which is not limited by the present invention.
  • the first preset condition is a policy condition configured by the service provider. For example, when the number of group terminals that receive a certain broadcast bearer reaches N or reaches M%, the broadcast bearer is determined to be the first broadcast bearer.
  • These policy conditions may also include other conditions for determining the first broadcast bearer, which are not limited by the present invention.
  • the first BMS is configured according to the first Determine the first broadcast bearer for the service group, including:
  • the first BMS establishes a first broadcast bearer according to the first message.
  • the BMS When the BMS receives the first message sent by the service server, it determines whether a broadcast bearer is available for the service group corresponding to the group identifier of the service group carried in the first message. When a pre-established broadcast bearer is stored in the BMS, the BMS determines whether there is a broadcast bearer available for the service group in the stored broadcast bearer.
  • the broadcast bearer stored in the BMS can be obtained from other BMSs.
  • the BMS When the BMS determines that the broadcast bearer that is used by the service group does not exist in the stored broadcast bearer according to the group identifier of the service group, the BMS newly establishes a broadcast bearer (the first broadcast bearer) for the service group. And store the information of the newly established broadcast bearer.
  • the newly established broadcast bearer information includes bearer information of the broadcast bearer, service description information of the broadcast bearer, and user plane information of the broadcast bearer.
  • the bearer information of the broadcast bearer includes a Temporary Mobile Group Identity (TMGI) for uniquely identifying the broadcast bearer, and may further include: a radio frequency and an MBMS service area identifier; the service description information of the newly established broadcast bearer includes Information such as QoS; user plane information of the newly established broadcast bearer includes the BM-SC IP address and port number of the user plane.
  • TMGI Temporary Mobile Group Identity
  • the method before the first BMS establishes the first broadcast bearer according to the first message, the method further includes:
  • the first BMS performs the establishing according to the first message.
  • the first broadcast bearer Obtaining, by the first BMS, the receiving state information of the at least one broadcast bearer sent by the at least one terminal; if the receiving state information of the at least one broadcast bearer sent by the at least one terminal does not satisfy the first preset condition, the first BMS performs the establishing according to the first message.
  • the first broadcast bearer Obtaining, by the first BMS, the receiving state information of the at least one broadcast bearer sent by the at least one terminal; if the receiving state information of the at least one broadcast bearer sent by the at least one terminal does not satisfy the first preset condition, the first BMS performs the establishing according to the first message.
  • the first broadcast bearer Obtaining, by the first BMS, the receiving state information of the at least one broadcast bearer sent by the at least one terminal; if the receiving state information of the at least one broadcast bearer sent by the at least one terminal does not satisfy the first preset condition, the first BMS performs the
  • the at least one broadcast bearer may be one or more broadcast bearers stored in the BMS. Obtaining, by the BMS, the receiving status information of the at least one broadcast bearer sent by the at least one terminal, where the BMS broadcasts the bearer information and the user plane information of the one or more broadcast bearers that are stored by the BMS, where the one or more terminals may be in the first message.
  • the carried group ID identifies the terminal in the service group
  • the BMS corresponds to all terminals in the system, or all BMS corresponds to all terminals in the system, Or a terminal located in a specific physical location area, or a terminal located in a specific broadcast service area
  • the terminal receiving the broadcast message listens to the received broadcast status of the received status information of at least one broadcast bearer, and determines whether it can be received on the broadcast bearer. Data, and the received status information of the received at least one broadcast bearer is sent to the BMS.
  • the description of the receiving status information of the broadcast bearer is the same as the broadcast bearer receiving status information in S221.
  • the description after the BMS receives the reception status information of the at least one broadcast bearer sent by the at least one terminal is the same as the description in S222.
  • the BMS receives the first preset condition that the receiving status information of the at least one broadcast bearer that is sent by the at least one terminal meets or does not satisfy the first preset condition, and may be a service group.
  • the number of terminals in which the receiving terminal receives the receiving status information of a certain broadcast bearer is “good”, and may also be other conditions.
  • the first message includes service description information
  • the first BMS establishes the first broadcast bearer according to the first message, and may include:
  • the first BMS performs to establish the first broadcast bearer according to the first message.
  • the BMS When the service description information of the broadcast bearer stored in the BMS does not meet the service description information required by the service group carried in the first message, the BMS newly establishes a broadcast bearer for the service group, and stores the bearer information of the newly established broadcast bearer. And user face information.
  • the first BMS establishes the first broadcast bearer according to the first message, and may include:
  • the first BMS obtains location information of the terminal in the service group.
  • the first BMS establishes a first broadcast bearer according to the service description information and the location information of the terminal in the service group.
  • the BMS obtains location information of the terminal in the service group, including:
  • the first BMS can manage services from the service server, the group management server, and the terminal location.
  • the location information of the terminal in the service group is obtained from at least one of the server and the second BMS.
  • the location information of the terminal in the BMS acquisition group may be obtained before the BMS receives the first message sent by the service server or before any new broadcast bearer is established.
  • the BMS may further receive location information sent by the terminal in the service group, to obtain location information of the terminal in the service group.
  • the BMS may obtain the group identity of the service group from the first message, and determine which service group finds the available broadcast bearer.
  • the BMS may acquire information of the group and members (eg, terminals) in the group from the group management server GMS before establishing a new broadcast bearer.
  • the group information of the group in the service group carried in the first message may be obtained according to the information of the group and the group member.
  • the BMS After the BMS obtains the location information of the terminal in the service group, the BMS can newly establish a broadcast bearer according to the service description information and the location information of the terminal.
  • the first BMS sends a broadcast bearer notification message to the terminal, where the broadcast bearer notification message carries the bearer information of the first broadcast bearer.
  • the BMS sends the bearer information of the newly established broadcast bearer to all the terminals in the service group, so that the terminal that receives the bearer information of the broadcast bearer monitors the newly established broadcast bearer, and determines whether the data can be received on the broadcast bearer. And sending the receiving status information of the broadcast bearer to the BMS.
  • the description of the reception state regarding the broadcast bearer is the same as that described in step S221.
  • the bearer information of the newly established broadcast bearer is carried in the broadcast bearer notification message and broadcasted to all the terminals in the service group.
  • the newly established broadcast bearer is The bearer message may also be carried in the other information to be broadcast to the terminal in the service group.
  • the name of the message for newly broadcasting the bearer information of the broadcast bearer is not limited in the embodiment of the present invention.
  • the first BMS receives the receiving status information of the first broadcast bearer sent by the at least one terminal. This information can also be sent at any time after S250. The information may also be sent multiple times, each time the status of the receiving broadcast bearer changes, that is, from "can receive” to "cannot receive", or from "cannot receive” to “can receive” , the receiving status information is sent to the BMS.
  • the description about the broadcast bearer receiving state information is the same as that in S221, and the description about the at least one broadcast bearer receiving state information sent by the BMS to the at least one terminal is the same as that in S222, and the description of the first preset condition is related to S222. description
  • the service group uses other bearers to transmit data, such as using unicast bearer transmission.
  • the pre-established broadcast bearer and the broadcast bearer just established in S240 exist in the system.
  • the service server uses the unicast bearer to transmit data to the terminal in the service group.
  • the terminal that receives the bearer information of the at least one broadcast bearer is still listening to the corresponding broadcast bearer.
  • the terminal sends the receiving status information of the broadcast bearer to the BMS.
  • the BMS determines a first broadcast bearer for the service group according to the service group identifier in the first message and the received state information of the at least one broadcast bearer sent by the at least one terminal, and sends a second message to the service server, and second The description of the message is related to the description of S230.
  • the service server may use the first broadcast bearer determined by the BMS to transmit data. If the service server starts to use the first broadcast bearer to transmit data after receiving the second message, the terminal or part of the terminal in the group may be simultaneously transmitted by the unicast bearer and the broadcast bearer.
  • the service server may stop the unicast bearer transmission data, and only use the broadcast bearer to transmit data according to a pre-configured policy, for example, after the specific time at which the same terminal transmits data using the broadcast bearer and the unicast bearer at the same time. Or there are other strategies, and the invention is not limited. Or After receiving the transmission mode indication message of S231, the service server may determine whether to use the broadcast transmission mode or the unicast transmission mode for the terminal in the group according to the transmission mode indication information.
  • the method 200 may further include:
  • the first BMS sends a broadcast bearer synchronization message to the second BMS, where the broadcast bearer synchronization message includes bearer information and user plane information of the first broadcast bearer.
  • the BMS synchronizes the bearer information and the user plane information of the newly established broadcast bearer to other BMSs other than the first BMS.
  • the message identifier is also included in the message.
  • the BMS synchronizes bearer information and user plane information of the newly established broadcast bearer with which service group uses the newly established broadcast bearer information to other BMSs other than the first BMS.
  • the method 200 may further include:
  • the first BMS sends a third message to the service server, where the third message carries the identifier of the terminal, and the third message is used to request the service server to use the single
  • the broadcast bearer sends media data to the terminal.
  • the BMS When the service server uses the broadcast bearer to transmit data to the service group, when the BMS receives the reception status information of the broadcast bearer sent by one or more terminals in the service group is “not good”, the BMS sends the service message to the service server.
  • the third message may be a broadcast bearer switching request message. It should be noted that, in the embodiment of the present invention, the third message may also adopt other names, and the name is not limited.
  • the broadcast bearer request message includes an identifier of the terminal that sends the broadcast status of the broadcast bearer to “not good”.
  • the broadcast bearer switching request message is used to request the service server to use the unicast bearer to send the media data to the terminal corresponding to the identifier of the terminal.
  • the third message may include transmission mode indication information.
  • the third message may be sent multiple times according to the receiving status of the first broadcast bearer of the user.
  • the size of the sequence numbers of the above processes does not mean the order of execution, and the order of execution of each process should be determined by its function and internal logic, and should not be taken to the embodiments of the present invention.
  • the implementation process constitutes any limitation.
  • Controlling the MC server which is a logical entity defined from the perspective of a group call, defines an emergency mission service server of the group, and assumes the main control function in the group call.
  • the location information of the group member and the receiving status information of the broadcast bearer received by the user equipment (UE) side may also be obtained, and the quality report information of the broadcast bearer may also be submitted.
  • UE user equipment
  • the participating MC service server participates in the MC service server registered by the user, and is responsible for routing the request/response sent by the group member in the group call, and routing the server's request message to the group member.
  • the group call can be understood as the service server sending the call of the group corresponding to the group identifier of the service group carried in the first message to the BMS.
  • the first BMS in FIG. 12 to FIG. 15 is a Controlling MC Service server.
  • BMS Controlling MC Service server
  • FIG. 12 is a flowchart of a method for managing broadcast bearer according to an embodiment of the present invention.
  • This embodiment describes notifying the BMS when there is a service group on the Controlling MC Service server, and letting the BMS decide which broadcast bearer to use.
  • Each business group involves a controlling MC service server and at least one participating MC service Server, for the media content of the same service group, all the group members in the same MBMS service area listen to the broadcast bearer corresponding to the same TMGI, that is, only one broadcast bearer is used for the same service group in the MBMS service area.
  • the method 300 can include the following steps:
  • the BMS needs to first obtain group information and group member information, and the like in the group management server GMS. If the BMS has already had a broadcast bearer available before the group session is established, the existing broadcast bearer is activated for use in the group session.
  • the first BMS sends a broadcast bearer notification message to a group member of the group.
  • the BMS carries the stored bearer information of the at least one broadcast bearer in an MBMS bearer announcement message to one or more MC service clients, or terminals.
  • the terminal monitors channel quality of at least one broadcast bearer.
  • the terminal After receiving the at least one broadcast bearer notification message of the BMS broadcast, the terminal stores the bearer information and the user plane information of the at least one broadcast bearer, where the bearer information of the broadcast bearer includes the TMGI, the service area information, and the service description information that uniquely identify the broadcast bearer.
  • the information related to the broadcast bearer The terminal monitors the receiving status of the broadcast bearer received on the corresponding broadcast bearer according to the TMGI, and enters the broadcast bearer service area or has detected in the service area that at least one TMGI corresponding broadcast bearer channel signal is good in quality and can receive data, at least one
  • the reception status information of the broadcast bearer is sent to the BMS, so that the BMS decides whether the broadcast transmission mode can be used for a certain service group.
  • the first BMS receives the receiving status information of the at least one broadcast bearer sent by the terminal.
  • the first BMS receives the reception status information of the at least one broadcast bearer sent by the at least one terminal.
  • the service server sends a broadcast bearer use request message to the BMS.
  • the MC Service server When a service group initiates group communication on an emergency service server (MC Service server), the MC Service server sends a MBMS bearer usage request message to the BMS, where the broadcast bearer request message includes the group.
  • Group ID identifies a service group.
  • the BMS after receiving the broadcast bearer usage message, the BMS returns a MBMS bearer usage response message to the MC Service server, for confirming receipt of the broadcast bearer use request message.
  • the BMS may receive a broadcast bearer use request message corresponding to different service groups sent by one or more controlling MC service servers, or multiple broadcast bearers corresponding to different service groups sent by a controlling MC service server. Use the request.
  • an MBMS bearer usage request message may carry broadcast bearer use request information of multiple service groups, that is, a correspondence between a group ID and a service description information. List.
  • the first BMS obtains a service group according to the broadcast bearer use request message.
  • the BMS determines the service group according to the group identifier carried in the broadcast bearer use request message, and obtains the location information of the group member of the service group and the member of the group according to the relationship between the stored service group and the group member. Information), group membership status (affiliation status) corresponding to the group member, and information about whether the service group has joined the service group.
  • the location information of the BMS acquisition member and the group association status corresponding to the group member may occur after S325, any time before step S330, but whether the group member joins the group can only occur in the group. After S325.
  • the first BMS queries and obtains from the BMS of the other system whether there is an available broadcast bearer that meets the requirements.
  • S335 may also be executed before S325 in the embodiment of the present invention. If it is executed before S325, and the BMS acquires a broadcast bearer to which other BMSs already exist, S350, 355, 365 is performed.
  • the BMS finds that there is no broadcast bearer currently available, the BMS dynamically establishes a new broadcast bearer as needed.
  • the process of dynamically establishing a new broadcast bearer on demand is similar to the execution condition and process in S240 in FIG. No further details are described here, and then S350, S355, and S360 are executed.
  • the first BMS sends a broadcast bearer notification message to the terminal.
  • the BMS sends a broadcast bearer announcement (MBMS bearer announcement) message to the terminal to notify the terminal of the bearer information of the newly established broadcast bearer.
  • MBMS bearer announcement broadcast bearer announcement
  • the terminal may be a terminal in a service group, or all terminals in the service group in the BMS, or all terminals in a BMS corresponding system, or all terminals in a specific physical area, or All terminals within the service area are hosted for a particular broadcast.
  • the terminal receives and stores bearer information of the at least one broadcast bearer, and the terminal monitors channel quality of the at least one broadcast bearer, and determines whether data can be received on the at least one broadcast bearer.
  • the terminal After receiving the broadcast bearer notification message, the terminal (MC service client) stores the bearer information of the newly established broadcast bearer.
  • the bearer information of the broadcast bearer includes TMGI(s), and may also include a broadcast service area and a radio frequency.
  • the terminal starts to listen to the receiving status information of the broadcast bearer corresponding to the TMGI (s).
  • the MBMS service area is entered or the broadcast bearer signal corresponding to the at least one TMGI is detected to be good in the service area, the data can be received, and the information is reported to the BMS.
  • a BMS it is decided whether reference information of the broadcast transmission mode can be used for a certain service group.
  • the first BMS receives the receiving status information of the broadcast bearer sent by the terminal.
  • the first BMS can also accept the receiving status information of the broadcast bearer sent by other terminals.
  • the first BMS determines a broadcast bearer for the service group according to the receiving status information of the broadcast bearer.
  • the BMS determines to use the broadcast bearer for the service group indicated in the broadcast bearer use request message according to the received status information of the obtained broadcast bearer.
  • the specific process is the same as the S220 shown in FIG. 8 , the SS 222 shown in FIG. 10 or the SS 270 shown in FIG. 11 , and is not described here for brevity.
  • the first BMS sends a broadcast bearer usage notification message to the service server.
  • the BMS sends a MBMS bearer usage notify message to the MC Service server to notify the service group indicated in the broadcast bearer use request message sent by the MC Service server to use the broadcast bearer to transmit media data.
  • the broadcast bearer uses the bearer information of the broadcast bearer used in the notification message.
  • the broadcast bearer usage notification message further includes a group identifier of the service group.
  • the first BMS sends a notification message that the group uses the broadcast bearer to the terminal in the service group.
  • the BMS sends a notification message (MapGroupToBear) to the group member indicating the service group in the broadcast bearer use request, indicating that the service group is about to use the broadcast bearer to transmit the media data.
  • MapGroupToBear a notification message
  • the first BMS sends a broadcast bearer synchronization message to the second BNS.
  • the BMS sends a broadcast bearer synchronization (MBMS bearer synchorize) message to the BMS of the other system to notify the other BMS of bearer information and user plane information of the new broadcast bearer.
  • MBMS bearer synchorize broadcast bearer synchronization
  • the group identifier of the service group that uses the broadcast bearer is further included. This embodiment describes the process of synchronizing the collection of bearer information between different BMSs. If there is no unsynchronized or newly created broadcast bearer, this step can be skipped.
  • the broadcast bearer management method provided by the embodiment of the present invention, when the BMS receives one or more When the broadcast bearer usage request message of the controlling MC service server is used, the location information of the service group and the service group member is determined according to the group identifier of the service group included in the received broadcast bearer use request message, and the service group is received.
  • the status information of the broadcast bearer sent by the member of the service group determines the media data of the service group transmitted by using the broadcast bearer, and then respectively notify the terminal and the service server (MC service server) in the service group to transmit the media data by using the broadcast bearer, so that The service group member and the controlling MC service server use the broadcast bearer to transmit the media data of the service group.
  • FIG. 13 is a flowchart of another method for managing a broadcast bearer according to an embodiment of the present invention.
  • This embodiment describes that the Participating MC Service server requests to use a broadcast bearer.
  • Each service group involves a controlling MC service server and at least one participating MC service server.
  • the downlink broadcast bearer is The participating MC service server is activated, and the action process of each participating is the same as that of the controlling MC service server in the method 300 shown in FIG.
  • the BMS receives a broadcast bearer use request message from the multiple participating MC service servers for the same service group.
  • the embodiment of the present invention describes a BMS.
  • the BMS ensures that the terminals under different participating MC service servers use the same broadcast bearer to receive downlink media data in the same broadcast service area.
  • the method 400 can include the following steps:
  • At least one service server participating in the same emergency task group communication sends a broadcast bearer use request message to the BMS.
  • the service group session has been established, and the Participating MC service server 1 and the Participating MC service server 2 participating in the group communication of the same service group belong to the same system.
  • Participating MC service server 1 and Participating MC service The server 2 sends a broadcast bearer use request message to the BMS, where the message includes the group identifier of the same service group.
  • the BMS requests, according to the broadcast bearer use request message, a broadcast bearer that can be used for at least one service server participating in the emergency task group communication.
  • the BMS checks if there is a broadcast bearer available. If not, the BMS creates a new broadcast bearer as needed.
  • the BMS sends a broadcast bearer notification message to the terminal corresponding to the at least one service server participating in the emergency task group communication.
  • the BMS sends a broadcast bearer notification (MBMS bearer announcement) message to the group member (or terminal) of the participating MC service server 1 and the participating MC service server 2, and the broadcast bearer notification message carries the bearer information of the broadcast bearer for notification.
  • the bearer information carried by the terminal broadcast.
  • the terminal After receiving the message, the terminal (MC service client) stores the bearer information of the received broadcast bearer.
  • the bearer information of the broadcast bearer includes TMGI(s), the service area and other information related to the broadcast bearer, and the terminal starts to listen to the TMGI ( s) Corresponding to the channel quality of the broadcast bearer, and determining whether the data on the broadcast bearer can be received.
  • the broadcast bearer corresponding to the at least one TMGI can receive the data, and the acceptance status information of the broadcast bearer is reported to the BMS, and the BMS determines whether it can be used for a certain service group.
  • Reference information for the broadcast transmission mode can be used for a certain service group.
  • steps S415 and S420 may be performed before step S405.
  • the terminal transmits the received status information of the received broadcast bearer to the BMS.
  • the BMS determines to use the broadcast bearer.
  • the BMS determines the broadcast bearer to be used for the service group carried in the broadcast bearer use request message requested by the service server participating in the emergency task group communication.
  • the process of specifically determining the broadcast bearer is the same as the process of S220 in the method 200 in FIG. 8 , S222 in FIG. 10 , S270 in FIG. 11 , or S365 in the method 300 in FIG. 12 .
  • S220 in the method 200 in FIG. 8 S222 in FIG. 10
  • S270 in FIG. 11 S270 in FIG. 11
  • S365 S365 in the method 300 in FIG. 12 .
  • the BMS sends the determined user plane information of the broadcast bearer to the service server.
  • the processes of S430 and S445, and the processes of S435 and S450 are the same as the processes of S370 and S375 in the method 300 of FIG.
  • the BMS can ensure that the same broadcast bearer is used by the same service group for different service servers.
  • FIG. 14 is a flowchart of still another method for broadcast bearer management according to an embodiment of the present invention.
  • the BMS described in the embodiment of the present invention ensures that users under different participating MC service servers in the same MBMS service area receive downlink media data by using the same broadcast bearer in different MC service systems.
  • This embodiment transmits the broadcast bearer information that has been used to the BMS of all Parter systems through the controlling MC service server of the service group definition system or the BMS of the group definition system. To put it simply, different BMS systems use the same broadcast bearer in different service groups in the same service area.
  • the method 500 includes the following steps:
  • the BMSs of different systems respectively receive the broadcast bearer use request message.
  • the service group session has been established, and the Participating MC service server 1 and the Participating MC service server 2 participating in the same service group communication belong to different systems.
  • Participating MC service server 1 belongs to the Primary System; the Participating MC service server belongs to the Partner System.
  • the participating MC service server 1 sends a broadcast bearer use request message to the BMS of the system to which the BMS1 belongs, and the participating MC service server 2 sends a broadcast bearer use request message to the BMS2 of the system, and the broadcast bearer use request message may include the same service group. Group ID.
  • the BMS1 determines a broadcast bearer used by the group of the service group communication.
  • the BMS1 in the Primary system decides to use the broadcast bearer for this service group.
  • the specific implementation process refers to S365 of the method 300 shown in FIG. 12 and S425 of the method 400 shown in FIG. 13 for brevity of description, and details are not described herein again.
  • the BMS1 sends synchronous broadcast bearer information to the BMSs of other systems.
  • the BMS of other systems refers to the BMS of the same system that controls MC service server. After the primary system uses the broadcast bearer to transmit data for the service group, it needs to notify the other participating MC service server of the bearer information. Because the controlling MC service server BMS of the same system must have all the information of the group.
  • the BMS of the primary system sends the synchronous MBMS bearer information to the BMS of the same system of the control MC service server, and the synchronous broadcast bearer information may include bearer information and user plane information of the broadcast bearer.
  • the group identifier of the service group is also included.
  • the BMS of the same system of the controlling MC service server After receiving the broadcast bearer synchronization message, the BMS of the same system of the controlling MC service server sends the bearer information and user plane information of the broadcast bearer to the BMS of the partner system participating in the same service group communication.
  • the BMS2 After receiving the synchronization message of the broadcast bearer, the BMS2 determines that the group that the service group communicates uses the broadcast bearer.
  • the BMS notifies the received bearer information of the broadcast bearer to the terminal of the service group participating in the service group communication in the partner system.
  • the BMS notifies the received user plane information of the broadcast bearer to the participating MC service server participating in the service group communication in the partner system.
  • S550, S560, and S570 are the same as S375 and S370 of the method 300 in FIG. 11, S435 and S450 of the diagram 400 in FIG. 12, or S430 and S445, and are not described here for brevity.
  • the broadcast bearer information that has been used is sent to the BMS of all the Parter systems through the controlling MC service server of the group definition system or the BMS of the group definition system to ensure different in the same broadcast service area in different MC service systems.
  • the users under the participating MC service server use the same broadcast bearer to receive downlink data of the same service group communication.
  • FIG. 15 is a flowchart of still another method for broadcast bearer management according to an embodiment of the present invention.
  • This embodiment describes that the BMS controls the MC service Client to switch from a broadcast bearer to a unicast bearer.
  • the method 600 includes the following steps:
  • the method 600 includes the following steps:
  • the terminal detects that the channel quality of the used broadcast bearer is deteriorated, and the data on the broadcast bearer cannot be received.
  • the BMS receives the receiving status information of the broadcast bearer sent by the terminal.
  • the reception status information of the broadcast bearer indicates that the terminal cannot receive data on the broadcast bearer.
  • the BMS decides to use the unicast bearer to transmit data.
  • the preset condition may be that the receiving status information of the broadcast bearer is “cannot be received”.
  • the BMS sends a broadcast bearer switching request message to the service server.
  • the broadcast bearer switching request message includes an identifier of the terminal that sends the broadcast bearer status information that does not meet the preset condition.
  • the broadcast bearer switching request message is used to request the service server to switch to the unicast bearer to transmit data to the terminal corresponding to the terminal identifier.
  • the service server transmits data to the terminal corresponding to the terminal identifier by using the unicast bearer according to the broadcast bearer switching request message.
  • the terminal receives data sent by the service server.
  • the service group has an ongoing service group communication
  • the broadcast bearer transmits the media data in the specific broadcast service area, where the terminal is in the specific broadcast bearer area, and the broadcast bearer can be received.
  • the data on it is not limited to, but not limited
  • the MC service client detects that the data of the broadcast bearer received by the MC service client is in a bad state or cannot receive the data on the broadcast bearer. That is, the MC service client reports the status of the broadcast bearer to the BMS. Roger that".
  • the BMS triggers the MC service server to use the unicast bearer to transmit media data to the MC service client according to the "cannot receive" decision of the broadcast status of the broadcast bearer.
  • the BMS sends a unicast bearer switch request message to the MC service server, where the message carries the identifier of the client.
  • the group identity of the service group can also be carried.
  • the MC service server sends the downlink media data of the service group to the MC service client in a unicast bearer manner.
  • the service group sends the downlink media data by using the broadcast bearer in the specific broadcast bearer service area. If the MC service cilent fails to receive the data on the broadcast bearer, it reports to the BMS, and the BMS triggers the MC service server to single.
  • the broadcast mode sends downlink data to the user to improve system performance.
  • FIG. 16 is a flowchart of still another method for managing broadcast bearers according to an embodiment of the present invention.
  • This embodiment describes the BMS control service group communication switching from unicast bearer transmission to broadcast bearer transmission.
  • the MC service clien in the following steps is the terminal in Figure 16.
  • the method 700 includes the following steps:
  • the service group is now transmitting the group communication data using the unicast bearer.
  • the service group sends the first message to the BMS to request the available broadcast bearer.
  • the BMS After receiving the first message, the BMS does not satisfy the first preset according to the receiving state of the at least one broadcast bearer that is sent by the at least one MC service client. When the condition is not, it is not possible to determine an available
  • the broadcast bearer transmits the data using the unicast bearer.
  • the MC service client enters or is already in the broadcast service area, and determines that it can receive data of at least one broadcast bearer.
  • the MC service client cannot receive the data of the at least one broadcast bearer before.
  • the MC service client determines that the data received by the broadcast bearer is the same as described above.
  • the BMS determines, according to the receiving status message of the at least one broadcast bearer sent by the at least one MC service client, that the service group uses the first broadcast bearer.
  • the BMS sends a unicast bearer switching request message to the service server.
  • the unicast bearer switching request message includes user plane information of the broadcast bearer determined by the BMS.
  • the unicast bearer switching request message is used to request the service server to use the broadcast bearer to transmit the group communication service.
  • a possible implementation method is: after receiving the message, the service server uses the broadcast bearer to transmit group communication data, and stops using the original unicast bearer to transmit group communication data to the MC service client in the group.
  • the unicast bearer switching request message further includes a list of group MC service clients, and after receiving the message, the service server uses the broadcast bearer to transmit group communication data, and stops using the original A unicast bearer transmits group communication data to an MC service client other than the list in the group.
  • the BMS sends bearer information of the first broadcast bearer to the MC service client to the group.
  • the message includes bearer information of the first broadcast bearer.
  • the message further includes a group identifier of the service group.
  • the message user informs the MC service client to receive the communication data of the service group on the first broadcast bearer.
  • the BMS sends a unicast bearer switching request message to the MC service server, where the message carries the user plane information of the first broadcast bearer determined by the BMS.
  • the MC service server sends the downlink media data to the MC service client in a broadcast bearer manner. In order to avoid data loss, The MC service server can simultaneously use the broadcast data and the media data delivered by the unicast bearer.
  • FIG. 17 is a schematic structural diagram of a device for managing broadcast bearer according to an embodiment of the present invention.
  • the device for managing the broadcast bearer is used to implement the steps performed by the first bearer management server BMS in the embodiment shown in FIG. 8 to FIG. 16 described above.
  • the device 800 for broadcast bearer management includes: a receiving unit 810, a determining unit 820, and a transmitting unit 830.
  • the receiving unit 810 is configured to receive a first message sent by the service server, where the first message includes a group identifier of the service group;
  • a determining unit 820 configured to determine, according to the first message, a first broadcast bearer for the service group
  • the sending unit 830 is configured to send a second message to the service server, where the second message carries user plane information of the first broadcast bearer.
  • the device for the broadcast bearer management determines the broadcast bearer that can be used for the service group by receiving the first message sent by the service server and according to the group identifier of the service group included in the first message. And the user plane information of the broadcast bearer is carried in the second message and sent to the service server, optionally carrying the group identifier of the group, so that the service server can use the broadcast bearer to transmit data for the group,
  • the decoupling between the broadcast bearer management function and the application service layer control function is performed.
  • the management and use of the broadcast bearer are centralized on one control point relative to the prior art, and the centralized scheduling of the broadcast bearer is completed.
  • the device 800 may further include an obtaining unit 840.
  • the obtaining unit 840 is configured to acquire the receiving state information of the at least one broadcast bearer sent by the at least one terminal.
  • the determining unit 820 is specifically configured to determine, according to the first message and the receiving state information of the at least one broadcast bearer sent by the at least one terminal, the first broadcast bearer for the service group.
  • the first message further includes service description information, and the determining unit 820 is specifically configured to:
  • the at least one broadcast bearer satisfies the service description information, and the receiving state information of the at least one broadcast bearer sent by the at least one terminal meets the first preset condition, determining the first for the service group Broadcast bearer.
  • the device 800 may further include an establishing unit 850.
  • the establishing unit 850 is configured to establish a first broadcast bearer according to the first message.
  • the sending unit is further configured to send a broadcast bearer notification message to the at least one terminal, where the broadcast bearer notification message carries the bearer information of the first broadcast bearer.
  • the receiving unit is further configured to receive the receiving state information of the first broadcast bearer sent by the at least one terminal.
  • the determining unit is specifically configured to: if the receiving state information of the first broadcast bearer sent by the at least one terminal meets the first preset condition, determine the first broadcast bearer for the service group.
  • the acquiring unit 840 is further configured to acquire the receiving state information of the at least one broadcast bearer sent by the at least one terminal.
  • the establishing unit establishes the first broadcast bearer according to the first message.
  • the establishing unit 850 is specifically configured to:
  • the first broadcast bearer is established according to the first message.
  • the first BMS establishes a first broadcast bearer according to the first message
  • the acquiring unit 840 is further configured to obtain location information of the terminal in the service group.
  • the establishing unit 850 is specifically configured to establish a first broadcast bearer according to the service description information and the location information of the terminal in the service group.
  • the obtaining unit 840 is specifically configured to acquire location information of the terminal in the service group from at least one of the service server, the group management server, the terminal location management server, and the second BMS; or
  • the sending unit 830 is further configured to send a broadcast bearer synchronization message to the second BMS, where The bearer information and the user plane information of the first broadcast bearer are included in the broadcast bearer synchronization message.
  • the receiving unit 810 is further configured to receive the receiving state information of the first broadcast bearer sent by the terminal in the service group.
  • the sending unit 830 is further configured to send a third message to the service server, where the third message carries the identifier of the terminal, and the third message is used to The requesting service server sends the media data to the terminal using the unicast bearer.
  • each unit in the device 800 of the broadcast bearer management provided in FIG. 17 can complete the methods/steps in FIG. 8 to FIG. 16 respectively, and is not described here for brevity.
  • determining unit 820, the obtaining unit 840, and the establishing unit 850 in FIG. 17 may be collectively referred to as a processing unit.
  • the disclosed systems, devices, and methods may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or may be Integrate into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, or an electrical, mechanical or other form of connection.
  • each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.

Landscapes

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

Abstract

本发明涉及一种广播承载管理的方法和设备，该方法包括：第一承载管理服务器BMS接收业务服务器发送的第一消息，第一消息中包括业务群组的群组标识；第一BMS根据所述第一消息，为业务群组确定第一广播承载；所述第一BMS向业务服务器发送第二消息，第二消息携带第一广播承载的用户面信息。实现了广播承载管理功能与应用业务层控制功能的解耦，同时相对现有技术将广播承载的管理和使用集中在一个控制点上，完成了广播承载的集中调度。

Description

一种广播承载管理的方法及其设备 技术领域
本发明涉及通信网络领域，尤其涉及一种多媒体广播/组播服务(Multimedia Broadcast/Multicast Service，MBMS)承载管理的方法及其设备。
背景技术
现有紧急任务即按即说(Mission critical push-to-talk over LTE)用于公共安全应用及一般的商业应用，例如公共事业或者铁路应用等，支持一对多(1-to-N)的群组通信。对于1-to-N的群组通信，紧急任务即按即说(Mission critical push-to-talk，MCPTT)系统支持两种媒体传输模式：单播(Unicast bearer)传输和MBMS广播(MBMS bearer)传输。对于MBMS广播模式MCPTT系统基于集群通信系统使能(Group Communication System Enablers for LTE，GCSE_LTE)网络结构，如图1所示。其中，紧急任务服务服务器(Mission critical service server，MCS服务器)作为GCS AS的一个实例，实现了广播承载的管理和使用。现有的MCPTT服务器是MCS服务器的一种类型，其中集成了集群通信系统应用服务器(Group Communication System Application Server，GCS AS)的功能，如图2所示，图2为MCPTT网络架构和功能模型。
随着公共安全领域引入的服务越来越多，为了适应和满足集群通信的需求，例如MCVideo、MCData等均需要使用广播承载广播媒体数据。广播承载服务是一种与具体应用层业务无关的底层传输服务。而现有技术中，负责管理和使用广播承载服务的GCS AS功能与应用层业务服务器绑定在一起，如MCPTT服务器，如此，每引入新的需要使用广播承载服务的业务都 需要重新实现GCS AS功能，造成了整个公共安全网络架构功能的重复和耦合，也不利于新业务的快速部署。而且对于一个群组配置多重紧急业务的情况下，因为服务器分离部署，无法保证对于同一个群组的各个业务都使用同一个广播承载传输。现有分发下行媒体数据的广播承载有两种类型：预建立广播承载和动态建立的广播承载，需要说明的是，预建立的广播承载是在业务群组会话建立完成之前建立，动态建立的广播承载是在业务群组会话建立完成之后建立，如图3和图4所示。
图3为基于MCPTT架构预建立广播承载的方法流程图。图4为基于MCPTT架构动态建立广播承载的方法流程图。在图3和图4所示的基于MCPTT架构预建立或者动态建立广播承载的使用过程中，广播承载的激活、管理，以及呼叫控制(call control)紧紧耦合在MCPTT服务器中，会导致广播承载资源使用的效率比较低；一个MCPTT系统中可以存在多个MCPTT服务器提供服务，而且MCPTT服务器(或GCS AS)需要根据参与组呼叫(group call)中的组成员(group member)决定是否需要使用广播承载，现有MCPTT架构中，每个MCPTT服务器对于广播承载的管理和使用都是相互独立的，缺乏一个系统级别的集中广播承载的控制节点。
发明内容
本发明提供了一种广播承载管理的方法及其设备，实现了广播承载管理功能和应用业务层控制功能的解耦。。
第一方面，本发明实施例提供了一种广播承载管理的方法，该方法包括：
第一承载管理服务器BMS接收业务服务器发送的第一消息，第一消息中包括业务群组的群组标识；
第一BMS根据第一消息，为业务群组确定第一广播承载；
第一BMS向业务服务器发送第二消息，第二消息携带第一广播承载的 用户面信息。
通过接收业务服务器发送的第一消息，并根据第一消息中包括的业务群组的群组标识为该业务群组确定可以使用的广播承载，并将确定广播承载的用户面信息携带在第二消息中发送给业务服务器，以便于业务服务器可以使用该广播承载为该群组传输数据，实现了广播承载管理功能与应用业务层控制功能的解耦，同时相对现有技术将广播承载的管理和使用集中在一个控制点上，完成了广播承载的集中调度。
在本发明的一个设计方案中，第一BMS向业务服务器发送传输模式指示信息，也可以称为指示信息。在本发明实施例中，该指示信息的名称作限制，该指示信息用于指示业务服务器采用第一BMS确定的传输模式向业务群组传输数据。
在一个设计方案中，传输模式指示信息用于指示业务服务器对业务群组使用广播传输模式，或者，
传输模式指示信息用于指示业务服务器对业务群组中全部成员或部分成员使用广播传输模式或使用单播传输模式；或者，
传输模式指示信息用于指示业务服务器对业务群组从单播传输模式切换到广播传输模式，或者从广播传输模式切换到单播传输模式，或者仅使用单播传输方式，或者仅使用广播传输模式，或者停止使用单播传输方式，或者停止使用广播传输模式。
在有一个设计方案中，第二消息包括所述传输模式指示信息。
结合第一方面，在第一方面的第一种可能实现的方式，第一BMS根据第一消息，为业务群组确定第一广播承载，包括：
第一BMS获取至少一个终端发送的至少一个广播承载的接收状态信息；
第一BMS根据第一消息和至少一个终端发送的至少一个广播承载的接收状态信息，为业务群组确定第一广播承载。
结合第一方面的第一种可能实现的方式，在第一方面的第二种可能实现的方式中，第一消息还包括服务描述信息，第一BMS根据第一消息和至少一个终端发送的至少一个广播承载的接收状态信息，为业务群组确定第一广播承载，包括：
若至少一个广播承载满足服务描述信息，且至少一个终端发送的至少一个广播承载的接收状态信息满足第一预设条件，则为业务群组确定第一广播承载。
结合第一方面，在第一方面的第三种可能实现的方式中，第一BMS根据第一消息，为业务群组确定第一广播承载，包括：
第一BMS根据第一消息建立第一广播承载；
第一BMS向至少一个终端发送广播承载通知消息，广播承载通知消息中携带第一广播承载的承载信息；
第一BMS接收至少一个终端发送的第一广播承载的接收状态信息；
若至少一个终端发送的第一广播承载的接收状态信息满足第一预设条件，则为业务群组确定第一广播承载。
结合第一方面的第三种可能实现的方式，在第一方面的第四种可能实现的方式中，在第一BMS根据第一消息建立第一广播承载之前，方法还包括：
第一BMS获取至少一个终端发送的至少一个广播承载的接收状态信息；
若至少一个终端发送的至少一个广播承载的接收状态信息不满足第一预设条件，则第一BMS执行根据第一消息建立第一广播承载。
结合第一方面的第三种可能实现的方式，在第一方面的第五种可能实现的方式中第一消息包括服务描述信息，第一BMS根据第一消息建立第一广播承载，包括：
若服务描述信息不满足第二预设条件，则第一BMS执行根据第一消息 建立第一广播承载。
结合第一方面的第五种可能实现的方式，在第一方面的第六种可能实现的方式中，第一BMS根据第一消息建立第一广播承载，包括：
第一BMS获取业务群组中终端的位置信息；
第一BMS根据服务描述信息和业务群组中终端的位置信息，建立第一广播承载。
结合第一方面的第六种可能实现的方式，在第一方面的第七种可能实现的方式中第一BMS获取业务群组中终端的位置信息，包括：
第一BMS从业务服务器、群组管理服务器、终端位置管理服务器以及第二BMS中的至少一个服务器中获取业务群组中终端的位置信息；或者，
第一BMS接收业务群组中终端发送的位置信息。
结合第一方面的第七种可能实现的方式，在第一方面的第八种可能实现的方式中在第一BMS向业务服务器发送第二消息之后，方法还包括：
第一BMS向第二BMS发送广播承载同步消息，广播承载同步消息中包括第一广播承载的承载信息和用户面信息。
在一个设计方案中，广播同步消息还可以包括群组标识。
结合第一方面，在第一方面的第九种可能实现的方式中，该方法还包括：
若第一BMS接收到业务群组中的终端发送的第一广播承载的接收状态信息；
若第一广播承载的接收状态信息不满足第三预设条件，则第一BMS向业务服务器发送第三消息，第三消息中携带终端的标识，第三消息用于请求业务服务器使用单播承载向终端发送媒体数据。
第二方面，本发明实施例提供了一种广播承载管理的设备，该设备包括：
接收单元，用于接收业务服务器发送的第一消息，第一消息中包括业务群组的群组标识；
确定单元，用于根据第一消息，为业务群组确定第一广播承载；
发送单元，用于向业务服务器发送第二消息，该第二消息携带第一广播承载的用户面信息。
通过接收业务服务器发送的第一消息，并根据第一消息中包括的业务群组的群组标识为该业务群组确定可以使用的广播承载，并将确定广播承载的用户面信息携带在第二消息中发送给业务服务器，以便于业务服务器可以使用该广播承载为该群组传输数据，实现了广播承载管理功能与应用业务层控制功能的解耦，同时相对现有技术将广播承载的管理和使用集中在一个控制点上，完成了广播承载的集中调度。
在本发明的一个设计方案中，第一BMS向业务服务器发送传输模式指示信息，也可以称为指示信息。在本发明实施例中，对该指示信息的名称不作限制，该指示信息用于指示业务服务器采用第一BMS确定的传输模式向业务群组传输数据。
在一个设计方案中，传输模式指示信息用于指示业务服务器对业务群组使用广播传输模式，或者，
传输模式指示信息用于指示业务服务器对业务群组中全部成员或部分成员使用广播传输模式或使用单播传输模式；或者，
传输模式指示信息用于指示业务服务器对业务群组从单播传输模式切换到广播传输模式，或者从广播传输模式切换到单播传输模式，或者仅使用单播传输方式，或者仅使用广播传输模式，或者停止使用单播传输方式，或者停止使用广播传输模式。
在又一个设计方案中，第二消息包括传输模式指示信息。
结合第二方面，在第二方面的第一种可能实现的方式，设备还包括获取单元，
获取单元，用于获取至少一个终端发送的至少一个广播承载的接收状态信息；
确定单元具体用于，根据第一消息和至少一个终端发送的至少一个广播承载的接收状态信息，为业务群组确定第一广播承载。
结合第二方面的第一种可能实现的方式，在第二方面的第二种可能实现的方式中，确定单元具体用于，
若至少一个广播承载满足服务描述信息，且至少一个终端发送的至少一个广播承载的接收状态信息满足第一预设条件，则为业务群组确定第一广播承载。
结合第二方面，在第二方面的第三种可能实现的方式中，该设备还包括建立单元，
建立单元，用于根据第一消息建立第一广播承载；
发送单元，还用于向至少一个终端发送广播承载通知消息，广播承载通知消息中携带第一广播承载的承载信息；
接收单元，还用于接收至少一个终端发送的第一广播承载的接收状态信息；
确定单元具体用于，若至少一个终端发送的第一广播承载的接收状态信息满足第一预设条件，则为业务群组确定第一广播承载。
结合第二方面的第三种可能实现的方式，在第二方面的第四种可能实现的方式中，该设备还包括获取单元，
获取单元，用于获取至少一个终端发送的至少一个广播承载的接收状态信息；
若至少一个终端发送的至少一个广播承载的接收状态信息不满足第一预设条件，则建立单元根据第一消息建立第一广播承载。
结合第二方面的第三种可能实现的方式，在第二方面的第五种可能实现的方式中第一消息包括服务描述信息，建立单元具体用于，
若服务描述信息不满足第二预设条件，则根据第一消息建立第一广播承载。
结合第二方面的第五种可能实现的方式，在第二方面的第六种可能实现的方式中，获取单元，还用于获取业务群组中终端的位置信息；
建立单元具体用于，根据服务描述信息和业务群组中终端的位置信息，建立第一广播承载。
结合第二方面的第六种可能实现的方式，在第二方面的第七种可能实现的方式中，
获取单元具体用于，从业务服务器、群组管理服务器、终端位置管理服务器以及第二BMS中的至少一个服务器中获取业务群组中终端的位置信息；或者，
接收业务群组中终端发送的位置信息。
结合第二方面的第七种可能实现的方式，在第二方面的第八种可能实现的方式中，
发送单元，还用于向第二BMS发送广播承载同步消息，广播承载同步消息中包括第一广播承载的承载信息和用户面信息。
在一个设计方案中，广播承载同步消息还包括群组标识。
结合第二方面，在第二方面的第九种可能实现的方式中，
接收单元，还用于接收业务群组中的终端发送的第一广播承载的接收状态信息；
若第一广播承载的接收状态信息不满足第三预设条件，发送单元，还用于向业务服务器发送第三消息，第三消息中携带终端的标识，第三消息用于请求业务服务器使用单播承载向终端发送媒体数据。
第三方面，本发明实施例提供了一种广播承载管理的设备。该设备包括处理器以及存储器。存储器用于存储程序。处理器运行存储器中的程序用于，
接收业务服务器发送的第一消息，第一消息中包括业务群组的群组标 识；
根据第一消息，为业务群组确定第一广播承载；
向业务服务器发送第二消息，第二消息携带第一广播承载的用户面信息。
第四方面，本发明实施例提供了一种计算机存储介质，用于储存计算机软件指令，计算机运行该指令，用于：
接收业务服务器发送的第一消息，第一消息中包括业务群组的群组标识；
根据第一消息，为业务群组确定第一广播承载；
向业务服务器发送第二消息，第二消息携带第一广播承载的用户面信息。
基于本发明实施例提供的广播承载管理的方法和设备，通过接收业务服务器发送的第一消息，并根据第一消息中包括的业务群组的群组标识为该业务群组确定可以使用的广播承载，并将确定的广播承载的用户面信息携带在第二消息中发送给业务服务器，以便于业务服务器可以使用该广播承载为该群组传输数据，实现了广播承载管理功能与应用业务层控制功能的解耦，同时相对现有技术将广播承载的管理和使用集中在一个控制点上，完成了广播承载的集中调度。
附图说明
为了更清楚地说明本发明实施例的技术方案，下面将对本发明实施例中所需要使用的附图作简单地介绍，显而易见地，下面所描述的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1为现有技术中MCPTT服务基于GCSE_LTE的网络架构；
图2为现有技术中MCPTT网络架构和功能模型示意图；
图3为基于MCPTT架构预建立广播承载的方法流程图；
图4为基于MCPTT架构动态建立广播承载的方法流程图；
图5为本发明实施例提供的一种广播承载管理与应用业务控制分离的网络架构；
图6为本发明实施例提供的另一种广播承载管理与应用业务控制分离的网络架构；
图7为本发明实施例提供的一种广播承载管理的设备；
图8为本发明实施例提供的一种广播承载管理的方法流程图；
图9为本发明实施例提供的另一种广播承载管理的方法流程图；
图10为本发明实施例提供的再一种广播承载管理的方法流程图；
图11为本发明实施例提供的又一种MBS承载管理的方法流程图；
图12为本发明实施例提供的又一种广播承载管理方法流程图；
图13为本发明实施例提供的又一种MBS承载管理的方法流程图；
图14为本发明实施例提供的又一种广播承载管理方法流程图；
图15为本发明实施例提供的又一种广播承载管理的方法流程图；
图16为本发明实施例提供的又一种广播承载管理的方法流程图
图17为本发明实施例提供的一种广播承载管理设备的结构示意图。
具体实施方式
本发明实施例提供了一种广播承载管理的方法及其设备，适用于紧急任务服务系统(Mission Critical Service System)架构，如MCPTT，MCVID，MCDATA等系统，本系统的架构如图5及图6所示。
图5为一种广播承载管理与应用业务控制分离的网络架构。与现有MCPTT架构相比，增加了承载管理服务器(Bearer Management server，BMS)，紧急任务服务服务器(Mission Critical Service Server，MC Service server)与承载管理服务器之间的接口CSC-N1，紧急任务服务用 户设备(MC Service UE)与承载管理服务器之间的接口CSC-N2，群组管理服务器(Group Management server)与承载管理服务器之间的接口CSC-N3，承载管理服务器与承载管理服务器之间的接口CSC-N4。现有MCPTT架构中紧急任务即按即说服务器(MCPTT server)出的控制面MB2-C和用户面MB2-U接口改为由承载管理服务器BMS出。
图6与图5相比的主要区别在于广播承载的用户面(MB2-U)是否下移。如图6所示，仅广播承载的控制面板MB2-C下移，用户面MB2-U不改变。
在本发明实施例提供的广播承载管理与应用业务控制分离的网络架构中，紧急任务服务服务器MC Service Server主要负责呼叫的控制和媒体的控制，是一个逻辑实体。在具体实现中，MC Service Server可以是MCPTT server，MCVideo server或MCData server等。
紧急任务服务用户设备MC Service UE也可以称为紧急任务服务客户端(Mission Critical Service Client，MC Service Client)。MC Service UE是与MC Service server对等的应用层实体，主要用于负责应用层事务的处理。
承载管理服务器BMS：主要负责广播承载的激活、切换，集中调度。可以接收MC service UE上报的位置信息和广播承载接收状态信息。
图7为本发明实施例提供的一种广播承载管理的设备，该设备可以为承载管理服务器BMS。如图7所示，该广播承载管理的设备100包括接收器110、发送器120、存储器130、处理器140、通信接口150和通信总线160。接收器110、发送器120、存储器130、处理器140、通信接口150和通信总线160连接，以完成相互之间的通信。
接收器110用于通过通信接口150接收业务服务器(例如，MC Sservice Sserver)以及终端等其他设备发送的数据。发送器120用于通过通信接口 150向业务服务器(例如，MC service server)以及终端等其他设备发送数据，其中，处理器140通过接收器110和发送器120可实现下述图8至图16所示的实施例中与业务服务器以及终端之间数据的交互。存储器130用于存储指令和数据。处理器140用于调用存储器130中的指令，用于执行下述图8至图16所示的实施例中第一承载管理服务器BMS执行的步骤。
在本发明实施例中，在本发明实施例中，处理器140可以是中央处理单元(Central Processing Unit，CPU)，该处理器330还可以是其他通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现场可编程门阵列(Field-Programmable Gate Array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
通信总线160除包括数据总线之外，还可以包括电源总线、控制总线和状态信号总线等。但是为了清楚说明起见，在图中将各种总线都标为通信总线160。
存储器130可以包括只读存储器和随机存取存储器，并向处理器140提供指令和数据。存储器的一部分还可以包括非易失性随机存取存储器。
为便于说明，结合图8至图16对本发明实施例的技术方案进行详细的说明。需要说明的是本发明涉及的终端可为紧急任务服务系统中的MC service client应理解，这仅是用以说明本发明实施例的技术方案的一个例子，并不对本发明实施例构成任何的限定。
图8为本发明实施例提供的一种广播承载管理的方法流程图。该方法的执行主体可以为图7所示的广播承载管理的设备100。如图8所示，该方法200可以包括以下步骤：
S210，第一承载管理服务器BMS接收业务服务器发送的第一消息，第 一消息中包括业务群组的群组标识。
一个广播承载管理与应用业务控制分离的网络系统中可以包括一个或多个承载管理服务器BMS。第一BMS可以为一个或多个BMS。
第一消息用于触发BMS为业务群组(或称为群组)确定可用的广播承载。在本发明实施例中，第一消息可以称为广播承载请求消息，以请求BMS为该业务群组确定可用的广播承载，或者为该业务群组确定存在可以使用的广播承载，以便于业务服务器通过BMS提供的可使用的广播承载为该群组中的终端传输数据。传输的数据可以是媒体面数据，也可以是媒体面信令消息。
需要说明的是，在本发明实施例中，第一消息还可以采用为其他的名称消息，以来完成对实现指示BMS指示确定可使用的广播承载，在本发明实施例中对此不做限制。
S220，第一BMS根据第一消息为业务群组确定第一广播承载。
在广播承载管理与应用业务控制分离的网络系统中，在业务群组进行群组通信之前，可以预先建立一个或多个广播承载，每个广播承载对应一个特定的服务区域，每个广播承载具有唯一的标识，可以为临时移动群组标识(Temporary Mobile Group Identity，TMGI)，每个广播承载拥有对应广播承载的服务描述信息，该服务描述信息中可以包括服务质量(Quality of Service，QoS)；广播承载的承载信息，包含TMGI，无线频率，广播服务区域；用户面信息，包含广播承载的用户面BM-SC的IP地址和端口号。
具体地，当BMS在存储的一个或多个广播承载中有满足业务群组的可用的广播承载时，确定该广播承载为该业务群组可用的广播承载。其中，BMS存储的广播承载可以是BMS预建立的，也可以是从其他的BMS中获取并保存的。
需要说明的是，当BMS在存储的广播承载中没有找到该业务群组可用 的广播承载时，BMS可以为该业务群组建立一个广播承载，以便于确定该建立的广播承载是否为该业务群组可以使用的广播承载。当该建立的广播承载为该呼叫群组可使用的广播承载时，确定该建立的广播承载为该业务群组使用的广播承载。
其中，在建立广播承载的过程中，上述业务群组的通信可以采用其他传输模式进行数据传输，例如单播承载进行数据传输。
S230，第一BMS向业务服务器发送第二消息，第二消息携带第一广播承载的用户面信息。
第二消息用于通知业务服务器该业务群组可以使用哪一个广播承载传输数据。在本发明实施例中，该第二消息可以称为广播承载绑定消息。
其中，第一广播承载的用户面信息可以是用户面广播多播服务中心(Broadcast Multicast-Service Centre，BM-SC)的IP地址和端口号。如果业务服务器使用第一广播承载传输数据，则业务服务器将数据发送到第一广播承载对应的BM-SC的IP地址和端口号上。
采用本发明实施例提供的广播承载管理的方法，通过接收业务服务器发送的第一消息，并根据第一消息中包括的业务群组的群组标识为该业务群组确定可以使用的广播承载，并将确定广播承载的用户面信息携带在第二消息中发送给业务服务器，以便于业务服务器获取可以使用该广播承载传输业务群组的群组通信的数据，实现了广播承载管理功能与应用业务层控制功能的解耦，同时相对现有技术将广播承载的管理和使用集中在一个控制点上，完成了广播承载的集中调度。
需要说明的是，第一消息中可以包括多个业务群组的群组标识，即一个业务服务器可以同时为多个业务群组请求广播承载，BMS可以根据图8所示的方法200为每一个呼叫群组确定是否可以提供可用的广播承载。
可选地，在上述实施例的一种实施场景下，如图9所示，上述方法还包括：
S231，第一BMS向业务服务器发送传输模式指示信息。
其中，S231可以通过步骤S230实现，也可以在S230之后或之前实现，本发明不予限制。
其中，所述传输模式指示信息可以用于指示所述业务服务器对所述业务群组使用广播传输模式，或者，
所述传输模式指示信息可以用于指示所述业务服务器对所述业务群组中全部成员或部分成员使用广播传输模式或使用单播传输模式；或者，
所述传输模式指示信息可以用于指示所述业务服务器对所述业务群组从单播传输模式切换到广播传输模式，或者从广播传输模式切换到单播传输模式，或者仅使用单播传输方式，或者仅使用广播传输模式，或者停止使用单播传输方式，或者停止使用广播传输模式。
具体地，传输模式指示信息可以是显示地指示业务服务器对业务群组使用哪种传输模式，如显示指示使用单播传输模式，或者显示指示使用广播传输模式。也可以是隐式地指示业务服务器对业务群组使用哪种传输模式，如不使用或停止单播传输模式，不使用或者停止使用广播模式。
在一种可选的实现方式中，传输模式指示信息可以是一条独立的消息，具体地，该消息的名称或者消息的类型即可以具备上述传输模式指示信息的作用。例如，第二消息可以是上述传输模式指示信息。进而，业务服务器在收到第二消息后，使用BMS确定的广播承载向业务群组的终端传输数据。
在另一种可选的实现方式中，传输模式指示信息可以是消息中的一个信元。例如，单播传输使能/禁能，广播传输模式使能/禁能。假设传输模式指示信息是广播传输模式使能信元，该广播传输模式使能信元可以放在第二消息中带给业务服务器，也可以放在其它消息中发送给业务服务器，进而，业务服务器在收到这个传输模式指示信息后使用BMS确定的广播承载向业务群组的终端传输数据。
再例如，该信元可以是上述第一广播承载的用户面信息，业务服务器在收到第一广播承载的用户面信息后使用BMS确定的第一广播承载向业务群组的终端传输数据。
另外，当所述传输模式指示信息用于指示所述业务服务器对所述业务群组中部分成员使用广播传输模式或使用单播传输模式时，传输模式指示信息还可以包括业务群组的部分终端列表。如果广播传输模式或单播传输模式使用的对象为业务群组的一部分终端，则此时传输模式指示信息还包括一个包含业务群组中的一个或多终端的列表，指示业务服务器对列表中的终端使用广播传输模式或单播传输模式。例如，传输模式指示信息可以包括第一广播承载的用户面信息和终端列表，则业务服务器在收到第一广播承载的用户面信息和终端列表后，对终端列表中的终端使用单播承载传输，对其仅他业务群组使用广播承载传输。
需要说明的是，广播传输模式可以称为广播承载模式，单播传输模式可以称为广播承载模式。
在一种可能的实现方式中，当所述传输模式指示信息用于指示所述业务服务器对所述业务群组中全部成员使用广播传输模式或使用单播传输模式时，传输模式指示信息还可以包括业务群组中全部终端的列表，例如，标识列表，显然，传输模式指示信息还可以不携带终端标识，用于隐含指示业务群组的全部终端。
可选地，如图10所示，作为本发明另一个实施例，第一BMS根据第一消息为业务群组确定第一广播承载，包括：
S221，第一BMS获取至少一个终端发送的至少一个广播承载的接收状态信息。
当BMS从其他的BMS中获取到广播承载，并保存后，BMS会将该广播承载的承载信息广播给该至少一个终端，这些终端可以来自与该BMS系统或者所有BMS系统，或者特定的物理位置区域，或者特定的广播服务区域， 以便于接收到广播承载的承载信息的终端监听该广播承载的信道质量，判断是否能够在广播承载上收到数据，并将该广播承载的接收状态信息发送给BMS。
BMS接收至少一个终端发送的一个或多个预建立广播承载接收的接收状态信息。
需要说明的是，在本发明实施例中，BMS获取至少一个终端发送的至少一个广播承载的接收状态信息可以在BMS接收业务服务器发送的第一消息之前，即S210之前。
需要说明的是，BMS接收到的广播承载的接收状态信息是一个状态指示，如能够接收到，不能够接收到；如正在监听，没有监听；如“好”与“不好”等，“能够收到”，“正在监听”，“好”表示广播承载的信道质量满足预设阈值，用户能够在该广播承载上收到数据；“不好”表示广播承载的信号质量不满足预设阈值，用户不能够在该广播承载上收到数据。
终端判断自己能否接收到广播承载的数据并不依赖于业务服务器已经在广播承载上传输数据，终端可以通过广播承载上的周期性调度信息做出判断，其中调度信息不是由业务服务器发送。终端还可以由其他的判断方法，在本发明中对此不做限定。
S222，第一BMS根据第一消息和至少一个终端发送的至少一个广播承载的接收状态信息为业务群组确定第一广播承载。
在本发明实施例中，第一消息还可以包括服务描述信息，该服务描述信息可以为服务质量QoS信息。第一BMS根据第一消息和至少一个终端发送的至少一个广播承载的接收状态信息，为业务群组确定第一广播承载，可以包括：
第一BMS收到至少一个终端发送的至少一个广播承载的接收状态信息后，会进行统计，对每个广播承载，每一个群组中发送表示能够收到广播承载数据(例如，“能够收到”或“正在监听”或“好”等)的终端进行 统计。统计的数目，可以是占群组所有终端的百分比。一种实现方式的统计信息如下表所示。
例如现在BMS收到多个终端上报的3个广播承载的接收状态。
Figure PCTCN2016101417-appb-000001
在其他的实现方式中也可以对至少一个广播承载，各个群组中不能收到广播承载数据的终端进行统计，或者二者均做统计，本发明不做限定。
若至少一个广播承载满足服务描述信息，即当一个或多个预建立广播承载的服务描述信息满足第一消息中业务群组的所请求使用的服务描述信息时，且接收到至少一个终端发送的至少一个广播承载的接收状态信息满足第一预设条件，则为业务群组确定第一广播承载。第一预设条件为服务运营商配置的策略条件，例如，接收到某个广播承载的群组终端数目达到N个或者达到M％时，则确定该广播承载为第一广播承载。这些策略条件还可以包含其他用于确定第一广播承载的条件，本发明不做限定。
可选地，如图11所示，作为本发明另一实施例，第一BMS根据第一消 息为业务群组确定第一广播承载，包括：
S240，第一BMS根据第一消息建立第一广播承载。
当BMS接收到业务服务器发送的第一消息时，会为该第一消息中携带的业务群组的群组标识对应的业务群组确定是否有可用的广播承载。当BMS中存储了预先建立的广播承载时，BMS会在存储的广播承载中为该业务群组确定是否有可用的广播承载。其中，BMS中存储的广播承载可以从其他的BMS中获取。
当BMS确定根据业务群组的群组标识确定已存储的广播承载中不存在符合该业务群组使用的广播承载时，BMS会为该业务群组新建立一个广播承载(第一广播承载)，并存储新建立的广播承载的信息。新建立的广播承载的信息包括广播承载的承载信息，广播承载的业务描述信息，和广播承载的的用户面信息。其中广播承载的承载信息包括用于唯一标识广播承载的临时移动群组标识(Temporary Mobile Group Identity，TMGI)；还可以包括：无线频率及MBMS服务区域标识；新建立的广播承载的业务描述信息包括QoS等信息；新建立的广播承载的用户面信息包括用户面的BM-SC IP地址和端口号。
可选地，作为本发明一个实施例，在第一BMS根据第一消息建立第一广播承载之前，方法还包括：
第一BMS获取至少一个终端发送的至少一个广播承载的接收状态信息；若至少一个终端发送的至少一个广播承载的接收状态信息不满足第一预设条件，则第一BMS执行根据第一消息建立第一广播承载。
至少一个广播承载可以为BMS中存储的一个或多个广播承载。获取至少一个终端发送的至少一个广播承载的接收状态信息可以为BMS将存储的一个或多个广播承载的承载信息和用户面信息广播至少一个终端，该一个或多个终端可以是第一消息中携带的群组标识对应的业务群组中的终端，BMS对应系统中的所有终端，或者所有的BMS对应系统中的所有终端时， 或者位于特定的物理位置区域的终端，或者位于特定的广播服务区域的终端，接收到广播消息的终端监听收到的至少一个广播承载的接收状态信息广播承载，判断是否能够在广播承载上收到数据，并将接收到的至少一个广播承载的接收状态信息发送给BMS。
其中，广播承载的接收状态信息的描述同S221中的广播承载接收状态信息。
BMS接收到至少一个终端发送的至少一个广播承载的接收状态信息后的描述同S222中的对应描述。
需要说明的是，在本发明实施例中对BMS接收至少一个终端发送的至少一个广播承载的接收状态信息满足或不满足第一预设条件的第一预设条件不作限制，可以为业务群组中终端接收某个广播承载的接收状态信息为“好”的终端的数量，也可以为其他的条件。
可选地，作为本发明另一实施例，第一消息包括服务描述信息，第一BMS根据第一消息建立第一广播承载，可以包括：
若服务描述信息不满足第二预设条件，则第一BMS执行根据第一消息建立第一广播承载。
当BMS存储的广播承载的中服务描述信息不满足第一消息中携带的业务群组所要求的服务描述信息时，BMS为业务群组新建立广播承载，并存储新建立的广播承载的承载信息和用户面信息。
可选地，作为本发明另一个实施例，第一BMS根据第一消息建立第一广播承载，可以包括：
第一BMS获取业务群组中终端的位置信息。
第一BMS根据服务描述信息和业务群组中终端的位置信息，建立第一广播承载。
具体的，BMS获取业务群组中终端的位置信息，包括：
第一BMS可以从业务服务器、群组管理服务器、终端位置管理服务 器以及第二BMS中的至少一个服务器中获取业务群组中终端的位置信息。其中BMS获取群组中终端的位置信息可以在BMS接收业务服务器发送的第一消息之前或者在建立新的广播承载之前的任一时刻获取。
在本发明实施例中BMS还可以接收业务群组中终端发送的位置信息，以获取业务群组中终端的位置信息。
需要说明的是，当BMS接收到业务服务器发送的第一消息后，可以从第一消息中获取业务群组的群组标识，确定为哪个业务群组寻找可使用的广播承载。
另外，BMS可以在建立新的广播承载之前从群组管理服务器GMS中获取群组以及群组中成员(例如，终端)的信息。
在BMS接收到业务服务器发送第一消息之后，可以根据群组与群组成员的信息获取相应的第一消息中携带的业务群组中群组成员，即终端对应的位置信息。
当BMS获取到业务群组中终端的位置信息后，可以根据服务描述信息和终端的位置信息新建立广播承载。
S250，第一BMS向终端发送广播承载通知消息，广播承载通知消息中携带第一广播承载的承载信息。
BMS将新建立的广播承载的承载信息发送给该业务群组中所有的终端，以便于接收到该广播承载的承载信息的终端监听新建立广播承载，判断是否能够在该广播承载上接收到数据，并将该广播承载的接收状态信息发送给BMS。关于广播承载的接收状态描述同步骤S221中的相关描述。
需要说明的是，在本发明实施通过将新建立的广播承载的承载信息携带在广播承载通知消息中广播给该业务群组中的所有终端，在本发明实施例中，新建立的广播承载的承载消息还可以携带在其他的信息中广播给业务群组中的终端，或者说，在本发明实施例中对广播新建立广播承载的承载信息的消息的名称不作限定。
S260，第一BMS接收至少一个终端发送的第一广播承载的接收状态信息。该信息还可以在S250之后的任意时刻发送。该信息也可以发送多次，每次终端接收广播承载的状态发生变化时，即从“可以收到”变化为“不能收到”，或者从“不能收到”变化为“可以收到”时，都会向BMS发送该接收状态信息。
S270，若第一广播承载的接收状态信息满足第一预设条件，则为业务群组确定第一广播承载。
关于广播承载接收状态信息描述同S221中的相关描述，关于BMS对至少一个终端发送的至少一个广播承载接收状态信息统计描述同S222中的相关描述，对于第一预设条件的描述同S222的相关描述
当终端的数量不满足预设阈值时，该业务群组使用其他的承载传输数据，如使用单播承载传输。
此时系统中已存在预建立广播承载与S240中刚刚建立的广播承载，此时业务服务器使用单播承载向业务群组中的终端传输数据。于此同时，接收到至少一个广播承载的承载信息的终端依然在监听对应的广播承载，当终端接收广播承载的状态发生变化时，即原来终端不能收到广播承载的数据，变化为可以接收到广播承载数据，终端向BMS发送广播承载的接收状态信息。BMS根据第一消息中的业务群组标识和接收到的至少一个终端发送的至少一个广播承载的接收状态信息，为业务群组确定第一广播承载，并向业服务器发送第二消息，第二消息的描述同S230的相关描述。业务服务器在收到第二消息后，可以使用BMS确定的第一广播承载传输数据。如果业务服务器在接收到第二消息后就开始使用第一广播承载传输数据，则此时群组中的终端或部分终端可能会同时受到单播承载和广播承载传输的数据。业务服务器可以根据预配置的策略，例如对于同一个终端在同时使用广播承载和单播承载传输数据的特定时间后，则停止单播承载传输数据，而仅仅使用广播承载传输数据。或者还有其他策略，本发明不做限制。或 者业务服务器在接收到S231的传输模式指示消息后，可以根据传输模式指示信息，对群组中的终端确定是否使用广播传输模式或者单播传输模式。
可选地，如图11所示，作为本发明另一实施例，在第一BMS向业务服务器发送第二消息之后，该方法200还可以包括：
S280，第一BMS向第二BMS发送广播承载同步消息，广播承载同步消息中包括第一广播承载的承载信息和用户面信息。
BMS将新建立的广播承载的承载信息和用户面信息同步给除第一BMS之外的其他BMS。
可选地，该消息中还包含群组标识。
BMS将新建立的广播承载的承载信息和用户面信息和哪个业务群组使用该新建立的广播承载的信息同步给除第一BMS之外的其他BMS。
可选地，如图11所示，作为本发明另一个实施例，若第一BMS接收到业务群组中的终端发送的第一广播承载的接收状态信息，该方法200还可以包括：
S290，若第一广播承载的接收状态信息不满足第三预设条件，则第一BMS向业务服务器发送第三消息，第三消息中携带终端的标识，第三消息用于请求业务服务器使用单播承载向终端发送媒体数据。
在业务服务器对业务群组使用广播承载传输数据过程中，当BMS接收到业务群组中的一个或多个终端发送的广播承载的接收状态信息为“不好”时，BMS向业务服务器发送第三消息，第三消息可以为广播承载切换请求消息，需要说明的是，在本发明实施例中第三消息还可以采用其他的名称，对其名称不作限制。其中，广播承载请求消息中包括发送广播承载的接收状态信息为“不好”的终端的标识。广播承载切换请求消息用于请求业务服务器使用单播承载向终端的标识对应的终端发送媒体数据。
该第三消息可包含传输模式指示信息。在群组通信的数据传输过程中，第三消息可以根据用户的第一广播承载的接收状态发送多次。
需要说明的是，本发明实施例图11所示的S290也可以在图9所示的方案中完成，为简洁描述，在这里不再赘述。
应理解，在本发明的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本发明实施例的实施过程构成任何限定。
下面结合图12至图15对本发明技术方案进行详细的说明，在描述图11至图15所示的实施例之前，需要先说明几个概念：
控制紧急任务服务服务器(Controlling MC Service server)，是从群组呼叫(Group call)角度定义的逻辑实体，定义群组(Group)的紧急任务服务服务器，在该群组呼叫中承担主要控制功能，获取群组成员(Group member)的位置信息和用户设备(UE)侧接收广播承载的接收状态信息，也可以交过广播承载的质量报告信息。
参加紧急任务服务服务器(Participating MC service server)为用户注册的MC service server，在群组呼叫中负责路由群组成员发出的请求/响应，及将服务器的请求消息路由给群组成员。
其中，群组呼叫可以理解为业务服务器向BMS发送第一消息中携带的业务群组的群组标识对应的群组的呼叫。
需要说明的是，图12至图15中的第一BMS为Controlling MC Service server。下文可以简称为BMS，如果没有明确为其他的BMS，则全文提到的BMS均为Controlling MC Service server。
图12为本发明实施例提供的一种广播承载管理的方法流程图。
该实施例描述了Controlling MC Service server上有业务群组时通知BMS，让BMS决定何时使用哪一个广播承载。每个业务群组涉及到一个controlling MC service server和至少一个participating MC service  server，对于同一个业务群组的媒体内容，在同一MBMS服务区域内所有的群组成员监听同一个TMGI对应的广播承载，即在该MBMS服务区域内对同一业务群组只需使用一个广播承载。
如图12所示，该方法300可以包括以下步骤：
S305，激活广播承载。
BMS需要先在群组管理服务器GMS中获取群组信息和群组成员信息，等相关的信息。如果BMS已经在群组会话建立之前已经有可用的广播承载，激活已存在的广播承载以便于群组会话时使用。
S310，第一BMS向群组的群组成员发送广播承载通知消息。
BMS将存储的至少一个广播承载的承载信息携带在广播承载通知(MBMS bearer announcement)消息中发送给一个或多个群组成员(MC service client)，或称为终端。
S315，终端监听至少一个广播承载的信道质量。
终端接收到BMS广播的至少一个广播承载通知消息后，存储至少一个广播承载的承载信息和用户面信息，该广播承载的承载信息中包括唯一标识该广播承载的TMGI、服务区域信息以及服务描述信息等广播承载的相关的信息。终端根据TMGI监听对应广播承载上接收到的广播承载的接收状态，当进入广播承载服务区域或者已经在服务区域内监测到至少一个TMGI对应的广播承载信道信号质量良好可以接收数据时，将至少一个广播承载的接收状态信息发送给BMS，以便BMS决定是否可以对某个业务群组使用广播传输模式。
具体描述参见图10中S221。
S320，第一BMS接收终端发送的至少一个广播承载的接收状态信息。
第一BMS会接收到至少一个终端发送的至少一个广播承载的接收状态信息。
S325,业务服务器向BMS发送广播承载使用请求消息。
当某一紧急任务业务服务器(MC Service server)上有业务群组发起群组通信时，则MC Service server向BMS发送广播承载使用请求(MBMS bearer usage request)消息，该广播承载请求消息中包括群组标识(group ID)，服务描述(service description)信息等信息。其中，群组标识(group ID)标识一个业务群组。
可选地，BMS接收到广播承载使用消息后，向MC Service server返回广播承载使用响应(MBMS bearer usage response)消息，用于确认收到广播承载使用请求消息。
在本发明实施例中BMS可能收到一个或多个controlling MC service server发送的对应不同业务群组的广播承载使用请求消息，或一个controlling MC service server发送的对应不同业务群组的多条广播承载使用请求。
在另一种可选的实现方式中，一条MBMS bearer usage request消息中可以携带多个业务群组的广播承载使用请求信息，即群组标识(group ID)与服务描述信息(service description)的对应列表(list)。
可选地，S330，第一BMS根据广播承载使用请求消息获取业务群组。
BMS根据广播承载使用请求消息中携带的群组标识确定业务群组，并根据存储的业务群组与群组成员的关系，获取业务群组的群组成员、其群组成员的位置信息(location information)、群组成员对应的群组关联状态(affiliation status)、以及业务群组是否已经加入业务群组等信息。
需要说明的是，BMS获取成员的位置信息和群组成员对应的群组关联状态(affiliation status)可以发生在S325之后，步骤S330之前的任意时间，但群组成员是否加入群组只能发生在S325之后。
可选地，S335，第一BMS从其他系统的BMS查询并获取是否有符合要求的可用广播承载。
S340，若BMS从其他BMS获取到到业务群组有可使用的广播承载时，执行S350。
需要说明的是，本发明实施例中S335也可以在S325之前执行。如果在S325之前执行，且BMS获取到其他BMS已经存在的广播承载，则执行S350，355,365。
S345，当BMS从预建立的广播承载和从其他BMS获取到已经存在的广播承载都不能用于通信的业务群组时，第一BMS根据广播承载使用请求消息建立新的广播承载。
如果BMS发现当前没有可用的广播承载，则BMS按需动态建立新的广播承载，其中，按需动态建立新的广播承载的过程与图11中S240中的执行条件和过程类似，为简洁描述，在这里不再赘述，然后执行S350、S355和S360。
S350，第一BMS向终端发送广播承载通知消息。
BMS向终端发送广播承载通知(MBMS bearer announcement)消息，用于通知终端新建立的广播承载的承载信息。
其中，该终端可以为业务群组中的终端，也可以为BMS中所述业务群组中的所有终端，或者为所有BMS对应系统中的所有终端，或者为特定物理区域内的所有终端，或者为特定广播承载服务区域内的所有终端。
S355，终端接收并保存至少一个广播承载的承载信息，终端监听该至少一个广播承载的信道质量，判断是否能够在该至少一个广播承载上收到数据。
终端(MC service client)收到该广播承载通知消息后，保存新建立的广播承载的承载信息，该广播承载的承载信息包括TMGI(s)，还可以包括广播服务区域及无线频率。终端开始监听TMGI(s)对应的广播承载的接收状态信息。当进入MBMS服务区域或者已经在服务区域内监测到至少一个TMGI对应的广播承载信号质量良好可以接收数据，则向BMS上报该信息， 作为BMS决定是否可以对某个业务群组使用广播传输模式的参考信息。
S360，第一BMS接收终端发送的广播承载的接收状态信息。
第一BMS还可以接受其他终端发送的广播承载的接收状态信息。
S365，第一BMS根据广播承载的接收状态信息为业务群组确定广播承载。
BMS根据获取的广播承载的接收状态信息决定对广播承载使用请求消息中指示的业务群组使用广播承载。其具体过程与图8所示的S220，图10所示的SS222或图11所示的SS270相同，为描述简洁，在这里不再赘述。
S370，第一BMS向业务服务器发送广播承载使用通知消息。
BMS向MC Service server发送广播承载使用通知(MBMS bearer usage notify)消息，通知MC Service server发送的广播承载使用请求消息中指示的业务群组使用广播承载传输媒体数据。该广播承载使用通知消息中包括使用的广播承载的承载信息。
可选地，该该广播承载使用通知消息中还包括业务群组的群组标识。
S375，第一BMS向业务群组中的终端发送群组使用广播承载的通知消息。
BMS向广播承载使用请求中指示业务群组的群组成员发送通知消息(MapGroupToBear)，指示该业务群组即将使用广播承载传输媒体数据。
S380，可选地，第一BMS向第二BNS发送广播承载同步消息。
如果BMS新建立了广播承载或有未与其他BMS同步的广播承载，则BMS向其他系统的BMS发送广播承载同步(MBMS bearer synchorize)消息将新广播承载的承载信息和用户面信息通知给其他BMS，可选地，还包括使用该广播承载的业务群组的群组标识。该实施例描述了不同BMS之间承载信息同步汇集的过程。若不存在未同步或者新建的广播承载，则该步骤可以跳过。
通过本发明实施例提供的广播承载管理的方法，当BMS接收一个或多 个controlling MC service server的广播承载使用请求消息时，根据收到的广播承载使用请求消息中包括的业务群组的群组标识确定业务群组、业务群组成员的位置信息，以及接收业务群组中业务群组成员发送的广播承载的状态信息等决定使用广播承载传输业务群组的媒体数据，然后分别通知业务群组中的终端和业务服务器(MC service server)使用广播承载传输媒体数据，以便业务群组成员和controlling MC service server使用广播承载方式传输业务群组的媒体数据。
图13为本发明实施例提供的另一种广播承载管理方法的流程图。
该实施例描述了Participating MC Service server请求使用广播承载，每个业务群组涉及到一个controlling MC service server和至少一个participating MC service server，对于同一个业务群组的媒体内容，如果下行的广播承载由participating MC service server激活使用，则每个participating的动作过程与图12所示的方法300中controlling MC service server的动作过程相同。BMS会收到来个多个participating MC service server关于同一个业务群组的广播承载使用请求消息。
本发明实施例描述了BMS，BMS保证在同一MC service系统内、同一广播承载服务区域内，不同participating MC service server下的终端使用同一个广播承载接收下行媒体数据。
如图13所示，该方法400可以包括以下步骤：
S405和S405’，至少一个参加同一紧急任务群组通信的业务服务器向BMS发送广播承载使用请求消息。
业务群组会话已经建立完成，参与同一业务群组的群组通信的Participating MC service server 1和Participating MC service server2属于同一系统。
participating MC service server 1和Participating MC service  server 2向BMS发送广播承载使用请求消息，该消息中包括同一个业务群组的群组标识。
S410，BMS根据广播承载使用请求消息为至少一个参加紧急任务群组通信的业务服务器请求可以使用的广播承载。
BMS检查是否有可用的广播承载，如果没有，则BMS按需新建广播承载。
该过程与图11所示的S330、S335、S340和S345的过程相同，为描述简洁在这里不再赘述。
S415和S420，BMS向至少一个参加紧急任务群组通信的业务服务器对应的终端发送广播承载通知消息。
BMS分别向participating MC service server 1和Participating MC service server 2下的群组成员(或终端)发送广播承载通知(MBMS bearer announcement)消息，广播承载通知消息中携带了广播承载的承载信息，用于通知终端广播承载的承载信息。终端(MC service client)收到该消息后，保存接收到的广播承载的承载信息，该广播承载的承载信息包括TMGI(s)，服务区域及其他和广播承载相关的信息，终端开始监听TMGI(s)对应广播承载的信道质量，并判断能否收到该广播承载上的数据。当进入MBMS服务区域或者已经在服务区域内监测到至少一个TMGI对应的广播承载可以接收到数据，则向BMS上报该该广播承载的接受状态信息，作为BMS决定是否可以对某个业务群组使用广播传输模式的参考信息。
需要说明的是，若BMS上存在广播承载，如预建立的广播承载，则步骤S415和S420可以在步骤S405之前执行。
S415’和S420’，终端向BMS发送接收到的广播承载的接收状态信息。
S425，BMS确定使用广播承载。
BMS为参加紧急任务群组通信的业务服务器请求的广播承载使用请求消息中携带的业务群组确定使用的广播承载。
具体确定广播承载的过程与图8中方法200中S220、图10中S222，、图11中的S270，或者图12中方法300中的S365的过程相同，为描述简洁，在这里不再赘述。
S430，BMS将确定的广播承载的用户面信息发送给业务服务器
在本发明实施例中，S430与S445，以及S435与S450的过程与的过程与图12中的方法300中的S370与S375的过程相同。通过本实施例的技术方案实现了至少一个Participating MC service server向BMS为同一个群组请求使用广播承载时，BMS可以保证对不同业务服务器对同一个业务群组使用同一个广播承载。
图14为本发明实施例提供的又一广播承载管理的方法流程图。
本发明实施例描述的BMS，BMS保证在不同MC service系统内同一MBMS服务区域内不同participating MC service server下的用户使用同一个广播承载接收下行媒体数据。该实施例通过将已经使用的广播承载信息通过业务群组定义系统的controlling MC service server或群组定义系统的BMS发送给所有的Parter系统的BMS。简单讲，是不同的BMS系统，在同一个服务区域，不同的业务群组使用同一广播承载。
如图14所示，该方法500包括以下步骤：
S510和S510’，不同系统的BMS分别接收广播承载使用请求消息。
业务群组会话已经建立完成，参与同一业务群组通信的Participating MC service server 1和Participating MC service server2属于不同的系统。Participating MC service server 1属于Primary System；Participating MC service server属于Partner System。
participating MC service server 1向所所属系统的BMS1向BMS发送广播承载使用请求消息，Participating MC service server 2向所属系统的BMS2发送广播承载使用请求消息，广播承载使用请求消息中可以包括同一个业务群组的群组标识。
S520，BMS1确定对业务群组通信的群组使用的广播承载。Primary系统中的BMS1决定对该业务群组使用广播承载。具体实现过程参考图12所示的方法300的S365和图13所示的方法400的S425，为描述简洁，在这里不再赘述。
S530，BMS1向其他系统的BMS发送同步广播承载信息。其他系统的BMS指的是controling MC service server同一系统的BMS。primary系统使用广播承载为业务群组传输数据后，需要将承载信息通知给其他的participating MC service server。因为controlling MC service server同一系统的BMS一定有该群组的全部信息。Primary系统的BMS向controlling MC service server同一系统的BMS发送同步广播承载信息(synchronize MBMS bearer information)，该同步广播承载信息中可以包括广播承载的承载信息和用户面信息。可选地，还包括业务群组的群组标识。
S540，BMS向BMS2发送同步广播承载信息。
Controlling MC service server同一系统的BMS收到广播承载同步消息后，将广播承载的承载信息和用户面信息发送给参与同一业务群组通信的partner系统的BMS。
S550,BMS2收到该广播承载的同步消息后，确定该业务群组通信的群组使用该广播承载。
S560，BMS将收到的该广播承载的承载信息通知给partner系统中参与该业务群组通信的业务群组的终端。
S570，BMS将收到的该广播承载的用户面信息通知给partner系统中参与该业务群组通信的participating MC service server。
S550、S560和S570与图11中方法300的S375和S370，图12中图400的S435和S450，或S430和S445的过程相同，为简洁描述，在这里不再赘述。
该实施例通过将已经使用的广播承载信息通过群组定义系统的controlling MC service server或群组定义系统的BMS发送给所有的Parter系统的BMS，保证在不同MC service系统内同一广播服务区域内不同participating MC service server下的用户使用同一个广播承载接收同一个业务群组通信的下行数据。
需要说明的是，图12至图16中的方法步骤同图8至图10中对应的方法/步骤。
图15为本发明实施例提供的又一种广播承载管理的方法流程图。
该实施例描述了BMS控制MC service Client从广播承载切换到单播承载。
如图15所示，该方法600包括以下步骤：
如图15所示，该方法600包括以下步骤：
S610，终端检测已使用的广播承载的信道质量变差，不能收到该广播承载上的数据。
S620，BMS接收终端发送的广播承载的接收状态信息。
该广播承载的接收状态信息指示终端不能在广播承载上收到数据。
S630，若广播承载的接收状态信息满足预设条件时，BMS决定使用单播承载传输数据。
其中，预设条件可以是判断广播承载的接收状态信息为“不能收到”。
S640，BMS向业务服务器发送广播承载切换请求消息。
该广播承载切换请求消息中包括发送广播承载状态信息不满足预设条件的终端的标识。该广播承载切换请求消息用于请求业务服务器切换到单播承载向该终端标识对应的终端传输数据。
S650，业务服务器根据广播承载切换请求消息以单播承载向终端标识对应的终端传输数据。
终端接收业务服务器发送的数据。
具体的，在S610之前业务群组有正在进行的业务群组通信，在特定的广播服务区域内使用广播承载传输媒体数据，该终端在该特定的广播承载区域内，且可以接收到该广播承载上的数据。
MC service client检测到自己接收到的广播承载的数据的状态不佳，或不能收到广播承载上的数据，即未满足预设条件，MC service client向BMS上报广播承载的接收状态信息为“不能收到”。BMS根据广播承载的接收状态信息为“不能收到”决定触发MC service server对MC service client使用单播承载传输媒体数据。
BMS向MC service server发送单播承载切换请求消息，该消息中携带client的标识。可选地还可以携带业务群组的群组标识。MC service server使用单播承载的方式向MC service client发送业务群组的下行媒体数据。
本发明实施例通过业务群组在特定的广播承载服务区域内使用广播承载发送下行媒体数据，如果有MC service cilent无法接收到广播承载上的数据，则上报给BMS，BMS触发MC service server以单播方式向该用户发送下行数据，以提高系统性能。
图16为本发明实施例提供的又一种广播承载管理的方法流程图。
该实施例描述了BMS控制业务群组通信从单播承载传输切换到广播承载传输。
以下步骤中的MC service clien即为图16中的终端。
如图16所示，该方法700包括以下步骤：
S710，现在业务群组正在使用单播承载传输群组通信数据。
其中，业务群组在向BMS发送第一消息请求可用广播承载，BMS在接收到第一消息后，根据接收到至少一种MC service client发送的至少一个广播承载的接收状态不满足第一预设条件时，没有能够确定一个可用的 广播承载，则业务服务器使用单播承载传输数据。
S720，MC service client进入或者已经在广播服务区域，判断自己可以接收到至少一个广播承载的数据。
其中，MC service client在此之前不能收到上述至少一个广播承载的数据。关于MC service client判断收到广播承载的数据同前文描述。
S740，BMS根据接收至少一个MC service client发送的至少一个广播承载的接收状态消息，确定业务群组使用第一广播承载。
S750，BMS向业务服务器发送单播承载切换请求消息。
该单播承载切换请求消息中包括BMS确定的广播承载的用户面信息。该单播承载切换请求消息用于请求业务服务器使用广播承载传输群组通信业务。
其中，一种可能的实现方法为，业务服务器收到该消息后，使用该广播承载传输群组通信数据，并停止使用原有单播承载向群组中的MC service client传输群组通信数据。
又一种可能实现方法为，该单播承载切换请求消息中还包含一个群组MC service client的列表，业务服务器在收到该消息后，使用该广播承载传输群组通信数据，并停止使用原有单播承载向群组中的除列表以外的MC service client传输群组通信数据。
S760，BMS向至群组的MC service client发送第一广播承载的承载信息。该消息中包含第一广播承载的承载信息。
可选地，该消息中还包含业务群组的群组标识。
该消息用户通知MC service client在第一广播承载上接收而业务群组的通信数据。
BMS向MC service server发送单播承载切换请求消息，该消息中携带BMS确定的第一广播承载的用户面信息。MC serviceserver使用广播承载的方式向MC service client发送下行媒体数据。为了避免数据丢失， 在一段时间内，MC service server可以同时使用广播承载和单播承载下发的媒体数据。
图17为本发明实施例提供的一种广播承载管理的设备结构示意图。该广播承载管理的设备用于实现上述图8至图16所示的实施例中第一承载管理服务器BMS执行的步骤。如图16所示，该广播承载管理的设备800包括：接收单元810，确定单元820和发送单元830。
接收单元810，用于接收业务服务器发送的第一消息，该第一消息中包括业务群组的群组标识；
确定单元820，用于根据第一消息，为业务群组确定第一广播承载；
发送单元830，用于向业务服务器发送第二消息，第二消息携带第一广播承载的用户面信息。
采用本发明实施例提供的广播承载管理的设备，通过接收业务服务器发送的第一消息，并根据第一消息中包括的业务群组的群组标识为该业务群组确定可以使用的广播承载，并将确定广播承载的用户面信息携带在第二消息中发送给业务服务器，可选地还携带该群组的群组标识，以便于业务服务器可以使用该广播承载为该群组传输数据，实现了广播承载管理功能与应用业务层控制功能的解耦，同时相对现有技术将广播承载的管理和使用集中在一个控制点上，完成了广播承载的集中调度。
可选地，作为本发明另一实施例，该设备800还可以包括获取单元840，
获取单元840，用于获取至少一个终端发送的至少一个广播承载的接收状态信息。
确定单元820具体用于，根据第一消息和至少一个终端发送的至少一个广播承载的接收状态信息，为业务群组确定第一广播承载。
其中，第一消息还包括服务描述信息，确定单元820具体用于，
若至少一个广播承载满足服务描述信息，且至少一个终端发送的至少一个广播承载的接收状态信息满足第一预设条件，则为业务群组确定第一 广播承载。
可选地，作为本发明另一实施例，该设备800还可以包括建立单元850，
建立单元850，用于根据第一消息建立第一广播承载.
发送单元，还用于向至少一个终端发送广播承载通知消息，广播承载通知消息中携带第一广播承载的承载信息。
接收单元，还用于接收至少一个终端发送的第一广播承载的接收状态信息。
确定单元具体用于，若至少一个终端发送的第一广播承载的接收状态信息满足第一预设条件，则为业务群组确定第一广播承载。
作为本发明另一实施例，获取单元840，还用于获取至少一个终端发送的至少一个广播承载的接收状态信息。
若至少一个终端发送的至少一个广播承载的接收状态信息不满足第一预设条件，则建立单元根据第一消息建立第一广播承载。
若第一消息包括服务描述信息，建立单元850具体用于，
若服务描述信息不满足第二预设条件，则根据第一消息建立第一广播承载。
可选地，作为本发明另一实施例，第一BMS根据第一消息建立第一广播承载，获取单元840，还用于获取业务群组中终端的位置信息。
建立单元850具体用于，根据服务描述信息和业务群组中终端的位置信息，建立第一广播承载。
获取单元840具体用于，从业务服务器、群组管理服务器、终端位置管理服务器以及第二BMS中的至少一个服务器中获取业务群组中终端的位置信息；或者，
接收业务群组中终端发送的位置信息。
可选地，发送单元830，还用于向第二BMS发送广播承载同步消息， 广播承载同步消息中包括第一广播承载的承载信息和用户面信息。
接收单元810，还用于接收业务群组中的终端发送的第一广播承载的接收状态信息。
若终端发送的第一广播承载的接收状态信息不满足第三预设条件，则发送单元830，还用于向业务服务器发送第三消息，第三消息中携带终端的标识，第三消息用于请求业务服务器使用单播承载向终端发送媒体数据。
需要说明的是，图17提供的广播承载管理的设备800中的各个单元可以分别完成图8至图16中的方法/步骤，为简洁描述，在这里不再赘述。
还需要说明的是，图17中的确定单元820、获取单元840和建立单元850可以统称为处理单元。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，该单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另外，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口、装置或单元的间接耦合或通信连接，也可以是电的，机械的或其它的形式连接。该作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本发明实施例方案的目的。另外，在本发明各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以是两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
以上所述，仅为本发明的具体实施方式，但本发明的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本发明揭露的技术范围内，可 想到各种等效的修改或替换，这些修改或替换都应涵盖在本发明的保护范围之内。因此，本发明的保护范围应以权利要求的保护范围为准。

Claims (28)

  1. 一种广播承载管理的方法，其特征在于，所述方法包括：
    第一承载管理服务器BMS接收业务服务器发送的第一消息，所述第一消息中包括业务群组的群组标识；
    所述第一BMS根据所述第一消息，为所述业务群组确定第一广播承载；
    所述第一BMS向所述业务服务器发送第二消息，所述第二消息携带所述第一广播承载的用户面信息。
  2. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    所述第一BMS向所述业务服务器发送传输模式指示信息。
  3. 根据权利要求2所述的方法，其特征在于，所述传输模式指示信息用于指示所述业务服务器对所述业务群组使用广播传输模式，或者，
    所述传输模式指示信息用于指示所述业务服务器对所述业务群组中全部成员或部分成员使用广播传输模式或使用单播传输模式；或者，
    所述传输模式指示信息用于指示所述业务服务器对所述业务群组从单播传输模式切换到广播传输模式，或者从广播传输模式切换到单播传输模式，或者仅使用单播传输方式，或者仅使用广播传输模式，或者停止使用单播传输方式，或者停止使用广播传输模式。
  4. 根据权利要求2或3所述的方法，其特征在于，所述第二消息包括所述传输模式指示信息。
  5. 根据权利要求1至4任一项所述的方法，其特征在于，所述第一BMS根据所述第一消息，为所述业务群组确定第一广播承载，包括：
    所述第一BMS获取至少一个终端发送的至少一个广播承载的接收状态信息；
    所述第一BMS根据所述第一消息和所述至少一个终端发送的至少一个广播承载的接收状态信息，为所述业务群组确定所述第一广播承载。
  6. 根据权利要求5所述的方法，其特征在于，所述第一消息还包括服 务描述信息，所述第一BMS根据所述第一消息和所述至少一个终端发送的至少一个广播承载的接收状态信息，为所述业务群组确定所述第一广播承载，包括：
    若所述至少一个广播承载满足所述服务描述信息，且所述至少一个终端发送的至少一个广播承载的接收状态信息满足第一预设条件，则为所述业务群组确定所述第一广播承载。
  7. 根据权利要求1至4任一项所述的方法，其特征在于，所述第一BMS根据所述第一消息，为所述业务群组确定第一广播承载，包括：
    所述第一BMS根据所述第一消息建立所述第一广播承载；
    所述第一BMS向至少一个终端发送广播承载通知消息，所述广播承载通知消息中携带所述第一广播承载的承载信息；
    所述第一BMS接收至少一个终端发送的所述第一广播承载的接收状态信息；
    若所述第一BMS接收到的至少一个终端发送的第一广播承载的接收状态信息满足第一预设条件，则为所述业务群组确定所述第一广播承载。
  8. 根据权利要求7所述的方法，其特征在于，在所述第一BMS根据所述第一消息建立所述第一广播承载之前，所述方法还包括：
    所述第一BMS获取至少一个终端发送的至少一个广播承载的接收状态信息；
    若所述第一BMS获取至少一个终端发送的至少一个广播承载的接收状态信息不满足第一预设条件，则所述第一BMS根据所述第一消息建立所述第一广播承载。
  9. 根据权利要求7所述的方法，其特征在于，所述第一消息包括服务描述信息，所述第一BMS根据所述第一消息建立所述第一广播承载，包括：
    若所述服务描述信息不满足第二预设条件，则所述第一BMS根据所述第一消息建立所述第一广播承载。
  10. 根据权利要求9所述的方法，其特征在于，所述第一BMS根据所述第一消息建立第一广播承载，包括：
    所述第一BMS获取所述业务群组中终端的位置信息；
    所述第一BMS根据所述服务描述信息和所述业务群组中终端的位置信息，建立所述第一广播承载。
  11. 根据权利要求10所述的方法，其特征在于，所述第一BMS获取所述业务群组中终端的位置信息，包括：
    所述第一BMS从所述业务服务器、群组管理服务器、终端位置管理服务器以及第二BMS中的至少一个服务器中获取所述业务群组中终端的位置信息；或者，
    所述第一BMS接收所述业务群组中终端发送的位置信息。
  12. 根据权利要求7至11任一项所述的方法，其特征在于，在所述第一BMS向所述业务服务器发送第二消息之后，所述方法还包括：
    所述第一BMS向第二BMS发送广播承载同步消息，所述广播承载同步消息中包括所述第一广播承载的承载信息和用户面信息。
  13. 根据权利要求12所述的方法，其特征在于，所述广播承载同步消息还包括所述群组标识。
  14. 根据权利要求1至13任一项所述的方法，其特征在于，所述方法还包括：
    所述第一BMS接收所述业务群组中的终端发送的所述第一广播承载的接收状态信息；
    若所述终端发送的第一广播承载的接收状态信息不满足第三预设条件，则所述第一BMS向所述业务服务器发送第三消息，所述第三消息中携带所述终端的标识，所述第三消息用于请求所述业务服务器使用单播承载向所述终端发送媒体数据。
  15. 一种广播承载管理的设备，其特征在于，所述设备包括：
    接收单元，用于接收业务服务器发送的第一消息，所述第一消息中包括业务群组的群组标识；
    确定单元，用于根据所述第一消息，为所述业务群组确定第一广播承载；
    发送单元，用于向所述业务服务器发送第二消息，所述第二消息携带所述第一广播承载的用户面信息。
  16. 根据权利要求15所述的设备，其特征在于，所述发送单元，还用于向所述业务服务器发送传输模式指示信息。
  17. 根据权利要求16所述的设备，其特征在于，所述传输模式指示信息用于指示所述业务服务器对所述业务群组使用广播传输模式，或者，
    所述传输模式指示信息用于指示所述业务服务器对所述业务群组中全部成员或部分成员使用广播传输模式或使用单播传输模式；或者，
    所述传输模式指示信息用于指示所述业务服务器对所述业务群组从单播传输模式切换到广播传输模式，或者从广播传输模式切换到单播传输模式，或者仅使用单播传输方式，或者仅使用广播传输模式，或者停止使用单播传输方式，或者停止使用广播传输模式。
  18. 根据权利要求16或17所述的设备，其特征在于，所述第二消息包括所述传输模式指示信息。
  19. 根据权利要求15至18任一项所述的设备，其特征在于，所述设备还包括获取单元，
    所述获取单元，用于获取至少一个终端发送的至少一个广播承载的接收状态信息；
    所述确定单元具体用于，根据所述第一消息和所述至少一个终端发送的至少一个广播承载的接收状态信息，为所述业务群组确定所述第一广播承载。
  20. 根据权利要求19所述的设备，其特征在于，所述第一消息还包括 服务描述信息，所述确定单元具体用于，
    若所述至少一个广播承载满足所述服务描述信息，且所述至少一个终端发送的至少一个广播承载的接收状态信息满足第一预设条件，则为所述业务群组确定所述第一广播承载。
  21. 根据权利要求15至18任一项所述的设备，其特征在于，所述设备还包括建立单元，
    所述建立单元，用于根据所述第一消息建立所述第一广播承载；
    所述发送单元，还用于向至少一个终端发送广播承载通知消息，所述广播承载通知消息中携带所述第一广播承载的承载信息；
    所述接收单元，还用于接收至少一个终端发送的所述第一广播承载的接收状态信息；
    所述确定单元具体用于，若所述至少一个终端发送的第一广播承载的接收状态信息满足第一预设条件，则为所述业务群组确定所述第一广播承载。
  22. 根据权利要求21所述的设备，其特征在于，所述设备还包括获取单元，
    所述获取单元，用于获取至少一个终端发送的至少一个广播承载的接收状态信息；
    若所述至少一个终端发送的至少一个广播承载的接收状态信息不满足第一预设条件，则所述建立单元根据所述第一消息建立所述第一广播承载。
  23. 根据权利要求21所述的设备，其特征在于，所述第一消息包括服务描述信息，所述建立单元具体用于，
    若所述服务描述信息不满足第二预设条件，则根据所述第一消息建立所述第一广播承载。
  24. 根据权利要求23所述的设备，其特征在于，所述获取单元，还用于获取所述业务群组中终端的位置信息；
    所述建立单元具体用于，根据所述服务描述信息和所述业务群组中终端的位置信息，建立所述第一广播承载。
  25. 根据权利要求24所述的设备，其特征在于，
    所述获取单元具体用于，从所述业务服务器、群组管理服务器、终端位置管理服务器以及第二BMS中的至少一个服务器中获取所述业务群组中终端的位置信息；或者，
    接收所述业务群组中终端发送的位置信息。
  26. 根据权利要求21至25任一项所述的设备，其特征在于，
    所述发送单元，还用于向第二BMS发送广播承载同步消息，所述广播承载同步消息中包括所述第一广播承载的承载信息和用户面信息。
  27. 根据权利要求26所述的设备，其特征在于，所述广播承载同步消息还包括所述群组标识。
  28. 根据权利要求15至27任一项所述的设备，其特征在于，
    所述接收单元，还用于接收所述业务群组中的终端发送的所述第一广播承载的接收状态信息；
    若所述终端发送的第一广播承载的接收状态信息不满足第三预设条件，所述发送单元，还用于向所述业务服务器发送第三消息，所述第三消息中携带所述终端的标识，所述第三消息用于请求所述业务服务器使用单播承载向所述终端发送媒体数据。
PCT/CN2016/101417 2016-10-01 2016-10-01 一种广播承载管理的方法及其设备 WO2018058692A1 (zh)

Priority Applications (7)

Application Number Priority Date Filing Date Title
CN201680089442.5A CN109716798B (zh) 2016-10-01 2016-10-01 一种广播承载管理的方法及其设备
PCT/CN2016/101417 WO2018058692A1 (zh) 2016-10-01 2016-10-01 一种广播承载管理的方法及其设备
EP16917442.2A EP3512222B1 (en) 2016-10-01 2016-10-01 Broadcast bearer management method and device thereof
CN202011617653.6A CN113163347B (zh) 2016-10-01 2016-10-01 一种广播承载管理的方法及其设备
EP22161501.6A EP4072170B1 (en) 2016-10-01 2016-10-01 Broadcast bearer management method and device thereof
US16/371,778 US10757542B2 (en) 2016-10-01 2019-04-01 Broadcast bearer management method and device thereof
US16/988,177 US11337040B2 (en) 2016-10-01 2020-08-07 Broadcast bearer management method and device thereof

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/101417 WO2018058692A1 (zh) 2016-10-01 2016-10-01 一种广播承载管理的方法及其设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/371,778 Continuation US10757542B2 (en) 2016-10-01 2019-04-01 Broadcast bearer management method and device thereof

Publications (1)

Publication Number Publication Date
WO2018058692A1 true WO2018058692A1 (zh) 2018-04-05

Family

ID=61762443

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/101417 WO2018058692A1 (zh) 2016-10-01 2016-10-01 一种广播承载管理的方法及其设备

Country Status (4)

Country Link
US (2) US10757542B2 (zh)
EP (2) EP3512222B1 (zh)
CN (2) CN109716798B (zh)
WO (1) WO2018058692A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110366121A (zh) * 2018-04-10 2019-10-22 成都鼎桥通信技术有限公司 组呼业务通信方法及装置
CN110505589A (zh) * 2018-05-16 2019-11-26 成都鼎桥通信技术有限公司 集群通信方法、装置、调度机、终端和系统

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018058692A1 (zh) * 2016-10-01 2018-04-05 华为技术有限公司 一种广播承载管理的方法及其设备
FR3074004B1 (fr) * 2017-11-20 2019-11-22 Airbus Ds Slc Systeme de communication de groupe pour la transmission de donnees multimedia
KR102187546B1 (ko) * 2019-01-30 2020-12-07 문재호 그룹소통 서비스를 제공하는 방법, 시스템 및 컴퓨터-판독가능 매체

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103036926A (zh) * 2011-09-29 2013-04-10 中国电信股份有限公司 业务推送系统及方法
CN103581836A (zh) * 2012-08-08 2014-02-12 中兴通讯股份有限公司 一种群组小数据的发送方法及系统
CN103609147A (zh) * 2012-10-25 2014-02-26 华为技术有限公司 集群通信系统、集群服务器、接入网络以及集群通信方法
CN104254054A (zh) * 2013-06-25 2014-12-31 电信科学技术研究院 一种集群通信方法及装置和系统

Family Cites Families (27)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7697523B2 (en) * 2001-10-03 2010-04-13 Qualcomm Incorporated Method and apparatus for data packet transport in a wireless communication system using an internet protocol
US6987764B2 (en) * 2001-11-05 2006-01-17 Qualcomm, Incorporated Method and apparatus for selecting a packet data serving node for multi-cast/broadcast services
CN1203695C (zh) * 2002-08-13 2005-05-25 北京三星通信技术研究有限公司 临时移动组标识的产生与分配方法
CN1476259A (zh) * 2002-08-16 2004-02-18 ��������ͨ�ż����о����޹�˾ 多媒体广播和组播业务寻呼的方法
CN101136814B (zh) * 2006-08-28 2010-12-08 西门子（中国）有限公司 一种支持mbms业务的方法和装置
KR100740874B1 (ko) * 2006-09-29 2007-07-19 한국전자통신연구원 부하 분산을 위한 멀티미디어 방송형 멀티캐스트 서비스제어 시스템 및 그 제어 방법
WO2009121406A1 (en) * 2008-04-02 2009-10-08 Telefonaktiebolaget Lm Ericsson (Publ) Transmission mode selection mechanism
CN101800938A (zh) * 2009-02-05 2010-08-11 华为技术有限公司 为mbms承载业务建立无线承载的方法、装置和系统
JP5225894B2 (ja) * 2009-03-04 2013-07-03 パナソニック株式会社 無線基地局装置、無線端末装置、無線通信システム、および基地局認証方法
JP5523130B2 (ja) * 2010-02-08 2014-06-18 キヤノン株式会社 通信装置、通信方法、及びプログラム
CN102378113B (zh) * 2010-08-12 2016-03-02 中兴通讯股份有限公司 一种多媒体广播多播业务传输方式的转换方法和系统
US8861419B2 (en) * 2010-12-29 2014-10-14 Motorola Solutions, Inc. Methods for binding and unbinding a MBMS bearer to a communication group in a 3GPP compliant system
CN102595328B (zh) * 2011-01-14 2017-11-10 中兴通讯股份有限公司 Mbms承载方式转化信息的配置发送方法及装置
US8934423B2 (en) * 2011-09-13 2015-01-13 Motorola Solutions, Inc. Methods for managing at least one broadcast/multicast service bearer
CN104284298B (zh) * 2013-07-08 2018-07-20 电信科学技术研究院 一种群组通信中的资源控制方法及组通信服务器
GB201319196D0 (en) * 2013-10-30 2013-12-11 Nec Corp Communication system
CN104640077B (zh) * 2013-11-08 2019-10-11 中兴通讯股份有限公司 一种集群通信的方法及系统、用户设备和网络侧设备
CN104812087A (zh) * 2014-01-24 2015-07-29 北京三星通信技术研究有限公司 支持组业务传输的方法、装置及系统
CN105323722B (zh) * 2014-07-31 2020-05-26 中兴通讯股份有限公司 基于mbms承载的集群通信中拥塞状态上报方法及系统
CN105323723A (zh) * 2014-07-31 2016-02-10 中兴通讯股份有限公司 基于mbms承载的集群通信中查询节点状态的方法及系统
US11212321B2 (en) * 2014-08-18 2021-12-28 Nokia Solutions and Network OY Group communication service enabler security
CN105376717B (zh) * 2014-08-25 2020-06-23 中兴通讯股份有限公司 建立lte集群通信承载的方法、用户设备及第一网元设备
JP6239791B2 (ja) * 2015-01-30 2017-11-29 京セラ株式会社 基地局、プロセッサ及びユーザ端末
WO2016142810A1 (en) * 2015-03-06 2016-09-15 Telefonaktiebolaget Lm Ericsson (Publ) Method and network node for delivering multimedia broadcast services
EP3301997B1 (en) * 2015-07-06 2019-09-11 Huawei Technologies Co., Ltd. Enhanced multimedia broadcast and multicast service embms system and management method therefor
WO2017026760A1 (en) * 2015-08-07 2017-02-16 Samsung Electronics Co., Ltd. Terminal and communication method of the same
WO2018058692A1 (zh) * 2016-10-01 2018-04-05 华为技术有限公司 一种广播承载管理的方法及其设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103036926A (zh) * 2011-09-29 2013-04-10 中国电信股份有限公司 业务推送系统及方法
CN103581836A (zh) * 2012-08-08 2014-02-12 中兴通讯股份有限公司 一种群组小数据的发送方法及系统
CN103609147A (zh) * 2012-10-25 2014-02-26 华为技术有限公司 集群通信系统、集群服务器、接入网络以及集群通信方法
CN104254054A (zh) * 2013-06-25 2014-12-31 电信科学技术研究院 一种集群通信方法及装置和系统

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110366121A (zh) * 2018-04-10 2019-10-22 成都鼎桥通信技术有限公司 组呼业务通信方法及装置
CN110505589A (zh) * 2018-05-16 2019-11-26 成都鼎桥通信技术有限公司 集群通信方法、装置、调度机、终端和系统

Also Published As

Publication number Publication date
CN113163347B (zh) 2022-09-09
CN109716798B (zh) 2021-01-08
EP4072170B1 (en) 2023-09-13
US10757542B2 (en) 2020-08-25
CN113163347A (zh) 2021-07-23
EP3512222A1 (en) 2019-07-17
US11337040B2 (en) 2022-05-17
US20190230481A1 (en) 2019-07-25
CN109716798A (zh) 2019-05-03
EP3512222A4 (en) 2019-08-21
EP3512222B1 (en) 2022-03-30
US20200374663A1 (en) 2020-11-26
EP4072170A1 (en) 2022-10-12

Similar Documents

Publication Publication Date Title
JP5844879B2 (ja) Ｍｂｍｓサービス送信方式の切替方法、装置及びユーザー装置
JP6503071B2 (ja) サービングセル情報を用いる、ポイントツーマルチポイント（ｐｔｍ）互換サービスのための送信メカニズム選択
WO2018058692A1 (zh) 一种广播承载管理的方法及其设备
CN104247470B (zh) 数据传输方法、装置及系统
CN109600721B (zh) 一种通信方法及装置
US8559352B2 (en) Apparatus and method for multicast broadcast service in wireless communication system that uses multi-carrier
GB2530585A (en) Managing communication resources
US20190149958A1 (en) Methods, Apparatuses and Computer Program for Transmission Format/Retransmission Adaptation in Wireless Network
WO2013170425A1 (zh) 上报业务指示消息的方法、装置及系统
US20210044938A1 (en) Mbms bearer handling in a group communications system
WO2016142810A1 (en) Method and network node for delivering multimedia broadcast services
WO2015109475A1 (zh) 一种集群通信方法、基站、用户设备及系统
US12225434B2 (en) Method and apparatus for transmitting and receiving data in wireless communication system
WO2016154848A1 (zh) 一种请求中继服务的通信方法、设备及系统
WO2015143795A1 (zh) Mbms差错处理方法、通信节点、通信系统和存储介质
WO2017000591A1 (zh) 一种信息发送的方法和终端
TW201215196A (en) Mechanism design for operator controlled MBMS reception status collection
WO2012122816A1 (zh) 一种确定用户设备切换的目标小区的方法和系统
CN104521251B (zh) 业务传输方法、装置、设备及系统
CN118120262A (zh) 点对多点通信
WO2018219218A1 (zh) 一种ma配置方法、系统及设备
JP5341821B2 (ja) マルチキャスト配信システム及び方法
KR20250028278A (ko) 비활성 상태에서 멀티캐스트 서비스들을 수신하는 것을 지원하기 위한 방법들 및 디바이스들
WO2015042836A1 (zh) 一种无线资源分配的方法及装置
CN113099391A (zh) 独立部署的5g系统承载mbms的方法与系统

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2016917442

Country of ref document: EP

Effective date: 20190412