WO2016015465A1 - 基于mbms承载的集群通信中拥塞状态上报方法及系统、存储介质 - Google Patents

基于mbms承载的集群通信中拥塞状态上报方法及系统、存储介质 Download PDF

Info

Publication number
WO2016015465A1
WO2016015465A1 PCT/CN2015/072811 CN2015072811W WO2016015465A1 WO 2016015465 A1 WO2016015465 A1 WO 2016015465A1 CN 2015072811 W CN2015072811 W CN 2015072811W WO 2016015465 A1 WO2016015465 A1 WO 2016015465A1
Authority
WO
WIPO (PCT)
Prior art keywords
congestion
overload
cluster service
network node
application server
Prior art date
Application number
PCT/CN2015/072811
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 EP15827932.3A priority Critical patent/EP3188517B1/en
Priority to US15/514,027 priority patent/US10104577B2/en
Publication of WO2016015465A1 publication Critical patent/WO2016015465A1/zh

Links

Images

Classifications

    • 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/0247—Traffic management, e.g. flow control or congestion control based on conditions of the access network or the infrastructure network
    • 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/0252—Traffic management, e.g. flow control or congestion control per individual bearer or channel
    • 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
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/10—Flow control between communication endpoints
    • 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/10—Flow control between communication endpoints
    • H04W28/14—Flow control between communication endpoints using intermediate storage
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • 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
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H04W4/08—User group management

Definitions

  • the present invention relates to a trunking communication technology based on a Multimedia Broadcast Multicast Service (MBMS), and more particularly to a method and system for reporting congestion status in a cluster communication based on an MBMS bearer, and a storage medium.
  • MBMS Multimedia Broadcast Multicast Service
  • the trunking communication system is a dedicated wireless communication system developed for industrial users' command and dispatching needs for specific industry applications. A large number of wireless users share a small number of wireless channels in the system, and the command and dispatch is the main application. It is a multi-purpose and high-performance system. 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 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.
  • FIG. 1 shows the system architecture of the LTE GCSE.
  • the 3rd Generation Partnership Project (3GPP) proposes Multimedia Broadcast Multicast Service (MBMS), which is a data source to multiple
  • MBMS Multimedia Broadcast Multicast Service
  • the technology for transmitting data by the target mobile terminal realizes sharing of resources of the network (including the core network and the access network), and improves utilization of network resources (especially air interface resources).
  • 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.
  • FIG. 2 shows a schematic diagram of the architecture of MBMS in LTE.
  • the industry is currently discussing the possibility of implementing cluster communication using MBMS technology.
  • cluster communication using MBMS technology.
  • the multicast mode is to receive the cluster service through the MBMS bearer. In this case, the UE needs to have the MBMS receiving capability.
  • the prior art has found that when the cluster service is sent through the MBMS bearer, if multiple cluster services start at the same time, the network may be congested or overloaded, and the GCS AS does not know whether the network is congested or overloaded. The information cannot be processed in time, resulting in the target UE not receiving the required cluster services normally.
  • the embodiments of the present invention provide a method and system for reporting congestion status in a cluster communication based on an MBMS bearer, and a storage medium, which can eliminate the impact of network congestion or overload on the cluster service.
  • a method for reporting congestion status in a cluster communication based on an MBMS bearer including:
  • the cluster service application server When the cluster service application server receives the user plane and/or control plane congestion or overload indication information reported by the network node of the cluster service based on the multimedia broadcast multicast service MBMS, the affected target user equipment UE and the cluster service are determined and executed. Corresponding strategies reduce the impact of congestion or overload on the target UE receiving cluster services.
  • the method further includes:
  • the cluster service application server When receiving the recovery indication information reported by the network node, the cluster service application server selects a bearer mode for sending the cluster service;
  • the recovery is that the network node detects congestion or overload termination.
  • the MBMS bearer includes a core network bearer and an air interface bearer
  • the MBMS bearer is established before the start of the cluster service.
  • the network node includes at least one of the following:
  • the base station eNodeB the multimedia multicast broadcast service coordination function entity MCE, the mobility management unit MME, the MBMS gateway MBMS GW, and the broadcast multicast service center BM-SC.
  • the congestion includes control plane signaling in the network and/or a user plane load reaches a preset threshold
  • the overload includes control plane signaling in the network and/or user plane load exceeding the load of the network node, the network node being unable to continue processing additional signaling and/or additional user plane loading.
  • the congestion/overload indication information includes at least one of the following:
  • Congestion/overload identification MBMS service area identification SAI, MBMS service identification TMGI, congestion/overload start/end identification;
  • the congestion/overload identifier is used to indicate whether the network is congested or overloaded; the SAI is used to indicate a service area affected by congestion/overload; and the TMGI is used to indicate a cluster service affected by congestion/overload.
  • the method further includes:
  • the network node When the network node generates a congestion/overload start or end event, reporting the congestion/overload start or end indication information to the cluster service application server;
  • the network node after receiving the request message for reporting the congestion/overload indication sent by the cluster service application server, reports the indication information of the congestion/overload start or end to the cluster service application server.
  • the strategy includes:
  • a unicast bearer is established for the target UE, and the cluster service is sent through the unicast bearer;
  • the cluster service When an overload occurs, the cluster service is queued, and the queued cluster service is sent after the overload is over. Otherwise, the high-priority cluster service can preempt the resources of the existing cluster service and ensure the transmission of the high-priority cluster service.
  • a specific set is included in the cluster service that affects the target UE reception.
  • the specific cluster service is a congestion/overload service determined by the QCI or the reserved reservation priority ARP according to the service quality level of the service;
  • the method further includes:
  • the target UE When congestion or overload occurs, the target UE has an impact on receiving normal MBMS services.
  • the method further includes:
  • the network node When the specific cluster service is congested/overloaded, the network node reports all the congestion/overloaded service identifiers TMGI to the network element between the network node and the cluster service application server; the network element selection is congested. / TMGI of the specific cluster service that is overloaded is sent to the cluster service application server;
  • the network node receives the request message of the SAI and the TMGI of the congestion service/suppressed by the cluster service application server, and reports the TMGI of the specific cluster service in the SAI to the cluster service application server;
  • the network node reports the TMGI of all services in the SAI to the cluster service application server after receiving the request message that the cluster service application server reports the congestion/overload SAI.
  • the method further includes:
  • the triggering manner of the network node reporting the related information to the cluster service application server is any one of the following: an event triggering, a cluster service application server request triggering, an event, and a cluster service application server request triggering;
  • the event is triggered by the network node reporting to the cluster service application server when a congestion/overload start/end event occurs on the network node;
  • the cluster service application server request is triggered, and the cluster service application server sends a report request message to the network node, and the network node that receives the request message reports to the cluster service application server;
  • the event and the cluster service application server request are triggered, and the cluster service application server sends a report request message to the network node, and the network node that receives the request message reports to the cluster service application server when a congestion/overload start/end event occurs.
  • a congestion state reporting system in a cluster communication based on an MBMS bearer including a cluster service application server and a network node, where:
  • the network node is configured to transmit the cluster service based on the MBMS bearer of the multimedia broadcast multicast service; and send the user plane and/or control plane congestion or overload indication information to the cluster service application server when the user plane and/or the control plane are congested or overloaded; ;
  • the cluster service application server is configured to receive the user plane and/or control plane congestion or overload indication information, determine the affected target user equipment UE and the cluster service, and execute a corresponding policy to reduce congestion or overload to receive the cluster service for the target UE. Impact.
  • the network node is further configured to: when detecting that the user plane and/or the control plane is congested or overloaded, send the restoration indication information to the cluster service application server;
  • the cluster service application server is further configured to: when receiving the restoration indication information, select a bearer mode for sending the cluster service;
  • the recovery is that the network node detects congestion or overload termination.
  • the MBMS bearer includes a core network bearer and an air interface bearer
  • the MBMS bearer is established before the start of the cluster service.
  • the network node includes at least one of the following:
  • the base station eNodeB the multimedia multicast broadcast service coordination function entity MCE, the mobility management unit MME, the MBMS gateway MBMS GW, and the broadcast multicast service center BM-SC.
  • the congestion includes control plane signaling in the network and/or a user plane load reaches a preset threshold
  • the overload includes control plane signaling in the network and/or user plane load exceeding the load of the network node, and the network node cannot continue to process additional signaling and/or additional user plane load.
  • the congestion/overload indication information includes at least one of the following:
  • Congestion/overload identification MBMS service area identification SAI, MBMS service identification TMGI, congestion/overload start/end identification;
  • the congestion/overload identifier is used to indicate whether the network is congested or overloaded; the SAI is used to indicate a service area affected by congestion/overload; and the TMGI is used to indicate a cluster service affected by congestion/overload.
  • the network node is further configured to report, to the cluster service application server, indication information about a congestion/overload start or end when a congestion/overload start or end event occurs;
  • the cluster service application server sends a request message for reporting the congestion/overload indication to the network node; the network node is further configured to: after receiving the request message for reporting the congestion/overload indication, to the cluster service The application server reports the indication that the congestion/overload starts or ends.
  • the strategy includes:
  • a unicast bearer is established for the target UE, and the cluster service is sent through the unicast bearer;
  • the cluster service When an overload occurs, the cluster service is queued, and the queued cluster service is sent after the overload is over. Otherwise, the high-priority cluster service can preempt the resources of the existing cluster service and ensure the transmission of the high-priority cluster service.
  • system further includes a network element between the network node and the cluster service application server;
  • the network node is further configured to: when the specific cluster service is congested/overloaded, report all the congestion/overload service identifiers TMGI to the network element; the network element is configured to select a specific cluster in which congestion/overload occurs.
  • the TMGI of the service is sent to the cluster service application server.
  • the cluster service application server is further configured to send, to the network node, a request message for reporting congestion/overload SAI and TMGI;
  • the network node is further configured to report the TMGI of the specific cluster service in the SAI to the cluster service application server after receiving the request message.
  • the cluster service application server is further configured to send, to the network node, a request message for reporting a congestion/overload SAI;
  • the network node is further configured to report the TMGI of all services in the SAI to the cluster service application server after receiving the request message.
  • the triggering manner of the network node reporting related information to the cluster service application server is any one of the following: an event triggering, a cluster service application server request triggering, an event, and a cluster service application server request triggering;
  • the event is triggered by the network node reporting to the cluster service application server when a congestion/overload start/end event occurs on the network node;
  • the cluster service application server request is triggered, and the cluster service application server sends a report request message to the network node, and the network node that receives the request message reports to the cluster service application server;
  • the event and the cluster service application server request are triggered, and the cluster service application server sends a report request message to the network node, and the network node that receives the request message reports to the cluster service application server when a congestion/overload start/end event occurs.
  • a storage medium storing a computer program configured to perform the aforementioned congestion state reporting method in a cluster communication based on an MBMS bearer.
  • the 3GPP network node that uses the MBMS bearer to send the cluster service detects the congestion of the user plane and/or the control plane or overloads the network service application server (GCS AS, Group Communication Service Application). Server) reports congestion or overload indication information, and the AS that receives the congestion or overload indication information determines the affected target UE and the cluster service, and performs corresponding policies to reduce the impact of network congestion or overload on the target UE receiving the cluster service; Node detected congestion or overload
  • the recovery indication information is reported to the cluster service application server (GCS AS), and the AS that receives the restoration indication information selects the bearer mode for transmitting the cluster service.
  • 1 is a schematic structural diagram of a trunking communication system
  • FIG. 2 is a schematic diagram of an MBMS communication architecture
  • FIG. 3 is a flowchart of a method for reporting congestion status in a cluster communication based on an MBMS bearer according to an embodiment of the present invention
  • FIG. 4 is a flowchart of a method for reporting congestion status in a cluster communication based on an MBMS bearer according to Embodiment 1 of the present invention
  • FIG. 5 is a flowchart of a method for reporting congestion status in a cluster communication based on an MBMS bearer according to Embodiment 2 of the present invention
  • FIG. 6 is a flowchart of a method for reporting congestion status in a cluster communication based on an MBMS bearer according to Embodiment 3 of the present invention
  • FIG. 7 is a flowchart of a method for reporting congestion status in a cluster communication based on MBMS bearer according to Embodiment 4 of the present invention.
  • FIG. 8 is a flowchart of a method for reporting congestion status in a cluster communication based on MBMS bearer according to Embodiment 5 of the present invention.
  • FIG. 9 is a flowchart of a method for reporting congestion status in a cluster communication based on MBMS bearer according to Embodiment 6 of the present invention.
  • FIG. 10 is a schematic structural diagram of a congestion state reporting system in a cluster communication based on an MBMS bearer according to an embodiment of the present invention.
  • MBMS refers to evolved MBMS, ie, eMBMS
  • AS refers to GCS AS.
  • the method for reporting congestion/overload status in a cluster communication based on MBMS bearer includes the following steps:
  • step 101 the GCS AS sends the cluster service through the MBMS bearer.
  • the cluster UE Before the start of step 101, the cluster UE first registers with the GCS AS corresponding to the cluster service. In this way, the GCS AS can know how many UEs have joined a certain cluster service.
  • the MBMS bearer is pre-established before the start of the cluster service.
  • the pre-establishment means that a certain cluster has not yet started, and the MBMS bearer is established in advance.
  • an MBMS bearer an MBSFN bearer, a multicast bearer, and a point-to-multipoint PTM bearer.
  • the MBMS bearer includes a core network bearer, that is, an Evolved Packet Internet Core (EPC) bearer and an air interface bearer.
  • EPC Evolved Packet Internet Core
  • RAN Radio Access Network
  • MCE multimedia multi-cell/multicast coordination entity
  • the above-mentioned cluster service may also be a normal MBMS service.
  • the normal MBMS service and the cluster service may be distinguished by different QCI parameters.
  • the corresponding MBMS bearer does not need to be pre-established.
  • step 102 the network node detects congestion and/or overload.
  • the network node includes: an eNodeB, an MCE, a Mobility Management Entity (MME), an MBMS Gateway (MBMS GW, MBMS GateWay), or a wide Broadcast Multicast Service Center (BM-SC).
  • MME Mobility Management Entity
  • MBMS GW MBMS Gateway
  • BM-SC Broadcast Multicast Service Center
  • the congestion refers to that the control plane signaling and/or the user plane load in the network reach a preset threshold, where the overload refers to that the control plane signaling and/or the user plane load in the network exceeds the load of the network node, and the network node Additional signaling and/or additional user plane loading cannot continue to be processed.
  • Step 103 The network node sends the congestion/overload indication information of the network node to the AS.
  • the congestion/overload indication information includes at least one of the following: a congestion/overload identifier, an MBMS Service Area Identifier (SAI), an MBMS Service Identity (TMGI, Temporary Mobile Group Identity), and a congestion/overload start/end identifier.
  • SAI MBMS Service Area Identifier
  • TMGI MBMS Service Identity
  • TMGI Temporary Mobile Group Identity
  • the congestion/overload indicator is used to indicate whether the network is congested or overloaded; the SAI is used to indicate the service area affected by congestion/overload; and the TMGI is used to indicate the cluster service affected by congestion/overload.
  • the content of congestion/overload start/end may include at least one of the following: start (indicated by 1 or true), end (indicated by 0 or false).
  • Congestion/overload start/end ie, congestion/overload start is equivalent to the current occurrence of congestion/overload, and congestion/overload termination is equivalent to the current no congestion/overload or the beginning of congestion/overload termination.
  • the congestion of the node refers to that the control plane signaling and/or the user plane data load in the network reach a certain preset threshold.
  • the overload of the node means that the control plane signaling and/or user plane load in the network exceeds the load of the network node, and the network node cannot continue to process additional control plane signaling and/or additional user plane data load.
  • the content of the MBMS service congestion/overload information is as follows: suppose the congestion is indicated by C, and the overload is indicated by O. For example:
  • ⁇ SA2 TMGI5, TMGI6; O, false ⁇
  • TMGI1, TMGI2, and TMGI3 in SA1 are congested; TMGI5 in SA2, The TMGI6 overload ends; the TMGI10 congestion in SA3 ends.
  • 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 congestion/overload service includes any one of the following: a normal MBMS service, and a specific cluster service. Considering that certain cluster services (such as PTT, Push To Talk) may be congested/overloaded. According to the QoS information of the service, such as QCI or ARP, it is determined that the traffic that is congested/overloaded is a specific cluster service, because the eNB does not know the QoS of the service.
  • cluster services such as PTT, Push To Talk
  • the eNB reports all the congestion/overload service identifier TMGI to the MCE, 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 congestion/overload occurs, and reports it to the GCS AS;
  • the AS requests the SAI and TMGI to report the status, and sends a request message to the eNB through the path AS->BM-SC->MBMS GW->MME->MCE->eNB, and the eNB passes eNB->MCE->MME-> MBMS GW->BM-SC->AS, reports the status of TMGI in a specific SAI to the AS.
  • the eNB reports all TMGI states in the SAI.
  • the reporting triggering mode is any one of the following: an event triggering, an AS request triggering, and the foregoing two are combined.
  • the event triggering report refers to the network node reporting the AS when the network node has a congestion/overload start/end event;
  • the AS request triggering means that the AS sends a request message to the network node, and the network node that receives the request reports the node status information to AS;
  • the combination of the two means that the AS sends a request message to the network node, and when the network node receiving the request has a congestion/overload start/end event, the network node reports to the AS.
  • the occurrence of a congestion/overload start/end event at the network node refers to: transitioning from a start state to an end state; or transitioning from an end state to a start state. That is: if there is no congestion/overload (equivalent to the last congestion/overload has ended), it is converted to start (equivalent to the current occurrence) Congestion/overload), the eNB needs to report; if there is congestion/overload (equivalent to start) to no congestion/overload (equivalent to the end), the eNB needs to report; and the eNB detects that the congestion state and the overload state occur with each other. Changes, the eNB also 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 104 the AS performs a policy to reduce the impact of congestion/overload.
  • the unicast bearer transmits the cluster service 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 resources of the existing cluster service.
  • step 105 the network node detects the end of congestion/overload.
  • the end of congestion/overload means that the network returns to normal, such as network signaling and or user plane load is lower than a preset threshold.
  • Step 106 The network node sends the recovery indication information to the AS.
  • the network node sends the indication information through an existing process.
  • the recovery indication information includes at least one of the following: a congestion/overload identifier, an MBMS SAI, a TMGI, and a congestion/overload end identifier.
  • Step 107 The AS selects a manner of sending 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.
  • the cluster service is continuously sent through the MBMS bearer.
  • the congestion state reporting method in the MBMS bearer-based cluster communication of the present example includes the following steps:
  • Step 201 The AS sends the cluster service by using the MBMS bearer.
  • the MBMS bearer of the cluster service is pre-established before the cluster service starts.
  • step 202 the MCE detects congestion/overload.
  • the congestion/overload is control plane signaling congestion/overload.
  • Step 203 The MCE sends congestion/overload indication information to the MME.
  • the MCE sends the indication information to the MME through the M3 interface, and the indication information can be implemented by extending the existing M3 interface signaling or creating a new M3 interface signaling procedure.
  • the indication information includes at least one of the following: congestion/overload identification, MBMS SAI, TMGI, congestion/overload start/end identification.
  • Step 204 The MME sends congestion/overload indication information to the MBMS GW.
  • the MME sends the congestion/overload indication information to the MBMS GW through the Sm interface, and the indication information can be implemented by extending the existing Sm interface signaling or creating a new Sm interface signaling procedure.
  • step 205 the MBMS GW sends congestion/overload indication information to the BM-SC.
  • the MBMS GW sends congestion/overload indication information to the BM-SC through the SGmb interface, and the indication information can be implemented by extending the existing SGmb interface signaling or creating a new SGmb interface signaling procedure.
  • Step 206 The BM-SC sends congestion/overload indication information to the AS.
  • the BM-SC sends congestion/overload indication information to the AS through the MB2 interface, and the indication information can be implemented by extending the existing MB2 interface signaling or creating a new MB2 interface signaling procedure.
  • step 207 the AS takes action to reduce the impact of congestion/overload.
  • the AS first determines the affected target UE and the cluster service, and takes different actions for the congestion and overload information. For example, when the congestion occurs, the AS uses the unicast bearer to send the cluster service. When the overload occurs, the AS queues the cluster service for overload and then sends the cluster service. Or use high-priority cluster services to seize the current Resources with cluster services.
  • step 208 the MCE detects the end of congestion/overload.
  • Step 209 The MCE sends the recovery indication information to the MME.
  • Step 210 The MME sends the recovery indication information to the MBMS GW.
  • step 211 the MBMS GW sends the restoration indication information to the BM-SC.
  • step 212 the BM-SC sends the recovery indication information to the AS.
  • Step 213 The AS selects a manner of sending the cluster service to the target UE.
  • the congestion state reporting method in the MBMS bearer-based cluster communication of the present example includes the following steps:
  • step 301 the AS sends the cluster service by using the MBMS bearer.
  • step 101 This step is exactly the same as step 101, and details are not described herein again.
  • step 302 the MME detects congestion/overload.
  • the congestion/overload refers to control plane signaling congestion/overload.
  • step 303 the MME sends congestion/overload indication information to the MBMS GW.
  • the MME sends congestion/overload indication information to the MBMS GW through the Sm interface.
  • step 304 the MBMS GW sends congestion/overload indication information to the BM-SC.
  • the MBMS GW sends congestion/overload indication information to the BM-SC through the SGmb interface.
  • the BM-SC sends congestion/overload indication information to the AS.
  • step 306 the AS takes action to reduce the impact of congestion/overload.
  • step 307 the MME detects the end of congestion/overload.
  • Step 308 the MME sends the recovery indication information to the MBMS GW.
  • the MME sends the recovery indication information to the MBMS GW through the Sm interface.
  • step 309 the MBMS GW sends the restoration indication information to the BM-SC.
  • the MBMS GW sends recovery indication information to the BM-SC through the SGmb interface.
  • Step 310 The BM-SC sends the recovery indication information to the AS.
  • Step 311 The AS selects a mode for sending the cluster service to the UE.
  • the congestion state reporting method in the MBMS bearer-based cluster communication of the present example includes the following steps:
  • step 401 the AS sends the cluster service through the MBMS bearer.
  • step 402 the eNB detects congestion/overload.
  • the eNB detects congestion/overload of the user plane or control plane.
  • step 403 the eNB sends congestion/overload indication information to the MCE.
  • the eNB sends congestion/overload indication information to the MCE through the M2 interface.
  • the congestion/overload indication information includes at least one of the following: a congestion/overload identifier, an MBMS Service Area Identity (SAI), and an MBMS Service Identity (TMGI).
  • SAI MBMS Service Area Identity
  • TMGI MBMS Service Identity
  • the congestion/overload identifier is used to indicate network congestion or overload, wherein the network congestion identifier may include multiple levels, such as high, medium, and low, and the SAI is used to indicate a traffic area affected by congestion/overload; the TMGI is used to indicate congestion/ Cluster services affected by overload.
  • the content of the congestion/overload identifier may include at least one of the following: node congestion indication information, node overload indication information.
  • the congestion of the node refers to that the control plane signaling and/or the user plane load in the network reach a certain preset threshold
  • the node overload means that the network node cannot continue to process additional control panel signaling and/or additional user plane load.
  • the eNB detects that the Physical Multicast Channel (PMCH) is congested or overloaded.
  • PMCH Physical Multicast Channel
  • Step 404 The MCE sends congestion/overload indication information to the MME.
  • step 405 the MME sends congestion/overload indication information to the MBMS GW.
  • step 406 the MBMS GW sends congestion/overload indication information to the BM-SC.
  • step 407 the BM-SC sends congestion/overload indication information to the AS.
  • step 408 the AS takes action to reduce the impact of congestion/overload.
  • step 409 the eNB detects that the congestion overload ends.
  • step 410 the eNB sends recovery indication information to the MCE.
  • step 411 the MCE sends the recovery indication information to the MME.
  • step 412 the MME sends the recovery indication information to the MBMS GW.
  • step 413 the MBMS GW sends the restoration indication information to the BM-SC.
  • step 414 the BM-SC sends the recovery indication information to the AS.
  • step 415 the AS selects a mode for sending the cluster service to the UE.
  • the congestion state reporting method in the MBMS bearer-based cluster communication of the present example includes the following steps:
  • step 501 the AS sends the cluster service through the MBMS bearer.
  • step 101 This step is exactly the same as step 101, and details are not described herein again.
  • step 502 the MBMS-GW detects congestion/overload.
  • the congestion/overload is a control plane and/or user plane congestion/overload.
  • step 503 the MBMS GW sends congestion/overload indication information to the BM-SC.
  • step 504 the BM-SC sends congestion/overload indication information to the AS.
  • step 505 the AS takes action to reduce the impact of congestion/overload.
  • step 506 the MBMS-GW detects the end of congestion/overload.
  • step 507 the MBMS GW sends the restoration indication information to the BM-SC.
  • step 508 the BM-SC sends the recovery indication information to the AS.
  • step 509 the AS selects a mode for sending the cluster service to the UE.
  • the congestion state reporting method in the MBMS bearer-based cluster communication of the present example includes the following steps:
  • step 601 the AS sends the cluster service by using the MBMS bearer.
  • step 101 This step is exactly the same as step 101, and details are not described herein again.
  • step 602 the BM-SC detects congestion/overload.
  • the congestion/overload is a control plane and/or user plane congestion/overload.
  • step 603 the BM-SC sends congestion/overload indication information to the AS.
  • the AS takes action to reduce the effects of congestion/overload.
  • step 605 the BM-SC detects the end of congestion/overload.
  • step 606 the BM-SC sends the recovery indication information to the AS.
  • Step 607 The AS selects a mode for sending the cluster service to the UE.
  • the congestion state reporting method in the MBMS bearer-based cluster communication of the present example includes the following steps:
  • step 701 the AS sends the cluster service by using the MBMS bearer.
  • step 101 This step is exactly the same as step 101, and details are not described herein again.
  • step 702 the AS requests the eNB to report congestion/overload information.
  • the AS requests the eNB to report congestion/overload information through the sequence of the path AS to the BM-SC to the MBMS GW to the MME to the MCE to the eNB;
  • the AS request message includes one or more of the following: one or more SAIs; one or more TMGIs in each SAI; a congestion indication; an overload indication.
  • the eNB needs to report the congestion/overload indication of all TMGIs carried by the SAI;
  • the eNB needs to report the indicated congestion/overload indication of the TMGI;
  • the eNB needs to report congestion (start), or all TMGIs that are overloaded (started).
  • the congestion/overload refers to control plane signaling and/or user plane data congestion/overload.
  • step 703 the eNB is congested/overloaded. If yes, step 704 is performed. Otherwise, step 710 is performed.
  • the eNB determines whether user plane data congestion/overload occurs through the PMCH state, or determines whether control plane signaling congestion/overload occurs through air interface signaling.
  • step 704 the eNB sends congestion/overload indication information to the MCE.
  • the eNB is congested/overloaded, and sends congestion/overload indication information to the MCE through the M2 interface.
  • Step 705 The MCE sends congestion/overload indication information to the MME.
  • step 706 the MME sends congestion/overload indication information to the MBMS GW.
  • step 707 the MBMS GW sends congestion/overload indication information to the BM-SC.
  • step 708 the BM-SC sends congestion/overload indication information to the AS.
  • step 709 the AS takes action to reduce the impact of congestion/overload.
  • step 710 the eNB detects the node status, and proceeds to step 703.
  • the eNB does not generate congestion/overload, does not send indication information to the AS, and the eNB continues to detect the node status, and proceeds to step 703 to determine whether congestion/overload is present.
  • the congestion/overload event of the eNB refers to: transitioning from a start state to an end state; or transitioning from an end state to a start state. That is, if the original congestion and overload (equivalent to the last congestion/overload has ended) is converted to start (equivalent to the current congestion/overload), the eNB needs to report; if there is congestion/overload (equivalent) The eNB needs to report when it is not congested/overloaded (equivalent to the end); and the eNB detects that the congestion state and the overload state have changed from each other, and the eNB also needs to report.
  • C congestion indication, identified by ⁇ 0,1 ⁇
  • O overload indication, identified by ⁇ 0,1 ⁇
  • the embodiment of the present invention further describes a congestion state reporting system in a cluster communication based on an MBMS bearer, where the system includes a cluster service application server and a network node, where:
  • the network node is configured to transmit the cluster service based on the MBMS bearer of the multimedia broadcast multicast service; and send the user plane and/or control plane congestion or overload indication information to the cluster service application server when the user plane and/or the control plane are congested or overloaded; ;
  • the cluster service application server is configured to receive the user plane and/or control plane congestion or overload indication information, determine the affected target user equipment UE and the cluster service, and execute a corresponding policy to reduce congestion or overload to receive the cluster service for the target UE. Impact.
  • the network node is further configured to: when detecting that the user plane and/or the control plane is congested or overloaded, send the restoration indication information to the cluster service application server;
  • the cluster service application server is further configured to: when the recovery indication information is received, use the restored network node to select a bearer mode for sending the cluster service;
  • the recovery is that the network node detects congestion or overload termination.
  • the MBMS bearer includes a core network bearer and an air interface bearer.
  • the MBMS bearer is established before the start of the cluster service.
  • the network node includes at least one of the following:
  • the base station The base station, the multimedia multicast broadcast service coordination function entity MCE, the mobility management unit MME, the MBMS gateway MBMS GW, and the broadcast multicast service center BM-SC.
  • the congestion includes control plane signaling and/or user plane load in the network reaching a certain preset threshold
  • the overload includes control plane signaling in the network and/or user plane load exceeding the load of the network node, and the network node cannot continue to process additional signaling and/or additional user plane load.
  • the congestion/overload indication information includes at least one of the following:
  • Congestion/overload identification MBMS service area identification SAI, MBMS service identification TMGI, Congestion/overload start flag;
  • the congestion/overload identifier is used to indicate whether the network is congested or overloaded; the SAI is used to indicate a service area affected by congestion/overload; and the TMGI is used to indicate a cluster service affected by congestion/overload.
  • the network node is further configured to report, to the cluster service application server, indication information about the start or end of congestion/overload when a congestion/overload start or end event occurs;
  • the cluster service application server sends a request message for reporting the congestion/overload indication to the network node; the network node is further configured to: after receiving the request message for reporting the congestion/overload indication, to the cluster service The application server reports the indication that the congestion/overload starts or ends.
  • the strategy includes:
  • a unicast bearer is established for the target UE, and the cluster service is sent through the unicast bearer;
  • the cluster service When an overload occurs, the cluster service is queued, and the queued cluster service is sent after the overload is over. Otherwise, the high-priority cluster service can preempt the resources of the existing cluster service and ensure the transmission of the high-priority cluster service.
  • the cluster service that affects the target UE receiving includes a specific cluster service
  • the specific cluster service is a congestion/overload service determined by the QCI or the reserved reservation priority ARP according to the service quality level of the service;
  • the target UE When congestion or overload occurs, the target UE has an impact on receiving normal MBMS services.
  • the system further includes a network element between the network node and the cluster service application server;
  • the network node is further configured to: when the specific cluster service is congested/overloaded, report all the congestion/overload service identifiers TMGI to the network element; the network element is configured to select a specific cluster in which congestion/overload occurs.
  • the TMGI of the service is sent to the cluster service application server.
  • the cluster service application server is further configured to send, to the network node, a request message for reporting congestion/overload SAI and TMGI;
  • the network node is further configured to report the TMGI of the specific cluster service in the SAI to the cluster service application server after receiving the request message.
  • the cluster service application server is further configured to send, to the network node, a request message for reporting a congestion/overload SAI;
  • the network node is further configured to report the TMGI of all services in the SAI to the cluster service application server after receiving the request message.
  • the triggering manner of the network node reporting the related information to the cluster service application server is any one of the following: an event triggering, a cluster service application server request triggering, an event, and a cluster service application server request triggering;
  • the event is triggered by the network node reporting to the cluster service application server when a congestion/overload start/end event occurs on the network node;
  • the cluster service application server request is triggered, and the cluster service application server sends a report request message to the network node, and the network node that receives the request message reports to the cluster service application server;
  • the event and the cluster service application server request are triggered, and the cluster service application server sends a report request message to the network node, and the network node that receives the request message reports to the cluster service application server when a congestion/overload start/end event occurs.
  • the congestion state reporting system in the above-mentioned MBMS bearer-based trunking communication is set to implement the congestion state reporting method in the foregoing MBMS bearer-based cluster communication.
  • the function and structure of the related network element can refer to the foregoing method. It is understood by the description of the embodiments.
  • the congestion state reporting system in the cluster communication based on the MBMS bearer in the embodiment of the present invention includes:
  • Group communication service application server GCS AS 81 configured to receive congestion/overload and recovery indication The information is processed according to the indication information, and the manner of sending the cluster service is selected. And transmitting, to the network element related to the radio access network, related indication information for reporting congestion/overload.
  • the core network 82 is configured to detect a congestion/overload state, send indication information to the AS 81, and is configured to receive related indication information about congestion/overload sent by the network element associated with the radio access network.
  • the core network 82 includes the following BM-SC, MBMS GW, MME and other network nodes.
  • the MCE 83 is configured to detect a congestion/overload state, receive congestion/overload indication information sent by the eNB 84, and send congestion/overload indication information to the AS 81 through the core network 82.
  • the eNB 84 is configured to detect a congestion/overload state, receive indication information of the MCE 83, and send congestion/overload indication information to the AS 81 through the MCE 83 and the core network 82.
  • the embodiment of the present invention further describes a storage medium in which a computer program is stored, and the computer program is configured to perform a congestion state reporting method in a cluster communication based on MBMS bearer in the foregoing embodiments.
  • the disclosed method and smart device 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 cluster service application service systems are ensured to provide services for all group members and cluster users to obtain cluster services in time, thereby reducing the impact of network congestion or overload on the cluster services, and improving The user experience.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephonic Communication Services (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本发明实施例公开了一种基于MBMS承载的集群通信中拥塞状态上报方法及系统、存储介质，所述方法包括：集群业务应用服务器接收到基于多媒体广播多播业务MBMS承载的集群业务的网络节点上报的用户面和/或控制面拥塞或过载指示信息时，确定受到影响的目标用户设备UE和集群业务，并执行相应策略，降低拥塞或过载对目标UE接收集群业务的影响；以及，集群业务应用服务器接收到所述网络节点上报的恢复指示信息时，利用恢复的所述网络节点选择发送集群业务的承载方式。本发明实施例的技术方案减少了网络拥塞或过载对集群业务的影响，提升了用户业的务体验。

Description

基于MBMS承载的集群通信中拥塞状态上报方法及系统、存储介质 技术领域
本发明涉及基于多媒体广播多播业务(MBMS，Multimedia Broadcast Multicast Service)承载的集群通信技术，尤其涉及一种基于MBMS承载的集群通信中拥塞状态上报方法及系统、存储介质。
背景技术
集群通信系统是为了满足行业用户指挥调度需求而开发的、面向特定行业应用的专用无线通信系统，系统中大量无线用户共享少量无线信道，以指挥调度为主体应用，是一种多用途、高效能的无线通信系统。集群通信系统在政府部门、公共安全、应急通信、电力、民航、石油化工和军队等领域有着广泛的应用市场。集群系统区别于公众系统的特性在于，集群系统需要具备高效的指挥调度特性，并且要求网络具有高可靠性和安全性。
在3GPP LTE中集群通信称为组通信服务能力GCSE，图1示出了LTE GCSE的系统架构。
为了有效地利用移动网络资源，第三代合作伙伴计划(3GPP，3rd Generation Partnership Project)提出了多媒体广播多播业务(MBMS，Multimedia Broadcast Multicast Service)，该业务是一种从一个数据源向多个目标移动终端传送数据的技术，实现了网络(包括核心网和接入网)资源的共享，提高了网络资源(尤其是空中接口资源)的利用率。3GPP定义的MBMS业务不仅能够实现纯文本低速率的消息类组播和广播，而且还能够实现高速多媒体业务的广播和组播，提供多种丰富的视频、音频和多媒体业务，这无疑顺应了未来移动数据发展的趋势，为3G的发展提供了更好的 业务前景。图2示出了LTE中MBMS的架构示意图。
目前业界正在讨论采用MBMS技术实现集群通信的可能性。针对特定的集群UE，可以通过以下两种方式的任意一种接收所需的集群业务：多播，单播。其中多播方式即通过MBMS承载接收集群业务，此时需要UE具备MBMS接收能力。
在对现有技术的研究和实践过程中发现现有技术存在以下问题：通过MBMS承载发送集群业务时，如果多个集群业务同时开始可能导致网络拥塞或过载，而GCS AS不知道网络拥塞或过载信息，无法进行及时处理，从而导致目标UE无法正常接收所需的集群业务。
发明内容
为解决上述技术问题，本发明实施例提供一种基于MBMS承载的集群通信中拥塞状态上报方法及系统、存储介质，能消除网络拥塞或过载对集群业务的影响。
本发明实施例的技术方案是这样实现的：
一种基于MBMS承载的集群通信中拥塞状态上报方法，包括：
集群业务应用服务器接收到基于多媒体广播多播业务MBMS承载的集群业务的网络节点上报的用户面和/或控制面拥塞或过载指示信息时，确定受到影响的目标用户设备UE和集群业务，并执行相应策略，降低拥塞或过载对目标UE接收集群业务的影响。
作为一种实现方式，所述方法还包括：
所述集群业务应用服务器接收到所述网络节点上报的恢复指示信息时，选择发送集群业务的承载方式；
所述恢复为所述网络节点检测到拥塞或过载结束。
作为一种实现方式，所述MBMS承载包括核心网承载和空口承载；
所述MBMS承载在所述集群业务开始前建立。
作为一种实现方式，所述网络节点包括以下至少之一：
基站eNodeB、多媒体多播广播业务协调功能实体MCE、移动管理单元MME、MBMS网关MBMS GW、广播组播业务中心BM-SC。
作为一种实现方式，所述拥塞包括网络中的控制面信令和/或用户面负载达到预设门限；
所述过载包括网络中的控制面信令和/或用户面负载超过所述网络节点的负荷，所述网络节点无法继续处理额外的信令和/或额外的用户面负载。
作为一种实现方式，所述拥塞/过载指示信息包括以下至少一种：
拥塞/过载标识、MBMS业务区域标识SAI、MBMS业务标识TMGI、拥塞/过载开始/结束标识；
其中，所述拥塞/过载标识用于指示网络拥塞还是过载；所述SAI用于指示拥塞/过载影响的业务区域；所述TMGI用于指示拥塞/过载影响的集群业务。
作为一种实现方式，所述方法还包括：
所述网络节点发生拥塞/过载开始或结束事件时，向所述集群业务应用服务器上报拥塞/过载开始或结束的指示信息；
或者，所述网络节点接收到所述集群业务应用服务器发送的上报拥塞/过载指示的请求消息后，向所述集群业务应用服务器上报拥塞/过载开始或结束的指示信息。
作为一种实现方式，所述策略包括：
发生拥塞时，为目标UE建立单播承载，并通过单播承载发送集群业务；
发生过载时，使集群业务排队，等待过载结束后再发送排队的集群业务，或者，使高优先级的集群业务抢占现有集群业务的资源，保证高优先级的集群业务的发送。
作为一种实现方式，对目标UE接收有影响的集群业务中包括特定的集 群业务；
其中，所述特定的集群业务为根据业务的服务质量等级标识QCI或分配保留优先级ARP确定的发生拥塞/过载的业务；
所述方法还包括：
发生拥塞或过载时，对目标UE接收普通MBMS业务有影响。
作为一种实现方式，所述方法还包括：
确定所述特定集群业务拥塞/过载时，所述网络节点向所述网络节点与所述集群业务应用服务器之间的网元上报所有发生拥塞/过载的业务标识TMGI；所述网元选择发生拥塞/过载的特定集群业务的TMGI向所述集群业务应用服务器发送；
或者，所述网络节点接收到所述集群业务应用服务器上报拥塞/过载的SAI和TMGI的请求消息后，向所述集群业务应用服务器上报SAI中特定集群业务的TMGI；
或者，所述网络节点接收到所述集群业务应用服务器上报拥塞/过载的SAI的请求消息后，向所述集群业务应用服务器上报SAI中所有业务的TMGI。
作为一种实现方式，所述方法还包括：
所述网络节点向所述集群业务应用服务器上报相关信息的触发方式为以下任意一种：事件触发，集群业务应用服务器请求触发，事件及集群业务应用服务器请求触发；
其中，事件触发为，当网络节点发生拥塞/过载开始/结束事件时，网络节点向集群业务应用服务器上报；
集群业务应用服务器请求触发为，集群业务应用服务器向网络节点发送上报的请求消息，接收到请求消息的网络节点向集群业务应用服务器上报；
事件及集群业务应用服务器请求触发为，集群业务应用服务器向网络节点发送上报的请求消息，接收到请求消息的网络节点在发生拥塞/过载开始/结束事件时，向集群业务应用服务器上报。
一种基于MBMS承载的集群通信中拥塞状态上报系统，包括集群业务应用服务器和网络节点，其中：
网络节点，配置为基于多媒体广播多播业务MBMS承载传输集群业务；在用户面和/或控制面拥塞或过载时，向所述集群业务应用服务器发送用户面和/或控制面拥塞或过载指示信息；
集群业务应用服务器，配置为接收所述用户面和/或控制面拥塞或过载指示信息，确定受到影响的目标用户设备UE和集群业务，并执行相应策略，降低拥塞或过载对目标UE接收集群业务的影响。
作为一种实现方式，所述网络节点，还配置为检测到用户面和/或控制面拥塞或过载结束时，向所述集群业务应用服务器发送恢复指示信息；
所述集群业务应用服务器，还配置为在接收到所述恢复指示信息时，选择发送集群业务的承载方式；
所述恢复为所述网络节点检测到拥塞或过载结束。
作为一种实现方式，所述MBMS承载包括核心网承载和空口承载；
所述MBMS承载在所述集群业务开始前建立。
作为一种实现方式，所述网络节点包括以下至少之一：
基站eNodeB、多媒体多播广播业务协调功能实体MCE、移动管理单元MME、MBMS网关MBMS GW、广播组播业务中心BM-SC。
作为一种实现方式，所述拥塞包括网络中的控制面信令和/或用户面负载达到预设门限；
所述过载包括网络中的控制面信令和/或用户面负载超过网络节点的负荷，网络节点无法继续处理额外的信令和/或额外的用户面负载。
作为一种实现方式，所述拥塞/过载指示信息包括以下至少一种：
拥塞/过载标识、MBMS业务区域标识SAI、MBMS业务标识TMGI、拥塞/过载开始/结束标识；
其中，所述拥塞/过载标识用于指示网络拥塞还是过载；所述SAI用于指示拥塞/过载影响的业务区域；所述TMGI用于指示拥塞/过载影响的集群业务。
作为一种实现方式，所述网络节点，还配置为在发生拥塞/过载开始或结束事件时，向所述集群业务应用服务器上报拥塞/过载开始或结束的指示信息；
或者，所述集群业务应用服务器向所述网络节点发送上报拥塞/过载指示的请求消息；所述网络节点，还配置为接收到所述上报拥塞/过载指示的请求消息后，向所述集群业务应用服务器上报拥塞/过载开始或结束的指示信息。
作为一种实现方式，所述策略包括：
发生拥塞时，为目标UE建立单播承载，并通过单播承载发送集群业务；
发生过载时，使集群业务排队，等待过载结束后再发送排队的集群业务，或者，使高优先级的集群业务抢占现有集群业务的资源，保证高优先级的集群业务的发送。
作为一种实现方式，所述系统还包括所述网络节点与所述集群业务应用服务器之间的网元；
所述网络节点，还配置为确定所述特定集群业务拥塞/过载时，向所述网元上报所有发生拥塞/过载的业务标识TMGI；所述网元，配置为选择发生拥塞/过载的特定集群业务的TMGI向所述集群业务应用服务器发送。
作为一种实现方式，所述集群业务应用服务器，还配置为向所述网络节点发送上报拥塞/过载的SAI和TMGI的请求消息；
所述网络节点，还配置为接收到所述请求消息后，向所述集群业务应用服务器上报SAI中特定集群业务的TMGI。
作为一种实现方式，所述集群业务应用服务器，还配置为向所述网络节点发送上报拥塞/过载的SAI的请求消息；
所述网络节点，还配置为接收到所述请求消息后，向所述集群业务应用服务器上报SAI中所有业务的TMGI。
作为一种实现方式，所述网络节点向所述集群业务应用服务器上报相关信息的触发方式为以下任意一种：事件触发，集群业务应用服务器请求触发，事件及集群业务应用服务器请求触发；
其中，事件触发为，当网络节点发生拥塞/过载开始/结束事件时，网络节点向集群业务应用服务器上报；
集群业务应用服务器请求触发为，集群业务应用服务器向网络节点发送上报的请求消息，接收到请求消息的网络节点向集群业务应用服务器上报；
事件及集群业务应用服务器请求触发为，集群业务应用服务器向网络节点发送上报的请求消息，接收到请求消息的网络节点在发生拥塞/过载开始/结束事件时，向集群业务应用服务器上报。
一种存储介质，所述存储介质中存储有计算机程序，所述计算机程序配置为执行前述的基于MBMS承载的集群通信中拥塞状态上报方法。
本发明实施例中，采用MBMS承载发送集群业务(GCS，Group Communication Service)的3GPP网络节点检测到用户面和/或控制面拥塞或者过载时，向集群业务应用服务器(GCS AS，Group Communication Service Application Server)上报拥塞或过载指示信息，接收到拥塞或过载指示信息的AS确定受到影响的目标UE和集群业务，并执行相应策略，以减少网络拥塞或过载对目标UE接收集群业务的影响；当网络节点检测到拥塞或过载 结束时，向集群业务应用服务器(GCS AS)上报恢复指示信息，接收到恢复指示信息的AS选择发送集群业务的承载方式。通过本发明实施例的技术方案，当发生MBMS承载拥塞或过载时，保障了所有集群业务应用服务系统为其所有群组成员提供业务和集群用户及时获取集群业务，减少了网络拥塞或过载对集群业务的影响，提升了用户业的务体验。
附图说明
图1为集群通信系统的架构示意图；
图2为MBMS通信架构示意图；
图3为本发明实施例的基于MBMS承载的集群通信中拥塞状态上报方法的流程图；
图4为本发明实施例一的基于MBMS承载的集群通信中拥塞状态上报方法的流程图；
图5为本发明实施例二的基于MBMS承载的集群通信中拥塞状态上报方法的流程图；
图6为本发明实施例三的基于MBMS承载的集群通信中拥塞状态上报方法的流程图；
图7为本发明实施例四的基于MBMS承载的集群通信中拥塞状态上报方法的流程图；
图8为本发明实施例五的基于MBMS承载的集群通信中拥塞状态上报方法的流程图；
图9为本发明实施例六的基于MBMS承载的集群通信中拥塞状态上报方法的流程图；
图10为本发明实施例的基于MBMS承载的集群通信中拥塞状态上报系统的结构示意图。
具体实施方式
为使本发明的目的、技术方案和优点更加清楚明白，以下举实施例并参照附图，对本发明进一步详细说明。
本发明实施例中，如无特别说明，MBMS是指演进的MBMS即eMBMS，AS是指GCS AS.
如图3所示，本发明实施例的基于MBMS承载的集群通信中拥塞/过载状态上报方法包括如下步骤：
步骤101，GCS AS通过MBMS承载发送集群业务。
在步骤101开始之前，集群UE首先到该集群业务所对应的GCS AS进行注册。这样GCS AS可以知道一共有多少UE加入了某个集群业务。
所述MBMS承载在所述集群业务开始前已预建立，本发明实施例中，所谓预建立是指，某个集群尚未开始，提前建立了MBMS承载。
本发明实施例中，以下描述表示同一概念：MBMS承载、MBSFN承载、多播承载、点到多点PTM承载。
所述MBMS承载包括核心网承载即演进分组核心网(EPC，Evolved Packet Internet Core)承载和空口承载；本发明实施例中，通过无线接入网(RAN，Radio Access Network)网元如基站和/或多媒体多播广播业务协调功能实体(MCE，Multi-cell/multicast Coordination Entity)配置MBMS空口资源，并在空口发送MBMS配置信息和集群数据。
需要指出的是，上述的集群业务也可以是普通MBMS业务，普通MBMS业务和集群业务可通过不同的QCI参数区别，对于普通MBMS业务，相应的MBMS承载不需要预建立。
步骤102，网络节点检测到拥塞和/或过载。
所述网络节点包括：eNodeB，MCE，移动管理单元(MME，Mobility Management Entity)，MBMS网关(MBMS GW，MBMS GateWay)，或广 播组播业务中心(BM-SC，Broadcast Multicast Service Center)。
所述拥塞是指网络中的控制面信令和/或用户面负载达到预设门限，所述过载是指网络中的控制面信令和/或用户面负载超过了网络节点的负荷，网络节点无法继续处理额外的信令和/或额外的用户面负载。
步骤103，网络节点向AS发送该网络节点的拥塞/过载指示信息。
所述拥塞/过载指示信息包括以下至少一种：拥塞/过载标识，MBMS业务区域标识(SAI，Service Area Identifier)，MBMS业务标识(TMGI，Temporary Mobile Group Identity)，拥塞/过载开始/结束标识。
其中，拥塞/过载标识用于指示网络拥塞还是过载；SAI用于指示拥塞/过载影响的业务区域；TMGI用于指示拥塞/过载影响的集群业务。
拥塞/过载开始/结束的内容可以包括以下至少一种：开始(用1或true指示)，结束(用0或false指示)。
拥塞/过载开始/结束，即，拥塞/过载开始等效于当前出现拥塞/过载，拥塞/过载结束等效于当前没有出现拥塞/过载或已开始的拥塞/过载结束。
所述节点拥塞是指网络中的控制面信令和/或用户面数据负载达到一定预设门限，
所述节点过载是指网络中的控制面信令和/或用户面负载超过了网络节点的负荷，网络节点无法继续处理额外的控制面信令和/或额外的用户面数据负载。
上报MBMS业务拥塞/过载信息的内容为：假设拥塞用C指示，过载用O指示，举例：
{SA1：TMGI 1，TMGI2，TMGI3；C，true}
{SA2：TMGI5，TMGI6；O，false}
{SA3：TMGI10；C，false}
上例中SA1中的TMGI1，TMGI2，TMGI3发生拥塞；SA2中的TMGI5， TMGI6过载结束；SA3中的TMGI10拥塞结束。
当过载指示O为1(True)的情况下，可以不再发送拥塞指示C；或者虽然发送了拥塞指示C，UE可以忽略该指示。
所述拥塞/过载业务包括以下任意一种：普通MBMS业务，特定的集群业务。考虑特定的集群业务(如PTT，Push To Talk)可能发生拥塞/过载，根据业务的QoS信息，如QCI或ARP，确定发生拥塞/过载的业务是特定的集群业务，由于eNB不知道业务的QoS信息，在eNB有两种上报拥塞/过载方式，分别为：1)eNB上报所有发生拥塞/过载的业务标识TMGI到MCE，根据特定业务的TMGI(MCE根据QCI/ARP与TMGI的对应关系)，MCE选择发生拥塞/过载的特定业务的TMGI上报到GCS AS；
2)AS请求需要上报状态的SAI和TMGI，通过路径AS->BM-SC->MBMS GW->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.
所述的当网络节点发生拥塞/过载开始/结束事件，是指：从开始状态转换为结束状态；或者从结束状态转换为开始状态。即：如果原先并没有拥塞/过载(等效于上次拥塞/过载已经结束)转换为开始(等效于当前出现了 拥塞/过载)，eNB需要上报；如果原先出现了拥塞/过载(等效于开始)到不拥塞/过载(等效于结束)，eNB需要上报；而且eNB检测到拥塞状态和过载状态彼此发生了变化，eNB也需要上报。
也就是说，C＝拥塞指示，用{0，1}标识；O＝过载指示，用{0，1}标识，只要C和/或O的标识发送了变化，eNB都需要上报。
总之，如果拥塞/过载的开始或者结束的状态不改变，则eNB不需要再上报，这样AS总能准确地掌握MBMS的拥塞/过载状态。
步骤104，AS执行减少拥塞/过载影响的策略。
所述AS首先根据上述拥塞/过载指示信息确定受到影响的目标UE和集群业务TMGI，然后所述AS根据拥塞/过载指示信息和本地策略确定采取的行动，如当发生拥塞时，为目标UE建立单播承载，并通过单播承载发送集群业务，当发生过载时，所述AS将集群业务排队等待过载结束再发送，或者AS利用高优先级的集群业务抢占现有集群业务的资源。
步骤105，网络节点检测到拥塞/过载结束。
所述拥塞/过载结束是指网络恢复正常，如网络信令和或用户面负载低于预设门限。
步骤106，网络节点向AS发送恢复指示信息。
所述网络节点通过现有流程发送指示信息。所述恢复指示信息包括以下至少一种：拥塞/过载标识，MBMS SAI，TMGI，拥塞/过载结束标识.
步骤107，AS选择向UE发送集群业务的方式。
所述AS通过上述恢复指示信息确定受到影响的目标UE，并选择合适的方式向目标UE发送集群业务。如继续通过MBMS承载发送集群业务。
下面通过具体集群业务流程的示例，进一步阐明本发明实施例的技术方案。
实施例一
针对检测到拥塞/过载的网络节点为MCE的场景，如图4所示，本示例的基于MBMS承载的集群通信中拥塞状态上报方法包括以下步骤：
步骤201，AS通过MBMS承载发送集群业务。
所述集群业务的MBMS承载在集群业务开始前已预建立。
步骤202，MCE检测到拥塞/过载。
所述拥塞/过载为控制面信令拥塞/过载。
步骤203，MCE向MME发送拥塞/过载指示信息。
所述MCE通过M3接口向MME发送所述指示信息，所述指示信息可以通过扩展现有M3接口信令，或新建M3接口信令流程实现。
所述指示信息包括以下至少一种：拥塞/过载标识，MBMS SAI，TMGI，拥塞/过载开始/结束标识。
步骤204，MME向MBMS GW发送拥塞/过载指示信息。
所述MME通过Sm接口向MBMS GW发送拥塞/过载指示信息，所述指示信息可以通过扩展现有Sm接口信令，或新建Sm接口信令流程实现。
步骤205，MBMS GW向BM-SC发送拥塞/过载指示信息。
所述MBMS GW通过SGmb接口向BM-SC发送拥塞/过载指示信息，所述指示信息可以通过扩展现有SGmb接口信令，或新建SGmb接口信令流程实现。
步骤206，BM-SC向AS发送拥塞/过载指示信息。
所述BM-SC通过MB2接口向AS发送拥塞/过载指示信息，所述指示信息可以通过扩展现有MB2接口信令，或新建MB2接口信令流程实现。
步骤207，AS采取行动以减少拥塞/过载的影响。
所述AS首先确定受到影响目标UE和集群业务，针对拥塞和过载信息采取不同的行动，如拥塞时，AS采用单播承载发送集群业务；过载时，AS将集群业务排队等待过载结束再发送，或者用高优先级的集群业务抢占现 有集群业务的资源。
步骤208，MCE检测到拥塞/过载结束。
步骤209，MCE向MME发送恢复指示信息。
步骤210，MME向MBMS GW发送恢复指示信息。
步骤211，MBMS GW向BM-SC发送恢复指示信息。
步骤212，BM-SC向AS发送恢复指示信息。
步骤213，AS选择向目标UE发送集群业务的方式。
实施例二
针对检测到拥塞/过载的网络节点为MME的场景，如图5所示，本示例的基于MBMS承载的集群通信中拥塞状态上报方法包括以下步骤：
步骤301，AS通过MBMS承载发送集群业务。
本步骤与步骤101完全相同，这里不再赘述。
步骤302，MME检测到拥塞/过载。
所述拥塞/过载是指控制面信令拥塞/过载。
步骤303，MME向MBMS GW发送拥塞/过载指示信息。
所述MME通过Sm接口向MBMS GW发送拥塞/过载指示信息。
步骤304，MBMS GW向BM-SC发送拥塞/过载指示信息。
所述MBMS GW通过SGmb接口向BM-SC发送拥塞/过载指示信息。
步骤305，BM-SC向AS发送拥塞/过载指示信息。
步骤306，AS采取行动以减少拥塞/过载的影响。
步骤307，MME检测到拥塞/过载结束。
步骤308，MME向MBMS GW发送恢复指示信息。
所述MME通过Sm接口向MBMS GW发送恢复指示信息。
步骤309，MBMS GW向BM-SC发送恢复指示信息。
所述MBMS GW通过SGmb接口向BM-SC发送恢复指示信息。
步骤310，BM-SC向AS发送恢复指示信息。
步骤311，AS选择向UE发送集群业务的方式。
实施例三
针对检测到拥塞/过载的网络节点为eNodeB的场景，如图6所示，本示例的基于MBMS承载的集群通信中拥塞状态上报方法包括以下步骤：
步骤401，AS通过MBMS承载发送集群业务。
步骤402，eNB检测到拥塞/过载。
所述eNB检测到用户面或控制面的拥塞/过载。
步骤403，eNB向MCE发送拥塞/过载指示信息。
所述eNB通过M2接口向MCE发送拥塞/过载指示信息。
所述拥塞/过载指示信息包括以下至少一种：拥塞/过载标识，MBMS业务区域标识(SAI)，MBMS业务标识(TMGI)。
其中，拥塞/过载标识用于指示网络拥塞或过载，其中网络拥塞标识可包括多个等级，如高、中、低等；SAI用于指示拥塞/过载影响的业务区域；TMGI用于指示拥塞/过载影响的集群业务。
拥塞/过载标识的内容可以包括以下至少一种：节点拥塞指示信息、节点过载指示信息。
所述节点拥塞是指网络中的控制面信令和/或用户面负载达到一定预设门限；
所述节点过载是指网络节点无法继续处理额外的控制面板信令和/或额外的用户面负载。
eNB检测到物理多播信道(PMCH，Physical Multicast Channel)拥塞或者过载。
步骤404，MCE向MME发送拥塞/过载指示信息。
步骤405，MME向MBMS GW发送拥塞/过载指示信息。
步骤406，MBMS GW向BM-SC发送拥塞/过载指示信息。
步骤407，BM-SC向AS发送拥塞/过载指示信息。
步骤408，AS采取行动减少拥塞/过载的影响。
步骤409，eNB检测到拥塞过载结束。
步骤410，eNB向MCE发送恢复指示信息。
步骤411，MCE向MME发送恢复指示信息。
步骤412，MME向MBMS GW发送恢复指示信息。
步骤413，MBMS GW向BM-SC发送恢复指示信息。
步骤414，BM-SC向AS发送恢复指示信息。
步骤415，AS选择向UE发送集群业务的方式。
实施例四
针对检测到拥塞/过载的网络节点为MBMS-GW的场景，如图7所示，本示例的基于MBMS承载的集群通信中拥塞状态上报方法包括以下步骤：
步骤501，AS通过MBMS承载发送集群业务。
本步骤与步骤101完全相同，这里不再赘述。
步骤502，MBMS-GW检测到拥塞/过载。
所述拥塞/过载为控制面和/或用户面拥塞/过载。
步骤503，MBMS GW向BM-SC发送拥塞/过载指示信息。
步骤504，BM-SC向AS发送拥塞/过载指示信息。
步骤505，AS采取行动以减少拥塞/过载的影响。
步骤506，MBMS-GW检测到拥塞/过载结束。
步骤507，MBMS GW向BM-SC发送恢复指示信息。
步骤508，BM-SC向AS发送恢复指示信息。
步骤509，AS选择向UE发送集群业务的方式。
实施例五
针对检测到拥塞/过载的网络节点为BM-SC的场景，如图8所示，本示例的基于MBMS承载的集群通信中拥塞状态上报方法包括以下步骤：
步骤601，AS通过MBMS承载发送集群业务。
本步骤与步骤101完全相同，这里不再赘述。
步骤602，BM-SC检测到拥塞/过载。
所述拥塞/过载为控制面和/或用户面拥塞/过载。
步骤603，BM-SC向AS发送拥塞/过载指示信息。
步骤604，AS采取行动以减少拥塞/过载的影响。
步骤605，BM-SC检测到拥塞/过载结束。
步骤606，BM-SC向AS发送恢复指示信息。
步骤607，AS选择向UE发送集群业务的方式。
实施例六
针对AS请求eNB上报拥塞/过载信息的场景，如图9所示，本示例的基于MBMS承载的集群通信中拥塞状态上报方法包括以下步骤：
步骤701，AS通过MBMS承载发送集群业务。
本步骤与步骤101完全相同，这里不再赘述。
步骤702，AS请求eNB上报拥塞/过载信息。
所述AS通过路径AS至BM-SC至MBMS GW至MME至MCE至eNB的顺序向eNB请求上报拥塞/过载信息；
所述AS请求消息中包括以下内容的一个或多个：一个或多个SAI；每个SAI中的一个或多个TMGI；拥塞指示；过载指示。
当请求消息中包括：一个或多个SAI，却没有包括每个SAI所对应的TMGI时候，eNB需要上报该SAI所承载的全部TMGI的拥塞/过载指示；
当请求消息中包括：一个或多个SAI，也包括所述SAI所对应的1个或多个TMGI时，eNB需要上报该所指示的TMGI的拥塞/过载指示；
当请求消息中包括：拥塞指示，过载指示，或拥塞/过载指示，eNB需要上报出现拥塞(开始)，或出现过载(开始)的所有TMGI.
所述拥塞/过载是指控制面信令和/或用户面数据拥塞/过载。
步骤703，eNB是否拥塞/过载，如果是，执行步骤704，否则，执行步骤710。
所述eNB通过PMCH状态判断是否发生用户面数据拥塞/过载，或者通过空口信令判断是否发生控制面信令拥塞/过载。
步骤704，eNB向MCE发送拥塞/过载指示信息。
所述eNB发生拥塞/过载，通过M2接口向MCE发送拥塞/过载指示信息。
步骤705，MCE向MME发送拥塞/过载指示信息。
步骤706，MME向MBMS GW发送拥塞/过载指示信息。
步骤707，MBMS GW向BM-SC发送拥塞/过载指示信息。
步骤708，BM-SC向AS发送拥塞/过载指示信息。
步骤709，AS采取行动以减少拥塞/过载的影响。
步骤710，eNB检测节点状态，转向步骤703。
所述eNB没有发生拥塞/过载，不发送指示信息到AS，eNB继续检测节点状态，转到步骤703判断是否拥塞/过载。
所述eNB发生拥塞/过载事件，是指：从开始状态转换为结束状态；或者从结束状态转换为开始状态。即，如果原先并没有拥塞/过载(等效于上次拥塞/过载已经结束)转换为开始(等效于当前出现了拥塞/过载)，eNB需要上报；如果原先出现了拥塞/过载(等效于开始)到不拥塞/过载(等效于结束)，eNB需要上报；而且eNB检测到拥塞状态和过载状态彼此发生了变化，eNB也需要上报。
简单地说，C＝拥塞指示，用{0，1}标识；O＝过载指示，用{0，1}标识， 只要C和/或O的标识发送了变化，eNB都需要上报。
本发明实施例还记载了一种基于MBMS承载的集群通信中拥塞状态上报系统，所述系统包括集群业务应用服务器和网络节点，其中：
网络节点，配置为基于多媒体广播多播业务MBMS承载传输集群业务；在用户面和/或控制面拥塞或过载时，向所述集群业务应用服务器发送用户面和/或控制面拥塞或过载指示信息；
集群业务应用服务器，配置为接收所述用户面和/或控制面拥塞或过载指示信息，确定受到影响的目标用户设备UE和集群业务，并执行相应策略，降低拥塞或过载对目标UE接收集群业务的影响。
其中，所述网络节点，还配置为检测到用户面和/或控制面拥塞或过载结束时，向所述集群业务应用服务器发送恢复指示信息；
所述集群业务应用服务器，还配置为在接收到所述恢复指示信息时，利用恢复的所述网络节点选择发送集群业务的承载方式；
所述恢复为所述网络节点检测到拥塞或过载结束。
其中，所述MBMS承载包括核心网承载和空口承载；
所述MBMS承载在所述集群业务开始前建立。
其中，所述网络节点包括以下至少之一：
基站、多媒体多播广播业务协调功能实体MCE、移动管理单元MME、MBMS网关MBMS GW、广播组播业务中心BM-SC。
其中，所述拥塞包括网络中的控制面信令和/或用户面负载达到一定预设门限；
所述过载包括网络中的控制面信令和/或用户面负载超过网络节点的负荷，网络节点无法继续处理额外的信令和/或额外的用户面负载。
其中，所述拥塞/过载指示信息包括以下至少一种：
拥塞/过载标识、MBMS业务区域标识SAI、MBMS业务标识TMGI、 拥塞/过载开始标识；
其中，所述拥塞/过载标识用于指示网络拥塞还是过载；所述SAI用于指示拥塞/过载影响的业务区域；所述TMGI用于指示拥塞/过载影响的集群业务。
其中，述网络节点，还配置为在发生拥塞/过载开始或结束事件时，向所述集群业务应用服务器上报拥塞/过载开始或结束的指示信息；
或者，所述集群业务应用服务器向所述网络节点发送上报拥塞/过载指示的请求消息；所述网络节点，还配置为接收到所述上报拥塞/过载指示的请求消息后，向所述集群业务应用服务器上报拥塞/过载开始或结束的指示信息。
其中，所述策略包括：
发生拥塞时，为目标UE建立单播承载，并通过单播承载发送集群业务；
发生过载时，使集群业务排队，等待过载结束后再发送排队的集群业务，或者，使高优先级的集群业务抢占现有集群业务的资源，保证高优先级的集群业务的发送。
本发明实施例中，对目标UE接收有影响的集群业务中包括特定的集群业务；
其中，所述特定的集群业务为根据业务的服务质量等级标识QCI或分配保留优先级ARP确定的发生拥塞/过载的业务；
当发生拥塞或过载时，对目标UE接收普通MBMS业务有影响。
所述系统还包括所述网络节点与所述集群业务应用服务器之间的网元；
所述网络节点，还配置为确定所述特定集群业务拥塞/过载时，向所述网元上报所有发生拥塞/过载的业务标识TMGI；所述网元，配置为选择发生拥塞/过载的特定集群业务的TMGI向所述集群业务应用服务器发送。
所述集群业务应用服务器，还配置为向所述网络节点发送上报拥塞/过载的SAI和TMGI的请求消息；
所述网络节点，还配置为接收到所述请求消息后，向所述集群业务应用服务器上报SAI中特定集群业务的TMGI。
所述集群业务应用服务器，还配置为向所述网络节点发送上报拥塞/过载的SAI的请求消息；
所述网络节点，还配置为接收到所述请求消息后，向所述集群业务应用服务器上报SAI中所有业务的TMGI。
所述网络节点向所述集群业务应用服务器上报相关信息的触发方式为以下任意一种：事件触发，集群业务应用服务器请求触发，事件及集群业务应用服务器请求触发；
其中，事件触发为，当网络节点发生拥塞/过载开始/结束事件时，网络节点向集群业务应用服务器上报；
集群业务应用服务器请求触发为，集群业务应用服务器向网络节点发送上报的请求消息，接收到请求消息的网络节点向集群业务应用服务器上报；
事件及集群业务应用服务器请求触发为，集群业务应用服务器向网络节点发送上报的请求消息，接收到请求消息的网络节点在发生拥塞/过载开始/结束事件时，向集群业务应用服务器上报。
本领域技术人员应当理解，上述基于MBMS承载的集群通信中拥塞状态上报系统是为实现前述的基于MBMS承载的集群通信中拥塞状态上报方法而设置的，相关网元的功能及结构可参照前述方法实施例的描述而理解。
作为一种具体实现方式，如图10所示，本发明实施例的基于MBMS承载的集群通信中拥塞状态上报系统包括：
组通信业务应用服务器GCS AS 81，配置为接收拥塞/过载及恢复指示 信息，根据指示信息进行处理，并选择发送集群业务的方式。以及，向无线接入网相关网元发送上报拥塞/过载的相关指示信息。
核心网络82，配置为检测拥塞/过载状态，向AS81发送指示信息，还配置为接收无线接入网相关网元发送的拥塞/过载的相关指示信息。核心网络82包括以下BM-SC，MBMS GW，MME等网络节点。
MCE83，配置为检测拥塞/过载状态，接收eNB84发送的拥塞/过载指示信息，通过核心网络82向AS81发送拥塞/过载指示信息。
eNB84，配置为检测拥塞/过载状态，接收MCE83的指示信息，通过MCE83和核心网络82向AS81发送拥塞/过载指示信息。
本发明实施例还记载了一种存储介质，所述存储介质中存储有计算机程序，所述计算机程序配置为执行前述各实施例的基于MBMS承载的集群通信中拥塞状态上报方法。
本发明实施例所记载的技术方案之间，在不冲突的情况下，可以任意组合。
在本发明所提供的几个实施例中，应该理解到，所揭露的方法和智能设备，可以通过其它的方式实现。以上所描述的设备实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，如：多个单元或组件可以结合，或可以集成到另一个系统，或一些特征可以忽略，或不执行。另外，所显示或讨论的各组成部分相互之间的耦合、或直接耦合、或通信连接可以是通过一些接口，设备或单元的间接耦合或通信连接，可以是电性的、机械的或其它形式的。
上述作为分离部件说明的单元可以是、或也可以不是物理上分开的，作为单元显示的部件可以是、或也可以不是物理单元，即可以位于一个地方，也可以分布到多个网络单元上；可以根据实际的需要选择其中的部分或全部单元来实现本实施例方案的目的。
另外，在本发明各实施例中的各功能单元可以全部集成在一个处理单元中，也可以是各单元分别单独作为一个单元，也可以两个或两个以上单元集成在一个单元中；上述集成的单元既可以采用硬件的形式实现，也可以采用硬件加软件功能单元的形式实现。
以上所述，仅为本发明的具体实施方式，但本发明的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本发明揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本发明的保护范围之内。
工业实用性
通过本发明，当发生MBMS承载拥塞或过载时，保障了所有集群业务应用服务系统为其所有群组成员提供业务和集群用户及时获取集群业务，减少了网络拥塞或过载对集群业务的影响，提升了用户业的务体验。

Claims (24)

  1. 一种基于MBMS承载的集群通信中拥塞状态上报方法，所述方法包括：
    集群业务应用服务器接收到基于多媒体广播多播业务MBMS承载的集群业务的网络节点上报的用户面和/或控制面拥塞或过载指示信息时，确定受到影响的目标用户设备UE和集群业务，并执行相应策略，降低拥塞或过载对目标UE接收集群业务的影响。
  2. 根据权利要求1所述的方法，其中，所述方法还包括：
    所述集群业务应用服务器接收到所述网络节点上报的恢复指示信息时，选择发送集群业务的承载方式；
    所述恢复为所述网络节点检测到拥塞或过载结束。
  3. 根据权利要求1或2所述的方法，其中，所述MBMS承载包括核心网承载和空口承载；
    所述MBMS承载在所述集群业务开始前建立。
  4. 根据权利要求1或2所述的方法，其中，所述网络节点包括以下至少之一：
    基站eNodeB、多媒体多播广播业务协调功能实体MCE、移动管理单元MME、MBMS网关MBMS GW、广播组播业务中心BM-SC。
  5. 根据权利要求1或2所述的方法，其中，所述拥塞包括网络中的控制面信令和/或用户面负载达到预设门限；
    所述过载包括网络中的控制面信令和/或用户面负载超过所述网络节点的负荷，所述网络节点无法继续处理额外的信令和/或额外的用户面负载。
  6. 根据权利要求1或2所述的方法，其中，所述拥塞/过载指示信息包括以下至少一种：
    拥塞/过载标识、MBMS业务区域标识SAI、MBMS业务标识TMGI、 拥塞/过载开始/结束标识；
    其中，所述拥塞/过载标识用于指示网络拥塞还是过载；所述SAI用于指示拥塞/过载影响的业务区域；所述TMGI用于指示拥塞/过载影响的集群业务。
  7. 根据权利要求6所述的方法，其中，所述方法还包括：
    所述网络节点发生拥塞/过载开始或结束事件时，向所述集群业务应用服务器上报拥塞/过载开始或结束的指示信息；
    或者，所述网络节点接收到所述集群业务应用服务器发送的上报拥塞/过载指示的请求消息后，向所述集群业务应用服务器上报拥塞/过载开始或结束的指示信息。
  8. 根据权利要求1或2所述的方法，其中，所述策略包括：
    发生拥塞时，为目标UE建立单播承载，并通过单播承载发送集群业务；
    发生过载时，使集群业务排队，等待过载结束后再发送排队的集群业务，或者，使高优先级的集群业务抢占现有集群业务的资源，保证高优先级的集群业务的发送。
  9. 根据权利要求1所述的方法，其中，对目标UE接收有影响的集群业务中包括特定的集群业务；
    其中，所述特定的集群业务为根据业务的服务质量等级标识QCI或分配保留优先级ARP确定的发生拥塞/过载的业务；
    所述方法还包括：
    发生拥塞或过载时，对目标UE接收普通MBMS业务有影响。
  10. 根据权利要求9所述的方法，其中，所述方法还包括：
    确定所述特定集群业务拥塞/过载时，所述网络节点向所述网络节点与所述集群业务应用服务器之间的网元上报所有发生拥塞/过载的业务标识TMGI；所述网元选择发生拥塞/过载的特定集群业务的TMGI向所述集群业 务应用服务器发送；
    或者，所述网络节点接收到所述集群业务应用服务器上报拥塞/过载的SAI和TMGI的请求消息后，向所述集群业务应用服务器上报SAI中特定集群业务的TMGI；
    或者，所述网络节点接收到所述集群业务应用服务器上报拥塞/过载的SAI的请求消息后，向所述集群业务应用服务器上报SAI中所有业务的TMGI。
  11. 根据权利要求1至10任一项所述的方法，其中，所述方法还包括：
    所述网络节点向所述集群业务应用服务器上报相关信息的触发方式为以下任意一种：事件触发，集群业务应用服务器请求触发，事件及集群业务应用服务器请求触发；
    其中，事件触发为，当网络节点发生拥塞/过载开始/结束事件时，网络节点向集群业务应用服务器上报；
    集群业务应用服务器请求触发为，集群业务应用服务器向网络节点发送上报的请求消息，接收到请求消息的网络节点向集群业务应用服务器上报；
    事件及集群业务应用服务器请求触发为，集群业务应用服务器向网络节点发送上报的请求消息，接收到请求消息的网络节点在发生拥塞/过载开始/结束事件时，向集群业务应用服务器上报。
  12. 一种基于MBMS承载的集群通信中拥塞状态上报系统，所述系统包括集群业务应用服务器和网络节点，其中：
    网络节点，配置为基于多媒体广播多播业务MBMS承载传输集群业务；在用户面和/或控制面拥塞或过载时，向所述集群业务应用服务器发送用户面和/或控制面拥塞或过载指示信息；
    集群业务应用服务器，配置为接收所述用户面和/或控制面拥塞或过载 指示信息，确定受到影响的目标用户设备UE和集群业务，并执行相应策略，降低拥塞或过载对目标UE接收集群业务的影响。
  13. 根据权利要求12所述的系统，其中，所述网络节点，还配置为检测到用户面和/或控制面拥塞或过载结束时，向所述集群业务应用服务器发送恢复指示信息；
    所述集群业务应用服务器，还配置为在接收到所述恢复指示信息时，选择发送集群业务的承载方式；
    所述恢复为所述网络节点检测到拥塞或过载结束。
  14. 根据权利要求12或13所述的系统，其中，所述MBMS承载包括核心网承载和空口承载；
    所述MBMS承载在所述集群业务开始前建立。
  15. 根据权利要求12或13所述的系统，其中，所述网络节点包括以下至少之一：
    基站eNodeB、多媒体多播广播业务协调功能实体MCE、移动管理单元MME、MBMS网关MBMS GW、广播组播业务中心BM-SC。
  16. 根据权利要求12或13所述的系统，其中，所述拥塞包括网络中的控制面信令和/或用户面负载达到预设门限；
    所述过载包括网络中的控制面信令和/或用户面负载超过网络节点的负荷，网络节点无法继续处理额外的信令和/或额外的用户面负载。
  17. 根据权利要求12或13所述的系统，其中，所述拥塞/过载指示信息包括以下至少一种：
    拥塞/过载标识、MBMS业务区域标识SAI、MBMS业务标识TMGI、拥塞/过载开始/结束标识；
    其中，所述拥塞/过载标识用于指示网络拥塞还是过载；所述SAI用于指示拥塞/过载影响的业务区域；所述TMGI用于指示拥塞/过载影响的集群 业务。
  18. 根据权利要求17所述的系统，其中，所述网络节点，还配置为在发生拥塞/过载开始或结束事件时，向所述集群业务应用服务器上报拥塞/过载开始或结束的指示信息；
    或者，所述集群业务应用服务器向所述网络节点发送上报拥塞/过载指示的请求消息；所述网络节点，还配置为接收到所述上报拥塞/过载指示的请求消息后，向所述集群业务应用服务器上报拥塞/过载开始或结束的指示信息。
  19. 根据权利要求12或13所述的系统，其中，所述策略包括：
    发生拥塞时，为目标UE建立单播承载，并通过单播承载发送集群业务；
    发生过载时，使集群业务排队，等待过载结束后再发送排队的集群业务，或者，使高优先级的集群业务抢占现有集群业务的资源，保证高优先级的集群业务的发送。
  20. 根据权利要求12所述的系统，其中，所述系统还包括所述网络节点与所述集群业务应用服务器之间的网元；
    所述网络节点，还配置为确定所述特定集群业务拥塞/过载时，向所述网元上报所有发生拥塞/过载的业务标识TMGI；所述网元，配置为选择发生拥塞/过载的特定集群业务的TMGI向所述集群业务应用服务器发送。
  21. 根据权利要求12所述的系统，其中，所述集群业务应用服务器，还配置为向所述网络节点发送上报拥塞/过载的SAI和TMGI的请求消息；
    所述网络节点，还配置为接收到所述请求消息后，向所述集群业务应用服务器上报SAI中特定集群业务的TMGI。
  22. 根据权利要求12所述的系统，其中，所述集群业务应用服务器，还配置为向所述网络节点发送上报拥塞/过载的SAI的请求消息；
    所述网络节点，还配置为接收到所述请求消息后，向所述集群业务应 用服务器上报SAI中所有业务的TMGI。
  23. 根据权利要求12至22任一项所述的系统，其中，所述网络节点向所述集群业务应用服务器上报相关信息的触发方式为以下任意一种：事件触发，集群业务应用服务器请求触发，事件及集群业务应用服务器请求触发；
    其中，事件触发为，当网络节点发生拥塞/过载开始/结束事件时，网络节点向集群业务应用服务器上报；
    集群业务应用服务器请求触发为，集群业务应用服务器向网络节点发送上报的请求消息，接收到请求消息的网络节点向集群业务应用服务器上报；
    事件及集群业务应用服务器请求触发为，集群业务应用服务器向网络节点发送上报的请求消息，接收到请求消息的网络节点在发生拥塞/过载开始/结束事件时，向集群业务应用服务器上报。
  24. 一种存储介质，所述存储介质中存储有计算机程序，所述计算机程序配置为执行权利要求1至11任一项所述的基于MBMS承载的集群通信中拥塞状态上报方法。
PCT/CN2015/072811 2014-07-31 2015-02-11 基于mbms承载的集群通信中拥塞状态上报方法及系统、存储介质 WO2016015465A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP15827932.3A EP3188517B1 (en) 2014-07-31 2015-02-11 Mbms bearer-based method and system for reporting congestion state in cluster communication and storage medium
US15/514,027 US10104577B2 (en) 2014-07-31 2015-02-11 MBMS bearer-based method and system for reporting congestion state in cluster communication and storage medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410373211.X 2014-07-31
CN201410373211.XA CN105323722B (zh) 2014-07-31 2014-07-31 基于mbms承载的集群通信中拥塞状态上报方法及系统

Publications (1)

Publication Number Publication Date
WO2016015465A1 true WO2016015465A1 (zh) 2016-02-04

Family

ID=55216724

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/072811 WO2016015465A1 (zh) 2014-07-31 2015-02-11 基于mbms承载的集群通信中拥塞状态上报方法及系统、存储介质

Country Status (4)

Country Link
US (1) US10104577B2 (zh)
EP (1) EP3188517B1 (zh)
CN (1) CN105323722B (zh)
WO (1) WO2016015465A1 (zh)

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105323723A (zh) * 2014-07-31 2016-02-10 中兴通讯股份有限公司 基于mbms承载的集群通信中查询节点状态的方法及系统
CN109716798B (zh) 2016-10-01 2021-01-08 华为技术有限公司 一种广播承载管理的方法及其设备
US20220322291A1 (en) * 2019-09-09 2022-10-06 Samsung Electronics Co., Ltd. Method for channel establishment, base station and multi-cell multicast coordination entity mce
CN112787973B (zh) * 2019-11-04 2022-11-18 成都鼎桥通信技术有限公司 宽带集群终端漫游场景下的集群业务流安装方法和装置
CN113923800A (zh) * 2020-07-08 2022-01-11 华为技术有限公司 一种通信方法及装置
WO2022017527A1 (zh) * 2020-07-23 2022-01-27 华为技术有限公司 一种数据传输方法、装置以及系统
CN118555217B (zh) * 2024-07-30 2024-10-18 山东云海国创云计算装备产业创新中心有限公司 数据传输方法、装置、网关节点、存储介质及系统

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1859645A (zh) * 2006-01-18 2006-11-08 华为技术有限公司 一种分配信道的方法
US20100027541A1 (en) * 2006-10-12 2010-02-04 Kent Eriksson Efficient mbms backbone distributionusing one tunnel approach
CN103428856A (zh) * 2012-05-21 2013-12-04 中兴通讯股份有限公司 实现多媒体广播多播业务连续性的方法及系统
CN104270725A (zh) * 2014-09-24 2015-01-07 中兴通讯股份有限公司 指示信息的确定、处理以及请求消息的处理方法及装置
CN104301931A (zh) * 2014-09-24 2015-01-21 中兴通讯股份有限公司 拥塞/过载的控制方法,系统,装置和基站

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2004221759A (ja) * 2003-01-10 2004-08-05 Nec Corp 移動通信システム及びそれに用いる無線端末並びに無線制御装置及びその動作制御方法
KR100559979B1 (ko) * 2003-04-03 2006-03-13 엘지전자 주식회사 이동통신 시스템에서의 메시지 전송방법
CN102378113B (zh) * 2010-08-12 2016-03-02 中兴通讯股份有限公司 一种多媒体广播多播业务传输方式的转换方法和系统
US9491735B2 (en) * 2010-12-19 2016-11-08 Motorola Solutions, Inc. System and method in a communication network of dynamically assigning a multimedia broadcast/multicast service bearer to a multicast channel
WO2013066103A1 (ko) * 2011-11-04 2013-05-10 주식회사 팬택 Ｍｂｍｓ 서비스의 연속성을 위한 혼잡 제어장치 및 방법
CN103220717B (zh) * 2012-01-20 2017-02-08 华为技术有限公司 一种负载均衡方法以及相关装置
US9723523B2 (en) * 2012-08-03 2017-08-01 Blackberry Limited Maintaining MBMS continuity

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1859645A (zh) * 2006-01-18 2006-11-08 华为技术有限公司 一种分配信道的方法
US20100027541A1 (en) * 2006-10-12 2010-02-04 Kent Eriksson Efficient mbms backbone distributionusing one tunnel approach
CN103428856A (zh) * 2012-05-21 2013-12-04 中兴通讯股份有限公司 实现多媒体广播多播业务连续性的方法及系统
CN104270725A (zh) * 2014-09-24 2015-01-07 中兴通讯股份有限公司 指示信息的确定、处理以及请求消息的处理方法及装置
CN104301931A (zh) * 2014-09-24 2015-01-21 中兴通讯股份有限公司 拥塞/过载的控制方法,系统,装置和基站

Also Published As

Publication number Publication date
US20170251398A1 (en) 2017-08-31
US10104577B2 (en) 2018-10-16
EP3188517B1 (en) 2019-01-30
EP3188517A4 (en) 2017-11-01
EP3188517A1 (en) 2017-07-05
CN105323722B (zh) 2020-05-26
CN105323722A (zh) 2016-02-10

Similar Documents

Publication Publication Date Title
WO2016015465A1 (zh) 基于mbms承载的集群通信中拥塞状态上报方法及系统、存储介质
EP3198958B1 (en) Managing communication resources
EP3200484B1 (en) Method and system for treatment of network overload or congestion
CN109151906B (zh) 通信方法、网络设备、终端设备和系统
US9055469B2 (en) Method and device for indicating MBMS service suspension, and user equipment
US10334480B2 (en) Method, system, device for controlling congestion or overload and evolved node B (eNB)
EP2638714B1 (en) Mobile communication device, base station and methods therefor for mbms counting for idle mode devices
CN104754522B (zh) 一种保持组通信业务连续性的方法、装置和系统
EP3217691B1 (en) Method and apparatus for processing instruction information
WO2016015472A1 (zh) 基于mbms承载的集群通信中查询节点状态的方法及系统、存储介质
CN103733657B (zh) 识别ue对embms的计数结果
JP2014509164A (ja) Ｍｂｍｓサービス送信方式の切替方法、装置及びユーザー装置
WO2016107204A1 (zh) 一种群组通信方法和服务器

Legal Events

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

Ref document number: 15827932

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

REEP Request for entry into the european phase

Ref document number: 2015827932

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 15514027

Country of ref document: US