WO2019062169A1 - 一种通信方法及装置 - Google Patents

一种通信方法及装置 Download PDF

Info

Publication number
WO2019062169A1
WO2019062169A1 PCT/CN2018/088256 CN2018088256W WO2019062169A1 WO 2019062169 A1 WO2019062169 A1 WO 2019062169A1 CN 2018088256 W CN2018088256 W CN 2018088256W WO 2019062169 A1 WO2019062169 A1 WO 2019062169A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
entity
multicast bearer
terminal group
target
Prior art date
Application number
PCT/CN2018/088256
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
Priority claimed from CN201810036433.0A external-priority patent/CN109600721B/zh
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to KR1020197007877A priority Critical patent/KR102191884B1/ko
Priority to BR112019007382A priority patent/BR112019007382A2/pt
Priority to JP2019517982A priority patent/JP6849795B2/ja
Priority to AU2018322503A priority patent/AU2018322503B2/en
Priority to EP18849392.8A priority patent/EP3496432B1/en
Publication of WO2019062169A1 publication Critical patent/WO2019062169A1/zh
Priority to US16/376,327 priority patent/US11251981B2/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
    • 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/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H04W4/10—Push-to-Talk [PTT] or Push-On-Call services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/90—Services for handling of emergency or hazardous situations, e.g. earthquake and tsunami warning systems [ETWS]

Definitions

  • the present application relates to the field of mobile communications technologies, and in particular, to a communication method and apparatus.
  • Public cluster services including Mission Critical Push-to-talk over LTE (MCPTT), Mission Critical Video (MCVideo), Mission Critical Data (MCData), etc.
  • MCPTT Mission Critical Push-to-talk over LTE
  • MCVideo Mission Critical Video
  • MCData Mission Critical Data
  • Public safety applications and general commercial applications such as utilities or rail applications, and support one-to-many group communication.
  • the emergency service system supports two media transmission modes: unicast bearer transmission and multicast bearer transmission.
  • the MC service entity can be implemented by using a mission critical service entity (MC service entity), for example, a mission critical service server (MC service server), and the MC service entity can be a slave logic. It is divided into a business control entity and a business participation entity.
  • MC service entity mission critical service entity
  • MC service server mission critical service server
  • the service participating entity is mainly used for registering the terminal, and sending data to the registered terminal, and determining to use the unicast bearer transmission or the multicast bearer to send data to the terminal group;
  • the service control entity is mainly used for management of group communication establishment, and receiving
  • the uplink service data of the terminal group distributes service data to the terminal group through the service participating entity.
  • the terminal group may be composed of the same terminal registered in the same service participating entity, or may be composed of terminals registered in different service participating entities.
  • the different service participating entities may send data to the terminal group, and the transmitted data may be the same, so that the terminal group The terminal repeatedly receives the same data, resulting in wasted resources.
  • the present application provides a communication method and apparatus for reducing the number of times a terminal group repeatedly receives the same service data, thereby saving resources.
  • the present application provides a communication method, which may be performed by a target service entity or a chip within a target service entity, where the target service entity may be a service control entity or a multicast bearer management entity.
  • the method includes: first, the target service entity receives a first request message from a first service participating entity, the first request message includes a group identity and an identifier of a target multicast bearer, and the first request message is used to request to use the target multicast
  • the service data of the terminal group corresponding to the sending group identifier is carried.
  • the target service entity sends a first response message to the first service participating entity, where the first response message includes a usage status of the target multicast group by the terminal group.
  • the method after receiving the first request message of the first service participating entity for requesting to use the service data of the target multicast bearer sending terminal group, the target service entity sends the terminal group to the target to the first service participating entity.
  • the usage status of the multicast bearer so that the first service participating entity can determine whether the service data can be sent to the terminal group by using the target multicast bearer according to the received usage status, for example, when the first service participating entity determines the terminal group.
  • the first service participating entity uses the target multicast bearer to send the service data, thereby helping to prevent multiple service participating entities from simultaneously using the target multicast bearer to the terminal group.
  • Sending data helps to avoid the terminal group's terminals repeatedly receiving the same service data, which saves resources.
  • the usage status of the target multicast carrier by the terminal group may also be expressed as the transmission status of the target multicast bearer to the terminal group.
  • the transmission status refers to a status of transmitting service data, and the service data includes control signaling and media data.
  • the terminal group in the foregoing method may have the following implementation manners for using the target multicast bearer:
  • the usage status is in use, or the usage status is unused.
  • the target service entity records the usage status of the target multicast bearer as: in use or not used.
  • the middle finger is that the current service participating entity is currently using the target multicast bearer to send service data, or the current service participating entity uses the target multicast bearer and is ready to send service data.
  • Unused means that no service entity is currently using the target multicast bearer to send service data, or no service participating entity currently uses the target multicast bearer and is ready to start transmitting service data.
  • the service data with the terminal group on the target multicast bearer is sent, or the service data with no terminal group on the target multicast bearer is sent.
  • the target service entity records the usage status of the target multicast bearer as follows: the service data of the terminal group on the target multicast bearer is sent, or the service data of the terminal group without the target multicast bearer is being sent.
  • the service data of the terminal group on the target multicast bearer is sent, and the target multicast bearer is currently used to send the service data of the terminal group.
  • the service data without the terminal group on the target multicast bearer is sent, which means that the target multicast bearer does not currently use the service data for the sending terminal group.
  • the usage status is that the service participation entity does not use the target multicast bearer to send the service data of the terminal group, or the usage status is that the service participation entity uses the target multicast bearer to send the service data of the terminal group, or the usage status.
  • the service data of the terminal group is transmitted by using the target multicast bearer for the second service participating entity.
  • the object that uses the target multicast bearer that is, the service participating entity, is further recorded.
  • the service data of the terminal group on the target multicast bearer in the foregoing implementation manner 2 is transmitted, and in the third implementation manner, the service participation entity uses the target multicast bearer to send the service of the terminal group.
  • the second service participating entity refers to any business participating entity associated with the target business entity.
  • the service data of the terminal group is not transmitted on the target multicast bearer in the foregoing implementation manner 2.
  • the service data is not recorded by the service participating entity using the target multicast bearer.
  • the target service entity receives an indication message from the first service participating entity, where the indication message is used to indicate that the first service participating entity uses the target multicast bearer to send the service data of the terminal group; the target service entity is configured according to Indicates the message and updates the usage status. That is, when the first service participating entity determines to use the target multicast carrier to transmit the service data of the terminal group, the target service entity is notified, so that the target service entity will update the usage status of the target multicast bearer.
  • the target service entity updates the usage status according to the indication message, including:
  • the target service entity updates the usage status to the first service participating entity using the target multicast bearer to transmit the service data of the terminal group;
  • the target service entity updates the usage status to the service data of the terminal group that the service participating entity uses the target multicast bearer;
  • the target business entity updates the usage status to in use.
  • the method further includes: the target service entity receives the second request message from the third service participating entity, where the second request message includes the group identifier and the identifier of the target multicast bearer, and the second request message is used by the second request message. And requesting to use the target multicast to carry the service data of the sending terminal group; the target service entity sends a second response message to the third service participating entity, where the second response message includes the updated usage status of the target multicast bearer.
  • the foregoing any one of the foregoing embodiments may further include: the target service entity sends a notification message to the third service participant entity, where the notification message includes the target multicast.
  • the updated usage status of the bearer may further include: the target service entity sends a notification message to the third service participant entity, where the notification message includes the target multicast.
  • the target service entity can manage the associated service participating entities, after the target service entity updates the usage status of the target multicast bearer, the updated usage status can be actively notified to the associated service participating entities.
  • the target service entity may further receive a notification status report message from the third service participating entity, where the notification status report message is used to notify the third service participating entity to notify the terminal to receive the terminal group on the target multicast bearer. Group of business data.
  • the method further includes: the target service entity receives the bearer information report message from the fourth service participating entity, where the bearer information report message includes an identifier of the service area, a group identifier, and an identifier of the target multicast bearer.
  • the method when the fourth service participating entity establishes a multicast bearer, actively reports the established multicast bearer information to the target service entity. For example, after the target multicast bearer is established, the bearer information report message is sent to the target service entity, where the bearer information report message includes the identifier of the service area used by the target multicast bearer, and the terminal group corresponding to the target multicast bearer The identity of the target and the identity of the target multicast bearer.
  • the bearer information reporting message further includes information of the fourth service entity, such as address information of the fourth service entity or identifier information of the fourth service entity.
  • the method further includes: the target service entity receives the query request message from the first service participating entity, where the query request message includes an identifier of the service area, and the query request message is used to request to acquire the terminal corresponding to the sending group identifier.
  • the multicast bearer of the service data of the group the target service entity sends a query response message to the first service participating entity, where the query response message includes the identifier of the target multicast bearer.
  • the present application provides a communication method that can be performed by a chip within a service participating entity or a business participating entity.
  • the method includes: the first service participating entity sends a request message to the target service entity, where the request message includes a group identifier and an identifier of the target multicast bearer, and the request message is used to request to send the terminal group corresponding to the group identifier by using the target multicast bearer.
  • the service data; the first service participating entity receives the response message from the target service entity, and the response message includes the usage status of the target multicast group by the terminal group.
  • the method when the first service participating entity sends the service data to the terminal group, sends a request message for requesting to use the target multicast carrier to send the service data of the terminal group to the target service entity, and then receives the request message sent by the target service entity.
  • the response message includes the usage status of the terminal group to the target multicast bearer.
  • the first service participating entity may determine, according to the received usage status, whether the target multicast carrier can be used to send service data to the terminal group, for example, when the first service participating entity determines that the terminal group is targeted to the target multicast bearer.
  • the first service participating entity When the usage status is not used, the first service participating entity sends the service data by using the target multicast bearer; when the first service participating entity determines that the use status of the target multicast group by the terminal group is in use, the first The service participating entity does not use the target multicast bearer to send service data, thereby helping to prevent multiple service participating entities from simultaneously transmitting data to the terminal group by using the target multicast bearer, thereby helping to avoid repeated receiving of the terminal group terminal.
  • the same business data can save resources.
  • the first service participating entity determines, according to the usage state, the service data of the sending terminal group by using the target multicast bearer; the first service participating entity sends an indication message to the target service entity, where the indication message is used to indicate The first service participating entity uses the target multicast bearer to transmit the service data of the terminal group.
  • the first service participating entity determines that the service data of the terminal group can be transmitted by using the target multicast group according to the used state of the target multicast group
  • the first service participating entity determines that And using the target multicast to carry the service data of the sending terminal group, and send an indication message to the target service entity, where the first service participating entity uses the target multicast bearer to send the service data of the terminal group, thereby enabling the target service.
  • the entity updates the usage status of the target multicast group by the terminal group.
  • the first service participating entity determines, according to the usage status, the service data of the terminal group to be transmitted by using the target multicast bearer, including: when the first service participating entity has the service data of the terminal group to be sent. And the usage status is that the service data is not used by the service participating entity to use the target multicast bearer to send the terminal group, or the usage status is unused or the usage status is that the service data without the terminal group on the target multicast bearer is transmitted, the first service The participating entity determines to use the target multicast to carry the service data of the sending terminal group; or
  • the usage status is that no service participating entity uses the target multicast carrier to transmit the service data of the terminal group or the usage status is unused or the usage status is that the service data without the terminal group on the target multicast bearer is sent.
  • the service participating entity determines the service data of the transmitting terminal group using the target multicast bearer.
  • the first service participating entity when the first service participating entity determines to use the target multicast bearer to send the service data of the terminal group, the first service participating entity further sends a notification message to the terminal, where the notification message is used to notify the terminal to pass the target.
  • the multicast bearer receives the service data of the terminal group.
  • the notification status report message is sent to the target service entity, where the notification status report message is used to notify the first service participating entity to notify the terminal of the target multicast bearer. Receive service data of the terminal group.
  • the first service participating entity uses the target multicast bearer to send the service data of the terminal group; or, when the target multicast bearer is configured by the first
  • the first service participating entity sends the indication information and the service data of the terminal group to be sent to the second service participating entity, where the indication information is used to indicate that the second service participating entity sends the to-be-sent to be sent by using the target multicast bearer.
  • Business data for the terminal group when the target multicast bearer is established by the first service participating entity, the first service participating entity uses the target multicast bearer to send the service data of the terminal group; or, when the target multicast bearer is configured by the first
  • the first service participating entity sends the indication information and the service data of the terminal group to be sent to the second service participating entity, where the indication information is used to indicate that the second service participating entity sends the to-be-sent to be sent by using the target multicast bearer.
  • Business data for the terminal group when the target multicast bearer is established by the first service participating entity, the first service participating entity uses
  • the first service participating entity sends a bearer information report message to the target service entity, where the bearer information report message includes an identifier of the service area, a group identifier, and an identifier of the target multicast bearer; or, the first service The participating entity receives the push message from the target service entity, and the push message includes an identifier of the service area, a group identifier, and an identifier of the target multicast bearer.
  • the present application provides a communication method that can be performed by a chip within a service control entity or a service control entity.
  • the method includes: the service control entity acquires the identifier of the multicast bearer, and the multicast bearer is used to transmit the service data of the terminal group in the service area; the service control entity sends the first indication message to the first service participating entity associated with the terminal group.
  • the first indication message is used to indicate that the first service participating entity sends the service data of the terminal group by using the multicast bearer, and the service control entity sends the second indication message to the second service participant entity associated with the terminal group, where the second indication message is sent.
  • the service data of the terminal group is not sent to the terminal located in the service area in the terminal group, where the first service participating entity is different from the second service participating entity;
  • a terminal is registered on the first service participating entity, and at least one terminal in the terminal group is registered on the second service participating entity.
  • the service control entity instructs the first service participating entity to send the service data of the terminal group through the multicast bearer, and instructs the second service participating entity to not send the service of the terminal group to the terminal located in the service area in the terminal group.
  • the data avoids the terminal repeatedly receiving the same service data and saves resources.
  • the service control entity obtains the identifier of the multicast bearer, including: the service control entity sends a query message to the multicast bearer management entity, where the query message includes the identifier of the service area, and the query message is used to request the query service area corresponding to Multicast bearer; the service control entity receives a response message from the multicast bearer management entity, and the response message includes an identifier of the multicast bearer.
  • the method is stored in the multicast bearer management entity due to related information of the multicast bearer, such as an identifier of the multicast bearer.
  • the service control entity requests the multicast bearer management entity to query the identifier of the multicast bearer corresponding to the service area by querying the message, so as to facilitate the management of the information carried by the multicast bearer.
  • the service control entity sends a request message to the third service participating entity associated with the terminal group, where the request message includes an identifier of the service area, and the request message is used to request the third service participating entity to establish more in the service area. Broadcast bearer.
  • the method when the service control entity fails to obtain the identifier of the multicast bearer from the multicast bearer management entity, requests the service participating entity, such as the third service participating entity, to establish a multicast bearer.
  • the service control entity receives a response message from the third service participating entity, where the response message includes an identifier of the established multicast bearer.
  • the service control entity can obtain the identity of the established multicast bearer.
  • the service control entity receives the response message from the third service participating entity, the response message includes indication information, the indication information is used to indicate that the multicast bearer is successfully established, and the third service participating entity
  • the established multicast bearer information such as the identifier of the multicast bearer, is sent to the multicast bearer management entity for storage, so that the service control entity can further obtain the established multicast bearer from the multicast bearer management entity.
  • the request message includes an identification of a group of terminals.
  • the identifier of the multicast bearer acquired by the service control entity is corresponding to the terminal group corresponding to the identifier of the terminal group, that is, the identifier of the obtained multicast bearer is the terminal The identity of the bearer associated with the group.
  • the foregoing response message further includes an identifier of the terminal group.
  • the service control entity receives the notification message from the first service participating entity, and the notification message is used to notify that the first service participating entity stops transmitting the service data of the terminal group through the multicast bearer; the service control entity The second service participating entity sends a third indication message, where the third indication message is used to indicate the second service participating entity, and sends the terminal group to the terminal located in the service area and registered on the second service participating entity in the terminal group.
  • Business data is used to indicate the second service participating entity, and sends the terminal group to the terminal located in the service area and registered on the second service participating entity in the terminal group.
  • the service control entity when the first service participating entity stops using the multicast bearer to send the service data of the terminal group, the service control entity notifies the second service participating entity that the terminal group is located in the service area and is registered in the second service participating entity.
  • the terminal transmits the service data, so that when the terminal located in the service area and the terminal registered in the second service participating entity cannot receive the service data from the first service participating entity, the terminal can also receive the service from the second service participating entity.
  • the data enables the terminal located in the service area and registered on the second service participating entity in the terminal group to receive the service data normally.
  • the service control entity sends the indication information to the fourth service participating entity, where the indication information is used to indicate to the terminal located in the service area and registered on the fourth service participating entity in the terminal group by using the unicast mode.
  • the service data is sent, and the fourth service participating entity is any one of the service participating entities associated with the terminal group. That is, when the service control entity decides to stop using the multicast bearer, it indicates that all the service participating entities associated with the multicast bearer use the unicast mode to register the service data in the terminal group to transmit the service data to the terminal.
  • the service control entity sends the indication information to the fourth service participating entity, where the indication information is used to indicate the fourth service participating entity, and is located in the service group in the terminal group and is registered in the fourth service participating entity.
  • the terminal sends the service data, and the fourth service participating entity is any one of the service participating entities associated with the terminal group. That is, when the service control entity decides to stop using the multicast bearer, it instructs all the service participating entities associated with the multicast bearer to separately send the service data to the terminal group to register the service data in the terminal group, and the data is sent by the service participating entity itself.
  • the decision may be, for example, a unicast method or a multicast method.
  • the present application provides a communication method that can be performed by a chip in a service participating entity or a business participating entity.
  • the method includes: the service participating entity receives a second indication message from the service control entity, where the second indication message includes an identifier of the multicast bearer, an identifier of the service area, and a group identifier, where the second indication message is used to indicate the service participating entity, Transmitting the service data of the terminal group to the terminal located in the service area in the terminal group corresponding to the group identifier; the service participation entity sends a fourth indication message to the terminal, where the fourth indication message includes the identifier of the multicast bearer, and the fourth indication message It is used to instruct the terminal to receive the service data of the terminal group through the multicast bearer.
  • the service participating entity receives a third indication message from the service control entity, where the third indication message is used to indicate the service participating entity, and sends the service data of the terminal group to the terminal.
  • the present application provides a communication method that can be performed by a chip in a service participating entity or a business participating entity.
  • the method includes: the service participating entity sends a request message to the target service entity, where the request message includes an identifier of the service area and a group identifier, the request message is used to request to query the target multicast bearer, and the target multicast bearer is used to send the group in the service area. Identifying the service data of the corresponding terminal group; the service participating entity receives the response message from the target service entity, and the response message includes the identifier of the target multicast bearer; the service participating entity sends an indication message to the terminal, where the indication message is used to indicate that the terminal passes the target.
  • the broadcast carries the service data of the receiving terminal group.
  • the service participating entity may actively obtain the identifier of the target multicast bearer from the target service entity, and after obtaining the identifier of the target multicast bearer, notify the terminal group that is located in the service area and is registered in the terminal of the service participating entity, Receiving service data on the target multicast bearer, so that the terminal in the service group in the terminal group receives the service on the target multicast bearer, so that only one service participating entity needs to send the service data, so that the terminal group of the terminal group can be made. Both receive the service data, avoid the terminal in the terminal group to receive data again, and reduce the resource overhead of the service participating entity.
  • the service participating entity sends the service data of the terminal group by using the target multicast bearer; or the response message further includes the first indication information, where the first indication information is used to indicate that the service participating entity passes the target multicast bearer. Transmitting the service data of the terminal group; the service participating entity sends the service data of the terminal group through the target multicast bearer.
  • the service participant entity when the service participating entity determines that the service data is no longer sent to the terminal group by using the target multicast bearer, the service participant entity sends a first notification message to the target service entity, where the first notification message is used to notify the target service entity.
  • the service participating entity stops, and transmits the service data of the terminal group through the target multicast bearer. Therefore, after receiving the first notification message, the target service entity may instruct other service participating entities to send the service data to the terminal group.
  • the response message further includes second indication information, where the second indication information is used to indicate the service participating entity, and the service data of the terminal group is not sent to the terminal located in the service area in the terminal group.
  • the service participating entity sends a request message to the target service entity, where the request message includes an identifier of the service area and a group identifier, and the request message is used to request to query the target multicast bearer, and the target multicast bearer is used to send the terminal corresponding to the group identifier in the service area.
  • the business data of the group; the business participating entity receives the response message from the target business entity, and the response message includes the indication information.
  • the service participating entity When the indication information is the identifier of the target multicast bearer, the service participating entity sends an indication message to the terminal, where the indication message is used to indicate that the terminal receives the service data of the terminal group on the target multicast bearer, where the terminal is in the service group in the terminal group. And the terminal registered on the business participating entity. And transmitting the service data of the terminal group through the target multicast bearer.
  • the service participating entity When the indication information is the identifier of the target multicast bearer and the first indication information, the service participating entity sends the indication message to the terminal. And transmitting, by the target multicast, the service data of the sending terminal group.
  • the first indication information is used to indicate the service participating entity, and the service data of the terminal group is sent by using the target multicast bearer.
  • the service participation entity When the indication information is the identifier of the target multicast bearer and the second indication information, the service participation entity sends the indication message to the terminal, where the second indication information is used to indicate the service participation entity, and is not located in the service area in the terminal group.
  • the terminal transmits the service data of the terminal group.
  • the present application provides a communication method that can be performed by a chip within a target service entity or a target service entity.
  • the method includes: the target service entity receives a request message from the service participating entity, where the request message includes an identifier of the service area and a group identifier, the request message is used to request to query the target multicast bearer, and the target multicast bearer is used in the service area, Sending service data of the terminal group corresponding to the group identifier; the target service entity sends a response message to the service participating entity, where the response message includes an identifier of the target multicast bearer.
  • the response message further includes first indication information, where the first indication information is used to indicate the service participating entity, and the service data of the terminal group is sent by the target multicast bearer.
  • the response message further includes second indication information, where the second indication information is used to indicate the service participating entity, and the service data of the terminal group is not sent to the terminal located in the service area in the terminal group.
  • the target service entity receives the request message from the service participating entity, where the request message includes the identifier of the service area and the group identifier, and the request message is used to request to query the target multicast bearer, and the target multicast bearer is used to send the group identifier corresponding to the service area.
  • the target service entity sends a response message to the service participating entity, and the response message includes indication information.
  • the indication information is an identifier of the target multicast bearer. or,
  • the indication information is an identifier of the target multicast bearer and the first indication information, where the first indication information is used to indicate the service participating entity, and the service data of the terminal group is sent by the target multicast bearer. or,
  • the indication information is an identifier of the target multicast bearer and the second indication information, where the second indication information is used to indicate the service participating entity, and the service data of the terminal group is not sent to the terminal located in the service area in the terminal group.
  • the target service entity when the target service entity receives the first notification message from the service participating entity, the first notification message is used to notify the target service entity, and the service participating entity stops transmitting the service data of the terminal group through the target multicast bearer.
  • the target service entity may send the indication information to the first service participant entity, where the indication information is used to indicate that the first service participant entity sends the service data of the terminal group by using the target multicast bearer.
  • the target service entity receives a second notification message from the second service participating entity, where the second notification message includes an identifier of the target multicast bearer and an identifier of the service area.
  • the application provides an apparatus, which may be a target service entity or a chip in a target service entity.
  • the device has the functionality to implement the various embodiments of the first aspect described above. This function can be implemented in hardware or in hardware by executing the corresponding software.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the target service entity when the device is a target service entity, the target service entity includes: a processing unit and a communication unit, the processing unit may be, for example, a processor, the communication unit may be, for example, a transceiver, and the transceiver includes a radio frequency circuit.
  • the service control entity further includes a storage unit, which may be, for example, a memory.
  • the storage unit stores a computer execution instruction
  • the processing unit is connected to the storage unit, and the processing unit executes a computer execution instruction stored by the storage unit, so that the target service entity executes the first A communication method of any of the aspects.
  • the chip when the device is a chip within a target service entity, the chip comprises: a processing unit and a communication unit, the processing unit being, for example, a processor, the communication unit being, for example, an input/output Interface, pin or circuit.
  • the processing unit may execute computer execution instructions stored by the storage unit to cause the communication method of any of the above aspects to be performed.
  • the storage unit is a storage unit in the chip, such as a register, a cache, etc., and the storage unit may also be a storage unit outside the chip, such as a read-only memory, in the target service entity. (read-only memory, ROM), other types of static storage devices that can store static information and instructions, random access memory (RAM), and the like.
  • the processor mentioned in any of the above may be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more An integrated circuit for controlling program execution of the communication method of the above first aspect.
  • CPU central processing unit
  • ASIC application-specific integrated circuit
  • the application provides an apparatus, which may be a service participating entity or a chip in a service participating entity.
  • the device has the functionality to implement the various embodiments of the second aspect described above. This function can be implemented in hardware or in hardware by executing the corresponding software.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the service participating entity when the device is a service participating entity, the service participating entity includes: a processing unit and a communication unit, and the processing unit may be, for example, a processor, and the communication unit may be, for example, a transceiver, The transceiver includes a radio frequency circuit.
  • the service participating entity further includes a storage unit, which may be, for example, a memory.
  • the storage unit stores a computer execution instruction
  • the processing unit is connected to the storage unit, and the processing unit executes a computer execution instruction stored by the storage unit, so that the service participating entity executes the second A communication method of any of the aspects.
  • the chip when the device is a chip in a service participating entity, the chip comprises: a processing unit and a communication unit, the processing unit being, for example, a processor, the communication unit being, for example, an input/output Interface, pin or circuit.
  • the processing unit may execute computer execution instructions stored by the storage unit to cause the communication method of any of the above second aspects to be performed.
  • the storage unit is a storage unit in the chip, such as a register, a cache, and the like, and the storage unit may also be a storage unit located outside the chip in the service participating entity, such as a ROM. Other types of static storage devices, RAM, etc. that store static information and instructions.
  • the processor mentioned in any of the above may be a general-purpose CPU, a microprocessor, an ASIC, or an integrated circuit of one or more programs for controlling the communication method of the above second aspect.
  • the application provides an apparatus, which may be a service control entity or a chip in a service control entity.
  • the device has the functionality to implement the various embodiments of the third aspect described above. This function can be implemented in hardware or in hardware by executing the corresponding software.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the service control entity when the device is a service control entity, the service control entity includes: a processing unit and a communication unit, the processing unit may be, for example, a processor, the communication unit may be, for example, a transceiver, and the transceiver includes a radio frequency circuit.
  • the service control entity further includes a storage unit, which may be, for example, a memory.
  • the storage unit stores a computer execution instruction
  • the processing unit is connected to the storage unit, and the processing unit executes a computer execution instruction stored by the storage unit, so that the service control entity executes the third A communication method of any of the aspects.
  • the chip when the device is a chip within a service control entity, the chip comprises: a processing unit and a communication unit, which may be, for example, a processor, which may be, for example, an input/output Interface, pin or circuit.
  • the processing unit may execute computer execution instructions stored by the storage unit to cause the communication method of any of the above third aspects to be performed.
  • the storage unit is a storage unit in the chip, such as a register, a cache, etc., and the storage unit may also be a storage unit located outside the chip in the service control entity, such as a ROM. Other types of static storage devices, RAM, etc. that store static information and instructions.
  • the processor mentioned in any of the above may be a general-purpose CPU, a microprocessor, an ASIC, or an integrated circuit of one or more programs for controlling the communication method of the above third aspect.
  • the application provides an apparatus, which may be a service participating entity or a chip in a service participating entity.
  • the device has the functionality to implement the various embodiments of the fourth aspect described above. This function can be implemented in hardware or in hardware by executing the corresponding software.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the service participating entity when the device is a service participating entity, the service participating entity includes: a processing unit and a communication unit, and the processing unit may be, for example, a processor, and the communication unit may be, for example, a transceiver, The transceiver includes a radio frequency circuit.
  • the service participating entity further includes a storage unit, which may be, for example, a memory.
  • the storage unit stores a computer execution instruction
  • the processing unit is connected to the storage unit, and the processing unit executes a computer execution instruction stored by the storage unit, so that the service participating entity executes the fourth A communication method of any of the aspects.
  • the chip when the device is a chip in a service participating entity, the chip comprises: a processing unit and a communication unit, the processing unit being, for example, a processor, the communication unit being, for example, an input/output Interface, pin or circuit.
  • the processing unit may execute computer execution instructions stored by the storage unit to cause the communication method of any of the above fourth aspects to be performed.
  • the storage unit is a storage unit in the chip, such as a register, a cache, and the like, and the storage unit may also be a storage unit located outside the chip in the service participating entity, such as a ROM. Other types of static storage devices, RAM, etc. that store static information and instructions.
  • the processor mentioned in any of the above may be a general-purpose CPU, a microprocessor, an ASIC, or an integrated circuit of one or more programs for controlling the communication method of the above fourth aspect.
  • the present application provides an apparatus, which may be a service participating entity or a chip in a service participating entity.
  • the device has the functionality to implement the various embodiments of the fifth aspect described above. This function can be implemented in hardware or in hardware by executing the corresponding software.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the service participating entity when the device is a service participating entity, the service participating entity includes: a processing unit and a communication unit, and the processing unit may be, for example, a processor, and the communication unit may be, for example, a transceiver, The transceiver includes a radio frequency circuit.
  • the service participating entity further includes a storage unit, which may be, for example, a memory.
  • the storage unit stores a computer execution instruction
  • the processing unit is connected to the storage unit, and the processing unit executes a computer execution instruction stored by the storage unit, so that the service participating entity executes the fifth A communication method of any of the aspects.
  • the chip when the device is a chip in a service participating entity, the chip comprises: a processing unit and a communication unit, the processing unit being, for example, a processor, the communication unit being, for example, an input/output Interface, pin or circuit.
  • the processing unit may execute computer execution instructions stored by the storage unit to cause the communication method of any of the above fifth aspects to be performed.
  • the storage unit is a storage unit in the chip, such as a register, a cache, and the like, and the storage unit may also be a storage unit located outside the chip in the service participating entity, such as a ROM. Other types of static storage devices, RAM, etc. that store static information and instructions.
  • the processor mentioned in any of the above may be a general-purpose CPU, a microprocessor, an ASIC, or an integrated circuit of one or more programs for controlling the communication method of the above fifth aspect.
  • the present application provides an apparatus, which may be a service control entity or a chip in a service control entity.
  • the device has the function of implementing the various embodiments of the sixth aspect described above. This function can be implemented in hardware or in hardware by executing the corresponding software.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the service control entity when the device is a service control entity, the service control entity comprises: a processing unit and a communication unit, the processing unit may be, for example, a processor, and the communication unit may be, for example, a transceiver, The transceiver includes a radio frequency circuit.
  • the service control entity further includes a storage unit, which may be, for example, a memory.
  • the storage unit stores a computer execution instruction
  • the processing unit is coupled to the storage unit, and the processing unit executes a computer execution instruction stored by the storage unit to cause the service control entity to perform the sixth A communication method of any of the aspects.
  • the chip when the device is a chip within a service control entity, the chip comprises: a processing unit and a communication unit, which may be, for example, a processor, which may be, for example, an input/output Interface, pin or circuit.
  • the processing unit may execute computer execution instructions stored by the storage unit to cause the communication method of any of the above sixth aspects to be performed.
  • the storage unit is a storage unit in the chip, such as a register, a cache, etc., and the storage unit may also be a storage unit located outside the chip in the service control entity, such as a ROM. Other types of static storage devices, RAM, etc. that store static information and instructions.
  • the processor mentioned in any of the above may be a general-purpose CPU, a microprocessor, an ASIC, or an integrated circuit of one or more programs for controlling the communication method of the sixth aspect.
  • the present application provides a communication method, which may be performed by a target service entity or a chip within a target service entity, where the target service entity may be a service control entity or a multicast bearer management entity.
  • the method includes: the target service entity receives a first request message from the first service participating entity, where the first request message includes an identifier of the target multicast bearer and a group identifier of the terminal group, where the first request message is used to request the target to be used. And transmitting, by the target service entity, the first service message to the first service participant entity, where the first service message is used to indicate that the first service participant entity uses the target multicast bearer to send the service data of the terminal group.
  • the first response message includes first indication information, where the first indication information is used to indicate that the first service participating entity uses the target multicast bearer to send the service data of the terminal group.
  • the target service entity receives the second request message from the second service participating entity, where the second request message includes the identifier of the target multicast bearer and the group identifier of the terminal group, and the second request message is used by the second request message.
  • the second response message includes second indication information, where the second indication information is used to indicate that the second service participating entity does not use the target multicast bearer to send the service data of the terminal group.
  • the target service entity receives the report message from the third service participating entity, and the report message includes the identifier of the target multicast bearer.
  • the reporting message further includes address information of the third service participating entity.
  • the present application provides a communication method that can be performed by a chip in a service participating entity or a business participating entity.
  • the method includes: the service participating entity sends a request message to the target service entity, where the request message includes an identifier of the target multicast bearer and a group identifier of the terminal group, and the request message is used to request to use the target multicast bearer to send the service data of the terminal group.
  • the service participating entity receives the response message from the target service entity, and the response message is used to indicate that the service participating entity uses the target multicast bearer to transmit the service data of the terminal group.
  • the response message includes first indication information, where the first indication information is used to indicate that the service participating entity uses the target multicast bearer to send the service data of the terminal group.
  • the service participating entity uses the target multicast bearer to send the service data of the terminal group.
  • the application provides a device, which may be a target service entity or a chip in a target service entity.
  • the device has the function of implementing the various embodiments of the thirteenth aspect described above. This function can be implemented in hardware or in hardware by executing the corresponding software.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the service control entity when the device is a target service entity, the service control entity includes: a processing unit and a communication unit, the processing unit may be, for example, a processor, the communication unit may be, for example, a transceiver, and the transceiver includes a radio frequency circuit.
  • the service control entity further includes a storage unit, which may be, for example, a memory.
  • the storage unit stores a computer execution instruction
  • the processing unit is coupled to the storage unit, and the processing unit executes a computer execution instruction stored by the storage unit to cause the target service entity to execute the tenth A communication method of any of the three aspects.
  • the chip when the device is a chip within a target service entity, the chip comprises: a processing unit and a communication unit, the processing unit being, for example, a processor, the communication unit being, for example, an input/output Interface, pin or circuit.
  • the processing unit may execute a computer-executed instruction stored by the storage unit to cause the communication method of any of the above-described thirteenth aspects to be performed.
  • the storage unit is a storage unit in the chip, such as a register, a cache, etc., and the storage unit may also be a storage unit located outside the chip in the service control entity, such as a ROM. Other types of static storage devices, RAM, etc. that store static information and instructions.
  • the processor mentioned in any of the above may be a general-purpose CPU, a microprocessor, an ASIC, or an integrated circuit of one or more programs for controlling the communication method of the thirteenth aspect.
  • the present application provides an apparatus, which may be a service participating entity or a chip in a service participating entity.
  • the device has the function of implementing the embodiments of the fourteenth aspect described above. This function can be implemented in hardware or in hardware by executing the corresponding software.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the service participating entity when the device is a service participating entity, the service participating entity includes: a processing unit and a communication unit, and the processing unit may be, for example, a processor, and the communication unit may be, for example, a transceiver, The transceiver includes a radio frequency circuit.
  • the service participating entity further includes a storage unit, which may be, for example, a memory.
  • the storage unit stores a computer execution instruction
  • the processing unit is connected to the storage unit, and the processing unit executes a computer execution instruction stored by the storage unit, so that the service participating entity executes the tenth A communication method of any of the four aspects.
  • the chip when the device is a chip in a service participating entity, the chip comprises: a processing unit and a communication unit, the processing unit being, for example, a processor, the communication unit being, for example, an input/output Interface, pin or circuit.
  • the processing unit may execute computer execution instructions stored by the storage unit to cause the communication method of any of the above fourth aspects to be performed.
  • the storage unit is a storage unit in the chip, such as a register, a cache, and the like, and the storage unit may also be a storage unit located outside the chip in the service participating entity, such as a ROM. Other types of static storage devices, RAM, etc. that store static information and instructions.
  • the processor mentioned in any of the above may be a general-purpose CPU, a microprocessor, an ASIC, or an integrated circuit of one or more programs for controlling the communication method of the above fourteenth aspect.
  • the present application also provides a computer readable storage medium having instructions stored therein that, when executed on a computer, cause the computer to perform the methods described in the above aspects.
  • the present application also provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the methods described in the above aspects.
  • FIG. 2 is a possible system architecture to which the present application applies;
  • FIG. 3 is a schematic diagram of a communication method provided by the present application.
  • FIG. 4 is a schematic diagram of another communication method provided by the present application.
  • FIG. 5 is a schematic diagram of another communication method provided by the present application.
  • FIG. 6 is a schematic diagram of another communication method provided by the present application.
  • FIG. 7 is a schematic diagram of another communication method provided by the present application.
  • FIG. 8 is a schematic diagram of another communication method provided by the present application.
  • Figure 9 is a schematic diagram of a device provided by the present application.
  • Figure 10 is a schematic view of another apparatus provided by the present application.
  • Figure 11 is a schematic diagram of a device provided by the present application.
  • FIG. 12 is a schematic diagram of another apparatus provided by the present application.
  • FIG. 13 is a schematic diagram of another communication method provided by the present application.
  • Figure 14 is a schematic view of another apparatus provided by the present application.
  • Figure 15 is a schematic view of another apparatus provided by the present application.
  • Figure 16 is a schematic diagram of another apparatus provided by the present application.
  • Figure 17 is a schematic view of another apparatus provided by the present application.
  • Figure 18 is a schematic view of another apparatus provided by the present application.
  • Figure 19 is a schematic view of another apparatus provided by the present application.
  • FIG. 21 is a schematic diagram of another apparatus provided by the present application.
  • the communication method of the present application can be performed by a device.
  • the device may be a service control entity, a multicast bearer management entity or a service participating entity, or a chip in a service control entity, a chip in a multicast bearer management entity, or a chip in a service participating entity.
  • the present application uses a device as a service control entity, a multicast bearer management entity, or a service participating entity as an example to describe a communication method
  • the device is a chip in a service control entity, and a chip in a multicast bearer management entity.
  • the implementation method of the chip in the service participating entity reference may be made to the specific description of the communication method of the service control entity, the multicast bearer management entity, or the service participating entity, and the description is not repeated.
  • the MC service entity has the following functions: receiving the uplink unicast data of the terminal; and transmitting the downlink data to the terminal in the terminal group by using the unicast or multicast mode, where the data may be control signaling, such as a group in the MCPTT service. Group call request message. It can also be media data such as voice, video, data, etc. It can also be media plane control signaling, such as a voice request message in the MCPTT service. Supports the continuity of the downlink data received by the terminal between unicast and multicast transmission modes.
  • the MC service entity is divided into functions and logically divided into a service control entity and a service participating entity.
  • the service control entity is a logical entity defined from the perspective of group call management, and assumes the main control function in the group call, directly or indirectly obtains the location information of the terminal group member, and directly or indirectly receives the multicast bearer quality from the terminal side.
  • the service control entity may, according to the location information of the terminal group member, receive the multicast bearer quality report, and decide whether to send data to the terminal group member by using unicast or multicast.
  • the service control entity includes, for example, a Controlling MC service server.
  • the service participating entity is used for registering the terminal and sending the service data to the terminal, that is, the terminal is registered in the service participating entity, and the service participating entity is responsible for routing the request or response sent by the group member in the group call, and the service control entity The request message is routed to the group members. It can be understood that the service participating entity directly communicates with the terminal, and the service participating entity includes, for example, a Participating MC service server.
  • the multicast bearer includes a multicast bearer and a broadcast bearer; in the fourth generation (4th generation, 4G), the multicast bearer is also called a multimedia broadcast. /Multicast Broadcast/Multicast Service (MBMS) bearer. In this application, the multicast bearer will be used uniformly.
  • MBMS Multicast Broadcast/Multicast Service
  • the MC service server may be an MCPTT server, an MCVideo server, an MCData server, or another type of server having similar functions.
  • the Controlling MC service server may be a controlling MCPTT server, a controlling MCVideo server, a controlling MCData server or other types of servers with similar functions in a specific service.
  • the participating MC service server may be a participating MCPTT server, a participating MCVideo server, a participating MCData server or other types of servers having similar functions in a specific service, and the present invention is not limited.
  • the service participating entity has a total of three terminals, namely, terminal 1, terminal 2, and terminal 3.
  • the communication of the terminal in the terminal group 1 is controlled by a service control entity, for example, Controlled by the service control entity 1.
  • terminal group 2 ⁇ terminal 2, terminal 3 ⁇
  • communication within the terminal group 2 is controlled by the service control entity 2.
  • terminal group 3 ⁇ terminal 1, terminal 2, terminal 3 ⁇ , and communication within the terminal group 3 is controlled by the service control entity 3.
  • one service participating entity may correspond to multiple service control entities.
  • each terminal group formed by terminals in one service participating entity may correspond to one service control entity, and therefore, how many terminal groups may correspond to How many service control entities, each of which controls the communication of terminals within a terminal group.
  • the service participating entity and the service control entity are logically divided. On the physical entity, the service participating entity and the service control entity may be two physical entities or part of two physical entities, respectively. Is integrated in the same physical entity.
  • the terminals in the multiple service participating entities form a terminal group, and the terminal group is controlled by a service control entity, and the service control entity may be integrated into any of the service participating entities, or may be physically independent of each Business engagement entity.
  • the system architecture further includes a multicast bearer management entity, where the multicast bearer management entity is used to manage the multicast or broadcast bearer used in the system, for example, storing multicast bearer or broadcast bearer related information, including multiple The identifier of the broadcast bearer, the identifier of the service area, and the correspondence between the two, and also records the multicast bearer being used and the identifier of the service participating entity that is using the multicast bearer, and can also record the number of uses being used.
  • the bearer bears the identity of the corresponding terminal group, and the like.
  • the multicast bearer management entity may also be referred to as a multicast bearer control entity, and may be, for example, a multicast bearer management server.
  • the function of the multicast bearer management entity may be integrated into the service control entity, that is, the multicast bearer management entity may be cancelled, and the function of the multicast bearer entity is integrated in the service control entity.
  • the function of the multicast bearer management entity may be integrated in the service control entity according to actual needs, or the service control entity and the multicast bearer management entity may be separately set.
  • the function of the multicast bearer management entity may also be integrated in the service participating entity. In this case, the service participating entity and the multicast bearer management entity may be integrated and deployed in the same physical network device, or may be the service participating entity and the multicast bearer management. Entities are set separately.
  • the present application is separately described by taking a separate setting of a service control entity, a service participating entity, and a multicast bearer management entity.
  • the service participating entity 1, the service participating entity 2, and the service participating entity 3 respectively manage a plurality of registered terminals, and the terminal 1, the terminal 2, the terminal 3, and the service participating entity 2 in the current service participating entity 1
  • it can be an MCPTT client, an MCVideo client, an MCData client, or a service client with similar functions.
  • an application scenario of the system shown in FIG. 2 may be: when a traffic accident occurs in a certain place, the traffic police, the hospital, and the public security need to be involved at the same time.
  • a communication device used by the traffic police such as a walkie-talkie
  • Participating entity 1 the communication device used by the hospital, such as the terminal display device, the walkie-talkie, etc.
  • the communication device used by the public security such as a walkie-talkie
  • the terminal 1 to the terminal 7 constitutes a terminal group A.
  • the downlink data of the group communication is downlink data transmitted by the service control entity to the terminal group A.
  • the service control entity or the service participating entity may determine whether the downlink group communication data is transmitted by using a unicast or a multicast mode. If multicast is used, the terminal group communication downlink data may be sent by using the multicast bearer.
  • the existing implementation manner is that each service participating entity independently decides to use and/or establish a multicast bearer according to the location of the terminal in the registered terminal group.
  • each terminal in the terminal group can trigger the service participating entity to use or establish a multicast bearer, so that multiple different multicast bearers transmit the same content in the same service area, resulting in Unnecessary multicast bearer resources are wasted.
  • each terminal in the terminal group can trigger the service entity to use or establish a multicast bearer, and the service participating entities use the same multicast bearer. At the same time, receiving the same service data sent by multiple business participating entities.
  • the present application proposes two communication methods for implementing the system architecture shown in FIG. 2 to save resources and improve communication quality.
  • FIG. 3 is a schematic diagram of a communication method provided by the present application. The method includes:
  • Step 301 The service control entity acquires an identifier of the multicast bearer.
  • the service control entity decides The downlink data of the terminal group is transmitted by using the multicast bearer in the service area.
  • the service control entity acquires the identifier of the multicast bearer, and the multicast bearer is used to transmit the service data of the terminal in the service area.
  • each multicast bearer is represented by an identifier of a multicast bearer, and each multicast bearer can be used to transmit service data of one or more terminal groups.
  • the service control entity obtains the identifier of the multicast bearer corresponding to the terminal group in the service area, and can also be understood that the service control entity can obtain the terminal group from the one or more multicast bearers in the service area.
  • the service control entity may determine the number of terminals located in the same service area according to the terminal location information reported by the terminal in the terminal group, and further determine the terminal group if the number of terminals in the same service area meets the preset condition.
  • a terminal located in the service area uses a multicast bearer to transmit service data.
  • the service data may be service control signaling, such as MCPTT/MCVideo call control message; or media plane control signaling, such as MCPTT call rights control message (such as voice rights occupation message), MCVideo transmission control message (such as media reception notification message) Or media data such as voice, video, files, etc.
  • service control signaling such as MCPTT/MCVideo call control message
  • media plane control signaling such as MCPTT call rights control message (such as voice rights occupation message), MCVideo transmission control message (such as media reception notification message)
  • media data such as voice, video, files, etc.
  • the location information may be geographic location information, or latitude and longitude information, or a cell identity, or a service area identifier, or a combination of two or more of the above.
  • the service control entity determines, according to the configuration policy, that the terminal located in the service area in the terminal group uses the multicast bearer to transmit service data, where the configuration policy indicates that the multicast bearer transmission terminal is always used in the service area.
  • the data of the group, or the configuration policy indicates that the data of the multicast bearer transmission terminal group is always used in the service area for a certain period of time.
  • Step 302 The service control entity sends a first indication message to the first service participant entity associated with the terminal group, where the first service participant entity receives the first indication message from the service control entity.
  • the first indication message is used to indicate that the first service participating entity sends the service data of the terminal group in the service area by using the multicast bearer corresponding to the identifier of the multicast bearer.
  • Step 303 The service control entity sends a second indication message to the second service participant entity associated with the terminal group, where the second service participant entity receives the second indication message from the service control entity.
  • the second indication message is used to indicate the second service participating entity, and does not send the service data of the terminal group to the terminal located in the service area in the terminal group.
  • the first indication message may be a broadcast bearer use message or a broadcast bearer use notification message.
  • the first indication message includes an identifier of the service area, an identifier of the multicast bearer, an identifier of the terminal group, and an indication of sending the service data.
  • the service control entity indicates, by using the first indication message, that the first service participating entity is allowed to send the service data of the terminal group in the service area by using the multicast bearer.
  • the service control entity indicates, by using the first indication message, that the first service participating entity can send the service data of the terminal group in the service area by using the multicast bearer.
  • the first indication message is used to indicate that the first service participating entity has the capability of transmitting the service data of the terminal group. As for when the first service participating entity sends service data to the terminal group terminal, it depends on the actual situation. In an implementation manner, after receiving the first indication message, the first service participating entity immediately sends the service data in the service area. In another implementation manner, after the first service participating entity receives the first indication message, the service data is not immediately sent in the service area, but the first service participation entity receives another indication message sent by the service control entity. The indication message is used to indicate that the first service participating entity immediately sends the service data in the service area. At this time, the first service participating entity starts to send the service data in the service area.
  • the second indication message in the foregoing step 303 may be a broadcast bearer use message or a broadcast bearer use indication message.
  • the second indication message includes an identifier of the service area, an identifier of the multicast bearer, an identifier of the terminal group, and a service data sending indication.
  • the second indication message is used to indicate that the second service participating entity does not send the service data of the terminal group to the terminal located in the service area in the terminal group.
  • the second indication message is used to indicate the second service participating entity, and cannot send the service data of the terminal group to the terminal located in the service area in the terminal group.
  • the second indication message is used to indicate that the second service participating entity does not allow the service data of the terminal group to be sent to the terminal located in the service area in the terminal group.
  • the service data transmission indication can be expressed by using 1 bit. For example, when the service data transmission indication is “1”, it indicates that the service data of the terminal group is transmitted through the multicast bearer in the service area. When the service data transmission indication is “0”, it indicates that the service area does not send the service data of the terminal group to the terminal located in the service area in the terminal group.
  • the service data transmission indication in the first indication information is “1”
  • the service data transmission indication in the second indication information is “0”.
  • the service data transmission indication in the first indication information is “0”, and the service data transmission indication in the second indication information is “1”. This application is not limited.
  • step 303 after the second service participating entity receives the second indication message, if the second service participating entity is currently transmitting the service data of the terminal group to the terminal located in the service area in the terminal group, the sending is stopped. If the second service participating entity does not currently send the service data of the terminal group to the terminal located in the service area in the terminal group, the service data of the terminal group is not sent to the terminal located in the service area in the terminal group.
  • the first indication message includes an identifier of the service area, an identifier of the multicast bearer, and an identifier of the terminal group.
  • the default first service participating entity may send the service data in the service area through the multicast bearer.
  • one or a combination of the identifier of the service area, the identifier of the multicast bearer, and the identifier of the terminal group may be regarded as an implicit service data transmission indication.
  • the second indication message includes an identifier of the service area, an identifier of the multicast bearer, an identifier of the terminal group, and a placeholder information, where the placeholder information may be any information, when the second service participating entity receives the When the information is occupied, it is determined that the service data of the terminal group is not sent to the terminal located in the service area in the terminal group.
  • the first indication message includes an identifier of the service area, an identifier of the multicast bearer, an identifier of the terminal group, and location information, when the first service participating entity receives the first indication information, Obtaining the placeholder information, the placeholder information may be any information.
  • the first service participating entity receives the placeholder information, it determines that the service data can be sent by using the multicast bearer in the service area.
  • the second indication information includes the identifier of the service area, the identifier of the multicast bearer, and the identifier of the terminal group, and does not include the placeholder information, according to the pre-agreed, the default second service participating entity is not located in the terminal group.
  • the terminal in the service area sends the service data of the terminal group.
  • the first service participating entity is different from the second service participating entity. At least one terminal in the terminal group is registered in the first service participating entity, and at least one terminal in the terminal group is registered in the second service participating entity.
  • the first service participating entity is a service participating entity in the service participating entity registered by the terminal in the terminal group.
  • the second service participating entity is a service participating entity other than the first service participating entity among the service participating entities registered by the terminal in the terminal group.
  • the service participating entities registered by the terminal of the terminal group A are the service participating entity 1, the service participating entity 2, and the service participating entity 3, and may be:
  • the first service participating entity is: the business participating entity 1
  • the second business participating entity is: the business participating entity 2, the business participating entity 3, or
  • the first service participating entity is: the business participating entity 2
  • the second business participating entity is: the business participating entity 1, the business participating entity 3, or
  • the first service participating entity is: the business participating entity 3
  • the second business participating entity is: the business participating entity 1, the business participating entity 2.
  • the first service participating entity sends a service reception indication message to the terminal, where the service reception indication message includes an identifier of the multicast bearer, and optionally, an identifier of the terminal group.
  • the first service participating entity sends the indication message to the service area by using a multicast transmission mode.
  • the terminal that receives the service reception indication message may include some or all terminals in the terminal group. Other groups of terminals may be included, and these terminals may be registered by the first service participating entity or may be registered by other business participating entities.
  • the implementation manner is understood to be that the first service participating entity sends a service reception indication message to some or all terminals of the service area in a service area by using a multicast transmission mode.
  • the first service participating entity sends the indication message to the terminal registered by the first service participating entity in the terminal group by using a unicast mode.
  • the first service participating entity sends the service reception indication message to the terminal group that is registered by the first service participation entity and is currently located in the service area by using the unicast mode.
  • the service receiving indication message is used to instruct the terminal to receive the service data by using the multicast bearer. If the terminal receiving the message is not in the service area, the service data cannot be received. If the terminal that receives the message is not a terminal in the terminal group, it is processed by other processing methods, such as dropping the data packet after attempting to decrypt the content of the message, or determining that it is not a terminal in the terminal group. Discard the packet.
  • the second service participating entity sends a service reception indication message to the terminal, and the service reception indication message may also be referred to as a fourth indication message.
  • the service receiving indication message includes an identifier of the multicast bearer, and optionally, an identifier of the terminal group.
  • the function and the implementation manner of the service receiving indication message are the same as the function and the implementation manner of the service receiving indication message sent by the first service participating entity to the terminal, and the foregoing description is omitted, and details are not described herein again.
  • the service control entity instructs the first service participating entity to send the service data of the terminal group through the multicast bearer in the service area, and indicates that the second service participating entity is not located in the service group in the terminal group.
  • the terminal transmits the service data of the terminal group, so that the terminal located in the service area in the terminal group receives the service data of the terminal group only from the first service participating entity, thereby avoiding receiving the same service from multiple service participating entities. Data, saving terminal overhead.
  • the terminal group A includes the terminal 1 to the terminal 7, and it is assumed that only the terminal 1 to the terminal 6 are located in the service area, and the terminal 7 is not in the service area.
  • the service control entity decides to use the multicast bearer to send the service data in the service area, if the service control entity determines that the service participating entity 1 is the first service participating entity, the service participating entity 2 and the service participating entity 3 are the second service participating entity. Then have the following steps:
  • Step 1 The service control entity obtains the identifier of the multicast bearer, and determines to use the multicast bearer to send the service data.
  • Step 2 The service control entity sends a first indication message to the service participating entity 1.
  • the first indication message is used to indicate that the service participating entity 1 sends the service data of the terminal group through the multicast bearer.
  • the service participation entity 1 After receiving the first indication message, the service participation entity 1 also sends a service reception indication message to the terminal 1 to the terminal 3 respectively. That is, the service participating entity 1 notifies the terminal 1 to the terminal 3 to receive the service data through the multicast bearer.
  • Step 3 The service control entity sends a second indication message to the service participating entity 2 and the service participating entity 3.
  • the second indication message is used to indicate the service participating entity 2 and the service participating entity 3, and does not send the service data of the terminal group to the terminal located in the service area in the terminal group, that is, the service participating entity 2 and the service participating entity are indicated. 3
  • the service data is not transmitted to the terminal 1 to the terminal 6.
  • the service reception indication message (or the fourth indication message) may be separately sent to the terminal 4 to the terminal 5. That is, the service participating entity 2 notifies the terminal 4 to the terminal 5 to receive the service data through the multicast bearer.
  • the service reception indication message (or the fourth indication message) may be sent to the terminal 6. That is, the service participating entity 3 notifies the terminal 6 to receive the service data through the multicast bearer.
  • Step 4 The service participating entity 1 transmits the service data of the terminal group in the service area by using the multicast bearer, and the terminal 1 to the terminal 6 receive the service data by using the multicast bearer.
  • the terminal 1 to the terminal 6 located in the service area of the terminal group A receive service data only from the service participating entity 1, thereby avoiding receiving the same service data from multiple service participating entities, thereby saving Terminal overhead.
  • the method for the service control entity to obtain the identifier of the multicast bearer may include, for example:
  • Step A The service control entity sends a query message to the multicast bearer management entity, and the multicast bearer management entity receives the query message from the service control entity.
  • the query message includes an identifier of the service area, and the query message is used to request to query a multicast bearer corresponding to the service area.
  • Step B The multicast bearer management entity sends a response message to the service control entity, and the service control entity receives the response message from the multicast bearer management entity.
  • the process ends; when the response message does not include the identifier of the multicast bearer, go to step C.
  • the response message includes the identifier of the multicast bearer, indicating that the multicast bearer can be used, and can be used to send downlink service data in the service area, so the service control entity successfully obtains the identifier of the multicast bearer in the service area.
  • the service control entity determines that the identifier of the multicast bearer is not acquired.
  • Step C The service control entity sends a request message to the third service participating entity associated with the terminal group, and the third service participating entity receives the request message from the service control entity.
  • the third service participating entity is any one of the service participating entities associated with the terminal group.
  • the third service participating entity may be the service participating entity 1 or the service participating entity 2 Or it can be a business participation entity 3.
  • the request message includes an identifier of the service area, and the request message is used to request the third service participating entity to establish a multicast bearer in the service area corresponding to the identifier of the service area.
  • the request message may also be referred to as a broadcast bearer setup request message or a broadcast bearer request message.
  • the third service participating entity is instructed to establish a multicast bearer in the service area.
  • Step D The third service participating entity sends a notification message to the multicast bearer management entity, and the multicast bearer management entity receives the notification message from the third service participating entity.
  • the notification message includes an identifier of the multicast bearer, an identifier of the service area, and information related to the multicast bearer.
  • the foregoing notification message is sent to the multicast bearer management entity.
  • Step E The third service participating entity sends a response message to the service control entity, and the service control entity receives the response message from the third service participating entity.
  • the response message includes an identification of the multicast bearer. That is, after the third service participating entity establishes the multicast bearer, on the one hand, the identifier of the multicast bearer is sent to the multicast bearer management entity for storage, and on the other hand, the identifier of the multicast bearer is sent to the service control entity, thereby The service control entity can successfully obtain the identifier of the multicast bearer. At this point, the process ends.
  • the response message includes notification information
  • the notification information is used to notify the service control entity that the multicast bearer has been successfully established and the identifier of the multicast bearer and related information is sent to the multicast bearer management entity. Therefore, when the service control entity receives the notification information, the above steps A and B are further performed, so that the identifier of the multicast bearer can be acquired. At this point, the process ends.
  • the service control entity requests to establish a multicast bearer for the terminal group corresponding to the identifier of the terminal group, and the notification message of step D is further
  • the identifier of the terminal group may be included, and in the first implementation manner of the step E, the response message includes not only the identifier of the multicast bearer but also the identifier of the terminal group.
  • steps A to E above may also be performed as follows:
  • An implementation manner is that only the step A and the step B are performed, and after the identifier of the multicast bearer is successfully obtained or failed from the multicast bearer management entity, the process ends, where the multicast bearer is obtained from the multicast bearer management entity. If the identity fails, it means that the transmission mode of the multicast bearer is no longer used.
  • step C and step D are performed first, that is, the multicast bearer is first established by the third service participating entity, and then the established multicast bearer is sent to the multicast bearer management entity, and then step A and step B are performed. And obtaining, by the service control entity, the multicast bearer established by the third service participating entity from the multicast bearer management entity.
  • step C and step D are performed first, that is, the multicast bearer is first established by the third service participating entity, and then the established multicast bearer is sent to the multicast bearer management entity, and then step E is performed, and steps are performed.
  • the response message of the E includes the multicast bearer established by the third service participating entity, that is, the third service participating entity directly feeds back to the service control entity after establishing the multicast bearer.
  • step C is performed first, that is, the multicast bearer is first established by the third service participating entity, and then step E is performed, and the response message of step E includes the multicast bearer established by the third service participating entity. That is, after the third service participating entity establishes the multicast bearer, it directly feeds back to the service control entity. And, further, the established multicast bearer is sent by the service control entity to the multicast bearer management entity for storage.
  • the third service participating entity includes the established multicast bearer, and the multicast bearer satisfies the request of the service control entity, it does not need to be established, but is directly sent to the service control entity, and/ Or, multicast bearer management entity. Further, if the third service participating entity fails to acquire the multicast bearer and fails to establish a multicast bearer, return an empty message to the service control entity, or return a message indicating failure.
  • step 303 step 304 and step 305 are further included.
  • Step 304 The first service participating entity sends a notification message to the service control entity, where the service control entity receives the notification message from the first service participating entity.
  • the notification message is used to notify that the first service participating entity stops transmitting the service data of the terminal group through the multicast bearer.
  • the first service participating entity sends a notification to the service control entity, because the first service participating entity needs to stop the multicast bearer and send the service data of the terminal group in the service area for some reasons, such as a fault or an overload.
  • the message informs that the service data will be stopped in the service area through the multicast bearer.
  • Step 305 The service control entity sends a third indication message to the second service participating entity, where the second service participating entity receives the third indication message from the service control entity.
  • the third indication message is used to indicate the second service participating entity, and sends the service data of the terminal group to the terminal located in the service area and registered on the second service participating entity in the terminal group.
  • each of the second service participating entities is separately located in the service area in the terminal group, and is registered in its own terminal, and transmits the service data of the terminal group.
  • the method of sending is determined by itself, for example, it can be unicast or multicast.
  • the first service participating entity is the service participating entity 1
  • the second service participating entity is the service participating entity 2 and the service participating entity 3.
  • the terminal 1 to the terminal 6 are located in the service area.
  • the service participating entity 1 transmits the service data of the terminal group through the multicast bearer, and the service participating entity 2 and the service participating entity 3 do not send the service data to the terminal 1 to the terminal 6. That is, the terminal 1 to the terminal 6 receive the service data of the terminal group from the service participating entity 1 through the multicast bearer.
  • the service participant entity 1 When the service participant entity 1 sends a notification message to the service control entity to notify the service control entity, the service participant entity 1 stops in the service area and uses the multicast bearer to send service data, so that the terminal 1 to the terminal 6 cannot pass the multicast bearer and the slave service
  • the participating entity 1 receives the service data of the terminal group.
  • the service control entity may send a third indication message to the service participating entity 2 and the service participating entity 3, where the third indication message includes an identifier of the service area.
  • the service participant entity 2 After receiving the third indication message, the service participant entity 2 determines to transmit the service data of the terminal group to the terminal 4 and the terminal 5 by using the unicast or multicast mode. When it is determined that the multicast mode can be used for transmission, the service participating entity 2 also requests the service control entity corresponding to the terminal group formed by the terminal 4 and the terminal 5 to identify the multicast bearer, and uses the requested multicast bearer. The service data is broadcasted to the terminal 4 and the terminal 5 by means of broadcasting. When it is determined that the unicast mode is used for transmission, the service participating entity 2 sends the service data of the terminal group to the terminal 4 and the terminal 5 in a unicast manner.
  • the service participant entity 3 After receiving the third indication message, the service participant entity 3 transmits the service data of the terminal group to the terminal 6 in a unicast manner.
  • the service information may be sent to all the service participating entities corresponding to the multicast bearer, for example, the indication.
  • the information is to stop using the multicast bearer message, and is used to indicate that all service participating entities use the unicast transmission mode to register the terminal in the terminal group to transmit the service data.
  • the service control entity when it decides to send the service data by using the multicast bearer in the service area, it sends the indication information to the service participant entity 1 to the service participant entity 3, respectively, indicating that the participant entity 1 uses the unicast mode to the terminal.
  • the terminal 3 sends the service data of the terminal group, and the participating entity 2 sends the service data of the terminal group to the terminal 4 to the terminal 5 by using the unicast mode, and instructs the participating entity 3 to send the terminal group to the terminal 6 by using the unicast mode.
  • Business data when the service control entity decides to send the service data by using the multicast bearer in the service area, it sends the indication information to the service participant entity 1 to the service participant entity 3, respectively, indicating that the participant entity 1 uses the unicast mode to the terminal.
  • the terminal 3 sends the service data of the terminal group
  • the participating entity 2 sends the service data of the terminal group to the terminal 4 to the terminal 5 by using the unicast mode, and instructs the participating entity 3 to send the terminal group to
  • the service information may be sent to all the service participating entities corresponding to the multicast bearer, for example, the indication.
  • the information is to stop using the multicast bearer message, and is used to indicate that each service participating entity separately registers with the terminal group in its own terminal to send the service data.
  • the way to send data can be unicast or multicast. That is, in this implementation, each service participating entity determines the manner in which the data is transmitted.
  • the service control entity decides to send the service data by using the multicast bearer in the service area
  • the service information is sent to the service participant entity 1 to the service participant entity 3, respectively, and the participant entity 1 is directed to the terminal 1 to the terminal 3.
  • the service data of the terminal group is transmitted in the unicast mode or the multicast mode, and is determined by the service participant entity 1 to instruct the participant entity 2 to send the service data of the terminal group to the terminal 4 to the terminal 5, whether the unicast mode or the unicast mode is used.
  • the broadcast mode is determined by the service participating entity 2, and the participating entity 3 is instructed to send the service data of the terminal group to the terminal 6, and the service participating entity 3 decides to transmit in the unicast mode.
  • the service control entity may control one of the service participating entities corresponding to the multicast bearer to send the service data of the terminal group, thereby preventing multiple service participating entities from simultaneously transmitting the same service data, thereby saving Resources, and improve communication quality; on the other hand, when the service participating entity stops transmitting service data, each service participating entity separately sends service data to the terminal registered in its own, so that the terminal can receive the service data in time.
  • FIG. 4 is a schematic diagram of another communication method provided by the present application. Includes the following steps:
  • Step 401 The service participating entity sends a request message to the target service entity, where the target service entity receives the request message from the service participating entity.
  • the target service entity is a service control entity or a multicast bearer management entity.
  • the request message includes an identifier of the service area for requesting to query the target multicast bearer, and the target multicast bearer is used to send the service data of the terminal group in the service area.
  • the target service entity After receiving the request message of the service participating entity, the target service entity queries the target multicast bearer and obtains the identifier of the target multicast bearer, which may be obtained locally, for example, the target multicast bearer may be pre-established, or It is dynamically newly established after receiving the 401 message, or is reported to the target control entity after the other business participating entities are established, or the target control entity requests other business participating entities to establish and save, or may be from other multicasts.
  • the bearer management entity obtains, of course, if the target multicast bearer is not obtained, any service participating entity may also be requested to establish the target multicast bearer.
  • the target service entity can obtain the identifier and related information of the target multicast bearer.
  • step 402 If no other service participating entity is using the target multicast bearer to send service data, or is ready to use the target multicast bearer to send service data, step 402 is performed.
  • Step 402 The target service entity sends a response message to the service participating entity, and the service participating entity receives the response message from the target service entity.
  • the target service entity carries the identifier of the target multicast bearer in the response message and sends the identifier to the service participating entity.
  • steps 401 and 402 For the above steps 401 and 402, the following steps 4011 to 4014 can be completed, that is, steps 4011 to 4014 as a whole, and the steps 401 to 402 can be replaced.
  • steps 401 and 402 For the above steps 401 and 402, the following steps 4013 to 4014 can be completed, that is, steps 4013 to 4014 as a whole, and steps 401 to 402 can be replaced.
  • Step 4011 The service participating entity sends a first request message to the target service entity, where the target service entity receives the first request message from the service participating entity.
  • the first request message includes an identifier of a service area, the first request message is used to request to query a target multicast bearer, and the target multicast bearer is used to send service data of a terminal group in a service area.
  • the target multicast bearer is a bearer that can provide a multicast bearer transmission service to the terminal group in the service area.
  • Step 4012 The target service entity sends a first response message to the service participating entity, and the service participating entity receives the first response message from the target service entity.
  • the first response message includes an identifier of the target multicast bearer.
  • the first response message may further include part or all of the following parameters of the target multicast bearer: a user plane address and a port number of the target multicast bearer, a service area corresponding to the target multicast bearer, and a target multicast. Carry the corresponding radio frequency and so on.
  • the first response message may further include address information of a service participating entity that establishes the target multicast bearer, where the address information may be an internet protocol version 4 (IPv4) address, which may be the Internet.
  • IPv4 internet protocol version 4
  • IPv6 internet protocol version 6, IPv6 address can be a fully qualified domain name (FQDN) or a uniform resoure locator (URL).
  • the address information may be used by another service participating entity that discovers and uses the target multicast bearer from the target service entity to forward the service data to the service participating entity that establishes the target multicast bearer, and the service participating entity that establishes the target multicast bearer will The received service data (media plane data and control signaling) is sent on the target multicast bearer.
  • the address of the service participating entity that establishes the target multicast bearer may be the address of the target service entity.
  • the target multicast bearer is any one of the service participating entities (such as the third service participating entity, and the third service participating entity is the service participating entity registered in the terminal group).
  • the business participation entity establishes, before the above step 4011, the following steps may also be included:
  • the third service participating entity sends a report message to the target service entity, where the report message includes the identifier of the target multicast bearer, and optionally, the address information of the third service participating entity.
  • the target service entity can obtain and store the information of the target multicast bearer, for example, the identifier of the target multicast bearer, so that after the service participating entity sends the first request message to the target service entity, the target service entity can The identifier of the target multicast bearer is obtained locally, and is carried in the first response message and sent to the service participating entity.
  • Step 4013 The service participating entity sends a second request message to the target service entity, where the target service entity receives the second request message from the service participating entity.
  • the second request message includes an identifier of the target multicast bearer and a group identifier of the terminal group.
  • the second request message may be used to request the target service entity to establish a binding relationship between the identifier of the target multicast bearer and the group identifier. That is, the target service entity is indicated, and the service participating entity uses the target multicast to carry the service data of the transmission terminal group. It can be understood that the second request message can be used to request to use the target multicast bearer to send the service data of the terminal group.
  • the multiple service participating entities may be coordinated to use the target multicast bearer. For example, when there are other service participating entities requesting to transmit the service data of the communication group of the same group identity in the same service area, the target service entity may notify the other service participating entity that the above-mentioned service participating entity is using the target multicast bearer.
  • the service data of the terminal group is transmitted in the service area.
  • the target service entity sends the identifier of the target multicast bearer to the other service participating entity, and indicates that the other service participating entity does not need to send the service data of the terminal group to the terminal located in the service area in the terminal group.
  • the target service entity receives a request message from the other service participating entity, where the request message includes an identifier of the target multicast bearer and a group identifier of the terminal group, and the request message is used to request to use the target multicast.
  • the bearer transmits the service data of the terminal group.
  • the target service entity sends a response message to the other service entity, where the response message is used to indicate that the other service participating entity does not use the target multicast bearer to send the service data of the terminal group.
  • the other service participating entity After receiving the identifier and the indication of the target multicast bearer of the target service entity, the other service participating entity notifies the terminal in the service area that is managed by the terminal to receive the service data of the group in the target multicast bearer, and the other service participating entity stops to The terminal located in the service area in the terminal group transmits the service data of the terminal group.
  • the service data of the terminal group is sent to the terminal located in the service area in the terminal group, and the agreed time may be pre-configured or may be the target service entity. Sent.
  • the other service participating entity may notify the terminal in the service area that it manages to receive the service data of the terminal group in the target multicast bearer by:
  • the other service participating entity notifies the terminal located in the service area that the managed terminal is in the multicast transmission mode to receive the service data of the terminal group in the target multicast bearer.
  • the other service participating entity notifies the terminal located in the service area that the managed terminal is in the unicast transmission mode to receive the service data of the terminal group in the target multicast bearer.
  • Step 4014 The target service entity sends a second response message to the service participating entity, where the service participating entity receives the second response message from the target service entity.
  • the second response message is used to notify the service participating entity, and the binding relationship between the identifier of the target multicast bearer and the group identifier of the terminal group is successfully established, and the service participating entity may use the target multicast bearer sending terminal.
  • Business data for the group is used to notify the service participating entity, and the binding relationship between the identifier of the target multicast bearer and the group identifier of the terminal group is successfully established, and the service participating entity may use the target multicast bearer sending terminal.
  • Business data for the group is used to notify the service participating entity, and the binding relationship between the identifier of the target multicast bearer and the group identifier of the terminal group is successfully established, and the service participating entity may use the target multicast bearer sending terminal.
  • the second response message can be used to indicate that the service participating entity sends the service data of the terminal group by using the target multicast bearer.
  • the target service entity may carry the first indication information in the second response message of the step 4014, where the first indication information is used to indicate that the service participating entity uses the target multicast bearer to send the service data of the terminal group.
  • the first indication information may be carried in a specific location of the second response message, for example, by using a character encoding or a digital encoding in a specific position of the second response message. Specifically, the first indication information may be represented by “00”, or Expressed with "SEND".
  • the service participating entity may confirm that no other service participating entity is using the target multicast bearer, and therefore, the service participating entity may use the target multicast. Hosted.
  • the service participating entity uses the target multicast bearer to send the service data of the terminal group, which can be implemented in the following manner:
  • the service participating entity may use the target multicast bearer to send the service data of the terminal group.
  • the service participating entity may send the service data of the terminal group to the other service participating entity, and the other service participating entity uses the target multicast bearer. Send the service data of the terminal group.
  • the service participating entity may send indication information to the other service participating entity, where the indication information is used to indicate the other service participating entity: use the target multicast bearer to send the service data of the terminal group.
  • the service participating entity may obtain the information of the other service participating entity by using a manner in which the service control entity pushes, or actively requests, for example, the other service participating entity identification information, and/or the other service participating entity. Address information.
  • the service participating entity directly uses the target multicast to carry the service data of the sending terminal group. Specifically, the service participating entity sends the service of the terminal group to the user plane address and the port number of the target multicast bearer. data. In the implementation manner 3, regardless of which service participating entity is established by the service participating entity, the service participating entity directly uses the target multicast carrier to transmit the service data of the terminal group.
  • Step 403 The service participating entity sends an indication message to the terminal, where the terminal receives the indication message from the service participating entity.
  • the service participant entity After receiving the response message, the service participant entity obtains the identifier of the target multicast bearer in the service, and the service participant entity also sends an indication message to the terminal of the service participant entity registered in the terminal group, where the indication message includes multiple targets.
  • An identifier of the broadcast bearer the indication message is used to instruct the terminal to receive the service data of the terminal group on the target multicast bearer.
  • the indication message includes an identifier of the multicast bearer, and optionally, an identifier of the terminal group.
  • the service participating entity sends the indication message to the service area by using a multicast transmission mode.
  • the terminal that receives the service reception indication message may include some or all terminals in the terminal group, and may also include Terminals of other groups, and these terminals may be registered by the business participating entity, or may be registered by other business participating entities.
  • the implementation manner can be understood as that the service participating entity sends a service reception indication message to some or all terminals of the service area in a service area by using a multicast transmission mode.
  • the service participating entity sends the indication message to the terminal registered by the service participating entity in the terminal group in a unicast manner.
  • the service participating entity sends the service receiving indication message to the terminal that is registered by the service participating entity in the terminal group and is currently located in the service area by using the unicast mode.
  • the service receiving indication message is used to instruct the terminal to receive the service data by using the multicast bearer. If the terminal receiving the message is not in the service area, the service data cannot be received. If the terminal that receives the message is not a terminal in the terminal group, it is processed by other processing methods, such as dropping the data packet after attempting to decrypt the content of the message, or determining that it is not a terminal in the terminal group. Discard the packet.
  • the terminals located in the service area in the terminal group are the terminals 1 to 6.
  • the service participant entity 1 sends a request message to the target service entity (the service control entity or the multicast bearer management entity), and obtains the identifier of the target multicast bearer in the received response message, thereby notifying the terminal. 1 to 3, receiving service data on the target multicast bearer.
  • the target service entity the service control entity or the multicast bearer management entity
  • the service participating entity 2 can notify the terminal 4 that the terminal 5 receives the service data on the target multicast bearer.
  • the service participating entity 3 can notify the terminal 6 to receive the service data on the target multicast bearer.
  • the service participating entity may actively obtain the identifier of the target multicast bearer from the target service entity, and after obtaining the identifier of the target multicast bearer, notify the terminal group that is located in the service area and is registered in its own terminal.
  • the terminal of the group receives the service data, which can reduce the resource overhead of the business participating entity.
  • each service participating entity determines whether it can use the target multicast bearer to send service data to terminals of the terminal group.
  • the result of the query has two situations, which are respectively described below.
  • the target service entity can notify the service participating entity that sends the request message, and the target multicast bearer can be used.
  • the target service entity can notify the service participating entity that sends the request message, and the target multicast bearer can be used.
  • the response message sent by the target service entity to the service participating entity includes the identifier of the target multicast bearer
  • the service participating entity may use the target multicast bearer by default. Therefore, the service participating entity may use the identifier.
  • the target multicast bearer when the response message includes only the identifier of the target multicast bearer, the service participating entity may use the target multicast bearer by default. Therefore, the service participating entity may use the identifier.
  • the target multicast bearer when the response message includes only the identifier of the target multicast bearer, the service participating entity may use the target multicast bearer by default. Therefore, the service participating entity may use the identifier.
  • the target multicast bearer may be used by default. Therefore, the service participating entity may use the identifier.
  • the service participating entity receives the response message, the identifier of the target multicast bearer is obtained.
  • the terminal sends an indication message to the terminal of the service participating entity in the terminal group, indicating that the terminal is The service data is received on the target multicast bearer.
  • the service participating entity sends the service data of the terminal group through the target multicast bearer in the service area.
  • the received response message includes only the identifier of the target multicast bearer, and the service participating entity considers that no other service participating entity currently uses the target multicast.
  • the service bearer sends the service data to the terminal group. Therefore, on the one hand, the service participant entity 1 notifies the terminal 1 to the terminal 3 to receive the service data on the target multicast bearer through the indication message. On the other hand, the service participant entity 1 passes the service data.
  • the target multicast carries the service data of the terminal group in the service area.
  • the service participating entity 2 and the service participating entity 3 are separately notified to receive the service data on the target multicast bearer.
  • the service participant entity 2 also sends a request message to the target service entity.
  • the service participant entity 2 obtains the identifier of the target multicast bearer carried in the response message, and the service participant entity 2 can also determine the current according to the response message.
  • the service participating entity 2 notifies the terminal 4 and the terminal 5 to receive the service data on the target multicast bearer by using the indication information, and the service participating entity 2 does not send the service data to the terminal 1 to the terminal 7 of the terminal group A;
  • the service participating entity 3 notifies the terminal 6 that the terminal 7 receives the service data on the target multicast bearer, and the service participating entity 3 does not send the service data to the terminal 1 to the terminal 7 of the terminal group A.
  • Implementation manner 2 The target service entity sends a response message to the service participating entity, including the identifier of the target multicast bearer and the first indication information.
  • the first indication information is used to indicate the service participating entity, and the service data of the terminal group is sent by using the target multicast bearer.
  • the main difference from the foregoing implementation manner 1 is that, by using the first indication information, the service participating entity is displayed in a display manner, and the service data of the terminal group can be currently sent through the target multicast bearer.
  • Other aspects are the same as the above-mentioned implementation manner 1, and the above description may be referred to, and details are not described herein again.
  • Case 2 Querying that other service participating entities are using the target multicast bearer to transmit the service data of the terminal group.
  • the response message includes not only the identifier of the target multicast bearer, but also a second indication information
  • the second indication information is used to indicate the service participating entity, and is not located in the service area in the terminal group.
  • the terminal sends the service data of the terminal group. Then the service participating entity determines that other service participating entities are using the target multicast bearer to send service data to the terminal group.
  • the service participating entity only needs to send an indication message to the terminal of the service participating entity registered in the terminal group, instructing the terminal to receive the service data of the terminal group on the target multicast bearer, and the service participating entity does not need to Send business data to the terminal group.
  • the target service entity when the service participating entity 1 transmits the service data using the target multicast bearer, then after the service participating entity 2 sends the request message to the target service entity, the target service entity sends the message to the service participating entity 2
  • the response message includes the identifier of the target multicast bearer and the second indication information, so that the service participating entity 2 sends the indication information to the terminal 4 and the terminal 5, indicating that the terminal 4 and the terminal 5 receive the service data on the target multicast bearer;
  • the service participating entity 3 sends the indication information to the terminal 6, instructing the terminal 6 to receive the service data on the target multicast bearer.
  • the foregoing implementation manner may also be understood as: when the service participating entity sends a request message to the target service entity, the target service entity sends a response message to the service participating entity, where the response message includes the indication information.
  • the indication information is the identifier of the target multicast bearer, the implementation manner 1 corresponding to the foregoing scenario 1; when the indication information is the identifier of the target multicast bearer and the first indication information, the implementation manner 2 corresponding to the foregoing scenario 1;
  • the indication information is the identifier of the target multicast bearer and the second indication information, it corresponds to the second case.
  • the response message when the response message includes only the identifier of the target multicast bearer, it may be agreed that no other service participating entity is currently using the target multicast bearer to send the service data. Certainly, when the response message includes only the identifier of the target multicast bearer, it may also be agreed that other service participating entities are currently using the target multicast bearer to send the service data, and the specific implementation manner is similar to the foregoing implementation manner, and is not described again. .
  • the target service entity queries that no other service participating entity is using the target multicast bearer, and the following implementation manners are available:
  • the target service entity may carry the first indication information in the second response message of the step 4014, where the first indication information is used to indicate the service participating entity, and the service data of the terminal group is sent by using the target multicast bearer.
  • the service participating entity may use no other service participating entity to use the target multicast bearer by default. Therefore, the service participates. The entity can use the target multicast bearer.
  • the second response message in the step 4014 carries the identifier of the terminal group, and the role of the identifier of the terminal group is the same as that of the first indication information, that is, the identifier of the terminal group is carried in the second response message.
  • the service participating entity confirms that no other service participating entity is using the target multicast bearer, and therefore, the service participating entity can use the target multicast bearer.
  • the target service entity queries that other service participating entities are using the target multicast bearer to send the service data of the terminal group.
  • the following implementation manners are available:
  • the target service entity may carry the second indication information in the second response message of the step 4014, where the second indication information is used to indicate the service participating entity, and does not send the location to the terminal located in the service area in the terminal group.
  • the second indication information may be carried in a specific location of the second response message, such as by using a character encoding or a digital encoding in a specific position of the second response message.
  • the second indication information may be represented by “01”, and It can be identified by "NOT SEND".
  • the second indication information may be distinguished from different values of the same cell at the same location where the first indication information is located in the second response information.
  • the second indication information may be used to indicate that the service participating entity does not use the target multicast bearer to send the service data of the terminal group.
  • the service participating entity does not send the received service data (media plane data and control signaling) to the user plane address and port number of the target multicast bearer, or is used to indicate that the service participating entity does not send the terminal group.
  • Business data When the service participating entity is not the service participating entity that establishes the target multicast bearer, the second indication information may be used to indicate that the service participating entity does not forward the service data of the terminal group to the service participating entity that establishes the target multicast bearer.
  • the service participating entity determines that there are other service participating entities that are using the target multicast bearer to send service data to the terminal group. Therefore, the service participating entity only needs to be located in the service group and registered in the service participating entity in the terminal group.
  • the terminal sends an indication message indicating that the terminal receives the service data of the terminal group on the target multicast bearer, and the service participating entity does not need to send the service data to the terminal group.
  • the other service participating entities when a service participating entity is using the target multicast bearer to send service data in the service area, the other service participating entities only need to notify the terminal group that is located in the service area and is registered in the terminal of the service participating entity, The service data can be received on the target multicast bearer. Therefore, in the service participating entity associated with the terminal group, only one service participating entity sends the service data to the terminal group by using the target multicast bearer, so that multiple service participating entities can simultaneously send the service data to the terminal group, which can solve the background. In the technology, different service participating entities repeatedly send the same service data, which is conducive to saving resources.
  • FIG. 5 is a schematic diagram of still another communication method provided by the present application.
  • the service participation entity in the embodiment shown in FIG. 5 may be the third service participation entity in the foregoing embodiment, and the broadcast bearer report message may be the response message in the foregoing embodiment.
  • the method includes the following steps:
  • Step 501 The service participating entity sends a broadcast bearer report message to the multicast bearer management entity.
  • the service participating entity (which may be any one of the service participating entities registered in the terminal group, for example, referred to as a third service participating entity) pre-establishes a multicast bearer or dynamically creates a multicast bearer.
  • the broadcast bearer report message is sent to the multicast bearer management entity, where the broadcast bearer report message includes a Temporary Mobile Group Identity (TMGI) and a service area identifier (SAI).
  • the device also includes an expiration time and a group identification (Group ID).
  • the address information of the service participating entity is further included, and the address may be an IPv4 address, an IPv6 address, an FQDN, or a URL.
  • the TMGI is used to identify a multicast bearer, that is, the TMGI can be understood as an identifier of a multicast bearer, the SAI is used to identify a service area, and the Group ID is used to indicate a terminal group that is using the multicast bearer. If there is no group communication currently being transmitted on the multicast bearer of the TMGI identity, the broadcast bearer report message may be without the Group ID.
  • broadcast bearer report message may also be referred to as a report message or the like.
  • Step 502 The multicast bearer management entity updates the locally saved multicast bearer according to the received broadcast bearer report message.
  • the multicast bearer management entity does not store the multicast bearer information, save the information in the broadcast bearer report message; if the multicast bearer management entity has stored the multicast bearer information, according to the received broadcast bearer report message Information, update stored multicast bearer information.
  • Step 503 The multicast bearer management entity sends a broadcast bearer report acknowledgement message to the service participating entity.
  • the broadcast bearer report acknowledgement message is used to indicate that the broadcast bearer report message has been successfully received.
  • the multicast bearer information may be sent to the multicast bearer management entity for storage, so that the multicast bearer management entity may be directly obtained from the multicast bearer management entity.
  • the multicast bearer may be sent to the multicast bearer management entity for storage, so that the multicast bearer management entity may be directly obtained from the multicast bearer management entity.
  • FIG. 6 is a schematic diagram of still another communication method provided by the present application.
  • the service participant entity 1 is the first service participant entity in the foregoing embodiment
  • the service participant entity 2 is the second service participant entity in the foregoing embodiment.
  • the method includes the following steps:
  • Step 601 The service control entity determines to transmit the group communication data to the terminal group by using the multicast bearer in the service area.
  • the service control entity may decide whether to transmit group communication data, such as sending service data, to the terminal group using the multicast bearer in a certain service area.
  • Step 602 The service control entity sends a broadcast bearer setup request message to the service participating entity 1, and the service participating entity 1 receives the broadcast bearer setup request message from the service control entity.
  • a service participating entity such as the service participating entity 1, is selected to establish a bearer.
  • the service control entity sends a broadcast bearer setup request message to the service participant entity 1, where the broadcast bearer setup request message includes the service area identifier SAI, the identifier group ID of the terminal group, and optionally, the session description protocol information (Session Description) Protocol, SDP), Quality of Service (QoS), where SDP is service description information, for example, including codec information.
  • SAI service area identifier
  • SDP Session Description Protocol
  • QoS Quality of Service
  • the TMGI may also be carried in the broadcast bearer setup request message, and sent to the service participating entity 1 to enable the service participating entity 1 to activate the bearer by using the TMGI.
  • step 603 the service participating entity 1 creates a multicast bearer.
  • Step 604a The service participating entity 1 sends the multicast bearer information to the multicast bearer management entity.
  • Step 604b The service participating entity 1 sends the multicast bearer information to the service control entity.
  • Step 605a The service control entity sends a broadcast bearer use message to the service participating entity 1, and the service participating entity 1 receives the broadcast bearer use message from the service control entity.
  • the broadcast bearer usage message includes a TMGI, a SAI, a group ID, and a media sending indicator, where the media sending indicator indicates that the service participating entity 1 indicates to the group ID, and uses the multicast bearer corresponding to the TMGI to send the group.
  • Communication data such as business data.
  • Step 605b The service control entity sends a broadcast bearer use message to the service participating entity 2, and the service participating entity 2 receives the broadcast bearer use message from the service control entity.
  • the broadcast bearer usage message includes a TMGI, a SAI, a Group ID, a media sending indicator, and optionally a timer, where the media sending indicator indicates that the service participating entity 2 is in the service area indicated by the SAI, not to the terminal group. Send communication data. If the timer is included, the timer is used to indicate how long the service participating entity 2 stops transmitting communication data to the terminal group in the service area indicated by the SAI.
  • Step 606a The service participating entity 1 transmits the communication data to the terminal group by using the multicast bearer corresponding to the TMGI in the service area corresponding to the SAI.
  • Step 606b The service participating entity 2 stops transmitting communication data to the terminal group in the service area corresponding to the SAI.
  • the service participating entity 2 also needs to notify the terminal located in the service area and registered in the service participating entity 2 in the terminal group, and receive the communication data on the multicast bearer corresponding to the TMGI.
  • step 607a the service participating entity 1 sends a broadcast bearer use confirmation message to the service control entity.
  • Step 607b The service participating entity 2 sends a broadcast bearer use confirmation message to the service control entity.
  • the service control entity instructs the service participating entity 1 to transmit the service data of the terminal group through the multicast bearer, and instructs the service participating entity 2 not to send the terminal group to the terminal located in the service area and registered in the service participating entity 2 in the terminal group.
  • the service data of the group avoids that the terminal group receives the same service data from multiple service participating entities, thereby saving resources.
  • FIG. 7 is a schematic diagram of still another communication method provided by the present application.
  • the embodiment describes that the service participating entity decides to use the multicast bearer, and then queries the target service entity (the service control entity or the multicast bearer management entity) for a certain service area, whether there is already a multicast bearer transmitting the same group communication. If yes, the service participating entity notifies its own terminal to receive service data on the existing multicast bearer, and the service participating entity no longer sends the service data to the terminal group.
  • the method includes the following steps:
  • Step 701 The service participating entity sends a broadcast bearer query request message to the target service entity, where the target service entity receives the broadcast bearer query request message from the service participating entity.
  • the broadcast bearer query request message includes an SAI, and optionally, a QoS, SDP.
  • the broadcast bearer query request message further includes a group ID.
  • Step 702 The target service entity queries the target multicast bearer that meets the condition according to the broadcast bearer query request message.
  • Step 703 The target service entity sends a broadcast bearer response message to the service participating entity, and the service participating entity receives the broadcast bearer response message from the target service entity.
  • the broadcast bearer response message includes a TMGI, a no-echo indication, where the TMGI is used to indicate the identifier of the target multicast bearer being used, and the No-echo indicator is used to indicate that the service participating entity does not need to associate with the SGI associated with the TMGI.
  • the service area sends communication data to the terminal of the group communication, and optionally also includes the SAI corresponding to the TMGI.
  • the TMGI is used to indicate the identifier of the target multicast bearer that the terminal group corresponding to the group ID is using.
  • Step 704a The service participating entity sends a broadcast service notification message to the terminal located in the service area and registered in the service participating entity, and the terminal receives the broadcast service notification message from the service participating entity.
  • the broadcast service notification message includes a TMGI and a SAI, and is used to notify the terminal to monitor the reception quality of the multicast bearer corresponding to the TMGI.
  • Step 704b The terminal sends a broadcast bearer quality report message to the service participating entity, and the service participating entity receives the broadcast bearer quality report message from the terminal.
  • the broadcast bearer quality report message includes the TMGI and the monitored quality information.
  • Step 705 The service participating entity sends a multicast bearer service and a group communication binding message to the terminal located in the service area and registered in the terminal group, and the terminal receives the multicast bearer service and the group communication binding from the service participating entity. Message.
  • the multicast bearer service and the group communication binding message include a TMGI and a group ID.
  • the terminal After receiving the message, the terminal binds the TMGI to the group ID, that is, establishes a correspondence.
  • step 705 can also be performed before step 704a or between step 704a and step 704b.
  • Step 706 The service participating entity sends a broadcast bearer use request message to the target service entity, where the target service entity receives the broadcast bearer use request message from the service participating entity.
  • the broadcast bearer use request message includes a TMGI, the reserved resource quantity, such as a bandwidth, and the group ID, indicating that the service participating entity is about to send the communication data to the terminal group corresponding to the group ID on the multicast bearer corresponding to the TMID, and thus needs to go to the target.
  • the amount of resources requested by the business entity such as bandwidth.
  • Step 707 The target service entity sends a broadcast bearer use response message to the service participating entity, and the service participating entity receives the broadcast bearer use response message from the target service entity.
  • the broadcast bearer use response message includes a TMGI, a SAI, a Group ID, and a No echo indicator, where the No echo indicator is used to indicate that the service participating entity is in the service area corresponding to the SAI, and does not need to use the multicast bearer corresponding to the TMGI, and corresponds to the Group ID.
  • the terminal group sends communication data, such as business data.
  • Step 708 The target service entity updates the multicast bearer information corresponding to the TMGI.
  • Step 709 After receiving the No echo indicator, the service participating entity does not use the multicast bearer corresponding to the TMGI, and sends the communication data to the terminal group corresponding to the Group ID.
  • FIG. 8 is a schematic diagram of still another communication method provided by the present application.
  • the service participant entity 1 and the service participant entity 2 are both in the service area, and the current service participant entity 1 transmits the service data of the terminal group to the terminal group through the multicast bearer in the service area, and the terminal group is registered in the terminal group.
  • the terminal of the service participating entity 2 receives the service data of the terminal group from the multicast bearer, and the service participating entity 2 does not send the service data to the terminal located in the service area and registered in the terminal group.
  • Step 801 The service participating entity 1 determines that the service data is no longer sent by using the multicast bearer in the service area.
  • the service participating entity 1 stops using the multicast bearer to send service data to the terminal group because of a fault, or overload, or exit communication.
  • Step 802 The service participating entity 1 sends a notification message to the service control entity, and the service control entity receives the notification message from the service participating entity 1.
  • the notification message may also be referred to as a stop sending data message, which includes TMGI, SAI, and Group ID, indicating that the service participating entity 1 is in the service area corresponding to the SAI, and does not use the multicast corresponding to the TMGI.
  • the bearer sends service data to the terminal group corresponding to the Group ID.
  • Step 803 The service control entity sends a broadcast bearer status notification message to the service participating entity 2, and the service participating entity 2 receives the broadcast bearer status notification message from the service control entity.
  • the broadcast bearer status notification message includes an SAI, and is used to instruct the service participating entity 2 to send service data to the terminal of the service participating entity 2 registered in the terminal group by using unicast or broadcast in the service area corresponding to the SAI.
  • Step 804 After receiving the broadcast bearer status notification message, the service participating entity 2 sends the service to the terminal located in the service area and registered in the service participating entity 2 in the service group corresponding to the SAI by using unicast or multicast. data.
  • the service participating entity that transmits the service data to the terminal group stops transmitting the service data
  • the service participating entity that can be registered by the terminal transmits the service data to the terminal for normal communication.
  • the device 900 may be a service control entity, or may be a system on chip or a chip, and may be controlled by a service in any of the foregoing embodiments.
  • the method that the entity performs may be a service control entity, or may be a system on chip or a chip, and may be controlled by a service in any of the foregoing embodiments. The method that the entity performs.
  • the apparatus 900 includes at least one processor 91, a transceiver 92, and optionally a memory 93.
  • the processor 91, the transceiver 92, and the memory 93 are connected by a communication bus.
  • the processor 91 can be a general purpose central processing unit (CPU), a microprocessor, an ASIC, or one or more integrated circuits for controlling the execution of the program of the present invention.
  • CPU general purpose central processing unit
  • ASIC application specific integrated circuit
  • the communication bus can include a path for communicating information between the above units.
  • the transceiver 92 is configured to communicate with other devices or communication networks, and the transceiver may be a communication interface, such as a wired interface or a wireless interface, or a wifi interface, or the transceiver includes a radio frequency circuit.
  • the memory 93 can be a ROM or other type of static storage device that can store static information and instructions, RAM or other type of dynamic storage device that can store information and instructions, or can be an electrically erasable programmable read only memory (Electrically erasable programmable reader) -only memory, EEPROM), compact disc read-only memory (CD-ROM) or other disc storage, optical disc storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), disk storage A medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of an instruction or data structure and that can be accessed by a computer, but is not limited thereto.
  • the memory 93 can exist independently and is coupled to the processor 91 via a communication bus.
  • the memory 93 can also be integrated with the processor.
  • the memory 93 is used to store application code for executing the solution of the present invention, and is controlled by the processor 91 for execution.
  • the processor 91 is configured to execute application code stored in the memory 93.
  • processor 91 may include one or more CPUs, such as CPU0 and CPU1 in FIG.
  • apparatus 900 can include multiple processors, such as processor 91 and processor 98 in FIG. Each of these processors may be a single-CPU processor or a multi-core processor, where the processor may refer to one or more devices, circuits, and/or A processing core for processing data, such as computer program instructions.
  • the device may be used to implement the steps performed by the service control entity in the communication method of the embodiment of the present invention.
  • the device may be used to implement the steps performed by the service control entity in the communication method of the embodiment of the present invention.
  • the present application may divide a functional module into a device according to the above method example.
  • each functional module may be divided according to each function, or two or more functions may be integrated into one processing module.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of the modules in the present application is schematic, and only a logical function division is performed, and the actual implementation may have another division manner.
  • FIG. 10 shows a schematic diagram of a device, which may be a service control entity or a system on chip or a chip involved in the above embodiment, and the device includes a processing unit. 1001 and communication unit 1002.
  • the processing unit 1001 is configured to acquire an identifier of a multicast bearer, where the multicast bearer is used to transmit service data of the terminal group in the service area;
  • the communication unit 1002 is configured to send, by the first service participant entity associated with the terminal group, a first indication message, where the first indication message is used to indicate that the first service participating entity sends the service data of the terminal group by using the multicast bearer;
  • the communication unit 1002 is further configured to send a second indication message to the second service participating entity that is associated with the terminal group, where the second indication message is used to indicate that the second service participating entity does not send the terminal in the terminal group that is located in the service area.
  • the service data of the terminal group, the first service participating entity is different from the second service participating entity;
  • At least one terminal in the terminal group is registered on the first service participating entity, and at least one terminal in the terminal group is registered on the second service participating entity.
  • the processing unit 1001 is specifically configured to control the communication unit 1002:
  • the response message includes an identifier of the multicast bearer.
  • the communication unit 1002 is further configured to:
  • the request message includes an identifier of the service area, and the request message is used to request the third service participating entity to establish a multicast bearer in the service area.
  • the communication unit 1002 is further configured to:
  • the response message includes an identifier of the multicast bearer.
  • the request message includes an identifier of the terminal group.
  • the communication unit 1002 is further configured to:
  • the notification message is used to notify the first service participating entity to stop sending the service data of the terminal group through the multicast bearer;
  • the processing unit 1001 is configured to control the communication unit 1002:
  • Business data ;
  • the terminal is a terminal that is located in the service area and is registered on the service participating entity.
  • the processing unit 1001 is further configured to control the communication unit 1002 to: send the service data of the terminal group by using the target multicast bearer; or
  • the response message further includes first indication information, where the first indication information is used to indicate the service participating entity, and the service data of the terminal group is sent by the target multicast bearer; the processing unit 1001 is further configured to control the communication unit 1002: the target multicast bearer Send the service data of the terminal group.
  • the response message further includes second indication information, where the second indication information is used to indicate that the service data of the terminal group is not sent to the terminal located in the service area in the terminal group.
  • the device is presented in the form of dividing each functional module corresponding to each function, or the service control entity is presented in a form that divides each functional module in an integrated manner.
  • a “module” herein may be an ASIC, a circuit, a processor and memory that executes one or more software or firmware programs, integrated logic circuits, and/or other devices that provide the functionality described above.
  • the device may be used to implement the steps performed by the service control entity in the communication method of the foregoing embodiment of the present invention.
  • the device may be used to implement the steps performed by the service control entity in the communication method of the foregoing embodiment of the present invention.
  • FIG. 11 a schematic diagram of a device provided by the present application, where the device 1100 can be, for example, a service participating entity, or a system on chip or a chip, can execute the service in any of the foregoing embodiments.
  • the method of participating in the execution of the entity can be, for example, a service participating entity, or a system on chip or a chip.
  • Apparatus 1100 includes at least one processor 111, a transceiver 112, and optionally a memory 113.
  • the processor 111, the transceiver 112, and the memory 113 are connected by a communication bus.
  • the processor 111 can be a general purpose central processing unit (CPU), a microprocessor, a specific ASIC, or one or more integrated circuits for controlling the execution of the program of the present invention.
  • the communication bus can include a path for communicating information between the above units.
  • the transceiver 112 is configured to communicate with other devices or communication networks, and the transceiver may be a communication interface, such as a wired interface or a wireless interface, or a wifi interface, or the transceiver includes a radio frequency circuit.
  • the memory 113 can be a ROM or other type of static storage device that can store static information and instructions, RAM or other types of dynamic storage devices that can store information and instructions, or can be EEPROM, CD-ROM or other optical disk storage, optical disk storage. (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and can be Any other media accessed, but not limited to this.
  • the memory 113 may be independent and connected to the processor 111 via a communication bus.
  • the memory 113 can also be integrated with the processor.
  • the memory 113 is used to store application code for executing the solution of the present invention, and is controlled by the processor 111 for execution.
  • the processor 111 is configured to execute application code stored in the memory 113.
  • the processor 111 may include one or more CPUs, such as CPU0 and CPU1 in FIG.
  • apparatus 1100 can include multiple processors, such as processor 111 and processor 118 in FIG. Each of these processors may be a single-CPU processor or a multi-core processor, where the processor may refer to one or more devices, circuits, and/or A processing core for processing data, such as computer program instructions.
  • processors such as processor 111 and processor 118 in FIG.
  • processors may be a single-CPU processor or a multi-core processor, where the processor may refer to one or more devices, circuits, and/or A processing core for processing data, such as computer program instructions.
  • the device may be used to implement the steps performed by the service participating entity in the communication method of the foregoing embodiment of the present invention.
  • the device may be used to implement the steps performed by the service participating entity in the communication method of the foregoing embodiment of the present invention.
  • the present application may divide a functional module into a device according to the above method example.
  • each functional module may be divided according to each function, or two or more functions may be integrated into one processing module.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules.
  • the division of modules in the present application is schematic, and is only a logical function division, and may be further divided in actual implementation.
  • FIG. 12 shows a schematic diagram of a device, which may be the service participating entity involved in the above embodiment, and the device includes a processing unit 1201 and a communication unit 1202. .
  • the processing unit 1201 is configured to control the communication unit 1202:
  • the terminal located in the service area in the group sends the service data of the terminal group;
  • Sending a fourth indication message to the terminal where the fourth indication message includes an identifier of the multicast bearer, and the fourth indication message is used to indicate that the terminal receives the service data of the terminal group by using the multicast bearer, where the terminal is located in the service area of the terminal group.
  • the fourth indication message includes an identifier of the multicast bearer
  • the fourth indication message is used to indicate that the terminal receives the service data of the terminal group by using the multicast bearer, where the terminal is located in the service area of the terminal group.
  • a terminal registered on a business participating entity.
  • processing unit 1201 is further configured to control the communication unit 1202:
  • the processing unit 1201 is configured to control the communication unit 1202:
  • the request message includes an identifier of the service area and a group identifier
  • the request message is used to request to query the target multicast bearer
  • the target multicast bearer is used to send the terminal corresponding to the group identifier in the service area.
  • the response message further includes first indication information, where the first indication information is used to indicate the service participating entity, and the service data of the terminal group is sent by using the target multicast bearer.
  • the response message further includes second indication information, where the second indication information is used to indicate that the service participating entity does not send the service data of the terminal group to the terminal located in the service area in the terminal group.
  • the device is presented in the form of dividing each functional module corresponding to each function, or the service control entity is presented in a form that divides each functional module in an integrated manner.
  • a “module” herein may refer to an ASIC, circuitry, processor and memory that executes one or more software or firmware programs, integrated logic circuitry, and/or other devices that provide the functionality described above.
  • the device may be used to implement the steps performed by the service participating entity in the communication method of the foregoing embodiment of the present invention.
  • the device may be used to implement the steps performed by the service participating entity in the communication method of the foregoing embodiment of the present invention.
  • the present application further provides a communication method, which may be a service participation entity managed by a target service entity and a target service participation entity (the first service participation entity and the third service participation entity in the figure are Example) Execution.
  • the first service participating entity and the third service participating entity are any two of the service participating entities managed by the target service participating entity.
  • the target service entity may be a service control entity or a multicast bearer management entity.
  • the second service participating entity and the fourth service participating entity are further mentioned, wherein the second service participating entity may refer to the service participating entity registered by the terminal of the terminal group except the first service participating entity.
  • the second service participating entity may refer to the service participating entity registered by the terminal of the terminal group except the first service participating entity.
  • the fourth service participating entity may be any one of the service participating entities registered by the terminal of the terminal group, and the fourth service participating entity may be the first service participating entity or the foregoing
  • the third business participation entity is not restricted.
  • the implementation process of the communication method shown in FIG. 13 will be described below.
  • the method includes the following steps:
  • Step 1301 The first service participating entity sends a first request message to the target service entity, where the target service entity receives the first request message from the first service participating entity.
  • the target service entity may be a service control entity or a multicast bearer management entity, and is not limited.
  • the first request message may include the group identifier and the identifier of the target multicast bearer, where the first request message may be used to request to send the service data of the terminal group corresponding to the group identifier by using the target multicast bearer.
  • the first service participating entity may be any service participating entity managed by the service control entity.
  • the service control entity For the terminal group corresponding to the group identifier, there is a corresponding service control entity and one or more corresponding service participating entities.
  • the “management” herein can be understood as the service control of the terminal group for the terminal group.
  • the entity may contact one or more corresponding business participation entities of the terminal group and assume centralized control functions in call control and media plane control.
  • the first service participating entity determines to use the target multicast bearer to send the service data of the terminal group
  • the first service message is sent to the target service entity, where the first request message includes the group identifier and the target multicast.
  • the first service participating entity may determine, by using terminal state information in the terminal group, service data of the terminal group using the target multicast bearer. For example, when the number of terminals in the terminal group that are served by the first service participating entity and the service area corresponding to the target multicast bearer meets a preset condition, the first service participating entity determines to use the target multicast bearer. Send the service data of the terminal group.
  • the target service entity has stored information about the target multicast bearer, such as the identifier of the target multicast bearer.
  • the information of the target multicast bearer stored on the target service entity can be obtained by:
  • the target multicast bearer is established by the first service participating entity, and the information about the target multicast bearer (for example, the identifier of the target multicast bearer) is reported to the target service entity.
  • the first service participating entity since the target multicast bearer is established by the first service participating entity, the first service participating entity locally stores the information of the target multicast bearer, and further, in the foregoing step 1301, The identifier of the target multicast bearer carried in the first request message sent by the service participating entity to the target service participant may be locally obtained by the first service participating entity.
  • the target multicast bearer is information that is established by another service participating entity (for example, the second service participating entity) and that is to be established by the target multicast bearer (for example, the identifier of the target multicast bearer). If the target service entity is reported to the target service entity, the identifier of the target multicast bearer carried in the first request message that is sent by the first service participant entity to the target service participant may be that the first service participant entity passes the following. Way to get:
  • the target business entity is a business control entity
  • the service control entity After receiving the information of the target multicast bearer reported by the second service participating entity, the service control entity pushes the information to the other service participating entity, for example, to the first service participating entity, and then the first service participating entity
  • the information carried by the broadcast is stored locally.
  • the identifier of the target multicast bearer may be locally obtained and carried in the first request message and sent to the target service entity.
  • the target service entity is a multicast bearer management entity.
  • the multicast bearer management entity After receiving the information about the multicast bearer reported by the second service participating entity, the multicast bearer management entity does not push the information to the other service participating entity.
  • the first service participating entity can obtain the target multicast bearer in the following manner.
  • the first service participating entity sends a query request message to the multicast bearer management entity, where the query request message includes an identifier of the service area, where the query request message is used to request to obtain information about the multicast bearer that sends the service data to the service area corresponding to the service area identifier.
  • the query request message may further include a group identifier, configured to acquire information about a multicast bearer that sends the service data of the terminal group corresponding to the group identifier to the service area corresponding to the service area identifier; and then multicast
  • the bearer management entity sends a query response message to the first service participating entity, where the query response message includes an identifier of the target multicast bearer. Then, the first service participating entity stores the information of the target multicast bearer (for example, the identifier of the target multicast bearer) locally.
  • the identifier of the target multicast bearer may be locally obtained and carried in the first request message and sent to the target service entity.
  • Step 1302 The target service entity sends a first response message to the first service participating entity, where the first service participating entity receives the first response message from the target service entity.
  • the first response message may include a usage status of the target multicast group by the terminal group.
  • the usage status of the terminal group to the target multicast bearer is: in use or not used.
  • the service data of the terminal group on the target multicast bearer is sent, or the service data of the terminal group without the target multicast bearer is being sent.
  • no service participating entity uses the target multicast bearer to transmit the service data of the terminal group, or a service participating entity uses the target multicast bearer to send the service data of the terminal group, or the second service participating entity uses the target multicast. Carry the service data of the sending terminal group.
  • the usage status of the target multicast bearer of the terminal group is in use, it indicates that another service participating entity sends the service data to the terminal group by using the target multicast bearer, and the first service participating entity does not go to the terminal.
  • the group sends business data to avoid repeatedly sending the same business data.
  • the first service participating entity only needs to notify the terminal to receive the service data on the target multicast bearer, which will be described in detail later.
  • the usage status of the target multicast bearer of the terminal group may indicate that no other service participating entity uses the target multicast bearer to send service data to the terminal group, and the first service participating entity may use the target.
  • the multicast bearer sends service data to the terminal group.
  • the target service entity after receiving the first request message of the first service participating entity, the target service entity sends the use status of the terminal group to the target multicast bearer to the first service participating entity, so that the first service participating entity Determining, according to the received usage status, whether the target multicast carrier can be used to send service data to the terminal group, for example, when the first service participating entity determines that the use status of the target multicast group by the terminal group is not used,
  • the first service participating entity uses the target multicast bearer to send service data, which helps to prevent multiple service participating entities from simultaneously transmitting data to the terminal group by using the target multicast bearer, thereby helping to avoid repeated reception of the terminal group terminal.
  • the same business data can save resources.
  • the foregoing method further includes:
  • Step 1303 The first service participating entity determines, according to the usage status, that the service data of the terminal group is sent by using the target multicast bearer, and sends an indication message to the target service entity.
  • the indication message may be used to indicate that the first service participating entity sends the service data of the terminal group by using the target multicast bearer.
  • it may also include:
  • Step 1304 The target service entity receives the indication message from the first service participating entity, and updates the usage status of the terminal group to the target multicast bearer according to the indication message.
  • step 1304 may update the usage status of the target multicast group by the terminal group in any of the following manners:
  • the target service entity updates the usage status of the target multicast bearer by the terminal group to: the first service participating entity uses the target multicast bearer to send the service data of the terminal group.
  • the target service entity updates the usage status of the target multicast bearer by the terminal group to: the service participating entity uses the target multicast carrier to send the service data of the terminal group.
  • the target service entity updates the usage status of the target multicast group by the terminal group to: in use.
  • the target service entity may further send a notification message to other service participating entities except the first service participating entity, where the notification message may be used to update the target multicast bearer.
  • the subsequent usage status is notified to other service participating entities, so that other service participating entities are also informed of the latest usage status of the target multicast bearer, so that other service entities can know the usage status of the target multicast bearer in time, and then can be used in time.
  • the multicast bearer transmits the service data of the group, expands the number of coverage terminals of the multicast bearer, and improves the transmission efficiency.
  • the latest usage status may be: the first service participating entity uses the target multicast bearer to send the service data of the terminal group, or the service participating entity uses the target multicast bearer to send the service data of the terminal group, or For, in use.
  • the first service participating entity determines, according to the usage status in the received first response message, whether the service data of the terminal group can be transmitted by using the target multicast bearer.
  • the first service participating entity determines, according to the usage status in the received first response message, that the service data of the terminal group is transmitted by using the target multicast bearer, the first service participating entity uses the target multicast bearer to the terminal group. Send business data.
  • the first service participating entity determines, according to the usage status, the service data of the sending terminal group by using the target multicast bearer, which may include the following methods:
  • the first service participating entity determines to use the target multicast bearer to transmit the service data of the terminal group.
  • the first service participating entity determines to use the target multicast bearer to send the terminal.
  • Business data for the group is not used
  • a service participating entity determines to use the target multicast bearer to send service data of the terminal group to be transmitted.
  • the first service participating entity determines to use the target multicast bearer to send the terminal group. Business data.
  • the first service participating entity determines to use the target multicast carrier to transmit the service data of the terminal group.
  • the first service participating entity determines to use the target multicast bearer to send the terminal group to be sent.
  • Business data For example, when the usage status in the received first response message is that the service data without the terminal group on the target multicast bearer is being transmitted, the first service participating entity determines to use the target multicast bearer to send the terminal group to be sent. Business data.
  • the first service participating entity may still send the service data of the terminal group.
  • the service control entity may discard the service data of the terminal group sent by one of the service participating entities, and generally discards the service data after the transmission.
  • the target service entity is a service control entity, and after the step 1304, the method further includes:
  • the target service entity sends a notification message to the third service participating entity, the notification message including the updated usage status of the target multicast bearer.
  • the service control entity notifies the other service participating entities other than the first service participating entity of the updated usage status.
  • the third service participating entity may be a business participation entity other than the first service participating entity, and is not limited.
  • the above method may further include:
  • the target service entity receives the notification status report message from the third service participating entity, and the notification status report message is used to notify the third service participating entity to notify the terminal to receive the service data of the terminal group on the target multicast bearer.
  • the method further includes:
  • Step 1305 The first service participating entity sends a notification message to the terminal.
  • the method may further include: receiving, by the terminal, a notification message from the first service participating entity.
  • the notification message may be used to notify the terminal to use the target multicast bearer to receive the service data of the terminal group.
  • the notification message may include an identifier of the target multicast bearer, and optionally, a group identifier.
  • the first service participating entity sends the notification message to the service area by using a multicast transmission mode.
  • the terminal that receives the notification message may include some or all terminals in the terminal group, and may also include Terminals of other groups, and these terminals may be registered by the first service participating entity, or may be registered by other business participating entities.
  • the implementation manner is understood to be that the first service participating entity sends a notification message to some or all terminals of the service area in a service area by using a multicast transmission mode.
  • the first service participating entity sends the notification message to the terminal registered by the first service participating entity in the terminal group by using a unicast manner.
  • the first service participating entity sends the notification message to the terminal that is registered by the first service participating entity in the terminal group and is currently located in the service area by using the unicast mode.
  • the notification message is used to instruct the terminal to receive service data using the target multicast bearer. If the terminal that receives the notification message is not in the service area, the service data cannot be received. If the terminal that receives the notification message is not a terminal in the terminal group, the processing may be performed by other processing methods, such as dropping the data packet after attempting to decrypt the content of the message, or determining that the terminal is not in the terminal group. When the packet is dropped.
  • the above method further includes:
  • Step 1306 The first service participating entity sends a notification status report message to the target service entity.
  • the method further includes: the target service entity receives the notification status report message from the first service participating entity.
  • the notification status report message may be used to indicate that the first service participating entity notifies the terminal to receive the service data of the terminal group on the target multicast bearer.
  • the notification status report message may also be referred to as a multicast status report message or a multicast use status report message, and details are not described herein again. It can be understood that, when the first service participating entity confirms the success notification to the terminal to receive the service data of the terminal group on the target multicast bearer (for example, receiving the acknowledgement message of the terminal), step 1306 is performed; or, as long as it is A service participating entity sends a message to the terminal to notify the terminal to receive the service data of the terminal group on the target multicast bearer. The first service participating entity performs step 1306 regardless of whether the terminal successfully receives the notification.
  • the first service participating entity when the first service participating entity determines to use the target multicast bearer to send the service data of the terminal group, the first service participating entity sends the first request message to the target service entity, and according to the receiving And determining, by the terminal group in the first response message, the usage status of the target multicast bearer, and determining whether the target multicast carrier can be used to send the service data to the terminal group.
  • the usage status of the target multicast bearer of the terminal group is unused, the first service participating entity may send the service data by using the target multicast bearer. Further, the target service entity may also update the usage status of the target multicast bearer. Further, if the target service entity is a service control entity, the service control entity also notifies the other service participation entities except the first service participating entity.
  • the foregoing method further includes:
  • Step 1307 The first service participating entity sends the service data of the terminal group to the terminal by using the target multicast bearer.
  • the first service participating entity uses the target multicast bearer to send the service data of the terminal group, that is, the first service participating entity directly uses the The target multicast bearer transmits the service data of the terminal group.
  • the first service participating entity when the target multicast bearer is not established by the first service participating entity, the first service participating entity sends the indication information and the service data of the terminal group to the service participating entity that establishes the target multicast bearer.
  • the indication information is used to indicate that the service participating entity that establishes the target multicast bearer uses the target multicast bearer to send the service data of the terminal group. That is, the first service participating entity sends the service data of the terminal group to the service participating entity that establishes the target multicast bearer, and the service participating entity that establishes the target multicast bearer sends the terminal group by using the target multicast bearer.
  • Group of business data
  • the target multicast bearer is established by the second service participating entity, and the first service participating entity may push through the service control entity, or the first service participating entity adopts the initiative request to obtain the second service.
  • Information of the participating entities for example, including the second service participating entity identification information, and/or the address information of the second service participating entity.
  • the first service participating entity sends the service data and the indication information of the terminal group to the second service participating entity, and instructs the second service participating entity to use the target multicast bearer to send the service data of the terminal group.
  • the service participating entity that establishes the target multicast bearer uses the target multicast bearer to send service data to the terminal.
  • the first service participating entity uses the target multicast bearer to send the service data to the terminal. It can be understood that the service participating entity that obtains the usage right of the target multicast bearer uses the target multicast bearer to send the service data to the terminal.
  • the other service participating entity may In the service participating entity registered for the terminal of the terminal group, the service participating entity that participates in the terminal group communication except for the first service participating entity, such as the third service participating entity, also determines to use the target multicast.
  • the method may further include the step 1308 to the step 1309, when the bearer sends the service data of the terminal group.
  • Step 1308 The third service participating entity sends a second request message to the target service entity.
  • the method may further include: receiving, by the target service entity, a second request message from the third service participating entity.
  • the second request message may include a group identifier and an identifier of the target multicast bearer, where the second request message is used to request to use the target multicast bearer to send service data of the terminal group.
  • Step 1309 The target service entity sends a second response message to the third service participating entity.
  • the method may further include: the third service participating entity receives the second response message from the target service entity.
  • the second response message may include an updated usage status of the target multicast bearer.
  • the updated usage status is: the first service participating entity uses the target multicast bearer to send the service data of the terminal group, or the service participating entity uses the target multicast bearer to send the service data of the terminal group. Or, in use.
  • the third service participating entity learns that the target multicast bearer is currently in use, that is, other service participating entities have used the target multicast bearer to send service data to the terminal group terminal, in order to avoid repeatedly sending the same service. Data, the third service participating entity decides not to send the service data of the terminal group. Therefore, it is helpful to prevent multiple service participating entities from simultaneously transmitting data to the terminal group by using the target multicast bearer, thereby helping to avoid the terminal group terminal repeatedly receiving the same service data, thereby saving resources.
  • step 1308-step 1309 may not be performed.
  • the above method may further include:
  • Step 1310 The third service participating entity sends a notification message to the terminal.
  • the method may further include: receiving, by the terminal, a notification message from the third service participating entity.
  • the notification message may be used to notify the terminal to receive the service data of the terminal group through the target multicast bearer.
  • the notification message includes an identifier of the target multicast bearer, and optionally, a group identifier.
  • the third service participating entity sends the notification message to the service area by using a multicast transmission mode.
  • the terminal that receives the notification message may include some or all terminals in the terminal group, and may also include Terminals of other groups, and these terminals may be registered by the third service participating entity, or may be registered by other business participating entities.
  • the implementation manner can be understood that the third service participating entity sends a notification message to some or all terminals of the service area in a service area by using a multicast transmission mode.
  • the third service participating entity sends the notification message to the terminal registered by the third service participating entity in the terminal group by using a unicast manner.
  • the third service participating entity sends the notification message to the terminal that is registered by the third service participating entity in the terminal group and is currently located in the service area by using the unicast mode.
  • the notification message may be used to instruct the terminal to receive the service data by using the target multicast bearer. If the terminal that receives the notification message is not in the service area, the service data cannot be received. If the terminal that receives the notification message is not a terminal in the terminal group, the processing may be performed by other processing methods, such as dropping the data packet after attempting to decrypt the content of the message, or determining that the terminal is not in the terminal group. When the packet is dropped.
  • the above method may further include:
  • Step 1311 The third service participating entity sends a notification status report message to the target service entity.
  • the method may further include: receiving, by the target service entity, a notification status report message from the third service participating entity.
  • the notification status report message may be used to indicate that the third service participating entity notifies the terminal to receive the service data of the terminal group on the target multicast bearer. It can be understood that, when the third service participating entity confirms the success notification to the terminal to receive the service data of the terminal group on the target multicast bearer (for example, receiving the acknowledgement message of the terminal), step 1311 is performed; or, as long as it is The third service participating entity sends a message to the terminal to notify the terminal to receive the service data of the terminal group on the target multicast bearer, and the third service participating entity performs step 1311 regardless of whether the terminal successfully receives the notification.
  • the third service participating entity determines to use the target multicast bearer to send the service data of the terminal group, and when the third service participating entity learns that the use status of the target multicast bearer is in use, then The three service participating entities do not send the service data to the terminal, but notify the terminal to receive the data on the target bearer. Therefore, it is helpful to prevent multiple service participating entities from simultaneously transmitting data to the terminal group by using the target multicast bearer, thereby helping to avoid the terminal group terminal repeatedly receiving the same service data, thereby saving resources.
  • each service participating entity sends a message to the multicast bearer management entity.
  • the current usage status of the multicast bearer can be known.
  • the target service entity in the foregoing embodiment is a service control entity
  • the service control entity may actively push the latest usage state of the multicast bearer to each service participating entity, and each service participating entity The usage status of the multicast bearer can be obtained.
  • the foregoing method further includes:
  • the first service participating entity may send an indication message to the target service entity.
  • the indication message is used to notify the target service entity that the first service participating entity stops using the target multicast bearer to send the service data.
  • the method may further include: the target service entity updating the usage status of the target multicast group by the terminal group to: no service participating entity uses the target multicast carrier to send the service data of the terminal group.
  • the target service entity updates the usage status of the target multicast bearer by the terminal group to: the service data without the terminal group on the target multicast bearer is sent.
  • the target service entity updates the usage status of the target multicast group by the terminal group to: unused.
  • the foregoing method further includes:
  • the first service participating entity sends a bearer information report message to the target service entity, where the bearer information report message includes an identifier of the service area, the group identifier, and an identifier of the target multicast bearer; or
  • the first service participating entity receives a push message from the service control entity, where the push message includes an identifier of the service area, the group identifier, and an identifier of the target multicast bearer.
  • the information about the target multicast bearer for example, the identifier of the service area, the group identifier, and the target multicast
  • the bearer identifier is carried in the bearer information report message and sent to the target service entity, and the target service entity can manage the target multicast bearer.
  • the service control entity has multiple pushes.
  • the function of the information carried by the bearer so that a push message may be sent to the service participating entity (for example, including the first service participating entity) other than the other service participating entity that establishes the target multicast bearer, where the push message includes the service area
  • the identifier, the group identifier, and the identifier of the target multicast bearer so that the service participating entity registered by the terminal of the terminal group can obtain the information of the multicast bearer established by one of the service participating entities.
  • the target service entity may be a service control entity or a multicast bearer management entity.
  • the target business entity is a business control entity.
  • the service control entity may manage the service participating entities registered by the terminals in the terminal group.
  • the first service participating entity managed by the service control entity establishes the target multicast bearer
  • the first service participating entity sends a bearer information report message to the service control entity after the target multicast bearer is established, and the bearer information is sent.
  • the report message includes the group identifier and the identifier of the target multicast bearer.
  • the bearer information reporting message further includes an identifier of the service area.
  • the bearer information reporting message may be used to report the information of the established multicast bearer.
  • the report message when any of the service participating entities establishes a multicast bearer and sends the established multicast bearer information by using the report message, the report message may be referred to as a bearer information report message.
  • the service control entity After receiving the bearer information report message sent by the first service participating entity, the service control entity obtains the group identifier and the identifier of the target multicast bearer. Optionally, an identification of the service area is also obtained. The service control entity then records the information of the target multicast bearer.
  • the service control entity also records the usage status of the multicast bearer. For example, there are the following ways.
  • the usage status is in use, or the usage status is unused.
  • the target service entity records the usage status of the multicast bearer as: in use or not used.
  • the middle finger is that the current service participating entity is currently using the multicast bearer to send service data, or the current service participating entity uses the multicast bearer and is ready to start sending service data.
  • Unused means that no service entity is currently using the multicast bearer to send service data, or no service participant entity currently uses the multicast bearer and is ready to start transmitting service data.
  • the service data with the terminal group on the multicast bearer is used for sending, or the service data with no terminal group on the multicast bearer is used for sending.
  • the service control entity records that the usage status of the multicast bearer is: the service data of the terminal group on the multicast bearer is sent, or the service data of the terminal group without the multicast bearer is being sent.
  • the service data of the terminal group on the multicast bearer is sent, and the multicast bearer is currently used to send the service data of the terminal group.
  • the service data without the terminal group on the multicast bearer is being transmitted, which means that the multicast bearer is not currently used for transmitting the service data of the terminal group.
  • the service state is that no service participating entity uses the multicast bearer to send the service data of the terminal group, or the service state is that the service participating entity uses the multicast bearer to send the service data of the terminal group, or the usage state is the second.
  • the service participating entity uses the multicast bearer to transmit the service data of the terminal group.
  • the service data of the terminal group is transmitted on the multicast bearer in the foregoing mode 2, and in the third mode, the service participation entity uses the multicast bearer to send the service data of the terminal group, or It is recorded that the second service participating entity uses the multicast bearer to transmit the service data of the terminal group.
  • the second service participating entity refers to any service participating entity associated with the service control.
  • the service data of the terminal group is not transmitted on the multicast bearer in the foregoing mode 2.
  • the third mode it is recorded that no service participating entity uses the multicast bearer to send the service data of the terminal group.
  • any service participating entity managed by the service control entity may establish a multicast bearer (for example, establish the target multicast bearer), and report the information of the established multicast bearer to the service control entity.
  • the reporting process may be as follows: the service control entity receives the bearer information report message from the fourth service participating entity, where the bearer information report message includes The identity of the service area and the identity of the multicast bearer.
  • the bearer information reporting message further includes a group identifier.
  • the bearer information reporting message further includes information of the fourth service participating entity, such as address information or identifier information.
  • the service control entity may record the information of the multicast bearer established and reported by each service participating entity, where the recorded information includes the usage status of the terminal group to the multicast bearer.
  • the service control entity After receiving the bearer information report message sent by the service participating entity, the service control entity obtains and records the multicast bearer information, such as the group identifier, the identifier of the multicast bearer, and the identifier of the service area, and then controls the service.
  • the service participating entity that is managed by the entity in addition to the service participating entity that establishes the multicast bearer, sends a push message, where the push message includes the group identifier and the identifier of the multicast bearer, optionally, Includes the identity of the service area.
  • the information about the service participating entity that establishes the multicast bearer is further included.
  • the usage status of the multicast bearer by the terminal group is also included.
  • any service participating entity establishes a multicast bearer and reports it to the service control entity.
  • the service control entity records the information carried in the multicast bearer on the one hand, and pushes the information of the multicast bearer to other information on the other hand.
  • the service participating entity enables the service participating entity managed by the service control entity to record related information of the multicast bearer.
  • the target service entity is a multicast bearer management entity.
  • the multicast bearer management entity may obtain the multicast bearer established by the service participating entity by using the same method as the foregoing service control entity obtains the information of the multicast bearer. information. And the manner of recording the information carried by the multicast can also adopt the same recording manner as the above-mentioned service control entity.
  • the multicast bearer management entity does not have the group information of the terminal group, it is impossible to know which service participating entities are in the group, and thus may not have the push function of the service control entity, that is, the multicast bearer management entity record. After the information of the multicast bearer reported by the service participating entity, the information of the recorded multicast bearer may not be pushed to other service participating entities.
  • the device 1400 may be a target service entity, or may be a system on chip or a chip, and may be implemented in the embodiment shown in FIG. 13 .
  • the method performed by the target business entity may be a target service entity, or may be a system on chip or a chip, and may be implemented in the embodiment shown in FIG. 13 . The method performed by the target business entity.
  • the apparatus 1400 includes at least one processor 141, a transceiver 142, and optionally a memory 143.
  • the processor 141, the transceiver 142, and the memory 143 are connected by a communication bus.
  • Processor 141 may be a general purpose central processing unit (CPU), a microprocessor, a specific ASIC, or one or more integrated circuits for controlling the execution of the program of the present invention.
  • CPU central processing unit
  • microprocessor a specific ASIC
  • integrated circuits for controlling the execution of the program of the present invention.
  • the communication bus can include a path for communicating information between the above units.
  • the transceiver 142 is configured to communicate with other devices or communication networks, and the transceiver may be a communication interface, such as a wired interface or a wireless interface, or a wifi interface, or the transceiver includes a radio frequency circuit.
  • the memory 143 may be a ROM or other type of static storage device that can store static information and instructions, RAM or other types of dynamic storage devices that can store information and instructions, or EEPROM, CD-ROM or other optical disk storage, optical disk storage. (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and can be Any other media accessed, but not limited to this.
  • the memory 143 may be independent and connected to the processor 141 via a communication bus. Memory 143 can also be integrated with the processor.
  • the memory 143 is used to store application code for executing the solution of the present invention, and is controlled by the processor 141 for execution.
  • the processor 141 is configured to execute application code stored in the memory 143.
  • processor 141 may include one or more CPUs, such as CPU0 and CPU1 in FIG.
  • apparatus 1400 can include multiple processors, such as processor 141 and processor 148 in FIG. Each of these processors may be a single-CPU processor or a multi-core processor, where the processor may refer to one or more devices, circuits, and/or A processing core for processing data, such as computer program instructions.
  • the device may be used to implement the steps performed by the target service entity in the communication method of the embodiment shown in FIG. 13, and related features may be referred to above, and details are not described herein again.
  • the present application may divide a functional module into a device according to the above method example.
  • each functional module may be divided according to each function, or two or more functions may be integrated into one processing module.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules.
  • the division of modules in the present application is schematic, and is only a logical function division, and may be further divided in actual implementation.
  • FIG. 15 shows a schematic diagram of a device, which may be a target service entity or a system on chip or a chip involved in the embodiment shown in FIG.
  • the device includes a processing unit 1501 and a communication unit 1502.
  • the processing unit 1501 is configured to control the communication unit 1502:
  • the usage status includes:
  • the service data of the terminal group is sent on the target multicast bearer, or the service data of the terminal group is not sent on the target multicast bearer; or
  • the service participation entity sends the service data of the terminal group by using the target multicast bearer, or the service participation entity sends the service data of the terminal group by using the target multicast bearer, or the second service participates.
  • the entity sends the service data of the terminal group by using the target multicast bearer.
  • processing unit 1501 is further configured to control the communication unit 1502:
  • the processing unit 1501 is further configured to update the usage status according to the indication message.
  • processing unit 1501 is specifically configured to:
  • processing unit 1501 is further configured to control the communication unit 1502:
  • the second request message including the group identifier and an identifier of the target multicast bearer, the second request message being used to request to use the target multicast Carrying service data for transmitting the terminal group;
  • the device 1500 is a service control entity; the processing unit 1501 is further configured to control the communication unit 1502 to send a notification message to a third service participating entity, where the notification message includes The updated usage status of the target multicast bearer.
  • processing unit 1501 is further configured to control the communication unit 1502:
  • processing unit 1501 is further configured to control the communication unit 1502:
  • the bearer information report message may include an identifier of the service area, the group identifier, and an identifier of the target multicast bearer.
  • the identifier and/or address of the fourth service participating entity are also included.
  • the device is presented in the form of dividing each functional module corresponding to each function, or the service control entity is presented in a form that divides each functional module in an integrated manner.
  • a “module” herein may refer to an ASIC, circuitry, processor and memory that executes one or more software or firmware programs, integrated logic circuitry, and/or other devices that provide the functionality described above.
  • the device may be used to implement the steps performed by the target service entity in the communication method of the embodiment of the present invention.
  • the device may be used to implement the steps performed by the target service entity in the communication method of the embodiment of the present invention.
  • FIG. 16 a schematic diagram of a device provided by the present application, which may be, for example, a service participating entity, or a system on chip or a chip, may be implemented in the embodiment shown in FIG. 13 .
  • the method performed by the first business participating entity.
  • Apparatus 1600 includes at least one processor 161, a transceiver 162, and optionally a memory 163.
  • the processor 161, the transceiver 162, and the memory 163 are connected by a communication bus.
  • Processor 161 may be a general purpose central processing unit (CPU), microprocessor, ASIC, or one or more integrated circuits for controlling the execution of the program of the present invention.
  • CPU central processing unit
  • ASIC application specific integrated circuit
  • the communication bus can include a path for communicating information between the above units.
  • the transceiver 162 is configured to communicate with other devices or communication networks, and the transceiver may be a communication interface, such as a wired interface or a wireless interface, or a wifi interface, or the transceiver includes a radio frequency circuit.
  • the memory 163 may be a ROM or other type of static storage device that can store static information and instructions, RAM or other types of dynamic storage devices that can store information and instructions, or EEPROM, CD-ROM or other optical disk storage, optical disk storage. (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and can be Any other media accessed, but not limited to this.
  • the memory 163 may be independent and connected to the processor 161 via a communication bus. Memory 163 can also be integrated with the processor. Among them, the memory 163 is used to store application code for executing the scheme of the present invention, and is controlled by the processor 161 for execution.
  • the processor 161 is configured to execute application code stored in the memory 163.
  • processor 161 may include one or more CPUs, such as CPU0 and CPU1 in FIG.
  • apparatus 1600 can include multiple processors, such as processor 161 and processor 168 in FIG. Each of these processors may be a single-CPU processor or a multi-core processor, where the processor may refer to one or more devices, circuits, and/or A processing core for processing data, such as computer program instructions.
  • processors such as processor 161 and processor 168 in FIG.
  • processors may be a single-CPU processor or a multi-core processor, where the processor may refer to one or more devices, circuits, and/or A processing core for processing data, such as computer program instructions.
  • the apparatus may be used to implement the steps performed by the first service participating entity in the communication method of the embodiment shown in FIG. 13, and related features may be referred to above, and details are not described herein again.
  • the present application may divide a functional module into a device according to the above method example.
  • each functional module may be divided according to each function, or two or more functions may be integrated into one processing module.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules.
  • the division of modules in the present application is schematic, and is only a logical function division, and may be further divided in actual implementation.
  • FIG. 17 shows a schematic diagram of a device, which may be the first service participating entity involved in the embodiment shown in FIG. 13, and the device includes processing.
  • the processing unit 1701 is configured to control the communication unit 1702:
  • the processing unit 1701 is further configured to determine, according to the usage status, that the service data of the terminal group is sent by using the target multicast bearer;
  • the processing unit 1701 is further configured to control the communication unit 1702 to send an indication message to the target service entity, where the indication message is used to indicate that the first service participating entity sends the terminal group by using the target multicast bearer. Business data.
  • processing unit 1701 is specifically configured to:
  • the usage state is that no service participating entity uses the target multicast bearer to send the service data of the terminal group or the When the usage status is unused or the usage status is that the service data without the terminal group on the target multicast bearer is sent, determining to use the target multicast bearer to send the service data of the terminal group; or ,
  • the usage status is that no service participating entity sends the service data of the terminal group by using the target multicast bearer, or the usage status is unused or the usage status is not used by the target multicast bearer.
  • the service data of the terminal group is sent, it is determined that the service data of the terminal group is sent by using the target multicast bearer.
  • the processing unit 1701 is further configured to control the communication unit 1702 to send a notification message to the terminal, where the notification message is used to notify the terminal to receive, by using the target multicast bearer, the Business data of the terminal group.
  • the processing unit 1701 is further configured to control the communication unit 1702 to send a notification status report message to the target service entity, where the notification status report message is used to indicate the first service.
  • the participating entity notifies the terminal to receive the service data of the terminal group on the target multicast bearer.
  • the processing unit 1701 when the target multicast bearer is established by the first service participating entity, the processing unit 1701 is further configured to control the communication unit 1702 to send by using the target multicast bearer. Service data of the terminal group; or
  • the processing unit 1701 is further configured to control the communication unit 1702 to send the indication information and the terminal group to be sent to the second service participating entity.
  • the service data, the indication information is used to indicate that the second service participating entity sends the service data of the terminal group to be sent by using the target multicast bearer.
  • processing unit 1701 is further configured to control the communication unit 1702:
  • the bearer information report message includes an identifier of the service area, the group identifier, and an identifier of the target multicast bearer;
  • the push message including an identifier of a service area, the group identity, and an identifier of the target multicast bearer.
  • the device is presented in the form of dividing each functional module corresponding to each function, or the service control entity is presented in a form that divides each functional module in an integrated manner.
  • a “module” herein may refer to an ASIC, circuitry, processor and memory that executes one or more software or firmware programs, integrated logic circuitry, and/or other devices that provide the functionality described above.
  • the apparatus may be used to implement the steps performed by the first service participating entity in the communication method of the embodiment shown in FIG. 13 of the present invention.
  • the apparatus may be used to implement the steps performed by the first service participating entity in the communication method of the embodiment shown in FIG. 13 of the present invention.
  • the device 1800 may be a target service entity, or may be a system on chip or a chip, and may perform the steps 4011 to 4014 of the foregoing embodiment. The method performed by the target business entity.
  • the apparatus 1800 includes at least one processor 181, a transceiver 182, and optionally a memory 183.
  • the processor 181, the transceiver 182, and the memory 183 are connected by a communication bus.
  • Processor 181 can be a general purpose central processing unit (CPU), a microprocessor, a specific ASIC, or one or more integrated circuits for controlling the execution of the program of the present invention.
  • CPU central processing unit
  • microprocessor a specific ASIC
  • integrated circuits for controlling the execution of the program of the present invention.
  • the communication bus can include a path for communicating information between the above units.
  • the transceiver 182 is configured to communicate with other devices or communication networks, and the transceiver may be a communication interface, such as a wired interface or a wireless interface, or a wifi interface, or the transceiver includes a radio frequency circuit.
  • the memory 183 may be a ROM or other type of static storage device that can store static information and instructions, RAM or other types of dynamic storage devices that can store information and instructions, or EEPROM, CD-ROM or other optical disk storage, optical disk storage. (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and can be Any other media accessed, but not limited to this.
  • the memory 183 can exist independently and be coupled to the processor 181 via a communication bus. Memory 183 can also be integrated with the processor.
  • the memory 183 is used to store application code for executing the solution of the present invention, and is controlled by the processor 181 for execution.
  • the processor 181 is configured to execute application code stored in the memory 183.
  • processor 181 may include one or more CPUs, such as CPU0 and CPU1 in FIG.
  • apparatus 1800 can include multiple processors, such as processor 181 and processor 188 in FIG. Each of these processors may be a single-CPU processor or a multi-core processor, where the processor may refer to one or more devices, circuits, and/or A processing core for processing data, such as computer program instructions.
  • processors such as processor 181 and processor 188 in FIG.
  • processors may be a single-CPU processor or a multi-core processor, where the processor may refer to one or more devices, circuits, and/or A processing core for processing data, such as computer program instructions.
  • the device may be used to implement the steps performed by the target service entity in step 4011 - step 4014 of the foregoing embodiment.
  • the device may be used to implement the steps performed by the target service entity in step 4011 - step 4014 of the foregoing embodiment.
  • the present application may divide a functional module into a device according to the above method example.
  • each functional module may be divided according to each function, or two or more functions may be integrated into one processing module.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules.
  • the division of modules in the present application is schematic, and is only a logical function division, and may be further divided in actual implementation.
  • FIG. 19 shows a schematic diagram of a device, which may be a target service entity or a system on chip or a chip involved in the embodiment shown in FIG.
  • the apparatus includes a processing unit 1901 and a communication unit 1902.
  • the processing unit 1901 is configured to control the communication unit 1902:
  • the first request message includes an identifier of the target multicast bearer and a group identifier of the terminal group, where the first request message is used to request to use the target multicast Carrying service data for transmitting the terminal group;
  • the first response message includes first indication information, where the first indication information is used to indicate that the first service participating entity sends the terminal group by using the target multicast bearer. Business data.
  • processing unit 1901 is further configured to control the communication unit 1902:
  • the second response message includes second indication information, where the second indication information is used to indicate that the second service participating entity does not use the target multicast bearer to send the terminal group. Group of business data.
  • processing unit 1901 is further configured to control the communication unit 1902:
  • the reporting message further includes address information of the third service participating entity.
  • the device is presented in the form of dividing each functional module corresponding to each function, or the service control entity is presented in a form that divides each functional module in an integrated manner.
  • a “module” herein may refer to an ASIC, circuitry, processor and memory that executes one or more software or firmware programs, integrated logic circuitry, and/or other devices that provide the functionality described above.
  • the device may be used to implement the steps performed by the target service entity in step 4011 - step 4014 of the foregoing embodiment of the embodiment of the present invention.
  • the device may be used to implement the steps performed by the target service entity in step 4011 - step 4014 of the foregoing embodiment of the embodiment of the present invention.
  • FIG. 20 is a schematic diagram of a device provided by the present application.
  • the device 2000 may be, for example, a service participating entity, or may be a system on chip or a chip, and may perform the step 4011-step of the foregoing embodiment.
  • Apparatus 2000 includes at least one processor 201, a transceiver 202, and optionally a memory 203.
  • the processor 201, the transceiver 202, and the memory 203 are connected by a communication bus.
  • Processor 201 can be a general purpose central processing unit (CPU), microprocessor, ASIC, or one or more integrated circuits for controlling the execution of the program of the present invention.
  • CPU central processing unit
  • ASIC application specific integrated circuit
  • the communication bus can include a path for communicating information between the above units.
  • the transceiver 202 is configured to communicate with other devices or communication networks, and the transceiver may be a communication interface, such as a wired interface or a wireless interface, or a wifi interface, or the transceiver includes a radio frequency circuit.
  • the memory 203 may be a ROM or other type of static storage device that can store static information and instructions, RAM or other types of dynamic storage devices that can store information and instructions, or EEPROM, CD-ROM or other optical disk storage, optical disk storage. (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and can be Any other media accessed, but not limited to this.
  • the memory 203 may exist independently and be coupled to the processor 201 via a communication bus.
  • the memory 203 can also be integrated with the processor.
  • the memory 203 is used to store application code for executing the solution of the present invention, and is controlled by the processor 201 for execution.
  • the processor 201 is configured to execute application code stored in the memory 203.
  • processor 201 may include one or more CPUs, such as CPU0 and CPU1 in FIG.
  • apparatus 2000 can include multiple processors, such as processor 201 and processor 208 in FIG. Each of these processors may be a single-CPU processor or a multi-core processor, where the processor may refer to one or more devices, circuits, and/or A processing core for processing data, such as computer program instructions.
  • processors such as processor 201 and processor 208 in FIG.
  • processors may be a single-CPU processor or a multi-core processor, where the processor may refer to one or more devices, circuits, and/or A processing core for processing data, such as computer program instructions.
  • the device may be used to implement the steps performed by the service participating entity in step 4011 - step 4014 of the foregoing embodiment.
  • the device may be used to implement the steps performed by the service participating entity in step 4011 - step 4014 of the foregoing embodiment.
  • the present application may divide a functional module into a device according to the above method example.
  • each functional module may be divided according to each function, or two or more functions may be integrated into one processing module.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules.
  • the division of modules in the present application is schematic, and is only a logical function division, and may be further divided in actual implementation.
  • FIG. 21 shows a schematic diagram of a device, which may be the service participating entity involved in step 4011 - step 4014 of the above embodiment, and the device includes processing.
  • the processing unit 2101 is configured to control the communication unit 2102:
  • the response message is used to indicate that the service participating entity sends the service data of the terminal group by using the target multicast bearer.
  • the response message includes first indication information, where the first indication information is used to indicate that the service participating entity sends the service data of the terminal group by using the target multicast bearer.
  • processing unit 2101 is further configured to control the communication unit 2102:
  • the device is presented in the form of dividing each functional module corresponding to each function, or the service control entity is presented in a form that divides each functional module in an integrated manner.
  • a “module” herein may refer to an ASIC, circuitry, processor and memory that executes one or more software or firmware programs, integrated logic circuitry, and/or other devices that provide the functionality described above.
  • the device may be used to implement the steps performed by the service participating entity in step 4011 - step 4014 of the foregoing embodiment.
  • the device may be used to implement the steps performed by the service participating entity in step 4011 - step 4014 of the foregoing embodiment.
  • the above embodiments it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • software it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions.
  • the computer program instructions When the computer program instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present invention are generated in whole or in part.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transfer to another website site, computer, server, or data center by wire (eg, coaxial cable, fiber optic, digital subscriber line (DSL), or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media.
  • the usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (such as a Solid State Disk (SSD)) or the like.
  • a magnetic medium eg, a floppy disk, a hard disk, a magnetic tape
  • an optical medium eg, a DVD
  • a semiconductor medium such as a Solid State Disk (SSD)
  • embodiments of the present application can be provided as a method, apparatus (device), computer readable storage medium, or computer program product.
  • the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware aspects, which are collectively referred to herein as "module” or "system.”
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Landscapes

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

Abstract

本申请提供一种通信方法及装置。该方法包括：目标业务实体在接收到第一业务参与实体的第一请求消息后，向该第一业务参与实体发送终端群组对目标多播承载的使用状态，使得第一业务参与实体可以根据接收到的使用状态判断是否可以使用该目标多播承载向终端群组发送业务数据，例如，当第一业务参与实体确定终端群组对目标多播承载的使用状态为未使用时，则第一业务参与实体才使用该目标多播承载发送业务数据，有助于避免多个业务参与实体同时使用目标多播承载向终端群组发送数据，进而有助于避免终端群组的终端重复接收到相同的业务数据，可节约资源。

Description

一种通信方法及装置
本申请要求在2017年9月30日提交中华人民共和国知识产权局、申请号为201710945904.5、发明名称为“一种通信方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中，要求在2018年1月15日提交中华人民共和国知识产权局、申请号为201810036433.0、发明名称为“一种通信方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及移动通信技术领域，尤其涉及一种通信方法及装置。
背景技术
公共集群业务，包括紧急任务即按即说(Mission critical push-to-talk over LTE，MCPTT)，紧急任务视频(Mission Critical Video，MCVideo)，紧急任务数据(Mission Critical Data，MCData)等，用于公共安全应用及一般的商业应用，如公共事业或者铁路应用等，且支持一对多的群组通信。
对于一对多的群组通信，紧急业务系统支持两种媒体传输模式：单播承载传输和多播承载传输。对于多播承载传输，可以使用紧急任务服务实体(Mission critical service entity，MC service entity)实现，MC service entity例如包括紧急任务服务服务器(Mission critical service server，MC service server)，MC service entity可以从逻辑上分为业务控制实体和业务参与实体。业务参与实体主要用于终端的注册，以及向注册的终端发送数据，决定对向终端群组使用单播承载传输或多播承载发送数据；业务控制实体主要用于群组通信建立的管理，接收终端群组的上行业务数据，通过业务参与实体向终端群组分发业务数据。其中，终端群组可以由同一个注册在同一业务参与实体的终端组成，也可以由注册在不同业务参与实体的终端组成。
当终端群组中的终端来自不同的业务参与实体时，此时，这些不同的业务参与实体都可以向该终端群组发送数据，并且发送的数据有可能是相同的，从而终端群组中的终端重复接收相同的数据，导致资源浪费。
发明内容
本申请提供一种通信方法及装置，用以减少终端群组重复接收相同业务数据的次数，节约资源。
第一方面，本申请提供一种通信方法，该方法可由目标业务实体或目标业务实体内的芯片执行，其中，目标业务实体可以是业务控制实体或多播承载管理实体。该方法包括：首先，目标业务实体接收来自第一业务参与实体的第一请求消息，该第一请求消息包括群组标识和目标多播承载的标识，第一请求消息用于请求使用目标多播承载发送群组标识对应的终端群组的业务数据。然后，目标业务实体向第一业务参与实体发送第一响应消息，第一响应消息包括终端群组对目标多播承载的使用状态。
该方法，目标业务实体在接收到第一业务参与实体的用于请求使用目标多播承载发送终端群组的业务数据的第一请求消息后，向该第一业务参与实体发送终端群组对目标多播承载的使用状态，从而使得第一业务参与实体可以根据接收到的使用状态判断是否可以使用该目标多播承载向终端群组发送业务数据，例如，当第一业务参与实体确定终端群组对 目标多播承载的使用状态为未使用时，则第一业务参与实体才使用该目标多播承载发送业务数据，因而有助于避免多个业务参与实体同时使用目标多播承载向终端群组发送数据，进而有助于避免终端群组的终端重复接收到相同的业务数据，可节约资源。
上述方法中，终端群组对目标多播承载的使用状态，也可以表述为，目标多播承载对终端群组的传输状态。其中，传输状态指的是传输业务数据的状态，业务数据包括控制信令和媒体数据。
在一种可能的实现方式中，上述方法中的终端群组对目标多播承载的使用状态可以有以下的实现方式：
实现方式一，使用状态为在使用中，或者，使用状态为未使用。
该实现方式中，目标业务实体记录目标多播承载的使用状态为：使用中或未使用。
其中，使用中指的是，当前有业务参与实体正在使用该目标多播承载发送业务数据，或者，当前有业务参与实体使用该目标多播承载并准备发送业务数据。
未使用指的是，当前没有业务实体正在使用该目标多播承载发送业务数据，或者，当前没有业务参与实体使用该目标多播承载并准备开始发送业务数据。
实现方式二，使用状态为目标多播承载上有终端群组的业务数据在发送，或者，使用状态为目标多播承载上没有终端群组的业务数据在发送。
该实现方式中，目标业务实体记录目标多播承载的使用状态为：目标多播承载上有终端群组的业务数据在发送，或，目标多播承载上没有终端群组的业务数据在发送。
其中，目标多播承载上有终端群组的业务数据在发送，指的是，该目标多播承载当前正在被用于发送终端群组的业务数据。
目标多播承载上没有终端群组的业务数据在发送，指的是，该目标多播承载当前未被用于发送终端群组的业务数据。
实现方式三，使用状态为没有业务参与实体使用目标多播承载发送终端群组的业务数据，或者，使用状态为有业务参与实体使用目标多播承载发送终端群组的业务数据，或者，使用状态为第二业务参与实体使用目标多播承载发送终端群组的业务数据。
该实现方式三，是在上述实现方式二的基础上，进一步还记录使用目标多播承载的对象，即业务参与实体。
具体地，上述实现方式二中的目标多播承载上有终端群组的业务数据在发送，在该实现方式三中，被记录为，有业务参与实体使用目标多播承载发送终端群组的业务数据，或者，被记录为，第二业务参与实体使用目标多播承载发送终端群组的业务数据。该第二业务参与实体指的是目标业务实体关联的任一业务参与实体。
上述实现方式二中的目标多播承载上没有终端群组的业务数据在发送，在该实现方式三中，被记录为，没有业务参与实体使用目标多播承载发送终端群组的业务数据。
需要说明的是，上述三种实现方式，均是对目标多播承载的使用状态的记录方法，在实际应用中，可选择其中任一种或几种方法来实施。
在一种可能的实现方式中，目标业务实体接收来自第一业务参与实体的指示消息，指示消息用于指示第一业务参与实体使用目标多播承载发送终端群组的业务数据；目标业务实体根据指示消息，更新使用状态。即，当第一业务参与实体确定使用该目标多播承载发送终端群组的业务数据时，则通知目标业务实体，从而，目标业务实体将更新该目标多播承载的使用状态。进而，其他业务参与实体此时将无法使用该目标多播承载向同一个终端 群组发送业务数据，使得只有一个业务参与实体使用该目标多播承载向终端群组发送业务数据，有助于保证同一个终端群组的终端不会同时从不同的业务参与实体接收相同的业务数据。
在一种可能的实现方式中，目标业务实体根据指示消息，更新使用状态，包括：
目标业务实体将使用状态更新为第一业务参与实体使用目标多播承载发送终端群组的业务数据；或者，
目标业务实体将使用状态更新为有业务参与实体使用目标多播承载发送终端群组的业务数据；或者，
目标业务实体将使用状态更新为在使用中。
在一种可能的实现方式中，进一步还包括：目标业务实体接收来自第三业务参与实体的第二请求消息，第二请求消息包括群组标识和目标多播承载的标识，第二请求消息用于请求使用目标多播承载发送终端群组的业务数据；目标业务实体向第三业务参与实体发送第二响应消息，第二响应消息包括目标多播承载的更新后的使用状态。
在一种可能的实现方式中，若上述目标业务实体为业务控制实体，则上述任一实施例中进一步还可以包括：目标业务实体向第三业务参与实体发送通知消息，通知消息包括目标多播承载的更新后的使用状态。
由于目标业务实体可以管理关联的各个业务参与实体，因而，当目标业务实体更新了目标多播承载的使用状态之后，可以主动将更新后的使用状态通知给关联的各个业务参与实体。
在一种可能的实现方式中，目标业务实体还可以接收来自第三业务参与实体的通知状态上报消息，通知状态上报消息用于指示第三业务参与实体通知终端在目标多播承载上接收终端群组的业务数据。
在一种可能的实现方式中，还包括：目标业务实体接收来自第四业务参与实体的承载信息上报消息，承载信息上报消息包括服务区域的标识、群组标识和目标多播承载的标识。
该方法，当第四业务参与实体建立了多播承载后，主动向目标业务实体上报建立的多播承载的信息。例如，建立了上述目标多播承载后，向目标业务实体发送承载信息上报消息，承载信息上报消息中包括该目标多播承载所使用的服务区域的标识，该目标多播承载对应的终端群组的标识，以及该目标多播承载的标识。可选地，该承载信息上报消息中还包括第四业务实体的信息，如第四业务实体的地址信息或第四业务实体的标识信息。
在一种可能的实现方式中，还包括：目标业务实体接收来自第一业务参与实体的查询请求消息，查询请求消息包括服务区域的标识，查询请求消息用于请求获取发送群组标识对应的终端群组的业务数据的多播承载；目标业务实体向第一业务参与实体发送查询响应消息，查询响应消息包括目标多播承载的标识。
第二方面，本申请提供一种通信方法，该方法可由业务参与实体或业务参与实体内的芯片执行。该方法包括：第一业务参与实体向目标业务实体发送请求消息，请求消息包括群组标识和目标多播承载的标识，请求消息用于请求使用目标多播承载发送群组标识对应的终端群组的业务数据；第一业务参与实体接收来自目标业务实体的响应消息，响应消息包括终端群组对目标多播承载的使用状态。
该方法，当第一业务参与实体向终端群组发送业务数据时，则向目标业务实体发送用于请求使用目标多播承载发送终端群组的业务数据的请求消息，然后接收目标业务实体发 送的响应消息，该响应消息中包括终端群组对目标多播承载的使用状态。进而，第一业务参与实体可以根据接收到的使用状态，判断是否可以使用该目标多播承载向终端群组发送业务数据，例如，当第一业务参与实体确定终端群组对目标多播承载的使用状态为未使用时，则第一业务参与实体才使用该目标多播承载发送业务数据；当第一业务参与实体确定终端群组对目标多播承载的使用状态为在使用时，则第一业务参与实体不使用该目标多播承载发送业务数据，因而有助于避免多个业务参与实体同时使用目标多播承载向终端群组发送数据，进而有助于避免终端群组的终端重复接收到相同的业务数据，可节约资源。
在一种可能的实现方式中，第一业务参与实体根据使用状态，确定使用目标多播承载发送终端群组的业务数据；第一业务参与实体向目标业务实体发送指示消息，指示消息用于指示第一业务参与实体使用目标多播承载发送终端群组的业务数据。
上述方法，当第一业务参与实体根据接收到的终端群组对目标多播承载的使用状态，确定可以使用该目标多播承载发送终端群组的业务数据，则该第一业务参与实体确定将使用该目标多播承载发送终端群组的业务数据，并向目标业务实体发送指示消息，用于指示：第一业务参与实体使用目标多播承载发送终端群组的业务数据，进而可以使得目标业务实体更新记录的终端群组对目标多播承载的使用状态。
在一种可能的实现方式中，第一业务参与实体根据使用状态，确定使用目标多播承载发送终端群组的业务数据，包括：当第一业务参与实体存在待发送的终端群组的业务数据，且使用状态为没有业务参与实体使用目标多播承载发送终端群组的业务数据或使用状态为未使用或使用状态为目标多播承载上没有终端群组的业务数据在发送时，第一业务参与实体确定使用该目标多播承载发送终端群组的业务数据；或者，
当使用状态为没有业务参与实体使用所述目标多播承载发送终端群组的业务数据或使用状态为未使用或使用状态为目标多播承载上没有终端群组的业务数据在发送时，第一业务参与实体确定使用该目标多播承载发送终端群组的业务数据。
在一种可能的实现方式中，当第一业务参与实体确定使用目标多播承载发送终端群组的业务数据，则第一业务参与实体还向终端发送通知消息，通知消息用于通知终端通过目标多播承载接收终端群组的业务数据。
作为一种实现方式，当第一业务参与实体向终端发送了通知消息之后，还向目标业务实体发送通知状态上报消息，通知状态上报消息用于指示第一业务参与实体通知终端在目标多播承载上接收终端群组的业务数据。
在一种可能的实现方式中，当目标多播承载由第一业务参与实体建立时，第一业务参与实体使用目标多播承载发送终端群组的业务数据；或者，当目标多播承载由第二业务参与实体建立时，第一业务参与实体向第二业务参与实体发送指示信息和待发送的终端群组的业务数据，指示信息用于指示第二业务参与实体使用目标多播承载发送待发送的终端群组的业务数据。
在一种可能的实现方式中，第一业务参与实体向目标业务实体发送承载信息上报消息，承载信息上报消息包括服务区域的标识、群组标识和目标多播承载的标识；或者，第一业务参与实体接收来自目标业务实体的推送消息，推送消息包括服务区域的标识、群组标识和目标多播承载的标识。
第三方面，本申请提供一种通信方法，该方法可由业务控制实体或业务控制实体内的芯片执行。该方法包括：业务控制实体获取多播承载的标识，多播承载用于在服务区域内 传输终端群组的业务数据；业务控制实体向终端群组关联的第一业务参与实体发送第一指示消息，第一指示消息用于指示第一业务参与实体，通过多播承载发送终端群组的业务数据；业务控制实体向终端群组关联的第二业务参与实体发送第二指示消息，第二指示消息用于指示第二业务参与实体，不向终端群组中位于服务区域内的终端发送终端群组的业务数据，第一业务参与实体与第二业务参与实体不同；其中，终端群组中存在至少一个终端注册在第一业务参与实体上，终端群组中存在至少一个终端注册在第二业务参与实体上。
该方法，业务控制实体指示第一业务参与实体，通过多播承载发送终端群组的业务数据，并指示第二业务参与实体不向终端群组中位于服务区域内的终端发送终端群组的业务数据，避免了终端重复接收到相同的业务数据，节约了资源。
在一种可能的设计中，业务控制实体获取多播承载的标识，包括：业务控制实体向多播承载管理实体发送查询消息，查询消息包括服务区域的标识，查询消息用于请求查询服务区域对应的多播承载；业务控制实体接收来自多播承载管理实体的响应消息，响应消息包括多播承载的标识。
该方法，由于多播承载的相关信息，如多播承载的标识，存储在多播承载管理实体。业务控制实体通过查询消息，向多播承载管理实体请求查询服务区域对应的多播承载的标识，方便多播承载的信息的管理。
在一种可能的设计中，业务控制实体向终端群组关联的第三业务参与实体发送请求消息，请求消息包括服务区域的标识，请求消息用于请求第三业务参与实体在服务区域内建立多播承载。
该方法，当业务控制实体从多播承载管理实体获取多播承载的标识失败时，则请求业务参与实体，如第三业务参与实体，建立一个多播承载。
在建立多播承载后，可选地，业务控制实体接收来自第三业务参与实体的响应消息，响应消息包括建立的多播承载的标识。从而，业务控制实体可获取到建立的多播承载的标识。
在建立多播承载后，可选地，业务控制实体接收来自第三业务参与实体的响应消息，响应消息包括指示信息，指示信息用于指示成功建立多播承载，并且，第三业务参与实体将建立的多播承载的信息，如多播承载的标识等，发送至多播承载管理实体进行存储，从而业务控制实体可进一步地从多播承载管理实体获取建立的多播承载。
在一种可能的设计中，上述请求消息包括终端群组的标识。当上述请求消息包括终端群组的标识时，业务控制实体获取的多播承载的标识则是与该终端群组的标识对应的终端群组相对应，即获取的多播承载的标识是与终端群组关联的承载的标识。
可选地，上述响应消息还包括终端群组的标识。
在一种可能的设计中，业务控制实体接收来自第一业务参与实体的通知消息，通知消息用于通知，第一业务参与实体停止通过多播承载发送终端群组的业务数据；业务控制实体向第二业务参与实体发送第三指示消息，第三指示消息用于指示第二业务参与实体，向终端群组中位于服务区域内且注册在第二业务参与实体上的终端，发送终端群组的业务数据。
该方法，当第一业务参与实体停止使用多播承载发送终端群组的业务数据时，则业务控制实体通知第二业务参与实体，向终端群组中位于服务区域且注册在第二业务参与实体上的终端发送业务数据，从而，当终端群组中位于服务区域且注册在第二业务参与实体上 的终端不能从第一业务参与实体接收业务数据时，还可以从第二业务参与实体接收业务数据，使得终端群组中位于服务区域且注册在第二业务参与实体上的终端，可正常接收业务数据。
在一种可能的设计中，业务控制实体向第四业务参与实体发送指示信息，指示信息用于指示使用单播方式，向终端群组中位于服务区域且注册在第四业务参与实体上的终端发送业务数据，第四业务参与实体为终端群组关联的业务参与实体中的任一业务参与实体。即，当业务控制实体决定停止使用多播承载时，则指示多播承载关联的所有业务参与实体，分别使用单播方式，向终端群组中注册在自身的终端发送业务数据。
在另一种可能的设计中，业务控制实体向第四业务参与实体发送指示信息，指示信息用于指示第四业务参与实体，向终端群组中位于服务区域且注册在第四业务参与实体的终端发送业务数据，第四业务参与实体为终端群组关联的业务参与实体中的任一业务参与实体。即，当业务控制实体决定停止使用多播承载时，则指示多播承载关联的所有业务参与实体，分别向终端群组中注册在自身的终端发送业务数据，发送数据的方式由业务参与实体自己决定，例如可以是单播方式，也可以是多播方式。
第四方面，本申请提供一种通信方法，该方法可由业务参与实体或业务参与实体内的芯片执行。该方法包括：业务参与实体接收来自业务控制实体的第二指示消息，第二指示消息包括多播承载的标识、服务区域的标识及群组标识，第二指示消息用于指示业务参与实体，不向群组标识对应的终端群组中位于服务区域内的终端发送终端群组的业务数据；业务参与实体向终端发送第四指示消息，第四指示消息包括多播承载的标识，第四指示消息用于指示终端，通过多播承载接收终端群组的业务数据。
在一种可能的设计中，业务参与实体接收来自业务控制实体的第三指示消息，第三指示消息用于指示业务参与实体，向终端发送终端群组的业务数据。
第五方面，本申请提供一种通信方法，该方法可由业务参与实体或业务参与实体内的芯片执行。该方法包括：业务参与实体向目标业务实体发送请求消息，请求消息包括服务区域的标识和群组标识，请求消息用于请求查询目标多播承载，目标多播承载用于在服务区域发送群组标识对应的终端群组的业务数据；业务参与实体接收来自目标业务实体的响应消息，响应消息包括目标多播承载的标识；业务参与实体向终端发送指示消息，指示消息用于指示终端通过目标多播承载接收终端群组的业务数据。
该方法，业务参与实体可以主动向目标业务实体获取目标多播承载的标识，在获取到目标多播承载的标识后，通知终端群组中位于服务区域且注册在该业务参与实体的终端，在目标多播承载上接收业务数据，使得终端群组中位于服务区域的终端都在目标多播承载上接收业务，从而，只需要有一个业务参与实体发送业务数据，便可以使得终端群组的终端都接收到业务数据，避免终端群组内的终端重新接收数据，还可以减少业务参与实体的资源开销。
在一种可能的设计中，业务参与实体通过目标多播承载发送终端群组的业务数据；或，响应消息还包括第一指示信息，第一指示信息用于指示业务参与实体通过目标多播承载发送终端群组的业务数据；业务参与实体通过目标多播承载发送终端群组的业务数据。
可选地，当业务参与实体决定不再通过目标多播承载向终端群组发送业务数据时，则业务参与实体向目标业务实体发送第一通知消息，第一通知消息用于通知目标业务实体，业务参与实体停止，通过目标多播承载发送终端群组的业务数据。从而，目标业务实体接 收到第一通知消息后，可指示其他业务参与实体向终端群组发送业务数据。
在一种可能的设计中，上述响应消息还包括第二指示信息，第二指示信息用于指示业务参与实体，不向终端群组中位于服务区域内的终端发送终端群组的业务数据。
可替换地，上述第五方面及各种可能的设计方案，还可以描述为：
业务参与实体向目标业务实体发送请求消息，请求消息包括服务区域的标识和群组标识，请求消息用于请求查询目标多播承载，目标多播承载用于在服务区域发送群组标识对应的终端群组的业务数据；业务参与实体接收来自目标业务实体的响应消息，响应消息包括指示信息。
当指示信息为目标多播承载的标识时，业务参与实体向终端发送指示消息，指示消息用于指示终端在目标多播承载上接收终端群组的业务数据，终端为终端群组中在服务区域且注册在业务参与实体上的终端。以及，通过目标多播承载，发送终端群组的业务数据。
当指示信息为目标多播承载的标识和第一指示信息时，业务参与实体向终端发送上述指示消息。以及，通过目标多播承载发送终端群组的业务数据。其中，第一指示信息用于指示业务参与实体，通过目标多播承载发送终端群组的业务数据。
当指示信息为目标多播承载的标识和第二指示信息时，业务参与实体向终端发送上述指示消息；其中，第二指示信息用于指示业务参与实体，不向终端群组中位于服务区域内的终端发送终端群组的业务数据。
第六方面，本申请提供一种通信方法，该方法可由目标业务实体或目标业务实体内的芯片执行。该方法包括：目标业务实体接收来自业务参与实体的请求消息，请求消息包括服务区域的标识和群组标识，请求消息用于请求查询目标多播承载，目标多播承载用于在服务区域内，发送群组标识对应的终端群组的业务数据；目标业务实体向业务参与实体发送响应消息，响应消息包括目标多播承载的标识。
在一种可能的设计中，响应消息还包括第一指示信息，第一指示信息用于指示业务参与实体，通过目标多播承载发送终端群组的业务数据。
在一种可能的设计中，响应消息还包括第二指示信息，第二指示信息用于指示业务参与实体，不向终端群组中位于服务区域内的终端发送终端群组的业务数据。
可替换地，上述第六方面及各种可能的设计方案，还可以描述为：
目标业务实体接收来自业务参与实体的请求消息，请求消息包括服务区域的标识和群组标识，请求消息用于请求查询目标多播承载，目标多播承载用于在服务区域发送群组标识对应的终端群组的业务数据；
目标业务实体向业务参与实体发送响应消息，响应消息包括指示信息。
指示信息为目标多播承载的标识。或者，
指示信息为目标多播承载的标识和第一指示信息，第一指示信息用于指示业务参与实体，通过目标多播承载发送终端群组的业务数据。或者，
指示信息为目标多播承载的标识和第二指示信息，第二指示信息用于指示业务参与实体，不向终端群组中位于服务区域内的终端发送终端群组的业务数据。
在一种可能的设计中，当目标业务实体接收来自业务参与实体的第一通知消息，第一通知消息用于通知目标业务实体，业务参与实体停止通过目标多播承载发送终端群组的业务数据。则目标业务实体可以向第一业务参与实体发送指示信息，指示信息用于指示第一业务参与实体通过目标多播承载发送终端群组的业务数据。
在一种可能的设计中，目标业务实体接收来自第二业务参与实体的第二通知消息，第二通知消息包括目标多播承载的标识、服务区域的标识。
第七方面，本申请提供一种装置，该装置可以是目标业务实体，也可以是目标业务实体内的芯片。该装置具有实现上述第一方面的各实施例的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
在一种可能的设计中，当该装置为目标业务实体时，目标业务实体包括：处理单元和通信单元，处理单元例如可以是处理器，通信单元例如可以是收发器，收发器包括射频电路，可选地，所述业务控制实体还包括存储单元，该存储单元例如可以是存储器。当业务控制实体包括存储单元时，该存储单元存储有计算机执行指令，该处理单元与该存储单元连接，该处理单元执行该存储单元存储的计算机执行指令，以使该目标业务实体执行上述第一方面任意一项的通信方法。
在另一种可能的设计中，当该装置为目标业务实体内的芯片时，芯片包括：处理单元和通信单元，所述处理单元例如可以是处理器，所述通信单元例如可以是输入/输出接口、管脚或电路等。该处理单元可执行存储单元存储的计算机执行指令，以使上述第一方面任意一项的通信方法被执行。可选地，所述存储单元为所述芯片内的存储单元，如寄存器、缓存等，所述存储单元还可以是所述目标业务实体内的位于所述芯片外部的存储单元，如只读存储器(read-only memory，ROM)、可存储静态信息和指令的其他类型的静态存储设备、随机存取存储器(random access memory，RAM)等。
其中，上述任一处提到的处理器，可以是一个通用的中央处理器(Central Processing Unit，CPU)，微处理器，特定应用集成电路(application-specific integrated circuit，ASIC)，或一个或多个用于控制上述第一方面的通信方法的程序执行的集成电路。
第八方面，本申请提供一种装置，该装置可以是业务参与实体，也可以是业务参与实体内的芯片。该装置具有实现上述第二方面的各实施例的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
在一种可能的设计中，当该装置为业务参与实体时，业务参与实体包括：处理单元和通信单元，所述处理单元例如可以是处理器，所述通信单元例如可以是收发器，所述收发器包括射频电路，可选地，所述业务参与实体还包括存储单元，该存储单元例如可以是存储器。当业务参与实体包括存储单元时，该存储单元存储有计算机执行指令，该处理单元与该存储单元连接，该处理单元执行该存储单元存储的计算机执行指令，以使该业务参与实体执行上述第二方面任意一项的通信方法。
在另一种可能的设计中，当该装置为业务参与实体内的芯片时，芯片包括：处理单元和通信单元，所述处理单元例如可以是处理器，所述通信单元例如可以是输入/输出接口、管脚或电路等。该处理单元可执行存储单元存储的计算机执行指令，以使上述第二方面任意一项的通信方法被执行。可选地，所述存储单元为所述芯片内的存储单元，如寄存器、缓存等，所述存储单元还可以是所述业务参与实体内的位于所述芯片外部的存储单元，如ROM、可存储静态信息和指令的其他类型的静态存储设备、RAM等。
其中，上述任一处提到的处理器，可以是一个通用的CPU，微处理器，ASIC，或一个或多个用于控制上述第二方面的通信方法的程序执行的集成电路。
第九方面，本申请提供一种装置，该装置可以是业务控制实体，也可以是业务控制实体内的芯片。该装置具有实现上述第三方面的各实施例的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
在一种可能的设计中，当该装置为业务控制实体时，业务控制实体包括：处理单元和通信单元，处理单元例如可以是处理器，通信单元例如可以是收发器，收发器包括射频电路，可选地，所述业务控制实体还包括存储单元，该存储单元例如可以是存储器。当业务控制实体包括存储单元时，该存储单元存储有计算机执行指令，该处理单元与该存储单元连接，该处理单元执行该存储单元存储的计算机执行指令，以使该业务控制实体执行上述第三方面任意一项的通信方法。
在另一种可能的设计中，当该装置为业务控制实体内的芯片时，芯片包括：处理单元和通信单元，所述处理单元例如可以是处理器，所述通信单元例如可以是输入/输出接口、管脚或电路等。该处理单元可执行存储单元存储的计算机执行指令，以使上述第三方面任意一项的通信方法被执行。可选地，所述存储单元为所述芯片内的存储单元，如寄存器、缓存等，所述存储单元还可以是所述业务控制实体内的位于所述芯片外部的存储单元，如ROM、可存储静态信息和指令的其他类型的静态存储设备、RAM等。
其中，上述任一处提到的处理器，可以是一个通用的CPU，微处理器，ASIC，或一个或多个用于控制上述第三方面的通信方法的程序执行的集成电路。
第十方面，本申请提供一种装置，该装置可以是业务参与实体，也可以是业务参与实体内的芯片。该装置具有实现上述第四方面的各实施例的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
在一种可能的设计中，当该装置为业务参与实体时，业务参与实体包括：处理单元和通信单元，所述处理单元例如可以是处理器，所述通信单元例如可以是收发器，所述收发器包括射频电路，可选地，所述业务参与实体还包括存储单元，该存储单元例如可以是存储器。当业务参与实体包括存储单元时，该存储单元存储有计算机执行指令，该处理单元与该存储单元连接，该处理单元执行该存储单元存储的计算机执行指令，以使该业务参与实体执行上述第四方面任意一项的通信方法。
在另一种可能的设计中，当该装置为业务参与实体内的芯片时，芯片包括：处理单元和通信单元，所述处理单元例如可以是处理器，所述通信单元例如可以是输入/输出接口、管脚或电路等。该处理单元可执行存储单元存储的计算机执行指令，以使上述第四方面任意一项的通信方法被执行。可选地，所述存储单元为所述芯片内的存储单元，如寄存器、缓存等，所述存储单元还可以是所述业务参与实体内的位于所述芯片外部的存储单元，如ROM、可存储静态信息和指令的其他类型的静态存储设备、RAM等。
其中，上述任一处提到的处理器，可以是一个通用的CPU，微处理器，ASIC，或一个或多个用于控制上述第四方面的通信方法的程序执行的集成电路。
第十一方面，本申请提供一种装置，该装置可以是业务参与实体，也可以是业务参与实体内的芯片。该装置具有实现上述第五方面的各实施例的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
在一种可能的设计中，当该装置为业务参与实体时，业务参与实体包括：处理单元和通信单元，所述处理单元例如可以是处理器，所述通信单元例如可以是收发器，所述收发器包括射频电路，可选地，所述业务参与实体还包括存储单元，该存储单元例如可以是存储器。当业务参与实体包括存储单元时，该存储单元存储有计算机执行指令，该处理单元与该存储单元连接，该处理单元执行该存储单元存储的计算机执行指令，以使该业务参与实体执行上述第五方面任意一项的通信方法。
在另一种可能的设计中，当该装置为业务参与实体内的芯片时，芯片包括：处理单元和通信单元，所述处理单元例如可以是处理器，所述通信单元例如可以是输入/输出接口、管脚或电路等。该处理单元可执行存储单元存储的计算机执行指令，以使上述第五方面任意一项的通信方法被执行。可选地，所述存储单元为所述芯片内的存储单元，如寄存器、缓存等，所述存储单元还可以是所述业务参与实体内的位于所述芯片外部的存储单元，如ROM、可存储静态信息和指令的其他类型的静态存储设备、RAM等。
其中，上述任一处提到的处理器，可以是一个通用的CPU，微处理器，ASIC，或一个或多个用于控制上述第五方面的通信方法的程序执行的集成电路。
第十二方面，本申请提供一种装置，该装置可以是业务控制实体，也可以是业务控制实体内的芯片。该装置具有实现上述第六方面的各实施例的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
在一种可能的设计中，当该装置为业务控制实体时，业务控制实体包括：处理单元和通信单元，所述处理单元例如可以是处理器，所述通信单元例如可以是收发器，所述收发器包括射频电路，可选地，所述业务控制实体还包括存储单元，该存储单元例如可以是存储器。当业务控制实体包括存储单元时，该存储单元存储有计算机执行指令，该处理单元与该存储单元连接，该处理单元执行该存储单元存储的计算机执行指令，以使该业务控制实体执行上述第六方面任意一项的通信方法。
在另一种可能的设计中，当该装置为业务控制实体内的芯片时，芯片包括：处理单元和通信单元，所述处理单元例如可以是处理器，所述通信单元例如可以是输入/输出接口、管脚或电路等。该处理单元可执行存储单元存储的计算机执行指令，以使上述第六方面任意一项的通信方法被执行。可选地，所述存储单元为所述芯片内的存储单元，如寄存器、缓存等，所述存储单元还可以是所述业务控制实体内的位于所述芯片外部的存储单元，如ROM、可存储静态信息和指令的其他类型的静态存储设备、RAM等。
其中，上述任一处提到的处理器，可以是一个通用的CPU，微处理器，ASIC，或一个或多个用于控制上述第六方面的通信方法的程序执行的集成电路。
第十三方面，本申请提供一种通信方法，该方法可由目标业务实体或目标业务实体内的芯片执行，其中，目标业务实体可以是业务控制实体或多播承载管理实体。该方法包括：目标业务实体接收来自第一业务参与实体的第一请求消息，第一请求消息包括目标多播承载的标识和终端群组的群组标识，第一请求消息用于请求使用目标多播承载发送终端群组的业务数据；目标业务实体向第一业务参与实体发送第一响应消息，第一响应消息用于指示第一业务参与实体使用目标多播承载发送终端群组的业务数据。
在一种可能的实现方式中，第一响应消息包括第一指示信息，第一指示信息用于指示第一业务参与实体使用目标多播承载发送终端群组的业务数据。
在一种可能的实现方式中，目标业务实体接收来自第二业务参与实体的第二请求消息，第二请求消息包括目标多播承载的标识和终端群组的群组标识，第二请求消息用于请求使用目标多播承载发送终端群组的业务数据；目标业务实体向第二业务实体发送第二响应消息，第二响应消息用于指示第二业务参与实体不使用目标多播承载发送终端群组的业务数据。
在一种可能的实现方式中，第二响应消息包括第二指示信息，第二指示信息用于指示第二业务参与实体不使用目标多播承载发送终端群组的业务数据。
在一种可能的实现方式中，目标业务实体接收来自第三业务参与实体的上报消息，上报消息包括目标多播承载的标识。
在一种可能的实现方式中，上报消息还包括第三业务参与实体的地址信息。
第十四方面，本申请提供一种通信方法，该方法可由业务参与实体或业务参与实体内的芯片执行。该方法包括：业务参与实体向目标业务实体发送请求消息，请求消息包括目标多播承载的标识和终端群组的群组标识，请求消息用于请求使用目标多播承载发送终端群组的业务数据；业务参与实体接收来自目标业务实体的响应消息，响应消息用于指示业务参与实体使用目标多播承载发送终端群组的业务数据。
在一种可能的实现方式中，响应消息包括第一指示信息，第一指示信息用于指示业务参与实体使用目标多播承载发送终端群组的业务数据。
在一种可能的实现方式中，业务参与实体使用目标多播承载发送终端群组的业务数据。
第十五方面，本申请提供一种装置，该装置可以是目标业务实体，也可以是目标业务实体内的芯片。该装置具有实现上述第十三方面的各实施例的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
在一种可能的设计中，当该装置为目标业务实体时，业务控制实体包括：处理单元和通信单元，处理单元例如可以是处理器，通信单元例如可以是收发器，收发器包括射频电路，可选地，所述业务控制实体还包括存储单元，该存储单元例如可以是存储器。当业务控制实体包括存储单元时，该存储单元存储有计算机执行指令，该处理单元与该存储单元连接，该处理单元执行该存储单元存储的计算机执行指令，以使该目标业务实体执行上述第十三方面任意一项的通信方法。
在另一种可能的设计中，当该装置为目标业务实体内的芯片时，芯片包括：处理单元和通信单元，所述处理单元例如可以是处理器，所述通信单元例如可以是输入/输出接口、管脚或电路等。该处理单元可执行存储单元存储的计算机执行指令，以使上述第十三方面任意一项的通信方法被执行。可选地，所述存储单元为所述芯片内的存储单元，如寄存器、缓存等，所述存储单元还可以是所述业务控制实体内的位于所述芯片外部的存储单元，如ROM、可存储静态信息和指令的其他类型的静态存储设备、RAM等。
其中，上述任一处提到的处理器，可以是一个通用的CPU，微处理器，ASIC，或一个或多个用于控制上述第十三方面的通信方法的程序执行的集成电路。
第十六方面，本申请提供一种装置，该装置可以是业务参与实体，也可以是业务参与实体内的芯片。该装置具有实现上述第十四方面的各实施例的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
在一种可能的设计中，当该装置为业务参与实体时，业务参与实体包括：处理单元和通信单元，所述处理单元例如可以是处理器，所述通信单元例如可以是收发器，所述收发器包括射频电路，可选地，所述业务参与实体还包括存储单元，该存储单元例如可以是存储器。当业务参与实体包括存储单元时，该存储单元存储有计算机执行指令，该处理单元与该存储单元连接，该处理单元执行该存储单元存储的计算机执行指令，以使该业务参与实体执行上述第十四方面任意一项的通信方法。
在另一种可能的设计中，当该装置为业务参与实体内的芯片时，芯片包括：处理单元和通信单元，所述处理单元例如可以是处理器，所述通信单元例如可以是输入/输出接口、管脚或电路等。该处理单元可执行存储单元存储的计算机执行指令，以使上述第四方面任意一项的通信方法被执行。可选地，所述存储单元为所述芯片内的存储单元，如寄存器、缓存等，所述存储单元还可以是所述业务参与实体内的位于所述芯片外部的存储单元，如ROM、可存储静态信息和指令的其他类型的静态存储设备、RAM等。
其中，上述任一处提到的处理器，可以是一个通用的CPU，微处理器，ASIC，或一个或多个用于控制上述第十四方面的通信方法的程序执行的集成电路。
第十七方面，本申请还提供一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机执行上述各方面所述的方法。
第十八方面，本申请还提供一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述各方面所述的方法。
本申请的这些方面或其他方面在以下实施例的描述中会更加简明易懂。
附图说明
图1为现有技术中的紧急任务服务系统架构；
图2为本申请所适用的一种可能的系统架构；
图3为本申请提供的一种通信方法示意图；
图4为本申请提供的另一种通信方法示意图；
图5为本申请提供的另一种通信方法示意图；
图6为本申请提供的另一种通信方法示意图；
图7为本申请提供的另一种通信方法示意图；
图8为本申请提供的另一种通信方法示意图；
图9为本申请提供的一种装置示意图；
图10为本申请提供的另一种装置示意图；
图11为本申请提供的一种装置示意图；
图12为本申请提供的另一种装置示意图；
图13为本申请提供的另一种通信方法示意图；
图14为本申请提供的另一种装置示意图；
图15为本申请提供的另一种装置示意图；
图16为本申请提供的另一种装置示意图；
图17为本申请提供的另一种装置示意图；
图18为本申请提供的另一种装置示意图；
图19为本申请提供的另一种装置示意图；
图20为本申请提供的另一种装置示意图；
图21为本申请提供的另一种装置示意图。
具体实施方式
为了使本申请的目的、技术方案和优点更加清楚，下面将结合附图对本申请作进一步地详细描述。方法实施例中的具体操作方法也可以应用于装置实施例或系统实施例中。其中，在本申请的描述中，除非另有说明，“多个”的含义是两个或两个以上。
需要说明的的是，本申请的通信方法可由装置执行。该装置可以是业务控制实体、多播承载管理实体或业务参与实体，或者是业务控制实体内的芯片、多播承载管理实体内的芯片或业务参与实体内的芯片。
为方便说明，本申请，以装置为业务控制实体、多播承载管理实体或业务参与实体为例，对通信方法进行说明，对于装置为业务控制实体内的芯片、多播承载管理实体内的芯片或业务参与实体内的芯片的实现方法，可参考装置为业务控制实体、多播承载管理实体或业务参与实体的通信方法的具体说明，不再重复介绍。
本申请中，MC service entity具有以下功能：接收终端上行单播数据；使用单播或多播方式向终端群组内的终端下发下行数据，该数据可以是控制信令，如MCPTT业务中群组呼叫请求消息。也可以是媒体数据，如语音，视频，数据等。还可以是媒体面控制信令，如MCPTT业务中的话权请求消息等。支持终端接收的下行数据在单播和多播传输方式之间的业务连续性。其中，MC service entity按功能划分，在逻辑上可分为业务控制实体和业务参与实体。
业务控制实体，是从群组呼叫管理角度定义的逻辑实体，在群组呼叫中承担主控功能，直接或间接获取终端群组成员的位置信息，以及从终端侧直接或间接接收多播承载质量报告，业务控制实体可根据终端群组成员的位置信息、接收多播承载质量报告，决策使用单播还是多播向终端群组成员发送数据。业务控制实体，例如包括控制紧急任务服务服务器(Controlling MC service server)等。
业务参与实体，用于终端的注册及向终端发送业务数据等，即终端注册在业务参与实体，业务参与实体在群组呼叫中负责路由群组成员发出的请求或响应，以及，将业务控制实体的请求消息路由给群组成员。可以理解为，业务参与实体与终端之间直接通信，业务参与实体，例如包括参与紧急任务服务服务器(Participating MC service server)。
需要说明的是，在第五代(5th generation，5G)通信中，多播承载，包括多播承载和广播承载；在第四代(4th generation，4G)中，多播承载也称为多媒体广播/组播服务(Multimedia Broadcast/Multicast Service，MBMS)承载。本申请中，将统一使用多播承载。
在具体的业务中，当MC service entity为MC service server时，则MC service server可以是MCPTT server，MCVideo server，MCData server或者其他类型的具备类似功能的服务器。
当业务控制实体为Controlling MC service server时，则Controlling MC service server在具体的业务中可以是controlling MCPTT server，controlling MCVideo server，controlling MCData server或者其他类型的具备类似功能的服务器。
当业务参与实体为participating MC service server时，则participating MC service server在具体的业务中可以是participating MCPTT server，participating MCVideo  server，participating MCData server或者其他类型的具备类似功能的服务器，本发明不做限制。
如图1所示，为现有技术中的紧急任务服务系统架构。例如，业务参与实体共注册有3个终端，分别为终端1、终端2、终端3。若终端1和终端2构成一个群组，称为终端群组1，即终端群组1＝{终端1、终端2}，则终端群组1内的终端的通信由一个业务控制实体控制，例如由业务控制实体1控制。再例如，终端群组2＝{终端2，终端3}，且终端群组2内的通信由业务控制实体2控制。再例如，终端群组3＝{终端1，终端2，终端3}，终端群组3内的通信由业务控制实体3控制。
因此，一个业务参与实体可对应多个业务控制实体，具体地，一个业务参与实体内的终端构成的每个终端群组，可对应一个业务控制实体，因此有多少个终端群组，则可以对应多少个业务控制实体，每个业务控制实体控制一个终端群组内终端的通信。
需要说明的是，业务参与实体和业务控制实体都是逻辑上的划分，在物理实体上，业务参与实体与业务控制实体可以分别是两个物理实体或分别是两个物理实体的一部分，也可以是集成于同一个物理实体。
基于图1所示的紧急任务服务系统架构，如图2所示，为本申请所适用的一种可能的系统架构。其中，多个业务参与实体中的终端构成一个终端群组，该终端群组由一个业务控制实体控制，该业务控制实体可以集成于其中任一业务参与实体，也可以是在物理上独立于各业务参与实体。
可选地，系统架构中还包括多播承载管理实体，多播承载管理实体主要用于对系统中使用到的多播或广播承载进行管理，例如存储多播承载或广播承载相关信息，包括多播承载的标识、服务区域的标识，以及二者之间的对应关系，还记录正在使用的多播承载及正在使用该多播承载的业务参与实体的标识，以及，还可以记录正在使用的多播承载对应的终端群组的标识等。多播承载管理实体，也可以称为多播承载控制实体，例如可以是多播承载管理服务器等。
可选地，多播承载管理实体的功能可以集成于业务控制实体，即可以取消多播承载管理实体，并在业务控制实体中集成多播承载实体的功能。实际应用中，视实际需要，可以在业务控制实体中集成多播承载管理实体的功能，也可以是将业务控制实体和多播承载管理实体分开单独设置。也可以在业务参与实体中集成多播承载管理实体的功能，此时业务参与实体和多播承载管理实体可以集成部署于同一个物理网络设备中，也可以是将业务参与实体和多播承载管理实体分开单独设置。
为方便说明，本申请，以业务控制实体，业务参与实体和多播承载管理实体分开单独设置为例进行说明。
如图2所示，给出了一种具体示例。其中，业务参与实体1、业务参与实体2、业务参与实体3，分别管理了多个注册的终端，并且，当前业务参与实体1中的终端1、终端2、终端3，业务参与实体2中的终端4、终端5，以及业务参与实体3中的终端6、终端7，组建成为一个终端群组，例如称为终端群组A，则终端群组A＝{终端1，终端2，终端3，终端4，终端5，终端6，终端7}，并且终端群组A由图2中的业务控制实体控制。
其中，图2中的终端，可以是紧急任务服务客户端(Mission Critical Service Client)，是与MC Service server对等的应用层实体，主要负责应用层事务的处理。在具体的业 务中，可以是MCPTT client，MCVideo client，MCData client或者具备类似功能的业务客户端。
作为示例，图2所示的系统的一个应用场景可以是：当某个地点发生了交通事故，需要交警、医院、公安同时介入，例如，交警使用的通信设备，如对讲机等，是注册在业务参与实体1，医院使用的通信设备，如终端显示设备、对讲机等，是注册在业务参与实体2，公安使用的通信设备，如对讲机等，是注册在业务参与实体3，并且，终端1～终端7构成一个终端群组A。群组通信的下行数据是由业务控制实体向终端群组A发送的下行数据。
具体地，可由业务控制实体或者业务参与实体决策，是采用单播还是多播的方式传输下行群组通信数据，如果使用多播，则可以使用多播承载发送终端群组通信下行数据。
目前，针对上述应用场景，现有实现方式是由每个业务参与实体根据注册的终端群组中的终端的位置独立决策使用和/或建立多播承载。
一种可能的情况是：终端群组中的每个终端，均可以触发业务参与实体使用或建立多播承载，因而在同一服务区域就会有多个不同的多播承载传输同样的内容，造成了不必要的多播承载资源浪费。
另外一种可能的情况是：终端群组中的每个终端，均可以触发业务实体使用或建立多播承载，且这些业务参与实体使用的是同一个多播承载，此时终端群组的终端，同时接收多个业务参与实体发送的相同的业务数据。
因此，现有技术方法，由多个业务参与实体使用相同或不同的多播承载，向终端群组的终端发送相同的业务数据，一方面，降低了通信质量，另一方面，造成资源的浪费。
为解决上述问题，本申请提出两种通信方法，用以实现在图2所示的系统架构下，节约资源，提高通信质量。
如图3所示，为本申请提供的一种通信方法示意图。该方法包括：
步骤301、业务控制实体获取多播承载的标识。
例如，当终端群组正在进行群组通信业务时，如正在进行群组语音通信，或正在进行群组视频通信，或者正在进行群组数据(如文件和数据流)通信时，业务控制实体决定在服务区域使用多播承载传输终端群组的下行数据，此时，业务控制实体获取多播承载的标识，该多播承载用于在服务区域内传输终端的业务数据。
在服务区域有一个或多个多播承载，每个多播承载用一个多播承载的标识来表示，每个多播承载可以用于传输一个或多个终端群组的业务数据。业务控制实体获取终端群组在服务区域对应的多播承载的标识，也可以理解为，业务控制实体从服务区域的一个或多个多播承载中，获取服务区域内可以用于传输该终端群组的业务数据的多播承载的标识。
业务控制实体可以根据终端群组内的终端上报的终端位置信息，确定位于同一服务区域的终端的数目，进一步地，若位于同一服务区域的终端的数目满足预设条件，则决定对终端群组内位于该服务区域内的终端，使用多播承载进行业务数据的传输。
业务数据可以是业务控制信令，如MCPTT/MCVideo呼叫控制消息；或者是媒体面控制信令，如MCPTT话权控制消息(如话权占用消息)，MCVideo传输控制消息(如 媒体接收通知消息)；或者是媒体数据，如语音，视频，文件等。
位置信息可以是地理位置信息，或者是经纬度信息，或者是小区标识，或者是服务区域标识，或者是以上两种或多种的组合。
再比如，业务控制实体根据配置策略，决定对终端群组内位于该服务区域内的终端，使用多播承载进行业务数据的传输，其中，配置策略指示在该服务区域始终使用多播承载传输终端群组的数据，或者，配置策略指示在特定时间段内在该服务区域始终使用多播承载传输终端群组的数据。
步骤302、业务控制实体向终端群组关联的第一业务参与实体发送第一指示消息，第一业务参与实体接收来自业务控制实体的第一指示消息。
第一指示消息，用于指示第一业务参与实体在服务区域，通过多播承载的标识对应的多播承载发送终端群组的业务数据。
步骤303、业务控制实体向终端群组关联的第二业务参与实体发送第二指示消息，第二业务参与实体接收来自业务控制实体的第二指示消息。
第二指示消息，用于指示第二业务参与实体，不向终端群组内位于服务区域的终端发送终端群组的业务数据。
上述步骤302中，第一指示消息可以是广播承载使用消息，或者是广播承载使用通知消息。可选地，第一指示消息中包括服务区域的标识、多播承载的标识、终端群组的标识及业务数据发送指示。可以理解为，业务控制实体通过第一指示消息，指示允许第一业务参与实体通过多播承载在服务区域发送终端群组的业务数据。也可以理解为，业务控制实体通过第一指示消息，指示第一业务参与实体能够通过多播承载在服务区域发送终端群组的业务数据。
即，第一指示消息，用于指示第一业务参与实体具备发送终端群组的业务数据的能力。至于第一业务参与实体什么时候向终端群组的终端发送业务数据，视实际情况而定。一种实现方式为，第一业务参与实体接收到第一指示消息后，立即在服务区域发送业务数据。另一种实现方式为，当第一业务参与实体接收到第一指示消息后，不立即在服务区域发送业务数据，而是在第一业务参与实体接收到业务控制实体发送的另一个指示消息，该指示消息用于指示第一业务参与实体立即在服务区域发送业务数据，此时，第一业务参与实体才开始在服务区域发送业务数据。
上述步骤303中的第二指示消息，可以是广播承载使用消息，或者是广播承载使用指示消息。可选地，该第二指示消息中包括服务区域的标识、多播承载的标识、终端群组的标识及业务数据发送指示。第二指示消息，用于指示第二业务参与实体，不向终端群组中位于服务区域内的终端发送终端群组的业务数据。
也可以理解为，第二指示消息，用于指示第二业务参与实体，不能够向终端群组中位于服务区域内的终端发送终端群组的业务数据。
也可以理解为，第二指示消息，用于指示第二业务参与实体，不允许向终端群组中位于服务区域内的终端发送终端群组的业务数据。
作为一种实现方式，业务数据发送指示，可以使用1个比特来表示。例如，当业务数据发送指示为“1”时，指示在服务区域通过多播承载发送终端群组的业务数据。当业务数据发送指示为“0”时，指示在服务区域不向终端群组内位于服务区域的终端发送终端群组的业务数据。
在该实现方式中，则上述第一指示信息中的业务数据发送指示为“1”，上述第二指示信息中的业务数据发送指示为“0”。
当然，也可以是用“1”指示在服务区域不向终端群组内位于服务区域的终端发送终端群组的业务数据，用“0”指示在服务区域通过多播承载发送终端群组的业务数据，则上述第一指示信息中的业务数据发送指示为“0”，上述第二指示信息中的业务数据发送指示为“1”。本申请不做限定。
上述步骤303中，当第二业务参与实体接收到第二指示消息后，如果第二业务参与实体当前正在向终端群组中位于服务区域内的终端发送终端群组的业务数据，则停止发送。如果第二业务参与实体当前没有向终端群组中位于服务区域内的终端发送终端群组的业务数据，则继续保持不向终端群组中位于服务区域内的终端发送终端群组的业务数据。
在另一实现方式中，还可以是第一指示消息包括服务区域的标识、多播承载的标识、终端群组的标识。当第一业务参与实体接收到该第一指示信息时，按照预先约定，默认第一业务参与实体可以在服务区域通过多播承载发送业务数据。此时服务区域的标识、多播承载的标识、终端群组的标识一种或者多种的组合可以视为隐式业务数据发送指示。以及，第二指示消息中包括服务区域的标识、多播承载的标识、终端群组的标识，以及还包括占位信息，该占位信息可以是任意信息，当第二业务参与实体接收到该占位信息时，就确定不向终端群组中位于服务区域内的终端发送终端群组的业务数据。
或者，在另一实现方式中，第一指示消息包括服务区域的标识、多播承载的标识、终端群组的标识和占位信息，当第一业务参与实体接收到该第一指示信息时，获取到该占位信息，该占位信息可以是任意信息，当第一业务参与实体接收到该占位信息时，就确定可以在服务区域通过多播承载发送业务数据。以及，第二指示信息中包括服务区域的标识、多播承载的标识、终端群组的标识，且不包括占位信息，则按照预先约定，默认第二业务参与实体不向终端群组中位于服务区域内的终端发送终端群组的业务数据。
其中，第一业务参与实体与第二业务参与实体不同，终端群组中存在至少一个终端注册在第一业务参与实体，终端群组中存在至少一个终端注册在第二业务参与实体。
其中，第一业务参与实体为终端群组内的终端注册的业务参与实体中的一个业务参与实体。第二业务参与实体是终端群组内的终端注册的业务参与实体中除第一业务参与实体之外的业务参与实体。
例如，参考图2，终端群组A的终端注册的业务参与实体为业务参与实体1、业务参与实体2和业务参与实体3，则可以是：
第一业务参与实体为：业务参与实体1，第二业务参与实体为：业务参与实体2、业务参与实体3，或者，
第一业务参与实体为：业务参与实体2，第二业务参与实体为：业务参与实体1、业务参与实体3，或者，
第一业务参与实体为：业务参与实体3，第二业务参与实体为：业务参与实体1、业务参与实体2。
在302之后，还包括，第一业务参与实体向终端发送业务接收指示消息，该业务 接收指示消息中包含多播承载的标识，可选的，还包括终端群组的标识。
在一种实现方式中，第一业务参与实体通过多播传输方式向服务区域发送该指示消息，此时，接收到该业务接收指示消息的终端可以包括终端群组中的部分或全部终端，也可以包括其他群组的终端，并且这些终端可以是通过第一业务参与实体注册的，也可以是通过其他业务参与实体注册的。该实现方式可以理解为，第一业务参与实体在服务区域，通过多播传输方式，向该服务区域的部分或所有终端发送业务接收指示消息。
在又一种实现方式中，第一业务参与实体通过单播方式，向终端群组中通过第一业务参与实体注册的终端发该指示消息。
在又一种实现方式中，第一业务参与实体通过单播方式，向终端群组中通过第一业务参与实体注册的,且当前位于服务区域内的终端发该业务接收指示消息。
该业务接收指示消息用于指示终端，通过多播承载接收业务数据。如果接收到该消息的终端不在服务区域，则不能收到业务数据。如果接收到该消息的终端不是终端群组内的终端，则由其他处理方式进行处理，如在尝试解密消息内容失败后，丢弃该数据包，或者判断自己不是该终端群组内的终端时，丢弃该数据包。
上述步骤303之后，还包括，第二业务参与实体向终端发送业务接收指示消息，该业务接收指示消息也可以称为第四指示消息。该业务接收指示消息中包含多播承载的标识，可选的，还包括终端群组的标识。该业务接收指示消息的作用及实现方式，与上述第一业务参与实体向终端发送的业务接收指示消息的作用及实现方式相同，可参考前述描述，此处不再赘述。
通过上述步骤301～步骤303，业务控制实体指示第一业务参与实体在服务区域，通过多播承载发送终端群组的业务数据，并指示第二业务参与实体不向终端群组中位于服务区域内的终端发送终端群组的业务数据，从而，终端群组内位于服务区域的终端，只会从第一业务参与实体接收终端群组的业务数据，避免了从多个业务参与实体接收相同的业务数据，节约了终端开销。
下面结合附图2，对上述步骤301～步骤303的实现过程进行说明。
终端群组A包括终端1～终端7，假设只有终端1～终端6位于服务区域，终端7不在服务区域。当业务控制实体决定使用多播承载在服务区域发送业务数据时，若业务控制实体确定业务参与实体1为第一业务参与实体，业务参与实体2和业务参与实体3为第二业务参与实体。则有以下步骤：
步骤1、业务控制实体获取多播承载的标识，确定使用该多播承载发送业务数据。
步骤2、业务控制实体向业务参与实体1发送第一指示消息。
该第一指示消息用于指示业务参与实体1，通过多播承载发送终端群组的业务数据。
当业务参与实体1接收到第一指示消息后，还向终端1～终端3分别发送业务接收指示消息。即，业务参与实体1通知终端1～终端3，通过该多播承载接收业务数据。
步骤3、业务控制实体向业务参与实体2和业务参与实体3发送第二指示消息。
该第二指示消息用于指示业务参与实体2和业务参与实体3，不向终端群组中位于服务区域内的终端发送终端群组的业务数据，也即，指示业务参与实体2和业务参与实体3不向终端1～终端6发送业务数据。
当业务参与实体2接收到第二指示消息后，例如，作为一种实现方式，可以向终端4～终端5分别发送业务接收指示消息(或称为第四指示消息)。即，业务参与实体2通知终端4～终端5，通过该多播承载接收业务数据。
当业务参与实体3接收到第二指示消息后，例如，作为一种实现方式，可以向终端6发送业务接收指示消息(或称为第四指示消息)。即，业务参与实体3通知终端6，通过该多播承载接收业务数据。
步骤4、业务参与实体1通过多播承载，在服务区域发送终端群组的业务数据，终端1～终端6通过该多播承载，接收业务数据。
从而，通过上述步骤1～步骤4，终端群组A中位于服务区域的终端1～终端6，只从业务参与实体1接收业务数据，避免了从多个业务参与实体接收相同的业务数据，节约了终端开销。
上述步骤301中，业务控制实体获取多播承载的标识的方法，例如可以包括：
步骤A、业务控制实体向多播承载管理实体发送查询消息，多播承载管理实体接收来自业务控制实体的查询消息。
其中，查询消息包括服务区域的标识，所述查询消息用于请求查询所述服务区域对应的多播承载。
步骤B、多播承载管理实体向业务控制实体发送响应消息，业务控制实体接收来自多播承载管理实体的响应消息。当响应消息包括多播承载的标识，流程结束；当响应消息不包括多播承载的标识，转到步骤C。
其中，当响应消息包括多播承载的标识，表明该多播承载可以使用，且可以用于在服务区域发送下行业务数据，因此业务控制实体成功获取到服务区域内的多播承载的标识。
当响应消息不包括多播承载的标识，例如响应消息为空，或者响应消息包括一个指示获取失败的指示信息，则业务控制实体确定未获取到多播承载的标识。
步骤C、业务控制实体向终端群组关联的第三业务参与实体发送请求消息，第三业务参与实体接收来自业务控制实体的请求消息。
其中，第三业务参与实体为与终端群组关联的业务参与实体中的任一业务参与实体，以图2为例，则第三业务参与实体可以是业务参与实体1，或者是业务参与实体2，或者还可以是业务参与实体3。
其中，请求消息包括服务区域的标识，所述请求消息用于请求第三业务参与实体在服务区域的标识对应的服务区域内建立多播承载。该请求消息也可以称为广播承载建立请求消息，或广播承载请求消息。
即，当业务控制实体从多播承载管理实体中请求获取多播承载的标识失败后，则指示第三业务参与实体在该服务区域建立一个多播承载。
步骤D、第三业务参与实体向多播承载管理实体发送通知消息，多播承载管理实体接收来自第三业务参与实体的通知消息。
其中，通知消息包括多播承载的标识、服务区域的标识，以及还包括与多播承载有关的信息。
当第三业务参与实体建立多播承载成功后，则向多播承载管理实体发送上述通知消息。
步骤E、第三业务参与实体向业务控制实体发送响应消息，业务控制实体接收来自第三业务参与实体的响应消息。
在一种实现方式中，响应消息包括多播承载的标识。即，第三业务参与实体在建立多播承载之后，一方面，将多播承载的标识发送至多播承载管理实体进行存储，另一方面，还将多播承载的标识发送给业务控制实体，从而业务控制实体可成功获取到多播承载的标识。至此，流程结束。
在另一种实现方式中，响应消息包括通知信息，该通知信息用于通知业务控制实体，已经成功建立多播承载并将多播承载的标识及相关信息发送至多播承载管理实体。因此，当业务控制实体接收到该通知信息，则进一步地再执行上述步骤A和步骤B，从而可获取到多播承载的标识。至此，流程结束。
可选地，当上述步骤C中的请求消息包括终端群组的标识时，表明业务控制实体请求为终端群组的标识对应的终端群组建立多播承载，此时，步骤D的通知消息还可以包括终端群组的标识，以及，步骤E的第一种实现方式中，响应消息不仅包括多播承载的标识，还可以包括终端群组的标识。
需要说明的是，上述步骤A～步骤E的操作，还可以是按照下述方式执行：
一种实现方式为，只执行步骤A和步骤B，当从多播承载管理实体中获取多播承载的标识成功或失败后，均结束流程，其中，从多播承载管理实体中获取多播承载的标识失败，则表示不再使用多播承载的传输方式。
另一种实现方式为，先执行步骤C和步骤D，即先由第三业务参与实体建立多播承载，然后将建立的多播承载发送至多播承载管理实体，接着再执行步骤A和步骤B，由业务控制实体从多播承载管理实体中获取第三业务参与实体建立的多播承载。
另一种实现方式为，先执行步骤C和步骤D，即先由第三业务参与实体建立多播承载，然后将建立的多播承载发送至多播承载管理实体，然后，执行步骤E，且步骤E的响应消息中包括第三业务参与实体建立的多播承载，即，第三业务参与实体建立多播承载后直接反馈给业务控制实体。
另一种实现方式为，先执行步骤C，即先由第三业务参与实体建立多播承载，然后，执行步骤E，且步骤E的响应消息中包括第三业务参与实体建立的多播承载，即，第三业务参与实体建立多播承载后直接反馈给业务控制实体。并且，进一步地，由业务控制实体将建立的多播承载发送至多播承载管理实体进行存储。
当然，需要说明的是，如果第三业务参与实体中包括建立好的多播承载，且该多播承载满足业务控制实体的请求，则无需再建立，而是直接发送至业务控制实体，和/或，多播承载管理实体。进一步地，如果第三业务参与实体获取多播承载失败，且建立多播承载失败，则向业务控制实体返回空消息，或返回指示失败的消息。
可选地，步骤303之后，还包括步骤304和步骤305。
步骤304、第一业务参与实体向业务控制实体发送通知消息，业务控制实体接收来自第一业务参与实体的通知消息。
其中，所述通知消息用于通知，第一业务参与实体停止通过多播承载发送终端群组的业务数据。
例如，第一业务参与实体因为某些原因，如故障、超负荷等，导致需要停止通过多播承载，在服务区域发送终端群组的业务数据，则第一业务参与实体向业务控制实 体发送通知消息，告知将要停止在服务区域通过多播承载发送业务数据。
步骤305、业务控制实体向第二业务参与实体发送第三指示消息，第二业务参与实体接收来自业务控制实体的第三指示消息。
其中，第三指示消息用于指示第二业务参与实体，向终端群组中位于服务区域内且注册在第二业务参与实体上的终端，发送终端群组的业务数据。
也即，每个第二业务参与实体，都单独向终端群组中位于服务区域，且注册在自身的终端，发送终端群组的业务数据。发送方式由自己决定，例如可以是单播，也可以是多播。
例如，参考图2，假设第一业务参与实体是业务参与实体1，第二业务参与实体为业务参与实体2、业务参与实体3。终端1～终端6位于服务区域。
当前，业务参与实体1通过多播承载发送终端群组的业务数据，且业务参与实体2和业务参与实体3不向终端1～终端6发送业务数据。即，终端1～终端6通过多播承载，从业务参与实体1接收终端群组的业务数据。
当业务参与实体1向业务控制实体发送通知消息，通知业务控制实体，业务参与实体1停止在服务区域，使用多播承载发送业务数据，从而，终端1～终端6无法通过多播承载，从业务参与实体1接收终端群组的业务数据。业务控制实体可以分别向业务参与实体2和业务参与实体3发送第三指示消息，其中，第三指示消息包括服务区域的标识。
业务参与实体2接收到第三指示消息后，确定采用单播或多播的方式，向终端4和终端5发送终端群组的业务数据。其中，当确定可以采用多播方式发送时，业务参与实体2还向由终端4和终端5构成的终端群组所对应的业务控制实体请求多播承载的标识，并使用请求的多播承载，采用广播的方式，向终端4和终端5广播发送业务数据。当确定采用单播方式发送时，则业务参与实体2向终端4、终端5采用单播方式发送终端群组的业务数据。
业务参与实体3接收到第三指示消息后，向终端6采用单播方式发送终端群组的业务数据。
在另外的一种可能的实现方式中，当业务控制实体决定，在服务区域不再使用多播承载发送业务数据时，还可以向多播承载对应的所有业务参与实体发送指示信息，例如该指示信息为停止使用多播承载消息，用于指示所有业务参与实体使用单播传输方式，向终端群组中注册在自身的终端，发送业务数据。
例如，参考图2，当业务控制实体决定在服务区域不再使用多播承载发送业务数据时，分别向业务参与实体1～业务参与实体3发送指示信息，指示参与实体1使用单播方式向终端1～终端3发送终端群组的业务数据，指示参与实体2使用单播方式向终端4～终端5发送终端群组的业务数据，指示参与实体3使用单播方式向终端6发送终端群组的业务数据。
在另外的一种可能的实现方式中，当业务控制实体决定，在服务区域不再使用多播承载发送业务数据时，还可以向多播承载对应的所有业务参与实体发送指示信息，例如该指示信息为停止使用多播承载消息，用于指示每个业务参与实体，分别向终端群组中注册在自身的终端，发送业务数据。发送数据的方式可以是单播方式，也可以是多播方式。即该实现方式中，由每个业务参与实体自己决定发送数据的方式。
例如，参考图2，当业务控制实体决定在服务区域不再使用多播承载发送业务数据时，分别向业务参与实体1～业务参与实体3发送指示信息，指示参与实体1向终端1～终端3发送终端群组的业务数据，具体采用单播方式还是多播方式，由业务参与实体1决定，指示参与实体2向终端4～终端5发送终端群组的业务数据，具体采用单播方式还是多播方式，由业务参与实体2决定，指示参与实体3向终端6发送终端群组的业务数据，且业务参与实体3决定采用单播方式发送。
通过上述通信方法，一方面，业务控制实体可控制多播承载对应的业务参与实体中的一个业务参与实体发送终端群组的业务数据，避免了多个业务参与实体同时发送相同业务数据，可节约资源，并提高通信质量；另一方面，当业务参与实体停止发送业务数据时，则每个业务参与实体各自向注册在自身的终端单独发送业务数据，使得终端能够及时接收到业务数据。
如图4，为本申请提供的另一种通信方法示意图。包括以下步骤：
步骤401、业务参与实体向目标业务实体发送请求消息，目标业务实体接收来自业务参与实体的请求消息。
其中，目标业务实体为业务控制实体或多播承载管理实体。
请求消息包括服务区域的标识和群组标识，所述请求消息用于请求查询目标多播承载，目标多播承载用于在服务区域发送终端群组的业务数据。
目标业务实体在接收到业务参与实体的请求消息后，查询目标多播承载，并获取目标多播承载的标识，其中，可以是从本地获取，如目标多播承载可以是之前预建立的，或者是接收到401消息后动态新建立的，或者是此前其他业务参与实体建立后上报到目标控制实体的，或者是此前目标控制实体请求其他业务参与实体建立并保存的，也可以是从其他多播承载管理实体获取，当然，如果未获取到目标多播承载，还可以请求任一业务参与实体建立该目标多播承载。最终，目标业务实体可以获取到目标多播承载的标识及相关信息。
进一步地，若获取到目标多播承载的标识，还查询当前是否已经有其他业务参与实体正在使用该目标多播承载，即，是否有其他业务参与实体正在使用该目标多播承载发送业务数据，或者准备使用该目标多播承载发送业务数据。若没有其他业务参与实体正在使用该目标多播承载发送业务数据，或者准备使用该目标多播承载发送业务数据，则执行步骤402。
步骤402、目标业务实体向业务参与实体发送响应消息，业务参与实体接收来自目标业务实体的响应消息。
目标业务实体将该目标多播承载的标识携带于响应消息，发送给业务参与实体。
针对上述步骤401和步骤402，还可以由下列步骤4011～步骤4014完成，即步骤4011～步骤4014作为一个整体，可替换该步骤401～步骤402。
针对上述步骤401和步骤402，还可以由下列步骤4013～步骤4014完成，即步骤4013～步骤4014作为一个整体，可替换步骤401～步骤402。
步骤4011、业务参与实体向目标业务实体发送第一请求消息，目标业务实体接收来自业务参与实体的第一请求消息。
该第一请求消息包括服务区域的标识，所述第一请求消息用于请求查询目标多播承载，所述目标多播承载用于在服务区域发送终端群组的业务数据。或者说，目标多 播承载是一个在服务区域，能够向终端群组提供多播承载传输服务的承载。
步骤4012、目标业务实体向业务参与实体发送第一响应消息，业务参与实体接收来自目标业务实体的第一响应消息。
该第一响应消息中包括目标多播承载的标识。可选地，该第一响应消息还可以包括该目标多播承载的以下参数中的部分或全部：目标多播承载的用户面地址和端口号、目标多播承载对应的服务区域、目标多播承载对应的无线频率等。
可选地，该第一响应消息中还可以包括建立该目标多播承载的业务参与实体的地址信息，该地址信息可以是互联网协议第四版(internet protocol version 4，IPv4)地址，可以是互联网协议第六版(internet protocol version 6，IPv6)地址，可以是正式域名(fully qualified domain name，FQDN),还可以是统一资源定位器(uniform resoure locator,URL)。该地址信息可以用于从目标业务实体发现并使用该目标多播承载的其他业务参与实体将业务数据转发给建立该目标多播承载的业务参与实体，该建立目标多播承载的业务参与实体将接收到的业务数据(媒体面数据和控制信令)在该目标多播承载上发送。该建立该目标多播承载的业务参与实体的地址可以是目标业务实体的地址。
例如，作为一种实现方式，该目标多播承载是由某个业务参与实体(如第三业务参与实体，该第三业务参与实体为终端群组中的终端注册的业务参与实体中的任一业务参与实体)建立的，在上述步骤4011之前，还可以包括以下步骤：
该第三业务参与实体向目标业务实体发送上报消息，该上报消息中包括该目标多播承载的标识，可选地，还包括该第三业务参与实体的地址信息。
通过该步骤，目标业务实体可以获取并存储该目标多播承载的信息，例如包括目标多播承载的标识，从而当上述业务参与实体向目标业务实体发送第一请求消息之后，目标业务实体可以从本地获取到该目标多播承载的标识，并携带于第一响应消息中发送给上述业务参与实体。
步骤4013、业务参与实体向目标业务实体发送第二请求消息，目标业务实体接收来自业务参与实体的第二请求消息。
该第二请求消息包括目标多播承载的标识和终端群组的群组标识。
第二请求消息可以用于请求目标业务实体建立目标多播承载的标识和群组标识的绑定关系。即指示目标业务实体，业务参与实体使用目标多播承载传输终端群组的业务数据。可以理解为，该第二请求消息可以用于请求使用目标多播承载发送终端群组的业务数据。
目标业务实体建立了目标多播承载的标识和群组标识的绑定关系之后，可以协调多个业务参与实体使用目标多播承载。例如，当有其他业务参与实体请求在同一服务区域传输同一群组标识的通信群组的业务数据，目标业务实体可以通知该其他业务参与实体，已经有上述业务参与实体正在使用目标多播承载，在服务区域发送终端群组的业务数据。目标业务实体将该目标多播承载的标识发送给该其他业务参与实体，并指示该其他业务参与实体无需向终端群组中位于该服务区域内的终端发送终端群组的业务数据。作为一种实现方式，目标业务实体接收来自该其他业务参与实体的请求消息，该请求消息包括目标多播承载的标识和终端群组的群组标识，该请求消息用于请求使用该目标多播承载发送该终端群组的业务数据。目标业务实体向该其他业务实体发送响应消息，该响应消息用于指示该其他业务参与实体不使用该目标多播承载发送 该终端群组的业务数据。
该其他业务参与实体收到目标业务实体的目标多播承载的标识和指示后，通知其管理的位于服务区域的终端在目标多播承载接收群组的业务数据，且该其他业务参与实体停止向终端群组中位于该服务区域的终端发送终端群组的业务数据。当然，也可以是过了一个约定的时间后，再停止向终端群组中位于该服务区域的终端发送终端群组的业务数据，该约定的时间可以是预配置的，也可能是目标业务实体发送的。
作为示例，该其他业务参与实体可以通过下述方式通知其管理的位于服务区域的终端在目标多播承载接收终端群组的业务数据：
在一种实现方式中，该其他业务参与实体通过多播传输方式，通知其管理的位于服务区域的终端在目标多播承载接收终端群组的业务数据。
在又一种实现方式中，该其他业务参与实体通过单播传输方式，通知其管理的位于服务区域的终端在目标多播承载接收终端群组的业务数据。
步骤4014、目标业务实体向业务参与实体发送第二响应消息，业务参与实体接收来自目标业务实体的第二响应消息。
可选地，该第二响应消息用于通知该业务参与实体，成功建立了目标多播承载的标识和终端群组的群组标识的绑定关系，业务参与实体可以使用目标多播承载发送终端群组的业务数据。
可以理解为，第二响应消息可以用于指示业务参与实体使用该目标多播承载发送该终端群组的业务数据。在一种实现方式中，目标业务实体可以在步骤4014的第二响应消息中携带第一指示信息，第一指示信息用于指示该业务参与实体使用目标多播承载发送终端群组的业务数据。该第一指示信息可以在第二响应消息的特定位置携带，如在第二响应消息的特定位置采用字符编码或数字编码的方式实现，具体地，第一指示信息可以用“00”表示，或用“SEND”表示。在又一种实现方式中，业务参与实体在接收到步骤4014的第二响应消息时，可以确认没有其他业务参与实体正在使用该目标多播承载，因此，该业务参与实体可以使用该目标多播承载。
这里，上述业务参与实体使用目标多播承载发送终端群组的业务数据，具体可以采用以下方式实现：
实现方式1，当该目标多播承载是由该业务参与实体建立时，该业务参与实体可以使用该目标多播承载发送该终端群组的业务数据。
实现方式2，当该目标多播承载是由其他业务参与实体建立时，该业务参与实体可以向该其他业务参与实体发送终端群组的业务数据，由该其他业务参与实体使用该目标多播承载发送该终端群组的业务数据。
在一个示例中，该业务参与实体可以向该其他业务参与实体发送指示信息，该指示信息用于指示该其他业务参与实体：使用该目标多播承载发送该终端群组的业务数据。其中，该业务参与实体可以是采用业务控制实体推送的方式，或者主动请求的方式，获取到该其他业务参与实体的信息，例如，该其他业务参与实体标识信息，和/或该其他业务参与实体的地址信息。
实现方式3，由该业务参与实体直接使用该目标多播承载发送终端群组的业务数据，具体的，该业务参与实体向该目标多播承载的用户面地址和端口号发送终端群组的业务数据。在实现方式3中，不论该目标多播承载是由哪个业务参与实体建立的， 均由该业务参与实体直接使用该目标多播承载发送终端群组的业务数据。
步骤403、业务参与实体向终端发送指示消息，终端接收来自业务参与实体的指示消息。
业务参与实体在接收到响应消息后，获取其中的目标多播承载的标识，因此，业务参与实体还向终端群组中注册在该业务参与实体的终端发送指示消息，该指示消息中包括目标多播承载的标识，该指示消息用于指示终端，在目标多播承载上接收终端群组的业务数据。
该指示消息中包含多播承载的标识，可选的，还包括终端群组的标识。
在一种实现方式中，业务参与实体通过多播传输方式向服务区域发送该指示消息，此时，接收到该业务接收指示消息的终端可以包括终端群组中的部分或全部终端，也可以包括其他群组的终端，并且这些终端可以是通过业务参与实体注册的，也可以是通过其他业务参与实体注册的。该实现方式可以理解为，业务参与实体在服务区域，通过多播传输方式，向该服务区域的部分或所有终端发送业务接收指示消息。
在又一种实现方式中，业务参与实体通过单播方式，向终端群组中通过业务参与实体注册的终端发该指示消息。
在又一种实现方式中，业务参与实体通过单播方式，向终端群组中通过业务参与实体注册的,且当前位于服务区域内的终端发该业务接收指示消息。
该业务接收指示消息用于指示终端，通过多播承载接收业务数据。如果接收到该消息的终端不在服务区域，则不能收到业务数据。如果接收到该消息的终端不是终端群组内的终端，则由其他处理方式进行处理，如在尝试解密消息内容失败后，丢弃该数据包，或者判断自己不是该终端群组内的终端时，丢弃该数据包。
例如，参考图2，假设终端群组中位于服务区域的终端是终端1～终端6。则作为一种实现方式，业务参与实体1向目标业务实体(业务控制实体或多播承载管理实体)发送请求消息，并在接收到的响应消息中获取到目标多播承载的标识，从而通知终端1～终端3，在该目标多播承载上接收业务数据。
同样地，作为一种实现方式，业务参与实体2可以通知终端4、终端5在该目标多播承载上接收业务数据。业务参与实体3可以通知终端6在该目标多播承载上接收业务数据。
通过上述步骤401～步骤403，业务参与实体可以主动向目标业务实体获取目标多播承载的标识，在获取到目标多播承载的标识后，通知终端群组中位于服务区域且注册在自身的终端，在目标多播承载上接收业务数据，使得终端群组中位于服务区域内的终端都在目标多播承载上接收业务，从而，只需要有一个业务参与实体发送业务数据，便可以使得终端群组的终端都接收到业务数据，可减少业务参与实体的资源开销。
下面具体介绍，每个业务参与实体如何判断自己是否可以使用目标多播承载向终端群组的终端发送业务数据。
上述步骤401中，目标业务实体接收到业务参与实体发送的请求消息后，查询的结果有两种情形，下面分别说明。
情形一、查询到没有其他业务参与实体正在使用该目标多播承载
在该情形下，由于当前没有其他业务参与实体正在使用该目标多播承载，因此，目标业务实体可以通知发送请求消息的业务参与实体，可以使用该目标多播承载。具 体地，至少有以下两种实现方式：
实现方式一、目标业务实体向业务参与实体发送的响应消息包括目标多播承载的标识
该实现方式中，当响应消息中只包括目标多播承载的标识时，则可按照预先约定，业务参与实体默认没有其他业务参与实体正在使用该目标多播承载，因此，该业务参与实体可以使用该目标多播承载。
因此，当业务参与实体接收到该响应消息，获取其中的目标多播承载的标识，一方面，通过上述步骤403，向终端群组中注册在该业务参与实体的终端发送指示消息，指示终端在目标多播承载上接收业务数据，另一方面，该业务参与实体在服务区域通过目标多播承载发送终端群组的业务数据。
例如，参考图2，业务参与实体1向目标业务实体发送请求消息后，接收到的响应消息中只包括目标多播承载的标识，则业务参与实体认为当前没有其他业务参与实体使用该目标多播承载向终端群组的终端发送业务数据，因此，一方面，业务参与实体1通过指示消息通知终端1～终端3在该目标多播承载上接收业务数据，另一方面，业务参与实体1通过该目标多播承载在服务区域发送终端群组的业务数据。
当然，对于终端4～终端6，还需要业务参与实体2和业务参与实体3分别进行通知，在该目标多播承载上接收业务数据。例如，业务参与实体2也向目标业务实体发送请求消息，业务参与实体2接收到响应消息后，获取响应消息中携带的目标多播承载的标识，并且业务参与实体2还可以根据响应消息确定当前已经有其他业务参与实体在使用该目标多播承载，即业务参与实体1在使用该目标多播承载，至于如何确定，后面会详细说明。因此，业务参与实体2通过指示信息，通知终端4、终端5在该目标多播承载上接收业务数据，并且，业务参与实体2不向终端群组A的终端1～终端7发送业务数据；同样地，业务参与实体3通知终端6、终端7在该目标多播承载上接收业务数据，并且，业务参与实体3不向终端群组A的终端1～终端7发送业务数据。
实现方式二、目标业务实体向业务参与实体发送响应消息包括目标多播承载的标识和第一指示信息
其中，第一指示信息用于指示业务参与实体，通过目标多播承载发送终端群组的业务数据。
该实现方式二，与上述实现方式一的主要区别在于：通过第一指示信息，显示地通知业务参与实体，当前可以通过目标多播承载发送终端群组的业务数据。其他方面，与上述实现方式一相同，可参考上述描述，不再赘述。
情形二、查询到有其他业务参与实体正在使用该目标多播承载发送终端群组的业务数据
该情形中，当响应消息中不仅包括目标多播承载的标识，还包括一个第二指示信息，第二指示信息用于指示业务参与实体，不向所述终端群组中位于所述服务区域内的终端发送所述终端群组的业务数据。则该业务参与实体确定有其他业务参与实体正在使用该目标多播承载向终端群组发送业务数据。
因此，该业务参与实体只需向终端群组中注册在该业务参与实体的终端发送指示消息，指示终端在该目标多播承载上接收终端群组的业务数据，并且，该业务参与实体不需要向终端群组发送业务数据。
例如，在上述给出的示例中，当业务参与实体1使用目标多播承载发送业务数据时，则当业务参与实体2向目标业务实体发送请求消息后，目标业务实体向业务参与实体2发送的响应消息中包括目标多播承载的标识和第二指示信息，从而，业务参与实体2向终端4、终端5发送指示信息，指示终端4、终端5在目标多播承载上接收业务数据；同样地，业务参与实体3向终端6发送指示信息，指示终端6在目标多播承载上接收业务数据。
上述实现方式也可以理解为：当业务参与实体向目标业务实体发送请求消息时，目标业务实体向业务参与实体发送响应消息，该响应消息包括指示信息。
当指示信息为目标多播承载的标识时，对应于上述情形一的实现方式一；当指示信息为目标多播承载的标识和第一指示信息时，对应于上述情形一的实现方式二；当指示信息为目标多播承载的标识和第二指示信息时，对应于上述情形二。具体可参考前述描述。
需要说明的是，上述实现方式中，当响应消息中只包括目标多播承载的标识时，可以约定，当前没有其他业务参与实体正在使用目标多播承载发送业务数据。当然，当响应消息中只包括目标多播承载的标识时，也可以约定，当前已经有其他业务参与实体正在使用目标多播承载发送业务数据，其具体实现方式与上述实现方式类似，不再赘述。
在另外的实现方式中，如果上述步骤401～步骤402是由上述步骤4011～步骤4014替换，则相应地：
在上述情形一中，即目标业务实体查询到没有其他业务参与实体正在使用该目标多播承载，此时有以下几种实现方式：
在一种实现方式中，目标业务实体可以在步骤4014的第二响应消息中携带第一指示信息，第一指示信息用于指示业务参与实体，通过目标多播承载发送终端群组的业务数据。
在又一种实现方式中，在步骤4014的第二响应消息中什么也不携带，则可以按照预先约定，业务参与实体默认没有其他业务参与实体正在使用该目标多播承载，因此，该业务参与实体可以使用该目标多播承载。
或者是，在步骤4014的第二响应消息中携带终端群组的标识，该终端群组的标识的作用与上述第一指示信息的作用相同，即当第二响应消息中携带终端群组的标识时，则业务参与实体确认没有其他业务参与实体正在使用该目标多播承载，因此，该业务参与实体可以使用该目标多播承载。
在上述情形二中，即目标业务实体查询到有其他业务参与实体正在使用该目标多播承载发送终端群组的业务数据，此时有以下几种实现方式：
目标业务实体可以在步骤4014的第二响应消息中携带第二指示信息，第二指示信息用于指示所述业务参与实体，不向所述终端群组中位于所述服务区域内的终端发送所述终端群组的业务数据。该第二指示信息可以在第二响应消息的特定位置携带，如在第二响应消息的特定位置采用字符编码或数字编码的方式实现，具体地，第二指示信息可以用“01”表示，也可以用“NOT SEND”标识。第二指示信息可以与第一指示信息位于第二响应信息的同一位置有同一信元的不同值区别。具体地，当业务参与实体是建立所述目标多播承载的业务参与实体时，第二指示信息可以用于指示该业务 参与实体不使用目标多播承载发送终端群组的业务数据具体的，该业务参与实体不将接收到的业务数据(媒体面数据和控制信令)向该目标多播承载的用户面地址和端口号上发送，或者，用于指示该业务参与实体不发送终端群组的业务数据。当该业务参与实体不是建立目标多播承载的业务参与实体时，第二指示信息可以用于指示该业务参与实体不向建立该目标多播承载的业务参与实体转发该终端群组的业务数据。
该业务参与实体确定有其他业务参与实体，正在使用该目标多播承载，向终端群组发送业务数据，因此，该业务参与实体只需向终端群组中位于服务区域且注册在该业务参与实体的终端发送指示消息，指示该终端在目标多播承载上接收终端群组的业务数据，并且，该业务参与实体不需要向终端群组发送业务数据。
通过上述方法，当有一个业务参与实体正在使用目标多播承载在服务区域发送业务数据时，则其他业务参与实体只需要通知终端群组中位于服务区域且注册在该业务参与实体的终端，在目标多播承载上接收业务数据即可。从而，使得终端群组关联的业务参与实体中，只有一个业务参与实体使用目标多播承载向终端群组发送业务数据，避免有多个业务参与实体同时向终端群组发送业务数据，可解决背景技术中不同业务参与实体重复发送相同业务数据的问题，有利于节约资源。
上述主要从各个实体之间交互的角度对本申请提供的方案进行了介绍。可以理解的是，上述实现各实体为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本发明能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本发明的范围。
下面结合附图，给出几个具体的实施例，详细说明本申请的通信方法。
如图5所述，为本申请提供的又一种通信方法示意图。图5所示的实施例中的业务参与实体，可以是上述实施例中的第三业务参与实体，广播承载报告消息可以是上述实施例中的响应消息。该方法包括以下步骤：
步骤501、业务参与实体向多播承载管理实体发送广播承载报告消息。
业务参与实体(该业务参与实体可以是终端群组注册的业务参与实体中的任一业务参与实体，例如称之为第三业务参与实体)在预建立多播承载，或者动态新建多播承载，或更新多播承载后，向多播承载管理实体发送广播承载报告消息，该广播承载报告消息包括临时移动群组标识(Temporary Mobile Group Identity，TMGI)，服务区域标识(service area identifier，SAI)，可选地，还包括承载过期时间(exporation time)，终端群组的标识(Group Identification，Group ID)。可选地，还包括该业务参与实体的地址信息，这个地址可以是IPv4地址，可以是IPv6地址，可以是FQDN,还可以是URL。
其中，TMGI用于标识一个多播承载，即，TMGI可以理解为一个多播承载的标识，SAI用于标识一个服务区域，Group ID用于表示正在使用该多播承载的终端群组，当然，若TMGI标识的多播承载上，当前没有正在传输的群组通信，则广播承载报告消息中可以不带Group ID。
需要说明的是，该广播承载报告消息也可以称之为上报消息等。
步骤502、多播承载管理实体根据接收到的广播承载报告消息，更新本地保存的多播承载。
如果多播承载管理实体没有存储该多播承载信息，则保存该广播承载报告消息中的信息；如果多播承载管理实体已经存储该多播承载信息，则根据接收到的广播承载报告消息中的信息，更新存储的多播承载信息。
步骤503、多播承载管理实体向业务参与实体发送广播承载报告确认消息。
该广播承载报告确认消息，用于指示已经成功接收到广播承载报告消息。
通过上述步骤501～步骤503，当某个业务参与实体建立了多播承载后，可将多播承载信息发送至多播承载管理实体进行保存，以便需要使用时，可直接从多播承载管理实体获取该多播承载。
如图6所述，为本申请提供的又一种通信方法示意图。其中，业务参与实体1即为上述实施例中的第一业务参与实体，业务参与实体2即为上述实施例中的第二业务参与实体。该方法包括以下步骤：
步骤601、业务控制实体决定在服务区域，对终端群组使用多播承载传输群组通信数据。
业务控制实体可决策，在某一服务区域，是否对终端群组使用多播承载传输群组通信数据，如发送业务数据。
步骤602、业务控制实体向业务参与实体1发送广播承载建立请求消息，业务参与实体1接收来自业务控制实体的广播承载建立请求消息。
如果业务控制实体没有从本地或多播承载管理实体查询到服务区域的多播承载信息，则选择一个业务参与实体，如业务参与实体1，建立承载。
因此，业务控制实体向业务参与实体1发送广播承载建立请求消息，该广播承载建立请求消息包括服务区域标识SAI、终端群组的标识Group ID，可选地，还包括会话描述协议信息(Session Description Protocol，SDP)，服务质量(Quality of Service，QoS)，其中，SDP为服务描述信息，例如包括编解码信息等。
可选地，如果业务控制实体有获取的与SAI对应的TMGI，则也可以将TMGI携带于广播承载建立请求消息，发送给业务参与实体1，让业务参与实体1用该TMGI激活承载。
步骤603，业务参与实体1创建多播承载。
步骤604a、业务参与实体1将多播承载信息发送给多播承载管理实体。
步骤604b、业务参与实体1将多播承载信息发送给业务控制实体。
步骤605a、业务控制实体向业务参与实体1发送广播承载使用消息，业务参与实体1接收来自业务控制实体的广播承载使用消息。
其中，广播承载使用消息包括TMGI、SAI、Group ID，媒体发送指示(Media sending indicator)，其中，media sending indicator指示业务参与实体1向Group ID指示的终端，使用TMGI对应的多播承载发送群组通信数据，如业务数据。
步骤605b、业务控制实体向业务参与实体2发送广播承载使用消息，业务参与实体2接收来自业务控制实体的广播承载使用消息。
广播承载使用消息包括TMGI、SAI、Group ID、Media sending indicator，可选地，还包括定时器(timer)，其中，media sending indicator指示业务参与实体2在SAI指 示的服务区域，不向终端群组发送通信数据。如果包括timer，则该timer用于指示多久后业务参与实体2在SAI指示的服务区域，停止向终端群组发送通信数据。
步骤606a、业务参与实体1在SAI对应的服务区域，使用TMGI对应的多播承载，向终端群组发送通信数据。
步骤606b、业务参与实体2在SAI对应的服务区域，停止向终端群组发送通信数据。
进一步地，业务参与实体2还需要通知终端群组中位于服务区域且注册在业务参与实体2的终端，接收TMGI对应的多播承载上的通信数据。
步骤607a，业务参与实体1向业务控制实体发送广播承载使用确认消息。
步骤607b、业务参与实体2向业务控制实体发送广播承载使用确认消息。
上述方法，业务控制实体指示业务参与实体1通过多播承载发送终端群组的业务数据，并指示业务参与实体2不向终端群组中位于服务区域且注册在业务参与实体2的终端发送终端群组的业务数据，避免了终端群组从多个业务参与实体接收相同的业务数据，节约了资源。
如图7所述，为本申请提供的又一种通信方法示意图。该本实施例描述了业务参与实体决策多播承载的使用，然后向目标业务实体(业务控制实体或多播承载管理实体)询问某一服务区域，是否已经有传输同一群组通信的多播承载，如果已经有，则该业务参与实体通知自己的终端在已有的多播承载上接收业务数据，该业务参与实体不再向该终端群组发送业务数据。该方法包括以下步骤：
步骤701、业务参与实体向目标业务实体发送广播承载查询请求消息，目标业务实体接收来自业务参与实体的广播承载查询请求消息。
其中，广播承载查询请求消息包括SAI，可选地，还包括QoS，SDP。
可选地，广播承载查询请求消息还包括Group ID。
步骤702、目标业务实体根据广播承载查询请求消息，查询满足条件的目标多播承载。
步骤703、目标业务实体向业务参与实体发送广播承载响应消息，业务参与实体接收来自目标业务实体的广播承载响应消息。
其中，广播承载响应消息包括TMGI、无需通信指示(No echo indicator)，其中，TMGI用于指示正在使用的目标多播承载的标识，No echo indicator用于指示业务参与实体无需在TMGI关联的SAI对应的服务区域，向群组通信的终端发送通信数据，可选地，还包括TMGI对应的SAI。
其中，若上述步骤701的请求消息包括Group ID，则该TMGI用于指示该Group ID对应的终端群组正在使用的目标多播承载的标识。
步骤704a、业务参与实体向终端群组中位于服务区域且注册在该业务参与实体的终端，发送广播业务通知消息，终端接收来自业务参与实体的广播业务通知消息。
其中，广播业务通知消息中包括TMGI、SAI，用于通知终端监听TMGI对应的多播承载的接收质量。
步骤704b、终端向业务参与实体发送广播承载质量上报消息，业务参与实体接收来自终端的广播承载质量上报消息。
其中，广播承载质量上报消息包括TMGI和监听到的质量信息。
步骤705、业务参与实体向终端群组中位于服务区域且注册在自身的终端发送多播承载业务与群组通信绑定消息，终端接收来自业务参与实体的多播承载业务与群组通信绑定消息。
其中，多播承载业务与群组通信绑定消息包括TMGI、group ID。
终端在接收到该消息后，将TMGI与group ID绑定，即建立对应关系。
需要说明的是，该步骤705还可以在步骤704a之前执行，或者是在步骤704a和步骤704b之间执行。
步骤706、业务参与实体向目标业务实体发送广播承载使用请求消息，目标业务实体接收来自业务参与实体的广播承载使用请求消息。
其中，广播承载使用请求消息包括TMGI，预留资源量如带宽，Group ID，表示业务参与实体即将在TMGI对应的多播承载上，向Group ID对应的终端群组发送通信数据，因而需要向目标业务实体申请资源量，如带宽。
步骤707、目标业务实体向业务参与实体发送广播承载使用响应消息，业务参与实体接收来自目标业务实体的广播承载使用响应消息。
其中，广播承载使用响应消息包括TMGI、SAI、Group ID、No echo indicator，其中，No echo indicator用于指示业务参与实体在SAI对应的服务区域，无需使用TMGI对应的多播承载，向Group ID对应的终端群组发送通信数据，如业务数据。
步骤708、目标业务实体更新TMGI对应的多播承载信息。
步骤709、业务参与实体在收到No echo indicator后，不再使用TMGI对应的多播承载，向Group ID对应的终端群组发送通信数据。
通过该实施例，可以实现在同一服务区域，只有一个业务参与实体使用多播承载向终端群组发送通信数据，避免终端群组的终端从不同业务参与实体接收相同的业务数据，可节约资源。
如图8所述，为本申请提供的又一种通信方法示意图。其中，业务参与实体1和业务参与实体2都在服务区域内，且当前业务参与实体1在服务区域内，通过多播承载向终端群组发送终端群组的业务数据，终端群组中注册在业务参与实体2的终端，从该多播承载上接收终端群组的业务数据，业务参与实体2不向终端群组中位于服务区域且注册在自身的终端发送业务数据。
如果业务参与实体1需要停止向终端群组发送业务数据，则执行以下步骤：
步骤801、业务参与实体1决定在服务区域，不再使用多播承载发送业务数据。
例如，业务参与实体1因为故障，或超负荷，或退出通信等原因，停止使用多播承载向终端群组发送业务数据。
步骤802、业务参与实体1向业务控制实体发送通知消息，业务控制实体接收来自业务参与实体1的通知消息。
其中，通知消息也可以称为停止发送数据消息(stop sending data message)，该消息中包括TMGI、SAI、Group ID，表示业务参与实体1在SAI对应的服务区域，不再使用TMGI对应的多播承载向Group ID对应的终端群组发送业务数据。
步骤803、业务控制实体向业务参与实体2发送广播承载状态通知消息，业务参与实体2接收来自业务控制实体的广播承载状态通知消息。
该广播承载状态通知消息中包括SAI，用于指示业务参与实体2在SAI对应的服 务区域内，使用单播或广播，向终端群组中注册在业务参与实体2的终端发送业务数据。
步骤804、业务参与实体2收到广播承载状态通知消息后，在SAI对应的服务区域内，使用单播或多播，向终端群组中位于服务区域且注册在业务参与实体2的终端发送业务数据。
通过该实施例，当向终端群组发送业务数据的业务参与实体停止发送业务数据时，可由终端注册的业务参与实体向终端发送业务数据，以便正常通信。
基于相同的发明构思，如图9所示，为本申请提供的一种装置示意图，该装置900可以是业务控制实体，也可以是片上系统或芯片，可执行上述任一实施例中由业务控制实体执行的方法。
该装置900包括至少一个处理器91，收发器92，可选地，还包括存储器93。所述处理器91、收发器92、存储器93通过通信总线连接。
处理器91可以是一个通用中央处理器(CPU)，微处理器，ASIC，或一个或多个用于控制本发明方案程序执行的集成电路。
通信总线可包括一通路，在上述单元之间传送信息。
所述收发器92，用于与其他设备或通信网络通信，该收发器可以是一种通信接口，例如，有线接口或无线接口，或wifi接口，或该收发器包括射频电路。
存储器93可以是ROM或可存储静态信息和指令的其他类型的静态存储设备，RAM或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(Electrically erasable programmabler-only memory，EEPROM)、只读光盘(compact disc read-only memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器93可以是独立存在，通过通信总线与处理器91相连接。存储器93也可以和处理器集成在一起。其中，所述存储器93用于存储执行本发明方案的应用程序代码，并由处理器91来控制执行。所述处理器91用于执行所述存储器93中存储的应用程序代码。
在具体实现中，作为一种实施例，处理器91可以包括一个或多个CPU，例如图9中的CPU0和CPU1。
在具体实现中，作为一种实施例，装置900可以包括多个处理器，例如图9中的处理器91和处理器98。这些处理器中的每一个可以是一个单核(single-CPU)处理器，也可以是一个多核(multi-CPU)处理器，这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
应理解，该装置可以用于实现本发明实施例的通信方法中由业务控制实体执行的步骤，相关特征可以参照上文，此处不再赘述。
本申请可以根据上述方法示例对装置进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实 现时可以有另外的划分方式。比如，在采用对应各个功能划分各个功能模块的情况下，图10示出了一种装置示意图，该装置可以是上述实施例中所涉及的业务控制实体或片上系统或芯片，该装置包括处理单元1001和通信单元1002。
在一种应用中：
处理单元1001，用于获取多播承载的标识，多播承载用于在服务区域内传输终端群组的业务数据；
通信单元1002，用于向终端群组关联的第一业务参与实体发送第一指示消息，第一指示消息用于指示第一业务参与实体通过多播承载发送终端群组的业务数据；
通信单元1002，还用于向终端群组关联的第二业务参与实体发送第二指示消息，第二指示消息用于指示第二业务参与实体，不向终端群组中位于服务区域内的终端发送终端群组的业务数据，第一业务参与实体与第二业务参与实体不同；
其中，终端群组中存在至少一个终端注册在第一业务参与实体上，终端群组中存在至少一个终端注册在第二业务参与实体上。
在一种可能的实现方式中，处理单元1001，具体用于控制通信单元1002：
向多播承载管理实体发送查询消息，查询消息包括服务区域的标识，查询消息用于请求查询服务区域对应的多播承载；
接收来自多播承载管理实体的响应消息，响应消息包括多播承载的标识。
在一种可能的实现方式中，通信单元1002，还用于：
向终端群组关联的第三业务参与实体发送请求消息，请求消息包括服务区域的标识，请求消息用于请求第三业务参与实体在服务区域内建立多播承载。
在一种可能的实现方式中，通信单元1002，还用于：
接收来自第三业务参与实体的响应消息，响应消息包括多播承载的标识。
在一种可能的实现方式中，请求消息包括终端群组的标识。
在一种可能的实现方式中，通信单元1002，还用于：
接收来自第一业务参与实体的通知消息，通知消息用于通知第一业务参与实体停止通过多播承载发送终端群组的业务数据；
向第二业务参与实体发送第三指示消息，第三指示消息用于指示第二业务参与实体，向终端群组中位于服务区域内且注册在第二业务参与实体上的终端，发送终端群组的业务数据。
在另一种应用中：
处理单元1001，用于控制通信单元1002：
向目标业务实体发送请求消息，请求消息包括服务区域的标识和群组标识，请求消息用于请求查询目标多播承载，目标多播承载用于在服务区域向发送群组标识对应的终端群组的业务数据；
接收来自目标业务实体的响应消息，响应消息包括目标多播承载的标识；
向终端发送指示消息，指示消息用于指示终端通过目标多播承载接收终端群组的业务数据；
其中，终端为位于服务区域内，且注册在业务参与实体上的终端。
在一种可能的实现方式中，处理单元1001，还用于控制通信单元1002：通过目标多播承载发送终端群组的业务数据；或，
响应消息还包括第一指示信息，第一指示信息用于指示业务参与实体，通过目标多播承载发送终端群组的业务数据；处理单元1001，还用于控制通信单元1002：通过目标多播承载发送终端群组的业务数据。
在一种可能的实现方式中，响应消息还包括第二指示信息，第二指示信息用于指示不向终端群组中位于服务区域内的终端发送终端群组的业务数据。
在本实施例中，该装置以对应各个功能划分各个功能模块的形式来呈现，或者，该业务控制实体以采用集成的方式划分各个功能模块的形式来呈现。这里的“模块”可以ASIC，电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。
应理解，该装置可以用于实现本发明上述实施例的通信方法中由业务控制实体执行的步骤，相关特征可以参照上文，此处不再赘述。
基于相同的发明构思，如图11所示，为本申请提供的一种装置示意图，该装置1100例如可以是业务参与实体，也可以是片上系统或芯片，可执行上述任一实施例中由业务参与实体执行的方法。
装置1100包括至少一个处理器111，收发器112，可选地，还包括存储器113。处理器111、收发器112、存储器113通过通信总线连接。
处理器111可以是一个通用中央处理器(CPU)，微处理器，特定ASIC，或一个或多个用于控制本发明方案程序执行的集成电路。
通信总线可包括一通路，在上述单元之间传送信息。
收发器112，用于与其他设备或通信网络通信，该收发器可以是一种通信接口，例如，有线接口或无线接口，或wifi接口，或该收发器包括射频电路。
存储器113可以是ROM或可存储静态信息和指令的其他类型的静态存储设备，RAM或者可存储信息和指令的其他类型的动态存储设备，也可以是EEPROM、CD-ROM或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器113可以是独立存在，通过通信总线与处理器111相连接。存储器113也可以和处理器集成在一起。其中，存储器113用于存储执行本发明方案的应用程序代码，并由处理器111来控制执行。处理器111用于执行存储器113中存储的应用程序代码。
在具体实现中，作为一种实施例，处理器111可以包括一个或多个CPU，例如图11中的CPU0和CPU1。
在具体实现中，作为一种实施例，装置1100可以包括多个处理器，例如图11中的处理器111和处理器118。这些处理器中的每一个可以是一个单核(single-CPU)处理器，也可以是一个多核(multi-CPU)处理器，这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
应理解，该装置可以用于实现本发明上述实施例的通信方法中由业务参与实体执行的步骤，相关特征可以参照上文，此处不再赘述。
本申请可以根据上述方法示例对装置进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。比如，在采用对应各个功能划分各个功能模块的情况下，图12示出了一种装置示意图，该装置可以是上述实施例中所涉及的业务参与实体，该装置包括处理单元1201和通信单元1202。
在一种应用中：
处理单元1201，用于控制通信单元1202：
接收来自业务控制实体的第二指示消息，第二指示消息包括多播承载的标识、服务区域的标识及群组标识，第二指示消息用于指示业务参与实体,不向群组标识对应的终端群组中位于服务区域内的终端发送终端群组的业务数据；
向终端发送第四指示消息，第四指示消息包括多播承载的标识，第四指示消息用于指示终端，通过多播承载接收终端群组的业务数据，终端为终端群组中位于服务区域且注册在业务参与实体上的终端。
在一种可能的实现方式中，处理单元1201，还用于控制通信单元1202：
接收来自业务控制实体的第三指示消息，第三指示消息用于指示业务参与实体，向终端发送终端群组的业务数据。
在另一种应用中：
处理单元1201，用于控制通信单元1202：
接收来自业务参与实体的请求消息，请求消息包括服务区域的标识和群组标识，请求消息用于请求查询目标多播承载，目标多播承载用于在服务区域内，发送群组标识对应的终端群组的业务数据；
向业务参与实体发送响应消息，响应消息包括目标多播承载的标识。
在一种可能的实现方式中，响应消息还包括第一指示信息，第一指示信息用于指示业务参与实体，通过目标多播承载发送终端群组的业务数据。
在一种可能的实现方式中，响应消息还包括第二指示信息，第二指示信息用于指示业务参与实体不向终端群组中位于服务区域内的终端发送终端群组的业务数据。
在本实施例中，该装置以对应各个功能划分各个功能模块的形式来呈现，或者，该业务控制实体以采用集成的方式划分各个功能模块的形式来呈现。这里的“模块”可以指ASIC，电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。
应理解，该装置可以用于实现本发明上述实施例的通信方法中由业务参与实体执行的步骤，相关特征可以参照上文，此处不再赘述。
如图13所示，本申请还提供一种通信方法，该通信方法可以由目标业务实体、目标业务参与实体所管理的业务参与实体(图中以第一业务参与实体和第三业务参与实体为例)执行。其中，第一业务参与实体和第三业务参与实体，为目标业务参与实体所管理的业务参与实体中的任两个业务参与实体。
其中，目标业务实体可以是业务控制实体，或者是多播承载管理实体。
该实施例中后续还提到第二业务参与实体和第四业务参与实体，其中，第二业务参与实体可以指的是终端群组的终端注册的业务参与实体中除上述第一业务参与实体之外的任一业务参与实体，第四业务参与实体可以指的是终端群组的终端注册的业务参与实体中的任一业务参与实体，第四业务参与实体可以是上述第一业务参与实体或上述第三业务参与实体，不予限制。
需要说明的是，这里的第一业务参与实体、第二业务参与实体、第三业务参与实体、第四业务参与实体中的编号，仅是为了做相互区别，在实际使用中，也可以有其他的名称。
下面介绍图13所示的通信方法的实现过程。该方法包括以下步骤：
步骤1301，第一业务参与实体向目标业务实体发送第一请求消息，目标业务实体接收来自第一业务参与实体的第一请求消息。
其中，该目标业务实体可以是业务控制实体，也可以是多播承载管理实体，不予限制。
其中，该第一请求消息可以包括群组标识和目标多播承载的标识，第一请求消息可以用于请求使用目标多播承载发送群组标识对应的终端群组的业务数据。
需要说明的是，第一业务参与实体可以为业务控制实体管理的任一业务参与实体。对于群组标识对应的终端群组，有一个对应的业务控制实体和一个或多个对应的业务参与实体，这里的“管理”可以理解为，针对该终端群组，该终端群组的业务控制实体可以联系到该终端群组的一个或多个对应的业务参与实体，并在呼叫控制和媒体面控制中承担集中控制功能。
在一个示例中，当第一业务参与实体确定使用目标多播承载发送终端群组的业务数据时，向目标业务实体发送第一请求消息，该第一请求消息中包括群组标识和目标多播承载的标识。其中，第一业务参与实体可以通过该终端群组中的终端状态信息来确定使用目标多播承载发送终端群组的业务数据。例如，当该终端群组中由第一业务参与实体提供服务的，且位于该目标多播承载对应的服务区域的终端的数量满足预设条件时，第一业务参与实体确定使用目标多播承载发送终端群组的业务数据。
在一个示例中，在上述步骤1301之前，目标业务实体上已经存储有该目标多播承载的信息，如该目标多播承载的标识等。该目标业务实体上存储的目标多播承载的信息可通过以下方式获取：
在一种实现方式中，该目标多播承载是由上述第一业务参与实体建立，并将建立的该目标多播承载的信息(例如，目标多播承载的标识)上报给该目标业务实体。
在该实现方式中，由于该目标多播承载是由该第一业务参与实体建立的，因此第一业务参与实体本地也存储有该目标多播承载的信息，进而，在上述步骤1301中，第一业务参与实体向目标业务参与发送的第一请求消息中携带的目标多播承载的标识，可以是由该第一业务参与实体从本地获取。
在另一种实现方式中，该目标多播承载是由其他业务参与实体(例如第二业务参与实体)建立，并将建立的该目标多播承载的信息(例如，目标多播承载的标识)上报给该目标业务实体，则在上述步骤1301中，第一业务参与实体向目标业务参与发送的第一请求消息中携带的目标多播承载的标识，可以是由该第一业务参与实体通过以下方式获取得到：
情形一，目标业务实体为业务控制实体
业务控制实体在接收到第二业务参与实体上报的目标多播承载的信息之后，会推送给其他业务参与实体，例如，推送给第一业务参与实体，然后，第一业务参与实体将该目标多播承载的信息存储在本地。
进而，在上述步骤1301中，第一业务参与实体在向目标业务实体发送第一请求消息时，可以从本地获取到目标多播承载的标识，并携带于第一请求消息中发送至目标业务实体。
情形二，目标业务实体为多播承载管理实体
多播承载管理实体在接收到第二业务参与实体上报的多播承载的信息之后，不会推送给其他业务参与实体，此时，第一业务参与实体可以通过下面的方式获取该目标多播承载的标识：
第一业务参与实体向多播承载管理实体发送查询请求消息，查询请求消息包括服务区域的标识，该查询请求消息用于请求获取向服务区域标识对应的服务区域发送业务数据的多播承载的信息，进一步地，查询请求消息中还可以包括群组标识，用于请求获取向服务区域标识对应的服务区域发送群组标识对应的终端群组的业务数据的多播承载的信息；然后，多播承载管理实体向第一业务参与实体发送查询响应消息，查询响应消息包括目标多播承载的标识。然后，第一业务参与实体将该目标多播承载的信息(例如，目标多播承载的标识)存储在本地。
进而，在上述步骤1301中，第一业务参与实体在向目标业务实体发送第一请求消息时，可以从本地获取到目标多播承载的标识，并携带于第一请求消息中发送至目标业务实体。
步骤1302，目标业务实体向第一业务参与实体发送第一响应消息，第一业务参与实体接收来自目标业务实体的第一响应消息。
其中，该第一响应消息可以包括终端群组对目标多播承载的使用状态。
可选地，终端群组对目标多播承载的使用状态为：在使用中或未使用。
或者为：目标多播承载上有终端群组的业务数据在发送，或者，目标多播承载上没有终端群组的业务数据在发送。
或者为：没有业务参与实体使用目标多播承载发送终端群组的业务数据，或者，有业务参与实体使用目标多播承载发送终端群组的业务数据，或者，第二业务参与实体使用目标多播承载发送终端群组的业务数据。
若终端群组对目标多播承载的使用状态为在使用，表明当前有其他业务参与实体使用该目标多播承载向该终端群组发送业务数据，此时，该第一业务参与实体不向终端群组发送业务数据，以避免重复发送相同的业务数据。第一业务参与实体只需要通知终端到该目标多播承载上接收业务数据即可，后续会详细说明。
若终端群组对目标多播承载的使用状态为未使用，则可以表明当前没有其他业务参与实体使用该目标多播承载向该终端群组发送业务数据，那么第一业务参与实体可以使用该目标多播承载向终端群组发送业务数据。
在上述实施例中，目标业务实体在接收到第一业务参与实体的第一请求消息后，向该第一业务参与实体发送终端群组对目标多播承载的使用状态，使得第一业务参与实体可以根据接收到的使用状态判断是否可以使用该目标多播承载向终端群组发送业 务数据，例如，当第一业务参与实体确定终端群组对目标多播承载的使用状态为未使用时，则第一业务参与实体才使用该目标多播承载发送业务数据，有助于避免多个业务参与实体同时使用目标多播承载向终端群组发送数据，进而有助于避免终端群组的终端重复接收相同的业务数据，可节约资源。
可选地，在上述实施例的第一种实施场景下，上述方法还包括：
步骤1303、第一业务参与实体根据使用状态，确定使用目标多播承载发送该终端群组的业务数据，并向目标业务实体发送指示消息。
其中，该指示消息可以用于指示第一业务参与实体使用目标多播承载发送该终端群组的业务数据。
相应地，还可以包括：
步骤1304、目标业务实体接收来自第一业务参与实体的指示消息，并根据指示消息，更新该终端群组对该目标多播承载的使用状态。
例如，步骤1304可以采用下述任一方式更新该终端群组对该目标多播承载的使用状态：
目标业务实体将终端群组对该目标多播承载的使用状态更新为：第一业务参与实体使用目标多播承载发送终端群组的业务数据。
或者，目标业务实体将终端群组对该目标多播承载的使用状态更新为：有业务参与实体使用该目标多播承载发送终端群组的业务数据。
或者，目标业务实体将终端群组对该目标多播承载的使用状态更新为：在使用中。
进一步地，若该目标业务实体是业务控制实体，则目标业务实体还可以向除第一业务参与实体之外的其他业务参与实体发送通知消息，该通知消息可以用于将该目标多播承载更新后的使用状态通知给其他业务参与实体，从而使得其他业务参与实体也获知该目标多播承载的最新的使用状态，以便于其他业务实体可以及时获知目标多播承载的使用状态，进而可以及时使用该多播承载发送群组的业务数据，扩大多播承载的覆盖终端数目，提高传输效率。
其中，该最新的使用状态可以为：第一业务参与实体使用目标多播承载发送终端群组的业务数据，或者为，有业务参与实体使用该目标多播承载发送终端群组的业务数据，或者为，在使用中。
在实际应用中，第一业务参与实体根据接收到的第一响应消息中的使用状态，判断是否可以使用该目标多播承载发送终端群组的业务数据。当第一业务参与实体根据接收到的第一响应消息中的使用状态，确定使用该目标多播承载发送终端群组的业务数据时，第一业务参与实体使用该目标多播承载向终端群组发送业务数据。
作为一种实现方式，第一业务参与实体根据使用状态，确定使用目标多播承载发送终端群组的业务数据，可以包括以下方法：
例如，当第一业务参与实体存在待发送的终端群组的业务数据，且接收到的第一响应消息中的使用状态为没有业务参与实体使用该目标多播承载发送终端群组的业务数据时，第一业务参与实体确定使用目标多播承载发送终端群组的业务数据。
再比如，当第一业务参与实体存在待发送的终端群组的业务数据，且接收到的第一响应消息中的使用状态为未使用时，第一业务参与实体确定使用目标多播承载发送终端群组的业务数据。
再比如，当第一业务参与实体存在待发送的终端群组的业务数据，且接收到的第一响应消息中的使用状态为目标多播承载上没有终端群组的业务数据在发送时，第一业务参与实体确定使用目标多播承载发送待发送的终端群组的业务数据。
再比如，当接收到的第一响应消息中的使用状态为没有业务参与实体使用该目标多播承载发送终端群组的业务数据时，第一业务参与实体确定使用目标多播承载发送终端群组的业务数据。
再比如，当接收到的第一响应消息中的使用状态为未使用时，第一业务参与实体确定使用目标多播承载发送终端群组的业务数据。
再比如，当接收到的第一响应消息中的使用状态为目标多播承载上没有终端群组的业务数据在发送时，第一业务参与实体确定使用目标多播承载发送待发送的终端群组的业务数据。
作为一种实现方式，当第一业务参与实体确定有其他业务参与实体使用该目标多播承载发送终端群组的业务数据时，该第一业务参与实体仍然可以发送该终端群组的业务数据，此时，业务控制实体可以丢弃其中的一个业务参与实体发送的终端群组的业务数据，一般是丢弃后发的业务数据。
进一步可选地，该目标业务实体是业务控制实体，在步骤1304之后，上述方法还包括：
目标业务实体向第三业务参与实体发送通知消息，该通知消息包括目标多播承载的更新后的使用状态。
在一个示例中，业务控制实体将更新后的使用状态，通知给除第一业务参与实体外的其他业务参与实体。
其中，该第三业务参与实体可以为除第一业务参与实体外的其他业务参与实体，不予限制。
进一步地，上述方法还可以包括：
目标业务实体接收来自该第三业务参与实体的通知状态上报消息，该通知状态上报消息用于指示该第三业务参与实体通知终端在该目标多播承载上接收该终端群组的业务数据。
具体地，可以参见步骤1306中的相关描述，不再赘述。
进一步可选地，当第一业务参与实体确定使用目标多播承载发送终端群组的业务数据时，上述方法还包括：
步骤1305、第一业务参与实体向终端发送通知消息。
相应地，还可以包括：终端接收来自第一业务参与实体的通知消息。
其中，该通知消息可以用于通知终端使用目标多播承载接收终端群组的业务数据。
其中，该通知消息中可以包含目标多播承载的标识，可选的，还包括群组标识。
需要指出的是，本实施例中提及的名词或术语，均可以参见前述各实施例中的相关描述，不予限制。
在一种实现方式中，第一业务参与实体通过多播传输方式向服务区域发送该通知消息，此时，接收到该通知消息的终端可以包括终端群组中的部分或全部终端，也可以包括其他群组的终端，并且这些终端可以是通过第一业务参与实体注册的，也可以是通过其他业务参与实体注册的。该实现方式可以理解为，第一业务参与实体在服务 区域，通过多播传输方式，向该服务区域的部分或所有终端发送通知消息。
在又一种实现方式中，第一业务参与实体通过单播方式，向终端群组中通过第一业务参与实体注册的终端发该通知消息。
在又一种实现方式中，第一业务参与实体通过单播方式，向终端群组中通过第一业务参与实体注册的,且当前位于服务区域内的终端发该通知消息。
该通知消息用于指示终端使用目标多播承载接收业务数据。如果接收到该通知消息的终端不在服务区域，则不能收到业务数据。如果接收到该通知消息的终端不是终端群组内的终端，则可以采用其他处理方式进行处理，如在尝试解密消息内容失败后，丢弃该数据包，或者判断自己不是该终端群组内的终端时，丢弃该数据包。
进一步可选地，上述方法还包括：
步骤1306、第一业务参与实体向目标业务实体发送通知状态上报消息。
相应地，还包括：目标业务实体接收来自第一业务参与实体的通知状态上报消息。
其中，该通知状态上报消息可以用于指示：第一业务参与实体通知终端在目标多播承载上接收终端群组的业务数据。该通知状态上报消息还可以称为多播状态上报消息，或多播使用状态上报消息，此处不再赘述。可以理解为，当第一业务参与实体确认成功通知到终端在目标多播承载上接收终端群组的业务数据(例如，收到终端的确认消息)后，执行步骤1306；或者是，只要是第一业务参与实体向终端发送消息，以通知终端在目标多播承载上接收终端群组的业务数据，不管终端是否成功接收到通知，第一业务参与实体都执行步骤1306。
通过上述第一种实施场景中的方法，当第一业务参与实体确定使用目标多播承载发送终端群组的业务数据时，第一业务参与实体向目标业务实体发送第一请求消息，并根据接收到的第一响应消息中的终端群组对目标多播承载的使用状态，判断是否可以使用该目标多播承载向终端群组发送业务数据。当终端群组对目标多播承载的使用状态为未使用时，第一业务参与实体可以使用该目标多播承载发送业务数据。进一步地，目标业务实体还可以更新该目标多播承载的使用状态。进一步地，若该目标业务实体是业务控制实体，则业务控制实体还将更新后的使用状态通知给除第一业务参与实体外的其他业务参与实体。
可选地，在上述第一种实施场景的基础上，上述方法还包括：
步骤1307、第一业务参与实体使用该目标多播承载向终端发送终端群组的业务数据。
作为一种实现方式，当该目标多播承载是由第一业务参与实体建立时，第一业务参与实体使用该目标多播承载发送终端群组的业务数据，即第一业务参与实体直接使用该目标多播承载发送该终端群组的业务数据。
作为另一种实现方式，当该目标多播承载不是由第一业务参与实体建立时，第一业务参与实体向建立该目标多播承载的业务参与实体发送指示信息和终端群组的业务数据，该指示信息用于指示建立该目标多播承载的业务参与实体使用该目标多播承载发送该终端群组的业务数据。即，第一业务参与实体将该终端群组的业务数据发送给建立该目标多播承载的业务参与实体，并由建立该目标多播承载的业务参与实体使用该目标多播承载发送该终端群组的业务数据。
例如，该目标多播承载是由第二业务参与实体建立的，则第一业务参与实体可以 通过业务控制实体推送的方式，或者是第一业务参与实体采用主动请求的方式，获取到第二业务参与实体的信息(例如包括，第二业务参与实体标识信息，和/或第二业务参与实体的地址信息)。第一业务参与实体向该第二业务参与实体发送终端群组的业务数据和指示信息，指示第二业务参与实体使用该目标多播承载发送该终端群组的业务数据。
在上述两种实现方式中，是由建立该目标多播承载的业务参与实体使用该目标多播承载向终端发送业务数据。
作为再一种实现方式，不管该目标多播承载是由哪个业务参与实体建立的，在该步骤中，均由该第一业务参与实体使用该目标多播承载向终端发送业务数据。可以理解为，由获取到该目标多播承载的使用权的业务参与实体使用该目标多播承载向终端发送业务数据。
可选地，在上述第一种实施场景的基础上，当第一业务参与实体使用该目标多播承载发送该终端群组的业务数据时，若存在其他业务参与实体(该其他业务参与实体可以为终端群组的终端注册的业务参与实体中，参与该终端群组通信的，除该第一业务参与实体之外的业务参与实体)，如第三业务参与实体，也确定使用该目标多播承载发送该终端群组的业务数据，则上述方法还可以包括步骤1308-步骤1309。
步骤1308，第三业务参与实体向目标业务实体发送第二请求消息。
相应地，还可以包括：目标业务实体接收来自第三业务参与实体的第二请求消息。
其中，该第二请求消息可以包括群组标识和上述目标多播承载的标识，所述第二请求消息用于请求使用该目标多播承载发送终端群组的业务数据。
步骤1309，目标业务实体向第三业务参与实体发送第二响应消息。
相应地，还可以包括：第三业务参与实体接收来自目标业务实体的第二响应消息。
其中，该第二响应消息可以包括目标多播承载的更新后的使用状态。
可选地，该更新后的使用状态为：第一业务参与实体使用目标多播承载发送终端群组的业务数据，或者为，有业务参与实体使用该目标多播承载发送终端群组的业务数据，或者为，在使用中。
因此，若第三业务参与实体获知该目标多播承载当前已经在使用，即已经有其他业务参与实体在使用该目标多播承载向终端群组的终端发送业务数据，为避免重复发送相同的业务数据，则该第三业务参与实体决定不发送终端群组的业务数据。因而有助于避免多个业务参与实体同时使用目标多播承载向终端群组发送数据，进而有助于避免终端群组的终端重复接收到相同的业务数据，可节约资源。
需要说明的是，若第三业务参与实体之前已经接收到了来自业务控制实体发送的通知消息，且已经获知目标多播承载当前已经在使用中，则可以不执行上述步骤1308-步骤1309。
进一步地，上述方法还可以包括：
步骤1310，第三业务参与实体向终端发送通知消息。
相应地，还可以包括：终端接收来自第三业务参与实体的通知消息。
其中，该通知消息可以用于通知终端通过目标多播承载接收终端群组的业务数据。
可选地，该通知消息中包含目标多播承载的标识，可选的，还包括群组标识。
在一种实现方式中，第三业务参与实体通过多播传输方式向服务区域发送该通知 消息，此时，接收到该通知消息的终端可以包括终端群组中的部分或全部终端，也可以包括其他群组的终端，并且这些终端可以是通过第三业务参与实体注册的，也可以是通过其他业务参与实体注册的。该实现方式可以理解为，第三业务参与实体在服务区域，通过多播传输方式，向该服务区域的部分或所有终端发送通知消息。
在又一种实现方式中，第三业务参与实体通过单播方式，向终端群组中通过第三业务参与实体注册的终端发该通知消息。
在又一种实现方式中，第三业务参与实体通过单播方式，向终端群组中通过第三业务参与实体注册的,且当前位于服务区域内的终端发该通知消息。
其中，该通知消息可以用于指示终端使用目标多播承载接收业务数据。如果接收到该通知消息的终端不在服务区域，则不能收到业务数据。如果接收到该通知消息的终端不是终端群组内的终端，则可以采用其他处理方式进行处理，如在尝试解密消息内容失败后，丢弃该数据包，或者判断自己不是该终端群组内的终端时，丢弃该数据包。
进一步地，上述方法还可以包括：
步骤1311，第三业务参与实体向目标业务实体发送通知状态上报消息。
相应地，还可以包括：目标业务实体接收来自第三业务参与实体的通知状态上报消息。
其中，该通知状态上报消息可以用于指示：第三业务参与实体通知终端在目标多播承载上接收终端群组的业务数据。可以理解为，当第三业务参与实体确认成功通知到终端在目标多播承载上接收终端群组的业务数据(例如，收到终端的确认消息)后，执行步骤1311；或者是，只要是第三业务参与实体向终端发送消息，以通知终端在目标多播承载上接收终端群组的业务数据，不管终端是否成功接收到通知，第三业务参与实体都执行步骤1311。
通过上述步骤1308-步骤1310，第三业务参与实体确定使用目标多播承载发送终端群组的业务数据，当第三业务参与实体获知到目标多播承载的使用状态为在使用中时，则第三业务参与实体不向终端发送业务数据，而是通知终端到该目标承载上接收数据即可。因而有助于避免多个业务参与实体同时使用目标多播承载向终端群组发送数据，进而有助于避免终端群组的终端重复接收到相同的业务数据，可节约资源。
在上述实施例的第一种实施场景的基础上，在一种实现方式中，当上述实施例中的目标业务实体为多播承载管理实体时，各个业务参与实体在向多播承载管理实体发送请求消息时，才可以获知多播承载当前的使用状态。在又一种实现方式中，当上述实施例中的目标业务实体为业务控制实体时，业务控制实体可以主动向各个业务参与实体推送多播承载的最新的使用状态，且各个业务参与实体中都可以获得该多播承载的的使用状态。
可选地，在上述实施例的第一种实施场景的基础上，上述方法还包括：
若第一业务参与实体停止使用上述目标多播承载发送业务数据，则第一业务参与实体可以向目标业务实体发送指示消息。
其中，该指示消息用于通知目标业务实体：第一业务参与实体停止使用上述目标多播承载发送业务数据。
相应地，上述方法还可以包括：目标业务实体将终端群组对该目标多播承载的使 用状态更新为：没有业务参与实体使用目标多播承载发送终端群组的业务数据。或者，目标业务实体将终端群组对该目标多播承载的使用状态更新为：目标多播承载上没有终端群组的业务数据在发送。或者，目标业务实体将终端群组对该目标多播承载的使用状态更新为：未使用。
可选地，在上述实施例的第二种实施场景中，上述方法还包括：
第一业务参与实体向目标业务实体发送承载信息上报消息，该承载信息上报消息包括服务区域的标识、该群组标识和该目标多播承载的标识；或者，
当目标业务参与实体为业务控制实体时，第一业务参与实体接收来自业务控制实体的推送消息，该推送消息包括服务区域的标识、该群组标识和该目标多播承载的标识。
需要说明的是，上述第二种实施场景和第一种实施场景可以结合，不予限制。
该第二种实施场景中，当由该第一业务参与实体建立上述目标多播承载时，则将该目标多播承载的信息，例如包括服务区域的标识、该群组标识和该目标多播承载的标识，携带于承载信息上报消息中发送至目标业务实体，可由目标业务实体对该目标多播承载进行管理。
当该目标多播承载是由其他业务参与实体建立，并将建立的目标多播承载的信息上报至该业务参与实体时，若该业务参与实体为业务控制实体，则该业务控制实体具有推送多播承载的信息的功能，因此可以向该除了建立该目标多播承载的其他业务参与实体之外的业务参与实体(例如包括第一业务参与实体)发送推送消息，该推送消息中包括服务区域的标识、该群组标识和该目标多播承载的标识，从而终端群组的终端注册的业务参与实体均可获取到由其中的某个业务参与实体建立的多播承载的信息。
下面介绍上述实施例中的目标业务实体获取上述目标多播承载的信息(包括目标多播承载的标识)和管理该目标多播承载的使用状态的实现方式。目标业务实体可以是业务控制实体或多播承载管理实体。
实现方式一，目标业务实体为业务控制实体。
业务控制实体可以管理终端群组中的终端所注册的业务参与实体。
例如，若由业务控制实体所管理的第一业务参与实体建立该目标多播承载，则第一业务参与实体在建立了目标多播承载后，向业务控制实体发送承载信息上报消息，该承载信息上报消息包括群组标识和目标多播承载的标识。可选地，承载信息上报消息还包括服务区域的标识。
其中，该承载信息上报消息可以用于上报建立的多播承载的信息。
该实施例中，任一业务参与实体在建立了一个多播承载，并通过上报消息发送建立的多播承载的信息时，该上报消息均可以称为承载信息上报消息。
业务控制实体在接收到第一业务参与实体发送的承载信息上报消息后，从中获取群组标识和目标多播承载的标识。可选地，还获取服务区域的标识。然后业务控制实体记录该目标多播承载的信息。
进一步地，业务控制实体还记录多播承载的使用状态。例如，可以有以下方式。
方式一，使用状态为在使用中，或者，使用状态为未使用。
该方式中，目标业务实体记录多播承载的使用状态为：使用中或未使用。
其中，使用中指的是，当前有业务参与实体正在使用该多播承载发送业务数据，或者，当前有业务参与实体使用该多播承载并准备开始发送业务数据。
未使用指的是，当前没有业务实体正在使用该多播承载发送业务数据，或者，当前没有业务参与实体使用该多播承载并准备开始发送业务数据。
方式二，使用状态为多播承载上有终端群组的业务数据在发送，或者，使用状态为多播承载上没有终端群组的业务数据在发送。
该实现方式中，业务控制实体记录多播承载的使用状态为：多播承载上有终端群组的业务数据在发送，或，多播承载上没有终端群组的业务数据在发送。
其中，多播承载上有终端群组的业务数据在发送，指的是，该多播承载当前正在被用于发送终端群组的业务数据。
多播承载上没有终端群组的业务数据在发送，指的是，该多播承载当前未被用于发送终端群组的业务数据。
方式三，使用状态为没有业务参与实体使用多播承载发送终端群组的业务数据，或者，使用状态为有业务参与实体使用多播承载发送终端群组的业务数据，或者，使用状态为第二业务参与实体使用多播承载发送终端群组的业务数据。
具体地，上述方式二中的多播承载上有终端群组的业务数据在发送，在该方式三中，被记录为，有业务参与实体使用多播承载发送终端群组的业务数据，或者，被记录为，第二业务参与实体使用多播承载发送终端群组的业务数据。该第二业务参与实体指的是业务控制关联的任一业务参与实体。
上述方式二中的多播承载上没有终端群组的业务数据在发送，在该方式三中，被记录为，没有业务参与实体使用多播承载发送终端群组的业务数据。
需要说明的是，上述三种方式，均是对多播承载的使用状态的记录方法，在实际应用中，可选择其中任一种或几种方法来实施。
在实际应用中，可以是业务控制实体管理的任一业务参与实体建立多播承载(例如，建立上述目标多播承载)，并将建立的多播承载的信息上报给业务控制实体。例如，使用第四业务参与实体来表示业务控制实体管理的任一业务参与实体，则上报过程可以表述为：业务控制实体接收来自第四业务参与实体的承载信息上报消息，该承载信息上报消息包括服务区域的标识和多播承载的标识。可选地，承载信息上报消息还包括群组标识，可选地，承载信息上报消息进一步还包括第四业务参与实体的信息，如地址信息或标识信息等。
通过上述方法，业务控制实体可记录各业务参与实体建立并上报的多播承载的信息，其中记录的信息包括终端群组对多播承载的使用状态。
业务控制实体在接收到业务参与实体发送的承载信息上报消息后，并获取并记录了多播承载的信息，如群组标识、多播承载的标识、服务区域的标识之后，还向该业务控制实体所管理的业务参与实体中除建立该多播承载的业务参与实体之外的其他业务参与实体，发送推送消息，该推送消息中包括群组标识和多播承载的标识，可选地，还包括服务区域的标识。可选地，还包括建立该多播承载的业务参与实体的信息。可选地，还包括终端群组对该多播承载的使用状态。
通过该方法，任一业务参与实体建立了多播承载后，上报给业务控制实体，业务控制实体一方面记录在多播承载的信息，另一方面，还将该多播承载的信息推送给其 他业务参与实体，使得业务控制实体所管理的业务参与实体均可以记录该多播承载的相关信息。
实现方式二，目标业务实体为多播承载管理实体。
若目标业务实体为多播承载管理实体，一方面，该多播承载管理实体可以采用与上述业务控制实体获取到多播承载的信息的相同的方法，获取到业务参与实体建立的多播承载的信息。且记录多播承载的信息的方式也可以采用与上述业务控制实体相同的记录方式。
另一方面，由于多播承载管理实体没有终端群组的群组信息，无法知道该群组中有哪些业务参与实体，因而可以不具有上述业务控制实体的推送功能，即多播承载管理实体记录了业务参与实体上报的多播承载的信息之后，可以不将记录的多播承载的信息推送给其他业务参与实体。
基于相同的发明构思，如图14所示，为本申请提供的一种装置示意图，该装置1400可以是目标业务实体，也可以是片上系统或芯片，可执行图13所示的实施例中由目标业务实体执行的方法。
该装置1400包括至少一个处理器141，收发器142，可选地，还包括存储器143。所述处理器141、收发器142、存储器143通过通信总线连接。
处理器141可以是一个通用中央处理器(CPU)，微处理器，特定ASIC，或一个或多个用于控制本发明方案程序执行的集成电路。
通信总线可包括一通路，在上述单元之间传送信息。
所述收发器142，用于与其他设备或通信网络通信，该收发器可以是一种通信接口，例如，有线接口或无线接口，或wifi接口，或该收发器包括射频电路。
存储器143可以是ROM或可存储静态信息和指令的其他类型的静态存储设备，RAM或者可存储信息和指令的其他类型的动态存储设备，也可以是EEPROM、CD-ROM或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器143可以是独立存在，通过通信总线与处理器141相连接。存储器143也可以和处理器集成在一起。其中，所述存储器143用于存储执行本发明方案的应用程序代码，并由处理器141来控制执行。所述处理器141用于执行所述存储器143中存储的应用程序代码。
在具体实现中，作为一种实施例，处理器141可以包括一个或多个CPU，例如图14中的CPU0和CPU1。
在具体实现中，作为一种实施例，装置1400可以包括多个处理器，例如图14中的处理器141和处理器148。这些处理器中的每一个可以是一个单核(single-CPU)处理器，也可以是一个多核(multi-CPU)处理器，这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
应理解，该装置可以用于实现图13所示的实施例的通信方法中由目标业务实体执行的步骤，相关特征可以参照上文，此处不再赘述。
本申请可以根据上述方法示例对装置进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。比如，在采用对应各个功能划分各个功能模块的情况下，图15示出了一种装置示意图，该装置可以是图13所示的实施例中所涉及的目标业务实体或片上系统或芯片，该装置包括处理单元1501和通信单元1502。
所述处理单元1501，用于控制所述通信单元1502：
接收来自第一业务参与实体的第一请求消息，所述第一请求消息包括群组标识和目标多播承载的标识，所述第一请求消息用于请求使用所述目标多播承载发送所述群组标识对应的终端群组的业务数据；
向所述第一业务参与实体发送第一响应消息，所述第一响应消息包括所述终端群组对所述目标多播承载的使用状态。
在一种可能的实现方式中，所述使用状态包括：
在使用中或未使用；或者，
所述目标多播承载上有所述终端群组的业务数据在发送，或者，所述目标多播承载上没有所述终端群组的业务数据在发送；或者，
没有业务参与实体使用所述目标多播承载发送所述终端群组的业务数据，或者，有业务参与实体使用所述目标多播承载发送所述终端群组的业务数据，或者，第二业务参与实体使用所述目标多播承载发送所述终端群组的业务数据。
在一种可能的实现方式中，所述处理单元1501，还用于控制所述通信单元1502：
接收来自所述第一业务参与实体的指示消息，所述指示消息用于指示所述第一业务参与实体使用所述目标多播承载发送所述终端群组的业务数据；
所述处理单元1501，还用于根据所述指示消息，更新所述使用状态。
在一种可能的实现方式中，所述处理单元1501，具体用于：
将所述使用状态更新为所述第一业务参与实体使用所述目标多播承载发送所述终端群组的业务数据；或者，
将所述使用状态更新为有业务参与实体使用所述目标多播承载发送所述终端群组的业务数据；或者，
将所述使用状态更新为在使用中。
在一种可能的实现方式中，所述处理单元1501，还用于控制所述通信单元1502：
接收来自第三业务参与实体的第二请求消息，所述第二请求消息包括所述群组标识和所述目标多播承载的标识，所述第二请求消息用于请求使用所述目标多播承载发送所述终端群组的业务数据；
向所述第三业务参与实体发送第二响应消息，所述第二响应消息包括所述目标多播承载的更新后的使用状态。
在一种可能的实现方式中，所述装置1500为业务控制实体；所述处理单元1501，还用于控制所述通信单元1502：向第三业务参与实体发送通知消息，所述通知消息包括所述目标多播承载的更新后的使用状态。
在一种可能的实现方式中，所述处理单元1501，还用于控制所述通信单元1502：
接收来自所述第三业务参与实体的通知状态上报消息，所述通知状态上报消息用于指示所述第三业务参与实体通知终端在所述目标多播承载上接收所述终端群组的业务数据。
在一种可能的实现方式中，所述处理单元1501，还用于控制所述通信单元1502：
接收来自第四业务参与实体的承载信息上报消息，所述承载信息上报消息可以包括服务区域的标识、所述群组标识和所述目标多播承载的标识。可选地，还包括所述第四业务参与实体的标识和或地址。
在本实施例中，该装置以对应各个功能划分各个功能模块的形式来呈现，或者，该业务控制实体以采用集成的方式划分各个功能模块的形式来呈现。这里的“模块”可以指ASIC，电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。
应理解，该装置可以用于实现本发明实施例的通信方法中由目标业务实体执行的步骤，相关特征可以参照上文，此处不再赘述。
基于相同的发明构思，如图16所示，为本申请提供的一种装置示意图，该装置1600例如可以是业务参与实体，也可以是片上系统或芯片，可执行图13所示的实施例中由第一业务参与实体执行的方法。
装置1600包括至少一个处理器161，收发器162，可选地，还包括存储器163。处理器161、收发器162、存储器163通过通信总线连接。
处理器161可以是一个通用中央处理器(CPU)，微处理器，ASIC，或一个或多个用于控制本发明方案程序执行的集成电路。
通信总线可包括一通路，在上述单元之间传送信息。
收发器162，用于与其他设备或通信网络通信，该收发器可以是一种通信接口，例如，有线接口或无线接口，或wifi接口，或该收发器包括射频电路。
存储器163可以是ROM或可存储静态信息和指令的其他类型的静态存储设备，RAM或者可存储信息和指令的其他类型的动态存储设备，也可以是EEPROM、CD-ROM或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器163可以是独立存在，通过通信总线与处理器161相连接。存储器163也可以和处理器集成在一起。其中，存储器163用于存储执行本发明方案的应用程序代码，并由处理器161来控制执行。处理器161用于执行存储器163中存储的应用程序代码。
在具体实现中，作为一种实施例，处理器161可以包括一个或多个CPU，例如图16中的CPU0和CPU1。
在具体实现中，作为一种实施例，装置1600可以包括多个处理器，例如图16中的处理器161和处理器168。这些处理器中的每一个可以是一个单核(single-CPU)处理器，也可以是一个多核(multi-CPU)处理器，这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
应理解，该装置可以用于实现图13所示的实施例的通信方法中由第一业务参与实 体执行的步骤，相关特征可以参照上文，此处不再赘述。
本申请可以根据上述方法示例对装置进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。比如，在采用对应各个功能划分各个功能模块的情况下，图17示出了一种装置示意图，该装置可以是图13所示的实施例中所涉及的第一业务参与实体，该装置包括处理单元1701和通信单元1702。
所述处理单元1701，用于控制所述通信单元1702：
向目标业务实体发送请求消息，所述请求消息包括群组标识和目标多播承载的标识，所述请求消息用于请求使用所述目标多播承载发送所述群组标识对应的终端群组的业务数据；
接收来自所述目标业务实体的响应消息，所述响应消息包括所述终端群组对所述目标多播承载的使用状态。
在一种可能的实现方式中，所述处理单元1701，还用于根据所述使用状态，确定使用所述目标多播承载发送所述终端群组的业务数据；
所述处理单元1701，还用于控制所述通信单元1702向所述目标业务实体发送指示消息，所述指示消息用于指示第一业务参与实体使用所述目标多播承载发送所述终端群组的业务数据。
在一种可能的实现方式中，所述处理单元1701，具体用于：
当所述第一业务参与实体存在所述待发送的终端群组的业务数据，且所述使用状态为没有业务参与实体使用所述目标多播承载发送所述终端群组的业务数据或所述使用状态为未使用或所述使用状态为所述目标多播承载上没有所述终端群组的业务数据在发送时，确定使用所述目标多播承载发送所述终端群组的业务数据；或者，
当所述使用状态为没有业务参与实体使用所述目标多播承载发送所述终端群组的业务数据或所述使用状态为未使用或所述使用状态为所述目标多播承载上没有所述终端群组的业务数据在发送时，确定使用所述目标多播承载发送所述终端群组的业务数据。
在一种可能的实现方式中，所述处理单元1701，还用于控制所述通信单元1702向终端发送通知消息，所述通知消息用于通知所述终端通过所述目标多播承载接收所述终端群组的业务数据。
在一种可能的实现方式中，所述处理单元1701，还用于控制所述通信单元1702向所述目标业务实体发送通知状态上报消息，所述通知状态上报消息用于指示所述第一业务参与实体通知终端在所述目标多播承载上接收所述终端群组的业务数据。
在一种可能的实现方式中，当所述目标多播承载由所述第一业务参与实体建立时，所述处理单元1701，还用于控制所述通信单元1702通过所述目标多播承载发送所述终端群组的业务数据；或者，
当所述目标多播承载由第二业务参与实体建立时，所述处理单元1701，还用于控制所述通信单元1702向所述第二业务参与实体发送指示信息和待发送的终端群组的 业务数据，所述指示信息用于指示所述第二业务参与实体，通过所述目标多播承载发送所述待发送的终端群组的业务数据。
在一种可能的实现方式中，所述处理单元1701，还用于控制所述通信单元1702：
向所述目标业务实体发送承载信息上报消息，所述承载信息上报消息包括服务区域的标识、所述群组标识和所述目标多播承载的标识；或者，
接收来自所述目标业务实体的推送消息，所述推送消息包括服务区域的标识、所述群组标识和所述目标多播承载的标识。
在本实施例中，该装置以对应各个功能划分各个功能模块的形式来呈现，或者，该业务控制实体以采用集成的方式划分各个功能模块的形式来呈现。这里的“模块”可以指ASIC，电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。
应理解，该装置可以用于实现本发明图13所示的实施例的通信方法中由第一业务参与实体执行的步骤，相关特征可以参照上文，此处不再赘述。
基于相同的发明构思，如图18所示，为本申请提供的一种装置示意图，该装置1800可以是目标业务实体，也可以是片上系统或芯片，可执行上述实施例的步骤4011-步骤4014中由目标业务实体执行的方法。
该装置1800包括至少一个处理器181，收发器182，可选地，还包括存储器183。所述处理器181、收发器182、存储器183通过通信总线连接。
处理器181可以是一个通用中央处理器(CPU)，微处理器，特定ASIC，或一个或多个用于控制本发明方案程序执行的集成电路。
通信总线可包括一通路，在上述单元之间传送信息。
所述收发器182，用于与其他设备或通信网络通信，该收发器可以是一种通信接口，例如，有线接口或无线接口，或wifi接口，或该收发器包括射频电路。
存储器183可以是ROM或可存储静态信息和指令的其他类型的静态存储设备，RAM或者可存储信息和指令的其他类型的动态存储设备，也可以是EEPROM、CD-ROM或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器183可以是独立存在，通过通信总线与处理器181相连接。存储器183也可以和处理器集成在一起。其中，所述存储器183用于存储执行本发明方案的应用程序代码，并由处理器181来控制执行。所述处理器181用于执行所述存储器183中存储的应用程序代码。
在具体实现中，作为一种实施例，处理器181可以包括一个或多个CPU，例如图18中的CPU0和CPU1。
在具体实现中，作为一种实施例，装置1800可以包括多个处理器，例如图18中的处理器181和处理器188。这些处理器中的每一个可以是一个单核(single-CPU)处理器，也可以是一个多核(multi-CPU)处理器，这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
应理解，该装置可以用于实现上述实施例的步骤4011-步骤4014中由目标业务实 体执行的步骤，相关特征可以参照上文，此处不再赘述。
本申请可以根据上述方法示例对装置进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。比如，在采用对应各个功能划分各个功能模块的情况下，图19示出了一种装置示意图，该装置可以是图13所示的实施例中所涉及的目标业务实体或片上系统或芯片，该装置包括处理单元1901和通信单元1902。
所述处理单元1901，用于控制所述通信单元1902：
接收来自第一业务参与实体的第一请求消息，所述第一请求消息包括目标多播承载的标识和终端群组的群组标识，所述第一请求消息用于请求使用所述目标多播承载发送所述终端群组的业务数据；
向所述第一业务参与实体发送第一响应消息，所述第一响应消息用于指示所述第一业务参与实体使用所述目标多播承载发送所述终端群组的业务数据。
在一种可能的实现方式中，所述第一响应消息包括第一指示信息，所述第一指示信息用于指示所述第一业务参与实体使用所述目标多播承载发送所述终端群组的业务数据。
在一种可能的实现方式中，其特征在于，所述处理单元1901，还用于控制所述通信单元1902：
接收来自第二业务参与实体的第二请求消息，所述第二请求消息包括所述目标多播承载的标识和所述终端群组的群组标识，所述第二请求消息用于请求使用所述目标多播承载发送所述终端群组的业务数据；
向所述第二业务实体发送第二响应消息，所述第二响应消息用于指示所述第二业务参与实体不使用所述目标多播承载发送所述终端群组的业务数据。
在一种可能的实现方式中，所述第二响应消息包括第二指示信息，所述第二指示信息用于指示所述第二业务参与实体不使用所述目标多播承载发送所述终端群组的业务数据。
在一种可能的实现方式中，所述处理单元1901，还用于控制所述通信单元1902：
接收来自第三业务参与实体的上报消息，所述上报消息包括所述目标多播承载的标识。
在一种可能的实现方式中，所述上报消息还包括所述第三业务参与实体的地址信息。
在本实施例中，该装置以对应各个功能划分各个功能模块的形式来呈现，或者，该业务控制实体以采用集成的方式划分各个功能模块的形式来呈现。这里的“模块”可以指ASIC，电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。
应理解，该装置可以用于实现本发明实施例的上述实施例的步骤4011-步骤4014中由目标业务实体执行的步骤，相关特征可以参照上文，此处不再赘述。
基于相同的发明构思，如图20所示，为本申请提供的一种装置示意图，该装置2000例如可以是业务参与实体，也可以是片上系统或芯片，可执行上述实施例的步骤4011-步骤4014中由业务参与实体执行的方法。
装置2000包括至少一个处理器201，收发器202，可选地，还包括存储器203。处理器201、收发器202、存储器203通过通信总线连接。
处理器201可以是一个通用中央处理器(CPU)，微处理器，ASIC，或一个或多个用于控制本发明方案程序执行的集成电路。
通信总线可包括一通路，在上述单元之间传送信息。
收发器202，用于与其他设备或通信网络通信，该收发器可以是一种通信接口，例如，有线接口或无线接口，或wifi接口，或该收发器包括射频电路。
存储器203可以是ROM或可存储静态信息和指令的其他类型的静态存储设备，RAM或者可存储信息和指令的其他类型的动态存储设备，也可以是EEPROM、CD-ROM或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器203可以是独立存在，通过通信总线与处理器201相连接。存储器203也可以和处理器集成在一起。其中，存储器203用于存储执行本发明方案的应用程序代码，并由处理器201来控制执行。处理器201用于执行存储器203中存储的应用程序代码。
在具体实现中，作为一种实施例，处理器201可以包括一个或多个CPU，例如图20中的CPU0和CPU1。
在具体实现中，作为一种实施例，装置2000可以包括多个处理器，例如图20中的处理器201和处理器208。这些处理器中的每一个可以是一个单核(single-CPU)处理器，也可以是一个多核(multi-CPU)处理器，这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
应理解，该装置可以用于实现上述实施例的步骤4011-步骤4014中由业务参与实体执行的步骤，相关特征可以参照上文，此处不再赘述。
本申请可以根据上述方法示例对装置进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。比如，在采用对应各个功能划分各个功能模块的情况下，图21示出了一种装置示意图，该装置可以是上述实施例的步骤4011-步骤4014中所涉及的业务参与实体，该装置包括处理单元2101和通信单元2102。
所述处理单元2101，用于控制所述通信单元2102：
向目标业务实体发送请求消息，所述请求消息包括目标多播承载的标识和终端群组的群组标识，所述请求消息用于请求使用所述目标多播承载发送所述终端群组的业务数据；
接收来自所述目标业务实体的响应消息，所述响应消息用于指示所述业务参与实 体使用所述目标多播承载发送所述终端群组的业务数据。
在一种可能的实现方式中，所述响应消息包括第一指示信息，所述第一指示信息用于指示所述业务参与实体使用所述目标多播承载发送所述终端群组的业务数据。
在一种可能的实现方式中，所述处理单元2101，还用于控制所述通信单元2102：
使用所述目标多播承载发送所述终端群组的业务数据。
在本实施例中，该装置以对应各个功能划分各个功能模块的形式来呈现，或者，该业务控制实体以采用集成的方式划分各个功能模块的形式来呈现。这里的“模块”可以指ASIC，电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。
应理解，该装置可以用于实现上述实施例的步骤4011-步骤4014中由业务参与实体执行的步骤，相关特征可以参照上文，此处不再赘述。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本发明实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘(Solid State Disk，SSD))等。
尽管在此结合各实施例对本发明进行了描述，然而，在实施所要求保护的本发明过程中，本领域技术人员通过查看所述附图、公开内容、以及所附权利要求书，可理解并实现所述公开实施例的其他变化。在权利要求中，“包括”(comprising)一词不排除其他组成部分或步骤，“一”或“一个”不排除多个的情况。单个处理器或其他单元可以实现权利要求中列举的若干项功能。相互不同的从属权利要求中记载了某些措施，但这并不表示这些措施不能组合起来产生良好的效果。
本领域技术人员应明白，本申请的实施例可提供为方法、装置(设备)、计算机可读存储介质或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式，这里将它们都统称为“模块”或“系统”。
本申请是参照本申请的方法、装置(设备)和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的 装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
尽管结合具体特征及其实施例对本发明进行了描述，显而易见的，在不脱离本发明的精神和范围的情况下，可对其进行各种修改和组合。相应地，本说明书和附图仅仅是所附权利要求所界定的本发明的示例性说明，且视为已覆盖本发明范围内的任意和所有修改、变化、组合或等同物。显然，本领域的技术人员可以对本发明进行各种改动和变型而不脱离本发明的精神和范围。这样，倘若本发明的这些修改和变型属于本发明权利要求及其等同技术的范围之内，则本发明也意图包含这些改动和变型在内。

Claims (36)

  1. 一种通信方法，其特征在于，包括：
    目标业务实体接收来自第一业务参与实体的第一请求消息，所述第一请求消息包括群组标识和目标多播承载的标识，所述第一请求消息用于请求使用所述目标多播承载发送所述群组标识对应的终端群组的业务数据；
    所述目标业务实体向所述第一业务参与实体发送第一响应消息，所述第一响应消息包括所述终端群组对所述目标多播承载的使用状态。
  2. 根据权利要求1所述的方法，其特征在于，所述使用状态包括：
    在使用中或未使用；或者，
    所述目标多播承载上有所述终端群组的业务数据在发送，或者，所述目标多播承载上没有所述终端群组的业务数据在发送；或者，
    没有业务参与实体使用所述目标多播承载发送所述终端群组的业务数据，或者，有业务参与实体使用所述目标多播承载发送所述终端群组的业务数据，或者，第二业务参与实体使用所述目标多播承载发送所述终端群组的业务数据。
  3. 根据权利要求1或2所述的方法，其特征在于，所述方法还包括：
    所述目标业务实体接收来自所述第一业务参与实体的指示消息，所述指示消息用于指示所述第一业务参与实体使用所述目标多播承载发送所述终端群组的业务数据；
    所述目标业务实体根据所述指示消息，更新所述使用状态。
  4. 根据权利要求3所述的方法，其特征在于，所述目标业务实体根据所述指示消息，更新所述使用状态，包括：
    所述目标业务实体将所述使用状态更新为所述第一业务参与实体使用所述目标多播承载发送所述终端群组的业务数据；或者，
    所述目标业务实体将所述使用状态更新为有业务参与实体使用所述目标多播承载发送所述终端群组的业务数据；或者，
    所述目标业务实体将所述使用状态更新为在使用中。
  5. 根据权利要求3或4所述的方法，其特征在于，所述方法还包括：
    所述目标业务实体接收来自第三业务参与实体的第二请求消息，所述第二请求消息包括所述群组标识和所述目标多播承载的标识，所述第二请求消息用于请求使用所述目标多播承载发送所述终端群组的业务数据；
    所述目标业务实体向所述第三业务参与实体发送第二响应消息，所述第二响应消息包括所述目标多播承载的更新后的使用状态。
  6. 根据权利要求3或4所述的方法，其特征在于，所述目标业务实体为业务控制实体；所述方法还包括：
    所述目标业务实体向第三业务参与实体发送通知消息，所述通知消息包括所述目标多播承载的更新后的使用状态。
  7. 根据权利要求6所述的方法，其特征在于，所述方法还包括：
    所述目标业务实体接收来自所述第三业务参与实体的通知状态上报消息，所述通知状态上报消息用于指示所述第三业务参与实体通知终端在所述目标多播承载上接收所述终端群组的业务数据。
  8. 根据权利要求1至7中任一项所述的方法，其特征在于，所述方法还包括：
    所述目标业务实体接收来自第四业务参与实体的承载信息上报消息，所述承载信息上报消息包括服务区域的标识、所述群组标识和所述目标多播承载的标识。
  9. 一种通信方法，其特征在于，包括：
    第一业务参与实体向目标业务实体发送请求消息，所述请求消息包括群组标识和目标多播承载的标识，所述请求消息用于请求使用所述目标多播承载发送所述群组标识对应的终端群组的业务数据；
    所述第一业务参与实体接收来自所述目标业务实体的响应消息，所述响应消息包括所述终端群组对所述目标多播承载的使用状态。
  10. 根据权利要求9所述的方法，其特征在于，所述方法还包括：
    所述第一业务参与实体根据所述使用状态，确定使用所述目标多播承载发送所述终端群组的业务数据；
    所述第一业务参与实体向所述目标业务实体发送指示消息，所述指示消息用于指示所述第一业务参与实体使用所述目标多播承载发送所述终端群组的业务数据。
  11. 根据权利要求10所述的方法，其特征在于，所述第一业务参与实体根据所述使用状态，确定使用所述目标多播承载发送所述终端群组的业务数据，包括：
    当所述第一业务参与实体存在待发送的所述终端群组的业务数据，且所述使用状态为没有业务参与实体使用所述目标多播承载发送所述终端群组的业务数据或所述使用状态为未使用或所述使用状态为所述目标多播承载上没有所述终端群组的业务数据在发送时，所述第一业务参与实体确定使用所述目标多播承载发送所述终端群组的业务数据；或者，
    当所述使用状态为没有业务参与实体使用所述目标多播承载发送所述终端群组的业务数据或所述使用状态为未使用或所述使用状态为所述目标多播承载上没有所述终端群组的业务数据在发送时，所述第一业务参与实体确定使用所述目标多播承载发送所述终端群组的业务数据。
  12. 一种通信方法，其特征在于，包括：
    目标业务实体接收来自第一业务参与实体的第一请求消息，所述第一请求消息包括目标多播承载的标识和终端群组的群组标识，所述第一请求消息用于请求使用所述目标多播承载发送所述终端群组的业务数据；
    所述目标业务实体向所述第一业务参与实体发送第一响应消息，所述第一响应消息用于指示所述第一业务参与实体使用所述目标多播承载发送所述终端群组的业务数据。
  13. 根据权利要求12所述的方法，其特征在于，所述第一响应消息包括第一指示信息，所述第一指示信息用于指示所述第一业务参与实体使用所述目标多播承载发送所述终端群组的业务数据。
  14. 根据权利要求12或13所述的方法，其特征在于，所述方法还包括：
    所述目标业务实体接收来自第二业务参与实体的第二请求消息，所述第二请求消息包括所述目标多播承载的标识和所述终端群组的群组标识，所述第二请求消息用于请求使用所述目标多播承载发送所述终端群组的业务数据；
    所述目标业务实体向所述第二业务实体发送第二响应消息，所述第二响应消息用于指示所述第二业务参与实体不使用所述目标多播承载发送所述终端群组的业务数据。
  15. 根据权利要求14所述的方法，其特征在于，所述第二响应消息包括第二指示信息，所述第二指示信息用于指示所述第二业务参与实体不使用所述目标多播承载发送所述终端群组的业务数据。
  16. 根据权利要求12至15任一项所述的方法，其特征在于，所述方法还包括：
    所述目标业务实体接收来自第三业务参与实体的上报消息，所述上报消息包括所述目标多播承载的标识和所述第三业务参与实体的地址信息。
  17. 一种通信方法，其特征在于，包括：
    业务参与实体向目标业务实体发送请求消息，所述请求消息包括目标多播承载的标识和终端群组的群组标识，所述请求消息用于请求使用所述目标多播承载发送所述终端群组的业务数据；
    所述业务参与实体接收来自所述目标业务实体的响应消息，所述响应消息用于指示所述业务参与实体使用所述目标多播承载发送所述终端群组的业务数据。
  18. 根据权利要求17所述的方法，其特征在于，所述响应消息包括第一指示信息，所述第一指示信息用于指示所述业务参与实体使用所述目标多播承载发送所述终端群组的业务数据。
  19. 一种装置，其特征在于，包括处理单元和通信单元；
    所述处理单元，用于控制所述通信单元：
    接收来自第一业务参与实体的第一请求消息，所述第一请求消息包括群组标识和目标多播承载的标识，所述第一请求消息用于请求使用所述目标多播承载发送所述群组标识对应的终端群组的业务数据；
    向所述第一业务参与实体发送第一响应消息，所述第一响应消息包括所述终端群组对所述目标多播承载的使用状态。
  20. 根据权利要求19所述的装置，其特征在于，所述使用状态包括：
    在使用中或未使用；或者，
    所述目标多播承载上有所述终端群组的业务数据在发送，或者，所述目标多播承载上没有所述终端群组的业务数据在发送；或者，
    没有业务参与实体使用所述目标多播承载发送所述终端群组的业务数据，或者，有业务参与实体使用所述目标多播承载发送所述终端群组的业务数据，或者，第二业务参与实体使用所述目标多播承载发送所述终端群组的业务数据。
  21. 根据权利要求19或20所述的装置，其特征在于，所述处理单元，还用于控制所述通信单元：
    接收来自所述第一业务参与实体的指示消息，所述指示消息用于指示所述第一业务参与实体使用所述目标多播承载发送所述终端群组的业务数据；
    所述处理单元，还用于根据所述指示消息，更新所述使用状态。
  22. 根据权利要求21所述的装置，其特征在于，所述处理单元，具体用于：
    将所述使用状态更新为所述第一业务参与实体使用所述目标多播承载发送所述终端群组的业务数据；或者，
    将所述使用状态更新为有业务参与实体使用所述目标多播承载发送所述终端群组的业务数据；或者，
    将所述使用状态更新为在使用中。
  23. 根据权利要求21或22所述的装置，其特征在于，所述处理单元，还用于控制所述通信单元：
    接收来自第三业务参与实体的第二请求消息，所述第二请求消息包括所述群组标识和所述目标多播承载的标识，所述第二请求消息用于请求使用所述目标多播承载发送所述终端群组的业务数据；
    向所述第三业务参与实体发送第二响应消息，所述第二响应消息包括所述目标多播承载的更新后的使用状态。
  24. 根据权利要求21或22所述的装置，其特征在于，所述装置为业务控制实体；所述处理单元，还用于控制所述通信单元：
    向第三业务参与实体发送通知消息，所述通知消息包括所述目标多播承载的更新后的使用状态。
  25. 根据权利要求24所述的装置，其特征在于，所述处理单元，还用于控制所述通信单元：
    接收来自所述第三业务参与实体的通知状态上报消息，所述通知状态上报消息用于指示所述第三业务参与实体通知终端在所述目标多播承载上接收所述终端群组的业务数据。
  26. 根据权利要求19至25中任一项所述的装置，其特征在于，所述处理单元，还用于控制所述通信单元：
    接收来自第四业务参与实体的承载信息上报消息，所述承载信息上报消息包括服务区域的标识、所述群组标识和所述目标多播承载的标识。
  27. 一种装置，其特征在于，包括处理单元和通信单元；
    所述处理单元，用于控制所述通信单元：
    向目标业务实体发送请求消息，所述请求消息包括群组标识和目标多播承载的标识，所述请求消息用于请求使用所述目标多播承载发送所述群组标识对应的终端群组的业务数据；
    接收来自所述目标业务实体的响应消息，所述响应消息包括所述终端群组对所述目标多播承载的使用状态。
  28. 根据权利要求27所述的装置，其特征在于，所述处理单元，还用于根据所述使用状态，确定使用所述目标多播承载发送所述终端群组的业务数据；
    所述处理单元，还用于控制所述通信单元向所述目标业务实体发送指示消息，所述指示消息用于指示第一业务参与实体使用所述目标多播承载发送所述终端群组的业务数据。
  29. 根据权利要求28所述的装置，其特征在于，所述处理单元，具体用于：
    当所述第一业务参与实体存在待发送的所述终端群组的业务数据，且所述使用状态为没有业务参与实体使用所述目标多播承载发送所述终端群组的业务数据或所述使用状态为未使用或所述使用状态为所述目标多播承载上没有所述终端群组的业务数据在发送时，确定使用所述目标多播承载发送所述终端群组的业务数据；或者，
    当所述使用状态为没有业务参与实体使用所述目标多播承载发送所述终端群组的业务数据或所述使用状态为未使用或所述使用状态为所述目标多播承载上没有所述终端群组的业务数据在发送时，确定使用所述目标多播承载发送所述终端群组的业务数 据。
  30. 一种装置，其特征在于，包括处理单元和通信单元；
    所述处理单元，用于控制所述通信单元：
    接收来自第一业务参与实体的第一请求消息，所述第一请求消息包括目标多播承载的标识和终端群组的群组标识，所述第一请求消息用于请求使用所述目标多播承载发送所述终端群组的业务数据；
    向所述第一业务参与实体发送第一响应消息，所述第一响应消息用于指示所述第一业务参与实体使用所述目标多播承载发送所述终端群组的业务数据。
  31. 根据权利要求30所述的装置，其特征在于，所述第一响应消息包括第一指示信息，所述第一指示信息用于指示所述第一业务参与实体使用所述目标多播承载发送所述终端群组的业务数据。
  32. 根据权利要求30或31所述的装置，其特征在于，所述处理单元，还用于控制所述通信单元：
    接收来自第二业务参与实体的第二请求消息，所述第二请求消息包括所述目标多播承载的标识和所述终端群组的群组标识，所述第二请求消息用于请求使用所述目标多播承载发送所述终端群组的业务数据；
    向所述第二业务实体发送第二响应消息，所述第二响应消息用于指示所述第二业务参与实体不使用所述目标多播承载发送所述终端群组的业务数据。
  33. 根据权利要求32所述的装置，其特征在于，所述第二响应消息包括第二指示信息，所述第二指示信息用于指示所述第二业务参与实体不使用所述目标多播承载发送所述终端群组的业务数据。
  34. 根据权利要求30至33任一项所述的装置，其特征在于，所述处理单元，还用于控制所述通信单元：
    接收来自第三业务参与实体的上报消息，所述上报消息包括所述目标多播承载的标识和所述第三业务参与实体的地址信息。
  35. 一种装置，其特征在于，包括处理单元和通信单元；
    所述处理单元，用于控制所述通信单元：
    向目标业务实体发送请求消息，所述请求消息包括目标多播承载的标识和终端群组的群组标识，所述请求消息用于请求使用所述目标多播承载发送所述终端群组的业务数据；
    接收来自所述目标业务实体的响应消息，所述响应消息用于指示所述业务参与实体使用所述目标多播承载发送所述终端群组的业务数据。
  36. 根据权利要求35所述的装置，其特征在于，所述响应消息包括第一指示信息，所述第一指示信息用于指示所述业务参与实体使用所述目标多播承载发送所述终端群组的业务数据。
PCT/CN2018/088256 2017-09-30 2018-05-24 一种通信方法及装置 WO2019062169A1 (zh)

Priority Applications (6)

Application Number Priority Date Filing Date Title
KR1020197007877A KR102191884B1 (ko) 2017-09-30 2018-05-24 통신 방법 및 장치
BR112019007382A BR112019007382A2 (pt) 2017-09-30 2018-05-24 método de comunicação, aparelho, sistema, meio legível por computador e produto de programa de computador
JP2019517982A JP6849795B2 (ja) 2017-09-30 2018-05-24 通信方法および装置
AU2018322503A AU2018322503B2 (en) 2017-09-30 2018-05-24 Communication method and apparatus
EP18849392.8A EP3496432B1 (en) 2017-09-30 2018-05-24 Efficient multicast transmission
US16/376,327 US11251981B2 (en) 2017-09-30 2019-04-05 Communication method and apparatus

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN201710945904 2017-09-30
CN201710945904.5 2017-09-30
CN201810036433.0A CN109600721B (zh) 2017-09-30 2018-01-15 一种通信方法及装置
CN201810036433.0 2018-01-15

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/376,327 Continuation US11251981B2 (en) 2017-09-30 2019-04-05 Communication method and apparatus

Publications (1)

Publication Number Publication Date
WO2019062169A1 true WO2019062169A1 (zh) 2019-04-04

Family

ID=65900479

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/088256 WO2019062169A1 (zh) 2017-09-30 2018-05-24 一种通信方法及装置

Country Status (1)

Country Link
WO (1) WO2019062169A1 (zh)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101527641A (zh) * 2008-03-05 2009-09-09 华为技术有限公司 一种多媒体子系统中子会议的实现方法、控制方法及装置
US20150173107A1 (en) * 2013-12-18 2015-06-18 Motorola Solutions, Inc Method and apparatus for bearer control in a group call
CN105813025A (zh) * 2014-12-31 2016-07-27 华为技术有限公司 一种群组通信方法和服务器
EP3079383A1 (en) * 2015-04-08 2016-10-12 BlackBerry Limited Regrouping push-to-talk groups
US9510166B1 (en) * 2015-06-29 2016-11-29 Blackberry Limited Merging active group calls
WO2017004062A1 (en) * 2015-06-29 2017-01-05 Blackberry Limited Merging active group calls

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101527641A (zh) * 2008-03-05 2009-09-09 华为技术有限公司 一种多媒体子系统中子会议的实现方法、控制方法及装置
US20150173107A1 (en) * 2013-12-18 2015-06-18 Motorola Solutions, Inc Method and apparatus for bearer control in a group call
CN105813025A (zh) * 2014-12-31 2016-07-27 华为技术有限公司 一种群组通信方法和服务器
EP3079383A1 (en) * 2015-04-08 2016-10-12 BlackBerry Limited Regrouping push-to-talk groups
US9510166B1 (en) * 2015-06-29 2016-11-29 Blackberry Limited Merging active group calls
WO2017004062A1 (en) * 2015-06-29 2017-01-05 Blackberry Limited Merging active group calls

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3496432A4 *

Similar Documents

Publication Publication Date Title
CN109600721B (zh) 一种通信方法及装置
WO2020001572A1 (zh) 通信方法及装置
CN111526553B (zh) Ue执行的方法及ue、以及smf实体执行的方法及smf实体
CN111556539B (zh) Ue执行的方法及ue、以及smf实体执行的方法及smf实体
US11337040B2 (en) Broadcast bearer management method and device thereof
KR20200017504A (ko) 통신 모드 스위칭 방법, 네트워크 측 디바이스 및 단말 디바이스
JP2013511867A (ja) 通信ネットワークにおけるデータトラフィック制御
WO2019165882A1 (zh) 一种切片信息的获取方法和中继装置
KR20220159371A (ko) 멀티캐스트 또는 브로드캐스트 세션 확립 및 관리
US11252538B2 (en) Message sending method and device
WO2021109134A1 (zh) Mbms信息的获取、发送方法、终端设备及网元设备
CN110383940B (zh) 用于释放任务关键数据通信的方法、用户设备和服务器
CN109819530B (zh) 一种通信方法及装置
WO2019062169A1 (zh) 一种通信方法及装置
WO2021228191A1 (zh) 一种传输方式确定方法、装置、设备及存储介质
US20160197789A1 (en) Application management method and apparatus
WO2018126443A1 (zh) 管理广播承载的方法及其网络设备
CN111405615A (zh) 一种通信数据的传输方法、装置及存储介质
WO2021058035A1 (zh) 一种隧道复用方法和核心网设备
WO2022237500A1 (zh) 一种通信方法及装置
WO2023185690A1 (zh) 一种通信方法、装置及设备
KR20230000796A (ko) 무선 통신 시스템에서 mbs를 제어하는 방법 및 장치
KR20230009640A (ko) 무선 통신 시스템에서 mbs 세션에 연계된 pdu 세션의 처리 방법 및 장치

Legal Events

Date Code Title Description
ENP Entry into the national phase

Ref document number: 20197007877

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2019517982

Country of ref document: JP

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2018322503

Country of ref document: AU

Date of ref document: 20180524

Kind code of ref document: A

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112019007382

Country of ref document: BR

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

Ref document number: 18849392

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 112019007382

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20190411

NENP Non-entry into the national phase

Ref country code: DE