WO2015143795A1 - Mbms差错处理方法、通信节点、通信系统和存储介质 - Google Patents

Mbms差错处理方法、通信节点、通信系统和存储介质 Download PDF

Info

Publication number
WO2015143795A1
WO2015143795A1 PCT/CN2014/081946 CN2014081946W WO2015143795A1 WO 2015143795 A1 WO2015143795 A1 WO 2015143795A1 CN 2014081946 W CN2014081946 W CN 2014081946W WO 2015143795 A1 WO2015143795 A1 WO 2015143795A1
Authority
WO
WIPO (PCT)
Prior art keywords
error
mbms
indication
indication information
data
Prior art date
Application number
PCT/CN2014/081946
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 EP14887181.7A priority Critical patent/EP3125466B1/en
Priority to US15/127,589 priority patent/US10129042B2/en
Publication of WO2015143795A1 publication Critical patent/WO2015143795A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/04—Arrangements for maintaining operational condition
    • 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
    • G—PHYSICS
    • G01—MEASURING; TESTING
    • G01R—MEASURING ELECTRIC VARIABLES; MEASURING MAGNETIC VARIABLES
    • G01R31/00—Arrangements for testing electric properties; Arrangements for locating electric faults; Arrangements for electrical testing characterised by what is being tested not provided for elsewhere
    • G01R31/08—Locating faults in cables, transmission lines, or networks
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0706—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment
    • G06F11/0736—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment in functional embedded systems, i.e. in a data processing system designed as a combination of hardware and software dedicated to performing a certain function
    • G06F11/0742—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment in functional embedded systems, i.e. in a data processing system designed as a combination of hardware and software dedicated to performing a certain function in a data processing system embedded in a mobile device, e.g. mobile phones, handheld devices
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
    • G06F11/3013—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system is an embedded system, i.e. a combination of hardware and software dedicated to perform a certain function in mobile devices, printers, automotive or aircraft systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04H—BROADCAST COMMUNICATION
    • H04H20/00—Arrangements for broadcast or for distribution combined with broadcast
    • H04H20/65—Arrangements characterised by transmission systems for broadcast
    • H04H20/71—Wireless systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0006—Systems modifying transmission characteristics according to link quality, e.g. power backoff by adapting the transmission format
    • 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/1895—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast for short real-time information, e.g. alarms, notifications, alerts, updates
    • 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/04—Error 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
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H04W76/32—Release of transport tunnels
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/64—Hybrid switching systems
    • H04L12/6418—Hybrid transport
    • H04L2012/6467—Information loss recovery, e.g. error correction, prediction

Definitions

  • the present invention relates to error handling techniques in the field of communications, and more particularly to an MBMS error handling method, a communication node, a communication system, and a storage medium.
  • the 3rd Generation Partnership Project (3GPP) proposes a Multimedia Broadcast Multimedia Service (MBMS) service, which is a kind of data from one data.
  • MBMS Multimedia Broadcast Multimedia Service
  • the technology of transmitting data to multiple targets realizes the sharing of resources of the network (including the core network and the access network) and improves the utilization of network resources (especially air interface resources).
  • the 3GPP-defined MBMS not only enables plain text low-rate message-like multicast and broadcast, but also enables high-speed multimedia services to broadcast and multicast, providing a variety of rich video, audio and multimedia services, which undoubtedly conforms to future mobile
  • the trend of data development provides a better business prospect for the development of 3G.
  • the MBMS service can use the multicast mode mode.
  • the MBSFN (Multicast/Broadcast over Single Frequency Network) transmission mode which uses the MBMS service generated in the multicast mode, also known as the MBSFN service, can use the same modulation and coding format in multiple cells. The same content occurs with the same physical resource.
  • MTCH Multicast Traffic CHannel
  • MCCH Multicast Control CHannel
  • MBSFN sync area MBSNF area
  • MBSFN transmission advertisement, reserved area
  • the UE (User equipment) of the multiple cells can receive multiple MBMS data with the same content and perform SFN combining, so that the gain of the received signal can be improved. ⁇ Using the same physical resources and sending MBSFN transmission mode, multiple cells transmitting the same MBMS service form an MBSFN area.
  • MBSFN MBSFN services on one MBSFN area.
  • All MBSFN services belonging to the same MBSFN area are called one MBSFN service group, that is, one MBSFN service group belongs to only one MBSFN area.
  • An MBSFN area includes multiple cells, and each cell is configured with an identical MBSFN service group.
  • the data channel MTCH of the plurality of MBSFN services having the same MBSFN area, and the control channel MCCH of the MBSFN service can be multiplexed into one MCH (Multicast Channel).
  • MCH and multiple MTCHs of the same MBSFN area that is, multiple logical channels can be mapped to the same transport channel MCH; MCH passes through the transport block of the MBSFN subframe Loaded.
  • an MSAP occasion is introduced in the MSAP concept, which indicates that all MMSs corresponding to an MCH in a time period of a dynamic scheduling period include all multicast resources.
  • Multiple MTCH and dynamic scheduling information can be sent in an MSAP occasion, and the MCCH can also be included.
  • the dynamic scheduling information is carried in a MAC PDU (Control Data Element), and the length of the MSAP occasion can be 320 ms.
  • the length of an MSAP occasion is a scheduling period, also known as a dynamic scheduling period.
  • One MCH allocates one or more MBSFN subframes in one or more MBSFN frames through the MSAP, where the subframes transmitted in the multicast mode are referred to as MBSFN subframes, and the frames containing the MBSFN subframes are referred to as MBSFN frames.
  • the dynamic scheduling information is carried on each MSAP occasion configured by the MCH, and carries the mapping information of the MTCH to the auxiliary MSAP subframe.
  • the mapping information is determined by using the MBSFN subframe number index relationship in a scheduling period, and the UE Reading the scheduling information may know which MBSFN subframes each MTCH is allocated, and the UE may read the MTCH of interest on the corresponding MBSFN subframe, and ignore the MBSFN subframes that it does not need to read, thereby improving the UE.
  • the MBMS service receives efficiency and saves the UE's power consumption.
  • the MB SFN subframe number described here is determined as follows: All MBSFN subframes allocated by one MCH in one scheduling period are sequentially arranged and numbered sequentially.
  • multiple logical channels multiplex the MCH channel in the following manner:
  • One subframe corresponds to one TTI (transmission time interval), and one transport data block TB can be transmitted in one TTI, and each transport data block corresponds to A MAC PDU (Media Access Control Layer Protocol Data Unit).
  • MAC PDU Media Access Control Layer Protocol Data Unit
  • multiple MAC SDUs Service Data Units
  • these MAC SDUs may be from different logical channels, and possible logical channels include MTCH, MCCH, and the like. These data from different logical channels are concatenated together in the MAC PDU and sent together on the physical channel.
  • the trunking communication system is a dedicated wireless communication system developed for industrial users' command and dispatching needs for specific industry applications.
  • Wireless communication system The trunking communication system has a wide application market in the fields of government departments, public security, emergency telecommunications, electric power, civil aviation, petrochemicals and military.
  • the cluster communication in 3GPP LTE is called the group communication service capability GCSE.
  • the industry is currently discussing the possibility of using MBMS technology to achieve cluster communication.
  • the embodiment of the present invention is to provide an MBMS error processing method, a communication node, a communication system, and a storage medium, so as to ensure timely transmission of data when MBMS errors are implemented, reduce data transmission delay, and improve user satisfaction. .
  • a first aspect of the embodiments of the present invention provides an MBMS error processing method, where the method includes: receiving indication information of an MBMS error;
  • the data is that when the MBMS error occurs, the user equipment carries the data being received or the data received by the MBMS.
  • the indication information for receiving an MBMS error includes:
  • the indication information of the MBMS error transmitted from the user equipment UE or the BM-SC is received.
  • the MBMS error is a network device problem that causes MBMS data to fail to be transmitted normally within a specified time.
  • a second aspect of the embodiments of the present invention provides an MBMS error processing method, where the method includes: Obtaining an error indication of an MBMS error of the network device;
  • the indication information is a basis for the application server to establish a unicast bearer and send data by using the unicast bearer.
  • the error indication of obtaining the MBMS error of the network device is:
  • the error indication is extracted from the MBMS scheduling information MSI or RRC signaling sent by the base station eNB.
  • the error indication of the MBMS error sent by the acquiring network device is:
  • the MBMS scheduling information MSI is not received within a specified time or is used to indicate the MBMS difference error indication.
  • the network device is an eNB, an MCE, an MME, an MBMS-GW or a BM-SC.
  • the error indication of acquiring the MBMS error of the network device is:
  • the user equipment UE obtains an error indication of the MBMS error sent by the network device from the MSI or RRC signaling sent by the eNB.
  • the sending the indication information to the application server is:
  • the UE sends the indication information to an application server through application layer signaling of the GC1 interface.
  • the error indication of acquiring the MBMS error of the network device is:
  • the BM-SC acquires its own MBMS error forming error indication
  • the BM-SC receives an error indication of an MBMS error.
  • the sending the indication information to the application server is:
  • the BM-SC sends the indication information to the application server through a GC2 interface.
  • the MBMS error is a network device problem that causes MBMS data to fail to be normally transmitted within a predetermined time.
  • a third aspect of the embodiments of the present invention provides an MBMS error processing method, where the method includes: instructing an information sending node to obtain an error indication of an MBMS error of a network device;
  • the indication information sending node forms the indication information according to the error indication
  • the indication information sending node sends the indication information to an application server
  • the application server receives indication information of an MBMS error
  • the application server establishes a unicast bearer according to the indication information
  • the data is data that the user equipment is receiving through the MBMS or data that is of interest to be received when the MBMS error occurs.
  • the indication information sending node is a UE or a BM-SC.
  • the indication that the indication information sending node acquires the MBMS error of the network device is:
  • the UE extracts the error indication from the MBMS scheduling information MSI or RRC signaling sent by the base station eNB;
  • the BM-SC acquires its own MBMS error forming error indication
  • the BM-SC receives an error indication of an MBMS error.
  • the error indication that the indication information sending node acquires the MBMS error of the network device comprises:
  • the user equipment UE When the user equipment UE does not receive the MBMS scheduling information MSI or the MSI value for indicating the error within the specified time, it determines that the network device has an MBMS error and obtains the error indication by default.
  • a fourth aspect of the embodiments of the present invention provides a communication node, where the communication node is an application service.
  • the application server includes:
  • a first receiving unit configured to receive indication information of an MBMS error
  • a first sending unit configured to send data by using the unicast bearer
  • the data is data that the user equipment is receiving through the MBMS or data that is of interest to be received when the MBMS error occurs.
  • the first receiving unit is configured to receive the user equipment or sent by the BM-SC.
  • a fifth aspect of the embodiments of the present invention provides a communication node, where the communication node includes: an acquiring unit, configured to acquire an error indication of an MBMS error of the network device;
  • Forming a unit configured to form indication information according to the error indication
  • a second sending unit configured to send the indication information to an application server
  • the indication information is a basis for the application server to establish a unicast bearer and send data by using the unicast bearer.
  • the acquiring unit is configured to extract the error indication from MBMS scheduling information MSI or RRC signaling sent by the base station eNB.
  • the communication node is a UE
  • the acquiring unit is configured to: when the MBMS scheduling information MSI is not received within the specified time or the MSI value used to indicate the MBMS error, determine that the network device has an MBMS error and obtain the error indication by default.
  • the network device is an eNB, an MCE, an MME, an MBMS-GW, or a BM-SC.
  • the communication node is a user equipment UE
  • the acquiring unit is configured to acquire, by using an eNB, an error indication of an MBMS error sent by the network device.
  • the second sending unit is configured to send the indication information to the application server by using application layer signaling of the GC1 interface.
  • the communication node is a BM-SC
  • the acquiring unit is configured to acquire an MBMS error forming error indication of the MB-SC itself, or receive an error indication of an MBMS error.
  • the second sending unit is configured to send the indication information to the application server by using a GC2 interface.
  • a sixth aspect of the embodiments of the present invention provides a communication system, where the communication system includes: an indication information sending node, configured to acquire an error indication of an MBMS error of the network device; forming indication information according to the error indication; The indication information is sent to the application server; the application server is configured to receive the indication information of the MBMS error; establish a unicast bearer according to the indication information; and send the data by using the unicast bearer;
  • the data is data that the user equipment is receiving through the MBMS or data that is of interest to be received when the MBMS error occurs.
  • the indication information sending node is a user equipment UE or a BM-SC.
  • the user equipment is configured to extract the error indication from MBMS scheduling information MSI or RRC signaling sent by the base station eNB; or
  • the BM-SC is configured to acquire an error indication of its own MBMS error formation; or The BM-SC is configured to receive an error indication of an MBMS error.
  • the UE is configured to determine that the network device has an MBMS error and obtains the error indication by default when the MBMS scheduling information MSI or the MSI value indicating the MBMS error is not received within a specified time.
  • a seventh aspect of the present invention provides a computer storage medium, where the computer storage medium stores computer executable instructions, and the computer executable instructions can be used in the first to third aspects of the embodiments of the present invention. At least one of the methods.
  • the MBMS error processing method, the communication node, the communication system, and the storage medium when the MBMS is in error or fault, forms indication information; and sends the indication information to the application server; the application server will follow the indication according to the indication
  • the information establishes the unicast bearer in time, so that the data that the user equipment receives through the MBMS or the data that is of interest is converted from the MBMS bearer transmission to the unicast bearer, thereby avoiding the problem that the data cannot be sent normally or in time when the MBMS error occurs. Therefore, the data sent by the sender will reach the receiving end in time, thereby improving user satisfaction.
  • FIG. 1 is a schematic flowchart of an MBMS error processing method according to Embodiment 1 of the present invention
  • FIG. 2 is a schematic flowchart of an MBMS error processing method according to Embodiment 2 of the present invention
  • FIG. 3 is an MBMS according to Embodiment 3 of the present invention
  • FIG. 4 is a schematic flowchart of an MBMS error processing method according to an example 1 of the present invention
  • FIG. 5 is a schematic flowchart of an MBMS error processing method according to an example 2 of the present invention
  • FIG. 7 is a schematic structural diagram of a communication node according to Embodiment 5 of the present invention.
  • FIG. 8 is a schematic structural diagram of a communication system according to Embodiment 6 of the present invention.
  • FIG. 9 is a second schematic structural diagram of a communication system according to Embodiment 6 of the present invention. detailed description
  • Embodiment 1 is a diagrammatic representation of Embodiment 1:
  • the embodiment provides an MBMS error processing method, where the method includes: Step S110: Receive indication information of an MBMS error;
  • Step S120 Establish a unicast bearer according to the indication information.
  • Step S130 Send data by using the unicast bearer.
  • the data is data that the user equipment is receiving through the MBMS or data that is of interest to be received when the MBMS error occurs.
  • the MBMS error in the step S110 may be that the MBMS error may cause the MBMS to be damaged, the interface is damaged, the link is faulty, and the link is congested. error.
  • the MBMS error usually does not include the failure of all network nodes of the communication network; when all the network nodes fail, the information cannot be sent between the network nodes, so the indication information of the MBMS error cannot be sent.
  • the MBMS error may not include an error that can be automatically recovered within the indicated time. In this case, multicast or multicast can still be established, and the MBMS data can still be smoothly performed after the network error is recovered, and the data is The transmission delay is small.
  • the application server when the application server (AS) receives the indication information, it indicates that the current network failure or an error causes the MBMS data to be unavailable, and the network failure or error causes the MBMS data to be unable to be transmitted. It can be called an MBMS error.
  • a unicast bearer with the user equipment is established.
  • the unicast bearer transmits the same data to a plurality of receiving ends at the same time as one transmitting end of the MBMS bearer, and is a data bearer mode in which one transmitting end transmits data only to one receiving end at a time.
  • the AS is a device that sends application layer signaling and/or data to the user equipment through a unicast bearer or an MBMS bearer.
  • the transmitting the data originally carried by the MBMS by using the unicast bearer in step S130 may include at least data that the user equipment is receiving and data that is of interest to the user equipment when the MBMS error is sent; and the data may include the cluster data.
  • the data of interest to the user equipment may specifically include data received by the user equipment to the MBMS bearer before the MBMS error.
  • the network device is a device in a network that provides network services to the user equipment, and specifically includes an eNB, an MCE, an MME, an MBMS-GW, and a BM-SC.
  • the eNB represents a base station, which corresponds to a user equipment UE, and the eNB is a bridge between the UE in the LTE (4G) and the EPC of the evolved core network, and the eNB performs the X2 interface. connection.
  • the MCE is an access network device, and the abbreviation of the Multicell/Multicast Coordination Entity multi-cell/multicast coordination entity configures radio resources for the MBMS service.
  • the MME Mobility Management Entity
  • the MME is a control plane node of the 3GPP protocol LTE core network, and is responsible for the positioning, paging, attachment, and location update of the UE (User Equipment).
  • the MBMS-GW is an MBMS gateway and is responsible for transmitting MBMS signaling and data of the core network.
  • the data can be sent to the destination in time.
  • User equipment to avoid the problem of unsuccessful data transmission or large transmission delay, thus improving user satisfaction.
  • the step S110 may include:
  • the user equipment and the application server are directly connected through the interface GC1.
  • the BM-SG is directly connected to the application server through the interface GC2.
  • the indication information can be forwarded to the user equipment or the BM-SG first, and then the user equipment or the BM-SG. Send to the application server.
  • the BM-SC Broadcast-Multicast Service Centre
  • broadcast multicast service center is used for establishing, modifying, and releasing MBMS bearers.
  • the application server is also directly connected to other network nodes; when the network device fails, the network node may also send indication information to the application server, such as S/P-GW (Serving/ PDN-GateWay); the S/P-GW is a user plane gateway.
  • S/P-GW Server/ PDN-GateWay
  • the S/P-GW is a user plane gateway.
  • the above improvement provides a specific scheme for transmitting indication information to the application gateway, and further simplifies the MBMS error processing method, and has the advantages of avoiding the problem that the data cannot be transmitted or the transmission delay is too large, and has the advantage of being simple.
  • Embodiment 2 is a diagrammatic representation of Embodiment 1:
  • this embodiment provides an MBMS error processing method, where the method includes: Step S210: Obtain an error indication of an MBMS error of a network device;
  • Step S220 Form indication information according to the error indication.
  • Step S230 Send the indication information to an application server.
  • the indication information is a basis for the application server to establish a unicast bearer and send data by using the unicast bearer.
  • the execution subject performing the steps S210 to S230 in this embodiment may be a communication node that can directly transmit data directly to the application server AS, such as a user equipment or a BM-SG.
  • the indication information is formed according to the error indication;
  • the indication information may specifically be a bit bitmap, and is an indication code for indicating a network failure or an error; the indication information may also be text information, etc.
  • the specific form may be various, and is not further limited herein.
  • the network error or fault is reported in the form of indication information in time. Go to the application server, so that the application server can draft the original according to the instructions.
  • the data carried by the MBMS is converted to a unicast bearer for transmission, so as to avoid the problem that the data cannot be transmitted and the transmission delay is large.
  • step S210 is:
  • the error indication is extracted from MBMS scheduling information MSI or RRC signaling sent by the base station eNB.
  • the MSI is an MBMS Scheduling Information (MSI) control unit, and is identified by a MAC PDU subheader carrying a Logical Channel Identifier (LCID).
  • MSI Scheduling Information
  • LCID Logical Channel Identifier
  • Each MAC control unit has a variable length of 2 X bytes (x is the number of elements in the MBMS Session Information List MBMS-Session Info List). The following fields should be included for each MTCH:
  • LCID This field indicates the logical channel ID of the MTCH, which is usually 5 bits in length;
  • Stop MTCH This field indicates the sequence number of the corresponding MTCH end subframe in the MSAP occasion. Usually, the field length is 11 bitS o.
  • the specific Stop MTCH value 2047 indicates that the corresponding MTCH is not scheduled, and the Stop MTCH values 2043 and 2046 are reserved values.
  • the error indication may be carried by using at least one of the 2043 and 2046, such that the composition of the Stop MTCH may be as shown in Table 1. Index represents a bit index, content type represents a content type; and the Stop MTCH value is used to specifically indicate a subframe position of the bearer data.
  • the error indication may be carried by the added value of the MSI or the reserved value 2043 or 2046 to indicate whether the current network device is faulty, resulting in an error that the MBMS bearer data cannot be transmitted.
  • the Radio Resource Control (RRC) protocol signaling may be existing RRC signaling, or may be newly added RRC signaling specifically for transmitting the error indication.
  • the existing RRC signaling may include a multicast control signaling MCCH, a system message block SIB, or a radio resource control reconfiguration signaling RRC Connection Reconfiguration 0 by adding a message or other information to the existing RRC signaling.
  • the coupling forms an error indication to inform the user equipment or the like that the communication node that can directly establish a communication link with the AS currently has an MBMS error.
  • the error indication is extracted from the MSI or RRC signaling by using the embodiment, which is compatible with the prior art, and is simple and fast to implement.
  • step S210 may also be:
  • the MBMS scheduling information MSI is not received within a specified time or is used to indicate the MBMS difference error indication.
  • the MSI is transmitted between the communication nodes to ensure normal communication, and the MSI is usually carried in a radio frame for periodic transmission.
  • the MSI will not be transmitted to the external device, and the user equipment that has not received the MSI will default to an MBMS error in the network at this time, and then step S220 and step S230 are performed. .
  • the method for obtaining an error indication in the embodiment separately uses the MSI and RRC signaling to transmit the content to obtain an error indication, but determines whether an MBMS error occurs according to whether the MSI is transmitted, and the same has the advantage of being simple to implement. .
  • the network device is an eNB, an MCE, an MME, an MBMS-GW or a BM-SC.
  • the error indication of acquiring the MBMS error of the network device is:
  • the user equipment directly or indirectly obtains an error indication of the MBMS error sent by the network device by using the eNB.
  • a wireless connection can be established between the user equipment and the eNB; the eNB can be connected to other network devices.
  • a wired or wireless connection is established, and the user equipment can establish a direct connection with the AS. Therefore, if an eNB or other network has an MBMS error, the eNB directly sends the user equipment or other network equipment to forward the error indication to the eNB, and then The eNB forwards to the user equipment, which is ultimately sent by the user equipment to the AS.
  • the user equipment and the AS can communicate directly through the GC1 port, so the step S230 can be:
  • the user equipment sends the indication information to an application server by using application layer signaling of the GC1 interface.
  • some network devices can establish a direct connection with the AS. Therefore, the network devices can directly send indication information to the AS or receive an error indication from other network devices as an intermediate node, form indication information, and send the indication information to the network device.
  • AS specific as BM-SC.
  • the S210 can also be:
  • the BM-SC acquires its own MBMS error forming error indication
  • the BM-SC receives an error indication of an MBMS error transmitted by another network device.
  • the other network devices are multicast network devices other than the BM-SC, such as an eNB, an MCE, an MME, and an MBMS-GW.
  • the step S230 may be: the BM-SC sends the indication information to the application server through the GC2 interface.
  • the user equipment or the BM-SC network device is used to obtain an error indication, form indication information, and transmit the indication information to the AS, which has the advantage of being simple.
  • the foregoing embodiment provides an MBMS error processing method.
  • the AS sends an indication message to the AS to notify the AS to transfer the data carried by the MBMS to the unicast bearer in time to avoid data. Unable to transmit in time, which improves user satisfaction.
  • Embodiment 3 is a diagrammatic representation of Embodiment 3
  • This embodiment provides an MBMS error processing method, where the method includes: Step S310: Instruct the information sending node to obtain an error indication of the MBMS error of the network device.
  • Step S320 The indication information sending node forms the indication information according to the error indication.
  • Step S330 the indication information sending node sends the indication information to the application server.
  • Step S340 The application server receives the indication of the MBMS error.
  • Step S350 The application server establishes a unicast bearer according to the indication information.
  • Step S360 The application server sends data by using the unicast bearer.
  • the data is data that the user equipment is receiving through the MBMS or data that is of interest to be received when the MBMS error occurs.
  • the embodiment is the combination of the first embodiment and the second embodiment.
  • the error indication of the MBMS error of the network device is obtained.
  • the indication information of the MBMS error is formed, for example, when the indication information sending node and the network device that generates the MBMS error are both BM-SC.
  • the indication information sending node may be a communication node such as a user equipment or a BM-SC that can directly communicate with the application server AS.
  • the step S310 may include: the user equipment extracting the error indication from the MBMS scheduling information MSI or RRC signaling sent by the base station eNB.
  • the user equipment is directly connected to the eNB.
  • the error indication can be directly sent to the user equipment.
  • the error indication can be sent to the The eNB is then sent by the eNB to the user equipment.
  • the error indication may be carried in the MSI or RRC signaling, so the user equipment extracts the error indication from the MSI or RRC signaling in the step S310.
  • the step S310 may further include: the user equipment does not receive the specified time.
  • the MBMS scheduling information MSI or the MSI value indicating the MBMS error is used, determining the Stop MTCH value that can be used to indicate an MBMS error in the foregoing embodiment, specifically, at least one of 2043 and 2046.
  • the Stop MTCH value that can be used to indicate an MBMS error in the foregoing embodiment, specifically, at least one of 2043 and 2046.
  • the MSI When the network device is running normally, the MSI is periodically sent to the user equipment. Therefore, when the MMS error occurs, the MSI is not sent to the user equipment to notify the user equipment that the network equipment failure causes the MBMS error, and the user equipment does not receive the specified time. In the case of MSI, it is directly considered that an error indication has been received, thereby forming indication information.
  • the step S310 may include: the BM-SC acquiring its own MBMS error forming error indication; or
  • the BM-SC receives an error indication of an MBMS error.
  • the BM-SG receives the error indication directly or indirectly from other network devices, such as an eNB, MCE, MME, or MBMS-GW.
  • the error indication may be sent by using newly added signaling or a message, or may be coupled and transmitted in existing various signaling or messages, and the implementation manner may be various. .
  • the MBMS error processing method in the foregoing embodiment is configured to send an indication information to the AS by acquiring an error indication.
  • the AS establishes a unicast bearer with the user equipment based on the indication information, and uses the unicast bearer to send the original MBMS bearer integration. Data can realize the transmission of integrated data in a timely manner, thereby improving user satisfaction.
  • Step 201 The network device generates an error, and the network device may include at least one of the following: an eNB, an MCE, an MME, an MBMS-GW, and a BM-SC.
  • the error refers to an event that causes the MBMS data to fail to be transmitted normally, and does not include a self-recoverable fault or a failure of the entire network node, and is also called an MBMS error.
  • Step 202 Whether the network device is an eNB, if it is to step 203, otherwise the steering step
  • the eNB directly sends the indication information to the UE. Otherwise, the eNB needs to send the indication information to the eNB, and then the eNB sends the indication information to the UE.
  • the network device such as the network device that first needs the error or the management network device of the network device that has the error sends the indication information to the eNB.
  • the indication information may specifically be MSI or RRC signaling including a special value.
  • Step 203 The eNB sends MSI or RRC signaling including a special value to the UE.
  • the RRC signaling is existing RRC signaling, such as MCCH, SIB, and RRC Connection Reconfiguration, or new RRC signaling.
  • Step 204 The UE sends the indication information to the AS.
  • the UE sends indication information to the AS through application layer signaling of the GC1 interface.
  • Step 205 The AS establishes a unicast bearer with the UE.
  • the AS determines, according to the received error indication information, that the data is sent by using the unicast bearer, and the AS establishes a unicast bearer with the UE and sends the data.
  • Step 206 the network device sends indication information to the eNB, and proceeds to step 203.
  • the indication information of the MBMS error is sent to the eNB, and the information may be sent through an existing process or an added procedure.
  • Example two For a method for implementing cluster communication by using a network entity to indicate a network error, as shown in FIG. 5, the method includes:
  • Step 301 An error occurs in the network device. This step is the same as step 201 and will not be described here.
  • Step 302 Whether the network device is a BM-SC, if yes, go to step 303, otherwise go to step 305. If it is a BM-SC, the BM-SC sends the indication information directly to the AS. Otherwise, the indication information is sent to the BM-SC, and then the indication information is sent to the AS through the BM-SC. When the error is not the BM-SC, there is no trigger condition for the BM-SC to generate and send the indication information to the AS. Therefore, the network device that needs the error first or the management network device of the network device that has the error is sent to the BM-SC. The indication information.
  • Step 303 The BM-SC sends an error indication information to the AS.
  • the BM-SC sends error indication information to the AS through the GC2 interface.
  • Step 304 The AS establishes a unicast bearer transmission data with the UE.
  • the AS determines, according to the received error indication information, that the data is sent by using the unicast bearer, and the AS establishes a unicast bearer with the UE and sends the data.
  • Step 305 The network device sends an indication of an MBMS error to the BM-SC, and proceeds to the step
  • the MBMS error indication information is sent to the BM-SC. Specifically, how the BM-SC sends the indication information to the AS, and any method in the prior art may be used.
  • Embodiment 4 is a diagrammatic representation of Embodiment 4:
  • the embodiment provides a communication node, where the communication node is an application server, and the application server includes:
  • the first receiving unit 110 is configured to receive indication information of an MBMS error.
  • the establishing unit 120 is configured to establish a unicast bearer according to the indication information;
  • the first sending unit 130 is configured to send data by using the unicast bearer; where the data is data that the user equipment is receiving through the MBMS or data that is received by the user.
  • the specific structure of the first receiving unit 110 may include a communication interface having a receiving function; the communication interface may be a wired communication interface or a wireless communication interface, such as a receiving antenna.
  • the establishing unit 120 can likewise include a communication interface for establishing a unicast bearer connection link between the application server and the user device.
  • the physical structure of the first sending unit 130 may also include a communication interface, and the communication interface may be a wired communication interface or a wireless communication interface, such as a transmitting antenna.
  • the first receiving unit is configured to receive indication information of an MBMS error sent by the user equipment or the BM-SG.
  • the communication node in this embodiment provides the hardware support for the MBMS error processing method in the first embodiment, and can be used to implement the technical solution in any one of the first embodiment, and has the problem that the data cannot be transmitted when the MBMS error is avoided. Increased user satisfaction.
  • Embodiment 5 is a diagrammatic representation of Embodiment 5:
  • the embodiment provides a communication node, where the communication node includes: an obtaining unit 210 configured to acquire an error indication of an MBMS error of the network device, and a forming unit 220 configured to form according to the error indication. Indication information;
  • the second sending unit 230 is configured to send the indication information to the application server; the indication information is a basis for the application server to establish a unicast bearer and send data by using the unicast bearer.
  • the obtaining unit 210 is configured to receive the error indication according to the difference of the acquisition error indication.
  • the specific structure of the obtaining unit 210 may include a communication interface.
  • the communication interface can be a wired or wireless communication interface, such as a receiving antenna.
  • the acquisition order The specific structure of the element 210 may include a processor; the processor may include a single core or multi-core central processing unit, a digital signal processor, a single chip microcomputer or a programmable logic array, and the like.
  • the physical structure of the second sending unit 230 may also include a communication interface, and the communication interface may be a wired communication interface or a wireless communication interface, such as a transmitting antenna.
  • the acquiring unit 310 is configured to extract the error indication from the MBMS scheduling information MSI or RRC signaling directly or indirectly sent by the network device.
  • MSI or RRC signaling directly or indirectly sent by the network device.
  • the communication node is a user equipment.
  • the acquiring unit 210 is configured to: when the MBMS scheduling information MSI is not received within a specified time, determine that the network device has an MBMS error and obtain the error indication by default. Normally, the user equipment acquires the MSI in a specified time slot or a designated subframe of each radio frame, and when the network abnormality occurs when an MBMS error occurs, the MSI may be suspended from being sent to the user equipment, and the user equipment is Whether or not an MBMS error has occurred in the network can be determined according to whether or not the MSI is received.
  • the obtaining unit 210 includes a communication interface and a processor connected to the communication interface. When the communication interface does not receive the MBMS scheduling information MSI within the specified time, the processor confirms that the network device has an MBMS error, that is, an error indication is obtained.
  • the network device is an eNB, an MCE, an MME, an MBMS-GW or a BM-SC.
  • the acquiring unit 210 may be further configured to obtain an error indication of the MBMS error sent by the network device from the MBMS scheduling information MSI or the RRC signaling sent by the eNB. Therefore, the specific hardware structure of the obtaining unit 210 may be a receiving communication interface such as a receiving antenna.
  • the second sending unit 230 is configured to send the indication information to the application server by using application layer signaling of the GC1 interface.
  • the communication node may also be a BM-SC; the acquiring unit 210 is configured to acquire The MBMS error of the BM-SC itself forms an error indication; or receives an error indication of an MBMS error transmitted by another network device;
  • the second sending unit 230 is specifically configured to send the indication information to the application server by using a GC2 interface.
  • the present embodiment provides an internal structure of the indication information sending node, which is used to send the indication information to the application server AS, and informs the AS that the MBMS error is currently present, and the unicast bearer needs to be established to send the cluster service, which is the MBMS described in the second embodiment.
  • the error handling method provides specific hardware support, and the same has the advantage of high user satisfaction.
  • the embodiment provides a communication system, where the communication system includes:
  • the indication information sending node is configured to obtain an error indication of the MBMS error of the network device; form indication information according to the error indication; and send the indication information to the application server; and the application server is configured to receive an indication of the MBMS error Information; establishing a unicast bearer according to the indication information; and sending data by using the unicast bearer;
  • the data is data that the user equipment is receiving through the MBMS or data that is of interest to be received when the MBMS error occurs.
  • This embodiment is used to provide hardware support for the MBMS error processing method in the third embodiment, and can be used to implement any technical solution described in the first embodiment, and the same problem that the data cannot be sent normally when the MBMS error is avoided. The same increase in user satisfaction.
  • the indication information sending node is a user equipment or a BM-SG.
  • the user equipment may be configured to extract the error indication from the MBMS scheduling information MSI or RRC signaling sent by the base station.
  • the user equipment may be further configured to determine an application example of the communication system according to the embodiment shown in FIG. 8 when the MBMS scheduling information MSI is not received within a specified time; the communication system includes the user equipment.
  • User equipment The UE 10 receives an error indication sent by the network device 20, and the user equipment UE10 forms indication information according to the error indication, and sends the indication information to the application server 30.
  • the network device 20 in which the MBMS error occurs may establish a connection with the application server 30, the network device 20 may also directly send the indication information to the application server 30.
  • the communication system includes a user equipment UE and an application server AS (wherein the cluster communication in 3GPP LTE is called a group communication service capability GCSE,
  • the application server is also referred to as GSCE AS), eNB, MCE, MME, MBMS gateway, BM-SC, service gateway, and PDN gateway.
  • the network device involved in the dashed box 401 can serve as a unicast device; the network device described in the dashed boxes 402 and 403 can function as a multicast device.
  • the Uu, Ml, M2, M3, NAS, Sm, GC1, GC2, and SGi, S1-MME, Sl-U, S11, SGmb, SGI-mb, and S5/8 are all communication interfaces.
  • the U1 is connected to the user equipment UE and the eNB; the M1 is connected to the eNB and the MBMS gateway; the M2 is connected to the eNB and the MCE; the M3 is connected to the MCE and the MME; the S1-MME is connected to the eNB and the MME; and the Sm is connected to the MME.
  • the MBMS gateway; the SGmb and the SGi-mb are both connected to the MBMS gateway and the BM-SG; the GC2 is connected to the BM-SC and the GCSE AS; and the SGi is connected to the GSCE AS and the PDN gateway.
  • the S11 is connected to the MME and the service gateway; the S5/8 is connected to the PDN gateway and the service network management; and the S1-U is connected to the eNB and the service gateway.
  • the communication system in this embodiment through the formation of the error indication and the indication information, enables the AS to convert the data originally scheduled to be carried by the MBMS into a unicast bearer in time, thereby avoiding the data failure when the MBMS service fails.
  • the problem of timely transmission increases user satisfaction.
  • 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 can be used to execute claim 1
  • the storage medium may specifically be a storage medium such as a magnetic tape, a DVD, an optical disk, a removable hard disk or a USB flash drive; the storage medium is preferably a non-transitory storage medium.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Quality & Reliability (AREA)
  • General Engineering & Computer Science (AREA)
  • Computing Systems (AREA)
  • Multimedia (AREA)
  • Mathematical Physics (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本发明公开了一种MBMS差错处理方法、通信节点及通信系统涉及通信领域，为解决现有的MBMS差错时数据无法及时传输而设计。所述方法包括：接收MBMS差错的指示信息；依据所述指示信息，建立单播承载；及通过所述单播承载发送数据；其中，所述数据为在所述MBMS差错发生时，用户设备通过MBMS承载正在接收的数据或感兴趣接收的数据。本发明还公开了一种计算机存储介质。

Description

MBMS差错处理方法、 通信节点、 通信系统和存储介质 技术领域
本发明涉及通信领域的差错处理技术， 尤其涉及一种 MBMS差错处理 方法、 通信节点、 通信系统和存储介质。 背景技术 随着网络 Internet的迅猛发展和大屏幕多功能手机的普及， 出现了大量 移动数据多媒体业务和各种高带宽多媒体业务， 例如， 视频会议、 电视广 播、 视频点播、 广告、 网上教育、 互动游戏等移动数据多媒体业务。 一方 面满足了移动用户不断上升的业务需求， 另一方面也为移动运营商带来新 的业务增长点。 这些移动数据多媒体业务要求多个用户能够同时接收相同 数据， 与一般的数据业务相比， 具有数据量大、 持续时间长、 时延敏感等 特点。
为了有效地利用移动网络资源， 第三代合作伙伴计划（3rd Generation Partnership Project， 简称为 3GPP ) 提出了多媒体广播和组播业务 ( Multimedia Broadcast Multimedia Service, MBMS ) 业务， 该业务是一种 从一个数据源向多个目标传送数据的技术， 实现了网络（包括核心网和接 入网） 资源的共享， 提高了网络资源 （尤其是空中接口资源） 的利用率。
3GPP定义的 MBMS不仅能够实现純文本低速率的消息类多播和广播， 而 且还能够实现高速多媒体业务的广播和多播， 提供多种丰富的视频、 音频 和多媒体业务， 这无疑顺应了未来移动数据发展的趋势， 为 3G 的发展提 供了更好的业务前景。
在长期演进 LTE 中， MBMS 业务可以釆用多播模式方式， 称为 MBSFN ( Multicast/Broadcast over Single Frequency Network, 单频网多播广 播）发送模式， 釆用多播模式发生的 MBMS业务， 也称为 MBSFN业务， 可以在多个小区釆用相同的调制后编码格式， 釆用相同的物理资源发生相 同内容。
所述 MBMS多小区传输的特征：
1 )在 MBSFN 区域内同步传输；
2 ) 支持多小区 MBMS 传输合并；
3 ) MTCH ( Multicast Traffic CHannel, 多播业务信道） 和 MCCH ( Multicast Control CHannel, 多播控制信道）在 p-T-m (点到多点）模式 下映射到 MCH ( Multicast Channel, 多播信道）信道上；
4) MBSFN 同步区域， MBSNF 区域， MBSFN传输， 广告， 保留小 区， 均由操作维护半静态配置。
这样多个小区的 UE ( User equipment, 用户设备）可以接收到多个内 容相同的 MBMS数据并进行 SFN合并， 从而可以提高接收信号的增益。 釆 用相同的物理资源并发送 MBSFN发送模式发送相同 MBMS业务的多个小 区构成了一个 MBSFN区域。
在实际的 LTE组网中， 一个 MBSFN区域上有若干个 MBSFN业务， 这些属于同一个 MBSFN区域的所有 MBSFN业务称为一个 MBSFN业务 组， 也就是说一个 MBSFN业务组仅属于一个 MBSFN区域。 一个 MBSFN 区域包括多个小区， 每个小区都配置了完全相同的一个 MBSFN 业务组。 具备相同的 MBSFN 区域的多个 MBSFN 业务的数据信道 MTCH， 以及 MBSFN业务的控制信道 MCCH可以复用到一条 MCH( Multicast Channel, 多播信道）。 相同 MBSFN区域的 MCCH和多个 MTCH， 即多条逻辑信道 可以映射到同一传输信道 MCH上； MCH通过 MBSFN子帧的传输块承 载。
现有公开技术中， 在 MSAP概念中同时引入 MSAP occasion ( MSAP 时机） ， 其指示了一个动态调度周期的时间段内某个 MSAP所对应的一条 MCH所包括全部多播资源。 在一个 MSAP occasion中可以发送多个 MTCH 和动态调度信息， 还可以包括 MCCH， 动态调度信息承载在 MAC PDU(Protocol Data Unit)控制粒子 CE ( Control Element ) ， MSAP occasion 长度可以为 320ms。 一个 MSAP occasion时间长度就是一个调度周期， 也 称为一个动态调度周期。 一条 MCH通过 MSAP分配了一个或多个 MBSFN 帧中的一个或多个 MBSFN 子帧， 其中釆用多播模式发送的子帧称为 MBSFN子帧， 含有 MBSFN子帧的帧称为 MBSFN帧。
在一条 MCH所配置的每个 MSAP occasion上承载了动态调度信息， 携 带 MTCH到辅助 MSAP子帧的映射信息， 这种映射信息借助于在一个调度 周期内的 MBSFN子帧编号索引关系确定的， UE读取调度信息可以知道每 个 MTCH被分配在哪些 MBSFN子帧上， UE可以在相应的 MBSFN子帧上 读取其感兴趣的 MTCH， 而忽略它不需要读取的 MBSFN子帧， 从而提高 UE的 MBMS业务接收效率， 节省 UE的电能消耗。 这里所述的 MB SFN子 帧编号是这样确定的： 将一个 MCH 在在一个调度周期内所分配的所有 MBSFN子帧按照顺序排列， 依次编号。
在现有 LTE技术中， 多个逻辑信道通过如下的方式复用 MCH信道： 一个子帧对应一个 TTI (传输时间间隔）， 在一个 TTI内可以发送一个传输 数据块 TB， 每个传输数据块对应一个 MAC PDU (媒体接入控制层 协议数 据单元） 。 在一个 MAC PDU中， 可以包含多个 MAC SDU (服务数据单 元） ， 这些 MAC SDU 可以来自不同的逻辑信道， 可能的逻辑信道包括 MTCH, MCCH等。 这些来自不同逻辑信道的数据在 MAC PDU中串接在 一起后一起在物理信道上发送。 集群通信系统是为了满足行业用户指挥调度需求而开发的、 面向特定 行业应用的专用无线通信系统， 系统中大量无线用户共享少量无线信道， 以指挥调度为主体应用， 是一种多用途、 高效能的无线通信系统。 集群通 信系统在政府部门、 公共安全、 应急通信、 电力、 民航、 石油化工和军队 等领域有着广泛的应用市场。在 3GPP LTE中集群通信称为组通信服务能力 GCSE。 目前业界正在讨论釆用 MBMS技术实现集群通信的可能性。
在对现有技术的研究和实践过程中发现现有技术存在以下问题： 当网络出现差错， 如何及时 MBMS承载的集群业务发送用户设备避免 数据无法发送或发送延时过大是现技术亟待解决的问题。 发明内容
有鉴于此， 本发明实施例期望提供一种 MBMS差错处理方法、 通信节 点、通信系统和存储介质，以实现 MBMS差错时及时保证数据的顺利发送， 降低数据发送延时， 提升用户了使用满意度。
为达到上述目的， 本发明实施例的技术方案是这样实现的：
本发明实施例第一方面提供一种 MBMS差错处理方法，所述方法包括： 接收 MBMS差错的指示信息；
依据所述指示信息， 建立单播承载；
通过所述单播承载发送数据；
其中， 所述数据为在所述 MBMS差错发生时， 用户设备通过 MBMS 承载正在接收的数据或感兴趣接收的数据。
优选地， 所述接收 MBMS差错的指示信息包括：
接收从用户设备 UE或 BM-SC发送的 MBMS差错的指示信息。
优选地， 所述 MBMS差错为导致 MBMS数据在规定时间内无法正常 发送的网络设备问题。
本发明实施例第二方面提供一种 MBMS差错处理方法，所述方法包括： 获取网络设备的 MBMS差错的差错指示；
依据所述差错指示， 形成指示信息；
将所述指示信息发送到应用服务器；
所述指示信息为所述应用服务器建立单播承载及利用所述单播承载发 送数据的依据。
优选地，
所述获取网络设备的 MBMS差错的差错指示为：
从基站 eNB发送的 MBMS调度信息 MSI或 RRC信令中提取所述差错 指示。
优选地，
所述获取网络设备发送的 MBMS差错的差错指示为：
在指定时间内未收到 MBMS调度信息 MSI或用于指示所述 MBMS差 差错指示。
优选地， 所述网络设备为 eNB、 MCE、 MME、 MBMS-GW或 BM-SC。 优选地， 所述获取网络设备的 MBMS差错的差错指示为：
用户设备 UE从 eNB发送的 MSI或 RRC信令中获取所述网络设备发 送的 MBMS差错的差错指示。
优选地， 所述将所述指示信息发送到应用服务器为：
所述 UE通过 GC1接口的应用层信令将所述指示信息发送到应用服务 器。
优选地， 所述获取网络设备的 MBMS差错的差错指示为：
所述 BM-SC获取自身的 MBMS差错形成差错指示； 或，
所述 BM-SC接收 MBMS差错的差错指示。
优选地， 所述将所述指示信息发送到应用服务器为： 所述 BM-SC通过 GC2接口向所述应用服务器发送所述指示信息。 优选地， 所述 MBMS差错为导致 MBMS数据在规定时间内无法正常 发送的网络设备问题。
本发明实施例第三方面提供一种 MBMS差错处理方法，所述方法包括： 指示信息发送节点获取网络设备的 MBMS差错的差错指示；
所述指示信息发送节点依据所述差错指示， 形成指示信息；
所述指示信息发送节点将所述指示信息发送到应用服务器；
所述应用服务器接收 MBMS差错的指示信息；
所述应用服务器依据所述指示信息， 建立单播承载；
所述应用服务器通过所述单播承载发送数据；
其中， 所述数据为在所述 MBMS差错发生时， 用户设备通过 MBMS 正在接收的数据或感兴趣接收的数据。
优选地， 所述指示信息发送节点为 UE或 BM-SC。
优选地， 所述指示信息发送节点获取网络设备的 MBMS差错的差错指 示为：
所述 UE从基站 eNB发送的 MBMS调度信息 MSI或 RRC信令中提取 所述差错指示；
所述 BM-SC获取自身的 MBMS差错形成差错指示； 或，
所述 BM-SC接收 MBMS差错的差错指示。
优选地， 所述指示信息发送节点获取网络设备的 MBMS差错的差错指 示包括：：
所述用户设备 UE在指定时间内未收到 MBMS调度信息 MSI或用于指 示差错的 MSI数值时，则确定所述网络设备出现 MBMS差错且默认获取了 所述差错指示。
本发明实施例第四方面提供一种通信节点， 所述通信节点为应用服务 器； 所述应用服务器包括：
第一接收单元， 配置为接收 MBMS差错的指示信息；
建立单元， 配置为依据所述指示信息， 建立单播承载；
第一发送单元， 配置为通过所述单播承载发送数据；
其中， 所述数据为在所述 MBMS差错发生时， 用户设备通过 MBMS 正在接收的数据或感兴趣接收的数据。
优选地， 所述第一接收单元， 配置为接收用户设备或 BM-SC发送的
MBMS差错的指示信息。
本发明实施例第五方面提供一种通信节点， 所述通信节点包括： 获取单元， 配置为获取网络设备的 MBMS差错的差错指示；
形成单元， 配置为依据所述差错指示， 形成指示信息；
第二发送单元， 配置为将所述指示信息发送到应用服务器；
所述指示信息为所述应用服务器建立单播承载及利用所述单播承载发 送数据的依据。
优选地，
所述获取单元，配置为从基站 eNB发送的 MBMS调度信息 MSI或 RRC 信令中提取所述差错指示。
优选地，
所述通信节点为 UE;
所述获取单元，配置为在指定时间内未收到 MBMS调度信息 MSI或用 于指示所述 MBMS差错的 MSI数值时， 则确定所述网络设备出现 MBMS 差错且默认获取了所述差错指示。
优选地，
所述网络设备为 eNB、 MCE、 MME、 MBMS-GW或 BM-SC。
优选地， 所述通信节点为用户设备 UE;
所述获取单元，配置为通过 eNB获取所述网络设备发送的 MBMS差错 的差错指示。
优选地，
所述第二发送单元， 配置为通过 GC1接口的应用层信令将所述指示信 息发送到应用服务器。
优选地，
所述通信节点为 BM-SC;
所述获取单元， 配置为获取所述 MB-SC 自身的 MBMS差错形成差错 指示； 或接收 MBMS差错的差错指示。
优选地，
所述第二发送单元， 配置为通过 GC2接口向所述应用服务器发送所述 指示信息。
本发明实施例第六方面提供一种通信系统， 所述通信系统包括： 指示信息发送节点， 配置为获取网络设备的 MBMS差错的差错指示； 依据所述差错指示， 形成指示信息； 及将所述指示信息发送到应用服务器； 所述应用服务器， 配置为接收 MBMS差错的指示信息； 依据所述指示 信息， 建立单播承载； 及通过所述单播承载发送数据；
其中， 所述数据为在所述 MBMS差错发生时， 用户设备通过 MBMS 正在接收的数据或感兴趣接收的数据。
优选地， 所述指示信息发送节点为用户设备 UE或 BM-SC。
优选地，
所述用户设备，配置为从基站 eNB发送的 MBMS调度信息 MSI或 RRC 信令中提取所述差错指示； 或，
所述 BM-SC, 配置为获取自身的 MBMS差错形成差错指示； 或， 所述 BM-SC， 配置为接收 MBMS差错的差错指示。
优选地， 所述 UE， 配置为在指定时间内未收到 MBMS调度信息 MSI 或用于指示所述 MBMS差错的 MSI数值时，确定所述网络设备出现 MBMS 差错且默认获取了所述差错指示。
本发明实施例第七方面提供一种计算机存储介质， 所述计算机存储介 质中存储有计算机可执行指令， 所述计算机可执行指令能用于本发明实施 例第一方面至第三方面所述的方法的至少中之一。
本发明实施例所述 MBMS差错处理方法、 通信节点、 通信系统和存储 介质， 当 MBMS差错或故障时， 将形成指示信息； 并将所述指示信息发送 到应用服务器； 应用服务器将根据所述指示信息及时的建立单播承载， 从 而将用户设备通过 MBMS正在接收的数据或感兴趣接收的数据由 MBMS 承载发送转换成由单播承载发送， 从而避免了 MBMS差错时数据无法正常 或及时发送的问题， 从而发送端所发送的数据将及时的达到接收端， 从而 提升了用户使用满意度。 附图说明
图 1为本发明实施例一所述的 MBMS差错处理方法的流程示意图； 图 2为本发明实施例二所述的 MBMS差错处理方法的流程示意图； 图 3为本发明实施例三所述的 MBMS差错处理方法的流程示意图； 图 4为本发明示例一所述的 MBMS差错处理方法的流程示意图； 图 5为本发明示例二所述的 MBMS差错处理方法的流程示意图； 图 6为本发明实施例四所述的通信节点的结构示意图；
图 7为本发明实施例五所述的通信节点的结构示意图；
图 8为本发明实施例六所述的通信系统的结构示意图之一；
图 9为本发明实施例六所述的通信系统的结构示意图之二。 具体实施方式
以下结合附图对本发明的优选实施例进行详细说明， 应当理解， 以下 所说明的优选实施例仅用于说明和解释本发明， 并不用于限定本发明。
实施例一：
如图 1所示，本实施例提供一种 MBMS差错处理方法，所述方法包括： 步骤 S110: 接收 MBMS差错的指示信息；
步骤 S120: 依据所述指示信息， 建立单播承载；
步骤 S130: 通过所述单播承载发送数据；
其中， 所述数据为在所述 MBMS差错发生时， 用户设备通过 MBMS 正在接收的数据或感兴趣接收的数据。
所述步骤 S110中的 MBMS差错可为所述 MBMS差错是指导致 MBMS 备的线路板损坏、 接口损坏、 链路失败及链路拥塞等方式都可以能导致 MBMS数据无法正常发送， 都可能造成 MBMS差错。 在具体的实现过程中 所述 MBMS差错通常不包括通信网络所有网络节点失效的情况； 当所有网 络节点失效时， 网络节点之间不能发送信息， 故所述 MBMS差错的指示信 息也就无法发送了。 此外， 所述 MBMS差错还可不包括可在指示时间内自 动恢复的差错， 这种情况下多播或组播还是可以建立的， 所述 MBMS数据 在网络差错恢复后依然可以顺利进行， 且对数据的传输时延很小。
在所述步骤 S120中， 当应用服务器 (Application Server, AS)接收到所 述指示信息时， 表示当前网络故障或出现差错导致 MBMS数据无法产生， 所述网络故障或差错导致 MBMS数据无法传输故又可称为 MBMS差错， 为了保证数据的及时传输， 故建立与用户设备之间的单播承载。 所述单播 承载相比较于 MBMS承载中一个发送端一次性同时向多个接收端发送相同 数据， 为一个发送端一次仅向一个接收端发送数据的数据承载模式。 所述 AS为通过单播承载或 MBMS承载向用户设备发送应用层信令和 /或数据的 设备。
在步骤 S130中利用所述单播承载发送原本该由 MBMS承载的数据至 少可包括发送 MBMS差错时用户设备正在接收的数据以及用户设备感兴趣 的数据； 具体所述数据可包括集群数据。 所述用户设备感兴趣的数据具体 可包括在所述 MBMS差错之前， 用户设备向通过 MBMS承载接收的数据。
在本实施例中所述网络设备为向用户设备提供网络服务的网络中的各 个设备， 具体的包括 eNB、 MCE、 MME、 MBMS-GW及 BM-SC等。
所述 eNB在 3GPP LTE与 LTE-A系统中， 表示基站， 与用户用户设备 UE对应， eNB是 LTE(4G)中 UE和演进后的核心网 EPC之间的桥梁， eNB 之间通过 X2接口进行连接。
所述 MCE为接入网设备， Multicell/Multicast Coordination Entity多 小区 /多播协调实体的缩写， 为 MBMS业务配置无线资源。
所述 MME ( Mobility Management Entity )是 3GPP协议 LTE核心网络 的控制面节点， 它负责 UE(User Equipment)的定位、 传呼、 附着及位置更新 等过程。
所述 MBMS-GW为 MBMS网关， 用于负责核心网 MBMS信令和数据 的传输。
在本实施例中， 通过指示信息的发送、 单播承载的建立并将数据由原 先 MBMS承载发送转换成单播承载发送， 使得当网络出现 MBMS故障或 差错时， 能及时的将数据发送到目的用户设备， 以避免数据的无法发送或 发送延时大的问题， 从而提升了用户满意度。
优选地， 所述步骤 S110可包括：
接收用户设备或 BM-SC发送的 MBMS差错的指示信息。
在现有网络结构中， 用户设备与应用服务器之间通过接口 GC1直接相 连， BM-SG与应用服务器之间通过接口 GC2直接相连； 当网络任一设备出 现故障或差错时， 都可以将指示信息先转发到用户设备或 BM-SG, 再由用 户设备或 BM-SG发送到应用服务器。 所述 BM-SC ( Broadcast-Multicast Service Centre )广播多播业务中心， 用于 MBMS承载的建立、 修改、 释放 等功能。
在具体的实现过程中， 所述应用服务器还直接与其他网络节点相连； 当网络设备出现故障时， 还可通过其他网络节点向应用服务器发送指示信 息， 具体的如 S/P-GW ( Serving/PDN-GateWay )；所述 S/P-GW为用户面网 关。
上述改进， 提供了向应用网关发送指示信息的具体方案， 进一步的具 体化了所述 MBMS差错处理方法， 在具有避免数据无法发送或发送延迟过 大的问题的同时， 还具有实现简便的优点。
实施例二：
如图 2所示，本实施例提供一种 MBMS差错处理方法，所述方法包括： 步骤 S210: 获取网络设备的 MBMS差错的差错指示；
步骤 S220: 依据所述差错指示， 形成指示信息；
步骤 S230: 将所述指示信息发送到应用服务器；
所述指示信息为所述应用服务器建立单播承载及利用所述单播承载发 送数据的依据。
在本实施例中执行所述步骤 S210至步骤 S230的执行主体可以为用户 设备或 BM-SG等可以直接向应用服务器 AS直接发送数据的通信节点。
在所述步骤 S220中， 将依据所述差错指示形成指示信息； 所述指示信 息具体可为比特位图， 为用于表示网络故障或差错的指示代码； 所述指示 信息还可以是文本信息等具体的形式可为多种， 在此就不做进一步的限定。
在所述步骤 S230中， 及时的将网络差错或故障以指示信息的形式上报 到应用服务器， 以便应用服务器根据所述指示信息及时的将原先拟定由
MBMS承载的数据转换到单播承载上来发送， 以避免数据的不能发送及发 送时延大的问题。
具体地， 所述步骤 S210为：
从所述基站 eNB发送的 MBMS调度信息 MSI或 RRC信令中提取所述 差错指示。
在具体的实现过程中， 所述 MSI 为 MBMS 调度信息 （MSI, MCH Scheduling Information ) MAC 控制单元， 通过携带逗辑信道标识 (Logical Channel Identifier, LCID)的 MAC PDU子头来标识。每个 MAC控制单元具 有可变长度， 为 2 X 字节 bytes (x为 MBMS 会话信息列表 MBMS-Session Info List序列中元素的个数)。 针对每个 MTCH应该包含如下域：
LCID: 该域指示 MTCH的逻辑信道 ID， 通常长度为 5 bits;
Stop MTCH: 该域指示 MSAP occasion中相应 MTCH结束子帧的序号， 通常该域长度为 11 bitS o 特定 Stop MTCH值 2047指示相应的 MTCH没有被调 度， Stop MTCH值 2043及 2046为预留值； 故可以利用所述 2043及 2046的至 少一个来承载所述差错指示， 从而所述 Stop MTCH 的构成可如表 1。 Index 表示比特索引， content type表示内容类型； 所述 Stop MTCH值用于具体指 示承载数据的子帧位置。
Figure imgf000014_0001
表 1
故在本实施例中可通过 MSI的新增值或预留值 2043或 2046来承载差 错指示， 来指示当前网络设备是否出现故障， 导致了 MBMS承载数据无法 传输的差错。 此外， 所述无线资源控制（Radio Resource Control, RRC )协议信令可 以为现有的 RRC信令， 也可是新增的专为传输所述差错指示的新增 RRC 信令。 所述现有的 RRC信令可包括多播控制信令 MCCH、 系统消息块 SIB, 或无线资源控制重配置信令 RRC Connection Reconfiguration 0通过在现有的 RRC信令中新增消息或与其他信息耦合形成差错指示来告知用户设备等可 以直接与 AS建立通信链路的通信节点当前出现了 MBMS差错。
釆用本实施例从所述 MSI或 RRC信令提取差错指示，能很好的与现有 技术实现兼容， 实现简便快捷。
具体地， 所述步骤 S210还可为：
在指定时间内未收到 MBMS调度信息 MSI或用于指示所述 MBMS差 差错指示。
在 MBMS通信过程中， 所述 MSI会在通信节点之间相互传输， 以保证 通信的正常进行， 且所述 MSI通常承载在无线帧中周期性传输。 在本实施 例中当某一网络设备出现 MBMS差错， 将不对外传输所述 MSI， 则未接收 到所述 MSI的用户设备即将默认此时网络中发生了 MBMS差错，进而执行 步骤 S220和步骤 S230。
本实施例中所述的获取差错指示的方式有别利用 MSI和 RRC信令来所 传输的内容来获取差错指示， 而是根据 MSI 是否传输来确定是否出现 MBMS差错， 同样的具有实现简便的优点。
优选地， 所述网络设备为 eNB、 MCE、 MME、 MBMS-GW或 BM-SC。 优选地， 所述获取网络设备的 MBMS差错的差错指示为：
用户设备通过 eNB直接或间接获取所述网络设备发送的 MBMS差错的 差错指示。
用户设备与 eNB之间可建立无线连接； eNB又与其他网络设备之间可 建立有线或无线的连接，用户设备又可与 AS之间建立直接连接，故若 eNB 或其他网络出现 MBMS差错时， eNB直接发送用户设备或其他网络设备可 以先将差错指示转发到 eNB， 再由 eNB转发到用户设备， 最终由用户设备 发送到 AS。用户设备与 AS之间通过 GC1口可直接通信，故所述步骤 S230 可为：
所述用户设备通过 GC1接口的应用层信令将所述指示信息发送到应用 服务器。
在具体的实现过程中，有些网络设备与所述 AS可建立直接连接，故这 些网络设备同样的可以直接向 AS 发送指示信息或作为中间节点从其他网 络设备接收差错指示、 形成指示信息并发送到 AS,具体的如 BM-SC。
故， 所述 S210还可为：
所述 BM-SC获取自身的 MBMS差错形成差错指示； 或，
所述 BM-SC接收其他网络设备发送的 MBMS差错的差错指示。 所述 其他网络设备为 BM-SC 以外的多播网络设备， 如 eNB、 MCE、 MME及 MBMS-GW等。 当接收所差错指示的网络设备为 BM-SC时， 则所述步骤 S230可为： 所述 BM-SC通过 GC2接口向所述应用服务器发送所述指示信 息。
利用用户设备或 BM-SC网络设备来获取差错指示、形成指示信息并将 指示信息发送到 AS， 具有实现简便的优点。
综合上述本实施例提供了一种 MBMS差错处理方法， 在网络故障导致 MBMS无法传输的差错时， 通过向 AS发送指示信息以告知 AS及时的将 MBMS承载的数据转移到单播承载上， 避免数据无法及时的传输， 从而提 升了用户满意度。
实施例三：
本实施例提供一种 MBMS差错处理方法， 所述方法包括： 步骤 S310: 指示信息发送节点获取网络设备的 MBMS差错的差错指 示；
步骤 S320: 所述指示信息发送节点依据所述差错指示， 形成指示信息； 步骤 S330:所述指示信息发送节点将所述指示信息发送到应用服务器； 步骤 S340: 所述应用服务器接收 MBMS差错的指示信息；
步骤 S350: 所述应用服务器依据所述指示信息， 建立单播承载； 步骤 S360: 所述应用服务器通过所述单播承载发送数据；
其中， 所述数据为在所述 MBMS差错发生时， 用户设备通过 MBMS 正在接收的数据或感兴趣接收的数据。
本实施例为实施例一与实施例二的结合， 步骤 S310中获取网络设备的 MBMS差错的差错指示中，当所述指示信息发送节点与发生 MBMS差错的 网络设备为同一通信节点时， 则依据自身 MBMS差错形成的指示信息， 具 体的如当所述指示信息发送节点与所述发生 MBMS 差错的网络设备均为 BM-SC时。
优选地，所述指示信息发送节点可为用户设备或 BM-SC等可以与应用 服务器 AS直接通信的通信节点。
当所述指示信息发送节点为用户设备时， 则所述步骤 S310可包括： 所述用户设备从基站 eNB发送的 MBMS调度信息 MSI或 RRC信令中 提取所述差错指示。
用户设备与 eNB直接相连， 当 eNB发送 MBMS差错时， 可以将差错 指示直接发送到用户设备； 当除 eNB以外不直接与用户设备相连的其他网 络设备发送 MBMS差错时， 可以先将差错指示发送到 eNB， 再由 eNB发 送到用户设备。且通常所述差错指示可以承载在 MSI或 RRC信令中， 故所 述步骤 S310中为用户设备从 MSI或 RRC信令中提取所述差错指示。
优选地， 所述步骤 S310 还可包括： 用户设备在指定时间内未收到 MBMS调度信息 MSI或用于指示所述 MBMS差错的 MSI数值时， 则确定 可如上一述实施例中用于指示 MBMS差错的所述的 Stop MTCH值， 具体 的如 2043及 2046中的至少其中之一。
网络设备正常运行时， 将周期性的向用户设备发送 MSI， 故可以在 MBMS差错时通过不对用户设备发送 MSI来告知用户设备网络设备故障导 致了 MBMS差错， 进而用户设备在指定时间内未接收到 MSI时， 则直接可 认为接收到了差错指示， 进而形成指示信息。
当所述指示信息发送节点为 BM-SC时， 则所述步骤 S310可包括： 所述 BM-SC获取自身的 MBMS差错形成差错指示； 或，
所述 BM-SC接收 MBMS差错的差错指示。
所述 BM-SG直接或间接从如 eNB、 MCE、 MME或 MBMS-GW等其 他网络设备接收所述差错指示。 所述差错指示可以是通过新增的信令或消 息来发送， 也可以是耦合在现有各种信令或消息中进行传输， 实现的方式 有多种， 在此就不再——进行阐述。
不管釆用上述哪种方法获取差错指示形成指示信息， 均具有与现有技 术兼容性大， 实现简便的优点。
综合上述本实施例所述的 MBMS差错处理方法， 通过获取差错指示， 向 AS发送指示信息； AS基于指示信息建立与用户设备之间的单播承载， 利用单播承载发送原拟定由 MBMS承载集成数据， 可以及时的实现集成数 据的传输， 从而提升了用户满意度。
以下结合实施例一至实施例三提供几个具体示例。
示例一：
针对通过 MSI中特殊值指示网络差错的场景实现集群通信的方法， 如 图 4所示， 所述方法包括： 步骤 201， 网络设备发生差错， 所述网络设备可包括以下至少一种： eNB、 MCE、 MME、 MBMS-GW及 BM-SC。 所述差错是指导致 MBMS数 据无法正常发送的事件， 不包括可自行恢复的故障或全网节点失效等情况， 又称为 MBMS差错。
步骤 202， 网络设备是否为 eNB， 如果是转向步骤 203， 否则转向步骤
206。
如果是 eNB， 则 eNB直接向 UE发送指示信息， 否则需要先向 eNB发 送指示信息，再通过 eNB向 UE发送指示信息。当发生差错的不是 eNB时， 没有触发条件使 eNB生成并向 UE发送指示信息， 故首先需要发生差错的 网络设备或发生差错的网络设备的管理网络设备等网络设备向 eNB发送所 述指示信息。 所述指示信息具体可以为包含特殊值的 MSI或 RRC信令。
步骤 203， eNB向 UE发送包含特殊值的 MSI或 RRC信令。 其中所述 MSI的特殊值或所述 RRC信令中承载有所述指示信息； 所述特殊值为 stop MTCH=2046或 2043， 所述 MSI由 MCE配置并发送到 eNB。 所述 RRC信 令为现有 RRC信令，如 MCCH、 SIB及 RRC Connection Reconfiguration等， 或新增的 RRC信令。
步骤 204， UE向 AS发送指示信息。 所述 UE通过 GC1接口的应用层 信令向 AS发送指示信息。
步骤 205， AS与 UE建立单播承载。
所述 AS 根据收到的差错指示信息， 确定通过单播承载发送数据， 则 AS与 UE建立单播承载并发送数据。
步骤 206， 网络设备向 eNB发送指示信息， 转向步骤 203.
所述网络设备不是 eNB， 则向 eNB发送 MBMS差错的指示信息， 具 体可通过现有流程或新增流程发送。
示例二 针对通过网络实体指示网络差错的场景实现集群通信的方法， 如图 5 所示， 所述方法包括：
步骤 301， 网络设备发生差错。 本步骤与步骤 201 相同， 这里不再赘 述。
步骤 302， 网络设备是否为 BM-SC， 如果是， 转向步骤 303， 否则转 向步骤 305。 如果是 BM-SC， 则 BM-SC直接向 AS发送指示信息， 否则先 向 BM-SC发送指示信息， 再通过 BM-SC向 AS发送指示信息。 当发生差 错的不是 BM-SC时， 没有触发条件使 BM-SC生成并向 AS发送指示信息， 故首先需要发生差错的网络设备或发生差错的网络设备的管理网络设备等 设备向 BM-SC发送所述指示信息。
步骤 303， BM-SC向 AS发送差错指示信息。
所述 BM-SC通过 GC2接口向 AS发送差错指示信息。
步骤 304， AS与 UE建立单播承载发送数据。
所述 AS 根据收到的差错指示信息， 确定通过单播承载发送数据， 则 AS与 UE建立单播承载并发送数据。
步骤 305， 网络设备向 BM-SC发送 MBMS差错的指示信息， 转向步骤
303。
所述网络设备不是 BM-SC，则向 BM-SC发送 MBMS差错的指示信息， 具体的所述 BM-SC如何向 AS发送所述指示信息， 可以釆用现有技术中任 种方法。
实施例四：
如图 6所示， 本实施例提供一种通信节点， 所述通信节点为应用服务 器； 所述应用服务器包括：
第一接收单元 110， 配置为接收 MBMS差错的指示信息；
建立单元 120， 配置为依据所述指示信息， 建立单播承载； 第一发送单元 130， 配置为通过所述单播承载发送数据； 其中， 所述数据为用户设备通过 MBMS正在接收的数据或感兴趣接收 的数据。
所述第一接收单元 110 的具体结构可包括具有接收功能的通信接口； 所述通信接口可为有线通信接口或无线通信接口， 具体的如接收天线。
所述建立单元 120 同样的可包括通信接口， 用于建立应用服务器与用 户设备之间的单播承载连接链路。
所述第一发送单元 130 的物理结构同样可包括通信接口， 所述通信接 口可为有线通信接口或无线通信接口， 具体的如发送天线。
优选地， 所述第一接收单元， 配置为接收用户设备或 BM-SG发送的 MBMS差错的指示信息。
本实施例所述的通信节点为实施例一所述 MBMS差错处理方法提供了 硬件支撑， 可用来实现实施例一中任一所述技术方案， 同样具有避免了 MBMS差错时数据无法传输的问题， 提升了用户满意度。
实施例五：
如图 7所示， 本实施例提供一种通信节点， 所述通信节点包括： 获取单元 210， 配置为获取网络设备的 MBMS差错的差错指示； 形成单元 220， 配置为依据所述差错指示， 形成指示信息；
第二发送单元 230， 配置为将所述指示信息发送到应用服务器； 所述指示信息为所述应用服务器建立单播承载及利用所述单播承载发 送数据的依据。
在本实施例中所述获取单元 210根据获取差错指示的不同， 当所述获 取单元 210用于从其他设备中接收所述差错指示时， 所述获取单元 210的 具体结构可包括通信接口； 所述通信接口可为有线或无线的通信接口， 具 体的如接收天线。 当所述获取单元 210 自身形成差错指示时， 所述获取单 元 210 的具体结构可包括处理器； 所述处理器可包括单核或多核的中央处 理器、 数字信号处理器、 单片机或可编程逻辑阵列等。
所述第二发送单元 230物理结构同样可包括通信接口， 所述通信接口 可为有线通信接口或无线通信接口， 具体的如发送天线。
作为本实施例的进一步改进， 所述获取单元 310， 配置为从所述网络设 备直接或间接发送的 MBMS调度信息 MSI或 RRC信令中提取所述差错指 示。具体的如何从 MSI或 RRC信令中获取所述差错指示， 可以参见实施例 二， 在此就不再做进一步的详细阐述。
所述通信节点为用户设备； 所述获取单元 210， 配置为在指定时间内未 收到 MBMS调度信息 MSI时， 则确定所述网络设备出现 MBMS差错且默 认获取了所述差错指示。 正常情况下， 用户设备将在每一个无线帧的指定 时隙或指定子帧内获取上所述 MSI，当出现 MBMS差错即出现网络异常时， 可中止向用户设备发送所述 MSI， 则用户设备可根据是否接收到 MSI确定 网络是否出现了 MBMS差错。 此时所述获取单元 210包括通信接口以及所 述通信接口相连的处理器。 所述处理器在所述通信接口未在指定时间内接 收到 MBMS调度信息 MSI时， 确认为网络设备出现 MBMS差错， 即实现 获取了差错指示。
优选地， 所述网络设备为 eNB、 MCE、 MME、 MBMS-GW或 BM-SC。 当所述通信节点为用户设备； 所述获取单元 210，还可具体用于从 eNB 发送的 MBMS 调度信息 MSI 或 RRC 信令中获取所述网络设备发送的 MBMS差错的差错指示。 故所述获取单元 210的具体硬件结构可为接收天 线等接收通信接口。
当所述通信节点为用户设备时， 所述第二发送单元 230， 配置为通过 GC1接口的应用层信令将所述指示信息发送到应用服务器。
此外， 所述通信节点还可为 BM-SC; 所述获取单元 210， 配置为获取 所述 BM-SC 自身的 MBMS差错形成差错指示； 或接收其他网络设备发送 的 MBMS差错的差错指示；。 优选地， 所述第二发送单元 230， 具体用于通 过 GC2接口向所述应用服务器发送所述指示信息。
本实施例提供了一种指示信息发送节点的内部结构， 用于向应用服务 器 AS发送指示信息， 告知 AS当前出现 MBMS差错， 需要建立单播承载 来发送集群业务， 为实施例二所述的 MBMS差错处理方法提供了具体的硬 件支持， 同样的具有用户满意度高的优点。
实施例六：
本实施例提供一种通信系统， 所述通信系统包括：
指示信息发送节点， 配置为获取网络设备的 MBMS差错的差错指示； 依据所述差错指示， 形成指示信息； 及将所述指示信息发送到应用服务器； 所述应用服务器， 配置为接收 MBMS差错的指示信息； 依据所述指示 信息， 建立单播承载； 及通过所述单播承载发送数据；
其中， 所述数据为在所述 MBMS差错发生时， 用户设备通过 MBMS 正在接收的数据或感兴趣接收的数据。
本实施例用于为实施例三所述的 MBMS差错处理方法提供硬件支持， 可以用来实现实施例一所述的任意技术方案， 同样的具有避免了 MBMS差 错时导致数据无法正常发送的问题， 同样的提升了用户满意度。
优选地， 所述指示信息发送节点为用户设备或 BM-SG。
当所述指示信息发送节点为用户设备时， 所述用户设备， 可配置为从 基站发送的 MBMS调度信息 MSI或 RRC信令中提取所述差错指示。 所述 用户设备还可配置为在指定时间内未收到 MBMS调度信息 MSI时，确定所 如图 8所示的为本实施例所述的通信系统的一个应用示例； 所述通信 系统包括用户设备 UE10、 网络设备 20以及应用服务器 30。 所述用户设备 UE10接收网络设备 20发送的差错指示， 所述用户设备 UE10依据所述差 错指示形成指示信息， 并将所述指示信息发送到所述应用服务器 30。
在具体的实现过程中， 若发生 MBMS差错的网络设备 20可与应用服 务器 30之间可建立连接， 则所述网络设备 20还可以直接向所述应用服务 器 30发送所述指示信息。
如图 9所述的为本实施例所述通信系统的另一应用示例； 所述通信系 统包括用户设备 UE、应用服务器 AS( 其中， 在 3GPP LTE中集群通信称为 组通信服务能力 GCSE， 故所述应用服务器又称为 GSCE AS)、 eNB， MCE, MME, MBMS网关、 BM-SC、 业务网关以及 PDN网关。 所述虚线框 401 中所涉及的网络设备可作为单播设备； 所述虚线框 402及 403 中所述的网 络设备可作为多播设备。 其中， 所述 Uu、 Ml、 M2、 M3、 NAS、 Sm、 GC1、 GC2及 SGi、 S1-MME、 Sl-U、 Sll、 SGmb、 SGI-mb以及 S5/8均为通信接 口。所述 Uu连接用户设备 UE及 eNB; 所述 Ml连接 eNB与 MBMS网关； 所述 M2连接 eNB与 MCE; 所述 M3连接 MCE与 MME; 所述 S1-MME 连接 eNB与 MME;所述 Sm连接 MME与 MBMS网关；所述 SGmb及 SGi-mb 均连接 MBMS网关与 BM-SG;所述 GC2连接 BM-SC与 GCSE AS;所述 SGi 连接 GSCE AS与 PDN 网关。 所述 S11连接 MME与业务网关； 所述 S5/8 连接 PDN网关与业务网管； 所述 S1-U连接 eNB与业务网关。
综合上述， 本实施例所述通信系统， 通过差错指示及指示信息的形成， 使得 AS能够及时的将原先拟定由 MBMS承载的数据转换由单播承载， 从 而避免了 MBMS业务出现故障时， 数据不能及时传输的问题， 提升了用户 满意度。
本发明实施例还记载一种计算机存储介质， 所述计算机存储介质中存 储有计算机可执行指令， 所述计算机可执行指令能用于执行权利要求 1 至
15 中至少其中之一所述的方法； 具体如执行所述可执行指令时， 可实现图 1、 图 2及图 3所示方法中的一种或多种。
所述存储介质具体的可以是磁带、 DVD、 光盘、 移动硬盘或 U盘等存 储介质； 所述存储介质优选为非瞬间存储介质。
以上所述， 仅为本发明的较佳实施例而已， 并非用于限定本发明的保 护范围。 凡按照本发明原理所作的修改， 都应当理解为落入本发明的保护 范围。

Claims

权利要求书
1、 一种 MBMS差错处理方法， 所述方法包括：
接收 MBMS差错的指示信息；
依据所述指示信息， 建立单播承载；
通过所述单播承载发送数据；
其中， 所述数据为在所述 MBMS差错发生时， 用户设备通过 MBMS 承载正在接收的数据或感兴趣接收的数据。
2、 根据权利要求 1所述的方法， 其中， 所述接收 MBMS差错的指示 信息包括：
接收从用户设备 UE或 BM-SC发送的 MBMS差错的指示信息。
3、 根据权利要求 1或 2所述的方法， 其中， 所述 MBMS差错为导致 MBMS数据在规定时间内无法正常发送的网络设备问题。
4、 一种 MBMS差错处理方法， 所述方法包括：
获取网络设备的 MBMS差错的差错指示；
依据所述差错指示， 形成指示信息；
将所述指示信息发送到应用服务器；
所述指示信息为所述应用服务器建立单播承载及利用所述单播承载发 送数据的依据。
5、 根据权利要求 4所述的方法， 其中，
所述获取网络设备的 MBMS差错的差错指示为：
从基站 eNB发送的 MBMS调度信息 MSI或 RRC信令中提取所述差错 指示。
6、 根据权利要求 5所述的方法， 其中，
所述获取网络设备发送的 MBMS差错的差错指示为： 在指定时间内未收到 MBMS调度信息 MSI或用于指示所述 MBMS差 差错指示。
7、 根据权利要求 4、 5或 6所述的方法， 其中， 所述网络设备为 eNB、 MCE、 MME、 MBMS-GW或 BM-SC。
8、 根据权利要求 7 所述的方法， 其中， 所述获取网络设备的 MBMS 差错的差错指示为：
用户设备 UE从 eNB发送的 MSI或 RRC信令中获取所述网络设备发 送的 MBMS差错的差错指示。
9、 根据权利要求 8所述的方法， 其中， 所述将所述指示信息发送到 应用服务器为：
所述 UE通过 GC1接口的应用层信令将所述指示信息发送到应用服务 器。
10、 根据权利要求 7所述的方法， 其中， 所述获取网络设备的 MBMS 差错的差错指示为：
所述 BM-SC获取自身的 MBMS差错形成差错指示； 或，
所述 BM-SC接收 MBMS差错的差错指示。
11、 根据权利要求 10所述的方法， 其中， 所述将所述指示信息发送到 应用服务器为：
所述 BM-SC通过 GC2接口向所述应用服务器发送所述指示信息。
12、 一种 MBMS差错处理方法， 所述方法包括：
指示信息发送节点获取网络设备的 MBMS差错的差错指示；
所述指示信息发送节点依据所述差错指示， 形成指示信息；
所述指示信息发送节点将所述指示信息发送到应用服务器；
所述应用服务器接收 MBMS差错的指示信息； 所述应用服务器依据所述指示信息， 建立单播承载；
所述应用服务器通过所述单播承载发送数据；
其中， 所述数据为在所述 MBMS差错发生时， 用户设备通过 MBMS 正在接收的数据或感兴趣接收的数据。
13、 根据权利要求 12 所述的方法， 其中， 所述指示信息发送节点为 UE或 BM-SC。
14、 根据权利要求 13所述的方法， 其中， 所述指示信息发送节点获取 网络设备的 MBMS差错的差错指示为：
所述 UE从基站 eNB发送的 MBMS调度信息 MSI或 RRC信令中提取 所述差错指示；
所述 BM-SC获取自身的 MBMS差错形成差错指示； 或，
所述 BM-SC接收 MBMS差错的差错指示。
15、 根据权利要求 13所述的方法， 其中， 所述指示信息发送节点获取 网络设备的 MBMS差错的差错指示包括：
所述用户设备 UE在指定时间内未收到 MBMS调度信息 MSI或用于指 示差错的 MSI数值时，则确定所述网络设备出现 MBMS差错且默认获取了 所述差错指示。
16、 一种通信节点， 所述通信节点为应用服务器； 所述应用服务器包 括：
第一接收单元， 配置为接收 MBMS差错的指示信息；
建立单元， 配置为依据所述指示信息， 建立单播承载；
第一发送单元， 配置为通过所述单播承载发送数据；
其中， 所述数据为在所述 MBMS差错发生时， 用户设备通过 MBMS 正在接收的数据或感兴趣接收的数据。
17、 根据权利要求 16所述的通信节点， 其中， 所述第一接收单元， 配 置为接收用户设备或 BM-SC发送的 MBMS差错的指示信息。
18、 一种通信节点， 所述通信节点包括：
获取单元， 配置为获取网络设备的 MBMS差错的差错指示；
形成单元， 配置为依据所述差错指示， 形成指示信息；
第二发送单元， 配置为将所述指示信息发送到应用服务器；
所述指示信息为所述应用服务器建立单播承载及利用所述单播承载发 送数据的依据。
19、 根据权利要求 18所述的通信节点， 其中，
所述获取单元，配置为从基站 eNB发送的 MBMS调度信息 MSI或 RRC 信令中提取所述差错指示。
20、 根据权利要求 18所述的通信节点， 其中， 所述通信节点为 UE; 所述获取单元，配置为在指定时间内未收到 MBMS调度信息 MSI或用 于指示所述 MBMS差错的 MSI数值时， 则确定所述网络设备出现 MBMS 差错且默认获取了所述差错指示。
21、 根据权利要求 18、 19或 20所述的通信节点， 其中， 所述网络设 备为 eNB、 MCE、 MME、 MBMS-GW或 BM-SC。
22、 根据权利要求 21所述的通信节点， 其中， 所述通信节点为用户设 备 UE;
所述获取单元，配置为通过 eNB获取所述网络设备发送的 MBMS差错 的差错指示。
23、 根据权利要求 22所述的通信节点， 其中， 所述第二发送单元， 配 置为通过 GC1接口的应用层信令将所述指示信息发送到应用服务器。
24、根据权利要求 21所述的通信节点，其中，所述通信节点为 BM-SC; 所述获取单元， 配置为获取所述 MB-SC 自身的 MBMS差错形成差错 指示； 或接收 MBMS差错的差错指示。
25、 根据权利要求 24所述的通信节点， 其中， 所述第二发送单元， 配 置为通过 GC2接口向所述应用服务器发送所述指示信息。
26、 一种通信系统， 所述通信系统包括：
指示信息发送节点， 配置为获取网络设备的 MBMS差错的差错指示； 依据所述差错指示， 形成指示信息； 及将所述指示信息发送到应用服务器； 所述应用服务器， 配置为接收 MBMS差错的指示信息； 依据所述指示 信息， 建立单播承载； 及通过所述单播承载发送数据；
其中， 所述数据为在所述 MBMS差错发生时， 用户设备通过 MBMS 正在接收的数据或感兴趣接收的数据。
27、 根据权利要求 26所述的通信系统， 其中， 所述指示信息发送节点 为用户设备 UE或 BM-SC。
28、 根据权利要求 27所述的通信系统， 其中，
所述用户设备，配置为从基站 eNB发送的 MBMS调度信息 MSI或 RRC 信令中提取所述差错指示； 或，
所述 BM-SC, 配置为获取自身的 MBMS差错形成差错指示； 或， 所述 BM-SC, 配置为接收 MBMS差错的差错指示。
29、 根据权利要求 27所述的通信方法， 其中， 所述 UE， 配置为在指 定时间内未收到 MBMS调度信息 MSI或用于指示所述 MBMS差错的 MSI
30、 一种计算机存储介质， 所述计算机存储介质中存储有计算机可执 行指令， 所述计算机可执行指令能用于执行权利要求 1至 15所述的方法的 至少其中之一。
PCT/CN2014/081946 2014-03-24 2014-07-10 Mbms差错处理方法、通信节点、通信系统和存储介质 WO2015143795A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP14887181.7A EP3125466B1 (en) 2014-03-24 2014-07-10 Mbms error processing method, communications node, communications system, and storage medium
US15/127,589 US10129042B2 (en) 2014-03-24 2014-07-10 MBMS error processing method, communication node, communication system, and storage medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410112665.1 2014-03-24
CN201410112665.1A CN104955086A (zh) 2014-03-24 2014-03-24 Mbms差错处理方法、通信节点及通信系统

Publications (1)

Publication Number Publication Date
WO2015143795A1 true WO2015143795A1 (zh) 2015-10-01

Family

ID=54169352

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/081946 WO2015143795A1 (zh) 2014-03-24 2014-07-10 Mbms差错处理方法、通信节点、通信系统和存储介质

Country Status (4)

Country Link
US (1) US10129042B2 (zh)
EP (1) EP3125466B1 (zh)
CN (1) CN104955086A (zh)
WO (1) WO2015143795A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113411857B (zh) * 2018-06-28 2022-08-26 华为技术有限公司 通信方法及装置
CN111757401B (zh) * 2019-03-29 2021-12-14 华为技术有限公司 一种网关选择系统及方法
CN116367093A (zh) * 2021-12-27 2023-06-30 维沃移动通信有限公司 多播业务的传输方法、终端及网络侧设备

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101163260A (zh) * 2006-10-14 2008-04-16 华为技术有限公司 一种控制承载变化的系统、装置和方法
WO2008052339A1 (en) * 2006-11-02 2008-05-08 Nortel Networks Limited Method and apparatus for computing alternate multicast/broadcast paths in a routed network
CN101222370A (zh) * 2008-02-01 2008-07-16 华为技术有限公司 使用故障定位报文进行故障定位的方法及装置

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101500194B (zh) * 2008-02-02 2013-01-16 中兴通讯股份有限公司 Rnc间多媒体广播组播业务同步的恢复方法和装置
US8611210B2 (en) * 2008-02-26 2013-12-17 Telefonaktiebolaget L M Ericsson (Publ) Method and apparatus for reliable broadcast/multicast service
CN101729518B (zh) * 2008-10-17 2013-10-23 电信科学技术研究院 实现mbms传输过程中故障保护的方法和系统
WO2010151037A2 (ko) 2009-06-23 2010-12-29 한국전자통신연구원 멀티미디어 브로드캐스트/멀티캐스트 서비스에서 오류 패킷의 재전송 요구 정보 전송 방법 및 재전송 요구에 대한 오류 패킷 재전송 방법
US9628935B2 (en) * 2011-11-15 2017-04-18 Qualcomm Incorporated Group communications with mixed casting services
US8780782B2 (en) * 2012-03-16 2014-07-15 Qualcomm Incorporated Method and apparatus for handling radio link failure in LTE eMBMS
WO2015000912A1 (en) * 2013-07-01 2015-01-08 Nec Europe Ltd. Method for providing multicast/broadcast service continuity for mobile terminals

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101163260A (zh) * 2006-10-14 2008-04-16 华为技术有限公司 一种控制承载变化的系统、装置和方法
WO2008052339A1 (en) * 2006-11-02 2008-05-08 Nortel Networks Limited Method and apparatus for computing alternate multicast/broadcast paths in a routed network
CN101222370A (zh) * 2008-02-01 2008-07-16 华为技术有限公司 使用故障定位报文进行故障定位的方法及装置

Also Published As

Publication number Publication date
EP3125466A1 (en) 2017-02-01
EP3125466A4 (en) 2017-03-22
EP3125466B1 (en) 2019-05-15
CN104955086A (zh) 2015-09-30
US20170180145A1 (en) 2017-06-22
US10129042B2 (en) 2018-11-13

Similar Documents

Publication Publication Date Title
JP5116853B2 (ja) Ｅ−ｕｔｒａｎシステムにおいてｍｂｍｓデータを送信する方法
JP6321830B2 (ja) 基地局、ユーザ端末及び装置
JP6093037B2 (ja) グループコールコンテキストを確立する方法、システム、基地局、及びクラスタｅｐｃ
WO2010121524A1 (zh) 广播多播系统中发送和获取控制信息的方法、基站和ue
KR101801363B1 (ko) Ｍｂｍｓ 제공 장치 및 이를 이용한 ｍｂｍｓ 제공 방법
US20160242216A1 (en) Group communication method, device and system
WO2011082699A1 (zh) 确定组播单频网区域与业务区域映射关系的方法和系统
CN105635984B (zh) 指示信息处理方法及装置
WO2016070579A1 (zh) 确定挂起业务的方法及装置、指示信息处理方法及装置
JP5911586B2 (ja) Ｍｃｅがクラスタセッション確立を制御する方法およびシステム
WO2011147239A1 (zh) Mbms业务上行反馈机制实现方法及系统
WO2022085717A1 (ja) 通信制御方法
EP4030846A1 (en) Method and device for multicasting network slice
WO2021189260A1 (zh) 多播通信方法及通信装置
WO2014153705A1 (zh) 新载波类型小区的业务处理方法、装置及通信系统
WO2015143795A1 (zh) Mbms差错处理方法、通信节点、通信系统和存储介质
EP2903310A1 (en) Multi-media broadcast/multi-media services
WO2012075829A1 (zh) 多媒体广播组播业务的计数方法和系统
WO2016070580A1 (zh) 恢复挂起业务的通知、指示信息处理方法及装置
CN112566045A (zh) 多媒体广播组播业务mbms传输方法及设备
KR20170113755A (ko) 무선통신시스템에서 그룹통신 및 멀티캐스트 서비스를 위한 서비스 연속성 제공 방법 및 장치
WO2011147268A1 (zh) 一种lte系统中广播业务的传输方法及装置
WO2012019542A1 (zh) Mbms业务接收状态的上报方法和设备
JP2024507928A (ja) マルチキャスト／ブロードキャストサービス通信方法、装置、およびシステム
WO2015070370A1 (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: 14887181

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 15127589

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

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2014887181

Country of ref document: EP