WO2016045325A1 - 指示信息的确定、处理以及请求消息的处理方法、装置及计算机存储介质 - Google Patents

指示信息的确定、处理以及请求消息的处理方法、装置及计算机存储介质 Download PDF

Info

Publication number
WO2016045325A1
WO2016045325A1 PCT/CN2015/074801 CN2015074801W WO2016045325A1 WO 2016045325 A1 WO2016045325 A1 WO 2016045325A1 CN 2015074801 W CN2015074801 W CN 2015074801W WO 2016045325 A1 WO2016045325 A1 WO 2016045325A1
Authority
WO
WIPO (PCT)
Prior art keywords
congestion
overload
indication information
service
gcs
Prior art date
Application number
PCT/CN2015/074801
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 EP15843224.5A priority Critical patent/EP3200484B1/en
Priority to US15/513,845 priority patent/US20170295211A1/en
Publication of WO2016045325A1 publication Critical patent/WO2016045325A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/1863—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast comprising mechanisms for improved reliability, e.g. status reports
    • H04L12/1868—Measures taken after transmission, e.g. acknowledgments
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1069—Session establishment or de-establishment
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/50—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
    • G06F21/55—Detecting local intrusion or implementing counter-measures
    • G06F21/552—Detecting local intrusion or implementing counter-measures involving long-term monitoring or reporting
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/102—Gateways
    • H04L65/1023—Media gateways
    • H04L65/103—Media gateways in the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/1046—Call controllers; Call servers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/80—Responding to QoS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0289—Congestion control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/60—Subscription-based services using application servers or record carriers, e.g. SIM application toolkits
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/189—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast in combination with wireless systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0284—Traffic management, e.g. flow control or congestion control detecting congestion or overload during communication

Definitions

  • the present invention relates to the field of communications, and in particular to a method, an apparatus, and a computer storage medium for determining, processing, and requesting message information.
  • the trunking communication system is a dedicated wireless communication system developed for industrial users to command and dispatch requirements. It is a multi-purpose wireless communication system in which a large number of wireless users share a small number of wireless channels and use command and dispatch as the main application. High performance wireless communication system.
  • the trunking communication system has a wide application market in the fields of government departments, public safety, emergency telecommunications, electric power, civil aviation, petrochemicals and military.
  • the trunked communication system has undergone a similar development process as cellular mobile communication systems.
  • the first generation of cluster systems is an analog trunking communication system that mainly supports voice communication.
  • the first analog trunking communication system that entered China was the Actionet system of Nokia, which used MPT-1327 signaling and was applied in the 450MHz frequency band. Since then, Japan's F.A.S.T and the US Motorola's Smartnet have entered China, and have long occupied more than 80% of the market share of China's cluster market.
  • the second-generation cluster system is a narrow-band digital trunking communication system. It started in the 1990s and began to be deployed in China around 2004. It is the most widely used cluster communication system in China.
  • the digital trunking communication system supports voice and low-speed data (up to 28.8 kbps) communication, and the representative system is a Terrestrial Trunked Radio (TETRA) system defined by the European Telecommunications Standards Institute (ETSI).
  • TETRA Terrestrial Trunked Radio
  • ETSI European Telecommunications Standards Institute
  • iDEN Integrated Digital Enhanced Networks
  • GoTa Global Open Trunking Architecture
  • GSM Global Open Trunking Architecture
  • the distinguishing feature of a cluster system from a public system is that the cluster system needs to have efficient command and dispatch characteristics and requires high reliability and security.
  • Call control establish, maintain, and release service bearers between the calling user and the called user according to the service request of the user;
  • Authentication authentication Supports authentication and authentication.
  • the authentication function may include: network-side authentication of the terminal and network-side authentication of the terminal and the terminal to the network side;
  • the weakening of the fault When the link between the network side and the internal network element of the base station or the network side fails, the base station can provide limited cluster services for the user terminals under the coverage.
  • Network interconnection and intercommunication function It can communicate with Public Switched Telephone Network (PSTN) and public mobile communication systems (eg Global System for Mobile Communications (GSM) / Code Division Multiple Access (CDMA), Time-sharing Long Term Evolution (TD) - LTE)), Internet Protocol (IP) telephones, other types of trunking communication systems, etc.
  • PSTN Public Switched Telephone Network
  • GSM Global System for Mobile Communications
  • CDMA Code Division Multiple Access
  • TD Time-sharing Long Term Evolution
  • IP Internet Protocol
  • cluster communication is called Group Communication Service Capability (GCSE).
  • 3GPP LTE cluster communication is called Group Communication Service Capability (GCSE). 1 is a schematic diagram of a system architecture of a trunking communication system according to the related art.
  • 3GPP proposes a Multimedia Broadcast Multicast Service (MBMS), which is a technology for transmitting data from one data source to multiple target mobile terminals, and realizes the network.
  • the sharing of resources including: core network and access network
  • the MBMS service defined by 3GPP can not only realize plain text low-rate message class multicast and broadcast, but also realize high-speed multimedia service broadcast and multicast, and provide a variety of rich video, audio and multimedia services, which undoubtedly conforms to the future.
  • the trend of mobile data development provides a better business prospect for the development of 3/4G.
  • the MBMS service is characterized by a large amount of data for the service, a long duration of reception by the mobile terminal, and a constant average data rate.
  • the above characteristics determine that the scheduling and control signaling configuration of the MBMS service is semi-static, that is, the scheduling information and control signaling information of the MBMS service are "long-term" unchanged, and the information passes through the MBMS Control Channel (MBMS Control Channel). , abbreviated as MCCH) is periodically transmitted, collectively referred to as MCCH information.
  • MCCH MBMS Control Channel
  • the evolved MBMS (eMBMS) system may have multiple MCCHs, and each MCCH corresponds to a different MBSFN area, and only the MBMS service corresponding to the MBMS over a Single Frequency Network (MBMSN) area is controlled.
  • MBMSN Single Frequency Network
  • the GCS AS Group Communication Service
  • the abbreviated as AS needs to establish a unicast bearer for the affected UE, and stop the multicast bearer transmission of the affected service.
  • the GCS AS does not know the MBSFN area where the affected UE is located, but only the MBMS service area where the UE is located.
  • MBMS Mobility Management Function
  • the service area is larger than the MBSFN area
  • MBMS multicast transmission of the cluster data is stopped according to the MBMS service area
  • it may affect other UEs that do not have a congestion/overload area, how to implement the mapping from the MBMS service area to the MBSFN area, and how to reduce congestion.
  • the impact of the overloaded area UE has not yet proposed an effective solution.
  • the embodiment of the present invention provides a method, a device, and a computer storage medium for determining, processing, and requesting a message, so as to at least how to implement mapping of an MBMS service area to an MBSFN area and how to reduce congestion. / The problem of the impact of the overload area UE.
  • a method of determining indication information is provided.
  • the determining method of the indication information includes: determining that the user plane data carried by the multimedia broadcast multicast service (MBMS) is congested or overloaded, configuring the first indication information; and applying the group communication service (GCS) application server (AS) Sending the first indication information, where the first indication information is used by the GCS AS to request the multi-cell multicast coordination entity MCE or the base station (eNB) to stop the cluster service affected by the congestion or overload of the user plane data by the MBMS bearer.
  • GCS group communication service
  • AS group communication service
  • determining that the user plane data of the MBMS bearer is congested or overloaded may include: determining, when one or more eNBs detect that the user plane data is congested or overloaded, determining an MBSFN area where one or more eNBs are located. Or congestion or overload in the MBMS service area.
  • the user plane data is detected to be congested or overloaded according to the determination condition, wherein the determination condition is pre-configured or carried in the request message received from the GCS AS.
  • the content carried in the first indication information comprises at least one of: a congestion or an overload identifier; one or more cell identifiers, wherein the cell identifier comprises at least one of: an evolved unified terrestrial radio access network (E- UTRAN) cell identity, E-UTRAN cell global identity; one or more service area identity (SAI); one or more single frequency network multimedia broadcast multicast service (MBSFN) zone identity; one or more MBMS service identity; congestion Or an overload start identifier; wherein the congestion or overload identifier is used to indicate whether the load of the user plane data in the current network is in a congestion or an overload occurs, and the cell identifier is used to indicate a cell affected by congestion or overload, and the SAI is used for Indicates the MBMS service area affected by congestion or overload.
  • the MBSFN area identifier is used to indicate the congestion or overloaded MBSFN area.
  • the MBMS service identifier is used to indicate the cluster service affected by congestion or overload.
  • the sending the first indication information to the GCS AS includes: sending all the MBMS service identifiers that are congested or overloaded to the MCE, so that the MCEs are all the MBMS service identifiers according to the correspondence between the first parameter and the second parameter.
  • the MBMS service identifier to be reported is selected and reported to the GCS AS, where the first parameter is the quality of service level identifier QCI or the allocation and retention priority ARP, and the second parameter is the temporary mobility group identifier TMGI;
  • the first request message of the GCS AS reports the TMGI status information in the SAI specified in the request message.
  • the method further includes: determining whether the trigger condition for sending the first indication information to the GCS AS includes one of: in the event of a congestion or overload start event, or occurs In the case of a congestion or overload end event, the first indication information is sent to the GCS AS; after receiving the request message from the GCS AS, the first indication information is sent to the GCS AS; the request message from the GCS AS is received and A congestion or overload start event occurs, or after receiving a request message from the GCS AS and a congestion or overload end event occurs, sending the first indication information to the GCS AS; sending the first indication information to the GCS AS according to a preset period; The first indication message is sent to the GCS AS after each restart.
  • the method further includes: determining that the congestion or overload of the user plane data has been restored, configuring the second indication information, and sending the second indication information to the GCS AS, where the second indication information It is used to provide a reference for the GCS AS to select whether to send the unicast bearer or to resume the MBMS bearer.
  • a method of processing a request message is provided.
  • a method for processing a request message includes: receiving a request message from a group communication service (GCS) application server (AS), wherein the request message is received from a base station at a GCS AS for indicating that the multimedia broadcast is
  • GCS group communication service
  • the request message is used to request to stop the cluster service that is affected by the congestion or overload of the user plane data carried by the MBMS; configured according to the request message. Stop sending affected cluster services through the MBMS bearer.
  • the request message from the GCS AS is received via the Broadcast Multicast Service Center BM-SC.
  • configuring to stop the affected cluster service by using the MBMS bearer according to the request message includes: acquiring the MBSFN area and the MBMS service of the multicast bearer to be stopped according to the request message; configuring the MBSFN area and the MBMS service to stop the multicast bearer.
  • the information carried in the request message includes at least one of the following: a cell identifier, an MBMS service identifier, and a service area identifier.
  • a method of processing indication information is provided.
  • the method for processing the indication information includes: receiving indication information from the base station, where the indication information is used to indicate that the user plane data carried by the multimedia broadcast multicast service (MBMS) is congested or overloaded;
  • the Multi-Cell Multicast Coordination Entity (MCE) sends a request message, wherein the request message is used to request to stop the cluster service that is affected by congestion or overload of the user plane data carried by the MBMS.
  • MCE Multi-Cell Multicast Coordination Entity
  • the request message is sent to the MCE via a Broadcast Multicast Service Center (BM-SC).
  • BM-SC Broadcast Multicast Service Center
  • the method before sending the request message to the MCE according to the indication information, the method further includes: determining, according to the indication information, the target user equipment UE and/or the cluster service identifier that are affected by the congestion or overload of the user plane data; the user plane data is congested.
  • the unicast bearer is set up for the target UE and the cluster service corresponding to the cluster service identifier is sent through the unicast bearer; or, if the user plane data is overloaded, the cluster service corresponding to the cluster service identifier is set to be queued. Waiting for the state, until the end of the overload, and then sending; or, if the user plane data is overloaded, the resources of the existing cluster service are preempted to send the cluster service corresponding to the cluster service identifier.
  • the information carried in the request message includes at least one of the following: a cell identifier, an MBMS service identifier, and a service area identifier.
  • a determining device for indicating information is provided.
  • the determining device of the indication information includes: a configuration module, configured to determine that the user plane data carried by the multimedia broadcast multicast service (MBMS) is congested or overloaded, and configured with the first indication information; and the sending module is set to the group A communication service (GCS) application server (AS) transmits first indication information, where the first indication information is used by the GCS AS to request the multi-cell multicast coordination entity (MCE) or the base station (eNB) to stop the user plane through the MBMS bearer Provide a reference for the process of cluster services affected by congestion or overload.
  • GCS group A communication service
  • AS group A communication service
  • MCE multi-cell multicast coordination entity
  • eNB base station
  • the configuration module is configured to determine that the MBSFN area or the MBMS service area in which the user plane is located is congested or overloaded when it is detected that the user plane data is congested or overloaded.
  • the configuration module is configured to detect that the user plane data is congested or overloaded according to the determination condition, wherein the determination condition is pre-configured or carried in the request message received from the GCS AS.
  • the content carried in the first indication information includes at least one of: a congestion or overload identifier; one or more cell identifiers, wherein the cell identifier comprises at least one of: an evolved unified terrestrial radio access network (E-UTRAN) cell identity, E-UTRAN cell global identity; one or more service area identity (SAI); one or more single frequency network multimedia broadcast multicast service (MBSFN) zone identity; one or more MBMS services
  • E-UTRAN evolved unified terrestrial radio access network
  • SAI service area identity
  • MBSFN single frequency network multimedia broadcast multicast service
  • the congestion or overload indication is used, where the congestion or overload identifier is used to indicate whether the load of the user plane data in the current network is being congested or overloaded, and the cell identifier is used to indicate the cell affected by congestion or overload.
  • the SAI is used to indicate the MBMS service area affected by congestion or overload.
  • the MBSFN area identifier is used to indicate the congestion or overloaded MBSFN area.
  • the sending module configured to send the first indication information to the GCS AS, includes one of the following manners: sending all the MBMS service identifiers that are congested or overloaded to the MCE, so that the MCE is based on the correspondence between the first parameter and the second parameter.
  • the MBMS service identifier to be reported is selected from all the MBMS service identifiers and reported to the GCS AS.
  • the first parameter is the quality of service level identifier (QCI) or the allocation and retention priority (ARP), and the second parameter is the temporary mobility group.
  • the identifier (TMGI); reports the TMGI status information in the SAI specified in the first request message according to the received first request message from the GCS AS.
  • the foregoing apparatus further includes: a determining module; the determining module, the triggering condition set to determine whether the first indication information needs to be sent to the GCS AS includes one of the following: a congestion or overload start event occurs, or a congestion or overload occurs.
  • the first indication information is sent to the GCS AS; after receiving the request message from the GCSAS, the first indication information is sent to the GCS AS; when the request message from the GCS AS is received and congestion or overload occurs The event, or, after receiving the request message from the GCS AS and generating a congestion or overload termination event, sending the first indication information to the GCS AS; sending the first indication information to the GCS AS according to the preset period; after each restart Sending the first indication information to the GCS AS.
  • the configuration module is further configured to determine that the congestion or overload of the user plane data has been restored, and the second indication information is configured; the sending module is further configured to send the second indication information to the GCS AS, where the second indication information is used.
  • the GCS AS provides a reference for the manner in which the stopped cluster service continues to be sent by means of a unicast bearer or the MBMS bearer is restored.
  • a processing apparatus for requesting a message is provided.
  • a processing apparatus for a request message includes: a receiving module configured to receive a request message from a group communication service (GCS) application server (AS), wherein the request message is received at a GCS AS from a base station Indicates that the user plane data carried by the Multimedia Broadcast Multicast Service (MBMS) is congested or overloaded, and the request message is used to request to stop the cluster service that is affected by congestion or overload of the user plane data carried by the MBMS.
  • the processing module is configured to stop sending the affected cluster service through the MBMS bearer according to the request message configuration.
  • the receiving module is arranged to receive the request message from the GCS AS via the Broadcast Multicast Service Center BM-SC.
  • the processing module includes: an obtaining unit, configured to acquire an MBSFN area and an MBMS service of the multicast bearer to be stopped according to the request message; and the processing unit is configured to configure the MBSFN area and the MBMS service to stop the multicast bearer.
  • the information carried in the request message includes at least one of the following: a cell identifier, an MBMS service identifier, and a service area identifier.
  • a processing apparatus for indicating information is provided.
  • the processing device of the indication information includes: a receiving module, configured to receive, by the receiving module, indication information from the base station, where the indication information is used to indicate that the user plane data carried by the multimedia broadcast multicast service (MBMS) is congested Or overloading; the first processing module is configured to send a request message to the multi-cell multicast coordination entity (MCE) according to the indication information, where the request message is used to request to stop the congestion or overload of the user plane data caused by the MBMS bearer Cluster business.
  • MCE multi-cell multicast coordination entity
  • the first processing module is arranged to send a request message to the MCE via the Broadcast Multicast Service Center BM-SC.
  • the apparatus further includes: a determining module, configured to determine, according to the indication information, the target user equipment UE and/or the cluster service identifier that are affected by congestion or overload of the user plane data; and the second processing module is configured to be in the user plane. If the data is congested, the unicast bearer is set up for the target UE, and the cluster service corresponding to the cluster service identifier is sent through the unicast bearer; or, if the user plane data is overloaded, the cluster service corresponding to the cluster service identifier is used. Set to wait in the queue state until the end of the overload, and then send the cluster service. The resource of the existing cluster service is sent to the cluster service corresponding to the cluster service identifier.
  • a determining module configured to determine, according to the indication information, the target user equipment UE and/or the cluster service identifier that are affected by congestion or overload of the user plane data
  • the second processing module is configured to be in the user plane. If the data is congested, the unicast bearer is
  • the information carried in the request message includes at least one of the following: a cell identifier, an MBMS service identifier, and a service area identifier.
  • an embodiment of the present invention further provides a computer storage medium, where the computer storage medium stores computer executable instructions, where the computer executable instructions are used for determining, processing, and processing a request message. method.
  • the first indication information is configured to be sent to the GCS AS by using the first indication information, and the first indication information is used in the GCS AS, in the embodiment of the present invention, to determine that the user plane data of the MBMS bearer is congested or overloaded.
  • the MCE or the eNB is configured to provide a reference for the process of the cluster service that is affected by the congestion or overload of the user plane data, and how to implement the mapping between the MBMS service area and the MBSFN area in the related art and how to reduce the The problem of the impact of the congestion/overload area UE occurs, and the MBMS service multicast bearer of the MBSFN area in the MBMS service area can be modified.
  • the sending of the cluster service in the MBSFN area through the MBMS bearer is stopped to alleviate
  • the MBMS carries congestion/overload, thereby reducing the impact on non-congested/overloaded area UEs.
  • FIG. 1 is a schematic diagram of a system architecture of a trunking communication system according to the related art
  • FIG. 2 is a schematic structural diagram of an MBMS in LTE according to the related art
  • FIG. 3 is a flowchart of a method of determining indication information according to an embodiment of the present invention.
  • FIG. 4 is a schematic diagram of a process for an eNB to send congestion/overload indication information to an AS according to a preferred embodiment of the present invention
  • FIG. 5 is a flowchart of a method for processing a request message according to an embodiment of the present invention.
  • FIG. 6 is a flowchart of a method of processing indication information according to an embodiment of the present invention.
  • FIG. 7 is a flowchart of a scenario implementation modified multicast bearer method for a eNB detecting a multicast bearer congestion/overload start according to a preferred embodiment of the present invention
  • FIG. 8 is a flowchart of a method for modifying a multicast bearer for a scenario in which an eNB detects a multicast bearer congestion/overload termination, in accordance with a preferred embodiment of the present invention
  • FIG. 9 is a flowchart of a method for modifying a multicast bearer for a scenario in which a eNB periodically reports congestion/overload according to a preferred embodiment of the present invention
  • FIG. 10 is a structural block diagram of determining means for indicating information according to an embodiment of the present invention.
  • FIG. 11 is a structural block diagram of determining means for indicating information according to a preferred embodiment of the present invention.
  • FIG. 12 is a structural block diagram of a processing apparatus for requesting a message according to an embodiment of the present invention.
  • FIG. 13 is a structural block diagram of a processing apparatus for requesting a message according to a preferred embodiment of the present invention.
  • FIG. 14 is a structural block diagram of a processing apparatus for indicating information according to an embodiment of the present invention.
  • Figure 15 is a block diagram showing the structure of a processing device for indicating information according to a preferred embodiment of the present invention.
  • 16 is a schematic diagram of a modified multicast bearer system in accordance with a preferred embodiment of the present invention.
  • the MBMS of the present invention refers to evolved MBMS, ie, eMBMS, AS refers to GCS AS, and group communication refers to cluster communication, unless otherwise specified.
  • the cluster service is deployed on the GCS AS.
  • other services can be deployed on the GCS AS.
  • the present invention is abbreviated as the cluster service.
  • the MCE is configured to be a centralized MCE in the network.
  • one MCE and several eNBs exist in one MBSFNarea, and the MCE and the eNB can communicate through the M2 interface.
  • the distributed MCE means that the MCE and the eNB are set together in one MBSFN area, and it can also be understood that a specific module in the eNB can perform the function and role of the MCE. In this MBSFN area, how many eNBs are present How many MCEs.
  • the MME can communicate with the MCE module in the eNB through the M3 interface, and the M2 interface still exists as a logical interface.
  • MCE For distributed MCE architecture, coordination between MCEs is achieved through OAM.
  • the invention can be applied to a centralized or distributed MCE architecture unless otherwise stated.
  • the MCE and the eNB can communicate via the M2 interface, which actually belongs to the internal communication between the eNB and its own MCE module.
  • FIG. 3 is a flowchart of a method of determining indication information according to an embodiment of the present invention. As shown in FIG. 3, the method may include the following processing steps:
  • Step S302 The eNB determines that the user plane data carried by the MBMS is congested or overloaded, and configures the first indication information.
  • Step S304 The eNB sends the first indication information to the GCS AS, where the first indication information is used in the process that the GCSAS requests the MCE or the eNB to stop the cluster service that is affected by the congestion or overload of the user plane data by the MBMS. Reference.
  • the base station may send indication information indicating that the user plane data is congested or overloaded to the GCS AS, and the GCS AS requests the MCE according to the indication information.
  • the GCS AS requests the MCE according to the indication information.
  • the cluster service that is affected by the congestion or overload of the user plane data by the MBMS is stopped, thereby solving the related art how to implement the MBMS service area to the MBSFN area.
  • the cluster service is sent to alleviate the congestion/overload of the MBMS bearer, thereby reducing the impact on the non-congested/overloaded area UE.
  • the determining, by the eNB, that the user plane data of the MBMS bearer is congested or overloaded may include: determining, when one or more eNBs detect that the user plane data is congested or overloaded, determining the MBSFN where the one or more eNBs are located. Congestion or overload in the area or MBMS service area. That is, whether the user plane data is congested or overloaded by one or more eNBs, where congestion or overload of one or more eNBs indicates that the MBSFN area in which it is located is congested or overloaded.
  • the above congestion refers to the user plane data load reaching a preset threshold, and the overload means that the network node cannot continue to process additional user plane data load.
  • the user plane data mentioned in the present invention refers to MBMS service data on a Physical Multicast Channel (PMCH).
  • PMCH Physical Multicast Channel
  • the eNB may detect that the user plane data is congested or overloaded according to the determination condition, where the determination condition may be pre-configured by operation management and maintenance (OAM) (not limited to the message type) or carried in receiving from the GCS AS. In the request message.
  • OAM operation management and maintenance
  • the eNB may determine whether the MBMS user plane data is congested/overloaded according to a preset rule, that is, a congestion/overload determination condition is defined in advance, and if the eNB can determine that the above-mentioned predefined congestion/overload determination condition is satisfied, it may determine Congestion/overload has occurred.
  • a preset rule that is, a congestion/overload determination condition is defined in advance
  • the congestion/overload determination condition that is, the set determination rule may be carried in the indication information transmitted to the eNB, in addition to the preset manner.
  • the eNB may send congestion/overload indication information to the GCSAS through the eNodeB (eNB) ⁇ MCE ⁇ MME ⁇ MBMS GW ⁇ BM-SC ⁇ AS. That is, the eNB first sends the indication information to the MCE through the M2 interface, and the indication information can be implemented by using the existing M2 interface signaling and adding a new indication field, or directly adopting the new M2 interface signaling;
  • the existing interface signaling may be used and a new indication field may be added, or a new proprietary interface may be directly adopted. Signaling implementation.
  • the content carried in the foregoing first indication information may include, but is not limited to, at least one of the following:
  • ECI E-UTRAN Cell Identifier
  • ECGI E-UTRAN Cell Global Identifier
  • SAIs Service Area Identifiers
  • one or more MBMS service identifiers such as: Temporary Mobile Group Identity (TMGI); and/or MBMS session identifier (eg, session ID);
  • the congestion/overload identifier is used to indicate whether the network is congested or overloaded
  • the cell identifier is used to indicate a cell affected by congestion/overload
  • the SAI is used to indicate an MBMS service area affected by congestion/overload
  • the MBSFN area identifier is used to indicate congestion/overload.
  • MBSFN area, TMGI is used to indicate the cluster service affected by congestion/overload.
  • the MBSFN area identifier is only sent on the M2 interface.
  • the content of the first indication information is determined by triggering detection of congestion:
  • the first indication information needs to include: a congestion/overload identifier, a start/end identifier; and further, an area identifier and a service identifier.
  • the first indication information may include: a congestion/overload identifier, an area identifier, a service identifier, and a start/end identifier, where the area identifier may include: a cell identifier, and/or SAI, and/or MBSFN Area ID.
  • the MCE can determine the MBSFN area/service area in which the congestion occurs according to the received cell identifier and the service identifier, and the area identifier reported by the MCE to the AS includes the cell identifier and/or the service area identifier.
  • the message that the AS can send the stop service to the MCE according to the received indication information includes the received service area identifier and/or the cell identifier, and then the MCE The service of the corresponding MBSFN area is closed according to the service area identifier and/or the cell identifier received from the AS and the MBSFN area information that has been locally determined to be congested. Other area identification information is similarly processed and will not be described here.
  • the content of congestion/overload start/end may include, but is not limited to, at least one of the following:
  • Congestion/overload start/end in other words, congestion/overload start is equivalent to current congestion/overload, and congestion/overload termination is equivalent to congestion/overload that is currently not present or the congestion/overload that has started is now over.
  • Node congestion means that the MBMS user plane data load in the network reaches a preset threshold; node overload means that the network node cannot continue to process additional MBMS user plane data load.
  • the content of the MBMS service congestion/overload information may include but is limited to: assume that the congestion is indicated by C, and the overload is indicated by O, for example:
  • TMGI1, TMGI2, and TMGI3 in the cell ECI1 are congested; TMGI5 and TMGI6 in ECI2 are overloaded; and TMGI10 in ECI3 is congested.
  • the congestion/overload indication information may be modified during the sending process.
  • the cell identifier ECI is usually modified to the MBMS service area identifier SAI. If the ECI in the indication information received by the MCE is modified to SAI, the GCS AS may receive the The indication information determines the congestion/overload MBMS service area.
  • the congestion indication C may not be transmitted any more; or although the congestion indication C is transmitted, the UE may ignore the indication.
  • the sending, by the eNB, the first indication information to the GCS AS includes one of the following manners:
  • the first method is to send all the MBMS service identifiers that are congested or overloaded to the MCE, so that the MCE selects the MBMS service to be reported from all the MBMS service identifiers according to the correspondence between the first parameter and the second parameter.
  • the identifier is reported to the GCS AS, where the first parameter is the quality of service level identifier QCI or the allocation and retention priority ARP, and the second parameter is the temporary mobility group identifier TMGI;
  • Manner 2 The TMGI status information in the SAI specified in the request message is reported according to the received first request message from the GCS AS.
  • QoS quality of service
  • the business is a specific cluster business. Since the eNB does not know the QoS information of the service, there are the following two methods of reporting congestion/overload in the eNB:
  • Method 1 the eNB reports all the congestion/overload service identifiers TMGI to the MCE, and according to the TMGI of the specific service (the MCE is based on the correspondence between the QCI/ARP and the TMGI), the MCE selects the TMGI of the specific service in which the congestion/overload occurs to be reported to the GCS AS. ;
  • the eNB detects the congestion/overload and reports the affected cluster service to the AS in at least one of the following manners:
  • all the cluster services configured on the MBSFN area that is, the cluster services carried on all the PMCHs in the MBSFN area;
  • Manner 3 One or more PMCHs are carried in each MBSFN area. When the eNB detects that one or more PMCHs are congested/overloaded, the eNB reports all the cluster services configured on the PMCH.
  • Method 2 The AS requests the SAI and the TMGI to report the status, and sends a request message to the eNB through the path AS ⁇ BM-SC ⁇ MBMSGW ⁇ MME ⁇ MCE ⁇ eNB, and the eNB can pass the eNB ⁇ MCE ⁇ MME ⁇ MBMS GW ⁇ BM-SC ⁇
  • the AS reports the status of the TMGI in the specific SAI to the AS.
  • the AS request information only includes the SAI information
  • the eNB reports all the TMGI states in the SAI.
  • the method may further include:
  • Step S1 The trigger condition for the eNB to determine whether the first indication information needs to be sent to the GCS AS may include, but is not limited to, one of the following:
  • the first indication information is sent to the GCS AS;
  • Condition 2 After receiving the request message from the GCS AS, sending the first indication information to the GCS AS;
  • Condition 3 After receiving the request message from the GCS AS and generating a congestion or overload start event, or receiving the request message from the GCS AS and generating a congestion or overload termination event, sending the first indication information to the GCS AS;
  • Condition 4 sending the first indication information to the GCS AS according to a preset period
  • Condition 5 Send the first indication message to the GCS AS after each restart.
  • the above-mentioned sending triggering mode may be one of the following: event triggering, AS request triggering, event triggering, and AS request triggering, and periodic reporting, wherein the event triggering reporting refers to a network node when a network node has a congestion/overload start/end event. Reporting to the AS; AS request triggering means that the AS sends a request message to the network node, and the network node that receives the request message reports the node status information to the AS; the event trigger and the AS request triggering means that the AS sends a request message to the network node, when the network node When the congestion/overload event is detected, the report is reported to the AS.
  • the periodic report refers to the configuration reporting period. In each period, the eNB reports the node status to the AS. The reporting period can be specified in advance or the AS specifies the request message.
  • a network node When a network node has a congestion/overload start/end event, it means: transition from the start state to the end state; or, from the end state to the start state. That is, if the congestion/overload (equivalent to the last congestion/overload has ended) is not converted to the beginning (equivalent to the current congestion/overload), the eNB needs to report; if there is congestion/overload originally (etc. Depending on whether the current congestion/overload has started) to no more congestion/overload (equivalent to the current congestion/overload has ended), the eNB needs to report; and when the eNB detects that the congestion state and the overload state change from each other, The eNB also needs to report.
  • C congestion indication, using ⁇ 0,1 ⁇ identifier
  • O overload indication, using ⁇ 0,1 ⁇ identifier, as long as the C and/or O identifiers are sent, the eNB needs to report.
  • the eNB may restart after the failure, and the eNB has a congestion/overload change, but the eNB does not know. Therefore, the eNB always needs to report the congestion/overload indication information after each restart.
  • the eNB reports congestion/overload indication information to the AS.
  • ⁇ ECI2/MBSFN area ID 1/SAI 1; TMGI2, TMGI3; C; true ⁇ that is, TMGI2 and TMGI3 in ECI2 in the MBSFN area 1 in SAI1 are congested.
  • the AS After receiving the congestion/overload indication information ⁇ ECI2/SAI1; TMGI2, TMGI3; C; true ⁇ , the AS determines that TMGI2 and TMGI3 in the cell ECI2 in SAI1 are congested.
  • the following steps may also be included:
  • Step S2 The eNB determines that the congestion or overload of the user plane data has been restored, and configures the second indication information.
  • Step S3 The eNB sends the second indication information to the GCS AS, where the second indication information is used to provide a reference for the GCS AS to select whether the stopped cluster service continues to be sent by using the unicast bearer or the MBMS bearer is resumed. in accordance with.
  • Congestion/overloading means that the network is back to normal. For example, the user plane data load does not meet the preset congestion/overload condition.
  • the eNB may send congestion/overload termination (recovery) indication information to the GCSAS through the eNodeB (eNB) ⁇ MCE ⁇ MME ⁇ MBMS GW ⁇ BM-SC ⁇ AS.
  • eNB eNodeB
  • the foregoing congestion/overload end indication information may include, but is not limited to, at least one of the following:
  • ECI E-UTRAN Cell Identifier
  • ECGI E-UTRAN Cell Global Identifier
  • SAIs Service Area Identifiers
  • one or more MBMS service identifiers such as: Temporary Mobile Group Identity (TMGI); and/or MBMS session identifier (eg, session ID);
  • the above-mentioned sending triggering mode may be one of the following: event triggering, AS request triggering, event triggering, and AS request triggering, and periodic reporting, wherein the event triggering reporting refers to a network node when a network node has a congestion/overload start/end event.
  • AS request triggering means that the AS sends a request message to the network node and receives it.
  • the network node of the request message reports the node status information to the AS;
  • the event triggering and the AS request triggering means that the AS sends a request message to the network node, and when the network node detects the congestion/overload event, it reports to the AS;
  • the periodic report refers to the configuration reporting period.
  • the eNB reports the node status to the AS in each period, and the reporting period may be specified in advance or the AS specifies when sending the request message.
  • FIG. 5 is a flowchart of a method of processing a request message according to an embodiment of the present invention. As shown in FIG. 5, the method may include the following processing steps:
  • Step S502 The MCE or the eNB receives the request message from the GCS AS, where the request message is sent after the GCS AS receives the indication information indicating that the user plane data carried by the MBMS is congested or overloaded, and the request message is sent by the GCS AS. Used to request to stop cluster services that are affected by congestion or overload of user plane data carried over the MBMS;
  • Step S504 The MCE or the eNB configures to stop sending the affected cluster service through the MBMS bearer according to the request message configuration.
  • the MCE or the eNB may determine, by using the received request message and the local database, the MBSFN area and the MBMS service that need to stop the multicast bearer, such as the MBSFN in the congestion/overload indication information sent by the eNB on the M2 interface.
  • Area ID and TMGI Area ID and TMGI.
  • the MCE receives the request message from the MME including ⁇ ECI2/SAI1; TMGI2, TMGI3 ⁇ , and the ECI2 belongs to two MBSFN areas, and the MCE knows that the MBSFN area 1 is congested, the MCE determines that the MBSFN is to be MBSFN.
  • TMGI2 and TMGI3 of Area 1 stop multicast transmission.
  • the MCE then transmits MBMS Scheduling information to the eNB in the MBSFN area 1, and deletes TMGI2 and TMGI3 in the above message.
  • the eNB receiving the MBMS Scheduling information transmits the updated MCCH information in the MBSFN area 1, and deletes the TMGI2 and the TMGI3 in the updated MCCH information, and the affected UE in the MBSFN area 1 receives the updated MCCH information, and determines the corresponding MBMS service. Deleted, that is, the corresponding cluster service TMGI2/TMGI3 stops sending on the multicast bearer.
  • FIG. 6 is a flowchart of a method of processing indication information according to an embodiment of the present invention. As shown in FIG. 6, the method may include the following processing steps:
  • Step S602 The GCS AS receives the indication information from the base station, where the indication information is used to indicate that the user plane data carried by the MBMS bearer of the multimedia broadcast multicast service is congested or overloaded;
  • Step S604 The GCS AS sends a request message to the MCE according to the indication information, where the request message is used to request to stop the cluster service that is affected by the congestion or overload of the user plane data by the MBMS.
  • the AS may request the MCE to stop the MBMS bearer of the affected service through the BM-SC.
  • the AS Before the AS sends the foregoing request message, the AS first determines the affected target UE and the cluster service TMGI according to the congestion/overload indication information, and then the AS determines the action to be taken according to the congestion/overload indication information and the local policy, when congestion occurs.
  • a unicast bearer is set up for the target UE, and the cluster service is sent through the unicast bearer.
  • the AS queues the cluster service for overload and then sends the packet, or the AS uses the high-priority cluster service to preempt the existing cluster service. Resources.
  • the AS sends a request message to the MME by using the BM-SC ⁇ MBMS GW ⁇ MME path, where the request message is used to stop the multicast bearer.
  • the information carried in the request message may include at least one of the following: a cell identifier, an MBMS service identifier, where The cell identifier and/or the MBMS service identifier is a cell identifier ECI and a service identifier TMGI in the congestion/overload indication information received by the AS.
  • the MBMS GW sends a request message to all MMEs in the area, and the MME determines whether it is the cell to which it belongs according to the cell identifier in the request message. If not, the MME discards the received request message.
  • the MME selects the MCE according to the cell identity and sends a request message. The MME can obtain the MCE to which the cell belongs by using the M3 interface message.
  • the foregoing request message may be implemented by an existing process or a new process, where the existing process is: an MBMS session stop request or an MBMS session update adds a cell identity field in an existing process.
  • a request message is sent to the MME through the BM-SC ⁇ MBMS GW ⁇ MME path, and the request message is used to stop the MBMS bearer.
  • the MBMS GW may send a request message to all MMEs in the area. Considering that the request message carries the identifier of the target cell, the MME can determine whether the target cell belongs to its own range and send a response message to the MBMS GW.
  • the MME sends a response message to the AS indicating that the MME has successfully/failed to receive the request message. If the response message indicates a failure, the AS/BM-SC/MBMS GW will resend the request message.
  • the AS may choose to send the cluster service to the UE.
  • the AS determines the affected target UE by using the foregoing restoration indication information, and selects an appropriate manner to send the cluster service to the target UE. For example: continue to send cluster services through unicast bearer or resume MBMS bearer.
  • the GCS AS can first establish a PTP bearer to the affected UE and then release the PTM bearer of the cluster service.
  • the MCE may also be a distributed MCE.
  • the MCE is set in the eNB, which is equivalent to a specific module in the eNB to complete the function of the MCE.
  • FIG. 7 is a flow chart of a method for modifying a multicast bearer for a scenario in which an eNB detects a multicast bearer congestion/overload start, in accordance with a preferred embodiment of the present invention. As shown in FIG. 7, the process may include the following processing steps:
  • Step S702 Select a base station eNB that detects congestion/overload.
  • the entity performing the selection may be one of: selected by the MCE, selected by the GCS AS, selected by the O&M.
  • the above congestion/overload refers to congestion/overload of the user plane data service of the MBMS, and the criterion for congestion/overload needs to be formulated and notified to the target eNB in advance.
  • the criterion may be carried in the indication information.
  • MBMS user plane data congestion/overload occurs in the MBSFN area, considering that all eNBs participating in the MBSFN transmission in the MBSFN area have the same resource configuration, all eNBs are congested/overloaded. If the congestion/overload indication is reported on the M2 interface, the reported content is the same. Therefore, it is not necessary for all eNBs to report the congestion/overload indication. If an eNB reports congestion/overload in an MBSFN area, the MBSFN area/MBMS service area can be determined. Congestion, that is, all congestion/overload information can be inferred based on partial congestion/overload information, thereby not only improving detection efficiency, but also reducing network signaling load.
  • the eNB may be one or more.
  • an eNB may be selected in one MBSFN area, and the notification may be implemented by using O&M or signaling.
  • the selected eNB When the eNB selects the eNB, the selected eNB is not congested/overloaded, but the target MBMS service area may still be congested/overloaded.
  • the target MBMS service area has multiple MBSFN areas, and the MBSFN area where the eNB is located is not congested/overloaded. Congestion/overload occurs in the MBSFN area, but the GCS AS does not know the MBSFN area configuration. In order to avoid this as much as possible, the GCS AS can select multiple eNBs to detect congestion/overload.
  • the eNB is an eNB in a specific MBMS service area. Generally, there are multiple eNBs in the MBMS service area. In this case, any eNB can be selected to monitor congestion/overload.
  • a target MBMS service area is generally also specified; a target MBMS service area is an area that needs to detect congestion/overload; and an MBMS service area is a Service Area Identifier (SAI), if The MBMS service area is not specified.
  • SAI Service Area Identifier
  • the selected eNB monitors the congestion/overload status of all MBMS service areas in which it is located.
  • the selected eNB may also indicate by the cell identity that the eNB is located by the cell identity.
  • MBMS bearer MBSFN bearer
  • multicast bearer multicast bearer
  • PTM bearer Point To Multipoint
  • the MBMS bearer may include: a core network bearer (ie, an Evolved Packet Core network (EPC) bearer) and an air interface bearer, and the RAN (base station eNB and/or MCE) configures the MBMS air interface resource, and sends the MBMS in the air interface. Configuration information and cluster data.
  • EPC Evolved Packet Core network
  • the data plane service in which congestion/overload occurs may be a normal MBMS service or a GCS service, and the ordinary MBMS service and the GCS service may be distinguished by different Quality of Service Level Indicator (QCI) parameters.
  • QCI Quality of Service Level Indicator
  • Step S704 The eNB detects the multicast bearer congestion/overload.
  • the user plane data in the present invention refers to the MBMS service data on the physical multicast channel (PMCH). .
  • the eNB may determine the congestion/overload of the MBMS user plane data according to a preset rule, that is, the congestion/overload condition is defined in advance, and the eNB determines that the congestion/overload occurs when the condition is satisfied.
  • the foregoing congestion/overload condition that is, the set judgment rule, may be carried in the indication information sent to the eNB in addition to being set in advance.
  • Step S706 The eNB sends congestion/overload indication information to the AS.
  • the eNB may send congestion/overload indication information to the GCSAS through the eNodeB (eNB) ⁇ MCE ⁇ MME ⁇ MBMS GW ⁇ BM-SC ⁇ AS. That is, the eNB first sends the indication information to the MCE through the M2 interface, and the indication information can be implemented by using the existing M2 interface signaling and adding a new indication field, or directly adopting the new M2 interface signaling;
  • the existing interface signaling may be used and a new indication field may be added, or a new proprietary interface may be directly adopted. Signaling implementation.
  • the foregoing congestion/overload indication information may include, but is not limited to, at least one of the following:
  • a cell identifier such as an E-UTRAN Cell Identifier (ECI) or an E-UTRAN Cell Global Identifier (ECGI);
  • SAI Service Area Identifier
  • MBMS service identifier for example, Temporary Mobile Group Identity (TMGI);
  • the congestion/overload identifier is used to indicate whether the network is congested or overloaded
  • the cell identifier is used to indicate a cell affected by congestion/overload
  • the SAI is used to indicate an MBMS service area affected by congestion/overload
  • the MBSFN area identifier is used to indicate congestion/overload.
  • MBSFN area, TMGI is used to indicate the cluster service affected by congestion/overload.
  • the MBSFN area identifier is only sent on the M2 interface.
  • the content of congestion/overload start/end may include, but is not limited to, at least one of the following:
  • Congestion/overload start/end in other words, congestion/overload start is equivalent to current congestion/overload, and congestion/overload termination is equivalent to congestion/overload that is currently not present or the congestion/overload that has started is now over.
  • Node congestion means that the MBMS user plane data load in the network reaches a preset threshold; node overload means that the network node cannot continue to process additional MBMS user plane data load.
  • the content of the MBMS service congestion/overload information may include but is limited to: assume that the congestion is indicated by C, and the overload is indicated by O, for example:
  • TMGI1, TMGI2, and TMGI3 in the cell ECI1 are congested; TMGI5 and TMGI6 in ECI2 are overloaded; and TMGI10 in ECI3 is congested.
  • the congestion/overload indication information may be modified during the sending process.
  • the cell identifier ECI is usually modified to the MBMS service area identifier SAI. If the ECI in the indication information received by the MCE is modified to SAI, the GCS AS may receive the The indication information determines the congestion/overload MBMS service area.
  • the congestion indication C may not be transmitted any more; or although the congestion indication C is transmitted, the UE may ignore the indication.
  • QoS quality of service
  • the business is a specific cluster business. Since the eNB does not know the QoS information of the service, there are the following two methods of reporting congestion/overload in the eNB:
  • Method 1 the eNB reports all the congestion/overload service identifiers TMGI to the MCE, and according to the TMGI of the specific service (the MCE is based on the correspondence between the QCI/ARP and the TMGI), the MCE selects the TMGI of the specific service in which the congestion/overload occurs to be reported to the GCS AS. ;
  • Method 2 The AS requests the SAI and the TMGI to report the status, and sends a request message to the eNB through the path AS ⁇ BM-SC ⁇ MBMSGW ⁇ MME ⁇ MCE ⁇ eNB, and the eNB can pass the eNB ⁇ MCE ⁇ MME ⁇ MBMS GW ⁇ BM-SC ⁇
  • the AS reports the status of the TMGI in the specific SAI to the AS.
  • the AS request information only includes the SAI information
  • the eNB reports all the TMGI states in the SAI.
  • the above-mentioned sending triggering mode may be one of the following: event triggering, AS request triggering, event triggering, and AS request triggering, and periodic reporting, wherein the event triggering reporting refers to a network node when a network node has a congestion/overload start/end event. Reporting to the AS; AS request triggering means that the AS sends a request message to the network node, and the network node that receives the request message reports the node status information to the AS; the event trigger and the AS request triggering means that the AS sends a request message to the network node, when the network node When the congestion/overload event is detected, the report is reported to the AS.
  • the periodic report refers to the configuration reporting period. In each period, the eNB reports the node status to the AS. The reporting period can be specified in advance or the AS specifies the request message.
  • a network node When a network node has a congestion/overload start/end event, it means: transition from the start state to the end state; or, from the end state to the start state. That is, if the congestion/overload (equivalent to the last congestion/overload has ended) is not converted to the beginning (equivalent to the current congestion/overload), the eNB needs to report; if there is congestion/overload originally (etc. Depending on whether the current congestion/overload has started) to no more congestion/overload (equivalent to the current congestion/overload has ended), the eNB needs to report; and when the eNB detects that the congestion state and the overload state change from each other, The eNB also needs to report.
  • C congestion indication, using ⁇ 0,1 ⁇ identifier
  • O overload indication, using ⁇ 0,1 ⁇ identifier, as long as the C and/or O identifiers are sent, the eNB needs to report.
  • the eNB does not need to report any more, so that the AS can always accurately grasp the congestion/overload state of the MBMS.
  • Step S708 The AS sends a request message to the MME through the BM-SC.
  • the AS Before the AS sends the foregoing request message, the AS first determines the affected target UE and the cluster service TMGI according to the congestion/overload indication information, and then the AS determines the action to be taken according to the congestion/overload indication information and the local policy, when congestion occurs.
  • a unicast bearer is set up for the target UE, and the cluster service is sent through the unicast bearer.
  • the AS queues the cluster service for overload and then sends the packet, or the AS uses the high-priority cluster service to preempt the existing cluster service. Resources.
  • the AS sends a request message to the MME by using the BM-SC ⁇ MBMS GW ⁇ MME path, where the request message is used to stop the multicast bearer.
  • the information carried in the request message may include at least one of the following: a cell identifier, an MBMS service identifier, where The cell identifier and/or the MBMS service identifier is a cell identifier ECI and a service identifier TMGI in the congestion/overload indication information received by the AS.
  • the foregoing request message may be implemented by an existing process or a new process, where the existing process is: an MBMS session stop request or an MBMS session update adds a cell identity field in an existing process.
  • a request message is sent to the MME through the BM-SC ⁇ MBMS GW ⁇ MME path, and the request message is used to stop the MBMS bearer.
  • the MBMS GW may send a request message to all MMEs in the area.
  • the MME may determine whether the target cell belongs to its own range, and if yes, proceed to step S10. Otherwise, the MME discards the received request message and sends a response message to the MBMS GW.
  • the MME sends a response message to the AS indicating that the MME has successfully/failed to receive the request message. If the response message indicates a failure, the AS/BM-SC/MBMS GW will resend the request message.
  • Step S710 The MME sends a request message to the target MCE.
  • the MME may determine the target MCE according to the cell identifier and the MCE report information.
  • the M3 installation request (M3setup request) or the M3 configuration update (M3CONFIGURATION UPDATE) message sent by the MCE to the MME includes an ECI/ECGI list, where the ECI/ECGI list is The cell identifier supported by the MCE, the MCE can obtain the cell identity supported by the eNB through the message sent by the eNB on the M2 interface, for example, an M2 installup request or an M2eNB CONFIGURATION UPDATE message.
  • the MCE sends a response message to the MME indicating that the request message has been successfully/failed. If the response message indicates a failure, the MME will resend the request message to the MCE.
  • Step S712 The MCE configuration stops the multicast bearer in the MBSFN area.
  • the MCE can determine the MBSFN area that needs to stop the multicast bearer by using the received request message and the local database. For example, the eNB sends a congestion/overload MBSFN area identifier on the M2 interface.
  • the request message received by the MCE includes ⁇ ECI2; TMGI2, TMGI3 ⁇ . Since the ECI2 belongs to two MBSFN areas, but the MCE knows that the MBSFN area 1 is congested, the MCE determines to stop transmitting the multicast of the TMGI2 and TMGI3 of the MBSFN area 1. send. Then, the MCE sends MBMS scheduling information (MBMS Scheduling information) to the eNB in the MBSFN area 1, and deletes the TMGI2 and the TMGI3 in the above message; the eNB that receives the MBMS Scheduling information transmits the updated MCCH information in the MBSFN area 1, and is updated.
  • MBMS Scheduling information MBMS Scheduling information
  • the MCCH information is deleted from the TMCH2 and the TMGI3.
  • the affected UE in the MBSFN area 1 receives the updated MCCH information, and determines that the corresponding MBMS service has been deleted, that is, the corresponding cluster service stops transmitting on the multicast bearer.
  • Step S714 The MCE sends a response message to the AS.
  • the MCE may send a request response message to the GCS AS through the MCE ⁇ MME ⁇ MBMS GW ⁇ BM-SC ⁇ AS to indicate that the request message of the AS has succeeded/failed to execute. If the response message indicates a failure, the AS may resend the request message to the MCE.
  • Step S716 The AS stops sending the cluster service through the multicast bearer.
  • the cluster service is a cluster service that is affected by congestion/overload.
  • FIG. 8 is a flow diagram of a method for modifying a multicast bearer for a scenario in which an eNB detects a multicast bearer congestion/overload termination, in accordance with a preferred embodiment of the present invention. As shown in FIG. 8, the process may include the following processing steps:
  • Step S802 The eNB detects the end of congestion/overload.
  • Congestion/overloading means that the network is back to normal. For example, the user plane data load does not meet the preset congestion/overload condition.
  • Step S804 The eNB sends the restoration indication information to the AS.
  • the eNB may send congestion/overload indication information to the GCSAS through the eNodeB (eNB) ⁇ MCE ⁇ MME ⁇ MBMS GW ⁇ BM-SC ⁇ AS.
  • eNB eNodeB
  • the foregoing congestion/overload indication information may include, but is not limited to, at least one of the following:
  • ECI E-UTRAN Cell Identifier
  • ECGI E-UTRAN Cell Global Identifier
  • SAIs Service Area Identifiers
  • one or more MBMS service identifiers such as: Temporary Mobile Group Identity (TMGI); and/or MBMS session identifier (eg, session ID);
  • the above-mentioned sending triggering mode may be one of the following: event triggering, AS request triggering, event triggering, and AS request triggering, and periodic reporting, wherein the event triggering reporting refers to a network node when a network node has a congestion/overload start/end event.
  • AS request triggering means that the AS sends a request message to the network node, and the network node that receives the request message reports the node status information to the AS;
  • periodic reporting is The configuration reporting period is performed, and the eNB reports the node status to the AS in each period, and the reporting period can be specified in advance or the AS specifies when sending the request message.
  • Step S806 The AS determines whether to resume the multicast bearer, and if yes, proceeds to step S808, otherwise, proceeds to step S816.
  • the AS determines the affected target UE by using the foregoing restoration indication information, and selects an appropriate manner to send the cluster service to the target UE. For example, the unicast bearer or the re-establishment of the MBMS bearer to send the cluster service, and the specific bearer mode is determined by the AS implementation.
  • Step S808 The AS sends a request message to the MCE through the BM-SC.
  • the request message is used to establish an MBMS bearer for the cluster service, where the request message may include at least one of the following: a cell identifier/SAI, a TMGI.
  • Step S810 The MCE determines whether a new MBSFN area is established, and if yes, proceeds to step S816, otherwise, proceeds to step S814.
  • the MCE may determine whether a new MBSFN area needs to be established according to the received request message and/or the OAM information and/or the operator policy. For example, if the existing MBSFN area does not include the requesting cell, a new MBSFN area is established, otherwise the original MBSFN is modified. region.
  • Step S812 The MCE establishes a new MBSFN area, and the AS sends the cluster service through the MBMS bearer.
  • the AS sends the cluster service to the UE in the new MBSFN through the MBMS bearer.
  • the new MBSFN area may contain the TMGI in the request cell and request message.
  • Step S814 The MCE modifies the MBSFN area, and the AS sends the cluster service in the MBSFN area.
  • the modification means that the existing MBSFN area contains the requested cell, and the requested TMGI is configured in the existing MBSFN area, and the AS sends the cluster service to the UE in the existing MBSFN area.
  • Step S816 The AS continues to send the cluster service through the unicast bearer.
  • the AS does not establish an MBMS bearer and continues to send the cluster service through the unicast bearer.
  • FIG. 9 is a flowchart of a method for modifying a multicast bearer for a scenario in which an eNB periodically reports congestion/overload according to a preferred embodiment of the present invention. As shown in FIG. 9, the process may include the following processing steps:
  • Step S902 Select an eNB that reports congestion/overload.
  • Step S904 The eNB determines whether congestion/overload occurs within the preset period. If yes, the process proceeds to step S906, otherwise, the process proceeds to step S912.
  • the preset period is used by the eNB to report the indication information to the AS.
  • the preset period can be set by the OAM or the AS.
  • the eNB needs to report the indication information to the AS even if the eNB does not detect the congestion/overload in the preset period.
  • the eNB detects the MBMS air interface user plane bearer, that is, whether congestion/overload occurs on the PMCH.
  • Step S906 The eNB reports congestion/overload information to the AS.
  • the congestion/overload indication information is sent to the GCS AS through the path eNodeB (eNB) ⁇ MCE ⁇ MME ⁇ MBMS GW ⁇ BM-SC ⁇ AS.
  • the indication information sent by the foregoing interface may use existing signaling and add a new field, or directly adopt new interface signaling.
  • the indication information may include at least one of the following: ECI, SAI, MBSFN area ID, TMGI, congestion/overload start identifier.
  • Step S908 The AS requests the MCE to modify the affected multicast bearer.
  • the AS receiving the indication information may send a request message to the MCE through the path AS ⁇ BM-SC ⁇ MBMS GW ⁇ MME ⁇ MCE: modify the affected multicast bearer.
  • Step S910 The MCE modifies the multicast bearer in the MBSFN area.
  • the MCE modifies the multicast bearer by using the MBMS Scheduling information, for example, deleting the TMGI in the affected MBSFN area; after receiving the MBMS Scheduling information, the eNB sends the updated MCCH message, and the UE that receives the updated MCCH message determines the corresponding MBMS service. Multicast delivery has been stopped.
  • Step S912 The eNB reports the indication information to the AS, and continues to monitor.
  • the eNB sends the indication information to the GCS AS through the path eNB ⁇ MCE ⁇ MME ⁇ MBMS GW ⁇ BM-SC ⁇ AS; the indication information sent by the interface may be an existing letter. Order and add new fields, or directly implement the new interface signaling.
  • the indication information may include at least one of the following: ECI, SAI, MBSFN area ID, TMGI, congestion/overload end identifier.
  • the eNB continues to monitor congestion/overload, returning to step S904.
  • FIG. 10 is a block diagram showing the structure of determining means for indicating information according to an embodiment of the present invention.
  • the device may be applied to the eNB.
  • the determining device may include: a configuration module 10 configured to determine that the user plane data of the MBMS bearer is congested or overloaded, and configure the first indication information;
  • the first indication information is sent to the GCSAS, where the first indication information is used to provide a reference basis in the process that the GCS AS requests the MCE or the eNB to stop the cluster service affected by the MBMS bearer due to congestion or overload of the user plane data. .
  • the configuration module 10 is configured to determine that the MBSFN area or the MBMS service area in which the user plane is located is congested or overloaded when it is detected that the user plane data is congested or overloaded.
  • the configuration module 10 is configured to detect congestion or overload of the user plane data according to the determination condition, wherein the determination condition is pre-configured or carried in the request message received from the GCS AS.
  • the content carried in the first indication information includes at least one of the following:
  • cell identifier comprises at least one of: an evolved unified terrestrial radio access network (E-UTRAN) cell identifier, and an E-UTRAN cell global identifier;
  • E-UTRAN evolved unified terrestrial radio access network
  • SAI business area identifiers
  • MMSFN single frequency network multimedia broadcast multicast service
  • the congestion or overload identifier is used to indicate whether the load of the user plane data in the current network is in the event of congestion or an overload
  • the cell identifier is used to indicate the cell affected by congestion or overload
  • the SAI is used to indicate that congestion or overload occurs.
  • the MBMS service area is used to indicate the congestion or overloaded MBSFN area.
  • the MBMS service identifier is used to indicate the cluster service affected by congestion or overload.
  • the sending module 20 is configured to send the first indication information to the GCS AS, including one of the following ways:
  • the first method is to send all the MBMS service identifiers that are congested or overloaded to the MCE, so that the MCE selects the MBMS service identifier to be reported from all the MBMS service identifiers according to the correspondence between the first parameter and the second parameter, and reports the MBMS service identifier to the GCS AS.
  • the first parameter is a quality of service level identification QCI or an allocation and retention priority ARP
  • the second parameter is a temporary mobility group identifier TMGI;
  • Manner 2 The TMGI status information in the SAI specified in the first request message is reported according to the received first request message from the GCS AS.
  • the foregoing apparatus further includes: a determining module 30; the determining module 30, the triggering condition set to determine whether the first indication information needs to be sent to the GCS AS includes one of the following:
  • the first indication information is sent to the GCS AS;
  • Condition 2 After receiving the request message from the GCS AS, sending the first indication information to the GCS AS;
  • Condition 3 After receiving the request message from the GCS AS and generating a congestion or overload start event, or receiving the request message from the GCS AS and generating a congestion or overload termination event, sending the first indication information to the GCS AS;
  • Condition 4 sending the first indication information to the GCS AS according to a preset period
  • Condition 5 Send the first indication message to the GCS AS after each restart.
  • the configuration module 10 is further configured to determine whether the congestion or overload of the user plane data has been restored, and the second indication information is configured.
  • the sending module 20 is further configured to send the second indication information to the GCS AS, where the second indication is The information is used to provide a reference for the GCS AS to select whether the stopped cluster service continues to be sent by means of a unicast bearer or the MBMS bearer is restored.
  • FIG. 12 is a structural block diagram of a processing apparatus for requesting a message according to an embodiment of the present invention.
  • the apparatus may be applied to the MCE.
  • the processing apparatus of the request message may include: a receiving module 40 configured to receive a request message from the group communication service GCS application server AS, where the request message is in the GCS After receiving the indication information indicating that congestion or overload of the user plane data carried by the multimedia broadcast multicast service MBMS is received from the base station, the AS is requested to stop the congestion or overload of the user plane data caused by the MBMS bearer.
  • the cluster service is affected; the processing module 50 is configured to stop sending the affected cluster service through the MBMS bearer according to the request message configuration.
  • the receiving module 40 is arranged to receive the request message from the GCS AS via the broadcast multicast service center BM-SC.
  • the processing module 50 may include: an obtaining unit 500, configured to acquire an MBSFN area and an MBMS service of the multicast bearer to be stopped according to the request message and the local database; and the processing unit 502 is configured to stop multicasting The bearer MBSFN area and the MBMS service are configured.
  • the information carried in the request message may include at least one of the following: a cell identifier, an MBMS service identifier, and a service area identifier.
  • FIG. 14 is a block diagram showing the structure of a processing device for indicating information according to an embodiment of the present invention.
  • the device may be applied to the GCS AS.
  • the processing device of the indication information may include: a receiving module 60, configured to receive, by the receiving module, indication information from the base station, where the indication information is used to indicate multimedia broadcast multicast.
  • the user plane data carried by the service MBMS is congested or overloaded.
  • the first processing module 70 is configured to send a request message to the MCE according to the indication information, where the request message is used to request to stop congestion or overload due to user plane data carried by the MBMS. Affected cluster business.
  • the first processing module 70 is arranged to send a request message to the MCE via the Broadcast Multicast Service Center BM-SC.
  • the apparatus may further include: a determining module 80 configured to determine, according to the indication information, the target user equipment UE and/or the cluster service identifier affected by congestion or overload of the user plane data;
  • the processing module 90 is configured to: when the user plane data is congested, establish a unicast bearer for the target UE, and send the cluster service corresponding to the cluster service identifier by using the unicast bearer; or, if the user plane data is overloaded, The cluster service corresponding to the cluster service identifier is set to the queue waiting state until the overload is completed. Otherwise, if the user plane data is overloaded, the resource transmission of the existing cluster service is corresponding to the cluster service identifier.
  • Cluster business configured to determine, according to the indication information, the target user equipment UE and/or the cluster service identifier affected by congestion or overload of the user plane data.
  • the information carried in the request message may include at least one of the following: a cell identifier, an MBMS service identifier, and a service area identifier.
  • FIG. 16 is a schematic diagram of a modified multicast bearer system according to a preferred embodiment of the present invention.
  • the modified multicast bearer system may include: AS1, configured to receive congestion/overload indication information sent by the RAN, and send a modified multicast bearer request message to the EPC; and select a bearer mode for sending the cluster service. ; and also used to send cluster business data.
  • EPC 2 which may include, but is not limited to: BM-SC, MBMS-GW, MME, configured to forward control messages between the AS and the RAN; for receiving a modified multicast bearer request message sent by the AS; and also for internal EPC Messaging.
  • the RAN 3 which may include, but is not limited to, an MCE and an eNB, is configured to modify a multicast bearer, wherein the eNB is configured to detect congestion/overload and send cluster service data and configuration information to the UE.
  • the user equipment UE 4 is configured to receive the modified multicast bearer indication information sent by the RAN, and receive the cluster service data sent by the AS.
  • the embodiment of the invention further describes a computer storage medium, wherein the computer storage medium stores computer executable instructions, and the computer executable instructions are configured to perform the determining method of the indication information as shown in FIG. 3, or The processing method of the request message shown in FIG. 5 or the processing method of the indication information as shown in FIG. 6.
  • the disclosed apparatus and method may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner such as: multiple units or components may be combined, or Can be integrated into another system, or some features can be ignored or not executed.
  • the coupling, or direct coupling, or communication connection of the components shown or discussed may be indirect coupling or communication connection through some interfaces, devices or units, and may be electrical, mechanical or other forms. of.
  • the units described above as separate components may or may not be physically separated, and the components displayed as the unit may or may not be physical units, that is, may be located in one place or distributed to multiple network units; Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may be separately used as one unit, or two or more units may be integrated into one unit;
  • the unit can be implemented in the form of hardware or in the form of hardware plus software functional units.
  • the foregoing program may be stored in a computer readable storage medium, and the program is executed when executed.
  • the foregoing storage medium includes: a mobile storage device, a random access memory (RAM), a read-only memory (ROM), a magnetic disk, or an optical disk.
  • RAM random access memory
  • ROM read-only memory
  • magnetic disk or an optical disk.
  • optical disk A medium that can store program code.
  • the above-described integrated unit of the present invention may be stored in a computer readable storage medium if it is implemented in the form of a software function module and sold or used as a standalone product.
  • the technical solution of the embodiments of the present invention may be embodied in the form of a software product in essence or in the form of a software product, which is stored in a storage medium and includes a plurality of instructions for making
  • a computer device which may be a personal computer, server, or network device, etc.
  • the foregoing storage medium includes various media that can store program codes, such as a mobile storage device, a RAM, a ROM, a magnetic disk, or an optical disk.
  • the congestion/overload indication information may be sent to the GCS AS through the MCE.
  • the GCS AS may request the MCE to stop sending the affected cluster service through the MBMS bearer through the BM-SC.
  • MCE receiving a stop request The configuration stops sending affected cluster services through the MBMS bearer in the affected MBSFN area.
  • the congestion/overload recovery indication information may also be sent to the AS through the MCE. Therefore, the MBMS service multicast bearer of the MBSFN area in the MBMS service area can be modified.
  • the affected cluster service is sent in the MBSFN area through the MBMS bearer to alleviate the MBMS bearer congestion/overload. Reduce the impact on UEs in non-congested/overloaded areas.
  • modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
  • the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module.
  • the invention is not limited to any specific combination of hardware and software.
  • the method, apparatus, and computer storage medium for determining, processing, and requesting message information of the indication information have the following beneficial effects: enabling MBMS service multicasting of the MBSFN area in the MBMS service area to be modified.
  • the bearer stops transmitting the affected cluster service through the MBMS bearer in the MBSFN area when the MBMS bearer congestion/overload occurs to alleviate the MBMS bearer congestion/overload, thereby reducing the impact on the non-congested/overload area UE.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Software Systems (AREA)
  • Computer Hardware Design (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本发明公开了一种指示信息的确定、处理以及请求消息的处理方法、装置及计算机存储介质，在上述方法中，确定MBMS承载的用户面数据是否发生拥塞或过载，配置第一指示信息；向GCS AS发送第一指示信息，其中，第一指示信息用于在GCS AS请求MCE或eNB停止通过MBMS承载的因用户面数据发生拥塞或过载而受到影响的集群业务的过程中提供参考依据。根据本发明提供的技术方案，能够缓解MBMS承载拥塞/过载，从而减少对非拥塞/过载区域UE的影响。

Description

指示信息的确定、处理以及请求消息的处理方法、装置及计算机存储介质 技术领域
本发明涉及通信领域，具体而言，涉及一种指示信息的确定、处理以及请求消息的处理方法、装置及计算机存储介质。
背景技术
集群通信系统是为了满足行业用户指挥调度需求而开发的、面向特定行业应用的专用无线通信系统，该系统中的大量无线用户共享少量无线信道，以指挥调度为主体应用，是一种多用途、高效能的无线通信系统。集群通信系统在政府部门、公共安全、应急通信、电力、民航、石油化工和军队等领域有着广泛的应用市场。
集群通信系统经历了与蜂窝移动通信系统类似的发展历程。第一代集群系统是模拟集群通信系统，主要支持语音通信。最早进入我国的模拟集群通信系统是诺基亚(Nokia)公司的Actionet系统，其采用MPT-1327信令，应用在450MHz频段上。此后，日本的F.A.S.T和美国摩托罗拉(Motorola)公司的Smartnet进入我国，并长期占领我国集群市场80％以上的市场份额。
第二代集群系统是窄带数字集群通信系统，兴起于20世纪90年代，2004年左右开始在我国部署，是当前国内应用最广泛的集群通信系统。数字集群通信系统支持语音和低速数据(最高28.8kbps)通信，代表系统是欧洲电信标准组织(European Telecommunications Standards Institute，简称为ETSI)定义的陆上集群无线电(Terrestrial Trunked Radio，简称为TETRA)系统、美国Motorola的综合数字增强型网络(Integrated Digital Enhanced Networks，简称为iDEN)系统，中兴通讯股份有限公司基于CDMA1X开发的开放式集群结构(Global Open Trunking Architecture，简称为GoTa)系统、华为技术有限公司基于GSM开发的GT800系统。从国内来看，最近两三年，TETRA网络的增长最快，在全国已建的数字集群通信网中，TETRA网的数量约占2/3强。
集群系统区别于公众系统的特性在于，集群系统需要具备高效的指挥调度特性，并且要求网络具有高可靠性和安全性。
呼叫控制：根据用户的业务请求，在主叫用户和被叫用户之间建立、维持和释放业务承载；
鉴权认证：支持鉴权和认证，鉴权功能可以包括：网络侧对终端鉴权以及网络侧对终端与终端对网络侧的双向鉴权；
故障弱化：当网络侧与基站或网络侧内部网元之间的链路发生故障时，基站能够为其覆盖范围下的用户终端提供受限的集群服务。
网络互联互通功能：能够与公共电话系统(Public Switched Telephone Network，简称为PSTN)、公众移动通信系统(例如：全球移动通信系统(GSM)/码分多址(CDMA)、分时长期演进(TD-LTE))、互联网协议(IP)电话、其他制式的集群通信系统等互通。在第三代合作伙伴计划(3rd Generation Partnership Project，简称为3GPP)LTE中集群通信称为组通信服务能力(GCSE)。图1是根据相关技术的集群通信系统的系统架构示意图。
为了有效地利用移动网络资源，3GPP提出了多媒体广播多播业务(Multimedia Broadcast Multicast Service，简称为MBMS)，该业务是一种从一个数据源向多个目标移动终端传送数据的技术，实现了网络(包括：核心网和接入网)资源的共享，提高了网络资源(尤其是空中接口资源)的利用率。3GPP定义的MBMS业务不仅能够实现纯文本低速率的消息类组播和广播，而且还能够实现高速多媒体业务的广播和组播，提供多种丰富的视频、音频和多媒体业务，这无疑顺应了未来移动数据发展的趋势，为3/4G的发展提供了更好的业务前景。
MBMS业务的特点是业务的数据量大，移动终端接收时持续时间长，平均数据率恒定。上述特点决定了MBMS业务的调度与控制信令配置都是半静态的，即MBMS业务的调度信息与控制信令信息都是“长期”保持不变的，这些信息通过MBMS控制信道(MBMS Control Channel，简称为MCCH)周期性地发送，统称为MCCH信息。演进型MBMS(eMBMS)系统可能存在多个MCCH，每个MCCH对应于不同的MBSFN区域，其中仅承载对应单频网MBMS(MBMS over a Single Frequency Network，简称为MBSFN)区域发送的MBMS业务的控制信息。图2是根据相关技术的LTE中MBMS的架构示意图。
目前业界正在讨论采用MBMS技术实现集群通信的可能性。
在对相关技术的研究和实践过程中发现相关技术存在以下问题：当发送集群业务的MBMS空口用户面数据发生拥塞/过载时，组通信业务(Group CommunicationService，简称为GCS)应用服务器(Application Server，简称为AS)需要为受影响的UE建立单播承载，同时停止受影响业务的多播承载发送。GCS AS不知道受影响UE所在的MBSFN区域，而只知道UE所在的MBMS业务区域。在通常情况下，MBMS 业务区域大于MBSFN区域，如果根据MBMS业务区域停止集群数据的多播发送，则可能影响其他未发生拥塞/过载区域的UE，如何实现MBMS业务区域到MBSFN区域的映射以及如何减少对未发生拥塞/过载区域UE的影响，目前尚未提出有效的解决方案。
发明内容
本发明实施例提供了一种指示信息的确定、处理以及请求消息的处理方法、装置及计算机存储介质，以至少解决相关技术中如何实现MBMS业务区域到MBSFN区域的映射以及如何减少对未发生拥塞/过载区域UE的影响的问题。
根据本发明实施例的一个方面，提供了一种指示信息的确定方法。
根据本发明实施例的指示信息的确定方法包括：确定多媒体广播多播业务(MBMS)承载的用户面数据发生拥塞或过载，配置第一指示信息；向组通信业务(GCS)应用服务器(AS)发送第一指示信息，其中，第一指示信息用于在GCS AS请求多小区多播协调实体MCE或基站(eNB)停止通过MBMS承载的因用户面数据发生拥塞或过载而受到影响的集群业务的过程中提供参考依据。
在优选实施过程中，上述确定MBMS承载的用户面数据发生拥塞或过载可以包括以下处理：当一个或多个eNB检测出用户面数据发生拥塞或过载时，确定一个或多个eNB所在的MBSFN区域或MBMS业务区域发生拥塞或过载。
优选地，根据判定条件检测到用户面数据发生拥塞或过载，其中，判定条件为预先配置完成或者携带在从GCS AS接收到的请求消息中。
优选地，第一指示信息中携带的内容包括以下至少之一：拥塞或过载标识；一个或多个小区标识，其中，小区标识包括以下至少之一：演进的统一陆地无线接入网(E-UTRAN)小区标识、E-UTRAN小区全球标识；一个或多个业务区域标识(SAI)；一个或多个单频网多媒体广播多播业务(MBSFN)区域标识；一个或多个MBMS业务标识；拥塞或过载开始标识；其中，拥塞或过载标识用于指示在当前网络中用户面数据的负载是在发生拥塞还是在发生过载，小区标识用于指示发生拥塞或过载所影响到的小区，SAI用于指示发生拥塞或过载所影响到的MBMS业务区域，MBSFN区域标识用于指示发生拥塞或过载的MBSFN区域，MBMS业务标识用于指示发生拥塞或过载所影响到的集群业务。
优选地，向GCS AS发送第一指示信息包括以下方式之一：将发生拥塞或过载的全部MBMS业务标识发送至MCE，以使MCE根据第一参数与第二参数的对应关系从全部MBMS业务标识中选取待上报的MBMS业务标识，并上报至GCS AS，其中，第一参数为服务质量等级标识QCI或分配与保持优先级ARP，第二参数为临时移动组标识TMGI；根据接收到的来自于GCS AS的第一请求消息上报在该请求消息中指定的SAI中的TMGI状态信息。
优选地，在向GCS AS发送第一指示信息的触发条件之前，还包括：判断是否需要向GCS AS发送第一指示信息的触发条件包括以下之一：在发生拥塞或过载开始事件，或者，发生拥塞或过载结束事件的情况下，向GCS AS发送第一指示信息；在接收到来自于GCS AS的请求消息后，向GCS AS发送第一指示信息；在接收到来自于GCS AS的请求消息并且发生拥塞或过载开始事件，或者，接收到来自于GCS AS的请求消息并且发生拥塞或过载结束事件后，向GCS AS发送第一指示信息；按照预设周期向GCS AS发送第一指示信息；在每次重新启动后向GCS AS发送第一指示信息。
优选地，在向GCS AS发送第一指示信息之后，还包括：确定用户面数据发生的拥塞或过载已经恢复，配置第二指示信息；向GCS AS发送第二指示信息，其中，第二指示信息用于为GCS AS选择对已停止的集群业务继续通过单播承载的方式进行发送或者恢复MBMS承载的方式进行发送提供参考依据。
根据本发明实施例的另一方面，提供了一种请求消息的处理方法。
根据本发明实施例的请求消息的处理方法包括：接收来自于组通信业务(GCS)应用服务器(AS)的请求消息，其中，请求消息是在GCS AS从基站接收到用于指示通过多媒体广播多播业务(MBMS)承载的用户面数据发生拥塞或过载的指示信息后发出的，请求消息用于请求停止通过MBMS承载的因用户面数据发生拥塞或过载而受到影响的集群业务；根据请求消息配置停止通过MBMS承载发送受到影响的集群业务。
优选地，经由广播多播服务中心BM-SC接收来自于GCS AS的请求消息。
优选地，根据请求消息配置停止通过MBMS承载发送受到影响的集群业务包括：根据请求消息获取待停止多播承载的MBSFN区域和MBMS业务；对待停止多播承载的MBSFN区域和MBMS业务进行配置。
优选地，请求消息中携带的信息包括以下至少之一：小区标识、MBMS业务标识、业务区域标识。
根据本发明实施例的又一方面，提供了一种指示信息的处理方法。
根据本发明实施例的指示信息的处理方法包括：接收来自于基站的指示信息，其中，指示信息用于指示多媒体广播多播业务(MBMS)承载的用户面数据发生拥塞或过载；根据指示信息向多小区多播协调实体(MCE)发送请求消息，其中，请求消息用于请求停止通过MBMS承载的因用户面数据发生拥塞或过载而受到影响的集群业务。
优选地，经由广播多播服务中心(BM-SC)向MCE发送请求消息。
优选地，在根据指示信息向MCE发送请求消息之前，还包括：根据指示信息确定因用户面数据发生拥塞或过载而受到影响的目标用户设备UE和/或集群业务标识；在用户面数据发生拥塞的情况下，为目标UE建立单播承载并通过单播承载发送与集群业务标识对应的集群业务；或者，在用户面数据发生过载的情况下，将与集群业务标识对应的集群业务设置为排队等待状态，直至等到过载结束后再进行发送；或者，在用户面数据发生过载的情况下，抢占现有集群业务的资源发送与集群业务标识对应的集群业务。
优选地，请求消息中携带的信息包括以下至少之一：小区标识、MBMS业务标识、业务区域标识。
根据本发明实施例的再一方面，提供了一种指示信息的确定装置。
根据本发明实施例的指示信息的确定装置包括：配置模块，设置为确定多媒体广播多播业务(MBMS)承载的用户面数据发生拥塞或过载，配置第一指示信息；发送模块，设置为向组通信业务(GCS)应用服务器(AS)发送第一指示信息，其中，第一指示信息用于在GCS AS请求多小区多播协调实体(MCE)或基站(eNB)停止通过MBMS承载的因用户面数据发生拥塞或过载而受到影响的集群业务的过程中提供参考依据。
优选地，配置模块，设置为当检测出用户面数据发生拥塞或过载时，确定自身所在的MBSFN区域或MBMS业务区域发生拥塞或过载。
优选地，配置模块，设置为根据判定条件检测到用户面数据发生拥塞或过载，其中，判定条件为预先配置完成或者携带在从GCS AS接收到的请求消息中。
优选地，第一指示信息中携带的内容包括以下至少之一：拥塞或过载标识；一个或多个小区标识，其中，小区标识包括以下至少之一：演进的统一陆地无线接入网 (E-UTRAN)小区标识、E-UTRAN小区全球标识；一个或多个业务区域标识(SAI)；一个或多个单频网多媒体广播多播业务(MBSFN)区域标识；一个或多个MBMS业务标识；拥塞或过载开始标识；其中，拥塞或过载标识用于指示在当前网络中用户面数据的负载是在发生拥塞还是在发生过载，小区标识用于指示发生拥塞或过载所影响到的小区，SAI用于指示发生拥塞或过载所影响到的MBMS业务区域，MBSFN区域标识用于指示发生拥塞或过载的MBSFN区域，MBMS业务标识用于指示发生拥塞或过载所影响到的集群业务。
优选地，发送模块，设置为向GCS AS发送第一指示信息包括以下方式之一：将发生拥塞或过载的全部MBMS业务标识发送至MCE，以使MCE根据第一参数与第二参数的对应关系从全部MBMS业务标识中选取待上报的MBMS业务标识，并上报至GCS AS，其中，第一参数为服务质量等级标识(QCI)或分配与保持优先级(ARP)，第二参数为临时移动组标识(TMGI)；根据接收到的来自于GCS AS的第一请求消息上报在该第一请求消息中指定的SAI中的TMGI状态信息。
优选地，上述装置还包括：判断模块；判断模块，设置为判断是否需要向GCS AS发送第一指示信息的触发条件包括以下之一：在发生拥塞或过载开始事件，或者，发生拥塞或过载结束事件的情况下，向GCS AS发送第一指示信息；在接收到来自于GCSAS的请求消息后，向GCS AS发送第一指示信息；在接收到来自于GCS AS的请求消息并且发生拥塞或过载开始事件，或者，接收到来自于GCS AS的请求消息并且发生拥塞或过载结束事件后，向GCS AS发送第一指示信息；按照预设周期向GCS AS发送第一指示信息；在每次重新启动后向GCS AS发送第一指示信息。
优选地，配置模块，还设置为确定用户面数据发生的拥塞或过载已经恢复，配置第二指示信息；发送模块，还设置为向GCS AS发送第二指示信息，其中，第二指示信息用于为GCS AS选择对已停止的集群业务继续通过单播承载的方式进行发送或者恢复MBMS承载的方式进行发送提供参考依据。
根据本发明实施例的再一方面，提供了一种请求消息的处理装置。
根据本发明实施例的请求消息的处理装置包括：接收模块，设置为接收来自于组通信业务(GCS)应用服务器(AS)的请求消息，其中，请求消息是在GCS AS从基站接收到用于指示通过多媒体广播多播业务(MBMS)承载的用户面数据发生拥塞或过载的指示信息后发出的，请求消息用于请求停止通过MBMS承载的因用户面数据发生拥塞或过载而受到影响的集群业务；处理模块，设置为根据请求消息配置停止通过MBMS承载发送受到影响的集群业务。
优选地，接收模块，设置为经由广播多播服务中心BM-SC接收来自于GCS AS的请求消息。
优选地，处理模块包括：获取单元，设置为根据请求消息获取待停止多播承载的MBSFN区域和MBMS业务；处理单元，设置为对待停止多播承载的MBSFN区域和MBMS业务进行配置。
优选地，请求消息中携带的信息包括以下至少之一：小区标识、MBMS业务标识、业务区域标识。
根据本发明的又一方面，提供了一种指示信息的处理装置。
根据本发明实施例的指示信息的处理装置包括：接收模块，设置为接收模块接收来自于基站的指示信息，其中，指示信息用于指示多媒体广播多播业务(MBMS)承载的用户面数据发生拥塞或过载；第一处理模块，设置为根据指示信息向多小区多播协调实体(MCE)发送请求消息，其中，请求消息用于请求停止通过MBMS承载的因用户面数据发生拥塞或过载而受到影响的集群业务。
优选地，第一处理模块，设置为经由广播多播服务中心BM-SC向MCE发送请求消息。
优选地，上述装置还包括：确定模块，设置为根据指示信息确定因用户面数据发生拥塞或过载而受到影响的目标用户设备UE和/或集群业务标识；第二处理模块，设置为在用户面数据发生拥塞的情况下，为目标UE建立单播承载并通过单播承载发送与集群业务标识对应的集群业务；或者，在用户面数据发生过载的情况下，将与集群业务标识对应的集群业务设置为排队等待状态，直至等到过载结束后再进行发送；或者，在用户面数据发生过载的情况下，抢占现有集群业务的资源发送与集群业务标识对应的集群业务。
优选地，请求消息中携带的信息包括以下至少之一：小区标识、MBMS业务标识、业务区域标识。
再一方面，本发明实施例还提供一种计算机存储介质，所述计算机存储介质中存储有计算机可执行指令，所述计算机可执行指令用于上述的指示信息的确定、处理以及请求消息的处理方法。
通过本发明实施例，采用确定MBMS承载的用户面数据发生拥塞或过载，配置第一指示信息；向GCS AS发送第一指示信息，其中，第一指示信息用于在GCS AS请 求MCE或eNB停止通过MBMS承载的因用户面数据发生拥塞或过载而受到影响的集群业务的过程中提供参考依据，解决了相关技术中如何实现MBMS业务区域到MBSFN区域的映射以及如何减少对未发生拥塞/过载区域UE的影响的问题，进而能够实现修改MBMS业务区域中的MBSFN区域的MBMS业务多播承载，当发生MBMS承载拥塞/过载时停止在MBSFN区域通过MBMS承载发送集群业务，以缓解MBMS承载拥塞/过载，从而减少对非拥塞/过载区域UE的影响。
附图说明
此处所说明的附图用来提供对本发明的进一步理解，构成本申请的一部分，本发明的示意性实施例及其说明用于解释本发明，并不构成对本发明的不当限定。在附图中：
图1是根据相关技术的集群通信系统的系统架构示意图；
图2是根据相关技术的LTE中MBMS的架构示意图；
图3是根据本发明实施例的指示信息的确定方法的流程图；
图4是根据本发明优选实施例的eNB向AS发送拥塞/过载指示信息过程的示意图；
图5是根据本发明实施例的请求消息的处理方法的流程图；
图6是根据本发明实施例的指示信息的处理方法的流程图；
图7是根据本发明优选实施例的针对eNB检测到多播承载拥塞/过载开始的场景实现修改多播承载方法的流程图；
图8是根据本发明优选实施例的针对eNB检测到多播承载拥塞/过载结束的场景实现修改多播承载的方法的流程图；
图9是根据本发明优选实施例的针对eNB周期性上报拥塞/过载的场景实现修改多播承载的方法的流程图；
图10是根据本发明实施例的指示信息的确定装置的结构框图；
图11是根据本发明优选实施例的指示信息的确定装置的结构框图；
图12是根据本发明实施例的请求消息的处理装置的结构框图；
图13是根据本发明优选实施例的请求消息的处理装置的结构框图；
图14是根据本发明实施例的指示信息的处理装置的结构框图；
图15是根据本发明优选实施例的指示信息的处理装置的结构框图；
图16是根据本发明优选实施例的修改多播承载系统的示意图。
具体实施方式
下文中将参考附图并结合实施例来详细说明本发明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
在下面所提供的实施例中，如无具体说明，本发明的MBMS是指演进的MBMS，即eMBMS，AS是指GCS AS，组通信是指集群通信。目前GCS AS上部署有集群业务，当然在GCS AS上还可以部署其他业务，本发明为了描述更加方便，将GCS AS分发的业务简称为集群业务。
在优选实施例中，配置MCE是指网络中配置了集中式MCE，此时在一个MBSFNarea中，存在一个MCE和若干个eNB，MCE与eNB之间可以通过M2接口进行通讯。分布式MCE是指在一个MBSFN area中MCE与eNB设置在一起，也可以理解为eNB中的特定模块能够完成MCE的功能和作用，此时在该MBSFN area中，相当于存在多少个eNB就有多少个MCE。在本发明中，为了描述方便，对于分布式MCE而言，MME可以通过M3接口与eNB中的MCE模块进行通信，此时M2接口作为逻辑接口依然存在。对于分布式MCE架构，通过OAM实现MCE之间的协调工作。如无特殊说明，本发明可以应用于集中式或分布式MCE架构。在本发明中，如果采用分布式MCE架构，则MCE与eNB之间可以通过M2接口进行通信，其实际上属于eNB与其自身的MCE模块之间的内部通信。
图3是根据本发明实施例的指示信息的确定方法的流程图。如图3所示，该方法可以包括以下处理步骤：
步骤S302：eNB确定MBMS承载的用户面数据发生拥塞或过载，配置第一指示信息；
步骤S304：eNB向GCS AS发送第一指示信息，其中，第一指示信息用于在GCSAS请求MCE或eNB停止通过MBMS承载的因用户面数据发生拥塞或过载而受到影响的集群业务的过程中提供参考依据。
相关技术中无法实现MBMS业务区域到MBSFN区域的映射以及无法减少对未发生拥塞/过载区域UE的影响。采用如图3所示的方法，基站在确定用户面数据发生拥塞或过载的情况下，可以向GCS AS发送用于指示用户面数据发生拥塞或过载的指示信息，GCS AS根据该指示信息请求MCE(针对集中式MCE)或eNB(针对分布式MCE)停止通过MBMS承载的因用户面数据发生拥塞或过载而受到影响的集群业务，由此解决了相关技术中如何实现MBMS业务区域到MBSFN区域的映射以及如何减少对未发生拥塞/过载区域UE的影响的问题，进而能够实现修改MBMS业务区域中的MBSFN区域的MBMS业务多播承载，当发生MBMS承载拥塞/过载时停止在MBSFN区域通过MBMS承载发送集群业务，以缓解MBMS承载拥塞/过载，从而减少对非拥塞/过载区域UE的影响。
在优选实施过程中，上述eNB确定MBMS承载的用户面数据发生拥塞或过载可以包括以下处理：当一个或多个eNB检测出用户面数据发生拥塞或过载时，确定一个或多个eNB所在的MBSFN区域或MBMS业务区域发生拥塞或过载。即通过一个或多个eNB检测用户面数据是否发生拥塞或过载，其中，一个或多个eNB发生拥塞或过载表明其所在的MBSFN区域发生拥塞或过载。
上述拥塞是指用户面数据负载达到预设阈值，而过载是指网络节点无法继续处理额外的用户面数据负载。本发明中所提到的用户面数据是指物理多播信道(PMCH)上的MBMS业务数据。
在优选实施过程中，eNB可以根据判定条件检测到用户面数据发生拥塞或过载，其中，判定条件可以由操作管理维护(OAM)预先配置完成(不限定消息类型)或者携带在从GCS AS接收到的请求消息中。
eNB可以根据事先设定的规则判断MBMS用户面数据是否发生拥塞/过载，即预先定义了拥塞/过载判定条件，如果eNB经过判断能够确定满足上述预先定义的拥塞/过载判定条件时，则可以确定已经发生拥塞/过载。
上述拥塞/过载判定条件，即设定的判断规则除了可以采用事先设定的方式，也可以在发送给eNB的指示信息中同时携带。
eNB可以通过eNodeB(eNB)→MCE→MME→MBMS GW→BM-SC→AS向GCSAS发送拥塞/过载指示信息。即eNB首先通过M2接口向MCE发送指示信息，该指示信息可以采用现有的M2接口信令并增加新的指示字段来实现，或者，直接采用新的M2接口信令；
同样的，在M3接口、Sm接口、SGmb接口、MB2-c接口上发送上述拥塞/过载指示信息时，可以采用现有接口信令并增加新的指示字段，或者，直接采用新的专有接口信令实现。
优选地，上述第一指示信息中携带的内容可以包括但不限于以下至少之一：
(1)拥塞/过载标识；
(2)一个或多个小区标识，例如：E-UTRAN小区标识(E-UTRAN Cell Identifier，简称为ECI)或E-UTRAN小区全球标识(E-UTRAN Cell Global Identifier，简称为ECGI)；
(3)一个或多个业务区域标识(Service Area Identifier，简称为SAI)；
(4)一个或多个MBSFN区域标识；
(5)一个或多个MBMS业务标识，例如：临时移动组标识(Temporary Mobile Group Identity，简称为TMGI)；和/或，MBMS会话标识(例如：session ID)；
(6)拥塞/过载开始标识。
其中，拥塞/过载标识用于指示网络拥塞还是过载，小区标识用于指示拥塞/过载影响的小区，SAI用于指示拥塞/过载影响的MBMS业务区域，MBSFN区域标识用于指示发生拥塞/过载的MBSFN区域，TMGI用于指示拥塞/过载影响的集群业务。
需要指出的是，MBSFN区域标识只在M2接口上发送。
在优选实施过程中，上述第一指示信息的内容由触发检测拥塞的方式决定：
1)如果是AS请求触发且请求消息中携带有区域标识和业务标识，则第一指示信息需要包括：拥塞/过载标识，开始/结束标识；进一步地，也可以包括：区域标识和业务标识。
2)如果周期性上报，则第一指示信息可以包括：拥塞/过载标识、区域标识、业务标识以及开始/结束标识，其中，区域标识可以包括：小区标识、和/或SAI、和/或MBSFN区域标识。假设eNB上报MCE的区域标识为小区标识，则MCE根据接收到的小区标识和业务标识可以判断发生拥塞的MBSFN区域/业务区域，则MCE向AS上报的区域标识包含小区标识和/或业务区域标识。AS可以根据接收到的指示信息向MCE下发停止业务的消息中包含接收到的业务区域标识和/或小区标识，然后MCE再 根据从AS接收到的业务区域标识和/或小区标识和本地已判断出发生拥塞的MBSFN区域信息，关闭相应MBSFN区域的业务。其他的区域标识标识信息作类似处理，此处不再赘述。
拥塞/过载开始/结束的内容可以包括但不限于以下至少之一：
(1)开始(用1或true指示)；
(2)结束(用0或false指示)。
拥塞/过载开始/结束，换言之，拥塞/过载开始等效于当前出现拥塞/过载，拥塞/过载结束等效于当前没有出现拥塞/过载或已经开始的拥塞/过载现已结束。
节点拥塞是指网络中的MBMS用户面数据负载达到预设阈值；节点过载是指网络节点无法继续处理额外的MBMS用户面数据负载。
上报MBMS业务拥塞/过载信息的内容可以包括但限于：假设拥塞用C指示，过载用O指示，举例：
{ECI1/MBSFN area ID1/SAI 1:TMGI 1,TMGI2,TMGI3；C,true}
{ECI2/MBSFN area ID1/SAI 1:TMGI5,TMGI6；O,false}
{ECI3/MBSFN area ID2/SAI 1:TMGI10；C,false}
说明：在上述示例中，小区ECI1中的TMGI1,TMGI2,TMGI3发生拥塞；ECI2中的TMGI5,TMGI6过载结束；ECI3中的TMGI10拥塞结束。
拥塞/过载指示信息在发送过程中可能进行修改，通常是将小区标识ECI修改为MBMS业务区域标识SAI，如果在MCE将接收到的指示信息中的ECI修改为SAI，则GCS AS可以根据接收到的指示信息确定发生拥塞/过载的MBMS业务区域。
当过载指示O为1(True)的情况下，可以不再发送拥塞指示C；或者虽然发送了拥塞指示C，UE可以忽略该指示。
优选地，上述eNB向GCS AS发送第一指示信息包括以下方式之一：
方式一、将发生拥塞或过载的全部MBMS业务标识发送至MCE，以使MCE根据第一参数与第二参数的对应关系从全部MBMS业务标识中选取待上报的MBMS业务 标识，并上报至GCS AS，其中，第一参数为服务质量等级标识QCI或分配与保持优先级ARP，第二参数为临时移动组标识TMGI；
方式二、根据接收到的来自于GCS AS的第一请求消息上报在该请求消息中指定的SAI中的TMGI状态信息。
考虑到只有特定的集群业务(例如：一键通话(Push To Talk，简称为PTT))可能发生拥塞/过载，根据业务的服务质量(QoS)信息，例如：QCI或ARP，确定发生拥塞/过载的业务是特定的集群业务。由于eNB不知道业务的QoS信息，因此在eNB中存在以下两种上报拥塞/过载方法：
方法一、eNB上报所有发生拥塞/过载的业务标识TMGI到MCE，根据特定业务的TMGI(MCE根据QCI/ARP与TMGI的对应关系)，MCE选择发生拥塞/过载的特定业务的TMGI上报到GCS AS；
可选地，eNB检测到拥塞/过载并向AS上报受影响的集群业务可以采用以下方式至少之一：
方式一、该eNB上承载的全部集群业务，即：包括全部MBSFN区域；
方式二、检测到拥塞/过载的MBSFN区域，这个/这些MBSFN区域上所配置的全部集群业务，即包括MBSFN区域的所有PMCH上所承载的集群业务；
方式三、每个MBSFN区域上承载了一个或多个PMCH，eNB检测到一个或多个PMCH发生了拥塞/过载，则eNB上报这个/这些PMCH上所配置的所有集群业务。
方法二、AS请求需要上报状态的SAI和TMGI，通过路径AS→BM-SC→MBMSGW→MME→MCE→eNB发送请求消息到eNB，eNB可以通过eNB→MCE→MME→MBMS GW→BM-SC→AS，上报特定SAI中TMGI的状态到AS。可选地，如果AS请求信息只包括SAI信息，则eNB上报SAI中所有的TMGI状态。
优选地，在eNB向GCS AS发送第一指示信息的触发条件之前，还可以包括操作：
步骤S1：eNB判断是否需要向GCS AS发送第一指示信息的触发条件可以包括但不限于以下之一：
条件一、在发生拥塞或过载开始事件，或者，发生拥塞或过载结束事件的情况下，向GCS AS发送第一指示信息；
条件二、在接收到来自于GCS AS的请求消息后，向GCS AS发送第一指示信息；
条件三、在接收到来自于GCS AS的请求消息并且发生拥塞或过载开始事件，或者，接收到来自于GCS AS的请求消息并且发生拥塞或过载结束事件后，向GCS AS发送第一指示信息；
条件四、按照预设周期向GCS AS发送第一指示信息；
条件五、在每次重新启动后向GCS AS发送第一指示信息。
上述发送触发方式可以为以下之一：事件触发、AS请求触发、事件触发和AS请求触发、周期性上报，其中，事件触发上报是指当网络节点发生拥塞/过载开始/结束事件时，网络节点上报到AS；AS请求触发是指AS向网络节点发送请求消息，接收到请求消息的网络节点上报节点状态信息到AS；事件触发和AS请求触发是指AS向网络节点发送请求消息，当网络节点检测到拥塞/过载事件时上报到AS；周期性上报是指配置上报周期，在每个周期eNB上报节点状态到AS，该上报周期可以事先指定或者AS在发送请求消息时指定。
当网络节点发生拥塞/过载开始/结束事件是指：从开始状态转换为结束状态；或者，从结束状态转换为开始状态。即如果原先并没有发生拥塞/过载(等效于上次拥塞/过载已经结束)转换为开始(等效于当前已经出现拥塞/过载)，则eNB需要上报；如果原先出现了拥塞/过载(等效于当前拥塞/过载已经开始)到不再发生拥塞/过载(等效于当前拥塞/过载已经结束)，则eNB需要上报；而且在eNB检测到拥塞状态和过载状态彼此发生变化的情况下，eNB也需要上报。
简单地说，C＝拥塞指示，采用{0,1}标识；O＝过载指示，采用{0,1}标识，只要C和/或O的标识发送了变化，eNB都需要进行上报。
总而言之，如果拥塞/过载的开始或者结束的状态未发生改变，则eNB不再需要上报，这样AS总能够准确地掌握MBMS的拥塞/过载状态。eNB可能在发生故障后重新启动，则eNB发生了拥塞/过载改变，但eNB却未曾得知，因此，eNB在每次重启后总是需要上报一次拥塞/过载指示信息。
图4是根据本发明优选实施例的eNB向AS发送拥塞/过载指示信息过程的示意图。如图4所示，MBMS业务区域SAI1中有两个MBSFN区域：MBSFN区域1和MBSFN区域2，其中，MBSFN区域1包含2个小区＝{ECI1，ECI2}，MBSFN区域2包含三个小区＝{ECI2,ECI3,ECI4}。假设eNB向AS上报拥塞/过载指示信息 {ECI2/MBSFN area ID 1/SAI 1；TMGI2,TMGI3；C；true}，即SAI1中的MBSFN区域1中的ECI2中的TMGI2和TMGI3发生拥塞。AS在接收到拥塞/过载指示信息{ECI2/SAI1；TMGI2,TMGI3；C；true}之后，确定SAI1中的小区ECI2中的TMGI2和TMGI3发生拥塞。
优选地，在步骤S304，向GCS AS发送第一指示信息之后，还可以包括以下步骤：
步骤S2：eNB确定用户面数据发生的拥塞或过载已经恢复，配置第二指示信息；
步骤S3：eNB向GCS AS发送第二指示信息，其中，第二指示信息用于为GCS AS选择对已停止的集群业务继续通过单播承载的方式进行发送或者恢复MBMS承载的方式进行发送提供参考依据。
拥塞/过载结束是指网络恢复正常，例如：用户面数据负载不满足预设拥塞/过载条件。
eNB可以通过eNodeB(eNB)→MCE→MME→MBMS GW→BM-SC→AS向GCSAS发送拥塞/过载结束(恢复)指示信息。
上述拥塞/过载结束指示信息可以包括但不限于以下至少之一：
(1)拥塞/过载标识；
(2)一个或多个小区标识，例如：E-UTRAN小区标识(E-UTRAN Cell Identifier，简称为ECI)或E-UTRAN小区全球标识(E-UTRAN Cell Global Identifier，简称为ECGI)；
(3)一个或多个业务区域标识(Service Area Identifier，简称为SAI)；
(4)一个或多个MBSFN区域标识；
(5)一个或多个MBMS业务标识，例如：临时移动组标识(Temporary Mobile Group Identity，简称为TMGI)；；和/或，MBMS会话标识(例如：session ID)；
(6)拥塞/过载结束标识。
上述发送触发方式可以为以下之一：事件触发、AS请求触发、事件触发和AS请求触发、周期性上报，其中，事件触发上报是指当网络节点发生拥塞/过载开始/结束事件时，网络节点上报到AS；AS请求触发是指AS向网络节点发送请求消息，接收到 请求消息的网络节点上报节点状态信息到AS；事件触发和AS请求触发是指AS向网络节点发送请求消息，当网络节点检测到拥塞/过载事件时上报到AS；周期性上报是指配置上报周期，在每个周期eNB上报节点状态到AS，该上报周期可以事先指定或者AS在发送请求消息时指定。
图5是根据本发明实施例的请求消息的处理方法的流程图。如图5所示，该方法可以包括以下处理步骤：
步骤S502：MCE或eNB接收来自于GCS AS的请求消息，其中，请求消息是在GCS AS从基站接收到用于指示通过MBMS承载的用户面数据发生拥塞或过载的指示信息后发出的，请求消息用于请求停止通过MBMS承载的因用户面数据发生拥塞或过载而受到影响的集群业务；
步骤S504：MCE或eNB根据请求消息配置停止通过MBMS承载发送受到影响的集群业务。
在优选实施例中，MCE或eNB可以通过接收到的请求消息和本地数据库判断需要停止多播承载的MBSFN区域和MBMS业务，如根据eNB在M2接口上发送的发生拥塞/过载指示信息中的MBSFN区域标识和TMGI。
如上述图4所示，假设MCE接收到来自于MME的请求消息包含{ECI2/SAI1；TMGI2,TMGI3}，ECI2属于两个MBSFN区域，而MCE已知MBSFN区域1发生拥塞，则MCE确定将MBSFN区域1的TMGI2和TMGI3停止多播发送。MCE继而向MBSFN区域1内的eNB发送MBMS调度信息(MBMS Scheduling information)，在上述消息中将TMGI2，TMGI3删除。接收到MBMS Scheduling information的eNB在MBSFN区域1内发送更新的MCCH信息，并在更新的MCCH信息中删除TMGI2和TMGI3，MBSFN区域1中的受影响UE接收到更新的MCCH信息，确定相应的MBMS业务已删除，即相应集群业务TMGI2/TMGI3停止在多播承载上发送。
图6是根据本发明实施例的指示信息的处理方法的流程图。如图6所示，该方法可以包括以下处理步骤：
步骤S602：GCS AS接收来自于基站的指示信息，其中，指示信息用于指示多媒体广播多播业务MBMS承载的用户面数据发生拥塞或过载；
步骤S604：GCS AS根据指示信息向MCE发送请求消息，其中，请求消息用于请求停止通过MBMS承载的因用户面数据发生拥塞或过载而受到影响的集群业务。
在优选实施例中，AS可以通过BM-SC向MCE请求停止受影响业务的MBMS承载。
在AS发送上述请求消息之前，AS首先根据上述拥塞/过载指示信息确定受到影响的目标UE和集群业务TMGI，然后，AS根据拥塞/过载指示信息和本地策略确定所要采取的行动，当发生拥塞时，为目标UE建立单播承载，并通过单播承载发送集群业务；当发生过载时，AS将集群业务排队等待过载结束再发送，或者，AS利用高优先级的集群业务抢占现有集群业务的资源。
AS通过BM-SC→MBMS GW→MME路径向MME发送请求消息，该请求消息用于停止多播承载；该请求消息中携带的信息可以包括以下至少之一：小区标识、MBMS业务标识，其中，小区标识和/或MBMS业务标识为AS接收到的拥塞/过载指示信息中的小区标识ECI和业务标识TMGI。
MBMS GW向区域内所有的MME发送请求消息，MME根据请求消息中的小区标识判断是否为所属的小区，如果否，则MME丢弃收到的请求消息。MME根据小区标识选择MCE并发送请求消息。MME可以通过M3接口消息获取小区所属的MCE。
上述请求消息可以通过现有流程或新建流程来实现，其中，现有流程为：MBMS任务停止请求(MBMS session stop request)或MBMS任务更新(MBMS session update)在现有流程中增加小区标识字段。通过BM-SC→MBMS GW→MME路径向MME发送请求消息，该请求消息用于停止MBMS承载。
如果MBMS GW无法确定具体的MME，则MBMS GW可以向区域内所有MME发送请求消息。考虑到请求消息中携带有目标小区的标识，MME可以判断目标小区是否属于自己的范围，并向MBMS GW发送响应消息。
MME向AS发送响应消息，表明MME已成功/失败接收请求消息。如果响应消息指示失败，则AS/BM-SC/MBMS GW将会重新发送请求消息。
此外，AS可以选择向UE发送集群业务的方式。AS通过上述恢复指示信息确定受到影响的目标UE，并选择合适的方式向目标UE发送集群业务。例如：继续通过单播承载或恢复MBMS承载发送集群业务。为了避免业务中断，GCS AS可以先向受影响的UE建立PTP承载，再释放集群业务的PTM承载。
下面将通过以下几个具体集群业务流程的优选实施例来对上述优选实施过程作进一步的说明。在下面的优选实施例中，仅以配置了集中式MCE为场景描述。然而，在实际场景中，还可以是分布式MCE，此时MCE设置于eNB中，其相当于eNB中的特定模块来完成MCE的功能。
优选实施例一
图7是根据本发明优选实施例的针对eNB检测到多播承载拥塞/过载开始的场景实现修改多播承载方法的流程图。如图7所示，该流程可以包括以下处理步骤：
步骤S702：选择检测拥塞/过载的基站eNB。
在该优选实施例中，执行选择的实体可以为以下之一：由MCE选择、由GCS AS选择、由O&M选择。上述拥塞/过载是指MBMS的用户面数据业务发生拥塞/过载，拥塞/过载的判断准则需要事先制定并通知目标eNB。可选地，可以在指示信息中携带该判断准则。
在正常情况下，如果MBSFN区域中发生MBMS用户面数据拥塞/过载，考虑到MBSFN区域中参与MBSFN传输的所有eNB都有相同的资源配置，则所有eNB都发生拥塞/过载，此时如果所有eNB在M2接口上报拥塞/过载指示，则上报的内容完全相同，所以没必要让所有eNB均上报拥塞/过载指示，一个MBSFN区域有一个eNB上报拥塞/过载即可确定该MBSFN区域/MBMS业务区域发生拥塞，即可以根据部分拥塞/过载信息推测出全部拥塞/过载信息，从而不仅可以提高检测效率，同时还可以降低网络信令负载。
上述eNB可以为一个或多个，当MCE或O&M选择eNB时，通常在一个MBSFN区域可以选择一个eNB，而通知可以通过O&M或信令方式实现。
当GCS AS选择eNB时，考虑到选中的eNB没有拥塞/过载，但是目标MBMS业务区域仍可能拥塞/过载，如目标MBMS业务区域有多个MBSFN区域，eNB所在的MBSFN区域没有拥塞/过载，其他MBSFN区域发生拥塞/过载，但是GCS AS不知道MBSFN区域配置。为了尽量避免上述情况发生，GCS AS可以选择多个eNB用来检测拥塞/过载。
eNB为特定MBMS业务区域中的eNB，一般在MBMS业务区域中有多个eNB，此时可以选择任意一个eNB用来监测拥塞/过载。
需要指出的是，在选择eNB的同时，一般也指定目标MBMS业务区域；目标MBMS业务区域为需要检测拥塞/过载的区域；MBMS业务区域采用业务区域标识(Service Area Identifier，简称为SAI)，如果没有指定MBMS业务区域，考虑到单个eNB可能属于多个MBMS业务区域，则选中的eNB监测所在的全部MBMS业务区域拥塞/过载状态。选择eNB也可以通过小区标识指示，即通过小区标识确定所在的eNB。
在本发明所提供的优选实施例中，以下描述表示同一概念：MBMS承载、MBSFN承载、多播承载、点到多点(Point To Multipoint，简称为PTM)承载。
MBMS承载可以包括：核心网承载(即演进的分组核心网(Evolved Packet Core network，简称为EPC)承载)和空口承载，RAN(基站eNB和/或MCE)配置MBMS空口资源，并在空口发送MBMS配置信息和集群数据。
需要指出的是，发生拥塞/过载的数据面业务可以是普通MBMS业务或GCS业务，普通MBMS业务和GCS业务可以通过不同的服务质量等级标识(QCI)参数加以区别。
步骤S704：eNB检测到多播承载拥塞/过载。
拥塞是指用户面数据负载达到预设阈值，而过载是指网络节点无法继续处理额外的用户面数据负载，在本发明中的用户面数据是指物理多播信道(PMCH)上的MBMS业务数据。
eNB可以根据事先设定的规则判断MBMS用户面数据拥塞/过载，即事先定义了拥塞/过载条件，eNB判断满足条件时则确定发生了拥塞/过载。
可选地，上述拥塞/过载条件，也就是设定的判断规则，除了可以事先设定之外，还可以在发送给eNB的指示信息中同时携带。
步骤S706：eNB向AS发送拥塞/过载指示信息。
eNB可以通过eNodeB(eNB)→MCE→MME→MBMS GW→BM-SC→AS向GCSAS发送拥塞/过载指示信息。即eNB首先通过M2接口向MCE发送指示信息，该指示信息可以采用现有的M2接口信令并增加新的指示字段来实现，或者，直接采用新的M2接口信令；
同样的，在M3接口、Sm接口、SGmb接口、MB2-c接口上发送上述拥塞/过载指示信息时，可以采用现有接口信令并增加新的指示字段，或者，直接采用新的专有接口信令实现。
上述拥塞/过载指示信息可以包括但不限于以下至少之一：
(1)拥塞/过载标识；
(2)小区标识，例如：E-UTRAN小区标识(E-UTRAN Cell Identifier，简称为ECI)或E-UTRAN小区全球标识(E-UTRAN Cell Global Identifier，简称为ECGI)；
(3)业务区域标识(Service Area Identifier，简称为SAI)；
(4)MBSFN区域标识；
(5)MBMS业务标识，例如：临时移动组标识(Temporary Mobile Group Identity，简称为TMGI)；
(6)拥塞/过载开始标识。
其中，拥塞/过载标识用于指示网络拥塞还是过载，小区标识用于指示拥塞/过载影响的小区，SAI用于指示拥塞/过载影响的MBMS业务区域，MBSFN区域标识用于指示发生拥塞/过载的MBSFN区域，TMGI用于指示拥塞/过载影响的集群业务。
需要指出的是，MBSFN区域标识只在M2接口上发送。
拥塞/过载开始/结束的内容可以包括但不限于以下至少之一：
(1)开始(用1或true指示)；
(2)结束(用0或false指示)。
拥塞/过载开始/结束，换言之，拥塞/过载开始等效于当前出现拥塞/过载，拥塞/过载结束等效于当前没有出现拥塞/过载或已经开始的拥塞/过载现已结束。
节点拥塞是指网络中的MBMS用户面数据负载达到预设阈值；节点过载是指网络节点无法继续处理额外的MBMS用户面数据负载。
上报MBMS业务拥塞/过载信息的内容可以包括但限于：假设拥塞用C指示，过载用O指示，举例：
{ECI1/MBSFN area ID1/SAI 1:TMGI 1,TMGI2,TMGI3；C,true}
{ECI2/MBSFN area ID1/SAI 1:TMGI5,TMGI6；O,false}
{ECI3/MBSFN area ID2/SAI 1:TMGI10；C,false}
说明：在上述示例中，小区ECI1中的TMGI1,TMGI2,TMGI3发生拥塞；ECI2中的TMGI5,TMGI6过载结束；ECI3中的TMGI10拥塞结束。
拥塞/过载指示信息在发送过程中可能进行修改，通常是将小区标识ECI修改为MBMS业务区域标识SAI，如果在MCE将接收到的指示信息中的ECI修改为SAI，则GCS AS可以根据接收到的指示信息确定发生拥塞/过载的MBMS业务区域。
当过载指示O为1(True)的情况下，可以不再发送拥塞指示C；或者虽然发送了拥塞指示C，UE可以忽略该指示。
考虑到只有特定的集群业务(例如：一键通话(Push To Talk，简称为PTT))可能发生拥塞/过载，根据业务的服务质量(QoS)信息，例如：QCI或ARP，确定发生拥塞/过载的业务是特定的集群业务。由于eNB不知道业务的QoS信息，因此在eNB中存在以下两种上报拥塞/过载方法：
方法一、eNB上报所有发生拥塞/过载的业务标识TMGI到MCE，根据特定业务的TMGI(MCE根据QCI/ARP与TMGI的对应关系)，MCE选择发生拥塞/过载的特定业务的TMGI上报到GCS AS；
方法二、AS请求需要上报状态的SAI和TMGI，通过路径AS→BM-SC→MBMSGW→MME→MCE→eNB发送请求消息到eNB，eNB可以通过eNB→MCE→MME→MBMS GW→BM-SC→AS，上报特定SAI中TMGI的状态到AS。可选地，如果AS请求信息只包括SAI信息，则eNB上报SAI中所有的TMGI状态。
上述发送触发方式可以为以下之一：事件触发、AS请求触发、事件触发和AS请求触发、周期性上报，其中，事件触发上报是指当网络节点发生拥塞/过载开始/结束事件时，网络节点上报到AS；AS请求触发是指AS向网络节点发送请求消息，接收到请求消息的网络节点上报节点状态信息到AS；事件触发和AS请求触发是指AS向网络节点发送请求消息，当网络节点检测到拥塞/过载事件时上报到AS；周期性上报是指配置上报周期，在每个周期eNB上报节点状态到AS，该上报周期可以事先指定或者AS在发送请求消息时指定。
当网络节点发生拥塞/过载开始/结束事件是指：从开始状态转换为结束状态；或者，从结束状态转换为开始状态。即如果原先并没有发生拥塞/过载(等效于上次拥塞/过载已经结束)转换为开始(等效于当前已经出现拥塞/过载)，则eNB需要上报；如果原先出现了拥塞/过载(等效于当前拥塞/过载已经开始)到不再发生拥塞/过载(等效于当前拥塞/过载已经结束)，则eNB需要上报；而且在eNB检测到拥塞状态和过载状态彼此发生变化的情况下，eNB也需要上报。
简单地说，C＝拥塞指示，采用{0,1}标识；O＝过载指示，采用{0,1}标识，只要C和/或O的标识发送了变化，eNB都需要进行上报。
总而言之，如果拥塞/过载的开始或者结束的状态未发生改变，则eNB不需要再上报，这样AS总能够准确地掌握MBMS的拥塞/过载状态。
步骤S708：AS通过BM-SC向MME发送请求消息。
在AS发送上述请求消息之前，AS首先根据上述拥塞/过载指示信息确定受到影响的目标UE和集群业务TMGI，然后，AS根据拥塞/过载指示信息和本地策略确定所要采取的行动，当发生拥塞时，为目标UE建立单播承载，并通过单播承载发送集群业务；当发生过载时，AS将集群业务排队等待过载结束再发送，或者，AS利用高优先级的集群业务抢占现有集群业务的资源。
AS通过BM-SC→MBMS GW→MME路径向MME发送请求消息，该请求消息用于停止多播承载；该请求消息中携带的信息可以包括以下至少之一：小区标识、MBMS业务标识，其中，小区标识和/或MBMS业务标识为AS接收到的拥塞/过载指示信息中的小区标识ECI和业务标识TMGI。
上述请求消息可以通过现有流程或新建流程来实现，其中，现有流程为：MBMS任务停止请求(MBMS session stop request)或MBMS任务更新(MBMS session update)在现有流程中增加小区标识字段。通过BM-SC→MBMS GW→MME路径向MME发送请求消息，该请求消息用于停止MBMS承载。
如果MBMS GW无法确定具体的MME，则MBMS GW可以向区域内所有MME发送请求消息。考虑到请求消息中携带有目标小区的标识，MME可以判断目标小区是否属于自己的范围，如果是，则继续执行步骤S10，否则，MME丢弃接收到的请求消息并向MBMS GW发送响应消息。
MME向AS发送响应消息，表明MME已成功/失败接收请求消息。如果响应消息指示失败，则AS/BM-SC/MBMS GW将会重新发送请求消息。
步骤S710：MME向目标MCE发送请求消息。
MME可以根据小区标识和MCE的上报信息确定目标MCE，例如：MCE向MME发送的M3安装请求(M3setup request)或M3配置更新(M3CONFIGURATION UPDATE)消息中包含ECI/ECGI列表，上述ECI/ECGI列表为MCE所支持的小区标识，MCE可以通过eNB在M2接口发送的消息获取自己支持的小区标识，例如：M2安装请求(M2setup request)或M2eNB配置更新(M2eNB CONFIGURATION UPDATE)消息。
MCE向MME发送响应消息，表明已成功/失败接收请求消息。如果响应消息指示失败，则MME将会向MCE重新发送请求消息。
步骤S712：MCE配置在MBSFN区域停止多播承载。
MCE可以通过接收到的请求消息和本地数据库判断需要停止多播承载的MBSFN区域，例如：eNB在M2接口上发送了发生拥塞/过载MBSFN区域标识。
假设MCE接收到的请求消息中包含{ECI2；TMGI2,TMGI3}，因为ECI2属于两个MBSFN区域，但是MCE已知MBSFN区域1发生拥塞，则MCE确定将MBSFN区域1的TMGI2和TMGI3停止发送多播发送。则MCE向MBSFN区域1内的eNB发送MBMS调度信息(MBMS Scheduling information)，在上述消息中将TMGI2和TMGI3删除；接收到MBMS Scheduling information的eNB在MBSFN区域1内发送更新的MCCH信息，并在更新的MCCH信息中删除TMGI2和TMGI3，MBSFN区域1中的受影响UE接收到更新的MCCH信息，确定相应的MBMS业务已删除，即相应集群业务停止在多播承载上发送。
步骤S714：MCE向AS发送响应消息。
MCE可以通过MCE→MME→MBMS GW→BM-SC→AS向GCS AS发送请求响应消息，用于指示AS的请求消息已成功/失败执行。如果响应消息指示失败，则AS可重新向MCE发送请求消息。
步骤S716：AS停止通过多播承载发送集群业务。
集群业务为受拥塞/过载影响的集群业务。
优选实施例二
图8是根据本发明优选实施例的针对eNB检测到多播承载拥塞/过载结束的场景实现修改多播承载的方法的流程图。如图8所示，该流程可以包括以下处理步骤：
步骤S802：eNB检测到拥塞/过载结束。
拥塞/过载结束是指网络恢复正常，例如：用户面数据负载不满足预设拥塞/过载条件。
步骤S804：eNB向AS发送恢复指示信息。
eNB可以通过eNodeB(eNB)→MCE→MME→MBMS GW→BM-SC→AS向GCSAS发送拥塞/过载指示信息。
上述拥塞/过载指示信息可以包括但不限于以下至少之一：
(1)拥塞/过载标识；
(2)一个或多个小区标识，例如：E-UTRAN小区标识(E-UTRAN Cell Identifier，简称为ECI)或E-UTRAN小区全球标识(E-UTRAN Cell Global Identifier，简称为ECGI)；
(3)一个或多个业务区域标识(Service Area Identifier，简称为SAI)；
(4)一个或多个MBSFN区域标识；
(5)一个或多个MBMS业务标识，例如：临时移动组标识(Temporary Mobile Group Identity，简称为TMGI)；和/或，MBMS会话标识(例如：session ID)；
(6)拥塞/过载结束标识。
上述发送触发方式可以为以下之一：事件触发、AS请求触发、事件触发和AS请求触发、周期性上报，其中，事件触发上报是指当网络节点发生拥塞/过载开始/结束事件时，网络节点上报到AS；AS请求触发是指AS向网络节点发送请求消息，接收到请求消息的网络节点上报节点状态信息到AS；事件触发和AS请求触发是指AS向网络节点发送请求消息，当网络节点检测到拥塞/过载事件时上报到AS；周期性上报是 指配置上报周期，在每个周期eNB上报节点状态到AS，该上报周期可以事先指定或者AS在发送请求消息时指定。
步骤S806：AS确定是否恢复多播承载，如果是，转向步骤S808，否则，转向步骤S816。
AS通过上述恢复指示信息确定受到影响的目标UE，并选择合适的方式向目标UE发送集群业务。例如：继续通过单播承载或重新建立MBMS承载发送集群业务，具体选择何种承载方式由AS实现决定。
步骤S808：AS通过BM-SC向MCE发送请求消息。
该请求消息用于为集群业务建立MBMS承载，其中，该请求消息可以包括以下至少之一：小区标识/SAI、TMGI。
步骤S810：MCE判断是否建立新的MBSFN区域，如果是，转向步骤S816，否则，转向步骤S814。
MCE可以根据接收到的请求消息和/或OAM信息和/或运营商策略判断是否需要建立新的MBSFN区域，例如：现有MBSFN区域不包含请求小区，则建立新的MBSFN区域，否则修改原MBSFN区域。
步骤S812：MCE建立新的MBSFN区域，AS通过MBMS承载发送集群业务。
AS通过MBMS承载向新的MBSFN中的UE发送集群业务。新的MBSFN区域可以包含请求小区和请求消息中的TMGI。
步骤S814：MCE修改MBSFN区域，AS在MBSFN区域内发送集群业务。
修改是指现有MBSFN区域包含请求的小区，在现有MBSFN区域中配置请求的TMGI，AS在现有MBSFN区域内向UE发送集群业务。
步骤S816：AS通过单播承载继续发送集群业务。
AS不建立MBMS承载，继续通过单播承载发送集群业务。
优选实施例三
图9是根据本发明优选实施例的针对eNB周期性上报拥塞/过载的场景实现修改多播承载的方法的流程图。如图9所示，该流程可以包括以下处理步骤：
步骤S902：选择上报拥塞/过载的eNB.
步骤S904：eNB判断在预设周期内是否发生拥塞/过载，如果是转向步骤S906，否则，转向步骤S912。
预设周期用于eNB上报指示信息到AS，预设周期可以通过OAM或AS设定，在预设周期内即使eNB未检测到拥塞/过载，eNB也需要上报指示信息到AS。
eNB检测MBMS空口用户面承载，即PMCH上是否发生拥塞/过载。
步骤S906：eNB上报拥塞/过载信息到AS。
eNB检测到拥塞/过载，则通过路径eNodeB(eNB)→MCE→MME→MBMS GW→BM-SC→AS向GCS AS发送拥塞/过载指示信息。上述接口发送的指示信息可采用现有信令并增加新的字段，或者，直接采用新的接口信令实现。指示信息可以包括以下至少之一：ECI、SAI、MBSFN area ID、TMGI、拥塞/过载开始标识。
步骤S908：AS请求MCE修改受影响的多播承载。
接收到指示信息的AS可以通过路径AS→BM-SC→MBMS GW→MME→MCE向MCE发送请求消息：修改受影响多播承载。
步骤S910：MCE修改MBSFN区域内的多播承载。
MCE通过MBMS Scheduling information修改多播承载，例如：删除受影响MBSFN区域内的TMGI；eNB在接收到MBMS Scheduling information后，则发送更新的MCCH消息，接收到更新的MCCH消息的UE确定相应的MBMS业务已停止多播发送。
步骤S912：eNB向AS上报指示信息，并继续监测。
eNB未检测到拥塞/过载或者拥塞/过载已结束，则eNB通过路径eNB→MCE→MME→MBMS GW→BM-SC→AS向GCS AS发送指示信息；上述接口发送的指示信息可采用现有信令并增加新的字段，或者，直接采用新的接口信令实现。指示信息可以包括以下至少之一：ECI、SAI、MBSFN area ID、TMGI、拥塞/过载结束标识。
eNB继续监测拥塞/过载，返回步骤S904。
图10是根据本发明实施例的指示信息的确定装置的结构框图。该装置可以应用于eNB，如图10所示，该指示信息的确定装置可以包括：配置模块10，设置为确定MBMS承载的用户面数据发生拥塞或过载，配置第一指示信息；发送模块20，设置为向GCSAS发送第一指示信息，其中，第一指示信息用于在GCS AS请求MCE或eNB停止通过MBMS承载的因用户面数据发生拥塞或过载而受到影响的集群业务的过程中提供参考依据。
优选地，配置模块10，设置为当检测出用户面数据发生拥塞或过载时，确定自身所在的MBSFN区域或MBMS业务区域发生拥塞或过载。
优选地，配置模块10，设置为根据判定条件检测到用户面数据发生拥塞或过载，其中，判定条件为预先配置完成或者携带在从GCS AS接收到的请求消息中。
优选地，上述第一指示信息中携带的内容包括以下至少之一：
(1)拥塞或过载标识；
(2)一个或多个小区标识，其中，小区标识包括以下至少之一：演进的统一陆地无线接入网(E-UTRAN)小区标识、E-UTRAN小区全球标识；
(3)一个或多个业务区域标识(SAI)；
(4)一个或多个单频网多媒体广播多播业务(MBSFN)区域标识；
(5)一个或多个MBMS业务标识；
(6)拥塞或过载开始标识；
其中，拥塞或过载标识用于指示在当前网络中用户面数据的负载是在发生拥塞还是在发生过载，小区标识用于指示发生拥塞或过载所影响到的小区，SAI用于指示发生拥塞或过载所影响到的MBMS业务区域，MBSFN区域标识用于指示发生拥塞或过载的MBSFN区域，MBMS业务标识用于指示发生拥塞或过载所影响到的集群业务。
优选地，发送模块20，设置为向GCS AS发送第一指示信息包括以下方式之一：
方式一、将发生拥塞或过载的全部MBMS业务标识发送至MCE，以使MCE根据第一参数与第二参数的对应关系从全部MBMS业务标识中选取待上报的MBMS业务标识，并上报至GCS AS，其中，第一参数为服务质量等级标识QCI或分配与保持优先级ARP，第二参数为临时移动组标识TMGI；
方式二、根据接收到的来自于GCS AS的第一请求消息上报在该第一请求消息中指定的SAI中的TMGI状态信息。
优选地，如图11所示，上述装置还包括：判断模块30；判断模块30，设置为判断是否需要向GCS AS发送第一指示信息的触发条件包括以下之一：
条件一、在发生拥塞或过载开始事件，或者，发生拥塞或过载结束事件的情况下，向GCS AS发送第一指示信息；
条件二、在接收到来自于GCS AS的请求消息后，向GCS AS发送第一指示信息；
条件三、在接收到来自于GCS AS的请求消息并且发生拥塞或过载开始事件，或者，接收到来自于GCS AS的请求消息并且发生拥塞或过载结束事件后，向GCS AS发送第一指示信息；
条件四、按照预设周期向GCS AS发送第一指示信息；
条件五、在每次重新启动后向GCS AS发送第一指示信息。
优选地，配置模块10，还设置为确定用户面数据发生的拥塞或过载是否已经恢复，配置第二指示信息；发送模块20，还设置为向GCS AS发送第二指示信息，其中，第二指示信息用于为GCS AS选择对已停止的集群业务继续通过单播承载的方式进行发送或者恢复MBMS承载的方式进行发送提供参考依据。
图12是根据本发明实施例的请求消息的处理装置的结构框图。该装置可以应用于MCE中，如图12所示，该请求消息的处理装置可以包括：接收模块40，设置为接收来自于组通信业务GCS应用服务器AS的请求消息，其中，请求消息是在GCS AS从基站接收到用于指示通过多媒体广播多播业务MBMS承载的用户面数据发生拥塞或过载的指示信息后发出的，请求消息用于请求停止通过MBMS承载的因用户面数据发生拥塞或过载而受到影响的集群业务；处理模块50，设置为根据请求消息配置停止通过MBMS承载发送受到影响的集群业务。
优选地，接收模块40，设置为经由广播多播服务中心BM-SC接收来自于GCS AS的请求消息。
优选地，如图13所示，处理模块50可以包括：获取单元500，设置为根据请求消息和本地数据库获取待停止多播承载的MBSFN区域和MBMS业务；处理单元502，设置为对待停止多播承载的MBSFN区域和MBMS业务进行配置。
优选地，上述请求消息中携带的信息可以包括以下至少之一：小区标识、MBMS业务标识、业务区域标识。
图14是根据本发明实施例的指示信息的处理装置的结构框图。该装置可以应用于GCS AS，如图14所示，该指示信息的处理装置可以包括：接收模块60，设置为接收模块接收来自于基站的指示信息，其中，指示信息用于指示多媒体广播多播业务MBMS承载的用户面数据发生拥塞或过载；第一处理模块70，设置为根据指示信息向MCE发送请求消息，其中，请求消息用于请求停止通过MBMS承载的因用户面数据发生拥塞或过载而受到影响的集群业务。
优选地，第一处理模块70，设置为经由广播多播服务中心BM-SC向MCE发送请求消息。
优选地，如图15所示，该装置还可以包括：确定模块80，设置为根据指示信息确定因用户面数据发生拥塞或过载而受到影响的目标用户设备UE和/或集群业务标识；第二处理模块90，设置为在用户面数据发生拥塞的情况下，为目标UE建立单播承载并通过单播承载发送与集群业务标识对应的集群业务；或者，在用户面数据发生过载的情况下，将与集群业务标识对应的集群业务设置为排队等待状态，直至等到过载结束后再进行发送；或者，在用户面数据发生过载的情况下，抢占现有集群业务的资源发送与集群业务标识对应的集群业务。
优选地，上述请求消息中携带的信息可以包括以下至少之一：小区标识、MBMS业务标识、业务区域标识。
作为本发明的一个优选实施例，还提供了一种修改多播承载系统，图16是根据本发明优选实施例的修改多播承载系统的示意图。如图16所示，该修改多播承载系统可以包括：AS 1，设置为接收RAN发送的拥塞/过载指示信息，并向EPC发送修改多播承载请求消息；用于选择发送集群业务的承载方式；以及还用于发送集群业务数据。EPC 2，可以包括但不限于：BM-SC、MBMS-GW、MME，设置为转发AS和RAN之间的控制消息；用于接收AS发送的修改多播承载请求消息；以及还用于EPC内部的消息传递。RAN 3，可以包括但不限于：MCE和eNB，设置为修改多播承载，其中，eNB用于检测拥塞/过载，以及向UE发送集群业务数据和配置信息。用户设备UE 4，设置为接收RAN发送的修改多播承载指示信息，并接收AS发送的集群服务数据。
本发明实施例还记载一种计算机存储介质，所述计算机存储介质中存储有计算机可执行指令，所述计算机可执行指令配置为执行如图3所示的指示信息的确定方法，或者，如图5所示的请求消息的处理方法，或者，如图6所示的指示信息的处理方法。
在本发明所提供的几个实施例中，应该理解到，所揭露的设备和方法，可以通过其它的方式实现。以上所描述的设备实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，如：多个单元或组件可以结合，或可以集成到另一个系统，或一些特征可以忽略，或不执行。另外，所显示或讨论的各组成部分相互之间的耦合、或直接耦合、或通信连接可以是通过一些接口，设备或单元的间接耦合或通信连接，可以是电性的、机械的或其它形式的。
上述作为分离部件说明的单元可以是、或也可以不是物理上分开的，作为单元显示的部件可以是、或也可以不是物理单元，即可以位于一个地方，也可以分布到多个网络单元上；可以根据实际的需要选择其中的部分或全部单元来实现本实施例方案的目的。
另外，在本发明各实施例中的各功能单元可以全部集成在一个处理单元中，也可以是各单元分别单独作为一个单元，也可以两个或两个以上单元集成在一个单元中；上述集成的单元既可以采用硬件的形式实现，也可以采用硬件加软件功能单元的形式实现。
本领域普通技术人员可以理解：实现上述方法实施例的全部或部分步骤可以通过程序指令相关的硬件来完成，前述的程序可以存储于一计算机可读取存储介质中，该程序在执行时，执行包括上述方法实施例的步骤；而前述的存储介质包括：移动存储设备、随机存取存储器(RAM，Random Access Memory)、只读存储器(ROM，Read-Only Memory)、磁碟或者光盘等各种可以存储程序代码的介质。
或者，本发明上述集成的单元如果以软件功能模块的形式实现并作为独立的产品销售或使用时，也可以存储在一个计算机可读取存储介质中。基于这样的理解，本发明实施例的技术方案本质上或者说对相关技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机、服务器、或者网络设备等)执行本发明各个实施例所述方法的全部或部分。而前述的存储介质包括：移动存储设备、RAM、ROM、磁碟或者光盘等各种可以存储程序代码的介质。
从以上的描述中，可以看出，上述实施例实现了如下技术效果(需要说明的是这些效果是某些优选实施例可以达到的效果)：采用本发明实施例所提供的技术方案，在eNB检测到MBMS承载用户面数据拥塞/过载的情况下，可以通过MCE向GCS AS发送拥塞/过载指示信息。GCS AS在接收到拥塞/过载指示信息之后，可以通过BM-SC向MCE请求停止通过MBMS承载发送受影响的集群业务。接收到停止请求的MCE 配置在受影响的MBSFN区域停止通过MBMS承载发送受影响的集群业务。然后，当eNB检测到拥塞/过载恢复时，还可以通过MCE向AS发送拥塞/过载恢复指示信息。由此能够实现修改MBMS业务区域中的MBSFN区域的MBMS业务多播承载，当发生MBMS承载拥塞/过载时停止在MBSFN区域通过MBMS承载发送受影响的集群业务，以缓解MBMS承载拥塞/过载，从而减少对非拥塞/过载区域UE的影响。
显然，本领域的技术人员应该明白，上述的本发明的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本发明不限制于任何特定的硬件和软件结合。
以上所述仅为本发明的优选实施例而已，并不用于限制本发明，对于本领域的技术人员来说，本发明可以有各种更改和变化。凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。
工业实用性
如上所述，本发明实施例提供的一种指示信息的确定、处理以及请求消息的处理方法、装置及计算机存储介质具有以下有益效果：能够实现修改MBMS业务区域中的MBSFN区域的MBMS业务多播承载，当发生MBMS承载拥塞/过载时停止在MBSFN区域通过MBMS承载发送受影响的集群业务，以缓解MBMS承载拥塞/过载，从而减少对非拥塞/过载区域UE的影响。

Claims (31)

  1. 一种指示信息的确定方法，包括：
    确定多媒体广播多播业务MBMS承载的用户面数据发生拥塞或过载，配置第一指示信息；
    向组通信业务GCS应用服务器AS发送第一指示信息，其中，所述第一指示信息用于在所述GCS AS请求多播协调实体MCE或基站eNB停止通过所述MBMS承载的因所述用户面数据发生拥塞或过载而受到影响的集群业务的过程中提供参考依据。
  2. 根据权利要求1所述的方法，其中，确定所述MBMS承载的所述用户面数据发生拥塞或过载包括：当一个或多个eNB检测出所述用户面数据发生拥塞或过载时，确定所述一个或多个eNB所在的MBSFN区域或MBMS业务区域发生拥塞或过载。
  3. 根据权利要求1所述的方法，其中，根据判定条件检测到所述用户面数据发生拥塞或过载，其中，所述判定条件为预先配置完成或者携带在从所述GCS AS接收到的请求消息中。
  4. 根据权利要求1至3中任一项所述的方法，其中，所述第一指示信息中携带的内容包括以下至少之一：
    拥塞或过载标识；
    一个或多个小区标识，其中，所述小区标识包括以下至少之一：演进的统一陆地无线接入网E-UTRAN小区标识、E-UTRAN小区全球标识；
    一个或多个业务区域标识SAI；
    一个或多个单频网多媒体广播多播业务MBSFN区域标识；
    一个或多个MBMS业务标识；
    拥塞或过载开始标识；
    其中，所述拥塞或过载标识用于指示在当前网络中所述用户面数据的负载是在发生拥塞还是在发生过载，所述小区标识用于指示发生拥塞或过载所影响到的小区，所述SAI用于指示发生拥塞或过载所影响到的MBMS业务区域， MBSFN区域标识用于指示发生拥塞或过载的MBSFN区域，所述MBMS业务标识用于指示发生拥塞或过载所影响到的集群业务。
  5. 根据权利要求4所述的方法，其中，向所述GCS AS发送所述第一指示信息包括以下方式之一：
    将发生拥塞或过载的全部MBMS业务标识发送至所述MCE，以使所述MCE根据第一参数与第二参数的对应关系从所述全部MBMS业务标识中选取待上报的MBMS业务标识，并上报至所述GCS AS，其中，第一参数为服务质量等级标识QCI或分配与保持优先级ARP，第二参数为临时移动组标识TMGI；
    根据接收到的来自于所述GCS AS的请求消息上报在该第一请求消息中指定的SAI中的TMGI状态信息。
  6. 根据权利要求1所述的方法，其中，在向所述GCS AS发送所述第一指示信息之前，还包括：
    判断是否需要向所述GCS AS发送所述第一指示信息的触发条件包括以下之一：
    在发生拥塞或过载开始事件，或者，发生拥塞或过载结束事件的情况下，向所述GCS AS发送所述第一指示信息；
    在接收到来自于所述GCS AS的请求消息后，向所述GCS AS发送所述第一指示信息；
    在接收到来自于所述GCS AS的请求消息并且发生拥塞或过载开始事件，或者，接收到来自于所述GCS AS的请求消息并且发生拥塞或过载结束事件后，向所述GCS AS发送所述第一指示信息；
    按照预设周期向所述GCS AS发送所述第一指示信息；
    在每次重新启动后向所述GCS AS发送所述第一指示信息。
  7. 根据权利要求1所述的方法，其中，在向所述GCS AS发送所述第一指示信息之后，还包括：
    确定所述用户面数据发生的拥塞或过载已经恢复，配置第二指示信息；
    向所述GCS AS发送所述第二指示信息，其中，所述第二指示信息用于为所述GCS AS选择对已停止的集群业务继续通过单播承载的方式进行发送或者恢复MBMS承载的方式进行发送提供参考依据。
  8. 一种请求消息的处理方法，包括：
    接收来自于组通信业务GCS应用服务器AS的请求消息，其中，所述请求消息是在所述GCS AS从基站接收到用于指示通过多媒体广播多播业务MBMS承载的用户面数据发生拥塞或过载的指示信息后发出的，所述请求消息用于请求停止通过所述MBMS承载的因所述用户面数据发生拥塞或过载而受到影响的集群业务；
    根据所述请求消息配置停止通过所述MBMS承载发送所述受到影响的集群业务。
  9. 根据权利要求8所述的方法，其中，经由广播多播服务中心BM-SC接收来自于所述GCS AS的所述请求消息。
  10. 根据权利要求8所述的方法，其中，根据所述请求消息配置停止通过所述MBMS承载发送所述受到影响的集群业务包括：
    根据所述请求消息获取待停止多播承载的MBSFN区域和MBMS业务；
    对所述待停止多播承载的MBSFN区域和MBMS业务进行配置。
  11. 根据权利要求8至10中任一项所述的方法，其中，所述请求消息中携带的信息包括以下至少之一：
    小区标识、MBMS业务标识、业务区域标识。
  12. 一种指示信息的处理方法，包括：
    接收来自于基站的指示信息，其中，所述指示信息用于指示多媒体广播多播业务MBMS承载的用户面数据发生拥塞或过载；
    根据所述指示信息向多小区多播协调实体MCE发送请求消息，其中，所述请求消息用于请求停止通过所述MBMS承载的因所述用户面数据发生拥塞或过载而受到影响的集群业务。
  13. 根据权利要求12所述的方法，其中，经由广播多播服务中心BM-SC向所述MCE发送所述请求消息。
  14. 根据权利要求12所述的方法，其中，在根据所述指示信息向所述MCE发送所述请求消息之前，还包括：
    根据所述指示信息确定因所述用户面数据发生拥塞或过载而受到影响的目标用户设备UE和/或集群业务标识；
    在所述用户面数据发生拥塞的情况下，为所述目标UE建立单播承载并通过所述单播承载发送与所述集群业务标识对应的集群业务；或者，在所述用户面数据发生过载的情况下，将与所述集群业务标识对应的集群业务设置为排队等待状态，直至等到过载结束后再进行发送；或者，在所述用户面数据发生过载的情况下，抢占现有集群业务的资源发送与所述集群业务标识对应的集群业务。
  15. 根据权利要求12至14中任一项所述的方法，其中，所述请求消息中携带的信息包括以下至少之一：
    小区标识、MBMS业务标识、业务区域标识。
  16. 一种指示信息的确定装置，包括：
    配置模块，设置为确定多媒体广播多播业务MBMS承载的用户面数据发生拥塞或过载，配置第一指示信息；
    发送模块，设置为向组通信业务GCS应用服务器AS发送第一指示信息，其中，所述第一指示信息用于在所述GCS AS请求多小区多播协调实体MCE或基站eNB停止通过所述MBMS承载的因所述用户面数据发生拥塞或过载而受到影响的集群业务的过程中提供参考依据。
  17. 根据权利要求16所述的装置，其中，所述配置模块，设置为当检测出所述用户面数据发生拥塞或过载时，确定自身所在的MBSFN区域或MBMS业务区域发生拥塞或过载。
  18. 根据权利要求16所述的装置，其中，所述检测模块，设置为根据判定条件检测到所述用户面数据发生拥塞或过载，其中，所述判定条件为预先配置完成或者携带在从所述GCS AS接收到的请求消息中。
  19. 根据权利要求16至18中任一项所述的装置，其中，所述第一指示信息中携带的内容包括以下至少之一：
    拥塞或过载标识；
    一个或多个小区标识，其中，所述小区标识包括以下至少之一：演进的统一陆地无线接入网E-UTRAN小区标识、E-UTRAN小区全球标识；
    一个或多个业务区域标识SAI；
    一个或多个单频网多媒体广播多播业务MBSFN区域标识；
    一个或多个MBMS业务标识；
    拥塞或过载开始标识；
    其中，所述拥塞或过载标识用于指示在当前网络中所述用户面数据的负载是在发生拥塞还是在发生过载，所述小区标识用于指示发生拥塞或过载所影响到的小区，所述SAI用于指示发生拥塞或过载所影响到的MBMS业务区域，MBSFN区域标识用于指示发生拥塞或过载的MBSFN区域，所述MBMS业务标识用于指示发生拥塞或过载所影响到的集群业务。
  20. 根据权利要求19所述的装置，其中，所述发送模块，设置为向所述GCS AS发送所述第一指示信息包括以下方式之一：
    将发生拥塞或过载的全部MBMS业务标识发送至所述MCE，以使所述MCE根据第一参数与第二参数的对应关系从所述全部MBMS业务标识中选取待上报的MBMS业务标识，并上报至所述GCS AS，其中，第一参数为服务质量等级标识QCI或分配与保持优先级ARP，第二参数为临时移动组标识TMGI；
    根据接收到的来自于所述GCS AS的第一请求消息上报在该第一请求消息中指定的SAI中的TMGI状态信息。
  21. 根据权利要求16所述的装置，其中，所述装置还包括：判断模块；
    所述判断模块，设置为判断是否需要向所述GCS AS发送所述第一指示信息的触发条件包括以下之一：
    在发生拥塞或过载开始事件，或者，发生拥塞或过载结束事件的情况下，向所述GCS AS发送所述第一指示信息；
    在接收到来自于所述GCS AS的请求消息后，向所述GCS AS发送所述第一指示信息；
    在接收到来自于所述GCS AS的请求消息并且发生拥塞或过载开始事件，或者，接收到来自于所述GCS AS的请求消息并且发生拥塞或过载结束事件后，向所述GCS AS发送所述第一指示信息；
    按照预设周期向所述GCS AS发送所述第一指示信息；
    在每次重新启动后向所述GCS AS发送所述第一指示信息。
  22. 根据权利要求16所述的装置，其中，
    所述配置模块，还设置为确定所述用户面数据发生的拥塞或过载已经恢复，配置第二指示信息；
    所述发送模块，还设置为向所述GCS AS发送所述第二指示信息，其中，所述第二指示信息用于为所述GCS AS选择对已停止的集群业务继续通过单播承载的方式进行发送或者恢复MBMS承载的方式进行发送提供参考依据。
  23. 一种请求消息的处理装置，包括：
    接收模块，设置为接收来自于组通信业务GCS应用服务器AS的请求消息，其中，所述请求消息是在所述GCS AS从基站接收到用于指示通过多媒体广播多播业务MBMS承载的用户面数据发生拥塞或过载的指示信息后发出的，所述请求消息用于请求停止通过所述MBMS承载的因所述用户面数据发生拥塞或过载而受到影响的集群业务；
    处理模块，设置为根据所述请求消息配置停止通过所述MBMS承载发送所述受到影响的集群业务。
  24. 根据权利要求23所述的装置，其中，所述接收模块，设置为经由广播多播服务中心BM-SC接收来自于所述GCS AS的所述请求消息。
  25. 根据权利要求23所述的装置，其中，所述处理模块包括：
    获取单元，设置为根据所述请求消息获取待停止多播承载的MBSFN区域和MBMS业务；
    处理单元，设置为对所述待停止多播承载的MBSFN区域和MBMS业务进行配置。
  26. 根据权利要求23至25中任一项所述的装置，其中，所述请求消息中携带的信息包括以下至少之一：
    小区标识、MBMS业务标识、业务区域标识。
  27. 一种指示信息的处理装置，包括：
    接收模块，设置为接收模块接收来自于基站的指示信息，其中，所述指示信息用于指示多媒体广播多播业务MBMS承载的用户面数据发生拥塞或过载；
    第一处理模块，设置为根据所述指示信息向多小区多播协调实体MCE发送请求消息，其中，所述请求消息用于请求停止通过所述MBMS承载的因所述用户面数据发生拥塞或过载而受到影响的集群业务。
  28. 根据权利要求27所述的装置，其中，所述第一处理模块，设置为经由广播多播服务中心BM-SC向所述MCE发送所述请求消息。
  29. 根据权利要求27所述的装置，其中，所述装置还包括：
    确定模块，设置为根据所述指示信息确定因所述用户面数据发生拥塞或过载而受到影响的目标用户设备UE和/或集群业务标识；
    第二处理模块，设置为在所述用户面数据发生拥塞的情况下，为所述目标UE建立单播承载并通过所述单播承载发送与所述集群业务标识对应的集群业务；或者，在所述用户面数据发生过载的情况下，将与所述集群业务标识对应的集群业务设置为排队等待状态，直至等到过载结束后再进行发送；或者，在所述用户面数据发生过载的情况下，抢占现有集群业务的资源发送与所述集群业务标识对应的集群业务。
  30. 根据权利要求27至29中任一项所述的装置，其中，所述请求消息中携带的信息包括以下至少之一：
    小区标识、MBMS业务标识、业务区域标识。
  31. 一种计算机存储介质，所述计算机存储介质中存储有计算机可执行指令，所述计算机可执行指令用于权利要求1至7任一项所述的指示信息的确定方法，或者，权利要求8至11任一项所述的请求消息的处理方法，或者，权利要求12至15任一项所述的指示信息的处理方法。
PCT/CN2015/074801 2014-09-24 2015-03-20 指示信息的确定、处理以及请求消息的处理方法、装置及计算机存储介质 WO2016045325A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP15843224.5A EP3200484B1 (en) 2014-09-24 2015-03-20 Method and system for treatment of network overload or congestion
US15/513,845 US20170295211A1 (en) 2014-09-24 2015-03-20 Method and Device for Determining and Processing Indication Information, Method and Device for Processing Request Message and Computer Storage Medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410495828.9A CN104270725B (zh) 2014-09-24 2014-09-24 指示信息的确定、处理以及请求消息的处理方法及装置
CN201410495828.9 2014-09-24

Publications (1)

Publication Number Publication Date
WO2016045325A1 true WO2016045325A1 (zh) 2016-03-31

Family

ID=52162201

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/074801 WO2016045325A1 (zh) 2014-09-24 2015-03-20 指示信息的确定、处理以及请求消息的处理方法、装置及计算机存储介质

Country Status (4)

Country Link
US (1) US20170295211A1 (zh)
EP (1) EP3200484B1 (zh)
CN (1) CN104270725B (zh)
WO (1) WO2016045325A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4109941A4 (en) * 2020-02-19 2024-02-28 Zte Corp METHOD, APPARATUS AND SYSTEM FOR CONVENTION CONTROL, DEVICE AND SUPPORT

Families Citing this family (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105323722B (zh) 2014-07-31 2020-05-26 中兴通讯股份有限公司 基于mbms承载的集群通信中拥塞状态上报方法及系统
CN105323723A (zh) * 2014-07-31 2016-02-10 中兴通讯股份有限公司 基于mbms承载的集群通信中查询节点状态的方法及系统
CN104270725B (zh) * 2014-09-24 2018-04-10 中兴通讯股份有限公司 指示信息的确定、处理以及请求消息的处理方法及装置
CN106211087A (zh) * 2015-01-16 2016-12-07 中兴通讯股份有限公司 数据处理方法及装置
WO2016140538A1 (ko) * 2015-03-03 2016-09-09 엘지전자 주식회사 무선 통신 시스템에서 mbms 관련 신호 송수신 방법 및 이를 위한 장치
WO2016163995A1 (en) 2015-04-07 2016-10-13 Nokia Solutions And Networks Oy Network location reporting broadcast bearer management
US10547984B2 (en) * 2015-09-25 2020-01-28 Lg Electronics Inc. Method and device for stopping SCPTM transmission
CN107040996B (zh) * 2016-02-04 2023-11-21 中兴通讯股份有限公司 车联网业务标识的处理方法及装置
CN107579807B (zh) * 2016-06-30 2020-11-27 电信科学技术研究院 数据传输的方法及装置
WO2018027931A1 (zh) * 2016-08-12 2018-02-15 华为技术有限公司 业务传输方法及无线通信设备
ES2721505T3 (es) * 2016-11-01 2019-08-01 Ericsson Telefon Ab L M Informe de interrupción del servicio
WO2019192780A1 (en) * 2018-04-06 2019-10-10 Telefonaktiebolaget Lm Ericsson (Publ) Delivering content in multiple areas using hierarchical area identifiers
CN112261124B (zh) * 2020-10-20 2023-10-13 亿咖通(湖北)技术有限公司 车辆状态数据的上报方法和系统以及车辆状态的查看方法
WO2023051193A1 (en) * 2021-09-29 2023-04-06 Telefonaktiebolaget Lm Ericsson (Publ) Network nodes and methods therein for notification event enhancement

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101166104A (zh) * 2006-10-16 2008-04-23 中兴通讯股份有限公司 用于ptm承载模式下的重计数周期调整装置及方法
CN101299831A (zh) * 2007-04-30 2008-11-05 中兴通讯股份有限公司 Mbms优选频率层选择方法及装置
CN101479997A (zh) * 2006-10-30 2009-07-08 华为技术有限公司 用户设备mbms测量结果报告的负载控制
CN104270725A (zh) * 2014-09-24 2015-01-07 中兴通讯股份有限公司 指示信息的确定、处理以及请求消息的处理方法及装置

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100461877C (zh) * 2006-12-31 2009-02-11 华为技术有限公司 一种对多媒体广播组播服务负载控制的方法
US9237483B2 (en) * 2010-12-30 2016-01-12 Motorola Solutions, Inc. Methods for managing resource utilization in a long term evolution communication system
CN102790948B (zh) * 2011-05-17 2017-04-05 中兴通讯股份有限公司 一种指示mbms业务中断的方法、装置及用户设备
CN102291688B (zh) * 2011-09-23 2014-03-19 电信科学技术研究院 一种基于mbms业务的切换方法和设备
CN105472663B (zh) * 2014-07-04 2020-12-25 北京三星通信技术研究有限公司 无线资源管理的方法和装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101166104A (zh) * 2006-10-16 2008-04-23 中兴通讯股份有限公司 用于ptm承载模式下的重计数周期调整装置及方法
CN101479997A (zh) * 2006-10-30 2009-07-08 华为技术有限公司 用户设备mbms测量结果报告的负载控制
CN101299831A (zh) * 2007-04-30 2008-11-05 中兴通讯股份有限公司 Mbms优选频率层选择方法及装置
CN104270725A (zh) * 2014-09-24 2015-01-07 中兴通讯股份有限公司 指示信息的确定、处理以及请求消息的处理方法及装置

Non-Patent Citations (1)

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

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4109941A4 (en) * 2020-02-19 2024-02-28 Zte Corp METHOD, APPARATUS AND SYSTEM FOR CONVENTION CONTROL, DEVICE AND SUPPORT

Also Published As

Publication number Publication date
CN104270725B (zh) 2018-04-10
CN104270725A (zh) 2015-01-07
US20170295211A1 (en) 2017-10-12
EP3200484A1 (en) 2017-08-02
EP3200484B1 (en) 2020-04-22
EP3200484A4 (en) 2017-12-13

Similar Documents

Publication Publication Date Title
WO2016045325A1 (zh) 指示信息的确定、处理以及请求消息的处理方法、装置及计算机存储介质
US10687179B2 (en) Service continuity for group communication over LTE eMBMS
EP3198958B1 (en) Managing communication resources
US10334480B2 (en) Method, system, device for controlling congestion or overload and evolved node B (eNB)
WO2016015472A1 (zh) 基于mbms承载的集群通信中查询节点状态的方法及系统、存储介质
WO2016015465A1 (zh) 基于mbms承载的集群通信中拥塞状态上报方法及系统、存储介质
KR20210127978A (ko) Mbms 다중 레벨 베어러 품질 표시자에 기초한 동적 mbms/유니캐스트 베어러 확립

Legal Events

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

Ref document number: 15843224

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 15513845

Country of ref document: US

NENP Non-entry into the national phase

Ref country code: DE

REEP Request for entry into the european phase

Ref document number: 2015843224

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2015843224

Country of ref document: EP