WO2017075792A1 - 小区多播业务处理方法以及设备 - Google Patents

小区多播业务处理方法以及设备 Download PDF

Info

Publication number
WO2017075792A1
WO2017075792A1 PCT/CN2015/093931 CN2015093931W WO2017075792A1 WO 2017075792 A1 WO2017075792 A1 WO 2017075792A1 CN 2015093931 W CN2015093931 W CN 2015093931W WO 2017075792 A1 WO2017075792 A1 WO 2017075792A1
Authority
WO
WIPO (PCT)
Prior art keywords
multicast service
base station
cell
service session
identifier
Prior art date
Application number
PCT/CN2015/093931
Other languages
English (en)
French (fr)
Inventor
李秉肇
王燕
高永强
张戬
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to CN201580084386.1A priority Critical patent/CN108353071B/zh
Priority to PCT/CN2015/093931 priority patent/WO2017075792A1/zh
Priority to EP15907634.8A priority patent/EP3361689B1/en
Publication of WO2017075792A1 publication Critical patent/WO2017075792A1/zh
Priority to US15/971,846 priority patent/US10587990B2/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
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • H04W68/005—Transmission of information for alerting of incoming communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/40—Connection management for selective distribution or broadcast

Definitions

  • the present invention relates to the field of communications, and in particular, to a cell multicast service processing method and device.
  • SC-PTM Single cell point to multipoint
  • the SC-PTM can be implemented in the area covered by the base station, and the base station only needs to send the multicast service data to the cell including the user equipment (UE) without transmitting the multicast service data to the cell not including the UE.
  • UE user equipment
  • the SC-PTM architecture includes: a Broadcast Multicast Service Center (BM-SC) 110, an MBMS Gateway (MBMS GateWay, MBMS-GW) 120, a Mobility Management Entity (MME) 130, and a multi-cell.
  • Multi-cell/multicast Coordination Entity (MCE) 140 Multi-cell/multicast Coordination Entity (MCE) 140, base station 150, and UE 160.
  • the BM-SC 110 is connected to the MBMS-GW 120
  • the MBMS-GW 120 is connected to the MME 130 and the base station 150, respectively.
  • the MME 130 is also connected to the MCE 140 and the base station 150, respectively.
  • the MCE 140 is also connected to the base station 150, and the base station 150 manages one or more cells. (not shown), base station 150 can communicate wirelessly with UE 160 within the cell.
  • the BM-SC 110 is omitted in FIG. It is assumed that the MCE 140 manages the base station 1 and the base station 2, the base station 1 manages the cell 1, the cell 2, and the cell 3, and the base station 2 manages the cell 4, the cell 5, and the cell 6.
  • the cell 1, the cell 2, the cell 3, the cell 4, and the cell 5 are cells that need to start multicast services.
  • the BM-SC 110 sends a first multicast service session initiation (MBMS Session Start) message to the MBMS-GW 120, where the first multicast service session initiation message includes a cell managed by the MBMS-GW 120 that needs to initiate a multicast service session. 1-5 logo.
  • MBMS Session Start a first multicast service session initiation
  • the MBMS-GW 120 After receiving the first multicast service session initiation message, the MBMS-GW 120 generates a second multicast service session initiation message according to the identifier of the cell in the first multicast service session initiation message, and sends a second multicast service session to the MME 130.
  • the start message wherein the second multicast service session initiation message includes an identifier of the cell 1-5 managed by the MME 130 that needs to initiate a multicast service session.
  • the MME 130 After receiving the second multicast service session initiation message, the MME 130 generates the identifier according to the cell in the second multicast service session initiation message.
  • the third multicast service session initiation message is sent to the MCE 140, where the third multicast service session initiation message includes the cells 1-5 managed by the MCE 140 that need to initiate the multicast service session.
  • logo After receiving the third multicast service session initiation message, the MCE 140 generates a fourth multicast service session initiation message and a fifth multicast service session initiation message for the base station 1 and the base station 2, respectively, where the fourth multicast service session initiation message is generated.
  • the identifier of the cell 1-3 that needs to be started by the base station 1 to start the multicast service session, and the fifth multicast service session initiation message includes the identifier of the cell 4-5 managed by the base station 2 that needs to initiate the multicast service session.
  • the base station 1 After receiving the fourth multicast service session initiation message, the base station 1 starts the multicast service of the cell 1-3 according to the identifier of the cell 1-3 in the fourth multicast service session initiation message. If one or more of the cells 1-3 start the multicast service successfully, the base station 1 returns a multicast service session start response (MBMS Session Start RSP) message to the MCE 140, if the cell 1-3 fails to start the multicast service ( MBMS Session Start failure), the base station 1 returns a multicast service session start failure message to the MCE 140.
  • MBMS Session Start RSP multicast service session start response
  • the base station 1 returns a multicast service session start failure message to the MCE 140.
  • the processing after the base station 2 receives the fifth multicast service session initiation message is similar to that of the base station 1, and the description will not be repeated here.
  • a multicast service session initiation response message is returned to the MME 130. If the MCE 140 receives the multicast service session initiation failure message returned by the base station 1 and the base station 2, a multicast service session initiation failure message is returned to the MME 130. If the MME 130 receives the multicast service session initiation response message, it transmits a multicast service session initiation response message to the MBMS-GW 120, and if the MME 130 receives the multicast service session initiation failure message, transmits the multicast to the MBMS-GW 120. Business session start failure message.
  • the MBMS-GW 120 If the MBMS-GW 120 receives the multicast service session initiation response message, it transmits a multicast service session initiation response message to the BM-SC 110, and if the MBMS-GW 120 receives the multicast service session initiation failure message, then to the BM-SC 110 sends a multicast service session start failure message.
  • the MCE 140 receives a multicast service session initiation response message, and the MCE 140 cannot know which specific cells are activated under the MCE 140 management.
  • the multicast service succeeds, and which cells fail to start the multicast service.
  • the technical problem to be solved by the embodiments of the present invention is to provide a cell multicast service processing method. And the device enables the MCE to know which cells initiate the multicast service successfully.
  • the first aspect provides a method for processing a cell multicast service, including:
  • the first base station sends a multicast service session initiation failure message or a multicast service session initiation response message to the MCE, where the multicast service session initiation failure message is used to indicate that the first base station needs to be started.
  • the cell initiating the multicast service fails to start the multicast service
  • the multicast service session initiation response message includes the identifier of the cell in the cell that needs to start the multicast service session that is initiated by the first base station to start the multicast service, and/ Or, the identifier of the cell that fails to start the multicast service in the cell that needs to start the multicast service session managed by the first base station.
  • the multicast service session initiation message further includes an identifier of a cell managed by the second base station that needs to initiate a multicast service session,
  • the first base station After the first base station receives the multicast service session start message sent by the MCE, before the first base station sends the multicast service session start failure message or the multicast service session start response message to the MCE, the first base station further includes:
  • the first base station starts the multicast service according to the identifier of the cell that needs to be started by the first base station to start the multicast service session, and acquires the cell managed by the second base station according to the identifier of the cell that needs to be activated by the second base station to start the multicast service session.
  • the situation in which the multicast service needs to be started is not limited.
  • the first base station After the first base station sends a multicast service session start failure message or a multicast service session start response message to the MCE, the first base station includes:
  • the first base station receives the MCE sent After the broadcast service session start message includes:
  • the second base station sends the identifier of the cell in the cell that needs to start the multicast service session that is initiated by the first base station to start the multicast service, and/or the cell that needs to start the multicast service session that is managed by the first base station The identity of the cell that failed to initiate the multicast service; or,
  • the method further includes:
  • the notification includes a bitmap indication bit, where the bitmap indication bit indicates the first base station and/or the A cell managed by the second base station to initiate a successful multicast service.
  • the second aspect provides a method for processing a cell multicast service, including:
  • the multicast cooperative entity MCE sends a first multicast service session initiation message to the first base station, where the first multicast service session initiation message includes an identifier of a cell managed by the first base station that needs to initiate a multicast service session;
  • a first multicast service session start failure message or a first multicast service session start response message where the first multicast service session start failure message is used to indicate the The cell initiated by the base station needs to start the multicast service session to start the multicast service, and the first multicast service session initiation response message includes the need to start the management of the first base station.
  • the first multicast service session initiation message further includes an identifier of a cell managed by the second base station that needs to initiate a multicast service session, where the method further include:
  • the MCE sends a second multicast service session initiation message to the second base station, where the second multicast service session initiation message includes an identifier of a cell managed by the second base station that needs to initiate a multicast service session;
  • the second base station Receiving, by the second base station, a second multicast service session initiation failure message or a second multicast service session initiation response message, where the second multicast service session initiation failure message is used to indicate the The cell initiated by the second base station that needs to start the multicast service session fails to start the multicast service, and the second multicast service session initiation response message includes the multicast initiated by the second base station to start the multicast service session.
  • the MCE receives the first multicast service session start failure message or the first multicast service that is returned by the first base station After the session start response message, it also includes:
  • the MCE sends, to the mobility management entity MME, at least one piece of information: the first base station manages and starts the multicast service.
  • the identity of the successful cell the identity of the first base station management and the failure to start the multicast service
  • the identity of the cell managed by the second base station and starting the multicast service the identity of the cell managed by the second base station and failing to start the multicast service logo.
  • the third aspect provides a method for processing a cell multicast service.
  • the multicast cooperative entity MCE determines whether the multicast service session initiation message sent by the received mobility management entity MME includes the multicast service that needs to be started. The identifier of the cell of the session; if not, the MCE sends a multicast service session initiation response message to the MME, where the multicast service session initiation response message includes a cell for indicating the multicast service session initiation message The list is not in the scope of MCE management.
  • the multicast service session initiation response message is a multicast service session initiation response message with an out of range flag, where the overrange flag is The field or bit set in the multicast service session initiation response message.
  • a fourth aspect provides a base station, where the base station is a first base station, and the first base station includes a receiver and a transmitter,
  • the receiver is configured to receive a multicast service session initiation message sent by a multicast cooperative entity (MCE), where the multicast service session initiation message includes an identifier of a cell that is required to be initiated by the first base station to initiate a multicast service session;
  • MCE multicast cooperative entity
  • the transmitter is configured to send a multicast service session initiation failure message or a multicast service session initiation response message to the MCE, where the multicast service session initiation failure message is used to indicate that the first base station manages to initiate a multicast service.
  • the cell in the session fails to start the multicast service
  • the multicast service session initiation response message includes the identifier of the cell in the cell that needs to start the multicast service session that is initiated by the first base station to start the multicast service, and/or the first The identity of the cell in the cell that needs to start the multicast service session initiated by the base station to start the multicast service failure.
  • the multicast service session initiation message further includes an identifier of a cell that is required to start a multicast service session managed by the second base station, where the base station further includes processing ,
  • the processor is configured to start a multicast service according to an identifier of a cell that is required to be started by the first base station to start a multicast service session, and acquire a cell managed by the second base station according to the identifier of the cell that needs to be started by the second base station to start the multicast service session. The situation in which the multicast service needs to be started.
  • the receiver is configured to receive, by the second base station, sent by the MCE, and start the multicast service succeeding.
  • the transmitter is configured to send, when the one or more cells managed by the first base station fail to initiate a multicast service, to the second base station to start the cell that is required to start a multicast service session managed by the first base station.
  • the transmitter is configured to send, to the second base station, an identifier of a cell that is successfully started to start a multicast service in a cell that needs to start a multicast service session that is managed by the first base station, and/or a need for the first base station management
  • the receiver is configured to receive the second base station Sending, by the second base station, the identifier of the cell that initiates the multicast service session in the cell that needs to initiate the multicast service session, and/or starting the multicast service in the cell that needs to start the multicast service session managed by the second base station The identity of the failed cell.
  • the transmitter is configured to send a notification to the user equipment UE, where the notification is used to manage the first base station
  • the cell that initiates the successful multicast service and/or the cell that initiates the multicast service managed by the second base station informs the UE.
  • the notification includes a bitmap indication bit, where the bitmap indication bit indicates the first base station and/or the A cell managed by the second base station to initiate a successful multicast service.
  • the fifth aspect provides a multicast cooperative entity MCE, including: a transmitter and a receiver,
  • the transmitter is configured to send a first multicast service session initiation message to the first base station, where the first multicast service session initiation message includes an identifier of a cell that is required to start a multicast service session managed by the first base station;
  • the receiver is configured to receive a first multicast service session initiation failure message or a first multicast service session initiation response message returned by the first base station, where the first multicast service session initiation failure message is used to indicate The cell initiated by the first base station that needs to start the multicast service session fails to start the multicast service, where the first multicast service session initiation response message includes the start of the cell managed by the first base station that needs to initiate the multicast service session.
  • the first multicast service session initiation message further includes an identifier of a cell that is required to start a multicast service session managed by the second base station,
  • the transmitter is configured to send a second multicast service session initiation message to the second base station, where the second multicast service session initiation message includes a second base station managed to initiate a multicast service session The identity of the cell;
  • the receiver is configured to receive a second multicast service session initiation failure message or a second multicast service session initiation response message returned by the second base station, where the second multicast service session initiation failure message is used to indicate
  • the cell initiated by the second base station that needs to start the multicast service session fails to start the multicast service
  • the second multicast service session initiation response message includes the start of the cell managed by the second base station that needs to initiate the multicast service session.
  • the transmitter is configured to send, to the first base station, an identifier of a cell that is managed by a second base station and that initiates a successful multicast service, and/or The identifier of the cell managed by the second base station and starting the multicast service failure.
  • the transmitter is configured to send, to the mobility management entity MME, at least one piece of information: the first base station manages and starts multiple The identifier of the cell that successfully broadcasts the service, the cell identifier that the first base station manages and fails to start the multicast service, the identifier of the cell that is managed by the second base station and that initiates the multicast service, and the failure of the second base station to manage the multicast service.
  • the identity of the cell is configured to send, to the mobility management entity MME, at least one piece of information: the first base station manages and starts multiple The identifier of the cell that successfully broadcasts the service, the cell identifier that the first base station manages and fails to start the multicast service, the identifier of the cell that is managed by the second base station and that initiates the multicast service, and the failure of the second base station to manage the multicast service.
  • the identity of the cell is configured to send, to the mobility management entity MME, at least one piece of information: the first base station manages and starts multiple The identifie
  • a sixth aspect provides a multicast cooperative entity MCE, where the MCE includes a processor and a transmitter,
  • the processor is configured to determine, in the multicast service session initiation message sent by the received mobility management entity MME, whether the identifier of the cell that is to be started by the MCE and that is to be started is included in the MCE management And sending, by the sender, a multicast service session initiation response message to the MME, where the multicast service session initiation response message includes, for indicating the multicast service, when the identifier of the cell of the multicast service session to be initiated is required.
  • the cell list in the session start message is not in the range of the MCE management.
  • the multicast service session initiation response message is a multicast service session initiation response message with an out of range flag, where the overrange flag is The field or bit set in the multicast service session initiation response message.
  • the multicast service session initiation response message returned by the present invention to the MCE includes the multicast service session initiation response message including the cell in the cell that needs to initiate the multicast service session managed by the first base station to start the multicast service successfully. Identification, and/or, the first base station management needs to be activated In the cell of the multicast service session, the identifier of the cell in which the multicast service fails is started. Therefore, the MCE can learn, according to the multicast service session initiation response message, that the multicast service initiated by the first base station to start the multicast service session is successful.
  • the identifier of the cell, and/or the identifier of the cell that fails to start the multicast service in the cell that needs to be started by the first base station determines which cells in the MCE 140 manage to initiate the multicast service successfully. Which cells failed to start the multicast service.
  • FIG. 1 is a schematic structural diagram of an SC-PTM architecture provided by the prior art
  • FIG. 2 is an interaction diagram of a multicast service through an SC-PTM architecture provided by the prior art
  • FIG. 3 is an interaction diagram of a multicast service through an SC-PTM architecture provided by the present invention.
  • FIG. 4 is an interaction diagram of another multicast service provided by the SC-PTM architecture provided by the present invention.
  • FIG. 5 is an interaction diagram of another multicast service provided by the SC-PTM architecture according to the present invention.
  • FIG. 6 is a schematic structural view of an MCE provided by the present invention.
  • FIG. 7 is a schematic structural diagram of a base station provided by the present invention.
  • FIG. 3 is an interaction diagram of a multicast service through an SC-PTM architecture provided by the present invention. Due to space limitations, the BM-SC 110 is omitted from FIG. It is assumed that the MCE 140 manages the base station 1 and the base station 2, the base station 1 manages the cell 1, the cell 2, and the cell 3, and the base station 2 manages the cell 4, the cell 5, and the cell 6. Among them, cell 1, cell 2, cell 3, cell 4, and cell 5 need to be started more. The cell of the broadcast service.
  • the base station 1 and the base station 2 are adjacent base stations under the management of the same MCE 140. In other embodiments, the base station 1 and the base station 2 may not be adjacent base stations.
  • the number of the base stations 150 managed by the MCE 140 and the number of cells managed by the base station 150 can be set according to factors such as the transmit power, environment, and requirements of the MCE 140 and the base station 150, and the number in this embodiment is only an example. , not limited.
  • the BM-SC 110 transmits a first multicast service session initiation (MBMS Session Start) message to the MBMS-GW 120.
  • the first multicast service session initiation message includes a quality requirement of the multicast service and an identifier of the cell 1-5 managed by the MBMS-GW 120 that needs to initiate the multicast service session.
  • the quality requirements of the multicast service include at least one of the following: a QoS Class Identifier (QCI), a guaranteed bit rate (GBR), a maximum bit rate (MBR), and a preemption retention priority ( Allocation and Retention Priority, ARP) and more.
  • the MBMS-GW 120 After receiving the first multicast service session initiation message, the MBMS-GW 120 generates a second multicast service session initiation message according to the identifier of the cell in the first multicast service session initiation message, and sends a second multicast service session to the MME 130. Start the message.
  • the second multicast service session initiation message includes the quality requirement of the multicast service and the identifier of the cell 1-5 managed by the MME 130 that needs to initiate the multicast service session.
  • the MME 130 After receiving the second multicast service session initiation message, the MME 130 generates a third multicast service session initiation message according to the identifier of the cell in the second multicast service session initiation message, and sends a third multicast service session start to the MCE 140. Message.
  • the third multicast service session initiation message includes a quality requirement of the multicast service and an identifier of the cell 1-5 managed by the MCE 140 that needs to initiate the multicast service session.
  • the MCE 140 After receiving the third multicast service session initiation message, the MCE 140 determines whether the cell identifier included in the third multicast service session initiation message is within the range managed by the MCE 140. If not within the scope managed by the MCE 140, the MCE 140 returns a multicast service session initiation response message without the cell identity to the MME 130 to indicate that the cell identity in the third multicast service session initiation message is not within the scope of the MCE management. It can be understood that the MCE 140 can also return the multicast service session initiation response information with the out of range flag to the MME 130 to indicate that the cell identity in the third multicast service session initiation message is not within the scope of the MCE management, and the like.
  • the overrange flag may be a field or a bit set in the multicast service session initiation response information.
  • the value in the field may be an artificially preset value, for example, the preset value is "0001", etc., and the overrange flag is set in the multicast service session start response information.
  • the value of this bit can be an artificially preset "0" or "1".
  • a fourth multicast service session initiation message and a fifth multicast service session initiation message are generated for the base station 1 and the base station 2, respectively.
  • the fourth multicast service session initiation message includes the quality requirement of the multicast service and the identity of the cell 1-3 managed by the base station 1 that needs to initiate the multicast service session
  • the fifth multicast service session initiation message includes the quality of the multicast service.
  • the base station 1 After receiving the fourth multicast service session initiation message, the base station 1 determines that the cell 1-3 needs to start the multicast service according to the identity of the cell that needs to be activated by the base station 1 in the cell list to start the multicast service session, and then determines that the multicast needs to be started. Whether the cell 1-3 of the service meets the quality requirements of the multicast service. According to whether the cell meets the quality requirements of the multicast service, it can be divided into two cases:
  • the base station 1 If at least one cell in the cell 1-3 is capable of initiating a multicast service that meets the quality requirements of the multicast service, the base station 1 starts the multicast service of the cell that can meet the quality requirement of the multicast service, and does not start.
  • the multicast service of the cell capable of meeting the quality requirements of the multicast service fails.
  • the base station 1 obtains the identifier of the cell that the base station 1 manages to start the multicast service successfully according to the situation in which the cell initiates the multicast service, and/or the identifier of the cell that the base station 1 manages to start the multicast service failure.
  • base station 1 initiates the multicast service of cell 1 and cell 2. Successfully, the multicast service of the cell 3 is started to fail.
  • the base station 1 obtains the identifier of the cell that the base station 1 successfully initiates the multicast service, that is, the identifier of the cell 1 and the identifier of the cell 2, and/or obtains the startup initiated by the base station 1 according to the situation in which the cell 1-3 starts the multicast service.
  • the identifier of the cell in which the broadcast service fails that is, the identifier of the cell 3.
  • the base station 1 encapsulates the identifier of the cell that the base station 1 manages to start the multicast service and/or the identifier of the cell that the base station 1 manages to initiate the multicast service failure into the first multicast service session initiation response message, and sends the message to the MCE. 140 sends a first multicast service session initiation response message.
  • the first multicast session initiation response message may also carry the failure reason of the cell that fails to start the multicast industry, for example, the resource is unavailable, the requested QCI (QoS Class Identifier), or the illegal QoS is not supported. A combination of one or more of Quality of Service and the like.
  • the base station 1 The MCE 140 sends a first multicast service session initiation failure message, where the first multicast service session initiation failure message may carry or not carry the identifier of the cell that the base station 1 manages to start the multicast service failure. If the first multicast service session start failure message does not carry the identifier of the cell that fails to start the multicast service managed by the base station 1, the MCE 140 receives the first multicast service session start failure message sent by the base station 1, and the default base station 1 The managed cell that needs to start the multicast service fails to start the multicast service.
  • the base station 1 encapsulates the identifier of the cell that the base station 1 manages to initiate the multicast service failure to the first multicast.
  • the business session starts in the failure message.
  • the base station 1 may further include, in the first multicast service session initiation failure message, a failure reason for starting a cell in which the multicast industry fails, for example, the resource is unavailable, the requested QCI is not supported, or the illegal Qos is used.
  • a failure reason for starting a cell in which the multicast industry fails for example, the resource is unavailable, the requested QCI is not supported, or the illegal Qos is used.
  • the processing after the base station 2 receives the fifth multicast service session initiation message sent by the MCE 140 is similar to that of the base station 1, and the description will not be repeated here.
  • the MCE 140 receives the messages returned by the base station 1 and the base station 2. According to the difference between the messages received by the MCE 140 and the base station 1 and the base station 2, there are four cases:
  • the first multicast service session initiation response message returned by the base station 1 may initiate a response.
  • the message obtains the identity of the cell managed by the base station 1 and initiates the successful multicast service.
  • the MCE 140 starts the cell of the multicast service according to the needs managed by the base station 1.
  • the identifier of the cell managed by the base station 1 and the multicast service failure is started, and the identifier of the cell managed by the base station 1 and the multicast service is started is obtained.
  • the MCE 140 learns that the cell that needs to be started by the base station 2 to start the multicast service fails to start the multicast service.
  • the MCE 140 obtains the identifier of the cell managed by the MCE 140 (including the management of the base station 1 and the base station 2) and starts the multicast service, and/or the identifier of the cell managed by the MCE 140 and fails to start the multicast service, and Encapsulating the identity of the cell managed by the MCE 140 and starting the multicast service and/or the identity of the cell managed by the MCE 140 and initiating the multicast service failure into the second multicast service session initiation response message, and transmitting the message to the MME 130
  • the second multicast service session initiates a response message.
  • the MCE 140 learns that the cell managed by the base station 1 needs to start the multicast service.
  • the multicast service failed. If the first multicast service session initiation response message returned by the base station 2 carries the identity of the cell managed by the base station 2 and the multicast service is successful, the MCE 140 receives the first multicast service session initiation response message returned by the base station 2 Obtaining, from the first multicast service session initiation response message returned by the base station 2, the identifier of the cell managed by the base station 2 and starting the multicast service is successful. If the first multicast service session initiation response message returned by the base station 2 carries the identity of the cell managed by the base station 2 and the multicast service fails, the MCE 140 starts the identity of the cell of the multicast service according to the needs managed by the base station 2.
  • the identifier of the cell managed by the base station 2 and starting the multicast service failure is obtained, and the identifier of the cell managed by the base station 2 and the multicast service is started is obtained.
  • the MCE 140 obtains the identity of the cell managed by the MCE 140 (including the management of the base station 1 and the base station 2) and initiates the multicast service, and/or the identity of the cell managed by the MCE 140 and fails to initiate the multicast service, and
  • the identity of the cell managed by the MCE 140 (including the management of the base station 1 and the base station 2) and initiating the multicast service success and/or the identity of the cell managed by the MCE 140 and initiating the multicast service failure is encapsulated into the second multicast service session initiation.
  • a second multicast service session initiation response message is sent to the MME 130.
  • the first multicast service session initiation response message returned by the base station 1 may initiate a response.
  • the message obtains the identity of the cell managed by the base station 1 and initiates the successful multicast service.
  • the MCE 140 starts the cell of the multicast service according to the needs managed by the base station 1.
  • the identifier of the cell managed by the base station 1 and the multicast service failure is started, and the identifier of the cell managed by the base station 1 and the multicast service is started is obtained. If the first multicast service session initiation response message returned by the base station 2 carries the identity of the cell managed by the base station 2 and the multicast service is successful, the MCE 140 receives the first multicast service session initiation response message returned by the base station 2 Obtaining, from the first multicast service session initiation response message returned by the base station 2, the identifier of the cell managed by the base station 2 and starting the multicast service is successful.
  • the MCE 140 starts the identity of the cell of the multicast service according to the needs managed by the base station 2.
  • the identifier of the cell managed by the base station 2 and starting the multicast service failure is obtained, and the identifier of the cell managed by the base station 2 and the multicast service is started is obtained.
  • the MCE 140 aggregates the identifier of the cell managed by the base station 1 and the cell that initiates the multicast service with the identity of the cell managed by the base station 2 and initiates the multicast service success, and/ Or, the identifiers of the cells managed by the base station 1 and failing to start the multicast service are aggregated with the identifiers of the cells managed by the base station 2 and the multicast service fails, to be managed by the MCE 140 (including the base station 1 and the base station 2) The identity of the cell that is managed and that initiates the success of the multicast service and/or the identity of the cell managed by the MCE 140 and that initiates the failure of the multicast service.
  • the MCE 140 encapsulates the identity of the cell managed by the MCE 140 (including the management of the base station 1 and the base station 2) and the cell that initiated the multicast service and/or the identity of the cell that the MCE 140 manages and initiates the failure of the multicast service to the second multicast.
  • the service session initiates a response message and sends a second multicast service session initiation response message to the MME 130.
  • the MCE 140 After receiving the first multicast service session failure response message returned by the base station 1, the MCE 140 learns that the cell that needs to be started by the base station 1 to start the multicast service fails to start the multicast service. After receiving the first multicast service session failure response message returned by the base station 2, the MCE 140 learns that the cell that needs to be started by the base station 2 to start the multicast service fails to start the multicast service. Therefore, the MCE 140 generates a second multicast service session failure response message and transmits a second multicast service session failure response message to the MME 130.
  • the MME 130 receives the second multicast service session initiation response message, it is managed according to the identity of the cell managed by the MCE 140 in the second multicast service session initiation response message and the multicast service is initiated and/or managed by the MCE 140.
  • the identifier of the cell that failed to start the multicast service generates a third multicast service session initiation response message, and sends a third multicast service session initiation response message to the MBMS-GW 120.
  • the MME 130 receives the second multicast service session initiation failure message, generates a third multicast service session failure response message according to the second multicast service session initiation failure message, and sends a third multicast service session to the MBMS-GW 120. Start failure message.
  • the identity and/or MCE 140 management of the cell managed by the MCE 140 in the third multicast service session initiation response message and the multicast service is initiated is successful. And identifying the cell that failed the multicast service to generate a fourth multicast service session initiation response message, and transmitting a fourth multicast service session initiation response message to the BM-SC 110. If the MBMS-GW 120 receives the fourth multicast service session initiation failure message, generates a fourth multicast service session failure response message according to the fourth multicast service session initiation failure message, and sends the fourth multicast to the BM-SC 110. Business session start failure message.
  • the first to fifth multicast service session initiation messages further include an identifier of the multicast service.
  • the base station 1 After receiving the fourth multicast service session initiation message, the base station 1 starts the multicast service corresponding to the identifier of the multicast service for the cell 1-3.
  • the base station 2 After receiving the fifth multicast service session initiation message, the base station 2 starts the multicast service corresponding to the identifier of the multicast service for the cells 4 and 5.
  • the multicast service session initiation response message returned by the present invention to the MCE includes the multicast service session initiation response message including the cell in the cell that needs to initiate the multicast service session managed by the first base station to start the multicast service successfully. And the identifier of the cell that fails to start the multicast service in the cell that needs to start the multicast service session that is managed by the first base station, so that the MCE can learn the needs of the first base station management according to the multicast service session initiation response message.
  • the embodiment shown in FIG. 4 is different from the embodiment shown in FIG. 3 in that the fourth multicast service session initiation message sent by the MCE 140 to the base station 1 further includes the need to start the management managed by the base station 2. Identification of cell 4 and cell 5 of the multicast service.
  • the fifth multicast service session initiation message sent by the MCE 140 to the base station 2 further includes the identifier of the cell 1-3 managed by the base station 1 that needs to start the multicast service. Or, when the identifiers are organized in the form of a list, the one of the fourth multicast service session initiation messages sent by the MCE 140 to the base station 1 is composed of the identifiers of the cells 1-3 including the base station 1 that need to initiate the multicast service.
  • the cell list 2 further includes another cell list composed of the identifiers of the cell 4 and the cell 5 that are required to start the multicast service, and the fifth multicast service session start message sent by the MCE 140 to the base station 2 includes the base station. 2, in addition to a cell list composed of the identifiers of the cell 4 and the cell 5 that need to start the multicast service, and another cell list composed of the identifiers of the cells 1-3 that need to be activated by the base station 1 to start the multicast service.
  • the base station 1 After receiving the fourth multicast service session initiation message sent by the MCE 140, the base station 1 acquires the cell needs managed by the base station 2 according to the identity of the cell managed by the base station 2 and needs to start the multicast service session in the fourth multicast service session initiation message. When the multicast service is started, it is known that the cell 4 and the cell 5 in the base station 2 need to start the multicast service. After receiving the fifth multicast service session initiation message sent by the MCE 140, the base station 2 acquires the cell needs managed by the base station 1 according to the identity of the cell managed by the base station 1 and needs to start the multicast service session in the fifth multicast service session initiation message. When the multicast service is started, it is known that the cell 1-3 in the base station 1 needs to start the multicast service.
  • the MCE 140 encapsulates the identifiers of the cell 1, the cell 2, and the cell 4 and/or the identifiers of the cell 3 and the cell 5 into a multicast service session update message or initiates a multicast service successful cell notification. The message is sent to the base station 1 and the base station 2.
  • the multicast service session update message may further include indication information, where the indication information is used to indicate that the cell identifier in the multicast service session update message is an identifier and/or an MCE of the cell managed by the MCE 140 and the multicast service is started successfully.
  • the base station 1 since the base station 1 already knows the identity of the cell in which the multicast service is successfully started in the cell that it manages, the multicast service session update message sent by the MCE 140 to the base station 1 or the start of the multicast service success cell notification message only needs to be included.
  • the identifier of the cell managed by the base station 2 and starting the multicast service is successful and/or the identity of the cell managed by the base station 2 and starting the multicast service failure.
  • the base station 1 After receiving the multicast service session update message or starting the multicast service success cell notification message, the base station 1 can know that the cell 4 needs to start the multicast service, the cell 4 starts the multicast service successfully, and the cell 5 starts the multicast. Business failed. Then, the base station 1 sends a notification to the user equipment in the cell managed by the base station 1, wherein the base station 1 is notified to inform the base station of the cell that successfully initiates the multicast service managed by the base station 1 and/or the cell that initiates the multicast service managed by the base station 2.
  • the UE in the managed cell enables the UE to know which cells managed by the base station 1 and/or the base station 2 have started the multicast service, so that if the UE moves to the base station 1 and/or the base station 2 manages the startup during the mobile process, When the cell that successfully broadcasts the service is received, the multicast service is directly received, or if the mobile device to the base station 1 and/or the base station 2 fails to start the multicast service or does not have the cell that starts the multicast service, it is determined as soon as possible whether the unicast needs to be started. Hosted to continue accepting multicast services.
  • the message of the cell that initiates the multicast service success may be the identifier of the cell that initiates the multicast service success, or may be the identifier of the cell that initiates the multicast service success expressed in other forms.
  • the identity of the cell that initiates the successful multicast service may also be represented by a bitmap indication sequence, wherein the bitmap indication sequence includes a plurality of bits, the bitmap indicates the bit of the sequence and the identity of the cell managed by the base station 1 and/or the base station
  • the identifier of the managed cell corresponds to the value of the bit of the bitmap indication sequence, which is used to indicate which of the cells indicated by the identifier of the corresponding cell initiates the multicast service.
  • Table 1 As shown in Table 1,
  • the first row in Table 1 is the identifier of the cell managed by the base station 1 and the base station 2.
  • the second row in Table 1 is a bitmap indication sequence 110100 of the multicast traffic with the multicast service identity being the service identity 1.
  • the value of the bit in the bitmap indication sequence is 1, it indicates that the cell represented by the corresponding cell identifier initiates the multicast service successfully.
  • the value of the bit in the bitmap indication sequence is 0, it indicates the cell represented by the corresponding cell identifier.
  • the bitmap indication sequence 110100 indicates that the multicast service whose multicast service identifier is the service identifier 1 is successfully started in the cell 1, the cell 2, and the cell 4, and the cell 3 and the cell 6 fail to start or do not start the multicast service.
  • each multicast service can be represented by the same bitmap indication sequence, thereby replacing the identifier of each transmitting cell with a bitmap indication sequence, thereby reducing waste of transmission resources.
  • the processing procedure of the base station 2 is similar to that of the base station 1, and the description will not be repeated here.
  • the embodiment shown in FIG. 5 differs from the embodiment shown in FIG. 4 in that the MCE 140 does not need to pass the identity and/or MCE 140 management of the cell managed to the MCE 140 and initiates the successful multicast service. And the identifier of the cell that fails the multicast service is started to inform the base station 1 and the base station 2 which cells initiate the multicast service success, and which cells initiate the multicast service failure, and instead:
  • the base station 1 After starting the multicast service of the cell, the base station 1 transmits, to the base station 2, the identifier of the cell managed by the base station 1 and starting the multicast service, and/or the identifier of the cell managed by the base station 1 and starting the multicast service failure. Or, after the base station 1 starts the multicast service of the cell, if one or more cells managed by the base station 1 If the multicast service fails, the identifier of the cell managed by the base station 1 and starting the multicast service is successfully sent to the base station 2 and/or the identifier of the cell managed by the base station 1 and the multicast service is started, if the cell managed by the base station 1 is started.
  • the identifier of the cell managed by the base station 1 and the success of the multicast service is not sent to the base station 2 and/or the identifier of the cell managed by the base station 1 and the multicast service is failed to be started. If the identifier of the cell managed by the base station 1 and the cell that successfully initiates the multicast service is not received, and the identifier of the cell managed by the base station 1 and the multicast service fails to be started, the fifth multicast service session is passed by default. The cell that needs to start the multicast service managed by the base station 1 successfully starts the multicast service to save the transmission resources.
  • the base station 1 also receives the identity of the cell managed by the base station 2 and activated by the base station 2 and the cell that is activated by the base station 2 and/or the identity of the cell managed by the base station 2 and which fails to start the multicast service, and is transmitted according to the base station 2
  • the identifier of the cell that is managed and that successfully initiates the multicast service and/or the identifier of the cell that is managed by the base station 2 and that fails to start the multicast service acquires the identifier of the cell that successfully starts the multicast service in the cell managed by the base station 2, thereby obtaining the identity Among the cells managed by the base station 2, which cells start the multicast service successfully, and which start the multicast service fails.
  • the processing procedure of the base station 2 is similar to that of the base station 1, and the description will not be repeated here.
  • the identifier may be organized in the form of a list or a bitmap to facilitate the transmission.
  • FIG. 6 is a schematic structural diagram of an MCE provided by the present invention.
  • the MCE 600 of this embodiment includes a processor 601, a memory 602, a transmitter 603, and a receiver 604.
  • the processor 601, the memory 602, the transmitter 603, and the receiver 604 are connected by a bus.
  • the processor 601 can be a central processing unit (CPU), a network processor (in English: network processor, NP), a hardware chip, or any combination thereof.
  • the hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof.
  • ASIC application-specific integrated circuit
  • PLD programmable logic device
  • the above PLD can be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), and a general array logic (GAL). Or any combination thereof.
  • the memory 602 can be used to store software programs and modules, and the processor 601 executes various functional applications and data processing by running software programs and modules stored in the memory 602.
  • the memory 602 can mainly include a storage program area and a storage data area, wherein the storage program area can store an operating system, At least one function required application (such as sound playback function, image playback function, etc.); the storage data area can store data created according to the use of the MCE 600, and the like.
  • memory 602 can include high speed random access memory, and can also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device. Accordingly, memory 602 can also include a memory controller to provide processor 601 access to memory 602.
  • Transmitter 603 and receiver 604 can be independent. It can also be brought together.
  • the transmitter 603 and the receiver 604 can transmit a wireless signal transmission signal to other devices through an antenna, and can also transmit optical signals to other devices through an optical fiber.
  • the transmitter 603 and the receiver 604 transmit wireless signal transmission signals to other devices through the antenna
  • the transmitter 603 and the receiver 604 include a resonator, a modem, an amplifier, and the like.
  • the transmitter 603 and the receiver 604 transmit optical signals to other devices through the optical fiber
  • the transmitter 603 and the receiver 604 include optical couplers, optical modems, amplifiers, and the like.
  • the MCE 600 when executed, executes one or more programs stored in the memory 602 by one or more processors for instructions to:
  • the transmitter 603 sends a first multicast service session initiation message to the first base station, where the first multicast service session initiation message includes an identifier of a cell managed by the first base station that needs to initiate a multicast service session;
  • the receiver 604 receives the first multicast service session initiation failure message or the first multicast service session initiation response message returned by the first base station, where the first multicast service session initiation failure message is used to indicate The cell initiated by the first base station that needs to start the multicast service session fails to start the multicast service, where the first multicast service session initiation response message includes the start of the cell managed by the first base station that needs to initiate the multicast service session.
  • the first multicast service session initiation message further includes an identifier of a cell managed by the second base station that needs to initiate a multicast service session, where
  • the transmitter 603 is configured to send a second multicast service session initiation message to the second base station, where the second multicast service session initiation message includes a cell managed by the second base station that needs to initiate a multicast service session.
  • the receiver 604 is configured to receive a second multicast service session start loss returned by the second base station
  • the failure message or the second multicast service session initiation response message wherein the second multicast service session initiation failure message is used to indicate that the cell that needs to start the multicast service session managed by the second base station fails to start the multicast service
  • the second multicast service session initiation response message includes an identifier of a cell in the cell that needs to initiate a multicast service session that is initiated by the second base station to start a multicast service, and/or is managed by the second base station. The identifier of the cell in which the multicast service fails to start the multicast service session.
  • the transmitter 603 is configured to send, to the first base station, an identifier of a cell that is managed by the second base station and that initiates the multicast service, and/or that is managed by the second base station, and initiates the multicast service. The identity of the failed cell.
  • the transmitter 603 is configured to send, to the mobility management entity MME, at least one piece of information: an identifier of a cell managed by the first base station and starting a multicast service success, a cell that is managed by the first base station, and fails to start the multicast service. And identifying, by the second base station, an identifier of a cell that is successful in starting the multicast service, and an identifier of a cell that is managed by the second base station and that fails to start the multicast service.
  • the processor 601 is configured to determine, in the multicast service session initiation message sent by the received mobility management entity MME, whether the identifier of the cell that is to be initiated by the MCE and that needs to be started is included in the multicast service session initiation message,
  • the transmitter 603 is configured to send a multicast service session initiation response message to the MME, where the identifier of the cell that is to be initiated by the MCE and needs to be initiated, and the multicast service session initiation response message is included.
  • the indication information indicating that the cell list in the multicast service session initiation message is not within the scope of the MCE management.
  • the multicast service session initiation response message is a multicast service session initiation response message with an out of range flag, where the overrange flag is a field or a bit set in the multicast service session initiation response information.
  • the multicast service session initiation response message returned by the present invention to the MCE includes the multicast service session initiation response message including the cell in the cell that needs to initiate the multicast service session managed by the first base station to start the multicast service successfully. And the identifier of the cell that fails to start the multicast service in the cell that needs to start the multicast service session that is managed by the first base station, so that the MCE can learn the needs of the first base station management according to the multicast service session initiation response message.
  • FIG. 7 is a schematic structural diagram of a base station provided by the present invention.
  • the base station 700 of this embodiment includes a processor 701, a memory 702, a transmitter 703, and a receiver 704.
  • the processor 701, the memory 702, the transmitter 703, and the receiver 704 are connected by a bus.
  • the processor 701 can be a central processing unit (CPU), a network processor (in English), a hardware chip, or any combination thereof.
  • the hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof.
  • ASIC application-specific integrated circuit
  • PLD programmable logic device
  • the above PLD can be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), and a general array logic (GAL). Or any combination thereof.
  • the memory 702 can be used to store software programs and modules, and the processor 701 executes various functional applications and data processing by running software programs and modules stored in the memory 702.
  • the memory 702 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application required for at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may be stored according to The data created by the use of the base station 700, and the like.
  • memory 702 can include high speed random access memory, and can also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device. Accordingly, memory 702 can also include a memory controller to provide processor 701 access to memory 702.
  • Transmitter 703 and receiver 704 can be independent. It can also be brought together.
  • the transmitter 703 and the receiver 704 can transmit a wireless signal transmission signal to other devices through an antenna, and can also transmit optical signals to other devices through an optical fiber.
  • the transmitter 703 and the receiver 704 transmit wireless signal transmission signals to other devices through the antenna
  • the transmitter 703 and the receiver 704 include a resonator, a modem, an amplifier, and the like.
  • the transmitter 703 and the receiver 704 transmit optical signals to other devices through the optical fiber
  • the transmitter 703 and the receiver 704 include an optical coupler, an optical modem, an amplifier, and the like.
  • the base station 700 when executed, executes one or more programs stored in the memory 702 by one or more processors for instructions to:
  • the receiver 704 is configured to receive a multicast service session initiation message sent by the multicast cooperation entity MCE, where the multicast service session initiation message includes a need to start multicasting managed by the first base station The identity of the cell of the service session;
  • the transmitter 703 is configured to send a multicast service session initiation failure message or a multicast service session initiation response message to the MCE, where the multicast service session initiation failure message is used to indicate that the first base station management needs to be started.
  • the cell-initiated multicast service of the broadcast service session fails, and the multicast service session start response message includes the identifier of the cell in the cell that needs to start the multicast service session that is initiated by the first base station to start the multicast service, and/or The identifier of the cell in which the multicast service fails to start the multicast service in the cell managed by the first base station.
  • the multicast service session initiation message further includes an identifier of a cell managed by the second base station that needs to initiate a multicast service session, where
  • the processor 701 is configured to start a multicast service according to an identifier of a cell that is required to be started by the first base station to start a multicast service session, and obtain a second base station management according to the identifier of the cell that needs to be started by the second base station to start the multicast service session.
  • the cell needs to start the multicast service.
  • the receiver 704 is configured to receive, by the MCE, an identifier of a cell that is managed by a second base station and that initiates a multicast service, and/or that is managed by the second base station, and that fails to start the multicast service.
  • the identity of the cell is configured to receive, by the MCE, an identifier of a cell that is managed by a second base station and that initiates a multicast service, and/or that is managed by the second base station, and that fails to start the multicast service. The identity of the cell.
  • the transmitter 703 is configured to: when the one or more cells managed by the first base station fail to initiate the multicast service, send, to the second base station, the first base station to manage the multicast service that needs to be initiated.
  • the transmitter 703 is configured to send, to the second base station, an identifier of a cell in the cell that needs to initiate a multicast service session that is initiated by the first base station to start a multicast service, and/or the first base station management The identifier of the cell in which the multicast service fails to start the multicast service session.
  • the receiver 704 is configured to receive, by the second base station, an identifier of a cell in the cell that needs to initiate a multicast service session that is initiated by the second base station to start a multicast service, and/or the The identifier of the cell in which the multicast service fails to start the multicast service in the cell managed by the second base station.
  • the sender 703 is configured to send a notification to the user equipment UE, where the notification is used to start the cell managed by the first base station and/or the second base station managed by the second base station.
  • the cell that successfully broadcasts the service informs the UE.
  • the notification includes a bitmap indication bit, the bitmap indication bit indicating the first base station and/or Or a cell managed by the second base station to start the multicast service successfully.
  • the multicast service session initiation response message returned by the present invention to the MCE includes the multicast service session initiation response message including the cell in the cell that needs to initiate the multicast service session managed by the first base station to start the multicast service successfully. And the identifier of the cell that fails to start the multicast service in the cell that needs to start the multicast service session that is managed by the first base station, so that the MCE can learn the needs of the first base station management according to the multicast service session initiation response message.
  • the storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).

Landscapes

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

Abstract

本发明公开了一种小区多播业务处理方法以及设备，包括：第一基站接收多播协作实体MCE发送的多播业务会话启动消息，其中，多播业务会话启动消息包括第一基站管理的需要启动多播业务会话的小区的标识；第一基站向MCE发送多播业务会话启动失败消息或者多播业务会话启动响应消息，其中，多播业务会话启动失败消息用于表示第一基站管理的需要启动多播业务会话的小区启动多播业务均失败，多播业务会话启动响应消息包含第一基站管理的需要启动多播业务会话的小区中启动多播业务成功的小区的标识，和/或，第一基站管理的需要启动多播业务会话的小区中启动多播业务失败的小区的标识。上述方法能够使MCE获知哪些小区启动多播业务成功。

Description

小区多播业务处理方法以及设备 技术领域
本发明涉及通信领域，尤其涉及一种小区多播业务处理方法以及设备。
背景技术
单小区点到多点(Single cell point to multipoint，SC-PTM)是一种多播传输技术。SC-PTM能够实现在基站覆盖的区域内，基站只需向包含用户设备(user equipment，UE)的小区发送多播业务数据，而无需向不包含UE的小区发送多播业务数据。
如图1所示，SC-PTM架构包括：广播多播业务中心(BM-SC)110，MBMS网关(MBMS GateWay，MBMS-GW)120，移动管理实体(Mobility Management Entity，MME)130，多小区/多播协调实体(Multi-cell/multicast Coordination Entity，MCE)140、基站150以及UE 160。其中，BM-SC 110连接MBMS-GW 120，MBMS-GW 120分别连接MME 130以及基站150，MME 130还分别连接MCE 140以及基站150，MCE 140还连接基站150，基站150管理一个或者多个小区(图未示)，基站150可以与小区内的UE 160进行无线通信。
请一并参阅图2，由于篇幅所限，图2中省略了BM-SC 110。现假设MCE 140管理基站1以及基站2，基站1管理小区1、小区2和小区3，基站2管理小区4、小区5以及小区6。其中，小区1、小区2、小区3、小区4和小区5为需要启动多播业务的小区。BM-SC 110向MBMS-GW 120发送第一多播业务会话启动(MBMS Session Start)消息，其中，第一多播业务会话启动消息中包含MBMS-GW 120管理的需要启动多播业务会话的小区1-5的标识。MBMS-GW 120接收到第一多播业务会话启动消息后，根据第一多播业务会话启动消息中小区的标识生成第二多播业务会话启动消息，并向MME 130发送第二多播业务会话启动消息，其中，第二多播业务会话启动消息中包含MME 130管理的需要启动多播业务会话的小区1-5的标识。MME 130接收到第二多播业务会话启动消息后，根据第二多播业务会话启动消息中的小区的标识生成 第三多播业务会话启动消息，并向MCE 140发送第三多播业务会话启动消息，其中，第三多播业务会话启动消息中包含MCE 140管理的需要启动多播业务会话的小区1-5的标识。MCE 140接收到第三多播业务会话启动消息后，分别为基站1以及基站2生成第四多播业务会话启动消息以及第五多播业务会话启动消息，其中，第四多播业务会话启动消息包含基站1管理的需要启动多播业务会话的小区1-3的标识，第五多播业务会话启动消息包含基站2管理的需要启动多播业务会话的小区4-5的标识。基站1在接收到第四多播业务会话启动消息后，根据第四多播业务会话启动消息中的小区1-3的标识启动小区1-3的多播业务。如果小区1-3中的一个或者多个启动多播业务成功，则基站1向MCE 140返回多播业务会话启动响应(MBMS Session Start RSP)消息，如果小区1-3均启动多播业务失败(MBMS Session Start failure)，则基站1向MCE 140返回多播业务会话启动失败消息。基站2在接收到第五多播业务会话启动消息后的处理与基站1类似，此处不再展开描述。如果MCE 140接收到基站1和/或基站2返回的多播业务会话启动响应消息，则向MME 130返回多播业务会话启动响应消息。如果MCE 140接收到基站1和基站2返回的多播业务会话启动失败消息，则向MME 130返回多播业务会话启动失败消息。如果MME 130接收到多播业务会话启动响应消息，则向MBMS-GW 120发送多播业务会话启动响应消息，如果MME 130接收到多播业务会话启动失败消息，则向MBMS-GW 120发送多播业务会话启动失败消息。如果MBMS-GW 120接收到多播业务会话启动响应消息，则向BM-SC 110发送多播业务会话启动响应消息，如果MBMS-GW 120接收到多播业务会话启动失败消息，则向BM-SC 110发送多播业务会话启动失败消息。
所以，在现有技术中，无论MCE 140管理下多少个小区启动多播业务成功，MCE 140都是收到一个多播业务会话启动响应消息，MCE 140无法知道MCE 140管理下具体哪些小区启动了多播业务成功，哪些小区启动多播业务失败。
发明内容
本发明实施例所要解决的技术问题在于，提供一种小区多播业务处理方法 以及设备，能够使MCE获知哪些小区启动多播业务成功。
第一方面提供了一种小区多播业务处理方法，包括：
第一基站接收多播协作实体MCE发送的多播业务会话启动消息，其中，所述多播业务会话启动消息包括所述第一基站管理的需要启动多播业务会话的小区的标识；
所述第一基站向所述MCE发送多播业务会话启动失败消息或者多播业务会话启动响应消息，其中，所述多播业务会话启动失败消息用于表示所述第一基站管理的需要启动多播业务会话的小区启动多播业务均失败，所述多播业务会话启动响应消息包含所述第一基站管理的需要启动多播业务会话的小区中启动多播业务成功的小区的标识，和/或，所述第一基站管理的需要启动多播业务会话的小区中启动多播业务失败的小区的标识。
结合第一方面，第一方面的第一种可能的实施方式中，所述多播业务会话启动消息还包括第二基站管理的需要启动多播业务会话的小区的标识，
所述第一基站接收MCE发送的多播业务会话启动消息之后，所述第一基站向所述MCE发送多播业务会话启动失败消息或者多播业务会话启动响应消息之前，还包括：
所述第一基站根据第一基站管理的需要启动多播业务会话的小区的标识启动多播业务，并根据第二基站管理的需要启动多播业务会话的小区的标识获取第二基站管理的小区需要启动多播业务的情况。
结合第一方面的第一种可能的实施方式，第一方面的第二种可能的实施方式中，
所述第一基站向所述MCE发送多播业务会话启动失败消息或者多播业务会话启动响应消息之后包括：
接收所述MCE发送的第二基站管理的，且启动多播业务成功的小区的标识，和/或第二基站管理的，且启动多播业务失败的小区的标识。
结合第一方面或第一方面的第一种可能的实施方式或第一方面的第二种可能的实施方式，第一方面的第三种可能的实施方式中，第一基站接收MCE发送的多播业务会话启动消息之后包括：
如果所述第一基站管理的一个或者多个小区启动多播业务失败，则向所述 第二基站发送所述第一基站管理的需要启动多播业务会话的小区中启动多播业务成功的小区的标识，和/或，所述第一基站管理的需要启动多播业务会话的小区中启动多播业务失败的小区的标识；或，
向所述第二基站发送所述第一基站管理的需要启动多播业务会话的小区中启动多播业务成功的小区的标识，和/或，所述第一基站管理的需要启动多播业务会话的小区中启动多播业务失败的小区的标识。
结合第一方面或第一方面的第一种至第三种可能的实施方式中的任意一种，第一方面的第四种可能的实施方式中，所述方法还包括：
接收所述第二基站发送的第二基站管理的需要启动多播业务会话的小区中启动多播业务成功的小区的标识，和/或，所述第二基站管理的需要启动多播业务会话的小区中启动多播业务失败的小区的标识。
结合第一方面的第四种可能的实施方式，第一方面的第五种可能的实施方式中，接收多播协作实体MCE发送的多播业务会话启动消息，以及，接收所述第二基站发送的第二基站管理的需要启动多播业务会话的小区中启动多播业务成功的小区的标识，和/或，所述第二基站管理的需要启动多播业务会话的小区中启动多播业务失败的小区的标识之后，还包括：
向用户设备UE发送通知，所述通知用于将所述第一基站管理的启动多播业务成功的小区和/或所述第二基站管理的启动多播业务成功的小区告知所述UE。
结合第一方面的第五种可能的实施方式，第一方面的第六种可能的实施方式中，所述通知中包含位图指示位，所述位图指示位指示第一基站和/或第二基站管理的启动多播业务成功的小区。
第二方面提供了一种小区多播业务处理方法，包括：
多播协作实体MCE向第一基站发送第一多播业务会话启动消息，其中，所述第一多播业务会话启动消息包括所述第一基站管理的需要启动多播业务会话的小区的标识；
所述MCE接收所述第一基站返回的第一多播业务会话启动失败消息或者第一多播业务会话启动响应消息，其中，所述第一多播业务会话启动失败消息用于表示所述第一基站管理的需要启动多播业务会话的小区启动多播业务均失败，所述第一多播业务会话启动响应消息包含所述第一基站管理的需要启动 多播业务会话的小区中启动多播业务成功的小区的标识，和/或，所述第一基站管理的需要启动多播业务会话的小区中启动多播业务失败的小区的标识。
结合第二方面，第二方面的第一种可能的实施方式中，所述第一多播业务会话启动消息还包括第二基站管理的需要启动多播业务会话的小区的标识，所述方法还包括：
MCE向所述第二基站发送第二多播业务会话启动消息，其中，所述第二多播业务会话启动消息包括第二基站管理的需要启动多播业务会话的小区的标识；
所述MCE接收所述第二基站返回的第二多播业务会话启动失败消息或者第二多播业务会话启动响应消息，其中，所述第二多播业务会话启动失败消息用于表示所述第二基站管理的需要启动多播业务会话的小区启动多播业务均失败，所述第二多播业务会话启动响应消息包含所述第二基站管理的需要启动多播业务会话的小区中启动多播业务成功的小区的标识，和/或，所述第二基站管理的需要启动多播业务会话的小区中启动多播业务失败的小区的标识。
结合第二方面的第一种可能的实施方式，第二方面的第二种可能的实施方式中，MCE接收所述第一基站返回的第一多播业务会话启动失败消息或者第一多播业务会话启动响应消息之后还包括：
向所述第一基站发送第二基站管理的，且启动多播业务成功的小区的标识，和/或，第二基站管理的，且启动多播业务失败的小区的标识。
结合第二方面的第二种可能的实施方式，第二方面的第三种可能的实施方式中，所述MCE向移动管理实体MME发送至少一项信息：第一基站管理的且启动多播业务成功的小区的标识、第一基站管理且启动多播业务失败的小区标识、第二基站管理的且启动多播业务成功的小区的标识和第二基站管理的且启动多播业务失败的小区的标识。
第三方面提供了一种小区多播业务处理方法，多播协作实体MCE判断接收到的移动管理实体MME发送的多播业务会话启动消息中是否包含所述MCE管理的，需要启动的多播业务会话的小区的标识；如果否，则所述MCE向MME发送多播业务会话启动响应消息，其中，所述多播业务会话启动响应消息包含用于表示所述多播业务会话启动消息中的小区列表不在MCE管理的范围内的指示信息。
结合第三方面，第三方面的第一种可能的实施方式中，所述多播业务会话启动响应消息为带超范围标记的多播业务会话启动响应信息，其中，所述超范围标记是所述多播业务会话启动响应信息中设置的字段或者位。
第四方面提供了一种基站，所述基站为第一基站，所述第一基站包括接收器和发送器，
所述接收器用于接收多播协作实体MCE发送的多播业务会话启动消息，其中，所述多播业务会话启动消息包括所述第一基站管理的需要启动多播业务会话的小区的标识；
所述发送器用于向所述MCE发送多播业务会话启动失败消息或者多播业务会话启动响应消息，其中，所述多播业务会话启动失败消息用于表示第一基站管理的需要启动多播业务会话的小区启动多播业务均失败，所述多播业务会话启动响应消息包含第一基站管理的需要启动多播业务会话的小区中启动多播业务成功的小区的标识，和/或，第一基站管理的需要启动多播业务会话的小区中启动多播业务失败的小区的标识。
结合第四方面，第四方面的第一种可能的实施方式中，所述多播业务会话启动消息还包括第二基站管理的需要启动多播业务会话的小区的标识，所述基站还包括处理器，
所述处理器用于根据第一基站管理的需要启动多播业务会话的小区的标识启动多播业务，并根据第二基站管理的需要启动多播业务会话的小区的标识获取第二基站管理的小区需要启动多播业务的情况。
结合第四方面的第一种可能的实施方式，第四方面的第二种可能的实施方式中，所述接收器用于接收所述MCE发送的第二基站管理的，且启动多播业务成功的小区的标识，和/或第二基站管理的，且启动多播业务失败的小区的标识。
结合第四方面或第四方面的第一种可能的实施方式或第四方面的第二种可能的实施方式，第四方面的第三种可能的实施方式中，
所述发送器用于在所述第一基站管理的一个或者多个小区启动多播业务失败时，向所述第二基站发送所述第一基站管理的需要启动多播业务会话的小区中启动多播业务成功的小区的标识，和/或，所述第一基站管理的需要启动多播业务会话的小区中启动多播业务失败的小区的标识；或，
所述发送器用于向所述第二基站发送所述第一基站管理的需要启动多播业务会话的小区中启动多播业务成功的小区的标识，和/或，所述第一基站管理的需要启动多播业务会话的小区中启动多播业务失败的小区的标识。
结合第四方面或第四方面的第一种至第三种可能的实施方式中的任意一种，第四方面的第四种可能的实施方式中，所述接收器用于接收所述第二基站发送的第二基站管理的需要启动多播业务会话的小区中启动多播业务成功的小区的标识，和/或，所述第二基站管理的需要启动多播业务会话的小区中启动多播业务失败的小区的标识。
结合第四方面的第四种可能的实施方式，第四方面的第五种可能的实施方式中，所述发送器用于向用户设备UE发送通知，所述通知用于将所述第一基站管理的启动多播业务成功的小区和/或所述第二基站管理的启动多播业务成功的小区告知所述UE。
结合第四方面的第五种可能的实施方式，第四方面的第六种可能的实施方式中，所述通知中包含位图指示位，所述位图指示位指示第一基站和/或第二基站管理的启动多播业务成功的小区。
第五方面提供了一种多播协作实体MCE，包括：发送器以及接收器，
所述发送器用于向第一基站发送第一多播业务会话启动消息，其中，所述第一多播业务会话启动消息包括所述第一基站管理的需要启动多播业务会话的小区的标识；
所述接收器用于接收所述第一基站返回的第一多播业务会话启动失败消息或者第一多播业务会话启动响应消息，其中，所述第一多播业务会话启动失败消息用于表示所述第一基站管理的需要启动多播业务会话的小区启动多播业务均失败，所述第一多播业务会话启动响应消息包含所述第一基站管理的需要启动多播业务会话的小区中启动多播业务成功的小区的标识，和/或，所述第一基站管理的需要启动多播业务会话的小区中启动多播业务失败的小区的标识。
结合第五方面，第五方面的第一种可能的实施方式中，所述第一多播业务会话启动消息还包括第二基站管理的需要启动多播业务会话的小区的标识，
所述发送器用于向所述第二基站发送第二多播业务会话启动消息，其中，所述第二多播业务会话启动消息包括第二基站管理的需要启动多播业务会话 的小区的标识；
所述接收器用于接收所述第二基站返回的第二多播业务会话启动失败消息或者第二多播业务会话启动响应消息，其中，所述第二多播业务会话启动失败消息用于表示所述第二基站管理的需要启动多播业务会话的小区启动多播业务均失败，所述第二多播业务会话启动响应消息包含所述第二基站管理的需要启动多播业务会话的小区中启动多播业务成功的小区的标识，和/或，所述第二基站管理的需要启动多播业务会话的小区中启动多播业务失败的小区的标识。
结合第五方面，第五方面的第一种可能的实施方式中，所述发送器用于向所述第一基站发送第二基站管理的，且启动多播业务成功的小区的标识，和/或，第二基站管理的，且启动多播业务失败的小区的标识。
结合第五方面的第一种可能的实施方式，第五方面的第二种可能的实施方式中，所述发送器用于向移动管理实体MME发送至少一项信息：第一基站管理的且启动多播业务成功的小区的标识、第一基站管理且启动多播业务失败的小区标识、第二基站管理的且启动多播业务成功的小区的标识和第二基站管理的且启动多播业务失败的小区的标识。
第六方面提供了一种多播协作实体MCE，所述MCE包括处理器以及发送器，
所述处理器用于判断接收到的移动管理实体MME发送的多播业务会话启动消息中是否包含所述MCE管理的，需要启动的多播业务会话的小区的标识，在不包含所述MCE管理的，需要启动的多播业务会话的小区的标识时，调用所述发送器向MME发送多播业务会话启动响应消息，其中，所述多播业务会话启动响应消息包含用于表示所述多播业务会话启动消息中的小区列表不在MCE管理的范围内的指示信息。
结合第六方面，第六方面的第一种可能的实施方式中，所述多播业务会话启动响应消息为带超范围标记的多播业务会话启动响应信息，其中，所述超范围标记是所述多播业务会话启动响应信息中设置的字段或者位。
通过上述方案，本发明在向MCE返回的多播业务会话启动响应消息包括了多播业务会话启动响应消息包含了第一基站管理的需要启动多播业务会话的小区中启动多播业务成功的小区的标识，和/或，第一基站管理的需要启动 多播业务会话的小区中启动多播业务失败的小区的标识，所以，MCE能够根据多播业务会话启动响应消息获知第一基站管理的需要启动多播业务会话的小区中启动多播业务成功的小区的标识，和/或，所述第一基站管理的需要启动多播业务会话的小区中启动多播业务失败的小区的标识，进而确定MCE 140管理下具体哪些小区启动了多播业务成功，哪些小区启动多播业务失败。
附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1是现有技术提供的一种SC-PTM架构的结构示意图；
图2是现有技术提供的一种通过SC-PTM架构进行多播业务的交互图；
图3是本发明提供的一种通过SC-PTM架构进行多播业务的交互图；
图4是本发明提供的另一种通过SC-PTM架构进行多播业务的交互图；
图5是本发明提供的再一种通过SC-PTM架构进行多播业务的交互图；
图6是本发明提供的一种MCE的结构示意图；
图7是本发明提供的一种基站的结构示意图。
具体实施方式
下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本发明一部分实施例，而不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本发明保护的范围。
参见图3，图3是本发明提供的一种通过SC-PTM架构进行多播业务的交互图。由于篇幅所限，图2中省略了BM-SC 110。现假设MCE 140管理基站1以及基站2，基站1管理小区1、小区2和小区3，基站2管理小区4、小区5以及小区6。其中，小区1、小区2、小区3、小区4和小区5为需要启动多 播业务的小区。在本实施例中，基站1和基站2是属于同一个MCE 140管理下的相邻基站，在其他的实施例中，基站1和基站2也可以不是相邻基站。可以理解的是，MCE 140管理基站150的数量，和基站150管理小区的数量可以根据MCE 140和基站150的发射功率、环境和要求等等因素进行设置，本实施例中的数量只是一种举例，而非限定。
BM-SC 110向MBMS-GW 120发送第一多播业务会话启动(MBMS Session Start)消息。其中，第一多播业务会话启动消息中包含多播业务的质量要求以及MBMS-GW 120管理的需要启动多播业务会话的小区1-5的标识。多播业务的质量要求包含下面至少一种：服务质量标识(QoS Class Identifier，QCI)，保证比特速率(guaranteed bit rate，GBR)，最大比特速率(Maximum Bit Rate，MBR)，抢占保留优先级(Allocation and Retention Priority，ARP)等等。
MBMS-GW 120接收到第一多播业务会话启动消息后，根据第一多播业务会话启动消息中小区的标识生成第二多播业务会话启动消息，并向MME 130发送第二多播业务会话启动消息。其中，第二多播业务会话启动消息中包含多播业务的质量要求以及MME 130管理的需要启动多播业务会话的小区1-5的标识。
MME 130接收到第二多播业务会话启动消息后，根据第二多播业务会话启动消息中的小区的标识生成第三多播业务会话启动消息，并向MCE 140发送第三多播业务会话启动消息。其中，第三多播业务会话启动消息中包含多播业务的质量要求以及MCE 140管理的需要启动多播业务会话的小区1-5的标识。
MCE 140接收到第三多播业务会话启动消息后，判断第三多播业务会话启动消息中包括的小区标识是否在MCE 140管理的范围内。如果不在MCE 140管理的范围内，则MCE 140向MME 130返回没有携带小区标识的多播业务会话启动响应消息，以表示第三多播业务会话启动消息中的小区标识不在MCE管理的范围内。可以理解的是，MCE 140也可以向MME 130返回带超范围标记的多播业务会话启动响应信息，以表示第三多播业务会话启动消息中的小区标识不在MCE管理的范围内等等。其中，超范围标记可以是多播业务会话启动响应信息中设置的字段或者位等等。当超范围标记为多播业务会话启 动响应信息中设置的字段时，字段中的数值可以是人为预先设定的数值，例如，预先设定的数值为“0001”等等，当超范围标记为多播业务会话启动响应信息中设置的位时，该位的值可以是人为预先设定的“0”或者“1”。
分别为基站1以及基站2生成第四多播业务会话启动消息以及第五多播业务会话启动消息。其中，第四多播业务会话启动消息包含多播业务的质量要求以及基站1管理的需要启动多播业务会话的小区1-3的标识，第五多播业务会话启动消息包含多播业务的质量要求以及基站2管理的需要启动多播业务会话的小区4-5的标识。
基站1在接收到第四多播业务会话启动消息后，根据小区列表中基站1管理的需要启动多播业务会话的小区的标识确定小区1-3需要启动多播业务，再判断需要启动多播业务的小区1-3是否符合多播业务的质量要求。根据小区是否符合多播业务的质量要求，可以分成两种情况：
(1)、如果小区1-3中至少有一个小区能够启动符合多播业务的质量要求的多播业务，则基站1启动能够符合多播业务的质量要求的小区的多播业务成功，启动不能够符合多播业务的质量要求的小区的多播业务失败。基站1根据小区启动多播业务的情况获得基站1管理的启动多播业务成功的小区的标识，和/或，基站1管理的启动多播业务失败的小区的标识。例如，如果小区1和小区2能够启动符合多播业务质量要求的多播业务，小区3不能启动符合多播业务的质量要求的多播业务，则基站1启动小区1和小区2的多播业务成功，启动小区3的多播业务失败。基站1根据小区1-3启动多播业务的情况获得基站1管理的启动多播业务成功的小区的标识，即小区1的标识和小区2的标识，和/或，获得基站1管理的启动多播业务失败的小区的标识，即小区3的标识。此后，基站1将基站1管理的启动多播业务成功的小区的标识和/或基站1管理的启动多播业务失败的小区的标识封装到第一多播业务会话启动响应消息中，并向MCE 140发送第一多播业务会话启动响应消息。可选地，还可以在第一多播会话启动响应消息中携带启动多播业失败的小区的失败原因，比如：资源不可用，不支持请求的QCI(QoS Class Identifier)，或者非法的QoS(Quality of Service)等等中的一个或者多个的组合。
(2)、如果小区1-3中没有一个符合多播业务的质量要求，则基站1向 MCE 140发送第一多播业务会话启动失败消息，其中，第一多播业务会话启动失败消息可以携带或者不携带基站1管理的启动多播业务失败的小区的标识。如果第一多播业务会话启动失败消息不携带基站1管理的启动多播业务失败的小区的标识，则MCE 140在接收到基站1发送的第一多播业务会话启动失败消息后，默认基站1管理的，需要启动多播业务的小区均启动多播业务失败。如果第一多播业务会话启动失败消息中需要携带基站1管理的启动多播业务失败的小区的标识，则基站1将基站1管理的启动多播业务失败的小区的标识封装到第一多播业务会话启动失败消息中。可选地，基站1还可以在第一多播业务会话启动失败消息中携带启动多播业失败的小区的失败原因，比如：资源不可用，不支持请求的QCI，或者非法的Qos等等中的一个或者多个的组合。
基站2在接收到MCE 140发送的第五多播业务会话启动消息后的处理与基站1类似，此处不再展开描述。
MCE 140接收到基站1和基站2返回的消息。根据MCE 140接收到基站1和基站2返回的消息的不同，可以分为4种情况：
(1)、如果基站1返回的第一多播业务会话启动响应消息携带基站1管理的，且启动多播业务成功的小区的标识，则可以从基站1返回的第一多播业务会话启动响应消息获得基站1管理的，且启动多播业务成功的小区的标识。或者，如果基站1返回的第一多播业务会话启动响应消息中携带基站1管理的，且启动多播业务失败的小区的标识，则MCE 140根据基站1管理的需要启动多播业务的小区的标识中，减去基站1管理的，且启动多播业务失败的小区的标识，得到基站1管理的，且启动多播业务成功的小区的标识。MCE 140接收到基站2返回的第一多播业务会话失败响应消息后，获知基站2管理的需要启动多播业务的小区均启动多播业务失败。MCE 140据此进行统计得到MCE 140管理的(包括基站1和基站2管理的)且启动多播业务成功的小区的标识和/或MCE 140管理的且启动多播业务失败的小区的标识，并将MCE 140管理的且启动多播业务成功的小区的标识和/或MCE 140管理的且启动多播业务失败的小区的标识封装到第二多播业务会话启动响应消息中，向MME 130发送第二多播业务会话启动响应消息。(2)、MCE 140接收到基站1返回的第一多播业务会话失败响应消息后，获知基站1管理的需要启动多播业务的小区均启 动多播业务失败。如果基站2返回的第一多播业务会话启动响应消息携带基站2管理的，且启动多播业务成功的小区的标识，则MCE 140接收到基站2返回的第一多播业务会话启动响应消息后，从基站2返回的第一多播业务会话启动响应消息中获得基站2管理的，且启动多播业务成功的小区的标识。如果基站2返回的第一多播业务会话启动响应消息中携带基站2管理的，且启动多播业务失败的小区的标识，则MCE 140根据基站2管理的需要启动多播业务的小区的标识，减去基站2管理的，且启动多播业务失败的小区的标识，得到基站2管理的，且启动多播业务成功的小区的标识。MCE 140据此统计得到MCE 140管理的(包括基站1和基站2管理的)且启动多播业务成功的小区的标识和/或MCE 140管理的且启动多播业务失败的小区的标识，并将MCE 140管理的(包括基站1和基站2管理的)且启动多播业务成功的小区的标识和/或MCE 140管理的且启动多播业务失败的小区的标识封装到第二多播业务会话启动响应消息中，并向MME 130发送第二多播业务会话启动响应消息。
(3)、如果基站1返回的第一多播业务会话启动响应消息携带基站1管理的，且启动多播业务成功的小区的标识，则可以从基站1返回的第一多播业务会话启动响应消息获得基站1管理的，且启动多播业务成功的小区的标识。或者，如果基站1返回的第一多播业务会话启动响应消息中携带基站1管理的，且启动多播业务失败的小区的标识，则MCE 140根据基站1管理的需要启动多播业务的小区的标识中，减去基站1管理的，且启动多播业务失败的小区的标识，得到基站1管理的，且启动多播业务成功的小区的标识。如果基站2返回的第一多播业务会话启动响应消息携带基站2管理的，且启动多播业务成功的小区的标识，则MCE 140接收到基站2返回的第一多播业务会话启动响应消息后，从基站2返回的第一多播业务会话启动响应消息中获得基站2管理的，且启动多播业务成功的小区的标识。如果基站2返回的第一多播业务会话启动响应消息中携带基站2管理的，且启动多播业务失败的小区的标识，则MCE 140根据基站2管理的需要启动多播业务的小区的标识，减去基站2管理的，且启动多播业务失败的小区的标识，得到基站2管理的，且启动多播业务成功的小区的标识。MCE 140将基站1管理的，且启动多播业务成功的小区的标识与基站2管理的，且启动多播业务成功的小区的标识进行汇集，和/ 或，将基站1管理的，且启动多播业务失败的小区的标识与基站2管理的，且启动多播业务失败的小区的标识进行汇集，以得到MCE 140管理的(包括基站1和基站2管理的)且启动多播业务成功的小区的标识和/或MCE 140管理的且启动多播业务失败的小区的标识。MCE 140将MCE 140管理的(包括基站1和基站2管理的)且启动多播业务成功的小区的标识和/或MCE 140管理的且启动多播业务失败的小区的标识封装到第二多播业务会话启动响应消息中，并向MME 130发送第二多播业务会话启动响应消息。
(4)、MCE 140接收到基站1返回的第一多播业务会话失败响应消息后，获知基站1管理的需要启动多播业务的小区均启动多播业务失败。MCE 140接收到基站2返回的第一多播业务会话失败响应消息后，获知基站2管理的需要启动多播业务的小区均启动多播业务失败。所以，MCE 140生成第二多播业务会话失败响应消息，并向MME 130发送第二多播业务会话失败响应消息。
如果MME 130接收到第二多播业务会话启动响应消息，则根据第二多播业务会话启动响应消息中的MCE 140管理的且启动多播业务成功的小区的标识和/或MCE 140管理的且启动多播业务失败的小区的标识生成第三多播业务会话启动响应消息，并向MBMS-GW 120发送第三多播业务会话启动响应消息。如果MME 130接收到第二多播业务会话启动失败消息，则根据第二多播业务会话启动失败消息生成第三多播业务会话失败响应消息，并向MBMS-GW 120发送第三多播业务会话启动失败消息。
如果MBMS-GW 120接收到第三多播业务会话启动响应消息，则根据第三多播业务会话启动响应消息中的MCE 140管理的且启动多播业务成功的小区的标识和/或MCE 140管理的且启动多播业务失败的小区的标识生成第四多播业务会话启动响应消息，并向BM-SC 110发送第四多播业务会话启动响应消息。如果MBMS-GW 120接收到第四多播业务会话启动失败消息，则根据第四多播业务会话启动失败消息生成第四多播业务会话失败响应消息，并向BM-SC 110发送第四多播业务会话启动失败消息。
可以理解的是，如果BM-SC 110需要启动多种类型的多播业务，则第一至第五多播业务会话启动消息中还包括多播业务的标识。基站1在接收到第四多播业务会话启动消息后，为小区1-3启动与多播业务的标识对应的多播业务。 基站2在接收到第五多播业务会话启动消息后，为小区4和5启动与多播业务的标识对应的多播业务。
通过上述方案，本发明在向MCE返回的多播业务会话启动响应消息包括了多播业务会话启动响应消息包含了第一基站管理的需要启动多播业务会话的小区中启动多播业务成功的小区的标识，和/或，第一基站管理的需要启动多播业务会话的小区中启动多播业务失败的小区的标识，所以，MCE能够根据多播业务会话启动响应消息获知第一基站管理的需要启动多播业务会话的小区中启动多播业务成功的小区的标识，和/或，所述第一基站管理的需要启动多播业务会话的小区中启动多播业务失败的小区的标识，进而确定MCE 140管理下具体哪些小区启动了多播业务成功，哪些小区启动多播业务失败。
请参阅图4，图4所示的实施例与图3所示的实施例的不同之处在于，MCE 140向基站1发送的第四多播业务会话启动消息中还包括基站2管理的需要启动多播业务的小区4和小区5的标识。MCE 140向基站2发送的第五多播业务会话启动消息中还包括基站1管理的需要启动多播业务的小区1-3的标识。或者，当标识以列表的形式组织起来时，MCE 140向基站1发送的第四多播业务会话启动消息中的除了包括基站1管理的需要启动多播业务的小区1-3的标识组成的一个小区列表外，还包括基站2管理的需要启动多播业务的小区4和小区5的标识组成的另一个小区列表，MCE 140向基站2发送的第五多播业务会话启动消息中的除了包括基站2管理的需要启动多播业务的小区4和小区5的标识组成的一个小区列表外，还包括基站1管理的需要启动多播业务的小区1-3的标识组成的另一个小区列表。
基站1在接收到MCE 140发送的第四多播业务会话启动消息后，根据第四多播业务会话启动消息中基站2管理的需要启动多播业务会话的小区的标识获取基站2管理的小区需要启动多播业务的情况，从而得知基站2中的小区4和小区5需要启动多播业务。基站2在接收到MCE 140发送的第五多播业务会话启动消息后，根据第五多播业务会话启动消息中基站1管理的需要启动多播业务会话的小区的标识获取基站1管理的小区需要启动多播业务的情况，从而得知基站1中的小区1-3需要启动多播业务。
假设基站1中的小区1和小区2启动多播业务成功，小区3启动多播业务失败，基站2中的小区4启动多播业务成功，小区5启动多播业务失败。则根据图3所示的实施例可知，MCE 140将小区1、小区2和小区4的标识和/或小区3和小区5的标识封装到多播业务会话更新消息或者启动多播业务成功小区通知消息向基站1和基站2发送。其中，多播业务会话更新消息还可以包括指示信息，所述指示信息用于指示多播业务会话更新消息中的小区标识为MCE 140管理的且启动多播业务成功的小区的标识和/或MCE 140管理的且启动多播业务失败的小区的标识。或者，由于基站1已经知道自己管理的小区中启动多播业务成功的小区的标识，所以，MCE 140向基站1发送的多播业务会话更新消息或者启动多播业务成功小区通知消息中只需包括基站2管理的且启动多播业务成功的小区的标识和/或基站2管理的且启动多播业务失败的小区的标识。
基站1在接收到多播业务会话更新消息或者启动多播业务成功小区通知消息之后，可以知道基站2管理的需要启动多播业务的小区中，小区4启动多播业务成功，小区5启动多播业务失败。然后，基站1向基站1管理的小区中的用户设备发送通知，其中，通知用于将基站1管理的启动多播业务成功的小区和/或基站2管理的启动多播业务成功的小区告知基站1管理的小区中的UE，使得UE能够知道基站1和/或基站2管理的哪些小区启动了多播业务，以便UE在移动过程中，如果移动到基站1和/或基站2管理的启动多播业务成功的小区时，直接接收多播业务，或者，如果移动到基站1和/或基站2管理的启动多播业务失败或没没有启动多播业务的小区时，尽快确定是否需要启动单播承载，以便继续接受多播业务。启动多播业务成功的小区的消息可以是启动多播业务成功的小区的标识，也可以是用其它的形式表达的启动多播业务成功的小区的标识。例如，启动多播业务成功的小区的标识也可以使用位图指示序列进行表示，其中，位图指示序列包括多个位，位图指示序列的位与基站1管理的小区的标识和/或基站2管理的小区的标识对应，位图指示序列的位的值用于表示对应的小区的标识所指示的小区中哪些启动多播业务成功。在一具体的实施例中，如表1所示，
表1 位图指示序列表
Figure PCTCN2015093931-appb-000001
其中，表1中的第一行是基站1和基站2管理的小区的标识。表1中的第二行是多播业务标识为业务标识1的多播业务的位图指示序列110100。位图指示序列中的位的值为1时，表示对应的小区标识所代表的小区启动多播业务成功，位图指示序列中的位的值为0时，表示对应的小区标识所代表的小区启动多播业务失败或者没有启动多播业务。所以，位图指示序列110100表示多播业务标识为业务标识1的多播业务在小区1、小区2和小区4启动成功，在小区3和小区6启动失败或者没有启动多播业务。当有多个多播业务时，每个多播业务都可以以同样的位图指示序列进行表示，从而用位图指示序列代替每次发送小区的标识，减少传输资源的浪费。
基站2的处理过程和基站1的类似，此处不再展开描述。
参阅图5，图5所示的实施例与图4所示的实施例的不同之处在于，MCE 140无须通过向MCE 140管理的且启动多播业务成功的小区的标识和/或MCE 140管理的且启动多播业务失败的小区的标识以告知基站1和基站2哪些小区启动多播业务成功，哪些小区启动多播业务失败，取而代之的是：
基站1在启动小区的多播业务后，向基站2发送基站1管理的且启动多播业务成功的小区的标识和/或基站1管理的且启动多播业务失败的小区的标识。或，基站1在启动小区的多播业务后，如果基站1管理的一个或者多个小区启 动多播业务失败，则向基站2发送基站1管理的且启动多播业务成功的小区的标识和/或基站1管理的且启动多播业务失败的小区的标识，如果基站1管理的小区启动多播业务均成功，则不需向向基站2发送基站1管理的且启动多播业务成功的小区的标识和/或基站1管理的且启动多播业务失败的小区的标识，基站2在一段时间内没有接收到基站1发送的基站1管理的且启动多播业务成功的小区的标识和/或基站1管理的且启动多播业务失败的小区的标识，则默认通过第五多播业务会话启动消息获取到的，基站1管理的需要启动多播业务的小区均成功启动多播业务，以节约传输资源。而且，基站1也同样接收基站2发送的基站2管理的且启动多播业务成功的小区的标识和/或基站2管理的且启动多播业务失败的小区的标识，并根据基站2发送的基站2管理的且启动多播业务成功的小区的标识和/或基站2管理的且启动多播业务失败的小区的标识获取基站2管理的小区中成功启动多播业务成功的小区的标识，从而获知基站2管理的小区中，哪些小区启动多播业务成功，哪些启动多播业务失败。
基站2的处理过程和基站1的类似，此处不再展开描述。
上述的实施例中，如果消息中的标识不止一个的时候，可将标识以列表或者位图等形式组织起来，以便于进行传输。
参阅图6，图6是本发明提供的一种MCE的结构示意图。本实施例的MCE 600包括：处理器601、存储器602、发送器603以及接收器604。其中，处理器601、存储器602、发送器603以及接收器604之间通过总线连接。
处理器601可以是中央处理器(英文：central processing unit，CPU)，网络处理器(英文：network processor，NP)，硬件芯片或者其任意组合。上述硬件芯片可以是专用集成电路(英文：application-specific integrated circuit，ASIC)，可编程逻辑器件(英文：programmable logic device，PLD)或其组合。上述PLD可以是复杂可编程逻辑器件(英文：complex programmable logic device，CPLD)，现场可编程逻辑门阵列(英文：field-programmable gate array，FPGA)，通用阵列逻辑(英文：generic array logic，GAL)或其任意组合。
存储器602可用于存储软件程序以及模块，处理器601通过运行存储在存储器602的软件程序以及模块，从而执行各种功能应用以及数据处理。存储器602可主要包括存储程序区和存储数据区，其中，存储程序区可存储操作***、 至少一个功能所需的应用程序(比如声音播放功能、图像播放功能等)等；存储数据区可存储根据MCE 600的使用所创建的数据等。此外，存储器602可以包括高速随机存取存储器，还可以包括非易失性存储器，例如至少一个磁盘存储器件、闪存器件、或其他易失性固态存储器件。相应地，存储器602还可以包括存储器控制器，以提供处理器601对存储器602的访问。
发送器603以及接收器604可以是独立的。也可以是集合在一起的。发送器603以及接收器604可以通过天线发射无线信号传输信号至其他的设备，也可以通过光纤发射光信号至其他的设备。当发送器603以及接收器604通过天线发射无线信号传输信号至其他的设备时，发送器603以及接收器604包括谐振器、调制解调器、放大器等等。当发送器603以及接收器604通过光纤发射光信号至其他的设备时，发送器603以及接收器604包括光耦合器、光调制解调器、放大器等等。
所述MCE 600在运行时，由一个或者一个以上处理器执行存储在存储器602中的一个或者一个以上程序，用于进行以下操作的指令：
所述发送器603向第一基站发送第一多播业务会话启动消息，其中，所述第一多播业务会话启动消息包括所述第一基站管理的需要启动多播业务会话的小区的标识；
所述接收器604接收所述第一基站返回的第一多播业务会话启动失败消息或者第一多播业务会话启动响应消息，其中，所述第一多播业务会话启动失败消息用于表示所述第一基站管理的需要启动多播业务会话的小区启动多播业务均失败，所述第一多播业务会话启动响应消息包含所述第一基站管理的需要启动多播业务会话的小区中启动多播业务成功的小区的标识，和/或，所述第一基站管理的需要启动多播业务会话的小区中启动多播业务失败的小区的标识。
可选地，所述第一多播业务会话启动消息还包括第二基站管理的需要启动多播业务会话的小区的标识，
所述发送器603用于向所述第二基站发送第二多播业务会话启动消息，其中，所述第二多播业务会话启动消息包括第二基站管理的需要启动多播业务会话的小区的标识；
所述接收器604用于接收所述第二基站返回的第二多播业务会话启动失 败消息或者第二多播业务会话启动响应消息，其中，所述第二多播业务会话启动失败消息用于表示所述第二基站管理的需要启动多播业务会话的小区启动多播业务均失败，所述第二多播业务会话启动响应消息包含所述第二基站管理的需要启动多播业务会话的小区中启动多播业务成功的小区的标识，和/或，所述第二基站管理的需要启动多播业务会话的小区中启动多播业务失败的小区的标识。
可选地，所述发送器603用于向所述第一基站发送第二基站管理的，且启动多播业务成功的小区的标识，和/或，第二基站管理的，且启动多播业务失败的小区的标识。
可选地，所述发送器603用于向移动管理实体MME发送至少一项信息：第一基站管理的且启动多播业务成功的小区的标识、第一基站管理且启动多播业务失败的小区标识、第二基站管理的且启动多播业务成功的小区的标识和第二基站管理的且启动多播业务失败的小区的标识。
可选地，所述处理器601用于判断接收到的移动管理实体MME发送的多播业务会话启动消息中是否包含所述MCE管理的，需要启动的多播业务会话的小区的标识，在不包含所述MCE管理的，需要启动的多播业务会话的小区的标识时，调用所述发送器603向MME发送多播业务会话启动响应消息，其中，所述多播业务会话启动响应消息包含用于表示所述多播业务会话启动消息中的小区列表不在MCE管理的范围内的指示信息。
可选地，所述多播业务会话启动响应消息为带超范围标记的多播业务会话启动响应信息，其中，所述超范围标记是所述多播业务会话启动响应信息中设置的字段或者位。
通过上述方案，本发明在向MCE返回的多播业务会话启动响应消息包括了多播业务会话启动响应消息包含了第一基站管理的需要启动多播业务会话的小区中启动多播业务成功的小区的标识，和/或，第一基站管理的需要启动多播业务会话的小区中启动多播业务失败的小区的标识，所以，MCE能够根据多播业务会话启动响应消息获知第一基站管理的需要启动多播业务会话的小区中启动多播业务成功的小区的标识，和/或，所述第一基站管理的需要启动多播业务会话的小区中启动多播业务失败的小区的标识，进而确定MCE 140管理下具体哪些小区启动了多播业务成功，哪些小区启动多播业务失败。
参阅图7，图7是本发明提供的一种基站的结构示意图。本实施例的基站700包括：处理器701、存储器702、发送器703以及接收器704。其中，处理器701、存储器702、发送器703以及接收器704之间通过总线连接。
处理器701可以是中央处理器(英文：central processing unit，CPU)，网络处理器(英文：network processor，NP)，硬件芯片或者其任意组合。上述硬件芯片可以是专用集成电路(英文：application-specific integrated circuit，ASIC)，可编程逻辑器件(英文：programmable logic device，PLD)或其组合。上述PLD可以是复杂可编程逻辑器件(英文：complex programmable logic device，CPLD)，现场可编程逻辑门阵列(英文：field-programmable gate array，FPGA)，通用阵列逻辑(英文：generic array logic，GAL)或其任意组合。
存储器702可用于存储软件程序以及模块，处理器701通过运行存储在存储器702的软件程序以及模块，从而执行各种功能应用以及数据处理。存储器702可主要包括存储程序区和存储数据区，其中，存储程序区可存储操作***、至少一个功能所需的应用程序(比如声音播放功能、图像播放功能等)等；存储数据区可存储根据基站700的使用所创建的数据等。此外，存储器702可以包括高速随机存取存储器，还可以包括非易失性存储器，例如至少一个磁盘存储器件、闪存器件、或其他易失性固态存储器件。相应地，存储器702还可以包括存储器控制器，以提供处理器701对存储器702的访问。
发送器703以及接收器704可以是独立的。也可以是集合在一起的。发送器703以及接收器704可以通过天线发射无线信号传输信号至其他的设备，也可以通过光纤发射光信号至其他的设备。当发送器703以及接收器704通过天线发射无线信号传输信号至其他的设备时，发送器703以及接收器704包括谐振器、调制解调器、放大器等等。当发送器703以及接收器704通过光纤发射光信号至其他的设备时，发送器703以及接收器704包括光耦合器、光调制解调器、放大器等等。
所述基站700在运行时，由一个或者一个以上处理器执行存储在存储器702中的一个或者一个以上程序，用于进行以下操作的指令：
所述接收器704用于接收多播协作实体MCE发送的多播业务会话启动消息，其中，所述多播业务会话启动消息包括所述第一基站管理的需要启动多播 业务会话的小区的标识；
所述发送器703用于向所述MCE发送多播业务会话启动失败消息或者多播业务会话启动响应消息，其中，所述多播业务会话启动失败消息用于表示第一基站管理的需要启动多播业务会话的小区启动多播业务均失败，所述多播业务会话启动响应消息包含第一基站管理的需要启动多播业务会话的小区中启动多播业务成功的小区的标识，和/或，第一基站管理的需要启动多播业务会话的小区中启动多播业务失败的小区的标识。
可选地，所述多播业务会话启动消息还包括第二基站管理的需要启动多播业务会话的小区的标识，
所述处理器701用于根据第一基站管理的需要启动多播业务会话的小区的标识启动多播业务，并根据第二基站管理的需要启动多播业务会话的小区的标识获取第二基站管理的小区需要启动多播业务的情况。
可选地，所述接收器704用于接收所述MCE发送的第二基站管理的，且启动多播业务成功的小区的标识，和/或第二基站管理的，且启动多播业务失败的小区的标识。
可选地，所述发送器703用于在所述第一基站管理的一个或者多个小区启动多播业务失败时，向所述第二基站发送所述第一基站管理的需要启动多播业务会话的小区中启动多播业务成功的小区的标识，和/或，所述第一基站管理的需要启动多播业务会话的小区中启动多播业务失败的小区的标识；或，
所述发送器703用于向所述第二基站发送所述第一基站管理的需要启动多播业务会话的小区中启动多播业务成功的小区的标识，和/或，所述第一基站管理的需要启动多播业务会话的小区中启动多播业务失败的小区的标识。
可选地，所述接收器704用于接收所述第二基站发送的第二基站管理的需要启动多播业务会话的小区中启动多播业务成功的小区的标识，和/或，所述第二基站管理的需要启动多播业务会话的小区中启动多播业务失败的小区的标识。
可选地，所述发送器703用于向用户设备UE发送通知，所述通知用于将所述第一基站管理的启动多播业务成功的小区和/或所述第二基站管理的启动多播业务成功的小区告知所述UE。
可选地，所述通知中包含位图指示位，所述位图指示位指示第一基站和/ 或第二基站管理的启动多播业务成功的小区。
通过上述方案，本发明在向MCE返回的多播业务会话启动响应消息包括了多播业务会话启动响应消息包含了第一基站管理的需要启动多播业务会话的小区中启动多播业务成功的小区的标识，和/或，第一基站管理的需要启动多播业务会话的小区中启动多播业务失败的小区的标识，所以，MCE能够根据多播业务会话启动响应消息获知第一基站管理的需要启动多播业务会话的小区中启动多播业务成功的小区的标识，和/或，所述第一基站管理的需要启动多播业务会话的小区中启动多播业务失败的小区的标识，进而确定MCE 140管理下具体哪些小区启动了多播业务成功，哪些小区启动多播业务失败。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程，是可以通过计算机程序来指令相关的硬件来完成，所述的程序可存储于一计算机可读取存储介质中，该程序在执行时，可包括如上述各方法的实施例的流程。其中，所述的存储介质可为磁碟、光盘、只读存储记忆体(Read-Only Memory，ROM)或随机存储记忆体(Random Access Memory，RAM)等。
以上所揭露的仅为本发明一种较佳实施例而已，当然不能以此来限定本发明之权利范围，本领域普通技术人员可以理解实现上述实施例的全部或部分流程，并依本发明权利要求所作的等同变化，仍属于发明所涵盖的范围。

Claims (26)

  1. 一种小区多播业务处理方法，其特征在于，包括：
    第一基站接收多播协作实体MCE发送的多播业务会话启动消息，其中，所述多播业务会话启动消息包括所述第一基站管理的需要启动多播业务会话的小区的标识；
    所述第一基站向所述MCE发送多播业务会话启动失败消息或者多播业务会话启动响应消息，其中，所述多播业务会话启动失败消息用于表示所述第一基站管理的需要启动多播业务会话的小区启动多播业务均失败，所述多播业务会话启动响应消息包含所述第一基站管理的需要启动多播业务会话的小区中启动多播业务成功的小区的标识，和/或，所述第一基站管理的需要启动多播业务会话的小区中启动多播业务失败的小区的标识。
  2. 根据权利要求1所述的方法，其特征在于，所述多播业务会话启动消息还包括第二基站管理的需要启动多播业务会话的小区的标识，
    所述第一基站接收MCE发送的多播业务会话启动消息之后，所述第一基站向所述MCE发送多播业务会话启动失败消息或者多播业务会话启动响应消息之前，还包括：
    所述第一基站根据第一基站管理的需要启动多播业务会话的小区的标识启动多播业务，并根据第二基站管理的需要启动多播业务会话的小区的标识获取第二基站管理的小区需要启动多播业务的情况。
  3. 根据权利要求2所述的方法，其特征在于，
    所述第一基站向所述MCE发送多播业务会话启动失败消息或者多播业务会话启动响应消息之后包括：
    接收所述MCE发送的第二基站管理的，且启动多播业务成功的小区的标识，和/或第二基站管理的，且启动多播业务失败的小区的标识。
  4. 根据权利要求1至3任一权利要求所述的方法，其特征在于，第一基站接收MCE发送的多播业务会话启动消息之后包括：
    如果所述第一基站管理的一个或者多个小区启动多播业务失败，则向所述第二基站发送所述第一基站管理的需要启动多播业务会话的小区中启动多播 业务成功的小区的标识，和/或，所述第一基站管理的需要启动多播业务会话的小区中启动多播业务失败的小区的标识；或，
    向所述第二基站发送所述第一基站管理的需要启动多播业务会话的小区中启动多播业务成功的小区的标识，和/或，所述第一基站管理的需要启动多播业务会话的小区中启动多播业务失败的小区的标识。
  5. 根据权利要求1至4任一权利要求所述的方法，其特征在于，所述方法还包括：
    接收所述第二基站发送的第二基站管理的需要启动多播业务会话的小区中启动多播业务成功的小区的标识，和/或，所述第二基站管理的需要启动多播业务会话的小区中启动多播业务失败的小区的标识。
  6. 根据权利要求5所述的方法，其特征在于，接收多播协作实体MCE发送的多播业务会话启动消息，以及，接收所述第二基站发送的第二基站管理的需要启动多播业务会话的小区中启动多播业务成功的小区的标识，和/或，所述第二基站管理的需要启动多播业务会话的小区中启动多播业务失败的小区的标识之后，还包括：
    向用户设备UE发送通知，所述通知用于将所述第一基站管理的启动多播业务成功的小区和/或所述第二基站管理的启动多播业务成功的小区告知所述UE。
  7. 根据权利要求6所述的方法，其特征在于，所述通知中包含位图指示位，所述位图指示位指示第一基站和/或第二基站管理的启动多播业务成功的小区。
  8. 一种小区多播业务处理方法，其特征在于，包括：
    多播协作实体MCE向第一基站发送第一多播业务会话启动消息，其中，所述第一多播业务会话启动消息包括所述第一基站管理的需要启动多播业务会话的小区的标识；
    所述MCE接收所述第一基站返回的第一多播业务会话启动失败消息或者第一多播业务会话启动响应消息，其中，所述第一多播业务会话启动失败消息用于表示所述第一基站管理的需要启动多播业务会话的小区启动多播业务均失败，所述第一多播业务会话启动响应消息包含所述第一基站管理的需要启动多播业务会话的小区中启动多播业务成功的小区的标识，和/或，所述第一基 站管理的需要启动多播业务会话的小区中启动多播业务失败的小区的标识。
  9. 根据权利要求8所述的方法，其特征在于，所述第一多播业务会话启动消息还包括第二基站管理的需要启动多播业务会话的小区的标识，所述方法还包括：
    MCE向所述第二基站发送第二多播业务会话启动消息，其中，所述第二多播业务会话启动消息包括第二基站管理的需要启动多播业务会话的小区的标识；
    所述MCE接收所述第二基站返回的第二多播业务会话启动失败消息或者第二多播业务会话启动响应消息，其中，所述第二多播业务会话启动失败消息用于表示所述第二基站管理的需要启动多播业务会话的小区启动多播业务均失败，所述第二多播业务会话启动响应消息包含所述第二基站管理的需要启动多播业务会话的小区中启动多播业务成功的小区的标识，和/或，所述第二基站管理的需要启动多播业务会话的小区中启动多播业务失败的小区的标识。
  10. 根据权利要求9所述的方法，其特征在于，MCE接收所述第一基站返回的第一多播业务会话启动失败消息或者第一多播业务会话启动响应消息之后还包括：
    向所述第一基站发送第二基站管理的，且启动多播业务成功的小区的标识，和/或，第二基站管理的，且启动多播业务失败的小区的标识。
  11. 根据权利要求10所述的方法，其特征在于，还包括：
    所述MCE向移动管理实体MME发送至少一项信息：第一基站管理的且启动多播业务成功的小区的标识、第一基站管理且启动多播业务失败的小区标识、第二基站管理的且启动多播业务成功的小区的标识和第二基站管理的且启动多播业务失败的小区的标识。
  12. 一种小区多播业务处理方法，其特征在于，
    多播协作实体MCE判断接收到的移动管理实体MME发送的多播业务会话启动消息中是否包含所述MCE管理的，需要启动的多播业务会话的小区的标识；如果否，则所述MCE向MME发送多播业务会话启动响应消息，其中，所述多播业务会话启动响应消息包含用于表示所述多播业务会话启动消息中的小区列表不在MCE管理的范围内的指示信息。
  13. 根据权利要求12所述的方法，其特征在于，所述多播业务会话启动 响应消息为带超范围标记的多播业务会话启动响应信息，其中，所述超范围标记是所述多播业务会话启动响应信息中设置的字段或者位。
  14. 一种基站，其特征在于，所述基站为第一基站，所述第一基站包括接收器和发送器，
    所述接收器用于接收多播协作实体MCE发送的多播业务会话启动消息，其中，所述多播业务会话启动消息包括所述第一基站管理的需要启动多播业务会话的小区的标识；
    所述发送器用于向所述MCE发送多播业务会话启动失败消息或者多播业务会话启动响应消息，其中，所述多播业务会话启动失败消息用于表示第一基站管理的需要启动多播业务会话的小区启动多播业务均失败，所述多播业务会话启动响应消息包含第一基站管理的需要启动多播业务会话的小区中启动多播业务成功的小区的标识，和/或，第一基站管理的需要启动多播业务会话的小区中启动多播业务失败的小区的标识。
  15. 根据权利要求14所述的基站，其特征在于，所述多播业务会话启动消息还包括第二基站管理的需要启动多播业务会话的小区的标识，所述基站还包括处理器，
    所述处理器用于根据第一基站管理的需要启动多播业务会话的小区的标识启动多播业务，并根据第二基站管理的需要启动多播业务会话的小区的标识获取第二基站管理的小区需要启动多播业务的情况。
  16. 根据权利要求15所述的基站，其特征在于，
    所述接收器用于接收所述MCE发送的第二基站管理的，且启动多播业务成功的小区的标识，和/或第二基站管理的，且启动多播业务失败的小区的标识。
  17. 根据权利要求14至16任一权利要求所述的基站，其特征在于，
    所述发送器用于在所述第一基站管理的一个或者多个小区启动多播业务失败时，向所述第二基站发送所述第一基站管理的需要启动多播业务会话的小区中启动多播业务成功的小区的标识，和/或，所述第一基站管理的需要启动多播业务会话的小区中启动多播业务失败的小区的标识；或，
    所述发送器用于向所述第二基站发送所述第一基站管理的需要启动多播业务会话的小区中启动多播业务成功的小区的标识，和/或，所述第一基站管 理的需要启动多播业务会话的小区中启动多播业务失败的小区的标识。
  18. 根据权利要求14至17任一权利要求所述的基站，其特征在于，所述接收器用于接收所述第二基站发送的第二基站管理的需要启动多播业务会话的小区中启动多播业务成功的小区的标识，和/或，所述第二基站管理的需要启动多播业务会话的小区中启动多播业务失败的小区的标识。
  19. 根据权利要求18所述的基站，其特征在于，所述发送器用于向用户设备UE发送通知，所述通知用于将所述第一基站管理的启动多播业务成功的小区和/或所述第二基站管理的启动多播业务成功的小区告知所述UE。
  20. 根据权利要求19所述的基站，其特征在于，所述通知中包含位图指示位，所述位图指示位指示第一基站和/或第二基站管理的启动多播业务成功的小区。
  21. 一种多播协作实体MCE，其特征在于，包括：发送器以及接收器，
    所述发送器用于向第一基站发送第一多播业务会话启动消息，其中，所述第一多播业务会话启动消息包括所述第一基站管理的需要启动多播业务会话的小区的标识；
    所述接收器用于接收所述第一基站返回的第一多播业务会话启动失败消息或者第一多播业务会话启动响应消息，其中，所述第一多播业务会话启动失败消息用于表示所述第一基站管理的需要启动多播业务会话的小区启动多播业务均失败，所述第一多播业务会话启动响应消息包含所述第一基站管理的需要启动多播业务会话的小区中启动多播业务成功的小区的标识，和/或，所述第一基站管理的需要启动多播业务会话的小区中启动多播业务失败的小区的标识。
  22. 根据权利要求21所述的MCE，其特征在于，所述第一多播业务会话启动消息还包括第二基站管理的需要启动多播业务会话的小区的标识，
    所述发送器用于向所述第二基站发送第二多播业务会话启动消息，其中，所述第二多播业务会话启动消息包括第二基站管理的需要启动多播业务会话的小区的标识；
    所述接收器用于接收所述第二基站返回的第二多播业务会话启动失败消息或者第二多播业务会话启动响应消息，其中，所述第二多播业务会话启动失败消息用于表示所述第二基站管理的需要启动多播业务会话的小区启动多播 业务均失败，所述第二多播业务会话启动响应消息包含所述第二基站管理的需要启动多播业务会话的小区中启动多播业务成功的小区的标识，和/或，所述第二基站管理的需要启动多播业务会话的小区中启动多播业务失败的小区的标识。
  23. 根据权利要求22所述的MCE，其特征在于，所述发送器用于向所述第一基站发送第二基站管理的，且启动多播业务成功的小区的标识，和/或，第二基站管理的，且启动多播业务失败的小区的标识。
  24. 根据权利要求23所述的MCE，其特征在于，
    所述发送器用于向移动管理实体MME发送至少一项信息：第一基站管理的且启动多播业务成功的小区的标识、第一基站管理且启动多播业务失败的小区标识、第二基站管理的且启动多播业务成功的小区的标识和第二基站管理的且启动多播业务失败的小区的标识。
  25. 一种多播协作实体MCE，其特征在于，所述MCE包括处理器以及发送器，
    所述处理器用于判断接收到的移动管理实体MME发送的多播业务会话启动消息中是否包含所述MCE管理的，需要启动的多播业务会话的小区的标识，在不包含所述MCE管理的，需要启动的多播业务会话的小区的标识时，调用所述发送器向MME发送多播业务会话启动响应消息，其中，所述多播业务会话启动响应消息包含用于表示所述多播业务会话启动消息中的小区列表不在MCE管理的范围内的指示信息。
  26. 根据权利要求25所述的MCE，其特征在于，所述多播业务会话启动响应消息为带超范围标记的多播业务会话启动响应信息，其中，所述超范围标记是所述多播业务会话启动响应信息中设置的字段或者位。
PCT/CN2015/093931 2015-11-05 2015-11-05 小区多播业务处理方法以及设备 WO2017075792A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
CN201580084386.1A CN108353071B (zh) 2015-11-05 2015-11-05 小区多播业务处理方法以及设备
PCT/CN2015/093931 WO2017075792A1 (zh) 2015-11-05 2015-11-05 小区多播业务处理方法以及设备
EP15907634.8A EP3361689B1 (en) 2015-11-05 2015-11-05 Cell multicast service processing method and device
US15/971,846 US10587990B2 (en) 2015-11-05 2018-05-04 Cell multicast service processing method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2015/093931 WO2017075792A1 (zh) 2015-11-05 2015-11-05 小区多播业务处理方法以及设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/971,846 Continuation US10587990B2 (en) 2015-11-05 2018-05-04 Cell multicast service processing method and device

Publications (1)

Publication Number Publication Date
WO2017075792A1 true WO2017075792A1 (zh) 2017-05-11

Family

ID=58661491

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/093931 WO2017075792A1 (zh) 2015-11-05 2015-11-05 小区多播业务处理方法以及设备

Country Status (4)

Country Link
US (1) US10587990B2 (zh)
EP (1) EP3361689B1 (zh)
CN (1) CN108353071B (zh)
WO (1) WO2017075792A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021136468A1 (zh) * 2020-01-02 2021-07-08 维沃移动通信有限公司 多播业务会话操作的方法、装置和通信设备
CN114071376A (zh) * 2020-08-03 2022-02-18 华为技术有限公司 一种通信方法、装置以及***

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113766431A (zh) * 2020-06-02 2021-12-07 海能达通信股份有限公司 增强型广播多播服务的业务调度方法及***

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101141669A (zh) * 2006-09-06 2008-03-12 华为技术有限公司 在ip无线接入网中下发多媒体广播/组播服务业务的方法
CN101179765A (zh) * 2007-12-13 2008-05-14 普天信息技术研究院有限公司 一种建立传输信道的方法、***和装置
CN101227653A (zh) * 2008-02-18 2008-07-23 普天信息技术研究院有限公司 一种管理公共传输信道的方法
KR20100069442A (ko) * 2008-12-16 2010-06-24 한국전자통신연구원 패킷기반 이동통신 시스템에서 ｍｂｍｓ 데이터 전송을 위한 베어러 설정 방법과 ｍｂｍｓ 코어 네트워크 장치 및 무선기지국

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100525529C (zh) * 2005-12-24 2009-08-05 华为技术有限公司 无线通信***中均衡负载的实现方法
CN102104836B (zh) * 2010-08-10 2014-04-02 电信科学技术研究院 Mbms业务接收状态的上报方法和设备
US8780876B2 (en) * 2010-08-13 2014-07-15 Intel Corporation Delivery of multicast and broadcast services concurrently with unicast data
CN102065376B (zh) * 2011-01-07 2013-09-11 大唐移动通信设备有限公司 接纳判决方法和设备
CN102143430B (zh) * 2011-02-15 2016-05-25 电信科学技术研究院 一种配置mbms会话位置信息的方法和装置
CN102761831B (zh) * 2011-04-27 2017-02-08 中兴通讯股份有限公司 一种多媒体广播组播业务计数方法及***
KR20150048611A (ko) * 2013-10-28 2015-05-07 삼성전자주식회사 이동성에 강인한 그룹 통신을 위한 방법 및 장치
WO2015065053A1 (en) * 2013-10-31 2015-05-07 Lg Electronics Inc. Method of receiving mbms service in wireless communication system and apparatus thereof
KR20170127448A (ko) * 2015-03-17 2017-11-21 엘지전자 주식회사 Scptm 서비스를 제공하는 셀의 리스트를 송수신하는 방법 및 장치
CN106658424B (zh) * 2015-11-02 2019-01-25 中兴通讯股份有限公司 车联网v2x业务的发送方法及装置
US11323979B2 (en) * 2016-08-09 2022-05-03 Nokia Technologies Oy Broadcasting or multicasting to user equipment that use extended idle mode discontinuous reception
CN107734606B (zh) * 2016-08-12 2023-09-01 中兴通讯股份有限公司 一种多播业务的传输方法及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101141669A (zh) * 2006-09-06 2008-03-12 华为技术有限公司 在ip无线接入网中下发多媒体广播/组播服务业务的方法
CN101179765A (zh) * 2007-12-13 2008-05-14 普天信息技术研究院有限公司 一种建立传输信道的方法、***和装置
CN101227653A (zh) * 2008-02-18 2008-07-23 普天信息技术研究院有限公司 一种管理公共传输信道的方法
KR20100069442A (ko) * 2008-12-16 2010-06-24 한국전자통신연구원 패킷기반 이동통신 시스템에서 ｍｂｍｓ 데이터 전송을 위한 베어러 설정 방법과 ｍｂｍｓ 코어 네트워크 장치 및 무선기지국

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021136468A1 (zh) * 2020-01-02 2021-07-08 维沃移动通信有限公司 多播业务会话操作的方法、装置和通信设备
CN114071376A (zh) * 2020-08-03 2022-02-18 华为技术有限公司 一种通信方法、装置以及***

Also Published As

Publication number Publication date
US10587990B2 (en) 2020-03-10
EP3361689A1 (en) 2018-08-15
EP3361689B1 (en) 2021-05-12
EP3361689A4 (en) 2018-10-24
CN108353071A (zh) 2018-07-31
CN108353071B (zh) 2020-07-07
US20180255435A1 (en) 2018-09-06

Similar Documents

Publication Publication Date Title
US20230180350A1 (en) Mode configuration method and apparatus, and device and storage medium
WO2020001572A1 (zh) 通信方法及装置
WO2021077434A1 (zh) 一种通信方法及装置
JP5241749B2 (ja) Ｍｂｍｓｕｅによって主導的にアップリンクシグナリングを開始する方法
WO2021088660A1 (zh) 通信方法、装置及设备
US9992635B2 (en) Device-to-device broadcast communication method and user equipment
CN101262630B (zh) 多媒体广播多播业务收发方法及装置
WO2021032008A1 (zh) 通信方法和通知装置
US20190149958A1 (en) Methods, Apparatuses and Computer Program for Transmission Format/Retransmission Adaptation in Wireless Network
WO2022082754A1 (zh) 一种通信方法及装置
WO2020042848A1 (zh) 一种网络切片管理方法及装置
TW201622465A (zh) 用於在蜂巢式網路中多重傳播的涵蓋範圍增加
WO2020164481A1 (zh) 一种终端装置识别方法及装置
WO2017075792A1 (zh) 小区多播业务处理方法以及设备
WO2021189260A1 (zh) 多播通信方法及通信装置
CN106488584B (zh) 一种数据发送、传输方法及装置
WO2020156052A1 (zh) 链路释放信息传输方法、装置及设备
JP2023536000A (ja) マルチキャストおよびブロードキャストサービスのための方法および装置
EP3700165B1 (en) Mbms bearer setup in a group communications system
WO2017091936A1 (zh) 一种上行数据传输的控制方法、用户终端及网络服务器
EP3577916B1 (en) Method and apparatus for transmitting and receiving data in mission critical data communication system
US20210044938A1 (en) Mbms bearer handling in a group communications system
EP3453193B1 (en) Group call setup in a group communications system
WO2022262589A1 (zh) 一种会话建立方法及装置
WO2021190233A1 (zh) 数据传输方法及装置

Legal Events

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

Ref document number: 15907634

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2015907634

Country of ref document: EP