WO2018058468A1 - 一种多播业务的发送方法和设备 - Google Patents

一种多播业务的发送方法和设备 Download PDF

Info

Publication number
WO2018058468A1
WO2018058468A1 PCT/CN2016/100942 CN2016100942W WO2018058468A1 WO 2018058468 A1 WO2018058468 A1 WO 2018058468A1 CN 2016100942 W CN2016100942 W CN 2016100942W WO 2018058468 A1 WO2018058468 A1 WO 2018058468A1
Authority
WO
WIPO (PCT)
Prior art keywords
multicast service
base station
rlc
terminal device
rlc pdu
Prior art date
Application number
PCT/CN2016/100942
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 EP16917222.8A priority Critical patent/EP3509329B1/en
Priority to PCT/CN2016/100942 priority patent/WO2018058468A1/zh
Priority to CN201680089577.1A priority patent/CN109792587B/zh
Publication of WO2018058468A1 publication Critical patent/WO2018058468A1/zh
Priority to US16/368,085 priority patent/US10966061B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/08—Arrangements for detecting or preventing errors in the information received by repeating transmission, e.g. Verdan system
    • 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/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1848—Time-out mechanisms
    • 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/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/188—Time-out mechanisms
    • 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/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/1896—ARQ related signaling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
    • H04W16/18—Network planning tools
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/18—Negotiating wireless communication parameters
    • H04W28/22—Negotiating communication rate
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/30—Resource management for broadcast services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/04—Registration at HLR or HSS [Home Subscriber Server]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices

Definitions

  • the present invention relates to the field of communications, and in particular, to a method and device for transmitting multicast services.
  • the 3rd Generation Partnership Project (3GPP) standard is based on cellular networks.
  • 3GPP 3rd Generation Partnership Project
  • IoT Internet of Things
  • NB-IoT Narrow Band-Internet of Things
  • the service generated by the NB-IoT network has smaller data packets, a longer data transmission period, and a lower cost of the terminal equipment under the NB-IoT base station, and a large number of terminal equipments may exist under one NB-IoT base station. To achieve massive deployment of terminal devices.
  • NB-IoT needs to design a multicast transmission scheme based on Single Cell-Point To Multipoint (SC-PTM) technology based on Long Term Evolution (LTE) to save network and upgrade software.
  • SC-PTM Single Cell-Point To Multipoint
  • LTE Long Term Evolution
  • IP Internet Protocol
  • the actual situation does not match. For example, when the coverage level selected by the base station is too low, when there is a poorly covered terminal device in the cell, the multicast transmission success rate of the poorly covered terminal device is low, so that the base station needs to send the service data to the terminal device again, and the coverage level is The poor terminal equipment itself consumes a large amount of resources for unicast, so that the overall resource consumption is large; when the coverage level is high, the transmission of the multicast service consumes a large amount of resources, and if the base station selects a higher coverage level, the cell When the terminal device coverage of the actual subscription multicast service is good, it will lead to a lot of resources. fee.
  • NB-IoT uses a lower Modulation and Coding Scheme (MCS), which uses a small Transport Block Size (TBS) at the physical layer to reduce the cost of the terminal equipment.
  • MCS Modulation and Coding Scheme
  • TBS Transport Block Size
  • PDSCH Physical Downlink Shared Channel
  • the embodiment of the invention provides a method and a device for transmitting a multicast service, which can improve the transmission success rate of the NB-IoT multicast service and reduce the waste of network resources.
  • a first aspect provides a method for transmitting a multicast service, including: a core network device determining a coverage requirement of a multicast service to be transmitted; a core network device sending an coverage request to the access network device, where the coverage requirement is used to determine the access network
  • the device sends the coverage level or transmission parameter of the multicast service to the terminal device.
  • Different coverage requirements may correspond to different coverage levels or transmission parameters. Therefore, the access network device may determine the coverage level or transmission parameter actually used by the multicast service transmission according to the coverage requirement received from the core network, thereby avoiding the base station. The problem of low transmission success rate and waste of resources caused by the choice of coverage level or transmission parameters is not selected.
  • the transmission parameters include an index of the coverage level corresponding to the multicast service or a number of repeated transmissions of the multicast service on the control channel or the shared channel of the physical layer. Different coverage levels can correspond to different transmission parameters.
  • the number of repeated transmissions may be, for example, 256, 512, etc., and the multicast success rate of the multicast service may be improved when the multicast service is repeatedly transmitted multiple times.
  • the core network device includes a broadcast multicast service center BM-SC; and the core network device determines that the coverage requirement of the multicast service to be transmitted includes: BM-SC Determining the coverage requirement of the multicast service according to the correspondence between the service type of the multicast service provided by the third-party server and the coverage requirement of the multicast service; or the service type of the multicast service provided by the BM-SC according to the third-party server, and the BM- The correspondence between the service type of the SC pre-configured multicast service and the coverage requirement of the multicast service determines the coverage requirement of the multicast service.
  • the core network device can pre-configure the correspondence between the service type and the coverage requirement of the multicast service, or the corresponding relationship between the service type of the third-party server and the coverage requirement of the multicast service to the core network device, for example, the coverage of the street lamp is good.
  • the coverage level of the street lamp software upgrade service can be lower, the coverage of the basement water and electricity meter is poor, and the coverage level of the water meter upgrade service can be higher.
  • the core network device includes a BM-SC
  • the access network device includes a base station
  • the core network device sends the coverage request to the access network device, where the BM-SC sends the coverage to the base station by using the mobility management entity and the MCE. It is required that the base station can determine the coverage level or the transmission parameter according to the coverage requirement received from the core network, so as to avoid the problem that the base station itself selects the coverage level or the transmission parameter is improper and the transmission success rate is low and the resource is wasted.
  • the core network device includes a home subscriber server HSS, and the access network device includes a base station; the core network device sends an coverage request to the access network device, including: the HSS sends a coverage request to the base station by using the mobility management entity and the MCE. .
  • the mobility management entity and the HSS interact to obtain the coverage level usage authority information of the multicast service or the multicast service provider, and determine that the coverage requirement is sent to the base station by using the MCE, so that the base station can determine according to the coverage requirement received from the core network.
  • Coverage level or transmission parameters to avoid the problem of low transmission success rate and waste of resources caused by the base station's own choice of coverage level or improper transmission parameters.
  • a second aspect provides a method for transmitting a multicast service, including: receiving, by an access network device, a coverage requirement sent by a core network device; and determining, by the access network device, a coverage of the multicast service sent by the access network device to the terminal device according to the coverage requirement.
  • Level or transmission parameter the access network device sends a multicast service to the terminal device according to the coverage level or transmission parameter. Therefore, the access network device can determine the multicast service transmission according to the coverage requirement received from the core network.
  • the coverage level or transmission parameter used in actual transmission avoids the problem that the base station itself selects the coverage level or the transmission parameter is not suitable, and the transmission success rate is low and the resource is wasted.
  • the transmission parameters include an index of the coverage level corresponding to the multicast service or a number of repeated transmissions of the multicast service on the control channel or the shared channel of the physical layer.
  • a third aspect provides a method for transmitting a multicast service, including: a radio link layer control protocol data control unit RLC PDU in which a base station transmits one or more multicast services to a terminal device at a radio link layer control protocol RLC layer. Or a part of the RLC PDU; the base station receives the feedback information sent by the terminal device, and the feedback information is used to indicate to the base station that the RLC PDU is not successfully received; the base station retransmits the unsuccessfully received RLC PDU to the terminal device.
  • a radio link layer control protocol data control unit RLC PDU in which a base station transmits one or more multicast services to a terminal device at a radio link layer control protocol RLC layer. Or a part of the RLC PDU; the base station receives the feedback information sent by the terminal device, and the feedback information is used to indicate to the base station that the RLC PDU is not successfully received; the base station retransmits the unsuccessfully received RLC PDU to the terminal device.
  • the base station can unicast and retransmit the unreceived RLC PDUs according to the feedback information of the terminal equipment, thereby improving the transmission of the IP data packets on the base station side.
  • the success rate can also avoid the waste of network resources caused by retransmission of the entire IP packet due to a small number of TB transmission errors.
  • the method before the RLC layer sends all the RLC PDUs or part of the RLC PDUs of the multicast service to the terminal device, the method further includes: the base station sends configuration information to the terminal device, where the configuration information includes multicasting. At least one of the number of repeated transmissions of the RLC PDU or part of the RLC PDU of the service at the RLC layer, the first indication information, and the first timer, where the first indication information is used to indicate whether all the RLC PDUs or part of the RLC PDUs support the terminal device.
  • the RLC layer feedback and the unicast retransmission do not receive a successful RLC PDU, and the first timer is used to indicate the length of time that the base station receives the feedback information within a predetermined time.
  • the number of repeated transmissions is the number of times the base station sends all RLC PDUs or partial RLC PDUs to the terminal device multiple times.
  • the configuration information sent by the base station to the terminal device may be the same for different multicast services, or may be used for each multicast service.
  • the duration at which the base station receives the feedback information within a predetermined time that is, the duration in which the base station buffers all the RLC PDUs or the partial RLC PDUs, so as to retransmit the unreceived RLC PDUs to the terminal device within a predetermined time.
  • each part of the RLC PDU corresponds to a first timer
  • the part of the RLC PDU that the base station sends one or more multicast services to the terminal device at the RLC layer includes: The base station sends one or more partial RLC PDUs to the terminal device at the RLC layer, and continues to send the next part of the RLC PDU to the terminal device after the first timer duration.
  • the base station may not need to buffer all the RLC PDUs after transmitting all the RLC PDUs, and the terminal device may not need to receive all the RLC PDUs and then cache all the RLC PDUs, so that the storage cost of the base station and the terminal device is reduced.
  • each RLC PDU header includes a first field, where the first field is used to indicate that the currently sent RLC PDU is the Nth repeated transmission, N is a positive integer, or the first field is used to indicate the current Whether the transmitted RLC PDU is the last repeated transmission; or the downlink control information transmitted by the physical downlink control channel PDCCH of the RLC PDU includes indication information indicating whether the currently transmitted RLC PDU is the last transmission.
  • the terminal device if the terminal device successfully receives a certain RLC PDU or a part of the RLC PDU, if the terminal receives the next RLC PDU, the RLC PDU header displays all the previous RLC PDUs. Or the partial transmission of the RLC PDU, the terminal can wait for a period of time to continue to receive all the RLC PDUs or partial RLC PDUs that the base station repeatedly transmits last time, thereby achieving the effect of saving power.
  • the last RLC PDU transmitted by the base station includes indication information for indicating completion of transmission of all RLC PDUs of the multicast service, for example, all the repeated completion indication bits may be reserved in the RLC PDU, and finally The last RLC PDU in one transmission indicates that all RLC PDU transmission is completed, so that the terminal device learns that the multicast service is repeatedly transmitted; or the base station includes the last RLC PDU in all the RLC PDUs that repeatedly transmit the multicast service.
  • the indication information of the completion is sent to all the RLC PDUs indicating the multicast service for the Nth time, so that the UE can determine whether the transmission of all the RLC PDUs is completed in combination with the number of repeated transmissions in the configuration information.
  • the base station sends configuration information to the terminal device, including: The station broadcasts system information to the terminal device, the system information includes configuration information; or the base station transmits configuration information to the terminal device in the MBMS control channel SC-MCCH; or the base station in the physical downlink control channel PDCCH of the SC-MCCH
  • the terminal device transmits the configuration information; or the base station transmits the configuration information to the terminal device in the PDCCH of the MBMS traffic channel SC-MCCH.
  • a fourth aspect provides a method for transmitting a multicast service, including: receiving, by a terminal device, all radio link layer control protocol data control units RLC of a multicast service that is sent by a base station one or more times in a radio link layer control protocol RLC layer. PDU or partial RLC PDU; the terminal device sends feedback information to the base station, the feedback information is used to indicate to the base station that the RLC PDU is not successfully received; and the terminal device receives the unsuccessfully received RLC PDU that the base station retransmits. After the multicast service is sent, the unicast retransmission of the RLC layer is performed on the base station side.
  • the transmission success rate of the UDP/IP data packet on the base station side can be improved, and on the other hand, a small part of the TB transmission is avoided.
  • the error causes a waste of network resources caused by retransmission of the entire UDP/IP packet.
  • the method further includes: receiving, by the terminal device, configuration information sent by the base station, configuration information Include at least one of the number of repeated transmissions of the RLC PDU or the partial RLC PDU of the multicast service at the RLC layer, the first indication information, and the first timer, where the first indication information is used to indicate whether all the RLC PDUs or part of the RLC PDUs are supported.
  • the terminal device retransmits the unreceived RLC PDU at the RLC layer, and the first timer is used to indicate the duration of time that the base station receives the feedback information within a predetermined time.
  • the terminal device receives a part of the RLC PDU of the multicast service that is sent by the base station one or more times at the RLC layer, and the terminal device receives any part of the multicast service that the base station sends one or more times at the RLC layer.
  • the RLC PDU After receiving the second timer, the RLC PDU receives the next part of the RLC PDU sent by the base station one or more times, and the duration of the second timer is the same as the duration of the first timer.
  • each RLC PDU header includes a first field, first The field is used to indicate that the currently sent RLC PDU is the Nth repeated transmission, N is a positive integer greater than or equal to 1, or the first field is used to indicate whether the currently transmitted RLC PDU is the last repeated transmission; or the physicality of the RLC PDU
  • the downlink control information transmitted by the downlink control channel PDCCH includes indication information indicating whether the currently transmitted RLC PDU is the last repeated transmission.
  • the last RLC PDU received by the terminal device includes indication information indicating that the transmission of all RLC PDUs of the multicast service is completed; or the entire RLC of the multicast service that the terminal device repeatedly receives each time.
  • the last RLC PDU in the PDU includes indication information indicating that the Nth transmission of all RLC PDUs of the multicast service is completed.
  • the terminal device receiving the configuration information sent by the base station includes: the terminal device receives system information broadcast by the base station, and the system information includes configuration information; or the terminal device receives the base station in the multimedia broadcast multicast service MBMS control channel SC-MCCH The configuration information transmitted in the medium device; or the terminal device receives the configuration information sent by the base station in the physical downlink control channel PDCCH of the SC-MCCH; or the terminal device receives the configuration information sent by the base station in the PDCCH of the MBMS service channel SC-MCCH.
  • the fifth aspect provides a core network device, including: a processing module, configured to determine a coverage requirement of a multicast service to be transmitted; and a communication module, configured to send, to the access network device, a coverage requirement determined by the processing module, where the coverage requirement is And determining, by the access network device, the coverage level or transmission parameter of the multicast service to the terminal device.
  • the transmission parameters include an index of the coverage level corresponding to the multicast service or a number of repeated transmissions of the multicast service on the control channel or the shared channel of the physical layer.
  • the processing module is specifically configured to determine a coverage requirement of the multicast service according to a correspondence between a service type of the multicast service provided by the third-party server and a coverage requirement of the multicast service, or according to a third-party server.
  • the service type of the multicast service, and the correspondence between the service type of the BM-SC pre-configured multicast service and the coverage requirement of the multicast service determine the coverage requirement of the multicast service.
  • the communication module is specifically configured to send, by the mobility management entity and the MCE, a coverage requirement determined by the processing module to the base station.
  • the communication module is specifically configured to send, by the mobility management entity and the MCE, a coverage requirement determined by the processing module to the base station.
  • the receiving module is configured to receive the coverage requirement sent by the core network device
  • the processing module is configured to determine, according to the coverage requirement received by the receiving module, the coverage level of the multicast service sent by the access network device to the terminal device.
  • a transmission parameter the communication module is configured to send the multicast service to the terminal device according to the coverage level or the transmission parameter determined by the processing module.
  • the transmission parameters include an index of the coverage level corresponding to the multicast service or a number of repeated transmissions of the multicast service on the control channel or the shared channel of the physical layer.
  • the sixth aspect provides an access network device, including: a receiving module, configured to receive an overlay request sent by a core network device; and a processing module, configured to determine, according to the coverage requirement received by the receiving module, the access network device to send to the terminal device The coverage level or transmission parameter of the multicast service; the communication module is configured to send the multicast service to the terminal device according to the coverage level or the transmission parameter determined by the processing module.
  • the transmission parameters include an index of the coverage level corresponding to the multicast service or a number of repeated transmissions of the multicast service on the control channel or the shared channel of the physical layer.
  • a base station including: a sending module, configured to send all radio link layer control protocol data control unit RLC PDUs of one or more multicast services to a terminal device at a radio link layer control protocol RLC layer or a part of the RLC PDU; the receiving module is configured to receive the feedback information sent by the terminal device, where the feedback information is used to indicate to the base station the RLC PDU that is sent by the communication module and is not successfully received; the sending module is further used to retransmit the terminal device unsuccessfully Received RLC PDU.
  • the sending module is further configured to: send the configuration to the terminal device
  • the information, the configuration information includes at least one of the number of repeated transmissions of the RLC PDU or the partial RLC PDU of the multicast service at the RLC layer, the first indication information, and the first timer, where the first indication information is used to indicate all the RLC PDUs or parts.
  • the first timer is used to indicate the length of time that the base station receives the feedback information within a predetermined time.
  • the sending module is configured to: send one or more RLC PDUs one or more times to the terminal device at the RLC layer, and continue to send the next part of the RLC PDU to the terminal device after the first timer duration.
  • each RLC PDU header includes a first field, where the first field is used to indicate that the currently sent RLC PDU is the Nth repeated transmission, N is a positive integer greater than or equal to 1, or the first The field is used to indicate whether the currently transmitted RLC PDU is the last one of the repeated transmissions; or the downlink control information transmitted by the physical downlink control channel PDCCH of the RLC PDU includes indication information indicating whether the currently transmitted RLC PDU is the last transmission.
  • the last RLC PDU transmitted by the sending module for transmitting all the RLC PDUs includes indication information indicating completion of transmission of all RLC PDUs of the multicast service; or, the communication module is configured to send all
  • the RLC PDU includes, in the last RLC PDU of all the RLC PDUs that repeatedly transmit the multicast service, indication information indicating that the Nth transmission of all the RLC PDUs of the multicast service is completed.
  • the sending module is configured to: broadcast system information to the terminal device, the system information includes configuration information; or send configuration information to the terminal device in the multimedia broadcast multicast service MBMS control channel SC-MCCH; or in the SC - transmitting the configuration information to the terminal device in the physical downlink control channel PDCCH of the MCCH; or transmitting the configuration information to the terminal device in the PDCCH of the MBMS traffic channel SC-MCCH.
  • the eighth aspect provides a terminal device, including: a receiving module, configured to receive all radio link layer control protocol data control unit RLC PDUs of a multicast service that is sent by the base station one or more times in a radio link layer control protocol RLC layer. Or a part of the RLC PDU; a sending module, configured to send feedback information to the base station, where the feedback information is used to indicate the communication to the base station The RLC PDU sent by the module and not successfully received; the receiving module is further configured to receive the unsuccessfully received RLC PDU retransmitted by the base station.
  • the receiving module is further configured to: receive configuration information sent by the base station, where the configuration information includes the number of repeated transmissions of the entire RLC PDU or part of the RLC PDU of the multicast service at the RLC layer, the first indication information, and the first At least one of the timers, the first indication information is used to indicate whether all the RLC PDUs or part of the RLC PDUs support the RLC PDUs that the terminal device does not receive successfully in the RLC layer feedback and the unicast retransmission, and the first timer is used to indicate that the base station is in the reservation. The length of time during which feedback is received.
  • the receiving module is configured to: after receiving any part of the RLC PDU of the multicast service that is sent by the base station one or more times at the RLC layer, and after receiving the duration of the second timer, receiving the base station one or more times The next part of the RLC PDU sent, the duration of the second timer is the same as the duration of the first timer.
  • each RLC PDU header includes a first field, where the first field is used to indicate that the currently sent RLC PDU is the Nth repeated transmission, N is a positive integer greater than or equal to 1, or the first The field is used to indicate whether the currently sent RLC PDU is the last repeated transmission; or the downlink control information transmitted by the physical downlink control channel PDCCH of the RLC PDU includes indication information indicating whether the currently transmitted RLC PDU is the last repeated transmission.
  • the receiving module is configured to receive, in the last RLC PDU received by all the RLC PDUs, the indication information that is used to indicate that all RLC PDUs of the multicast service are sent, or the receiving module is configured to receive all the RLC PDUs.
  • the last RLC PDU of all the RLC PDUs of the multicast service received each time includes indication information indicating that the Nth transmission of all the RLC PDUs of the multicast service is completed.
  • the receiving module is configured to: receive system information broadcast by the base station, the system information includes configuration information; or receive configuration information sent by the base station in the MBMS control channel SC-MCCH of the multimedia broadcast multicast service; or receive the base station Configuration information transmitted in the physical downlink control channel PDCCH of the SC-MCCH; or configuration information transmitted by the base station in the PDCCH of the MBMS traffic channel SC-MCCH.
  • a ninth aspect provides a core network device, including: a processor, configured to determine a coverage requirement of a multicast service to be transmitted; and a transceiver, configured to send, to the access network device, a coverage requirement acquired by the processor, and a coverage requirement And used to determine an coverage level or transmission parameter of the access network device sending the multicast service to the terminal device.
  • the transmission parameters include an index of the coverage level corresponding to the multicast service or a number of repeated transmissions of the multicast service on the control channel or the shared channel of the physical layer.
  • the processor is configured to determine a coverage requirement of the multicast service according to a correspondence between a service type of the multicast service provided by the third-party server and a coverage requirement of the multicast service, or according to the multicast provided by the third-party server.
  • the service type of the service, and the correspondence between the service type of the BM-SC pre-configured multicast service and the coverage requirement of the multicast service determine the coverage requirement of the multicast service.
  • the transceiver is configured to: send, by the mobility management entity and the MCE, the coverage requirement obtained from the processor to the base station.
  • the transceiver is configured to: send, by the mobility management entity and the MCE, the coverage requirement obtained from the processor to the base station.
  • the tenth aspect provides an access network device, including: a receiver, configured to receive an overlay request sent by a core network device, and a processor, configured to determine, according to the coverage requirement acquired by the receiver, the access network device to send to the terminal device The coverage level or transmission parameter of the multicast service; the access network device sends the multicast service to the terminal device according to the coverage level or the transmission parameter.
  • the transmission parameters include an index of the coverage level corresponding to the multicast service or a number of repeated transmissions of the multicast service on the control channel or the shared channel of the physical layer.
  • a base station comprising: a transceiver, all radio link layer control protocol data control unit RLC PDUs for transmitting one or more multicast services to a terminal device at a radio link layer control protocol RLC layer Or a partial RLC PDU; a receiver, configured to receive feedback information sent by the terminal device, where the feedback information is used to indicate to the base station The received RLC PDU; the transceiver is also used to retransmit the unreceived RLC PDU to the terminal device.
  • the transceiver is further configured to send configuration information to the terminal device, where the configuration information includes the number of repeated transmissions of the entire RLC PDU or part of the RLC PDU of the multicast service at the RLC layer, the first indication information, and the first At least one of the timers, the first indication information is used to indicate whether all the RLC PDUs or part of the RLC PDUs support the RLC PDUs that the terminal device does not receive successfully in the RLC layer feedback and the unicast retransmission, and the first timer is used to indicate that the base station is in the reservation. The length of time during which feedback is received.
  • each part of the RLC PDU corresponds to a first timer
  • the transceiver is configured to send one or more partial RLC PDUs to the terminal device at the RLC layer, and After the first timer duration, the next part of the RLC PDU is sent to the terminal device one or more times.
  • each RLC PDU header includes a first field, where the first field is used to indicate that the currently sent RLC PDU is the Nth repeated transmission, N is a positive integer, or the first field is used to indicate the current Whether the transmitted RLC PDU is the last repeated transmission; or the downlink control information transmitted by the physical downlink control channel PDCCH of the RLC PDU includes indication information indicating whether the currently transmitted RLC PDU is the last transmission.
  • the last RLC PDU used by the transceiver for transmission includes indication information indicating completion of transmission of all RLC PDUs of the multicast service; or, the transceiver is used to repeatedly transmit all the multicast services each time.
  • the last RLC PDU in the RLC PDU includes indication information indicating that the Nth transmission of all RLC PDUs of the multicast service is completed.
  • the transceiver is configured to broadcast system information to the terminal device, the system information includes configuration information; or the base station transmits configuration information to the terminal device in the Multimedia Broadcast Multicast Service MBMS Control Channel SC-MCCH; or the base station is in the SC -
  • the physical downlink control channel PDCCH of the MCCH transmits configuration information to the terminal device; or the base station transmits configuration information to the terminal device in the PDCCH of the MBMS traffic channel SC-MCCH.
  • a terminal device includes: a receiver, a radio link layer control protocol data control unit RLC for receiving a multicast service that is sent by the base station one or more times in a radio link layer control protocol RLC layer a PDU or a part of the RLC PDU; the transceiver is configured to send feedback information to the base station, the feedback information is used to indicate to the base station that the RLC PDU is not successfully received, and the receiver is configured to receive the unsuccessfully received RLC PDU that is retransmitted by the base station.
  • the receiver before the terminal device receives all RLC PDUs or partial RLC PDUs of the multicast service that the base station sends one or more times in the RLC layer, the receiver is further configured to: receive configuration information sent by the base station, and configure information. Include at least one of the number of repeated transmissions of the RLC PDU or the partial RLC PDU of the multicast service at the RLC layer, the first indication information, and the first timer, where the first indication information is used to indicate whether all the RLC PDUs or part of the RLC PDUs are supported. The terminal device retransmits the unreceived RLC PDU at the RLC layer, and the first timer is used to indicate the duration of time that the base station receives the feedback information within a predetermined time.
  • the receiver is configured to: after receiving any part of the RLC PDU of the multicast service sent by the base station one or more times at the RLC layer, and after the duration of the second timer, the receiving base station sends the base station one or more times.
  • the next part of the RLC PDU, the duration of the second timer is the same as the duration of the first timer.
  • each RLC PDU header used by the transceiver includes a first field, where the first field is used to indicate that the currently sent RLC PDU is the Nth repeated transmission, and N is greater than or equal to 1.
  • An integer, or a first field is used to indicate whether the currently sent RLC PDU is the last repeated transmission; or the downlink control information transmitted by the physical downlink control channel PDCCH of the RLC PDU includes indicating whether the currently transmitted RLC PDU is the last time. Repeatedly send instructions.
  • the receiver uses the last RLC PDU received to include indication information indicating completion of transmission of all RLC PDUs of the multicast service; or the receiver is configured to repeat the received multicast service each time.
  • the last RLC PDU in all RLC PDUs includes the Nth transmission of all RLC PDUs used to indicate multicast traffic. Completed instructions.
  • the receiver is configured to: receive system information broadcast by the base station, the system information includes configuration information; or the receiver is configured to receive configuration information sent by the base station in the MBMS control channel SC-MCCH of the multimedia broadcast multicast service; or The receiver is configured to receive configuration information that is sent by the base station in the physical downlink control channel PDCCH of the SC-MCCH; or the receiver is configured to receive configuration information that is sent by the base station in the PDCCH of the MBMS service channel SC-MCCH.
  • the base station of the access network device can determine the coverage level or transmission parameter actually used by the current multicast service transmission according to the coverage requirement received from the core network, thereby avoiding the base station not selecting the coverage level or the transmission parameter.
  • the problem of low transmission success rate and waste of resources after the completion of the transmission of the multicast service, the base station can perform unicast retransmission at the RLC layer on the base station side according to the feedback information of the terminal device, and on the other hand, can improve the UDP/IP data of the base station side.
  • the transmission success rate of the packet avoids the problem of wasted network resources caused by retransmission of the entire UDP/IP data packet due to a small number of TB transmission errors.
  • FIG. 1 is a schematic structural diagram of a network according to an embodiment of the present disclosure
  • FIG. 2 is a schematic flowchart of a method for transmitting a multicast service according to an embodiment of the present invention
  • FIG. 3 is a schematic flowchart of a method for sending a multicast service according to an embodiment of the present disclosure
  • FIG. 4 is a schematic flowchart of a method for sending a multicast service according to an embodiment of the present disclosure
  • FIG. 5 is a schematic flowchart of a method for sending a multicast service according to an embodiment of the present invention
  • FIG. 6 is a schematic flowchart of a method for sending a multicast service according to an embodiment of the present invention.
  • FIG. 7 is a signal flow diagram of multiple transmissions of all RLC PDUs of a multicast service according to an embodiment of the present invention.
  • FIG. 8 is a signal flow diagram of multiple transmissions of a partial RLC PDU of a multicast service according to an embodiment of the present invention.
  • FIG. 9 is a schematic structural diagram of a core network device according to an embodiment of the present disclosure.
  • FIG. 10 is a schematic structural diagram of a core network device according to an embodiment of the present disclosure.
  • FIG. 11 is a schematic structural diagram of an access network device according to an embodiment of the present disclosure.
  • FIG. 12 is a schematic structural diagram of an access network device according to an embodiment of the present disclosure.
  • FIG. 13 is a schematic structural diagram of a base station according to an embodiment of the present disclosure.
  • FIG. 14 is a schematic structural diagram of a base station according to an embodiment of the present disclosure.
  • FIG. 15 is a schematic structural diagram of a terminal device according to an embodiment of the present disclosure.
  • FIG. 16 is a schematic structural diagram of a terminal device according to an embodiment of the present invention.
  • the embodiments of the present invention are applicable to wireless devices requiring low complexity and low power consumption of terminal devices.
  • Communication systems such as IoT communication systems, etc., are applicable, for example, to multicast scenarios in NB-IoT communication systems.
  • the network architecture of the embodiment of the present invention may include a terminal device, an access network device, and a core network device.
  • the terminal device may be a user equipment (User Equipment, UE), and the access network may be an Evolved UMTS Terrestrial Radio Access Network (E-UTRAN) or an evolved Universal Mobile Telecommunications System (UMTS)
  • E-UTRAN includes an evolved base station (eNodeB, eNB)
  • the core network device may include a Mobility Management Entity (MME), a Broadcast-Multicast Service Centre (BM-SC), and a multimedia broadcast multicast service. (Multimedia Broadcast Multicast Service, MBMS) and MBMS Coordination Entity (MCE).
  • MME Mobility Management Entity
  • BM-SC Broadcast-Multicast Service Centre
  • MCE Multimedia Broadcast Multicast Service
  • the BM-SC is responsible for managing the MBMS bearer, the temporary temporary mobile group identity (TMGI) of the activation/release service, etc.; the MCE can be used to determine the multicast broadcast single frequency network for the multicast service (Multicast-Broadcast Single)
  • the Frequency Network, MBSFN mode is also the SC-PTM mode.
  • the embodiment of the present invention is directed to the problem that the base station in the prior art is difficult to determine a reasonable coverage level of the multicast service, and the resource is wasted due to the reduction of the transmission reliability.
  • the signaling transmission from the BM-SC to the base station is performed by the present invention.
  • the coverage level or transmission parameter of the multicast service is determined by the core network, and is sent to the base station along with the relevant signaling, so that the base station can send the multicast service by using a reasonable coverage level or transmission parameter, and ensuring that the multicast service is enhanced in coverage.
  • the access network device when transmitting an IP data packet for the NB-IoT, if one or several TB transmissions are unsuccessful, the retransmission and reception overhead caused by the entire IP data packet retransmission may be caused.
  • the access network device when the access network device sends the IP data packet, the IP data packet is segmented into several RLC PDUs at the RLC layer, and after transmitting the several RLC PDUs, the feedback information of the terminal device is received, and the terminal device is heavy. Passing unreceived RLC PDUs does not require retransmission of the entire IP packet to reduce transmission errors. The resource overhead caused by unicast retransmission after error.
  • the embodiment of the present invention provides a method for transmitting the multicast service, as shown in FIG. 2 . Shown, including:
  • the core network device determines a coverage requirement of the multicast service to be transmitted.
  • the coverage requirement of the multicast service to be transmitted may be determined by the characteristics of the current transmission service in the interaction information between the BM-SC and the third-party server in the core network.
  • the coverage requirement is used to characterize the degree of coverage enhancement when the base station transmits the multicast service to the terminal device.
  • the core network device sends an coverage request to the access network device.
  • the BM-SC can send coverage requirements to the base station through the mobility management entity and the MCE.
  • the coverage requirement may be an index of the coverage level or an index range of the coverage level.
  • the access network device determines, according to the coverage requirement, a coverage level or a transmission parameter for transmitting the multicast service to the terminal device.
  • the base station may determine, according to the index of the coverage level or the index range of the coverage level corresponding to the coverage requirement, the coverage level or transmission parameter of the multicast service to be sent to the terminal device.
  • the index of the coverage level may be represented by 0, 1, 2, ..., the index of different coverage levels corresponds to different coverage levels or transmission parameters, and different coverage levels correspond to different transmission parameters, and the transmission parameters may include the multicast service at the physical layer.
  • the number of repeated transmissions on the control channel or the shared channel for example, the number of repeated transmissions may be 256, 512, 1024, and the like.
  • the access network device can determine the coverage level or transmission parameter actually used by the multicast service transmission according to the coverage requirement received from the core network, thereby avoiding the successful transmission of the base station by selecting the coverage level or the transmission parameter is inappropriate.
  • An embodiment of the present invention provides a method for transmitting a multicast service, as shown in FIG. 3, including:
  • the BM-SC obtains a multicast service from a third-party server, allocates a corresponding session identifier and TMGI for the multicast service, and determines a coverage requirement of the multicast service.
  • the multicast service is sent to the BM-SC of the core network device, and the BM-SC allocates a session identifier (Session ID) and a TMGI for the multicast service to send the session identifier and the TMGI.
  • the UE receiving the multicast service starts to receive the multicast service.
  • the BM-SC can determine the coverage requirement of the multicast service according to the correspondence between the service type of the multicast service provided by the third-party server and the coverage requirement of the multicast service; or the BM-SC can multicast according to the third-party server.
  • the service type of the service and the correspondence between the service type of the BM-SC pre-configured multicast service and the coverage requirement of the multicast service determine the coverage requirement of the multicast service.
  • the coverage requirement is used to indicate the coverage enhancement degree when the base station sends the multicast service to the terminal device, and different coverage requirements correspond to different coverage levels or transmission parameters.
  • the BM-SC can determine the coverage requirement according to the service type of the service provided by the third-party server, for example, because the coverage of the street lamp is good, the coverage requirement of the street lamp software upgrade service can be lower; due to poor coverage of the basement The coverage requirements of the basement's hydropower software upgrade business can be higher.
  • the operator service operation or the network management system may pre-configure the correspondence between the service type and the coverage requirement in the BM-SC, so that after obtaining the service type from the third-party server, the BM-SC may determine the multiple according to the pre-configured correspondence. Coverage requirements for broadcasting services.
  • the BM-SC sends the session identifier of the multicast service, the TMGI, and the start time of the service to the UE in a unicast manner.
  • the UE can prepare to receive the multicast service according to the session identifier, the TMGI, and the start time of the service.
  • the BM-SC Before the multicast service starts transmitting, the BM-SC sends a session start request message to the MME, where the session start request message includes a cell list and an coverage requirement for using the multicast for the multicast service.
  • the cell list includes a cell identifier of a base station that receives the multicast service, so that the MME sends the coverage request to the base station indicated by the cell identifier.
  • Coverage requirements can be used
  • a word or other identification indicates that different data or identifications indicate different coverage levels or transmission parameters.
  • the MME sends an MBMS Session Start Request message to the MCE, where the MBMS Session Start Request message includes a cell list and an overlay requirement for using the multicast for the multicast service.
  • the MCE sends the coverage requirement and the SC-PTM indication to the base station corresponding to the cell list.
  • SC-PTM is a single-cell point-to-multipoint technology used to implement the transmission of multicast services.
  • the base station determines the coverage level or the transmission parameter according to the coverage requirement, and sends the received service to the UE in multicast form.
  • the base station determines, according to the coverage requirement, a coverage level or a transmission parameter for transmitting the multicast service to the terminal device.
  • Different coverage requirements correspond to different coverage levels or transmission parameters.
  • the coverage level is 0, and the corresponding transmission parameter may be the number of repeated transmissions of the multicast service on the control channel or the shared channel of the physical layer, for example, The number of repeated transmissions may be 256, 512, 1024, and the like.
  • the transmission parameter may also be a range of the number of repeated transmissions, for example, the range is [256, 512], and the base station may take values in the range according to different service types, so as to select an appropriate number of repeated transmissions for the service.
  • the streetlight software upgrade service has better coverage of the streetlights, and the number of repeated transmissions can be lower.
  • the base station may send a parameter configuration to the UE by using a system information (SIB) 20 and a single cell MBMS control channel (SC-MCCH), where the parameter configuration includes the repeated transmission times, and The multicast service is transmitted to the UE through a single cell MBMS Traffic Channel (SC-MTCH).
  • SIB system information
  • SC-MCCH single cell MBMS control channel
  • the MME and the MCE send the coverage request to the base station, so that the base station determines the coverage level or the transmission parameter according to the received coverage requirement to avoid The base station chooses to cover itself, etc.
  • the embodiment of the present invention provides a method for transmitting the multicast service, as shown in FIG. 4 . Show, including:
  • the BM-SC obtains a multicast service from a third-party server, and allocates a session identifier and a TMGI for the multicast service.
  • the multicast service is sent to the BM-SC of the core network device, and the BM-SC allocates the session identifier Session ID and the TMGI for the multicast service, so as to send the session identifier and the TMGI to the receiving.
  • the UE of the multicast service starts to receive the multicast service.
  • the BM-SC sends the session identifier of the multicast service, the TMGI, and the start time of the multicast service to the UE in a unicast manner.
  • the BM-SC Before the multicast service starts transmitting, the BM-SC sends a session start request message to the MME, where the session start request message includes a cell list that uses multicast for the multicast service.
  • the MME sends a request message to the HSS, where the request message includes multicast service information, and the HSS sends a response message to the MME, where the response message includes the usage authorization information of the coverage level in the subscription information of the multicast service or the multicast service provider.
  • the multicast service information may include a session identifier, a TMGI or an identifier of the multicast service provider, etc.
  • the response message may include the use authorization information of the coverage level in the subscription information of the TMGI allocated by the HSS for the multicast service, or a response.
  • the message may include usage authorization information of the coverage level of the HSS according to the subscription information of the multicast service provider.
  • the subscription information is generated when the multicast service or the multicast service provider registers in the network, and is stored in the HSS, and the subscription information may include the usage permission of the service or service provider in the coverage level of the network.
  • the MME determines a coverage requirement of the multicast service according to the use authorization information, and sends an MBMS session start request message to the MCE, and the MBMS session start request message packet Including the coverage requirements of the multicast service and the list of cells in which the multicast service uses multicast.
  • the MME may determine the coverage requirement of the multicast service according to the corresponding relationship between the usage rights of the coverage level and the coverage requirement, and send the coverage requirement of the multicast service to the MCE.
  • the cell list includes a cell identifier of the base station that receives the multicast service, so that the MCE sends the coverage requirement of the multicast service according to the base station indicated by the cell list.
  • the MCE sends an SC-PTM indication and a coverage requirement of the multicast service to the base station.
  • the base station determines, according to the coverage requirement of the multicast service, the coverage level or transmission parameter of the multicast service sent by the base station to the UE.
  • step 407 For the implementation of the step 407, refer to the foregoing step 306, and details are not described herein again.
  • the HSS of the core network sends the usage rights of the coverage level of the multicast service or the multicast service provider in the network to the MME, so that the MME determines the coverage requirement of the multicast service according to the usage authority of the coverage level, and then passes the The MCE sends the coverage requirement to the base station, so that the base station determines the coverage level or the transmission parameter according to the received coverage requirement, so as to avoid the problem that the base station itself selects the coverage level or the transmission parameter is low and the transmission success rate is low and the resource is wasted.
  • An embodiment provides a method for transmitting a multicast service, as shown in FIG. 5, including:
  • the base station sends, at the radio link layer control protocol RLC layer, all radio link layer control protocol data control unit RLC PDUs or partial RLC PDUs of the one or more multicast services to the terminal device in a multicast manner.
  • the transmission of all RLC PDUs or partial RLC PDUs here may be understood as the base station repeatedly transmitting N times all RLC PDUs or partial RLC PDUs to the terminal device, where N is a positive integer.
  • the partial RLC PDU is an RLC PDU included in each part after the IP data packet is divided and concatenated at the RLC layer to form a plurality of RLC PDUs, and the number of the RLC PDUs is divided into a plurality of parts.
  • the terminal device may process the connected state when receiving the multicast service sent by the base station, or may be in an idle state.
  • the terminal can receive the multicast service in an idle state.
  • the terminal device sends feedback information to the base station, where the feedback information is used to indicate to the base station that the RLC PDU is not successfully received.
  • the terminal device When the terminal device receives the complete RLC PDU, the RLC PDU that is not successfully received is fed back to the base station; or when the terminal device receives the partial RLC PDU, the RLC PDU that is not successfully received is fed back to the base station, so that the base station continues to send the next to the terminal device. A part of the RLC PDU.
  • the base station retransmits the RLC PDU that is not successfully received to the terminal device.
  • the base station may retransmit the unreceived RLC PDU to the terminal device in unicast mode, or retransmit the RLC PDUs that are not successfully received by the multiple terminal devices in the multicast mode. limited.
  • the base station can retransmit the unreceived RLC PDUs to the terminal device according to the feedback information of the terminal device, thereby improving the transmission success rate of the IP data packets on the base station side. It can also avoid the waste of network resources caused by retransmission of the entire IP data packet due to a small number of TB transmission errors.
  • An embodiment of the present invention provides a method for transmitting a multicast service, as shown in FIG. 6, including:
  • the base station sends configuration information to the terminal device.
  • the configuration information may include at least one of the number of repeated transmissions of the RLC PDU or the partial RLC PDU of the multicast service at the RLC layer, the first indication information, and the first timer, where the first indication information is used to indicate all the RLC PDUs or part of the RLC. Whether the PDU supports the RLC layer feedback and unicast retransmission of the RLC PDU that the terminal device does not receive successfully, and the first timer is used to indicate the length of time that the base station receives the feedback information within a predetermined time.
  • the number of repeated transmissions is the number of times the base station sends all RLC PDUs or partial RLC PDUs to the terminal device multiple times.
  • the configuration information sent by the base station to the terminal device may be the same for different multicast services, or may be used for each multicast service. This application is not limited.
  • the sending, by the base station, the configuration information to the terminal device may include: the base station broadcasting the system information to the terminal device, where the system information includes the configuration information, for example, the base station carries the configuration information in a dedicated system information block (SIB) 20 of the SC-PTM.
  • SIB system information block
  • the terminal device sends configuration information, which is not limited in this application.
  • the base station sends, at the RLC layer, all the RLC PDUs or partial RLC PDUs of the one or more multicast services to the terminal device.
  • the base station may divide and concatenate the IP data packets of the multicast service at the RLC layer to form a plurality of RLC PDUs, and then the base station may send all the RLC PDUs to the terminal device at the RLC layer, or may send the RLC PDU to the terminal device at the RLC layer. After the partial RLC PDUs of the plurality of RLC PDUs, the next part of the RLC PDUs of the plurality of RLC PDUs are transmitted; or the base station may repeatedly send the IP to the terminal device at the RLC layer according to the repeated transmission times in the configuration information in step 601.
  • the RLC PDU or part of the RLC PDU of the data packet can improve the receiving success rate of the RLC PDU, that is, the receiving success rate of the IP data packet provided by the base station side.
  • each RLC PDU header includes a first field, where the first field is used to indicate the currently sent RLC PDU.
  • the first field is used to indicate that the current number of repetitions is the first time, the second time, the third time, etc.; or, the first field is used to indicate whether the currently transmitted RLC PDU is the last.
  • the one-time repeated transmission may occupy 1 bit; or the downlink control information transmitted by the PDCCH that sends the RLC PDU includes whether the current transmitted RLC PDU is the most
  • the indication information that is repeatedly transmitted the next time can occupy 1 bit.
  • the terminal device For the terminal device, if the terminal device successfully receives a certain RLC PDU, if the terminal receives the RLC PDU that is sent next time, the RLC PDU header displays the repeated transmission of the previously sent RLC PDU, then The terminal can wait for a period of time before continuing to receive the last repeated RLC PDU sent by the base station, thereby achieving the effect of saving power.
  • the base station transmits all the RLC PDUs in the multicast form to the terminal device at the RLC layer, the re-segment transmission is supported between different repeated transmissions of the same RLC PDU.
  • the physical layer cannot provide the TBS of the same size to carry the RLC PDU0.
  • the base station can re-segment the RLC PDU0 and further disassemble the original RLC PDU.
  • each RLC segment PDU carries The same sequence number as the split RLC PDU, the sub-sequence of the RLC segment PDU, and indication information indicating whether the RLC segment PDU is the last segment of the RLC PDU.
  • the last RLC PDU that the base station repeats may include indication information indicating that the transmission of all the RLC PDUs of the multicast service is complete, for example, All the repeated completion indication bits are reserved in the RLC PDU, and all the RLC PDUs are sent in the last RLC PDU of the last transmission, so that the terminal device knows that the multicast service is repeatedly transmitted; or, the base station repeats the transmission every time.
  • the last RLC PDU of all the RLC PDUs of the broadcast service includes indication information indicating that the Nth transmission of all the RLC PDUs of the multicast service is completed, so that the UE can determine whether all the RLC PDUs are sent according to the number of repeated transmissions in the configuration information. carry out.
  • the multicast service may be divided into several parts at the RLC layer, and then multiple partial RLC PDUs are obtained, and each part of the RLC PDU is sent once or multiple times.
  • Each part of the RLC PDU is transmitted in a similar manner to the base station transmitting all RLC PDUs, and in each part of the RLC PDU.
  • the last RLC PDU carries the indication information that the partial RLC PDU is sent.
  • the granularity of the part may be: each IP data packet, or the maximum buffer of the RLC layer, or the maximum serial number (SN) of the RLC layer, or may be flexible control of the base station.
  • the terminal device sends feedback information to the base station, where the feedback information is used to indicate to the base station that the RLC PDU is successfully received.
  • the base station may buffer all RLC PDUs during the first timer operation to receive the terminal device transmission during the first timer operation. Feedback information to facilitate unicast retransmission of the unsuccessfully received RLC PDU indicated by the feedback information to the terminal device.
  • the second timer, the duration of the second timer, and the first timing may be started in the terminal device according to the duration of the first timer in the configuration information.
  • the duration of the device is the same, and the terminal device may initiate a random access procedure within the duration of the second timer to feed back the unsuccessfully received RLC PDU to the base station, where the feedback information carries the information of the RLC PDU that was not successfully received, such as the SN number. Wait.
  • the terminal device may also carry a new cause value in the access request to indicate for multicast feedback. Since it is a multicast transmission service, a large number of terminal devices may perform feedback.
  • the terminal device randomly selects a time to access the base station between [0-second timer duration], network congestion can be alleviated.
  • the second timer in the terminal device is activated because the terminal device identifies all RLC PDUs that the base station has transmitted the multicast service, but if the terminal device receives the error, for example, the terminal is not successfully received.
  • the terminal device cannot recognize whether the multicast service is transmitted or not, and does not trigger feedback. Therefore, the terminal device may start or restart the third timer after receiving one RLC PDU. If the third timer expires, the terminal device has not received the new RLC PDU, and the network abnormality may be considered.
  • the terminal device can directly initiate feedback when the random access is in the connected state, so as to acquire a new RLC PDU from the base station.
  • the third timer can be configured by the base station and carried in the configuration letter. Interest. That is, the configuration information may further include a third timer, where the third timer is used by the terminal device to send any one of the RLC PDUs within a predetermined time of the third timer after receiving one RLC PDU, and then send the signal to the base station. Feedback information to indicate to the base station that the RLC PDU was not successfully received.
  • the base station retransmits the unreceived RLC PDU to the terminal device.
  • the base station may retransmit the unreceived RLC PDU to the terminal device in unicast mode, or retransmit the RLC PDUs that are not successfully received by the multiple terminal devices in the multicast mode. limited.
  • re-segmentation can also be supported between multicast transmission and unicast retransmission.
  • the physical layer cannot provide the same size of the TBS to carry the RLC PDU0, and the base station re-segmentes the RLC PDU0 during the unicast retransmission, and splits the RLC PDU0 into A plurality of RLC segment PDUs are transmitted.
  • the base station may re-segment any RLC PDU when unicasting any RLC PDU to obtain at least one RLC segment PDU, and each RLC segment
  • the PDU carries the same sequence number as the previous RLC PDU, the sub-sequence of the RLC segment PDU, and indication information indicating whether the RLC segment PDU is the last segment of the RLC PDU.
  • the base station needs to send the multicast service after transmitting the configuration information to the UE1 ⁇ UEx. If the multicast service has a total of N RLC PDUs, the N RLC PDUs are sent three times, and the Nth is sent the third time. The RLC PDU carries the transmission completion indication. After the three transmissions are completed, UE1 and UE2 have unsuccessfully received RLC PDUs. UE1 and UE2 can initiate random access and send feedback information to the base station.
  • the base station unicasts the RLC PDU that the UE1 has not successfully received, and then unicasts to the UE2, and retransmits the RLC PDU that the UE2 has not successfully received.
  • the number of repeated transmissions in the configuration information is 3, and the first part of the RLC PDU1 to a is repeatedly transmitted, and then the second part of the RLC PDU is continued.
  • the base station first UE1 to UEx transmit the first RLC PDU1 ⁇ a, then send the second RLC PDU1 ⁇ a to UE1 ⁇ UEx, and then send the third RLC PDU1 ⁇ a to UE1 ⁇ UEx, and the third RLC PDU1 ⁇ a
  • the last RLC PDU carries the repeated transmission completion indication, and then the UE that has not successfully received the RLC PDU in UE1 to UEx sends feedback information to the base station, and the base station performs unicast retransmission to the UE that has not successfully received the RLC PDU;
  • the base station sends the first RLC PDU a+1 ⁇ b to UE1 ⁇ UEx, and then sends the second RLC PDU a+1 ⁇ b to UE1 ⁇ UEx, and then sends the third RLC PDU a+1 to UE1 ⁇ UEx ⁇ b.
  • the last RLC PDU of the third RLC PDUs a+1 to b carries the repeated transmission completion indication, and then the UEs that have not successfully received the RLC PDU in UE1 to UEx send feedback information to the base station, and the base station redirects.
  • a UE that has not successfully received the RLC PDU performs unicast retransmission.
  • multiple transmissions are performed at the RLC layer by using the multicast service, which can improve the reception success rate of the RLC PDU, that is, improve the reception success rate of the UDP/IP data packet provided by the base station side.
  • the multicast service is sent, the unicast retransmission of the RLC layer is performed on the base station side.
  • the transmission success rate of the UDP/IP data packet on the base station side can be improved, and on the other hand, a small part is avoided.
  • the TB transmission error causes a problem of wasted network resources caused by retransmission of the entire UDP/IP packet.
  • the base station and the UE need to buffer all the RLC PDUs of the multicast transmission once, so that when the storage cost of the terminal device increases, the base station may send the terminal device one or more times.
  • the base station After the sub-part RLC PDU receives the feedback information and unicasts the unreceived RLC PDU to the terminal device, the base station sends the next part of the RLC PDU to the terminal device, which can reduce the storage cost of the base station and the terminal device.
  • each network element such as a core network device, an access network device, and a terminal device, includes a hardware structure and/or a software module for performing each function in order to implement the above functions.
  • a hardware structure and/or a software module for performing each function in order to implement the above functions.
  • the present invention can be implemented in a combination of hardware or hardware and computer software in combination with the elements and algorithm steps of the various examples described in the embodiments disclosed herein. a function Whether it is implemented in hardware or computer software to drive hardware depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods for implementing the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present invention.
  • the embodiments of the present invention may perform functional module division on a core network device, an access network device, and a terminal device according to the foregoing method.
  • each functional module may be divided according to each function, or two or more functions may be used.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of the module in the embodiment of the present invention is schematic, and is only a logical function division, and the actual implementation may have another division manner.
  • FIG. 9 is a schematic structural diagram of a data transmission apparatus involved in the foregoing embodiment, which may be used to perform the function of the core network device in the foregoing method embodiment.
  • the apparatus may include: a processing module 901 and a communication module 902. .
  • the physical device corresponding to the processing module 901 may be a processor
  • the physical device corresponding to the communication module 902 may be a transceiver.
  • the device may further include a storage module 903, configured to store program code and data of the core network device.
  • the core network device involved in the embodiment of the present invention may be the core network device shown in FIG.
  • the core network device includes a processor 102, a transceiver 103, a memory 101, and a bus 104.
  • the transceiver 803, the processor 102, and the memory 101 are connected to each other through a bus 104.
  • the bus 104 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. Wait.
  • PCI Peripheral Component Interconnect
  • EISA Extended Industry Standard Architecture
  • Wait The bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in FIG. 10, but it does not mean that there is only one bus or one type of bus.
  • FIG. 11 is a schematic structural diagram of another data transmission apparatus involved in the foregoing embodiment, which may be used to perform the function of access network device behavior in the foregoing method embodiment, and the apparatus may include: a processing module 112 and Communication module 113.
  • the physical device corresponding to the processing module 112 may be a process
  • the physical device corresponding to the communication module 113 may be a transceiver
  • the device may further include a storage module 111 for storing program codes and data of the access network device.
  • the access network device may be the access network device shown in FIG.
  • the access network device includes a processor 122, a transceiver 123, a memory 121, and a bus 124.
  • the transceiver 123, the processor 122, and the memory 121 are connected to each other through a bus 124.
  • the bus 124 may be a peripheral component interconnect standard PCI bus or an extended industry standard structure EISA bus.
  • the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 12, but it does not mean that there is only one bus or one type of bus.
  • FIG. 13 is a schematic diagram of a possible structure of a base station involved in the foregoing embodiment, for performing the function of a base station in the foregoing method embodiment, where the base station may include: a sending module 132 and a receiving module 133.
  • the physical device corresponding to the sending module 132 and the receiving module 133 may be a transceiver.
  • the base station may further include a storage module 131 for storing program codes and data of the base station.
  • the sending module 132 and the receiving module 133 may be a transceiver, a transceiver circuit, a communication interface, or the like.
  • the storage module 133 can be a memory.
  • the base station involved in the embodiment of the present invention may be the base station shown in FIG.
  • the base station includes a processor 142, a transceiver 143, a memory 141, and a bus 144.
  • the transceiver 143 and the memory 141 are mutually connected by a bus 144;
  • the processor 142 is used for controlling and managing the action of the base station, and
  • the bus 144 may be a peripheral component interconnect standard PCI bus or an extended industry standard structure EISA total Line and so on.
  • the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 14, but it does not mean that there is only one bus or one type of bus.
  • FIG. 15 is a schematic diagram showing a possible structure of a terminal device involved in the foregoing embodiment, which may be used to perform the function of the terminal device in the foregoing method embodiment.
  • the terminal device may include: a receiving module 152 and a sending module 153.
  • the physical device corresponding to the receiving module 152 and the sending module 153 may be a transceiver.
  • the terminal device may further include a storage module 151 for storing program codes and data of the terminal device.
  • the receiving module 152 and the sending module 153 may be a transceiver, a transceiver circuit, a communication interface, or the like.
  • the storage module 151 can be a memory.
  • the terminal device When the receiving module 152 and the sending module 153 are transceivers, and the storage module 151 is a memory, the terminal device according to the embodiment of the present invention may be the terminal device shown in FIG.
  • the terminal device includes a processor 162, a transceiver 163, a memory 161, and a bus 164.
  • the transceiver 163 and the memory 161 are connected to each other through a bus 164.
  • the processor 142 is configured to control and manage the actions of the terminal device.
  • the bus 164 may be a peripheral component interconnect standard PCI bus or an extended industry standard structure EISA bus.
  • the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 16, but it does not mean that there is only one bus or one type of bus.
  • the steps of a method or algorithm described in connection with the present disclosure may be implemented in a hardware, or may be implemented by a processor executing software instructions.
  • the software instructions may be composed of corresponding software modules, which may be stored in a random access memory (RAM), a flash memory, a read only memory (ROM), an erasable programmable read only memory ( Erasable Programmable ROM (EPROM), electrically erasable programmable read only memory (EEPROM), registers, hard disk, removable hard disk, compact disk read only (CD-ROM) or any other form of storage medium known in the art.
  • An exemplary storage medium is coupled to the processor to enable the processor to read information from, and write information to, the storage medium.
  • the storage medium can also be an integral part of the processor.
  • the processor and the storage medium can be located in an ASIC. Additionally, the ASIC can be located in a core network interface device.
  • the processor and the storage medium may also exist as discrete components in the core network interface device.
  • the functions described herein can be implemented in hardware, software, firmware, or any combination thereof.
  • the functions may be stored in a computer readable medium or transmitted as one or more instructions or code on a computer readable medium.
  • Computer readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one location to another.
  • a storage medium may be any available media that can be accessed by a general purpose or special purpose computer.

Landscapes

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

Abstract

本发明实施例提供一种多播业务的发送方法和设备，涉及通信领域，能够提升NB-IoT的多播业务的传输成功率，减少网络资源的浪费。其方法为：核心网设备确定待传输的多播业务的覆盖要求；核心网设备向接入网设备发送覆盖要求，覆盖要求用于确定接入网设备向终端设备发送多播业务的覆盖等级或传输参数；或基站在无线链路层控制协议RLC层向终端设备发送一次或多次多播业务的全部无线链路层控制协议数据控制单元RLC PDU或部分RLC PDU；基站接收终端设备发送的反馈信息，反馈信息用于向基站指示未成功接收的RLC PDU；基站向终端设备重传未成功接收的RLC PDU。本发明实施例用于多播业务的传输。

Description

一种多播业务的发送方法和设备 技术领域
本发明涉及通信领域，尤其涉及一种多播业务的发送方法和设备。
背景技术
目前第三代合作伙伴计划(3rd Generation Partnership Project，3GPP)标准基于蜂窝网络，通过设计新的空口，并利用窄带技术的特点承载物联网(Internet of Things，IoT)业务，这一类IoT被称为窄带物联网(Narrow Band-Internet of Things，NB-IoT)。与传统的蜂窝网络相比，NB-IoT网络的业务产生的数据包更小，数据传输周期长，且NB-IoT基站下终端设备的成本低，一个NB-IoT基站下可能存在大量终端设备设备，以实现终端设备的海量部署。
NB-IoT需要基于长期演进(Long Term Evolution，LTE)的单小区点对多点(Single Cell-Point To Multipoint，SC-PTM)技术来设计多播传输方案，以节省网络进行软件升级等具有多播特性业务的资源开销。基于上述NB-IoT网络业务和终端设备的特点，和LTE相比，在NB-IoT中，无线接入网的多播传输针对网际协议(User Internet Protocol，IP)数据包的可靠性和效率更难保证。一方面，这是由于多播业务是针对多个终端设备的，基站并不知晓终端设备的业务订阅信息，因此，如果直接由基站确定传输参数，可能会导致基站使用的覆盖等级和终端设备的实际情况不匹配。例如基站选取的覆盖等级过低，当小区中存在覆盖较差的终端设备时，覆盖较差的终端设备的多播传输成功率较低，使得基站需要向终端设备再次发送业务数据，而覆盖等级较差的终端设备本身单播消耗的资源也较大，使得整体资源消耗较大；由于覆盖等级高时的多播业务的传输会消耗大量的资源，若基站选取的覆盖等级较高，小区中实际订阅多播业务的终端设备覆盖本身较好时，将会导致资源的大量浪 费。另一方面，NB-IoT采用较低的调制编码策略(Modulation and Coding Scheme，MCS)，在物理层使用很小的传输块大小(Transport Block Size，TBS)，以降低终端设备成本，因此，对于同一个需要进行多播的传输层或网络层数据包，比如IP数据包，NB-IoT需要在物理下行共享信道(Physical Downlink Shared Channel，PDSCH)上使用更多的传输块(Transport Block，TB)来进行承载，若由于一个或几个TB的传输错误，就会导致整个IP数据包的重传，这样就会导致该IP数据包中原本被接收正确的TB也要被重传，造成网络资源的浪费。
发明内容
本发明实施例提供一种多播业务的发送方法和设备，能够提升NB-IoT的多播业务的传输成功率，减少网络资源的浪费。
第一方面，提供一种多播业务的发送方法，包括：核心网设备确定待传输的多播业务的覆盖要求；核心网设备向接入网设备发送覆盖要求，覆盖要求用于确定接入网设备向终端设备发送多播业务的覆盖等级或传输参数。不同的覆盖要求可以对应不同的覆盖等级或传输参数，由此，接入网设备可以根据从核心网接收到的覆盖要求确定本次多播业务传输实际使用的覆盖等级或传输参数，避免了基站自己选择覆盖等级或传输参数不合适带来的传输成功率低和资源浪费的问题。
在一种可能的设计中，传输参数包括多播业务对应的覆盖等级的索引或多播业务在物理层的控制信道或共享信道上的重复发送次数。不同的覆盖等级可以对应不同的传输参数。重复发送次数例如可以为256、512等，当多播业务重复发送多次时可提升多播业务的接收成功率。
在一种可能的设计中，核心网设备包括广播多播服务中心BM-SC；核心网设备确定待传输多播业务的覆盖要求包括：BM-SC 根据第三方服务器提供的多播业务的业务类型与多播业务的覆盖要求的对应关系确定多播业务的覆盖要求；或BM-SC根据第三方服务器提供的多播业务的业务类型，和BM-SC预配置的多播业务的业务类型与多播业务的覆盖要求的对应关系确定多播业务的覆盖要求。即核心网设备可以预配置业务类型与多播业务的覆盖要求的对应关系，也可以是第三方服务器向核心网设备提供业务类型与多播业务的覆盖要求的对应关系，例如路灯的覆盖较好，路灯软件升级业务的覆盖等级可以较低，地下室水电表的覆盖较差，水电表升级业务的覆盖等级可以较高。
在一种可能的设计中，核心网设备包括BM-SC，接入网设备包括基站；核心网设备向接入网设备发送覆盖要求包括：BM-SC通过移动性管理实体和MCE向基站发送覆盖要求，这样可使得基站根据从核心网收到的覆盖要求确定覆盖等级或传输参数，以避免基站自己选择覆盖等级或传输参数不当带来的传输成功率低和资源浪费的问题。
在一种可能的设计中，核心网设备包括归属用户服务器HSS，接入网设备包括基站；核心网设备向接入网设备发送覆盖要求包括：HSS通过移动性管理实体和MCE向基站发送覆盖要求。这样通过移动性管理实体和HSS交互，获取多播业务或多播业务提供者的覆盖等级使用权限信息，并确定覆盖要求通过MCE发送给基站，可使得基站根据从核心网收到的覆盖要求确定覆盖等级或传输参数，以避免基站自己选择覆盖等级或传输参数不当带来的传输成功率低和资源浪费的问题。
第二方面，提供一种多播业务的发送方法，包括：接入网设备接收核心网设备发送的覆盖要求；接入网设备根据覆盖要求确定接入网设备向终端设备发送多播业务的覆盖等级或传输参数；接入网设备根据覆盖等级或传输参数向终端设备发送多播业务。由此，接入网设备可以根据从核心网接收到的覆盖要求确定本次多播业务传 输实际使用的覆盖等级或传输参数，避免了基站自己选择覆盖等级或传输参数不合适带来的传输成功率低和资源浪费的问题。
在一种可能的设计中，传输参数包括多播业务对应的覆盖等级的索引或多播业务在物理层的控制信道或共享信道上的重复发送次数。
第三方面，提供一种多播业务的发送方法，包括：基站在无线链路层控制协议RLC层向终端设备发送一次或多次多播业务的全部无线链路层控制协议数据控制单元RLC PDU或部分RLC PDU；基站接收终端设备发送的反馈信息，反馈信息用于向基站指示未成功接收的RLC PDU；基站向终端设备重传未成功接收的RLC PDU。这样，在多播业务的全部RLC PDU或部分RLC PDU传输完成后，基站可根据终端设备的反馈信息向终端设备单播重传未接收成功的RLC PDU，可以提高基站侧的IP数据包的传输成功率，也可以避免由于少部分TB传输错误造成整个IP数据包进行重传导致的网络资源的浪费。
在一种可能的设计中，基站在RLC层向终端设备发送一次或多次多播业务的全部RLC PDU或部分RLC PDU之前，方法还包括：基站向终端设备发送配置信息，配置信息包括多播业务的全部RLC PDU或部分RLC PDU在RLC层的重复发送次数、第一指示信息和第一定时器中的至少一个，第一指示信息用于指示全部RLC PDU或部分RLC PDU是否支持终端设备在RLC层反馈和单播重传未接收成功的RLC PDU、第一定时器用于指示基站在预定时间内接收反馈信息的时长。重复发送次数即基站向终端设备多次发送全部RLC PDU或部分RLC PDU的次数。基站向终端设备发送的该配置信息针对不同的多播业务可以都相同，也可以是针对每一个多播业务使用一套配置信息。基站在预定时间内接收反馈信息的时长也即基站缓存全部RLC PDU或部分RLC PDU的时长，以便在预定时间内向终端设备重传未接收成功的RLC PDU。
在一种可能的设计中，当配置信息包括第一定时器时，每部分RLC PDU对应一个第一定时器，基站在RLC层向终端设备发送一次或多次多播业务的部分RLC PDU包括：基站在RLC层向终端设备发送一次或多次任一部分RLC PDU，并经过第一定时器时长后继续向终端设备发送一次或多次下一部分RLC PDU。这样，基站可不需要在发送全部RLC PDU后缓存全部RLC PDU，终端设备也可不需要再接收全部RLC PDU后缓存全部RLC PDU，使得基站和终端设备的存储成本降低。
在一种可能的设计中，每个RLC PDU头中包括第一字段，第一字段用于指示当前发送的RLC PDU为第N次重复发送，N为正整数，或第一字段用于指示当前发送的RLC PDU是否为最后一次重复发送；或RLC PDU的物理下行控制信道PDCCH所传输的下行控制信息中包括用于指示当前发送的RLC PDU是否为最后一次发送的指示信息。这样对于终端设备来说，如果终端设备在成功接收某一次全部RLC PDU或部分RLC PDU时，如果终端再接收到下一次发送的RLC PDU时，RLC PDU头中显示还是前一次发送的全部RLC PDU或部分RLC PDU的重复发送，那么终端可以等一段时间后再继续接收基站最后一次重复发送的全部RLC PDU或部分RLC PDU，从而达到节省电量的效果。
在一种可能的设计中，基站传输的最后一个RLC PDU中包括用于指示多播业务的所有RLC PDU发送完成的指示信息，例如可以在RLC PDU中预留所有重复完成的指示位，在最后一次传输的最后一个RLC PDU中指示全部RLC PDU发送完成，以便终端设备获知多播业务重复发送完毕；或，基站每次重复发送完多播业务的所有RLC PDU中的最后一个RLC PDU中包括用于指示多播业务的所有RLC PDU第N次发送完成的指示信息，以便UE可以结合配置信息中的重复发送次数判断全部RLC PDU是否发送完成。
在一种可能的设计中，基站向终端设备发送配置信息包括：基 站向终端设备广播***信息，***信息包括配置信息；或基站在多媒体广播多播服务MBMS控制信道SC-MCCH中向终端设备发送配置信息；或基站在SC-MCCH的物理下行控制信道PDCCH中向终端设备发送配置信息；或基站在MBMS业务信道SC-MCCH的PDCCH中向终端设备发送配置信息。
第四方面，提供一种多播业务的发送方法，包括：终端设备接收基站在无线链路层控制协议RLC层一次或多次发送的多播业务的全部无线链路层控制协议数据控制单元RLC PDU或部分RLC PDU；终端设备向基站发送反馈信息，反馈信息用于向基站指示未成功接收的RLC PDU；终端设备接收基站重传的未成功接收的RLC PDU。在多播业务发送完成后，在基站侧进行RLC层的单播重传，一方面，可以提高基站侧的UDP/IP数据包的传输成功率，另一方面也避免了因为少部分的TB传输错误导致整个UDP/IP数据包进行重传而导致的网络资源浪费的问题。
在一种可能的设计中，在终端设备接收基站在RLC层一次或多次发送的多播业务的全部RLC PDU或部分RLC PDU之前，方法还包括：终端设备接收基站发送的配置信息，配置信息包括多播业务的全部RLC PDU或部分RLC PDU在RLC层的重复发送次数、第一指示信息和第一定时器中的至少一个，第一指示信息用于指示全部RLC PDU或部分RLC PDU是否支持终端设备在RLC层反馈和单播重传未接收成功的RLC PDU，第一定时器用于指示基站在预定时间内接收反馈信息的时长。
在一种可能的设计中，终端设备接收基站在RLC层一次或多次发送的多播业务的部分RLC PDU包括：终端设备接收完基站在RLC层一次或多次发送的多播业务的任一部分RLC PDU，并经过第二定时器的时长后，接收基站一次或多次发送的下一部分RLC PDU，第二定时器的时长与第一定时器的时长相同。
在一种可能的设计中，每个RLC PDU头中包括第一字段，第一 字段用于指示当前发送的RLC PDU为第N次重复发送，N为大于或等于1的正整数，或第一字段用于指示当前发送的RLC PDU是否为最后一次重复发送；或RLC PDU的物理下行控制信道PDCCH所传输的下行控制信息中包括用于指示当前发送的RLC PDU是否为最后一次重复发送的指示信息。
在一种可能的设计中，终端设备接收到的最后一个RLC PDU中包括用于指示多播业务的全部RLC PDU发送完成的指示信息；或终端设备每次重复接收到的多播业务的全部RLC PDU中的最后一个RLC PDU包括用于指示多播业务的所有RLC PDU第N次发送完成的指示信息。
在一种可能的设计中，终端设备接收基站发送的配置信息包括：终端设备接收基站广播的***信息，***信息包括配置信息；或终端设备接收基站在多媒体广播多播服务MBMS控制信道SC-MCCH中发送的配置信息；或终端设备接收基站在SC-MCCH的物理下行控制信道PDCCH中发送的配置信息；或终端设备接收基站在MBMS业务信道SC-MCCH的PDCCH中发送的配置信息。
第五方面，提供一种核心网设备，包括：处理模块，用于确定待传输的多播业务的覆盖要求；通信模块，用于向接入网设备发送处理模块确定的覆盖要求，覆盖要求用于确定接入网设备向终端设备发送多播业务的覆盖等级或传输参数。
在一种可能的设计中，传输参数包括多播业务对应的覆盖等级的索引或多播业务在物理层的控制信道或共享信道上的重复发送次数。
在一种可能的设计中，处理模块具体用于根据第三方服务器提供的多播业务的业务类型与多播业务的覆盖要求的对应关系确定多播业务的覆盖要求；或根据第三方服务器提供的多播业务的业务类型，和BM-SC预配置的多播业务的业务类型与多播业务的覆盖要求的对应关系确定多播业务的覆盖要求。
在一种可能的设计中，通信模块具体用于通过移动性管理实体和MCE向基站发送处理模块确定的覆盖要求。
在一种可能的设计中，通信模块具体用于通过移动性管理实体和MCE向基站发送处理模块确定的覆盖要求。
在一种可能的设计中，接收模块，用于接收核心网设备发送的覆盖要求；处理模块，用于根据接收模块所接收的覆盖要求确定接入网设备向终端设备发送多播业务的覆盖等级或传输参数；通信模块，用于根据处理模块确定的覆盖等级或传输参数向终端设备发送多播业务。
在一种可能的设计中，传输参数包括多播业务对应的覆盖等级的索引或多播业务在物理层的控制信道或共享信道上的重复发送次数。
第六方面，提供一种接入网设备，包括：接收模块，用于接收核心网设备发送的覆盖要求；处理模块，用于根据接收模块所接收的覆盖要求确定接入网设备向终端设备发送多播业务的覆盖等级或传输参数；通信模块，用于根据处理模块确定的覆盖等级或传输参数向终端设备发送多播业务。
在一种可能的设计中，传输参数包括多播业务对应的覆盖等级的索引或多播业务在物理层的控制信道或共享信道上的重复发送次数。
第七方面，提供一种基站，包括：发送模块，用于在无线链路层控制协议RLC层向终端设备发送一次或多次多播业务的全部无线链路层控制协议数据控制单元RLC PDU或部分RLC PDU；接收模块，用于接收终端设备发送的反馈信息，反馈信息用于向基站指示通信模块发送的、且未成功接收的RLC PDU；发送模块，还用于向终端设备重传未成功接收的RLC PDU。
在一种可能的设计中，发送模块还用于：向终端设备发送配置 信息，配置信息包括多播业务的全部RLC PDU或部分RLC PDU在RLC层的重复发送次数、第一指示信息和第一定时器中的至少一个，第一指示信息用于指示全部RLC PDU或部分RLC PDU是否支持终端设备在RLC层反馈和单播重传未接收成功的RLC PDU、第一定时器用于指示基站在预定时间内接收反馈信息的时长。
在一种可能的设计中，发送模块用于：在RLC层向终端设备发送一次或多次任一部分RLC PDU，并经过第一定时器时长后继续向终端设备发送一次或多次下一部分RLC PDU。
在一种可能的设计中，每个RLC PDU头中包括第一字段，第一字段用于指示当前发送的RLC PDU为第N次重复发送，N为大于或等于1的正整数，或第一字段用于指示当前发送的RLC PDU是否为最后一次重复发送；或RLC PDU的物理下行控制信道PDCCH所传输的下行控制信息中包括用于指示当前发送的RLC PDU是否为最后一次发送的指示信息。
在一种可能的设计中，发送模块用于发送全部RLC PDU时所传输的最后一个RLC PDU中包括用于指示多播业务的全部RLC PDU发送完成的指示信息；或，通信模块用于发送全部RLC PDU时每次重复发送完多播业务的全部RLC PDU中的最后一个RLC PDU中包括用于指示多播业务的全部RLC PDU第N次发送完成的指示信息。
在一种可能的设计中，发送模块用于：向终端设备广播***信息，***信息包括配置信息；或在多媒体广播多播服务MBMS控制信道SC-MCCH中向终端设备发送配置信息；或在SC-MCCH的物理下行控制信道PDCCH中向终端设备发送配置信息；或在MBMS业务信道SC-MCCH的PDCCH中向终端设备发送配置信息。
第八方面，提供一种终端设备，包括：接收模块，用于接收基站在无线链路层控制协议RLC层一次或多次发送的多播业务的全部无线链路层控制协议数据控制单元RLC PDU或部分RLC PDU；发送模块，用于向基站发送反馈信息，反馈信息用于向基站指示通信 模块发送的、且未成功接收的RLC PDU；接收模块，还用于接收基站重传的未成功接收的RLC PDU。
在一种可能的设计中，接收模块还用于：接收基站发送的配置信息，配置信息包括多播业务的全部RLC PDU或部分RLC PDU在RLC层的重复发送次数、第一指示信息和第一定时器中的至少一个，第一指示信息用于指示全部RLC PDU或部分RLC PDU是否支持终端设备在RLC层反馈和单播重传未接收成功的RLC PDU、第一定时器用于指示基站在预定时间内接收反馈信息的时长。
在一种可能的设计中，接收模块用于：接收完基站在RLC层一次或多次发送的多播业务的任一部分RLC PDU，并经过第二定时器的时长后，接收基站一次或多次发送的下一部分RLC PDU，第二定时器的时长与第一定时器的时长相同。
在一种可能的设计中，每个RLC PDU头中包括第一字段，第一字段用于指示当前发送的RLC PDU为第N次重复发送，N为大于或等于1的正整数，或第一字段用于指示当前发送的RLC PDU是否为最后一次重复发送；或RLC PDU的物理下行控制信道PDCCH所传输的下行控制信息中包括用于指示当前发送的RLC PDU是否为最后一次重复发送的指示信息。
在一种可能的设计中，接收模块用于接收全部RLC PDU接收到的最后一个RLC PDU中包括用于指示多播业务的全部RLC PDU发送完成的指示信息；或接收模块用于接收全部RLC PDU每次重复接收到的多播业务的全部RLC PDU中的最后一个RLC PDU包括用于指示多播业务的全部RLC PDU第N次发送完成的指示信息。
在一种可能的设计中，接收模块用于：接收基站广播的***信息，***信息包括配置信息；或接收基站在多媒体广播多播服务MBMS控制信道SC-MCCH中发送的配置信息；或接收基站在SC-MCCH的物理下行控制信道PDCCH中发送的配置信息；或接收基站在MBMS业务信道SC-MCCH的PDCCH中发送的配置信息。
第九方面，提供一种核心网设备，包括：处理器，用于确定待传输的多播业务的覆盖要求；收发器，用于向接入网设备发送从处理器获取的覆盖要求，覆盖要求用于确定接入网设备向终端设备发送多播业务的覆盖等级或传输参数。
在一种可能的设计中，传输参数包括多播业务对应的覆盖等级的索引或多播业务在物理层的控制信道或共享信道上的重复发送次数。
在一种可能的设计中，处理器用于根据第三方服务器提供的多播业务的业务类型与多播业务的覆盖要求的对应关系确定多播业务的覆盖要求；或根据第三方服务器提供的多播业务的业务类型，和BM-SC预配置的多播业务的业务类型与多播业务的覆盖要求的对应关系确定多播业务的覆盖要求。
在一种可能的设计中，收发器用于：通过移动性管理实体和MCE向基站发送从处理器获取的覆盖要求。
在一种可能的设计中，收发器用于：通过移动性管理实体和MCE向基站发送从处理器获取的覆盖要求。
第十方面，提供一种接入网设备，包括：接收器，用于接收核心网设备发送的覆盖要求；处理器，用于根据从接收器获取的覆盖要求确定接入网设备向终端设备发送多播业务的覆盖等级或传输参数；接入网设备根据覆盖等级或传输参数向终端设备发送多播业务。
在一种可能的设计中，传输参数包括多播业务对应的覆盖等级的索引或多播业务在物理层的控制信道或共享信道上的重复发送次数。
第十一方面，提供一种基站，包括：收发器，用于在无线链路层控制协议RLC层向终端设备发送一次或多次多播业务的全部无线链路层控制协议数据控制单元RLC PDU或部分RLC PDU；接收器，用于接收终端设备发送的反馈信息，反馈信息用于向基站指示未成 功接收的RLC PDU；收发器，还用于向终端设备重传未成功接收的RLC PDU。
在一种可能的设计中，收发器，还用于向终端设备发送配置信息，配置信息包括多播业务的全部RLC PDU或部分RLC PDU在RLC层的重复发送次数、第一指示信息和第一定时器中的至少一个，第一指示信息用于指示全部RLC PDU或部分RLC PDU是否支持终端设备在RLC层反馈和单播重传未接收成功的RLC PDU、第一定时器用于指示基站在预定时间内接收反馈信息的时长。
在一种可能的设计中，当配置信息包括第一定时器时，每部分RLC PDU对应一个第一定时器，收发器用于在RLC层向终端设备发送一次或多次任一部分RLC PDU，并经过第一定时器时长后继续向终端设备发送一次或多次下一部分RLC PDU。
在一种可能的设计中，每个RLC PDU头中包括第一字段，第一字段用于指示当前发送的RLC PDU为第N次重复发送，N为正整数，或第一字段用于指示当前发送的RLC PDU是否为最后一次重复发送；或RLC PDU的物理下行控制信道PDCCH所传输的下行控制信息中包括用于指示当前发送的RLC PDU是否为最后一次发送的指示信息。
在一种可能的设计中，收发器用于传输的最后一个RLC PDU中包括用于指示多播业务的所有RLC PDU发送完成的指示信息；或，收发器用于每次重复发送完多播业务的所有RLC PDU中的最后一个RLC PDU中包括用于指示多播业务的所有RLC PDU第N次发送完成的指示信息。
在一种可能的设计中，收发器用于向终端设备广播***信息，***信息包括配置信息；或基站在多媒体广播多播服务MBMS控制信道SC-MCCH中向终端设备发送配置信息；或基站在SC-MCCH的物理下行控制信道PDCCH中向终端设备发送配置信息；或基站在MBMS业务信道SC-MCCH的PDCCH中向终端设备发送配置信息。
第十二方面，提供一种终端设备，包括：接收器，用于接收基站在无线链路层控制协议RLC层一次或多次发送的多播业务的全部无线链路层控制协议数据控制单元RLC PDU或部分RLC PDU；收发器，用于向基站发送反馈信息，反馈信息用于向基站指示未成功接收的RLC PDU；接收器用于接收基站重传的未成功接收的RLC PDU。
在一种可能的设计中，在终端设备接收基站在RLC层一次或多次发送的多播业务的全部RLC PDU或部分RLC PDU之前，接收器还用于：接收基站发送的配置信息，配置信息包括多播业务的全部RLC PDU或部分RLC PDU在RLC层的重复发送次数、第一指示信息和第一定时器中的至少一个，第一指示信息用于指示全部RLC PDU或部分RLC PDU是否支持终端设备在RLC层反馈和单播重传未接收成功的RLC PDU，第一定时器用于指示基站在预定时间内接收反馈信息的时长。
在一种可能的设计中，接收器用于：接收完基站在RLC层一次或多次发送的多播业务的任一部分RLC PDU，并经过第二定时器的时长后，接收基站一次或多次发送的下一部分RLC PDU，第二定时器的时长与第一定时器的时长相同。
在一种可能的设计中，收发器用于发送的每个RLC PDU头中包括第一字段，第一字段用于指示当前发送的RLC PDU为第N次重复发送，N为大于或等于1的正整数，或第一字段用于指示当前发送的RLC PDU是否为最后一次重复发送；或RLC PDU的物理下行控制信道PDCCH所传输的下行控制信息中包括用于指示当前发送的RLC PDU是否为最后一次重复发送的指示信息。
在一种可能的设计中，接收器用于接收到的最后一个RLC PDU中包括用于指示多播业务的全部RLC PDU发送完成的指示信息；或接收器用于每次重复接收到的多播业务的全部RLC PDU中的最后一个RLC PDU包括用于指示多播业务的所有RLC PDU第N次发送 完成的指示信息。
在一种可能的设计中，接收器用于：接收基站广播的***信息，***信息包括配置信息；或接收器用于接收基站在多媒体广播多播服务MBMS控制信道SC-MCCH中发送的配置信息；或接收器用于接收基站在SC-MCCH的物理下行控制信道PDCCH中发送的配置信息；或接收器用于接收基站在MBMS业务信道SC-MCCH的PDCCH中发送的配置信息。
由此，接入网设备的基站可以根据从核心网接收到的覆盖要求确定本次多播业务传输实际使用的覆盖等级或传输参数，避免了基站自己选择覆盖等级或传输参数不合适带来的传输成功率低和资源浪费的问题；在多播业务发送完成后，基站可根据终端设备的反馈信息在基站侧进行RLC层的单播重传，一方面，可以提高基站侧的UDP/IP数据包的传输成功率，另一方面也避免了因为少部分的TB传输错误导致整个UDP/IP数据包进行重传而导致的网络资源浪费的问题。
附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1为本发明实施例提供的一种网络结构示意图；
图2为本发明实施例提供的一种多播业务的发送方法的流程示意图；
图3为本发明实施例提供的一种多播业务的发送方法的流程示意图；
图4为本发明实施例提供的一种多播业务的发送方法的流程示意图；
图5为本发明实施例提供的一种多播业务的发送方法的流程示意图；
图6为本发明实施例提供的一种多播业务的发送方法的流程示意图；
图7为本发明实施例提供的一种多播业务的全部RLC PDU多次发送的信号流程图；
图8为本发明实施例提供的一种多播业务的部分RLC PDU多次发送的信号流程图；
图9为本发明实施例提供的一种核心网设备的结构示意图；
图10为本发明实施例提供的一种核心网设备的结构示意图；
图11为本发明实施例提供的一种接入网设备的结构示意图；
图12为本发明实施例提供的一种接入网设备的结构示意图；
图13为本发明实施例提供的一种基站的结构示意图；
图14为本发明实施例提供的一种基站的结构示意图；
图15为本发明实施例提供的一种终端设备的结构示意图；
图16为本发明实施例提供的一种终端设备的结构示意图。
具体实施方式
下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本发明一部分实施例，而不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本发明保护的范围。
本发明实施例可适用于要求终端设备低复杂度、低功耗的无线 通信***，如IoT通信***等，例如可适用于NB-IoT通信***中的多播场景。
如图1所示，本发明实施例的网络架构可以包括终端设备、接入网设备和核心网设备。终端设备可以为用户设备(User Equipment，UE)，接入网可以为演进的通用移动通信***(Universal Mobile Telecommunications System，UMTS)陆地无线接入网(Evolved UMTS Terrestrial Radio Access Network，E-UTRAN)或UTRAN，包括演进型基站(eNodeB，eNB)，核心网设备可以包括移动管理实体(Mobility Management Entity，MME)、广播多播服务中心(Broadcast-multicast Service Centre，BM-SC)、多媒体广播多播服务(Multimedia Broadcast Multicast Service，MBMS)和MBMS协调实体(MBMS Coordination Entity，MCE)等。其中，BM-SC负责管理MBMS承载，激活/释放业务的临时临时移动组标识(Temporaty Mobile Group Identity，TMGI)等；MCE可用于对于多播业务决定使用多播广播单频网(Multicast-Broadcast Single Frequency Network，MBSFN)模式还是SC-PTM模式。
本发明实施例一方面针对现有技术中的基站难以确定合理的发送多播业务的覆盖等级，使得传输可靠性降低带来的资源浪费的问题，本发明从BM-SC到基站的信令传输过程中，通过核心网确定多播业务的覆盖等级或传输参数，并随相关信令发送给基站，以便基站能够使用合理的覆盖等级或传输参数发送多播业务，保证多播业务在覆盖增强的基础上减少多播资源的浪费；
本发明实施例另一方面针对NB-IoT传输IP数据包时，若传输一个或几个TB传输不成功，会导致整个IP数据包重传带来的额外的重传和接收开销的问题，本发明实施例在接入网设备发送IP数据包时，在RLC层将IP数据包分段为若干个RLC PDU，在发送该若干个RLC PDU后，接收终端设备的反馈信息，并向终端设备重传未接收成功的RLC PDU，不需要重传整个IP数据包，以减少传输错 误后单播重传带来的资源开销。
下面针对现有技术中的基站难以确定合理的发送多播业务的覆盖等级，使得传输可靠性降低带来的资源浪费的问题，本发明实施例提供一种多播业务的发送方法，如图2所示，包括：
201、核心网设备确定待传输的多播业务的覆盖要求。
例如可以通过核心网中的BM-SC与第三方服务器的交互信息中本次传输业务的特点确定待传输的多播业务的覆盖要求。该覆盖要求用于表征基站向终端设备发送多播业务时的覆盖增强程度。
202、核心网设备向接入网设备发送覆盖要求。
BM-SC可以通过移动性管理实体和MCE向基站发送覆盖要求。该覆盖要求可以为覆盖等级的索引或覆盖等级的索引范围。
203、接入网设备根据覆盖要求确定向终端设备发送多播业务的覆盖等级或传输参数。
基站在接收到覆盖要求后，可以根据该覆盖要求对应的覆盖等级的索引或覆盖等级的索引范围确定此次向终端设备发送多播业务的覆盖等级或传输参数。覆盖等级的索引可以用0,1,2……表示，不同的覆盖等级的索引对应不同的覆盖等级或传输参数，不同的覆盖等级对应不同的传输参数，传输参数可以包括多播业务在物理层的控制信道或共享信道上的重复发送次数，例如重复发送次数可以为256、512、1024等。
由此，接入网设备可以根据从核心网接收到的覆盖要求确定本次多播业务传输实际使用的覆盖等级或传输参数，避免了基站自己选择覆盖等级或传输参数不合适带来的传输成功率低和资源浪费的问题。
下面对上述实施例进一步进行说明。
本发明实施例提供一种多播业务的传输方法，如图3所示，包括:
301、BM-SC从第三方服务器获取多播业务，为该多播业务分配相应的会话标识和TMGI，并确定该多播业务的覆盖要求。
当第三方服务器下发多播业务时，将多播业务发送至核心网设备的BM-SC，BM-SC为该多播业务分配会话标识(Session ID)以及TMGI，以便将会话标识和TMGI发送给接收该多播业务的UE开始接收多播业务。同时，BM-SC可以根据第三方服务器提供的多播业务的业务类型与多播业务的覆盖要求的对应关系确定多播业务的覆盖要求；或，BM-SC可以根据第三方服务器提供的多播业务的业务类型，和BM-SC预配置的多播业务的业务类型与多播业务的覆盖要求的对应关系确定多播业务的覆盖要求。覆盖要求用于表征基站向终端设备发送多播业务时的覆盖增强程度，不同的覆盖要求对应不同的覆盖等级或传输参数。
示例性的，BM-SC可以根据和第三方服务器提供的本次业务的业务类型确定覆盖要求，例如由于路灯的覆盖较好，路灯软件升级业务的覆盖要求可以较低；由于地下室的覆盖较差，地下室的水电表软件升级业务的覆盖要求可以较高。也可以由运营商运维或网管***在BM-SC预先配置业务类型和覆盖要求的对应关系，这样BM-SC在从第三方服务器获取业务类型后，可以根据该预先配置的对应关系确定该多播业务的覆盖要求。
302、BM-SC以单播形式向UE发送多播业务的会话标识、TMGI以及业务的开始时间。
这样，UE可根据会话标识、TMGI以及业务的开始时间准备接收该多播业务。
303、在多播业务开始传输之前，BM-SC向MME发送会话开始请求消息，该会话开始请求消息包括针对该多播业务使用多播的小区列表以及覆盖要求。
该小区列表中包括接收该多播业务的基站的小区标识，以便该MME向该小区标识指示的基站发送该覆盖要求。覆盖要求可以用数 字或其他标识指示，不同的数据或标识指示不同的覆盖等级或传输参数。
304、MME向MCE发送MBMS会话开始请求消息，该MBMS会话开始请求消息包括针对该多播业务使用多播的小区列表以及覆盖要求。
305、MCE将包含覆盖要求和SC-PTM指示发送给小区列表对应的基站。
SC-PTM为单小区点对多点技术，用于实现多播业务的传输。当基站接收到SC-PTM指示时，基站根据覆盖要求确定覆盖等级或传输参数，并将接收到的业务以多播形式下发给UE。
306、基站根据覆盖要求确定向终端设备发送多播业务的覆盖等级或传输参数。
不同的覆盖要求对应不同的覆盖等级或传输参数，例如覆盖要求为0时，覆盖等级为0，对应的传输参数可以为多播业务在物理层的控制信道或共享信道上的重复发送次数，例如重复发送次数可以为256、512、1024等。可替换的，该传输参数也可以为重复传输次数的范围，例如该范围取值为[256,512]，基站可以根据不同的业务类型在该范围内取值，以便为该业务选取合适的重复传输次数，譬如路灯软件升级业务下路灯的覆盖较好，选取的重复传输次数可以较低，地下室水电表软件升级业务下水电表的覆盖较差，选取的重复传输次数可以较高。进而，基站可以通过***信息(System Information Block，SIB)20和单小区MBMS控制信道(SC-MBMS Control Channel，SC-MCCH)向UE下发参数配置，该参数配置中包括该重复传输次数，并通过单小区MBMS业务信道(SC-MBMS Traffic Channel，SC-MTCH)向UE发送多播业务。
由此，通过核心网的BM-SC在确定待传输多播业务的覆盖要求后，通过MME和MCE向基站发送覆盖要求，可使得基站根据收到的覆盖要求确定覆盖等级或传输参数，以避免基站自己选择覆盖等 级或传输参数不当带来的传输成功率低和资源浪费的问题。
针对现有技术中的基站难以确定合理的发送多播业务的覆盖等级，使得传输可靠性降低带来的资源浪费的问题，本发明实施例提供一种多播业务的发送方法，如图4所示，包括：
401、BM-SC从第三方服务器获取多播业务，并为该多播业务分配会话标识和TMGI。
当第三方服务器下发多播业务时，将多播业务发送至核心网设备的BM-SC，BM-SC为该多播业务分配会话标识Session ID以及TMGI，以便将会话标识和TMGI发送给接收该多播业务的UE开始接收多播业务。
402、BM-SC将多播业务的会话标识、TMGI和多播业务的开始时间以单播形式发送给UE。
403、在多播业务开始传输之前，BM-SC向MME发送会话开始请求消息，该会话开始请求消息包括针对该多播业务使用多播的小区列表。
404、MME向HSS发送请求消息，该请求消息包括多播业务信息，HSS向MME发送响应消息，响应消息包括多播业务或多播业务提供者的签约信息中的覆盖等级的使用授权信息。
多播业务信息中可以包括会话标识，TMGI或多播业务提供者的标识等，响应消息中可以包括HSS根据为该多播业务分配的TMGI的签约信息中的覆盖等级的使用授权信息，或响应消息中可以包括HSS根据多播业务提供者的签约信息中的覆盖等级的使用授权信息。该签约信息为多播业务或多播业务提供者在网络中注册时产生的，存储于HSS中，签约信息可以包括业务或业务提供者在网络中的覆盖等级的使用权限。
405、MME根据使用授权信息确定多播业务的覆盖要求，并向MCE发送MBMS会话开始请求消息，MBMS会话开始请求消息包 括多播业务的覆盖要求以及多播业务使用多播的小区列表。
MME可以根据预设的覆盖等级的使用权限与覆盖要求的对应关系确定该多播业务的覆盖要求，并将该多播业务的覆盖要求发送给MCE。小区列表中包括接收该多播业务的基站的小区标识，以便MCE根据该小区列表指示的基站发送该多播业务的覆盖要求。
406、MCE向基站发送SC-PTM指示和多播业务的覆盖要求。
407、基站根据多播业务的覆盖要求确定基站向UE发送该多播业务的覆盖等级或传输参数。
步骤407的实现方式可以参见上述步骤306，此处不再赘述。
由此，通过核心网的HSS向MME发送多播业务或多播业务提供者在网络中传输的覆盖等级的使用权限，使得MME根据该覆盖等级的使用权限确定多播业务的覆盖要求后，通过MCE向基站发送覆盖要求，可使得基站根据收到的覆盖要求确定覆盖等级或传输参数，以避免基站自己选择覆盖等级或传输参数不当带来的传输成功率低和资源浪费的问题。
下面针对现有技术中的NB-IoT传输IP数据包时，若传输一个或几个TB传输不成功，会导致整个IP数据包重传带来的额外的重传和接收开销的问题，本发明实施例提供一种多播业务的传输方法，如图5所示，包括：
501、基站在无线链路层控制协议RLC层，以多播形式向终端设备发送一次或多次多播业务的全部无线链路层控制协议数据控制单元RLC PDU或部分RLC PDU。
这里发送多次全部RLC PDU或部分RLC PDU可以理解为基站向终端设备重复发送N次全部RLC PDU或部分RLC PDU，N为正整数。部分RLC PDU为将IP数据包在RLC层进行分割和级联，形成若干个RLC PDU时，将该若干个RLC PDU分为若干个部分后每个部分包括的RLC PDU。
需要说明的是，终端设备在接收基站发送的多播业务时可以处理连接态，也可以处于空闲态。例如在NB-IoT中，终端可以处于空闲态接收多播业务。
502、终端设备向基站发送反馈信息，反馈信息用于向基站指示未成功接收的RLC PDU。
当终端设备接收完全部RLC PDU时，向基站反馈未成功接收的RLC PDU；或当终端设备接收完部分RLC PDU时，向基站反馈未成功接收的RLC PDU，以便基站再向终端设备继续发送下一部分RLC PDU。
503、基站向终端设备重传未成功接收的RLC PDU。
基站可以向终端设备以单播形式重传未成功接收的RLC PDU，也可以多个终端设备的反馈信息，以多播形式重传多个终端设备未成功接收到的RLC PDU，本申请不做限定。
这样，在多播业务的全部RLC PDU或部分RLC PDU传输完成后，基站可根据终端设备的反馈信息向终端设备重传未接收成功的RLC PDU，可以提高基站侧的IP数据包的传输成功率，也可以避免由于少部分TB传输错误造成整个IP数据包进行重传导致的网络资源的浪费。
下面对图5所示的实施例进行进步一说明。
本发明实施例提供一种多播业务的发送方法，如图6所示，包括；
601、基站向终端设备发送配置信息。
配置信息可以包括多播业务的全部RLC PDU或部分RLC PDU在RLC层的重复发送次数、第一指示信息和第一定时器中的至少一个，第一指示信息用于指示全部RLC PDU或部分RLC PDU是否支持终端设备在RLC层反馈和单播重传未接收成功的RLC PDU、第一定时器用于指示基站在预定时间内接收反馈信息的时长。
重复发送次数即基站向终端设备多次发送全部RLC PDU或部分RLC PDU的次数。基站向终端设备发送的该配置信息针对不同的多播业务可以都相同，也可以是针对每一个多播业务使用一套配置信息，本申请不做限定。
基站向终端设备发送配置信息可以包括：基站向终端设备广播***信息，***信息中包括该配置信息，例如基站在SC-PTM的专用***信息块(System Information Block，SIB)20中携带该配置信息发送给终端设备；或者，基站可以在MBMS控制信道SC-MCCH中向终端设备发送配置信息；或者，基站可以在MBMS业务信道SC-MCCH的物理下行控制信道(Physical Downlink Control Channel，PDCCH)中向终端设备发送配置信息，本申请不做限定。
602、基站在RLC层向终端设备发送一次或多次多播业务的全部RLC PDU或部分RLC PDU。
基站可以将多播业务的IP数据包在RLC层进行分割和级联，形成若干个RLC PDU，而后，基站可以在RLC层向终端设备发送一次全部RLC PDU，也可以在RLC层向终端设备发送一次若干个RLC PDU中的部分RLC PDU后，继续发送若干个RLC PDU中的下一部分RLC PDU；或者基站可以根据步骤601中的配置信息中的重复发送次数，在RLC层向终端设备重复发送IP数据包的全部RLC PDU或部分RLC PDU，这样可以提高RLC PDU的接收成功率，也即提高了基站侧提供的IP数据包的接收成功率。
当基站在RLC层向终端设备以多播形式发送多次全部RLC PDU时，一种可能的实现方式中，每个RLC PDU头中包括第一字段，第一字段用于指示当前发送的RLC PDU为第N次重复发送，即第一字段用于指示当前的重复次数为第1次、第2次，第3次……等；或者，第一字段用于指示当前发送的RLC PDU是否为最后一次重复发送，可以占用1比特；或者，发送RLC PDU的PDCCH所传输的下行控制信息中包括用于指示当前发送的RLC PDU是否为最 后一次重复发送的指示信息，可以占用1比特。这样对于终端设备来说，如果终端设备在成功接收某一次全部RLC PDU时，如果终端再接收到下一次发送的RLC PDU时，RLC PDU头中显示还是前一次发送的RLC PDU的重复发送，那么终端可以等一段时间后再继续接收基站最后一次重复发送的RLC PDU，从而达到节省电量的效果。
此外，当基站在RLC层向终端设备以多播形式发送多次全部RLC PDU时，在同一个RLC PDU的不同重复发送之间，支持重分段传输。例如，RLC PDU0第二次发送时，由于此时空口可能发生变化，物理层不能提供同样大小的TBS承载该RLC PDU0，基站可以对该RLC PDU0进行重分段，将原有的RLC PDU进一步拆分成若干个RLC分段PDU进行发送，也就是说，基站在重复发送任一RLC PDU时可以将任一RLC PDU重分段，得到至少一个RLC分段PDU，且每个RLC分段PDU携带和拆分之前的RLC PDU相同的序列号、该RLC分段PDU的子序号和用于指示RLC分段PDU是否为RLC PDU的最后一个分段的指示信息。
无论基站发送一次还是多次多播业务的IP数据包的全部RLC PDU时，基站最后一次重复的最后一个RLC PDU中可以包括用于指示多播业务的全部RLC PDU发送完成的指示信息，例如可以在RLC PDU中预留所有重复完成的指示位，在最后一次传输的最后一个RLC PDU中指示全部RLC PDU发送完成，以便终端设备获知多播业务重复发送完毕；或者，基站每次重复发送完多播业务的所有RLC PDU中的最后一个RLC PDU中包括用于指示多播业务的所有RLC PDU第N次发送完成的指示信息，以便UE可以结合配置信息中的重复发送次数判断全部RLC PDU是否发送完成。
当基站在RLC层向终端设备发送多播业务时，可以在RLC层将多播业务分为若干个部分，然后得到多个部分RLC PDU，对每个部分RLC PDU进行一次发送或多次发送，每部分RLC PDU发送的实现方式与基站发送全部RLC PDU类似，且在每部分RLC PDU中 的最后一个RLC PDU中携带该部分RLC PDU发送完成的指示信息。其中，分为若干个部分的粒度可以为：每个IP数据包、或RLC层的最大缓存、或RLC层的最大序号(Serial Number，SN)限制，也可以是基站灵活控制。
603、终端设备向基站发送反馈信息，反馈信息用于向基站指示为成功接收的RLC PDU。
当基站确定全部RLC PDU一次发送完成或多次发送完成后，对于基站来说，基站可以在第一定时器运行期间，缓存所有的RLC PDU，以在第一定时器运行期间接收终端设备发送的反馈信息，以便于向终端设备单播重传反馈信息指示的未成功接收的RLC PDU。
示例性的，若终端设备确定有RLC PDU未接收成功，则可以根据配置信息中的第一定时器的时长，在终端设备中启动运行第二定时器，第二定时器的时长与第一定时器的时长相同，终端设备可以在第二定时器的时长范围内发起随机接入过程，以向基站反馈未成功接收的RLC PDU，反馈信息中携带未成功接收的RLC PDU的信息，如SN号等。此外，终端设备在发起随机接入时，也可以在接入请求中携带一个新的原因值，以指示用于多播反馈。由于是多播传输业务，可能会有大量的终端设备进行反馈，当终端设备在[0-第二定时器时长]之间随机选择时间接入基站时，可以减轻网络拥塞。
此外，由于是多播传输，终端设备中第二定时器的启动，是由于终端设备识别了基站已经发送完多播业务的所有RLC PDU，但是，如果终端设备因为接收错误，例如未成功接收最后一个RLC PDU，则终端设备无法识别多播业务是否传输完成，也就不会触发反馈。于是，终端设备可以在每接收到一个RLC PDU后，启动或重启第三定时器，若第三定时器超时，终端设备还未接收到新的RLC PDU，可以认为此时出现网络异常，若终端设备处于空闲态，则终端设备可以直接发起随机接入处于连接态时进行反馈，以向基站获取新的RLC PDU。其中，第三定时器可以由基站进行配置，携带在配置信 息中。也即，配置信息还可以包括第三定时器，第三定时器用于终端设备在每接收到一个RLC PDU后在第三定时器的预定时间内还未接收到任意一个RLC PDU，则向基站发送反馈信息，以向基站指示未成功接收的RLC PDU。
604、基站向终端设备重传未成功接收的RLC PDU。
基站可以向终端设备以单播形式重传未成功接收的RLC PDU，也可以多个终端设备的反馈信息，以多播形式重传多个终端设备未成功接收到的RLC PDU，本申请不做限定。
当基站以单播形式重传任一RLC PDU时，多播发送和单播重传之间，也可以支持重分段。例如基站在单播重传RLC PDU0时，由于空口发生变化，物理层不能提供同样大小的TBS承载RLC PDU0，则基站在单播重传时将RLC PDU0进行重分段，将RLC PDU0拆分成若干个RLC分段PDU进行发送，与步骤602类似的，基站在单播重传任一RLC PDU时可以将任一RLC PDU重分段，得到至少一个RLC分段PDU，且每个RLC分段PDU携带和拆分之前的RLC PDU相同的序列号、该RLC分段PDU的子序号和用于指示RLC分段PDU是否为RLC PDU的最后一个分段的指示信息。
根据步骤601-步骤604的说明，假设基站向UE1～UEx发送配置信息后需发送多播业务，若该多播业务共N个RLC PDU，N个RLC PDU发送三次，第三次发送的第N个RLC PDU中携带发送完成指示，三次发送完成后，UE1和UE2有未成功接收的RLC PDU，则UE1和UE2可以发起随机接入，向基站发送反馈信息，如图7所示，假设UE1先于UE2向基站发起随机接入，则基站先向UE1单播重传UE1未成功接收的RLC PDU，后向UE2单播重传UE2未成功接收的RLC PDU。
如图8所示，假设基站在向UE1～UEx发送配置信息后，配置信息中的重复发送次数为3，以先重复发送第一部分RLC PDU1～a后，再继续发送第二部分RLC PDU a+1～b的方式进行说明，基站先向 UE1～UEx发送第一次RLC PDU1～a，再向UE1～UEx发送第二次RLC PDU1～a，再向UE1～UEx发送第三次RLC PDU1～a，第三次发送的RLC PDU1～a中的最后一个RLC PDU中携带重复发送完成指示，而后，UE1～UEx中有未成功接收RLC PDU的UE向基站发送反馈信息，基站再向有未成功接收RLC PDU的UE进行单播重传；而后，基站向UE1～UEx发送第一次RLC PDU a+1～b，再向UE1～UEx发送第二次RLC PDU a+1～b，再向UE1～UEx发送第三次RLC PDU a+1～b，第三次发送的RLC PDU a+1～b中的最后一个RLC PDU中携带重复发送完成指示，而后，UE1～UEx中有未成功接收RLC PDU的UE向基站发送反馈信息，基站再向有未成功接收RLC PDU的UE进行单播重传。
由此，本实施例通过多播业务在RLC层进行多次传输，可以提高RLC PDU的接收成功率，也即提高了基站侧提供的UDP/IP的数据包的接收成功率。同时，在多播业务发送完成后，在基站侧进行RLC层的单播重传，一方面，可以提高基站侧的UDP/IP数据包的传输成功率，另一方面也避免了因为少部分的TB传输错误导致整个UDP/IP数据包进行重传而导致的网络资源浪费的问题。进一步的，当基站向终端设备发送一次或多次全部RLC PDU时使得基站和UE需要缓存一次多播传输的全部RLC PDU，使得终端设备的存储成本增加时，基站可以向终端设备发送一次或多次部分RLC PDU，接收到反馈信息，并向终端设备单播重传未成功接收的RLC PDU后，基站再向终端设备发送下一部分RLC PDU，可降低基站和终端设备的存储成本。
上述主要从各个网元之间交互的角度对本发明实施例提供的方案进行了介绍。可以理解的是，各个网元，例如核心网设备、接入网设备和终端设备等为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本发明能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究 竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本发明的范围。
本发明实施例可以根据上述方法示例对核心网设备、接入网设备和终端设备等进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本发明实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
图9示出了上述实施例中所涉及的一种数据传输装置可能的结构示意图，可以用于执行上述方法实施例中核心网设备行为的功能，该装置可以包括：处理模块901和通信模块902。具体的，处理模块901对应的实体设备可以为处理器，通信模块902对应的实体设备可以为收发器，该装置还可以包括存储模块903，用于存储核心网设备的程序代码和数据。
当处理模块901为处理器，通信模块902为收发器，存储模块903为存储器时，本发明实施例所涉及的核心网设备可以为图10所示的核心网设备。
参阅图10所示，该核心网设备包括：处理器102、收发器103、存储器101以及总线104。其中，收发器803、处理器102以及存储器101通过总线104相互连接；总线104可以是外设部件互连标准(Peripheral Component Interconnect，PCI)总线或扩展工业标准结构(Extended Industry Standard Architecture，EISA)总线等。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图10中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
图11示出了上述实施例中所涉及的另一种数据传输装置可能的结构示意图，可以用于执行上述方法实施例中接入网设备行为的功能，该装置可以包括包括：处理模块112和通信模块113。具体的，处理模块112对应的实体设备可以为处理，通信模块113对应的实体设备可以为收发器，该装置还可以包括存储模块111，用于存储接入网设备的程序代码和数据。
当处理模块112为处理器，通信模块113为收发器，存储模块111为存储器时，本发明实施例所涉及的接入网设备可以为图12所示的接入网设备。
参阅图12所示，该接入网设备包括：处理器122、收发器123、存储器121以及总线124。其中，收发器123、处理器122以及存储器121通过总线124相互连接；总线124可以是外设部件互连标准PCI总线或扩展工业标准结构EISA总线等。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图12中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
图13示出了上述实施例中所涉及的基站的一种可能的结构示意图，用于执行上述方法实施例中基站行为的功能，该基站可以包括：发送模块132和接收模块133。发送模块132和接收模块133对应的实体设备可以为收发器。基站还可以包括存储模块131，用于存储基站的程序代码和数据。
其中，发送模块132和接收模块133可以是收发器、收发电路或通信接口等。存储模块133可以是存储器。
当发送模块132和接收模块133为收发器，存储模块131为存储器时，本发明实施例所涉及的基站可以为图14所示的基站。
参阅图14所示，该基站包括：处理器142、收发器143、存储器141以及总线144。其中，收发器143以及存储器141通过总线144相互连接；处理器142用于对基站的动作进行控制管理，总线144可以是外设部件互连标准PCI总线或扩展工业标准结构EISA总 线等。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图14中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
图15示出了上述实施例中所涉及的终端设备的一种可能的结构示意图，可以用于执行上述方法实施例中终端设备行为的功能。该终端设备可以包括：接收模块152和发送模块153。接收模块152和发送模块153对应的实体设备可以为收发器。终端设备还可以包括存储模块151，用于存储终端设备的程序代码和数据。
其中，接收模块152和发送模块153可以是收发器、收发电路或通信接口等。存储模块151可以是存储器。
当接收模块152和发送模块153为收发器，存储模块151为存储器时，本发明实施例所涉及的终端设备可以为图16所示的终端设备。
参阅图16所示，该终端设备包括：处理器162、收发器163、存储器161以及总线164。其中，收发器163以及存储器161通过总线164相互连接；处理器142用于对终端设备的动作进行控制管理，总线164可以是外设部件互连标准PCI总线或扩展工业标准结构EISA总线等。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图16中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
结合本发明公开内容所描述的方法或者算法的步骤可以硬件的方式来实现，也可以是由处理器执行软件指令的方式来实现。软件指令可以由相应的软件模块组成，软件模块可以被存放于随机存取存储器(Random Access Memory，RAM)、闪存、只读存储器(Read Only Memory，ROM)、可擦除可编程只读存储器(Erasable Programmable ROM，EPROM)、电可擦可编程只读存储器(Electrically EPROM，EEPROM)、寄存器、硬盘、移动硬盘、只读光盘(CD-ROM)或者本领域熟知的任何其它形式的存储介质中。 一种示例性的存储介质耦合至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息。当然，存储介质也可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。另外，该ASIC可以位于核心网接口设备中。当然，处理器和存储介质也可以作为分立组件存在于核心网接口设备中。
本领域技术人员应该可以意识到，在上述一个或多个示例中，本发明所描述的功能可以用硬件、软件、固件或它们的任意组合来实现。当使用软件实现时，可以将这些功能存储在计算机可读介质中或者作为计算机可读介质上的一个或多个指令或代码进行传输。计算机可读介质包括计算机存储介质和通信介质，其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是通用或专用计算机能够存取的任何可用介质。
以上所述的具体实施方式，对本发明的目的、技术方案和有益效果进行了进一步详细说明，所应理解的是，以上所述仅为本发明的具体实施方式而已，并不用于限定本发明的保护范围，凡在本发明的技术方案的基础之上，所做的任何修改、等同替换、改进等，均应包括在本发明的保护范围之内。

Claims (38)

  1. 一种多播业务的发送方法，其特征在于，包括：
    核心网设备确定待传输的多播业务的覆盖要求；
    所述核心网设备向接入网设备发送所述覆盖要求，所述覆盖要求用于确定所述接入网设备向终端设备发送所述多播业务的覆盖等级或传输参数。
  2. 根据权利要求1所述的方法，其特征在于，所述传输参数包括所述多播业务对应的覆盖等级的索引或所述多播业务在物理层的控制信道或共享信道上的重复发送次数。
  3. 根据权利要求1或2所述的方法，其特征在于，所述核心网设备包括广播多播服务中心BM-SC；
    所述核心网设备确定待传输多播业务的覆盖要求包括：
    所述BM-SC根据第三方服务器提供的所述多播业务的业务类型与所述多播业务的覆盖要求的对应关系确定所述多播业务的覆盖要求；或
    所述BM-SC根据所述第三方服务器提供的所述多播业务的业务类型，和所述BM-SC预配置的多播业务的业务类型与多播业务的覆盖要求的对应关系确定所述多播业务的覆盖要求。
  4. 根据权利要求1-3任一项所述的方法，其特征在于，所述核心网设备包括BM-SC，所述接入网设备包括基站；
    所述核心网设备向接入网设备发送所述覆盖要求包括：
    所述BM-SC通过所述移动性管理实体和所述MCE向所述基站发送所述覆盖要求。
  5. 根据权利要求1-3任一项所述的方法，其特征在于，所述核心网设备包括归属用户服务器HSS，所述接入网设备包括基站；
    所述核心网设备向接入网设备发送所述覆盖要求包括：
    所述HSS通过所述移动性管理实体和所述MCE向所述基站发送所述覆盖要求。
  6. 一种多播业务的传输方法，其特征在于，包括：
    接入网设备接收核心网设备发送的覆盖要求；
    所述接入网设备根据所述覆盖要求确定所述接入网设备向终端设备发送多播业务的覆盖等级或传输参数；
    所述接入网设备根据所述覆盖等级或所述传输参数向所述终端设备发送所述多播业务。
  7. 根据权利要求6所述的方法，其特征在于，所述传输参数包括所述多播业务对应的覆盖等级的索引或所述多播业务在物理层的控制信道或共享信道上的重复发送次数。
  8. 一种多播业务的发送方法，其特征在于，包括：
    基站在无线链路层控制协议RLC层向终端设备发送一次或多次多播业务的全部无线链路层控制协议数据控制单元RLC PDU或部分RLC PDU；
    所述基站接收终端设备发送的反馈信息，所述反馈信息用于向所述基站指示未成功接收的RLC PDU；
    所述基站向所述终端设备重传所述未成功接收的RLC PDU。
  9. 根据权利要求8所述的方法，其特征在于，所述基站在RLC层向所述终端设备发送一次或多次所述多播业务的全部RLC PDU或部分RLC PDU之前，所述方法还包括：
    所述基站向所述终端设备发送配置信息，所述配置信息包括所述多播业务的全部RLC PDU或所述部分RLC PDU在所述RLC层的重复发送次数、第一指示信息和第一定时器中的至少一个，所述第一指示信息用于指示所述全部RLC PDU或所述部分RLC PDU是否支持所述终端设备在所述RLC层反馈和单播重传所述未接收成功的RLC PDU、所述第一定时器用于指示所述基站在预定时间内接收所述反馈信息的时长。
  10. 根据权利要求9所述的方法，其特征在于，当所述配置信息包括所述第一定时器时，每部分RLC PDU对应一个所述第一定时器，所述基站在所述RLC层向所述终端设备发送一次或多次所述多播业务的部分RLC PDU包括：
    所述基站在所述RLC层向所述终端设备发送一次或多次任一部分RLC PDU，并经过所述第一定时器时长后继续向所述终端设备发送一次或多次下一部分RLC PDU。
  11. 根据权利要求8-10任一项所述的方法，其特征在于，每个RLC PDU头中包括第一字段，所述第一字段用于指示当前发送的RLC PDU为第N次重复发送，N为正整数，或所述第一字段用于指 示当前发送的RLC PDU是否为最后一次重复发送；或
    所述RLC PDU的物理下行控制信道PDCCH所传输的下行控制信息中包括用于指示当前发送的RLC PDU是否为最后一次发送的指示信息。
  12. 根据权利要求8-11任一项所述的方法，其特征在于，所述基站传输的最后一个RLC PDU中包括用于指示所述多播业务的所有RLC PDU发送完成的指示信息；
    或，所述基站每次重复发送完所述多播业务的所有RLC PDU中的最后一个RLC PDU中包括用于指示所述多播业务的所有RLC PDU第N次发送完成的指示信息。
  13. 根据权利要求9所述的方法，其特征在于，所述基站向终端设备发送配置信息包括：
    所述基站向所述终端设备广播***信息，所述***信息包括所述配置信息；或
    所述基站在多媒体广播多播服务MBMS控制信道SC-MCCH中向所述终端设备发送所述配置信息；或
    所述基站在SC-MCCH的物理下行控制信道PDCCH中向所述终端设备发送所述配置信息；或
    所述基站在MBMS业务信道SC-MCCH的PDCCH中向所述终端设备发送所述配置信息。
  14. 一种多播业务的发送方法，其特征在于，包括：
    终端设备接收基站在无线链路层控制协议RLC层一次或多次发送的多播业务的全部无线链路层控制协议数据控制单元RLC PDU或部分RLC PDU；
    所述终端设备向基站发送反馈信息，所述反馈信息用于向所述基站指示未成功接收的RLC PDU；
    所述终端设备接收所述基站重传的所述未成功接收的RLC PDU。
  15. 根据权利要求14所述的方法，其特征在于，在所述终端设备接收所述基站在所述RLC层一次或多次发送的多播业务的全部RLC PDU或部分RLC PDU之前，所述方法还包括：
    所述终端设备接收所述基站发送的配置信息，所述配置信息包 括所述多播业务的所述全部RLC PDU或所述部分RLC PDU在所述RLC层的重复发送次数、第一指示信息和第一定时器中的至少一个，所述第一指示信息用于指示所述全部RLC PDU或所述部分RLC PDU是否支持所述终端设备在RLC层反馈和单播重传所述未接收成功的RLC PDU，所述第一定时器用于指示所述基站在预定时间内接收所述反馈信息的时长。
  16. 根据权利要求15所述的方法，其特征在于，所述终端设备接收基站在RLC层一次或多次发送的多播业务的部分RLC PDU包括：
    所述终端设备接收完所述基站在所述RLC层一次或多次发送的所述多播业务的任一部分RLC PDU，并经过第二定时器的时长后，接收所述基站一次或多次发送的下一部分RLC PDU，所述第二定时器的时长与所述第一定时器的时长相同。
  17. 根据权利要求14-16任一项所述的方法，其特征在于，每个RLC PDU头中包括第一字段，所述第一字段用于指示当前发送的RLC PDU为第N次重复发送，N为大于或等于1的正整数，或所述第一字段用于指示当前发送的RLC PDU是否为最后一次重复发送；或
    所述RLC PDU的物理下行控制信道PDCCH所传输的下行控制信息中包括用于指示当前发送的RLC PDU是否为最后一次重复发送的指示信息。
  18. 根据权利要求14-17任一项所述的方法，其特征在于，所述终端设备接收到的最后一个RLC PDU中包括用于指示所述多播业务的全部RLC PDU发送完成的指示信息；或
    所述终端设备每次重复接收到的所述多播业务的全部RLC PDU中的最后一个RLC PDU包括用于指示所述多播业务的所有RLC PDU第N次发送完成的指示信息。
  19. 根据权利要求15所述的方法，其特征在于，所述终端设备接收所述基站发送的配置信息包括：
    所述终端设备接收所述基站广播的***信息，所述***信息包括所述配置信息；或
    所述终端设备接收所述基站在多媒体广播多播服务MBMS控制 信道SC-MCCH中发送的所述配置信息；或
    所述终端设备接收所述基站在SC-MCCH的物理下行控制信道PDCCH中发送的所述配置信息；或
    所述终端设备接收所述基站在MBMS业务信道SC-MCCH的PDCCH中发送的所述配置信息。
  20. 一种核心网设备，其特征在于，包括：
    处理模块，用于确定待传输的多播业务的覆盖要求；
    通信模块，用于向接入网设备发送所述处理模块确定的覆盖要求，所述覆盖要求用于确定所述接入网设备向终端设备发送所述多播业务的覆盖等级或传输参数。
  21. 根据权利要求20所述的核心网设备，其特征在于，所述传输参数包括所述多播业务对应的覆盖等级的索引或所述多播业务在物理层的控制信道或共享信道上的重复发送次数。
  22. 根据权利要求20或21所述的核心网设备，其特征在于，
    所述处理模块具体用于根据第三方服务器提供的所述多播业务的业务类型与所述多播业务的覆盖要求的对应关系确定所述多播业务的覆盖要求；或根据所述第三方服务器提供的所述多播业务的业务类型，和所述BM-SC预配置的多播业务的业务类型与多播业务的覆盖要求的对应关系确定所述多播业务的覆盖要求。
  23. 根据权利要求20-22任一项所述的核心网设备，其特征在于，
    所述通信模块具体用于通过所述移动性管理实体和所述MCE向所述基站发送所述处理模块确定的覆盖要求。
  24. 根据权利要求20-22任一项所述的核心网设备，其特征在于，
    所述通信模块具体用于通过所述移动性管理实体和所述MCE向所述基站发送所述处理模块确定的覆盖要求。
  25. 一种接入网设备，其特征在于，包括：
    接收模块，用于接收核心网设备发送的覆盖要求；
    处理模块，用于根据所述接收模块所接收的覆盖要求确定所述接入网设备向终端设备发送多播业务的覆盖等级或传输参数；
    通信模块，用于根据所述处理模块确定的覆盖等级或所述传输 参数向所述终端设备发送所述多播业务。
  26. 根据权利要求25所述的接入网设备，其特征在于，所述传输参数包括所述多播业务对应的覆盖等级的索引或所述多播业务在物理层的控制信道或共享信道上的重复发送次数。
  27. 一种基站，其特征在于，包括：
    发送模块，用于在无线链路层控制协议RLC层向终端设备发送一次或多次多播业务的全部无线链路层控制协议数据控制单元RLC PDU或部分RLC PDU；
    接收模块，用于接收所述终端设备发送的反馈信息，所述反馈信息用于向所述基站指示所述通信模块发送的、且未成功接收的RLC PDU；
    所述发送模块，还用于向所述终端设备重传所述未成功接收的RLC PDU。
  28. 根据权利要求27所述的基站，其特征在于，所述发送模块还用于：
    向所述终端设备发送配置信息，所述配置信息包括所述多播业务的全部RLC PDU或所述部分RLC PDU在所述RLC层的重复发送次数、第一指示信息和第一定时器中的至少一个，所述第一指示信息用于指示所述全部RLC PDU或所述部分RLC PDU是否支持所述终端设备在所述RLC层反馈和单播重传所述未接收成功的RLC PDU、所述第一定时器用于指示所述基站在预定时间内接收所述反馈信息的时长。
  29. 根据权利要求28所述的基站，其特征在于，所述发送模块用于：
    在所述RLC层向所述终端设备发送一次或多次任一部分RLC PDU，并经过所述第一定时器时长后继续向所述终端设备发送一次或多次下一部分RLC PDU。
  30. 根据权利要求27-29任一项所述的基站，其特征在于，每个RLC PDU头中包括第一字段，所述第一字段用于指示当前发送的RLC PDU为第N次重复发送，N为大于或等于1的正整数，或所述第一字段用于指示当前发送的RLC PDU是否为最后一次重复发送；或
    所述RLC PDU的物理下行控制信道PDCCH所传输的下行控制信息中包括用于指示当前发送的RLC PDU是否为最后一次发送的指示信息。
  31. 根据权利要求27-30任一项所述的基站，其特征在于，所述发送模块用于发送所述全部RLC PDU时所传输的最后一个RLC PDU中包括用于指示所述多播业务的全部RLC PDU发送完成的指示信息；
    或，所述发送模块用于发送所述全部RLC PDU时每次重复发送完所述多播业务的全部RLC PDU中的最后一个RLC PDU中包括用于指示所述多播业务的全部RLC PDU第N次发送完成的指示信息。
  32. 根据权利要求28所述的基站，其特征在于，所述发送模块用于：
    向所述终端设备广播***信息，所述***信息包括所述配置信息；或
    在多媒体广播多播服务MBMS控制信道SC-MCCH中向所述终端设备发送所述配置信息；或
    在SC-MCCH的物理下行控制信道PDCCH中向所述终端设备发送所述配置信息；或
    在MBMS业务信道SC-MCCH的PDCCH中向所述终端设备发送所述配置信息。
  33. 一种终端设备，其特征在于，包括：
    接收模块，用于接收基站在无线链路层控制协议RLC层一次或多次发送的多播业务的全部无线链路层控制协议数据控制单元RLC PDU或部分RLC PDU；
    发送模块，用于向基站发送反馈信息，所述反馈信息用于向所述基站指示所述通信模块发送的、且未成功接收的RLC PDU；
    所述接收模块，还用于接收所述基站重传的所述未成功接收的RLC PDU。
  34. 根据权利要求33所述的终端设备，其特征在于，所述接收模块还用于：
    接收所述基站发送的配置信息，所述配置信息包括所述多播业务的所述全部RLC PDU或所述部分RLC PDU在所述RLC层的重复 发送次数、第一指示信息和第一定时器中的至少一个，所述第一指示信息用于指示所述全部RLC PDU或所述部分RLC PDU是否支持所述终端设备在RLC层反馈和单播重传所述未接收成功的RLC PDU、所述第一定时器用于指示所述基站在预定时间内接收所述反馈信息的时长。
  35. 根据权利要求34所述的终端设备，其特征在于，所述接收模块用于：
    接收完所述基站在所述RLC层一次或多次发送的所述多播业务的任一部分RLC PDU，并经过第二定时器的时长后，接收所述基站一次或多次发送的下一部分RLC PDU，所述第二定时器的时长与所述第一定时器的时长相同。
  36. 根据权利要求33-35任一项所述的终端设备，其特征在于，每个RLC PDU头中包括第一字段，所述第一字段用于指示当前发送的RLC PDU为第N次重复发送，N为大于或等于1的正整数，或所述第一字段用于指示当前发送的RLC PDU是否为最后一次重复发送；或
    所述RLC PDU的物理下行控制信道PDCCH所传输的下行控制信息中包括用于指示当前发送的RLC PDU是否为最后一次重复发送的指示信息。
  37. 根据权利要求33-36任一项所述的终端设备，其特征在于，所述接收模块用于接收所述全部RLC PDU接收到的最后一个RLC PDU中包括用于指示所述多播业务的全部RLC PDU发送完成的指示信息；或
    所述接收模块用于接收所述全部RLC PDU每次重复接收到的所述多播业务的全部RLC PDU中的最后一个RLC PDU包括用于指示所述多播业务的全部RLC PDU第N次发送完成的指示信息。
  38. 根据权利要求34所述的终端设备，其特征在于，所述接收模块用于：
    接收所述基站广播的***信息，所述***信息包括所述配置信息；或
    接收所述基站在多媒体广播多播服务MBMS控制信道SC-MCCH中发送的所述配置信息；或
    接收所述基站在SC-MCCH的物理下行控制信道PDCCH中发送的所述配置信息；或
    接收所述基站在MBMS业务信道SC-MCCH的PDCCH中发送的所述配置信息。
PCT/CN2016/100942 2016-09-29 2016-09-29 一种多播业务的发送方法和设备 WO2018058468A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
EP16917222.8A EP3509329B1 (en) 2016-09-29 2016-09-29 Multicast service sending method and system
PCT/CN2016/100942 WO2018058468A1 (zh) 2016-09-29 2016-09-29 一种多播业务的发送方法和设备
CN201680089577.1A CN109792587B (zh) 2016-09-29 2016-09-29 一种多播业务的发送方法和设备
US16/368,085 US10966061B2 (en) 2016-09-29 2019-03-28 Multicast service transmission method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/100942 WO2018058468A1 (zh) 2016-09-29 2016-09-29 一种多播业务的发送方法和设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/368,085 Continuation US10966061B2 (en) 2016-09-29 2019-03-28 Multicast service transmission method and device

Publications (1)

Publication Number Publication Date
WO2018058468A1 true WO2018058468A1 (zh) 2018-04-05

Family

ID=61763542

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/100942 WO2018058468A1 (zh) 2016-09-29 2016-09-29 一种多播业务的发送方法和设备

Country Status (4)

Country Link
US (1) US10966061B2 (zh)
EP (1) EP3509329B1 (zh)
CN (1) CN109792587B (zh)
WO (1) WO2018058468A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022087990A1 (zh) * 2020-10-29 2022-05-05 Oppo广东移动通信有限公司 一种多播业务的重传方法及装置、终端设备、网络设备
CN114598997A (zh) * 2020-12-04 2022-06-07 中国电信股份有限公司 窄带物联网组播实现方法、***、服务器和终端

Families Citing this family (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106033465B (zh) * 2015-03-19 2019-09-17 阿里巴巴集团控股有限公司 一种信息推送方法和装置
US11617193B2 (en) * 2018-05-11 2023-03-28 Telefonaktiebolaget Lm Ericsson (Publ) Control signalling for a repeated transmission
CN112261671B (zh) * 2019-07-22 2022-07-29 华为技术有限公司 通信方法和通信装置
CN111836311B (zh) * 2019-08-09 2024-03-19 维沃移动通信有限公司 能力协商方法、终端及网络设备
CN113853808B (zh) * 2019-09-23 2023-06-20 华为技术有限公司 一种多播传输控制方法以及相关设备
CN112584322B (zh) * 2019-09-27 2021-11-19 华为技术有限公司 多播业务的处理方法及设备
US11452166B2 (en) * 2019-11-07 2022-09-20 Qualcomm Incorporated Discontinuous reception operation for new radio multicast communications
CN113840241A (zh) * 2020-06-24 2021-12-24 华为技术有限公司 一种通信方法及通信装置
CN113939042A (zh) * 2020-07-14 2022-01-14 维沃移动通信有限公司 处理方法、发送方法及相关设备
CN114070482B (zh) * 2020-07-31 2023-04-07 大唐移动通信设备有限公司 业务传输的处理方法、装置、网络侧设备及终端
CN114630283B (zh) * 2020-12-11 2023-06-23 维沃移动通信有限公司 多播业务的确认模式传输方法、装置、设备及存储介质
CN116868593A (zh) * 2021-02-25 2023-10-10 三菱电机株式会社 通信***及通信终端
CN115175255A (zh) * 2021-04-01 2022-10-11 华为技术有限公司 一种多播广播业务的传输切换方法及装置
CN115694596B (zh) * 2021-07-31 2024-06-04 华为技术有限公司 一种北斗通信***中入站传输控制方法、***及相关装置
CN117998303A (zh) * 2022-11-03 2024-05-07 华为技术有限公司 一种业务数据处理方法和设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1515575A1 (en) * 2003-09-15 2005-03-16 Motorola, Inc. A 3rd generation cellular communication network, user equipment and method for the communication of paging indication messages
CN1756414A (zh) * 2004-09-28 2006-04-05 华为技术有限公司 移动通信***中进行多播的方法
CN101370156A (zh) * 2007-08-15 2009-02-18 上海华为技术有限公司 多播组播业务传输的方法和网络***
CN101627611A (zh) * 2007-01-10 2010-01-13 Lg电子株式会社 在移动通信***中用于传输控制信息的方法

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP6675301B2 (ja) * 2013-04-18 2020-04-01 クアルコム，インコーポレイテッド ｅＭＢＭＳを介したプッシュツートークまたはプッシュツーエブリシングのためのＭＢＭＳベアラエンハンスメント
US20150078241A1 (en) * 2013-09-13 2015-03-19 Nokia Solutions And Networks Oy Method and apparatus for supporting multicast delivery
US9338715B1 (en) * 2014-08-21 2016-05-10 Sprint Spectrum L.P. Method and system for facilitating transition from broadcast to unicast
EP3487193B1 (en) 2016-08-12 2020-05-27 Huawei Technologies Co., Ltd. Service transmission method and wireless communication device
WO2019142051A1 (en) * 2018-01-16 2019-07-25 Lenovo (Singapore) Pte. Ltd. Rate-matching a data transmission around resources

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1515575A1 (en) * 2003-09-15 2005-03-16 Motorola, Inc. A 3rd generation cellular communication network, user equipment and method for the communication of paging indication messages
CN1756414A (zh) * 2004-09-28 2006-04-05 华为技术有限公司 移动通信***中进行多播的方法
CN101627611A (zh) * 2007-01-10 2010-01-13 Lg电子株式会社 在移动通信***中用于传输控制信息的方法
CN101370156A (zh) * 2007-08-15 2009-02-18 上海华为技术有限公司 多播组播业务传输的方法和网络***

Non-Patent Citations (1)

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

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022087990A1 (zh) * 2020-10-29 2022-05-05 Oppo广东移动通信有限公司 一种多播业务的重传方法及装置、终端设备、网络设备
CN114598997A (zh) * 2020-12-04 2022-06-07 中国电信股份有限公司 窄带物联网组播实现方法、***、服务器和终端

Also Published As

Publication number Publication date
EP3509329A4 (en) 2019-09-04
EP3509329A1 (en) 2019-07-10
US10966061B2 (en) 2021-03-30
CN109792587B (zh) 2021-02-12
CN109792587A (zh) 2019-05-21
EP3509329B1 (en) 2021-04-07
US20190222970A1 (en) 2019-07-18

Similar Documents

Publication Publication Date Title
WO2018058468A1 (zh) 一种多播业务的发送方法和设备
WO2020088540A1 (zh) 传输方法和装置
WO2018133720A1 (zh) 反馈信息传输方法及装置
JP5081908B2 (ja) 移動通信システムにおけるマルチメディアブロードキャストマルチキャストサービス（ｍｂｍｓ）の品質保障方法、及びその端末
JP4864096B2 (ja) １対多サービス通信
WO2016163548A1 (ja) 基地局及びユーザ端末
CN113853808B (zh) 一种多播传输控制方法以及相关设备
KR20100138812A (ko) 멀티미디어 브로드캐스트/멀티캐스트 서비스에서 오류 패킷의 재전송 요구 정보 전송 방법 및 재전송 요구에 대한 오류 패킷 재전송 방법
US10244400B2 (en) Service data transmission method and apparatus
JP2007518307A (ja) Ｍｂｍｓサービスのデータエラーの修復方法
WO2018027983A1 (zh) 一种数据传输方法及设备
WO2008115023A1 (en) Mbms data transmission and receiving in packet based on mobile communication system
US10917818B2 (en) Method and apparatus for group communication in wireless communication system
WO2014067144A1 (zh) 群组寻呼方法、基站及用户设备
US20100110879A1 (en) Method and apparatus for providing multimedia broadcast multicast service
CN113678500B (zh) 一种反馈资源配置方法及通信方法、装置、通信设备
EP1898659A2 (en) Method of reporting MBMS service information for user equipment in a wireless communications system and related apparatus
JP2023547407A (ja) ハイブリッド自動再送信要求のための方法および装置
WO2018063326A1 (en) Multicast retransmission for machine type devices
KR101268580B1 (ko) 멀티미디어 브로드캐스트 멀티캐스트 서비스 제공 방법 및 그 장치
WO2024031307A1 (zh) 混合自动重传请求harq反馈方法、装置、设备及介质
WO2023102898A1 (zh) 重传方式的确定方法及定时器的控制方法、装置
WO2023097613A1 (zh) 一种信息确定方法及装置、终端设备
WO2024031395A1 (zh) 重复传输方法、终端设备和网络设备
CN118104355A (zh) 一种drx定时器的运行方法及装置、终端设备

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2016917222

Country of ref document: EP

Effective date: 20190403