WO2011020403A1 - 多媒体广播组播业务中多调度周期联合调度的方法及装置 - Google Patents

多媒体广播组播业务中多调度周期联合调度的方法及装置 Download PDF

Info

Publication number
WO2011020403A1
WO2011020403A1 PCT/CN2010/075605 CN2010075605W WO2011020403A1 WO 2011020403 A1 WO2011020403 A1 WO 2011020403A1 CN 2010075605 W CN2010075605 W CN 2010075605W WO 2011020403 A1 WO2011020403 A1 WO 2011020403A1
Authority
WO
WIPO (PCT)
Prior art keywords
scheduling period
data
scheduling
service
sent
Prior art date
Application number
PCT/CN2010/075605
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 中兴通讯股份有限公司
Publication of WO2011020403A1 publication Critical patent/WO2011020403A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/121—Wireless traffic scheduling for groups of terminals or users
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/30—Resource management for broadcast services

Definitions

  • the present invention relates to a service scheduling technology in a Long Term Evolution (LTE) system, and more particularly to a method and apparatus for joint scheduling of multiple scheduling periods in a Multimedia Broadcast Multicast Service (MBMS).
  • LTE Long Term Evolution
  • MBMS Multimedia Broadcast Multicast Service
  • the 3rd Generation Partnership Project (3GPP) proposes an MBMS service, which is a point-to-multipoint service that transmits data from one data source to multiple targets.
  • Network resources including the core network and the access network, are shared, thereby improving the utilization of network resources, especially air interface resources.
  • the MBMS service not only enables plain text low-rate message-like multicast and broadcast, but also enables high-speed multimedia service broadcast and multicast, and can provide a variety of rich video, audio and multimedia services, which undoubtedly conforms to future mobile data.
  • the development trend provides a better business prospect for the development of 3G.
  • the MBMS service can use the Multicast/Broadcast over Single Frequency Network (MBSFN) technology, also known as the multicast single frequency network technology.
  • MBSFN Multicast/Broadcast over Single Frequency Network
  • MBMS service transmitted by MBSFN also known as MBSFN service, can use the same modulation and coding format and use the same physical resource in multiple cells to transmit the same content.
  • MBSFN Multicast/Broadcast over Single Frequency Network
  • MTCH Multicast Traffic Channel
  • MCCH Multicast Control Channel
  • PTm point-to-multipoint
  • MBSFN synchronization area MBSNF area, MBSFN transmission, reserved cell, etc. are all semi-statically configured by operation and maintenance.
  • the user equipment (UE, User equipment) of the multiple cells can receive multiple MBMS data with the same content and perform the combining processing, so that the gain of the received signal can be improved.
  • the same physical resource is used, and multiple cells of the same MBMS service are transmitted in the MBSFN transmission mode to form an MBSFN area.
  • MBSFN service group belongs to only one MBSFN area, and one MBSFN area includes multiple cells, and each cell is configured with exactly one MBSFN service group.
  • the data channel MTCH of multiple MBSFN services having the same MBSFN area, and the control channel MCCH of the MBSFN service may be multiplexed into one transport channel.
  • the transport channel is a multicast channel (MCH, Multicast Channel);
  • MCH multicast channel
  • UMTS the transmission channel is a forward access channel (FACH) oblige MCCH and multiple MTCHs of the same MBSFN area, that is, multiple logical channels can be mapped to the same transmission channel; one MBSFN area can be configured with one or Multiple transport channels, each carrying one or more logical channels.
  • a multicast subframe allocation mode timing (MSAP occasion) is introduced, which indicates all multicast subframe resources included in one (P) MCH in a time period, and one scheduling period includes one Or multiple MSAP occasion lengths.
  • the scheduling period is a time period periodically configured by the wireless interface, in which the transmission channel or the physical channel carrying the service data is configured with a set of channel resources, and the specific service data is scheduled to be sent on the scheduling resource.
  • the service data of the MTCH transmitted in a scheduling period is respectively processed by a radio link control (RLC) protocol at a logical channel level, including RLC concatenation and fragmentation, and generating an RLC protocol data unit (PDU), that is, a transmission channel.
  • RLC radio link control
  • PDU RLC protocol data unit
  • MAC Media Access Control
  • SDU Media Access Control
  • one or more MAC SDUs are carried on one MAC PDU
  • multiple MAC SDUs are multiplexed in the same MAC PDU by MAC concatenation function.
  • MAC PDUs from different MTCHs are sequentially transmitted on the transport channel in a predetermined order.
  • data of one MTCH is continuously transmitted, that is, data of one service continuously occupies MBSFN subframe resources of the MCH channel, until all service data that needs to be sent in the scheduling period of the service is completely transmitted.
  • FIG. 1 is a schematic diagram of dynamic scheduling of two services in a scheduling period.
  • the part filled with slashes represents the service S1
  • the part filled with blanks represents the service S2
  • the part filled with the vertical lines represents the filling. It can be seen that In scheduling period 1 and scheduling period 2, both service S1 and service S2 are dynamically multiplexed separately.
  • FIG. 2 is a schematic diagram of a method for multiplexing two MAC PDUs in a MAC PDU carried by an MBSFN sub-frame, that is, a MAC concatenation method.
  • a MAC PDU includes a MAC header, a MAC control unit, a plurality of MAC SDUs, and a padding (opt) portion.
  • the MAC header further includes a MAC subheader 1 to a MAC subheader 6, and a plurality of MAC SDUs are concatenated.
  • the dynamic scheduling information of the service is also sent in each scheduling period, which is simply referred to as scheduling information, and the scheduling information carries the mapping information of the MTCH to the MBSFN subframe, and the UE reads the scheduling information to know which MBSFN subframes each MTCH is allocated.
  • the specific scheduling information may be the start of each service in one scheduling period, the end subframe position information, and the number of MBSFN subframes occupied by the service data, where the subframe position is (P) MCH channel configuration.
  • TDM Time Division Multiplexing
  • TDM offset And repetition length one or more TDM cycles constitute a scheduling period of a service.
  • RLC layer processing on the data of the service in a scheduling period RLC is concatenated and fragmented, and the generated RLC PDU is carried to the transport channel.
  • the resources occupied by each service are exclusive, that is, there is no wireless channel resource in which the data between the services is shared by the same transmission time interval.
  • One or more services multiplex shared wireless channel resources through a transport channel, or a physical channel, where the wireless channel resources refer to spreading codes in the UMTS system.
  • the radio interface determines a periodic scheduling period, and in each scheduling period, the network element schedules data of one or more services for transmission. In this manner, traffic data units of one or more services can share radio channel resources for the same transmission time interval.
  • scheduling information is also present, and the scheduling information is carried on the multi-point scheduling channel (MSCH).
  • MSCH multi-point scheduling channel
  • Each FACH channel carrying the MTCH carries an MSCH channel, which is used to indicate scheduling information of the MTCH data carried by the FACH channel, and scheduling information.
  • the specific performance is the start time, duration, and the like of the service data scheduling. Different from the LTE technology, there is no strict correspondence between the transmission period and the scheduling period of the scheduling information.
  • a synchronous protocol processing (SYNC) method is provided for the MBSF service in the MBSFN mode of multiple network element entities, such as the cell of the base station network element.
  • the network element architecture and processing principle are shown in FIG.
  • the method includes an upper layer network element and N lower layer network elements, and the SYNC protocol manner includes the following processing:
  • Step 10 The upper layer network element sends the MBMS service data packet to each lower layer network element, and the MBMS service data packet carries the service data, and carries the timestamp information, the data packet sequence number information, the accumulated service data length information, and the like, and the upper layer network membered same continuous MBMS service stamp packet identification information to one or more of these markers have the same timestamp make up a data packet sent smile (data burst) is called synchronization sequence or bad 1 J (synchronization sequence), Head 4
  • the time stamp difference of the synchronization sequence is the length of the synchronization sequence, or SYNC period.
  • the timestamp information of each synchronization sequence can be indicated in two ways: one is to include, in each data packet included in the synchronization sequence, reference time information that the synchronization sequence starts to transmit at the wireless interface; For example, each data packet in the above synchronization sequence includes reference time information that the previous synchronization sequence starts to transmit at the wireless interface.
  • Step 11 At the end of each synchronization sequence, the upper layer network element further sends a SYNC control frame, which only carries the total number of data packets of the previous synchronization sequence and the total length of the data packet, and is used for detecting the lower layer network element.
  • a SYNC control frame which only carries the total number of data packets of the previous synchronization sequence and the total length of the data packet, and is used for detecting the lower layer network element.
  • Step 12 The service data carried by the lower layer network element to the service data packet in the same synchronization sequence is sequentially sent on the radio interface in the scheduling period corresponding to the timestamp.
  • mapping relationships from the synchronization sequence to the scheduling period including: mapping multiple synchronization sequences to one scheduling period, where the SYNC period length is one of integer multiples of the scheduling period, and one SYNC sequence mapping To a scheduling period, the length of the SYNC period is equal to the scheduling period.
  • the SYNC period length is equal to the scheduling period, then one synchronization sequence is mapped to one scheduling period; when multiple services dynamically multiplex channels, one synchronization sequence data of each service is mapped to the same scheduling period.
  • the service data S1 and service S2 share the same channel
  • Pl-1 and P1-2 are data packets of service SI
  • P2-l and P2-2 are data packets of service S2.
  • the scheduling periods T1 and T2 of FIG. 4 are two scheduling periods
  • the service data S1 has service data in the scheduling period T1 and the scheduling period T2 according to the SYNC protocol. Need to send.
  • the scheduling period T1 since the service data amount of the services S1 and S2 exceeds the maximum capability that the channel resource corresponding to the scheduling period T1 can be transmitted, part of the service data of the service S2, that is, part of the service data of the P2-2 data packet occurs. Cannot send the situation.
  • overflow processing is required on the overflow data, because: the service data sent at the beginning of each scheduling period is determined to be sent from a specific synchronization sequence packet, that is, mapped to The data of the previous scheduling period will not be sent in the next scheduling period. Even if the data in the previous scheduling period cannot be sent all, it will not be sent in the next scheduling period. And, at the beginning of each scheduling period, the base station network element resets the user plane protocol. For example: In the UMTS system, the sequence number of the RLC PDU of the service data is reset at the beginning of each scheduling period to ensure that the sequence number of the RLC PDU is allocated from a fixed value at the beginning of each scheduling period.
  • the advantages of the foregoing processing method are: for a newly added base station network element, or a base station network element that restarts, at any time, according to the SYNC protocol, data transmitted by other network elements in a certain scheduling period, and wireless can be determined according to the SYNC protocol.
  • the interface protocol is especially the protocol state of the RLC layer (for example, the RLC sequence number), so that the network element can transmit the service data synchronously with other base station network elements, without considering other base station network elements in the previous scheduling period. How is the data processed? That is to say, the processing of each scheduling period is independent, avoiding mutual interference, and providing the opportunity for the restarted network element to resend the service with other network elements.
  • the above processing method also has certain problems: Due to the dynamic characteristics of the MBMS service, traffic changes of service data in different scheduling periods will be very large, and service data to be sent in different scheduling periods will be greatly different, especially for one. When a service enjoys one channel, or multiple services multiplex channels and the number of services is relatively small. The resources are not configured to be infinite to meet the change of service traffic. Then, when the service traffic changes greatly and the configurable resources are insufficient to meet the maximum possible service data rate, according to the prior art processing manner, the service Loss of data will be inevitable, and discarding the corresponding business data will directly lead to a decline in the quality of business services. Summary of the invention
  • the main object of the present invention is to provide a method and apparatus for joint scheduling of multiple scheduling periods in a multimedia broadcast multicast service, which can avoid the loss of service data due to service data overflow as much as possible, thereby improving service quality.
  • the present invention provides a data overflow in a scheduling period of a multi-scheduling cycle joint scheduling in a multimedia broadcast multicast service, and when there is a scheduling period of the same scheduling period group after a scheduling period in which a data overflow occurs, the present invention cannot be present.
  • the data sent during the scheduling period of the data overflow is sent in the subsequent scheduling period of the same scheduling period group.
  • the method further includes: discarding the data of the overflow part when there is a data overflow in the scheduling period, and there is no scheduling period of the same scheduling period group after the scheduling period in which the data overflow occurs.
  • the data that cannot be sent in the scheduling period in which the data overflow occurs is sent in the subsequent scheduling period of the same scheduling period group as: the data that cannot be sent in the previous scheduling period belongs to the same The scheduling period group is sent in the next scheduling period.
  • the data sent in the subsequent scheduling period of the same scheduling period group is the entire data packet of the data packet that cannot be completely transmitted in the scheduling period in which the data overflow occurs; or in the scheduling period in which the data overflow occurs. Part of the data of the completely transmitted packet.
  • the sending in the subsequent scheduling period of the same scheduling period group is: sending as the first data part in the subsequent scheduling period; or as the service corresponding to the overflow data in the subsequent scheduling period.
  • a data part is sent.
  • the data transmission is performed by an underlying network element, where the lower layer network element is an evolved base station, or a radio network controller, or a Node B (NB+).
  • the method further includes: the out-of-synchronization lower layer network element starts or restarts to send the service synchronously with other lower layer network elements from the start boundary of the next scheduling period group.
  • the present invention also provides a device for joint scheduling of multiple scheduling periods in a multimedia broadcast multicast service, comprising: a setting unit and a data packet processing unit; wherein, the data packet processing unit is used in a scheduling period in which data overflow occurs and data overflow occurs Then, when there is a scheduling period that belongs to the same scheduling period group, the data that cannot be transmitted in the scheduling period in which the data overflow occurs is transmitted in the subsequent scheduling period of the same scheduling period group.
  • the data packet processing unit is further configured to discard the data of the overflow part when there is no scheduling period of the same scheduling period group after the scheduling period in which the data overflow occurs and the data overflow occurs.
  • the apparatus further includes a determining unit, configured to determine whether there is a data overflow in the scheduling period in the scheduling period group, and determine whether a scheduling period of the same scheduling period group exists after the scheduling period in which the data overflow occurs, and the determining result is Send to the packet processing unit.
  • the multi-scheduling cycle joint scheduling method in the multimedia broadcast multicast service provided by the present invention and the data overflow in the scheduling period in the period group, it is first determined whether there is a scheduling period of the same scheduling period group after the scheduling period in which the data overflow occurs.
  • the data sent during the scheduling period in which the data overflow occurs cannot be delayed to be sent to the subsequent scheduling period of the same scheduling period group. Therefore, the quality of service quality caused by completely discarding the overflow data in the prior art can be avoided. decline.
  • the present invention provides the feature of resynchronization by setting the scheduling period group. For the lower layer network element that loses synchronization, it can be made in the scheduling period group, from the scheduling week where the out-of-synchronization occurs. The start boundary of the next scheduling period group of the period group starts, and restarts the transmission of the received service data in synchronization with the other lower layer network elements, thereby ensuring synchronization of data transmission and reception between the lower layer network elements.
  • FIG. 1 is a schematic diagram of dynamic multiplexing scheduling of two services in one scheduling period in the prior art
  • FIG. 2 is a schematic diagram of multiplexing one MAC PDU of data of two services in dynamic multiplexing scheduling
  • FIG. 3 is a schematic diagram of SYNC in the prior art. Schematic diagram of the network element architecture and processing principle of the protocol mode
  • FIG. 4 is a schematic diagram of service data overflow in the prior art scheduling
  • FIG. 5a is a schematic diagram of an implementation process of the method of the present invention.
  • FIG. 5b is a schematic diagram of an implementation process of the method of the present invention.
  • FIG. 6 is a schematic diagram of a data packet that the lower layer network element cannot transmit completely in the previous scheduling period as the first data part in the latter scheduling period;
  • FIG. 7 is a schematic diagram of a data packet that the lower layer network element cannot transmit completely in the previous scheduling period as the first data part of its corresponding service in the latter scheduling period;
  • FIG. 8 is that the lower layer network element cannot be in the A schematic diagram of a portion of data of a data packet transmitted in a previous scheduling period being transmitted as a first data portion in a next scheduling period;
  • FIG. 9 is a schematic diagram of a part of data of a data packet that the lower layer network element cannot transmit in the previous scheduling period is sent as the first data part of its corresponding service in the next scheduling period;
  • FIG. 10 is a schematic diagram of the lower layer network element discarding data that cannot be sent in the last scheduling period in a scheduling period group.
  • DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS A period group has a data overflow in a scheduling period in a scheduling period group, and a data overflow occurs. When there is a scheduling period of the same scheduling period group after the scheduling period, the data that cannot be completely transmitted in the scheduling period in which the data overflow occurs may be delayed to be sent to the subsequent scheduling period of the same scheduling period group.
  • the data of the overflow portion is discarded.
  • the lower layer network element groups a plurality of adjacent scheduling periods into a scheduling period group, and each scheduling period belongs to only one scheduling period group.
  • the overflow means that the synchronization sequence data mapped to a scheduling period according to the timestamp of the synchronization sequence cannot be transmitted within the mapped scheduling period, that is, the synchronization sequence data mapped to one scheduling period exceeds the scheduling.
  • the transmission capacity of the channel resources in the period; the service data for the overflow part may be simply referred to as overflow data.
  • the transmitting the data that cannot be completely transmitted in the scheduling period in which the data overflow occurs to the subsequent scheduling period of the same scheduling period group means: delaying the data that cannot be completely transmitted in the scheduling period in which the data overflow occurs Sent within the next scheduling period of the same scheduling period group.
  • it may also be sent in the second scheduling period, or the third scheduling period, which belong to the same scheduling period group, in the scheduling period in which the data overflow occurs.
  • the entire packet of the transmitted packet can also be part of the data in the packet that cannot be completely transmitted.
  • the overflow data may be sent as the first data part of the another scheduling period when sent by another scheduling period, that is, before being mapped to the service data of the corresponding scheduling period by using the time stamp; or may be used as the another scheduling.
  • the first data part of the service corresponding to the overflow data is sent in the period, that is, the data of the overflow part is sent before the data corresponding to the service corresponding to the overflow data in the corresponding scheduling period.
  • a data packet that cannot be completely transmitted in the previous scheduling period is transmitted in the latter scheduling period.
  • the data packet P2-2 in the synchronization sequence of the service S2 cannot be in the scheduling period 1.
  • the next scheduling period adjacent to the scheduling period 1 is the scheduling period 2, and the scheduling period 1 and the scheduling period 2 constitute a scheduling period group.
  • the entire P2-2 data packet may be transmitted in the scheduling period 2; only the data in the P2-2 data packet overflowed in the scheduling period 1 may be transmitted in the scheduling period 2.
  • the data of the overflow part of the entire P2-2 data packet or the P2-2 data packet to be transmitted in the scheduling period 2 may be transmitted in the first data portion of the scheduling period 2, in which case the first data portion is not considered.
  • the data of the overflow portion of the entire P2-2 data packet or the P2-2 data packet to be transmitted in the scheduling period 2 may also be sent in the first data portion of the corresponding service S2 in the scheduling period 2.
  • the data of the overflow portion of the entire P2-2 packet or the P2-2 packet to be transmitted in the scheduling period 2 is transmitted as the first data portion of the service S2 only when the scheduling of the service S2 is started.
  • the lower layer network element for the lower layer network element that loses synchronization, it can keep the data transmission and reception synchronization in units of the scheduling period group, start from the start boundary of the next scheduling period group, start or restart the transmission and reception synchronized with other lower layers.
  • Business data to. Specifically, the process of resynchronizing is: the lower layer network element first obtains the size and boundary of the scheduling period group, and starts to schedule the received service data at the beginning of a scheduling period group after the current time, and sends the received service data to the wireless interface. .
  • the lower-layer network element that is out of synchronization is: a new network element that is newly added to the service to be sent during the process of the service; or, in the process of sending the service, the lower-layer network element that is added to the service after the restart occurs; Or, in the process of the service transmission, the lower layer network element that does not receive the consecutive multiple synchronization sequences and causes the out-of-synchronization is not received; or, for other reasons, the lower layer network element that cannot determine how to perform the transmission service does not cause interference to the neighboring area.
  • step 550011aa when the current data overflow overflow occurs, it is judged whether or not the current data overflow overflow occurs after the scheduling period is after the cycle period is whether or not there is It is the period of the scheduling period that belongs to the same period of the same scheduling period, and if the existence exists, then it will not be able to appear in the current data.
  • the number of data sent and sent within the weekly period of the spillover period is late and the subsequent renewed scheduling is the same as the group of the same period of the same period. Sending and sending within the period of the week;; otherwise, discarding the data of the part of the overflow and overflow. .
  • the number of data packets that cannot be sent and sent in the previous one-to-one scheduling period is not one after the other.
  • the dispatching schedule is sent and sent within the weekly period, and the processing flow of the specific body is as shown in FIG. 55bb, and the package includes the following steps:
  • Step 501b When a data overflow occurs, determine whether the scheduling period in which the data overflow occurs is the last scheduling period in the scheduling period group, and if not, the data that cannot be sent in the previous scheduling period is sent in the next scheduling period; If yes, the data of the overflow part is discarded.
  • the sending in the next scheduling period may be the entire data packet of the data packet that cannot be completely transmitted in the previous scheduling period; or may be part of the data in the data packet that cannot be completely transmitted in the previous scheduling period;
  • the sending in the next scheduling period means: transmitting as the first data part in the next scheduling period, or as the first data part of its corresponding service in the next scheduling period.
  • the following is an example of sending a data packet that cannot be completely transmitted in the previous scheduling period in a subsequent scheduling period, and specifically describes the implementation of the method of the present invention, and the principle and process of sending subsequent scheduling periods in the same scheduling period group. Basically the same.
  • the method of the present invention is applicable to a network architecture similar to that shown in FIG. 3, in the present invention, the above
  • the layer network element and the lower layer network element are respectively two termination points of the SYNC protocol.
  • the upper layer network element may be a broadcast multicast service center (BMSC), or an MBMS service gateway (MGW), or a gateway general grouping in the UMTS network.
  • Wireless Service Support Node (GGSN) may be an evolved base station eNB, or a Radio Network Controller (RNC), or NB+, and the like.
  • the lower layer network element receives the synchronization sequence sent by the upper layer network element, and maps the data packet of the synchronization sequence to the corresponding scheduling period according to the timestamp information of the synchronization sequence; when multiple services dynamically multiplex channel resources, the multiple The synchronization sequence of the services mapped to the same scheduling period is sequentially sent in the scheduling period according to a predetermined sequence.
  • the synchronization sequence of the service S1 includes the data packets P1-1, P1-2, and the synchronization of the service S2.
  • the data packets P2-l and P2-2 in the sequence are respectively mapped into the scheduling period T1, and the data packets P1-1, P1-2, and P2-1 are sequentially transmitted in a predetermined order within the scheduling period T1.
  • the lower layer network element forms a plurality of scheduling periods into a scheduling period group. If an overflow data occurs in a scheduling period, the service for performing the overflow processing is selected according to a predetermined rule, and the service data that needs to be overflowed is determined. If the scheduling period in which the overflow occurs belongs to the same scheduling period group as the next scheduling period, the data of the overflow part is sent in the next scheduling period; if the scheduling period in which the overflow occurs does not belong to the same scheduling period as the next scheduling period When the cycle group is scheduled, the data of the overflow part is discarded.
  • the predetermined rule may be a preset priority, a preset scheduling rule, or the like.
  • the scheduling period is a time period of the wireless interface, corresponding to a group of wireless channel resources.
  • the scheduling period may include one or more MBSFN resource allocation periods, or MSAP periods, or MSAP occasion lengths.
  • the scheduling period may include one or more MBSFN TDM period sizes, or a range of radio interface periods expressed in units of transmission time intervals ( ⁇ ).
  • the synchronization sequence is a set of service data packets sent by the upper layer network element to the lower layer network element, where the service data packet carries timestamp information, and the service data packet of the same synchronization sequence carries the same Timestamp information.
  • the service data packet further carries a data packet sequence number and accumulated length information, respectively indicating a sequence number of a service data packet in a synchronization sequence, and a total data length of the data packet before a service data packet.
  • the degree period group may be: the lower layer network element obtains the number of consecutive scheduling periods N of the scheduling period group by the configuration management network element, where the N is a semi-static configuration parameter; the scheduling period group is specifically represented by the wireless
  • the interface forms one scheduling period group every N scheduling periods. Among them, the continuous scheduling period can also be said to be two adjacent scheduling periods.
  • the lower layer network element determines whether it is necessary to perform overflow processing in a scheduling period according to the following method, and selects a service for performing overflow processing: the number of channel resources in the lower layer network element according to a scheduling period, and the service to be sent in the scheduling period.
  • the number of data is determined whether service data overflow processing is required. If the total amount of service data to be sent exceeds the maximum amount of service data that can be sent to the maximum service data in the scheduling period, the lower layer network element determines that the service data overflow occurs, and Calculate the amount of data that overflows.
  • the lower layer network element can obtain the number of services that need to be sent in one scheduling period as follows: The lower layer network element adds the length of all data packets in a synchronization sequence by statistics, and obtains data sent by a service in a scheduling period. Or the lower layer network element obtains the total length of the data packet and the number of data packets of the synchronization sequence by detecting the total length of the data and the number of data packets of the synchronization sequence carried by the data packet of the next synchronization sequence or the SYNC control frame. .
  • the lower layer network element selects the service data according to the pre-configured service transmission order or service priority.
  • the data of one or more of the plurality of services sent is overflow processed. Only one service is multiplexed to the scheduling period as a special case. In this case, the service data that needs to be overflowed is directly determined.
  • the method for the lower layer network element to determine the data that needs to be processed by overflow is:
  • the lower layer network element will not be able to send one or more complete service data packets in the scheduled scheduling period as the service data that needs to be processed by overflow. In other words, if a service data packet cannot be completely sent in one scheduling period, Then overflowing the entire data packet of the service data packet;
  • the lower layer network element determines that one or more complete service data packets that cannot be sent in the scheduling period are overflow processed, and if part of the data of one service data packet can be sent in the scheduling period, the service data is Part of the data that the packet cannot be sent is overflowed.
  • the upper layer network element is a BMSC
  • the lower layer network element is an eNB.
  • the SYNC protocol is used to process the service data packets into a synchronization sequence, and the data packets of each synchronization sequence identify the same timestamp, and are used to indicate the current synchronization sequence of the eNB or the previous one.
  • the start time information of the synchronization sequence transmitted on the wireless interface; each SYNC protocol data packet also carries the data packet sequence number and the data packet cumulative length information; in addition to the service data packet, the BMSC also sends a SYNC control packet to the eNB, carrying the previous synchronization.
  • the eNB configures the scheduling period length to be an integer multiple of the SYNC period, or equal to the SYNC period.
  • Each scheduling period contains a set of MBSFN subframe resources.
  • the SYNC period and the radio interface scheduling period are respectively 320 ms
  • SFN is the system frame number
  • each system frame length is 10 ms
  • the SFN maximum value is 1024. Indicates that the scheduling period is periodically configured every 320 ms.
  • the eNB After receiving the synchronization sequence sent by the BMSC, the eNB maps the scheduling period to the radio interface according to the timestamp indication. Specifically, the eNB maps the data packet of the synchronization sequence to the scheduling period after the time indicated by the transmission timestamp, or is directly opposite. The scheduling period begins to be sent.
  • the eNB will multiplex multiple services to the same service channel in a dynamic scheduling manner on the radio interface. Specifically, the eNB maps to multiple services in one scheduling period of a transport channel, such as the MCH, according to the SYNC protocol, according to the predetermined schedule.
  • Business delivery order in turn, multiple business numbers Transmitted according to the wireless subframe resources in the scheduling period.
  • S1 and S2 are mapped to the channel MCH.
  • the total length of the data packets mapped by the services S1 and S2 to the scheduling period exceeds the total amount of services that the MCH channel can transmit during the scheduling period.
  • the synchronization sequence of the service S1 includes two data packets P1-1 and P1-2
  • the synchronization sequence of the service S2 includes two service data packets P2-1 and P2-2. Their lengths are Ll-1, Ll-2, L2-1, L2-2.
  • the total length of the service data packet that can be sent in the scheduling period T1 is L. If the total length of the four data packets P1-1, Pl-2, P2-l, and P2-2 exceeds L, it means that within the scheduling period T1, A data overflow will occur, and according to the service priority, the eNB selects part of the data of S2 for overflow processing.
  • the eNB sets each scheduling period to one scheduling period group. That is, the scheduling period group length is 640 ms, and each 640 ms is a scheduling period group, and the boundaries are 0, 640, and 1280 ms, respectively.
  • the eNB selects that the service data packet P2-2 that cannot be completely transmitted in the scheduling period T1 is sent in the scheduling period T2.
  • the eNB selects part of the data in the P2-2 packet that cannot be transmitted in the scheduling period T1, and continues to transmit in the scheduling period T2.
  • the synchronization sequences of the services S1 and S2 respectively contain data packets P1-3 and P2-3.
  • the eNB first sends the data packet overflowing in the scheduling period T1 in the scheduling period T2; or, in the scheduling period T2, the eNB puts the data part that the service S2 overflows in the scheduling period T1 in the service S2 in the scheduling period.
  • the traffic data of T2 is transmitted before, which is equivalent to the data of the overflow portion of the service S2 in the scheduling period T1 as a part of the synchronization sequence data mapped by the service S2 in the scheduling period T2.
  • Embodiment 1 is further described below in conjunction with the drawings and specific embodiments.
  • the scheduling period T1 and the scheduling period T2 are grouped into one scheduling period group, and the synchronization sequence of the service S1 includes the data packets P1-1, P1-2, and P1-3, and the synchronization sequence of the service S2 includes the data packet P2-l. , P2-2, P2-3, wherein the data packets Pl-1, Pl-2, P2-l, and P2-2 are mapped to the scheduling period T1, and the data packets P1-3 and P2-3 are mapped to the scheduling period T2. Transmitted, and packet P2-2 cannot be completely transmitted in scheduling period T1.
  • the eNB transmits the entire data packet of the data packet P2-2 that cannot be completely transmitted in the scheduling period T1 in the scheduling period T2, and transmits it as the first data part in the scheduling period T2, that is, in the data.
  • the packets are sent before Pl-3 and P2-3, as shown in the slash fill section.
  • Embodiment 2 is a diagrammatic representation of Embodiment 1:
  • the scheduling period T1 and the scheduling period T2 are grouped into one scheduling period group, and the synchronization sequence of the service S1 includes the data packets P1-1, P1-2, and P1-3, and the synchronization sequence of the service S2 includes the data packet P2-l. , P2-2, P2-3, wherein the data packets Pl-1, Pl-2, P2-l, and P2-2 are mapped to the scheduling period T1, and the data packets P1-3 and P2-3 are mapped to the scheduling period T2. Transmitted, and packet P2-2 cannot be completely transmitted in scheduling period T1.
  • the eNB transmits the entire data packet of the data packet P2-2 that cannot be completely transmitted in the scheduling period T1 in the scheduling period T2, and transmits it as the first data part of the service S2 in the scheduling period T2. That is, after the packet P1-3, before P2-3, as shown in the slash fill section.
  • Embodiment 3 In this embodiment, the scheduling period T1 and the scheduling period T2 are grouped into one scheduling period group, and the synchronization sequence of the service S1 includes the data packets P1-1, P1-2, and P1-3, and the synchronization sequence of the service S2 includes the data packet P2-l. , P2-2, P2-3, wherein the data packets Pl-1, Pl-2, P2-l, and P2-2 are mapped to the scheduling period T1, and the data packets P1-3 and P2-3 are mapped to the scheduling period T2. Transmitted, and packet P2-2 cannot be completely transmitted in scheduling period T1.
  • the eNB transmits part of the data of the data packet P2-2 that cannot be completely transmitted in the scheduling period T1, that is, the data of the overflow part in the scheduling period T2, and performs the first data part in the scheduling period T2.
  • Embodiment 4 is a diagrammatic representation of Embodiment 4:
  • the scheduling period T1 and the scheduling period T2 are grouped into one scheduling period group, and the synchronization sequence of the service S1 includes the data packets P1-1, P1-2, and P1-3, and the synchronization sequence of the service S2 includes the data packet P2-l. , P2-2, P2-3, wherein the data packets Pl-1, Pl-2, P2-l, and P2-2 are mapped to the scheduling period T1, and the data packets P1-3 and P2-3 are mapped to the scheduling period T2. Transmitted, and packet P2-2 cannot be completely transmitted in scheduling period T1.
  • the eNB transmits part of the data of the data packet P2-2 that cannot be completely transmitted in the scheduling period T1, that is, the data of the overflow part in the scheduling period T2, and is the first one of the service S2 in the scheduling period T2.
  • the data portion is sent, ie sent before packets Pl-3, P2-3, as shown in the slash fill section.
  • the data that cannot be transmitted in the scheduling period T1 is continuously transmitted in the scheduling period T2 by the above method, thereby avoiding the data because the service data is in the scheduling period T1. A large amount of packets that result in packet loss.
  • the case where the MCCH message occupies the subframe resource within one scheduling period is not considered. If the MCCH is transmitted at the beginning of a scheduling period, the MCCH may be transmitted as the first part of the scheduling period. In this case, the business data will be sent in the following order in the mapping order.
  • Embodiment 5 if the total packet length that needs to be transmitted during the scheduling period T2 exceeds the total length of the service data that can be transmitted by the scheduling period T2. Since the latter scheduling period of the scheduling period T2 and the scheduling period T2 do not belong to the same scheduling period group, the partially overflowed data will be discarded.
  • the scheduling period T1 and the scheduling period T2 are grouped into one scheduling period group, and the synchronization sequence of the service S1 includes the data packets P1-1, P1-2, and P1-3, and the synchronization sequence of the service S2 includes the data packet P2-l. , P2-2, P2-3, wherein the data packets Pl-1, Pl-2, P2-l, and P2-2 are mapped to the scheduling period T1, and the data packets P1-3 and P2-3 are mapped to the scheduling period T2. Transmitted, and the data packet P2-2 cannot be completely transmitted in the scheduling period T1, and the data packet P2-3 cannot be completely transmitted in the scheduling period T2.
  • the eNB transmits part of the data of the data packet P2-2 that cannot be completely transmitted in the scheduling period T1, that is, the data of the overflow part in the scheduling period T2, and is the first one of the service S3 in the scheduling period T2.
  • the data portion is transmitted, that is, sent before the packets Pl-3, P2-3, as shown in the slash fill portion.
  • the overflow data of the data packet P2-3 since the scheduling period T2 is the last scheduling period in the scheduling period group, the overflow data of the data packet P2-3 cannot be sent in the next scheduling period. Therefore, the overflow data in the packet P2-3 is discarded, and the flag 100 in Fig. 10 indicates the discarded data in the packet P2-3.
  • the transmission of the service data cannot be restarted from the scheduling period T2. Otherwise, the eNB will be inconsistent with other eNBs, and the MBSFN transmission condition will be destroyed.
  • the present invention further provides a device for joint scheduling of multiple scheduling periods in a multimedia broadcast multicast service, including a setting unit and a data packet processing unit;
  • the data packet processing unit is configured to: when the scheduling period of the same scheduling period group exists after the scheduling period in which the data overflow occurs and the data overflow occurs, the data that cannot be sent in the scheduling period in which the data overflow occurs belongs to the same schedule Sent within the subsequent scheduling period of the periodic group;
  • the data packet that cannot be completely transmitted in the previous scheduling period is transmitted in the latter scheduling period.
  • the data packet processing unit is further configured to discard the data of the overflow part when there is a scheduling period of the same scheduling period group after the scheduling period in which the data overflow occurs and the data overflow occurs;
  • the data packet processing unit is further configured to send the corresponding data packet in a corresponding scheduling period according to a mapping order of the data packets when no data overflow occurs.
  • the apparatus further includes a judging unit, configured to determine whether there is a data overflow in the scheduling period in the scheduling period group, and determine whether a scheduling period of the same scheduling period group exists after the scheduling period in which the data overflow occurs, and the judgment result is sent to the data packet. Processing unit.

Landscapes

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

Description

多媒体广播组播业务中多调度周期联合调度的方法及装置 技术领域
本发明涉及长期演进（LTE, Long Term Evolution ) 系统中的业务调度 技术， 尤其是指一种多媒体广播组播业务 ( MBMS , Multimedia Broadcast Multicast Service ) 中多调度周期联合调度的方法及装置。 背景技术
为了有效利用移动网络资源， 第三代合作伙伴计划 （3GPP , 3rd Generation Partnership Project )提出了 MBMS业务， MBMS业务是一种从 一个数据源向多个目标传送数据的点到多点业务， 能实现包括核心网和接 入网在内的网络资源共享， 进而提高网络资源的利用率， 尤其是空中接口 资源。 MBMS业务不仅能够实现纯文本低速率的消息类组播和广播， 而且 还能够实现高速多媒体业务的广播和组播， 能提供多种丰富的视频、 音频 和多媒体业务， 这无疑顺应了未来移动数据发展的趋势， 为 3G的发展提供 了更好的业务前景。
在 3GPP 的 LTE 系统中， MBMS 业务可以釆用单频网多播广播 ( MBSFN, Multicast/Broadcast over Single Frequency Network )技术, 也称 多播单频网技术。 釆用 MBSFN发送的 MBMS业务， 也称为 MBSFN业务， 可在多个小区釆用相同的调制编码格式、 釆用相同的物理资源， 发送相同 内容， MBMS业务多小区传输的特征是：
1 )在 MBSFN区域内同步传输；
2 ) 支持多小区 MBMS传输合并；
3 ) MBMS业务的多播业务信道 ( MTCH, Multicast traffic Channel )和 多播控制信道（MCCH, Multicast Control Channel )在点到多点 （p-T-m ) 模式下映射到传输信道上；
4 ) MBSFN同步区域、 MBSNF区域、 MBSFN传输、 保留小区等， 均 由操作维护半静态配置。
这样， 多个小区的用户设备（ UE , User equipment )可以接收到多个内 容相同的 MBMS数据， 并进行合并处理， 从而可以提高接收信号的增益。 这里， 釆用相同物理资源， 并釆用 MBSFN发送模式发送相同 MBMS业务 的多个小区， 构成一个 MBSFN区域。
在实际组网中， 一个 MBSFN区域上有若干个 MBSFN业务， 这些属于 同一个 MBSFN区域的所有 MBSFN业务称为一个 MBSFN业务组。也就是 说， 一个 MBSFN业务组仅属于一个 MBSFN区域， 一个 MBSFN区域包括 多个小区， 每个小区都配置有完全相同的一个 MBSFN业务组。
具备相同 MBSFN区域的多个 MBSFN业务的数据信道 MTCH、 以及 MBSFN业务的控制信道 MCCH可以复用到一条传输信道， 在 LTE中， 该 传输信道为多播信道 ( MCH, Multicast Channel ); 在通用移动通信系统 ( UMTS )中， 该传输信道为前向接入信道 ( FACH )„ 相同 MBSFN区域的 MCCH和多个 MTCH, 即多条逻辑信道可以映射到同一传输信道上； 一个 MBSFN 区域可以配置一条或多条传输信道， 分别承载一条或多条逻辑信 道。
现有 LTE 的公开技术中， 引入了多播子帧分配模式时机 （MSAP occasion ), 其指示了一个时间段内一条（P ) MCH 所包括的全部多播子帧 资源， 而一个调度周期包含一个或多个 MSAP occasion长度。 所述调度周 期为无线接口周期性配置的时间段， 在该时间段内， 承载业务数据的传输 信道或物理信道配置有一组信道资源， 并在所述调度资源上调度发送特定 的业务数据。
承载在同一个 MCH信道的多个 MTCH通过如下方式进行信道复用： 在一个调度周期内发送的 MTCH的业务数据， 在逻辑信道层次分别进行无 线链路控制（ RLC )协议处理， 包括 RLC串接和分片、 生成 RLC协议数据 单元（ PDU ),也就是传输信道的媒体接入控制（ MAC )服务数据单元（ SDU ), 一个或多个 MAC SDU承载在一个 MAC PDU上，多个 MAC SDU通过 MAC 串接功能复用在同一个 MAC PDU中。 来自不同 MTCH的 MAC PDU按照 预定的顺序在传输信道依次发送。 在一个调度周期内， 一个 MTCH的数据 连续发送， 也就是说， 一个业务的数据连续占用 MCH信道的 MBSFN子帧 资源， 直到该业务在该调度周期内需要发送的业务数据全部发送完毕。
图 1为一个调度周期内两个业务动态复用调度的示意图， 图 1 中， 斜 线填充的部分表示业务 S1 , 空白填充的部分表示业务 S2, 竖线填充的部分 表示填充， 可以看出， 在调度周期 1和调度周期 2中， 业务 S1和业务 S2 均分别动态复用。 图 2为一个 MBSFN子帧承载的 MAC PDU中两个业务 复用同一个 MAC PDU的方法示意图， 也就是 MAC串接的方法。 图 2中， 一个 MAC PDU包括 MAC头、 MAC控制单元、 若干个 MAC SDU以及填 充（opt )部分， 其中， MAC头还包括 MAC子头 1至 MAC子头 6, 多个 MAC SDU串接。
在每个调度周期还发送业务的动态调度信息， 本文中简称为调度信息， 调度信息携带有 MTCH到 MBSFN子帧的映射信息， UE读取调度信息可以 知道每个 MTCH被分配在哪些 MBSFN子帧上， 具体的调度信息可以是每 个业务在一个调度周期内的开始、 结束子帧位置信息、 业务数据占据的 MBSFN子帧个数信息， 所述的子帧位置为 （P ) MCH信道配置的 MBSFN 子帧在一个时间段内的相对位置、 或者偏移、 或者索引。
在 3GPP UMTS技术中， 存在如下的资源分配方式： MBSFN时分复用 ( TDM ) 方式， 多个业务通过时分复用共享同一个传输信道、 或物理信道 资源， 每个业务在一个 TDM周期内占据固定的资源位置， 称为 TDM偏移 和重复长度； 一个或多个 TDM周期构成了一个业务的调度周期。 在一个调 度周期内， 对所述业务的数据进行 RLC层处理时， 进行 RLC串接和分片， 并将生成的 RLC PDU承载到传输信道。 在上述方式中， 每个业务占用的资 源都是独占的， 也就是： 不存在业务间数据共享同一个传输时间间隔的无 线信道资源。
在 UMTS技术中， 还存在如下的资源分配和调度方式： 一个或多个业 务通过传输信道、 或物理信道复用共享无线信道资源， 这里的无线信道资 源是指 UMTS系统中的扩频码。 在无线接口确定周期性的调度周期， 在每 个调度周期内， 网元调度一个或多个业务的数据进行发送。 在这种方式下， 一个或多个业务的业务数据单元可以共享同一个传输时间间隔的无线信道 资源。
在 UMTS技术中， 同样存在调度信息， 调度信息承载在多点调度信道 ( MSCH )上， 每个承载 MTCH的 FACH信道承载有一条 MSCH信道， 用 于指示 FACH信道承载 MTCH数据的调度信息， 调度信息具体的表现为业 务数据调度的开始时间、 持续长度等。 与 LTE技术不同， 该调度信息的发 送周期和调度周期没有严格的对应关系。
为实现 MBMS业务在多个网元实体如基站网元的小区间的 MBSFN方 式发送， 现有技术中提供了一种同步协议处理（SYNC )方式， 其网元架构 及处理原理如图 3所示， 该方法包括上层网元和 N个下层网元， 该 SYNC 协议方式包括以下处理：
步骤 10:上层网元发送 MBMS业务数据包到各个下层网元，该 MBMS 业务数据包承载了业务数据， 并携带有时间戳信息、 数据包序列号信息、 累计业务数据长度信息等等， 上层网元对一个或多个连续的 MBMS业务数 据包标识相同的时间戳信息， 这些标记有相同时间戳的数据包组成一个数 据笑发 ( data burst )或称为同步序歹1 J ( synchronization Sequence ), 目 4|5两个 同步序列的时间戳差为同步序列的长度， 或称为 SYNC周期。
目前， 可以通过下述两种方式指示每个同步序列的时间戳信息： 一种 是， 在上述同步序列包含的每个数据包中包含该同步序列在无线接口开始 发送的参考时间信息； 另一种是， 在上述同步序列中的每个数据包中包含 上一个同步序列在无线接口开始发送的参考时间信息。
步骤 11： 在每个同步序列最后， 上层网元还发送一种 SYNC控制帧， 该控制帧只携带前一个同步序列的数据包总个数、 数据包总长度信息， 用 于下层网元检测一个同步序列的结束， 并获知一个同步序列的总数据长度 和数据包个数。
步骤 12: 下层网元对同一个同步序列中的业务数据包所携带的业务数 据， 在其时间戳对应的调度周期开始在无线接口依次发送。
根据 SYNC周期和调度周期长度， 同步序列到调度周期存在多种映射 关系， 包括： 多个同步序列映射到一个调度周期， 此时 SYNC周期长度为 调度周期的整数倍分之一， 一个 SYNC 序列映射到一个调度周期， 此时 SYNC周期长度等于调度周期。
优选的， SYNC 周期长度等于调度周期， 则一个同步序列映射到一个 调度周期； 在多个业务动态复用信道时， 每个业务的一个同步序列数据映 射到同一个调度周期。
在上述调度过程中， 按照现有技术， 如果一个调度周期内映射的同步 序列的数据不能在所述的调度周期内发送， 则将出现数据溢出， 溢出部分 的数据将被丟弃。 在多业务复用信道的情况下， 将按照业务的优先级， 选 择一个业务或多个业务的数据进行溢出处理。 具体例子如图 4所示， 业务
S1和业务 S2共享同一个信道， Pl-1、 P1-2为业务 SI的数据包， P2-l、 P2-2 为业务 S2的数据包。在图 4的调度周期 T1和 T2是两个调度周期中， 业务 数据 S1根据 SYNC协议， 在调度周期 T1和调度周期 T2中都有业务数据 需要发送。在调度周期 T1中， 因为业务 S1和 S2的业务数据量超过了调度 周期 T1所对应的信道资源能发送的最大能力， 因而出现业务 S2的部分业 务数据， 即 P2-2数据包的部分业务数据不能发送的情况。
现有技术中， 需要对溢出的数据进行溢出处理， 原因是： 每个调度周 期的开始发送的业务数据， 都是确定的从一个特定的同步序列的数据包开 始发送， 也就是说， 映射到前一个调度周期的数据不会在后一个调度周期 内发送， 即使前一个调度周期内的数据不能全部发送， 也不会在后一个调 度周期内发送。 并且， 在每个调度周期的开始， 基站网元对用户面协议进 行复位。 例如： 在 UMTS系统中， 每个调度周期开始时， 业务数据的 RLC PDU的序列号将进行复位处理， 以保证每个调度周期的开始 RLC PDU的 序列号都是从一个固定值开始分配。 上述处理方法的好处是： 对于一个新 加入的基站网元， 或一个发生重启的基站网元， 在任何时刻都可以根据 SYNC 协议， 确定其它网元在某一个调度周期内发送的数据、 和无线接口 协议尤其是 RLC层的协议状态 （例如 RLC序列号）， 这样， 该网元能和其 他基站网元保持同步的发送业务数据， 而不需要考虑在此之前的调度周期 内， 其它基站网元是如何处理数据的。 也就是说， 每个调度周期的处理存 在独立性， 避免了相互之间的干扰， 提供了重启的网元重新和其它网元保 持同步发送业务的机会。
但上述处理方法也存在一定的问题： 由于 MBMS业务的动态特性， 业 务数据在不同的调度周期内的流量变化会非常大， 不同调度周期内需要发 送的业务数据有较大差别， 尤其是对一个业务独享一个信道， 或多个业务 复用信道而业务数量比较少的时候。 而资源也不会配置为无限大来满足业 务流量的变化， 那么， 在业务流量变化较大、 而可配置的资源不足以满足 最大可能的业务数据速率时， 按照现有技术的处理方式， 业务数据的丟失 将是不可避免的， 而丟弃相应业务数据将会直接导致业务服务质量的下降。 发明内容
有鉴于此， 本发明的主要目的在于提供一种多媒体广播组播业务中多 调度周期联合调度的方法及装置， 能尽可能地避免因为业务数据溢出而丟 弃业务数据， 从而提高业务服务质量。
为达到上述目的， 本发明的技术方案是这样实现的：
本发明提供了一种多媒体广播组播业务中多调度周期联合调度的方 有调度周期出现数据溢出， 且出现数据溢出的调度周期之后存在与其 属于同一调度周期组的调度周期时， 将不能在出现数据溢出的调度周期内 发送的数据在与其属于同一调度周期组的后续调度周期内发送。
该方法进一步包括： 有调度周期出现数据溢出， 且出现数据溢出的调 度周期之后不存在与其属于同一调度周期组的调度周期时， 丟弃溢出部分 的数据。
上述方案中， 所述将不能在出现数据溢出的调度周期内发送的数据在 与其属于同一调度周期组的后续调度周期内发送为： 将不能在前一个调度 周期内发送的数据在与其属于同一个调度周期组的下一个调度周期内发 送。
上述方案中， 所述在同一调度周期组的后续调度周期内发送的数据为 不能在出现数据溢出的调度周期内完整发送的数据包的整个数据包； 或为 不能在出现数据溢出的调度周期内完整发送的数据包的部分数据。
上述方案中， 所述在同一调度周期组的后续调度周期内发送为： 作为 所述后续调度周期内的第一个数据部分发送； 或作为所述后续调度周期内 该溢出数据对应的业务的第一个数据部分发送。
上述方案中， 所述数据发送由下层网元完成， 所述下层网元为演进基 站、 或无线网络控制器、 或节点 B ( NB+ )。 该方法进一步包括： 失去同步的下层网元从下一个调度周期组的起始 边界， 开始或重新开始与其他下层网元同步发送业务。
本发明还提供了一种多媒体广播组播业务中多调度周期联合调度的装 置， 包括设置单元和数据包处理单元； 其中， 数据包处理单元， 用于在出现数据溢出且出现数据溢出的调度周期之 后存在与其属于同一调度周期组的调度周期时， 将不能在出现数据溢出的 调度周期内发送的数据在与其属于同一调度周期组的后续调度周期内发 送。
其中， 所述数据包处理单元， 还用于在出现数据溢出且出现数据溢出 的调度周期之后不存在与其属于同一调度周期组的调度周期时， 丟弃溢出 部分的数据。
上述方案中， 该装置进一步包括判断单元， 用于判断调度周期组中是 否有调度周期出现数据溢出， 并判断出现数据溢出的调度周期之后是否存 在与其属于同一调度周期组的调度周期， 将判断结果发送给数据包处理单 元。
本发明所提供的多媒体广播组播业务中多调度周期联合调度的方法及 期组中有调度周期出现数据溢出时， 先确定出现数据溢出的调度周期之后 是否存在与其属于同一调度周期组的调度周期， 存在时将不能在出现数据 溢出的调度周期内发送的数据延迟到同一调度周期组的后续调度周期内发 送， 如此， 可避免现有技术中将溢出部分数据完全丟弃所导致的业务服务 质量下降。
另外， 本发明通过调度周期组的设置， 提供了重新同步的特性， 对于 失去同步的下层网元， 可使其以调度周期组为单位， 从发生失步的调度周 期组的下一个调度周期组的起始边界开始， 开始或重新开始与其他下层网 元保持同步的发送接收到的业务数据， 从而保证各下层网元之间的数据收 发同步。 附图说明
图 1为现有技术中一个调度周期内两个业务动态复用调度的示意图； 图 2为动态复用调度中两个业务的数据复用一个 MAC PDU的示意图； 图 3为现有技术中 SYNC协议方式的网元架构及处理原理示意图； 图 4为现有技术调度中出现业务数据溢出的示意图；
图 5a为本发明方法的实现流程示意图；
图 5b为本发明方法的一种实现流程示意图；
图 6为下层网元将不能在前一个调度周期内完整发送的数据包在后一 个调度周期内作为第一个数据部分进行发送的示意图；
图 7为下层网元将不能在前一个调度周期内完整发送的数据包在后一 个调度周期内作为其对应的业务的第一个数据部分进行发送的示意图； 图 8为下层网元将不能在前一个调度周期内发送的数据包的部分数据 在下一个调度周期内作为第一个数据部分进行发送的示意图；
图 9为下层网元将不能在前一个调度周期中发送的数据包的部分数据 在下一个调度周期内作为其对应的业务的第一个数据部分进行发送的示意 图；
图 10为下层网元将一个调度周期组内最后一个调度周期中不能发送的 数据进行丟弃的示意图。 具体实施方式 期组， 当一个调度周期组中有调度周期出现数据溢出， 且出现数据溢出的 调度周期之后存在与其属于同一调度周期组的调度周期时， 将不能在出现 数据溢出的调度周期内完整发送的数据延迟到同一调度周期组的后续调度 周期内发送。
进一步地， 在有调度周期出现数据溢出， 且出现数据溢出的调度周期 之后不存在与其属于同一调度周期组的调度周期时， 将溢出部分的数据丟 弃。
这里， 由下层网元将多个相邻的调度周期组成调度周期组， 且每个调 度周期只属于一个调度周期组。 所述溢出是指， 根据同步序列的时间戳映 射到一个调度周期内的同步序列数据不能在所映射到的调度周期内发送， 也就是说， 映射到一个调度周期内的同步序列数据超过该调度周期内信道 资源的发送容量； 对于溢出部分的业务数据可简称为溢出数据。
优选的， 所述将不能在出现数据溢出的调度周期内完整发送的数据延 迟到同一调度周期组的后续调度周期内发送是指： 将不能在出现数据溢出 的调度周期内完整发送的数据延迟到与其属于同一调度周期组的下一个调 度周期内发送。 当然， 也可以在出现数据溢出的调度周期后续属于同一调 度周期组的第二个调度周期、 或第三个调度周期等发送。 发送的数据包的整个数据包， 也可以是不能完整发送的数据包中的部分数 据。 溢出数据在另一调度周期发送时可以作为所述另一调度周期的第一个 数据部分发送， 即： 在通过时间戳映射到相应调度周期的业务数据之前发 送； 也可以作为所述另一调度周期内该溢出数据对应的业务的第一个数据 部分发送， 即： 将溢出部分的数据在相应调度周期内该溢出数据对应的业 务需要发送的数据之前发送。
以不能在前一个调度周期内完整发送的数据包在后一个调度周期内发 送举例来说， 假设业务 S2同步序列中的数据包 P2-2不能在调度周期 1 中 完整发送， 调度周期 1相邻的下一个调度周期为调度周期 2 , 且调度周期 1 和调度周期 2组成一个调度周期组。 那么， 可以将整个 P2-2数据包在调度 周期 2中发送； 也可以仅将 P2-2数据包中在调度周期 1内溢出部分的数据 在调度周期 2中发送。 可以将要在调度周期 2中发送的整个 P2-2数据包或 P2-2数据包中溢出部分的数据在调度周期 2的第一个数据部分发送， 这种 情况下不考虑第一个数据部分是否为发送业务 S2的数据部分； 还可以将要 在调度周期 2中发送的整个 P2-2数据包或 P2-2数据包中溢出部分的数据在 调度周期 2中对应业务 S2的第一个数据部分发送， 这种情况下， 只有等到 开始调度业务 S2时，才将要在调度周期 2中发送的整个 P2-2数据包或 P2-2 数据包中溢出部分的数据作为业务 S2的第一数据部分发送。
本发明中， 对于失去同步的下层网元， 可使其以调度周期组为单位保 持数据收发同步， 从下一个调度周期组的起始边界开始， 开始或重新开始 与其他下层保持同步的发送接收到的业务数据。 具体实现重新同步的过程 是： 所述下层网元先获得调度周期组的大小和边界， 并在当前时间之后的 一个调度周期组的开始， 重新开始调度接收到的业务数据， 并发送到无线 接口。
这里， 所述失去同步的下层网元为： 在业务进行过程中， 新加入到业 务发送的下层网元； 或者， 在发送业务过程中， 发生了重启后又加入到业 务发送的下层网元； 或者， 在业务发送过程中， 未接收到连续多个同步序 列而导致失步的下层网元； 或者， 由于其它原因导致不能判断如何进行发 送业务不会导致对邻区干扰的下层网元。
所述调度周期组的边界可通过如下方式计算： SFN mod TN = 0, 其中， SFN是系统帧号， TN是以 SFN个数为单位的调度周期组的长度。
本发明多媒体广播组播业务中多调度周期联合调度的方法， 如图 5a所 示， 包括以下步骤： 这里, 步步骤骤 550011aa:: 出出现现数数据据溢溢出出时时，， 判判断断出出现现数数据据溢溢出出的的调调度度周周期期之之后后是是否否 存存在在与与其其属属于于同同一一调调度度周周期期组组的的调调度度周周期期，， 如如果果存存在在，， 则则将将不不能能在在出出现现数数 据据溢溢出出的的调调度度周周期期内内发发送送的的数数据据延延迟迟到到与与其其属属于于同同一一调调度度周周期期组组的的后后续续调调 度度周周期期内内发发送送；； 否否则则丟丟弃弃溢溢出出部部分分的的数数据据。。
较较佳佳的的，， 将将不不能能在在前前一一个个调调度度周周期期内内完完整整发发送送的的数数据据包包在在后后一一个个调调度度 周周期期内内发发送送，， 其其具具体体的的处处理理流流程程如如图图 55bb所所示示，， 包包括括以以下下步步骤骤：：
Figure imgf000014_0001
步骤 501b: 出现数据溢出时， 判断出现数据溢出的调度周期是否为本 调度周期组中的最后一个调度周期， 如果不是， 则将不能在前一个调度周 期内发送的数据在下一个调度周期内发送； 如果是， 则丟弃溢出部分的数 据。
这里， 所述在下一个调度周期内发送， 可以是发送前一个调度周期内 不能完整发送的数据包的整个数据包； 也可以是发送前一个调度周期内不 能完整发送的数据包中的部分数据； 所述在下一个调度周期内发送是指： 在下一个调度周期内作为第一个数据部分发送， 或在下一个调度周期内作 为其对应的业务的第一个数据部分发送。
下文均以将不能在前一个调度周期内完整发送的数据包在后一个调度 周期内发送为例， 具体说明本发明方法的实现， 在同一调度周期组中的后 续其他调度周期发送的原理与流程与此基本相同。
本发明的方法适用于类似图 3 所示的网络架构中， 本发明中， 所述上 层网元和下层网元分别为 SYNC协议的两个终结点， 具体的， 上层网元可 以是广播多播业务中心（BMSC )、 或 MBMS业务网关（MGW )、 或 UMTS 网络中的网关通用分组无线业务支持节点 （GGSN ); 下层网元可以是演进 基站 eNB、 或无线网络控制器（RNC )、 或 NB+等等。
下层网元接收上层网元发送的同步序列， 并按照同步序列的时间戳信 息， 将同步序列的数据包映射到相应的调度周期内发送； 在多个业务动态 复用信道资源时， 所述多个业务映射到同一个调度周期的同步序列按照预 定顺序依次在所述调度周期内发送， 如图 5所示， 业务 S1的同步序列中有 数据包 Pl-1、 P1-2, 业务 S2的同步序列中有数据包 P2-l、 P2-2, 分别映射 到调度周期 T1中， 并在调度周期 T1内按预定顺序依次发送数据包 Pl-1、 Pl-2、 P2-l。
本发明中， 下层网元将多个调度周期组成一个调度周期组， 在一个调 度周期内， 如果出现溢出数据的情况， 则按照预定规则选择进行溢出处理 的业务， 并确定需要溢出的业务数据。 如果所述出现溢出的调度周期与其 下一个调度周期属于同一个调度周期组， 则溢出部分的数据在后一个调度 周期中发送； 如果所述出现溢出的调度周期与其下一个调度周期不属于同 一个调度周期组， 则溢出部分的数据被丟弃。 其中， 所述预定规则可以是 预设的优先级、 或预设的调度规则等等。
这里， 所述调度周期为无线接口的一个时间段， 对应一组无线信道资 源。具体地，对于 LTE系统来说，所述调度周期可以包含一个或多个 MBSFN 资源分配周期、 或 MSAP周期、 或 MSAP occasion长度。 对于 UMTS系统 而言， 所述调度周期可以包含一个或多个 MBSFN TDM周期大小、 或一段 以传输时间间隔 （ ΤΉ )为单位表示的无线接口时间段。
上述同步序列为上层网元发送到下层网元的一组业务数据包， 所述业 务数据包携带有时间戳信息， 同一个同步序列的业务数据包携带有相同的 时间戳信息。 所述业务数据包还携带有数据包序列号和累计长度信息， 分 别表示一个业务数据包在一个同步序列中的序号， 以及一个业务数据包之 前的数据包的数据总长度。 度周期组， 具体方式可以是： 下层网元通过配置管理网元获得组成调度周 期组的连续的调度周期个数 N, 所述 N为半静态配置参数； 所述调度周期 组具体表现为在无线接口每 N个调度周期组成一个调度周期组。 其中， 连 续的调度周期也可以说是两两相邻的调度周期。
一般， 下层网元按照下述方法确定是否需要在一个调度周期内进行溢 出处理， 并选择进行溢出处理的业务： 下层网元根据一个调度周期内的信 道资源数量、 该调度周期内需要发送的业务数据的数量， 确定是否需要进 行业务数据溢出处理， 如果需要发送的业务数据的总量超过在该调度周期 内信道资源能发送到最大业务数据量， 则下层网元确定出现业务数据的溢 出， 并计算得到溢出的数据量的大小。
可选的， 下层网元可通过如下方式获得需要在一个调度周期内发送的 业务的数量： 下层网元通过统计累加一个同步序列中所有数据包的长度， 得到一个业务在调度周期内发送的数据长度； 或者， 下层网元通过检测下 一个同步序列的数据包或 SYNC控制帧携带的该同步序列的数据总长度和 数据包个数， 得到所述同步序列的数据包总长度和数据包个数。
如果在某调度周期内将发生业务数据溢出， 则在多个业务复用到同一 个调度周期的信道资源时， 下层网元根据预先配置的业务发送顺序、 或业 务优先级， 选择有业务数据需要发送的多个业务中的一个或多个业务的数 据进行溢出处理。 只有一个业务复用到所述调度周期时为一特例， 这种情 况下， 直接确定需要溢出处理的业务数据即可。
具体地， 下层网元确定需要进行溢出处理的数据的方法是： 下层网元将不能在所属调度周期内发送的一个或多个完整的业务数据 包作为需要溢出处理的业务数据， 换句话说就是， 如果某个业务数据包不 能完整的在一个调度周期内发送， 则对该业务数据包的整个数据包进行溢 出处理；
或者， 下层网元确定不能在所属调度周期内发送的一个或多个完整的 业务数据包进行溢出处理， 并且， 如果一个业务数据包的部分数据能在所 属调度周期内发送， 则对该业务数据包不能发送的部分数据进行溢出处理。
举个具体应用实例来说： 在 LTE系统中， 上层网元为 BMSC, 下层网 元为 eNB。 上层网元向下层网元发送业务时， 釆用 SYNC协议处理， 将业 务数据包组成一个个同步序列， 每个同步序列的数据包标识相同的时间戳， 用于指示 eNB当前同步序列或前一个同步序列在无线接口发送的开始时间 信息；每个 SYNC协议数据包还携带数据包序列号和数据包累计长度信息； 除了业务数据包之外， BMSC还向 eNB发送 SYNC控制包， 携带前一个同 步序列的数据包总个数和总长度。
在无线接口， eNB配置调度周期长度为 SYNC周期的整数倍， 或等于 SYNC周期。 每个调度周期包含一组 MBSFN子帧资源。 典型的， SYNC周 期和无线接口调度周期分别为 320ms, 调度周期的边界典型值为 SFN mod 32 = 0, SFN为系统帧号， 每个系统帧长度为 10ms, SFN最大值为 1024, 则上式表示每隔 320ms, 调度周期周期性的配置。
eNB接收到的 BMSC发送的同步序列后， 按照时间戳指示映射到无线 接口的调度周期， 具体的， eNB 将同步序列的数据包映射到其发送时间戳 指示的时间之后的调度周期、 或正对的调度周期开始发送。
eNB 将在无线接口釆用动态调度的方式将多个业务复用到同一个业务 信道， 具体的， eNB根据 SYNC协议将映射到一个传输信道如 MCH 的一 个调度周期内的多个业务， 按照预定的业务发送顺序， 依次将多个业务数 据在所述调度周期内的无线子帧资源上发送。 在本应用实例中， 两个业务
S1和 S2映射到信道 MCH中。
在调度周期 T1中，业务 S1和 S2映射到该调度周期的数据包总长度超 过了 MCH信道在该调度周期能发送的业务总量。 具体的， 业务 S1的同步 序列包括两个数据包 P1-1和 P1-2 , 业务 S2的同步序列包含两个业务数据 包 P2-1 , P2-2。 其长度分别为 Ll-1 , Ll-2, L2-1 , L2-2。
调度周期 Tl内能发送的业务数据包总长度为 L,如果四个数据包 Pl-1、 Pl-2、 P2-l、 P2-2的总长度超过 L, 则意味着在调度周期 Tl内， 将发生数 据溢出， 按照业务优先级， eNB选择 S2的部分数据进行溢出处理。
eNB 将每两个调度周期设为一个调度周期组， 也就是说， 调度周期组 长度为 640ms, 则每 640ms为一个调度周期组， 其边界将分别为 0, 640、 1280ms—。
由于调度周期 T1的后一个调度周期 T2与调度周期 T1属于同一个调度 周期组， 则在本发明中， 调度周期 T1 内溢出的数据将在调度周期 T2内发 送。
可选的， eNB选择不能在调度周期 T1 中完整发送的业务数据包 P2-2 整个在调度周期 T2中发送。 或者， eNB选择 P2-2数据包中不能在调度周 期 T1内发送的部分数据， 在调度周期 T2中继续发送。 在调度周期 T2 , 业 务 S1和 S2的同步序列分别包含数据包 P1-3和 P2-3。
可选的， eNB在调度周期 T2内先发送在调度周期 T1中溢出的数据包； 或者， eNB在调度周期 T2内，将业务 S2在调度周期 T1内溢出的数据部分 放在业务 S2在调度周期 T2的业务数据之前发送，相当于将业务 S2在调度 周期 T1中溢出部分的数据当作业务 S2在调度周期 T2映射的同步序列数据 的一部分。
下面结合附图和具体实施例进一步说明本发明方法的实现。 实施例一：
本实施例中， 将调度周期 T1和调度周期 T2组成一个调度周期组， 业 务 S1的同步序列包含数据包 Pl-1、 Pl-2、 P1-3 , 业务 S2的同步序列包含 数据包 P2-l、 P2-2、 P2-3 , 其中， 数据包 Pl-1、 Pl-2、 P2-l、 P2-2映射到 调度周期 Tl中发送， 数据包 Pl-3、 P2-3映射到调度周期 T2中发送， 且数 据包 P2-2不能在调度周期 T1中完整发送。
那么，如图 6所示，由于发送数据包 P2-2时发生数据溢出，数据包 P2-2 是映射在调度周期 T1中的， 且调度周期 T1不是本调度周期组最后一个调 度周期， 因此， 本实施例中， eNB将不能在调度周期 T1中完整发送的数据 包 P2-2的整个数据包在调度周期 T2中发送，且在调度周期 T2中作为第一 个数据部分进行发送， 即在数据包 Pl-3、 P2-3之前发送， 如斜线填充部分 所示。
实施例二：
本实施例中， 将调度周期 T1和调度周期 T2组成一个调度周期组， 业 务 S1的同步序列包含数据包 Pl-1、 Pl-2、 P1-3 , 业务 S2的同步序列包含 数据包 P2-l、 P2-2、 P2-3 , 其中， 数据包 Pl-1、 Pl-2、 P2-l、 P2-2映射到 调度周期 Tl中发送， 数据包 Pl-3、 P2-3映射到调度周期 T2中发送， 且数 据包 P2-2不能在调度周期 T1中完整发送。
那么，如图 7所示，由于发送数据包 P2-2时发生数据溢出，数据包 P2-2 是映射在调度周期 T1中的， 且调度周期 T1不是本调度周期组最后一个调 度周期， 因此， 本实施例中， eNB将不能在调度周期 T1中完整发送的数据 包 P2-2的整个数据包在调度周期 T2中发送，且在调度周期 T2中作为业务 S2的第一个数据部分进行发送， 即在数据包 P1-3之后、 P2-3之前发送， 如 斜线填充部分所示。
实施例三： 本实施例中， 将调度周期 Tl和调度周期 T2组成一个调度周期组， 业 务 S1的同步序列包含数据包 Pl-1、 Pl-2、 P1-3 , 业务 S2的同步序列包含 数据包 P2-l、 P2-2、 P2-3 , 其中， 数据包 Pl-1、 Pl-2、 P2-l、 P2-2映射到 调度周期 Tl中发送， 数据包 Pl-3、 P2-3映射到调度周期 T2中发送， 且数 据包 P2-2不能在调度周期 T1中完整发送。
那么，如图 8所示，由于发送数据包 P2-2时发生数据溢出，数据包 P2-2 是映射在调度周期 T1中的， 且调度周期 T1不是本调度周期组最后一个调 度周期， 因此， 本实施例中， eNB将不能在调度周期 T1中完整发送的数据 包 P2-2的部分数据， 即溢出部分的数据在调度周期 T2中发送， 且在调度 周期 T2中作为第一个数据部分进行发送，即在数据包 Ρ1-3、Ρ2-3之前发送， 如斜线填充部分所示。
实施例四：
本实施例中， 将调度周期 T1和调度周期 T2组成一个调度周期组， 业 务 S1的同步序列包含数据包 Pl-1、 Pl-2、 P1-3 , 业务 S2的同步序列包含 数据包 P2-l、 P2-2、 P2-3 , 其中， 数据包 Pl-1、 Pl-2、 P2-l、 P2-2映射到 调度周期 Tl中发送， 数据包 Pl-3、 P2-3映射到调度周期 T2中发送， 且数 据包 P2-2不能在调度周期 T1中完整发送。
那么，如图 9所示，由于发送数据包 P2-2时发生数据溢出，数据包 P2-2 是映射在调度周期 T1中的， 且调度周期 T1不是本调度周期组最后一个调 度周期， 因此， 本实施例中， eNB将不能在调度周期 T1中完整发送的数据 包 P2-2的部分数据， 即溢出部分的数据在调度周期 T2中发送， 且在调度 周期 T2中作为业务 S2的第一个数据部分进行发送，即在数据包 Pl-3、 P2-3 之前发送， 如斜线填充部分所示。
上述实施例中， 在调度周期 T1内不能发送的数据， 通过上述方法将在 调度周期 T2内继续发送， 从而避免了因为业务数据在调度周期 T1的数据 量较大而导致丟包的情况。
在上述例子中， 没有考虑到 MCCH消息占据一个调度周期内子帧资源 的情况， 如果在一个调度周期的开始发送 MCCH, 则 MCCH可能作为该调 度周期内的第一个部分进行发送。 这种情况下， 业务数据将在其后面按映 射顺序发送。
但是，如果在调度周期 T2内需要发送的总数据包长度也超过了调度周 期 T2能发送的业务数据的总长度。 因为调度周期 T2的后一个调度周期与 调度周期 T2不属于同一个调度周期组， 则该部分溢出的数据将被丟弃。 实施例五：
本实施例中， 将调度周期 T1和调度周期 T2组成一个调度周期组， 业 务 S1的同步序列包含数据包 Pl-1、 Pl-2、 P1-3 , 业务 S2的同步序列包含 数据包 P2-l、 P2-2、 P2-3 , 其中， 数据包 Pl-1、 Pl-2、 P2-l、 P2-2映射到 调度周期 Tl中发送， 数据包 Pl-3、 P2-3映射到调度周期 T2中发送， 且数 据包 P2-2不能在调度周期 T1中完整发送， 数据包 P2-3也不能在调度周期 T2中完整发送。
那么， 如图 10所示， 由于发送数据包 P2-2时发生数据溢出， 数据包 P2-2是映射在调度周期 T1中的， 且调度周期 T1不是本调度周期组最后一 个调度周期， 因此， 本实施例中， eNB将不能在调度周期 T1中完整发送的 数据包 P2-2的部分数据， 即溢出部分的数据在调度周期 T2中发送， 且在 调度周期 T2中作为业务 S3的第一个数据部分进行发送，即在数据包 Pl-3、 P2-3之前发送， 如斜线填充部分所示。
而对于数据包 P2-3的溢出数据， 如点填充的部分所示， 由于调度周期 T2是本调度周期组中最后一个调度周期，数据包 P2-3的溢出数据无法在其 下一个调度周期发送， 所以， 将数据包 P2-3中的溢出数据丟弃， 图 10中标 记 100表示数据包 P2-3中被丟弃的数据。 对于一个失步的 eNB, 由于不知道调度周期 T1溢出到调度周期 T2的 数据包的长度， 所以无法从调度周期 T2就重新开始发送业务数据。 否则， 将会导致该 eNB与其他 eNB的不一致， 破坏 MBSFN发送条件。
从调度周期 T3开始， 由于 eNB发送的数据不包含前一个调度周期应 该发送的数据， 只包含根据 SYNC协议映射到该调度周期的业务数据， 这 样， 该失步的 eNB, 可以从调度周期 T3开始， 重新在无线接口发送业务数 据。 因为从调度周期 T3的发送只与 SYNC协议相关， 与前一个调度周期的 发送状态、 是否溢出无关。 无论调度周期 T3之前各个 eNB是如何处理调 度的， 从调度周期 T3开始的一个调度周期组内， 各个 eNB的处理将完全 保持一致。
为实现上述方法， 本发明还提供了一种多媒体广播组播业务中多调度 周期联合调度的装置， 包括设置单元和数据包处理单元； 其中，
Figure imgf000022_0001
数据包处理单元， 用于在出现数据溢出、 且出现数据溢出的调度周期 之后存在与其属于同一调度周期组的调度周期时， 将不能在出现数据溢出 的调度周期内发送的数据在与其属于同一调度周期组的后续调度周期内发 送；
较佳的， 将不能在前一个调度周期内完整发送的数据包在后一个调度 周期内发送。
所述数据包处理单元， 还用于在出现数据溢出、 且出现数据溢出的调 度周期之后存在与其属于同一调度周期组的调度周期时， 丟弃溢出部分的 数据；
所述数据包处理单元， 还用于在未出现数据溢出时， 按照数据包的映 射顺序在相应调度周期中发送相应数据包。 该装置还包括判断单元， 用于判断调度周期组中是否有调度周期出现 数据溢出， 并判断出现数据溢出的调度周期之后是否存在与其属于同一调 度周期组的调度周期， 将判断结果发送给数据包处理单元。
以上所述， 仅为本发明的较佳实施例而已， 并非用于限定本发明的保 护范围， 凡在本发明的精神和原则之内所作的任何修改、 等同替换和改进 等， 均应包含在本发明的保护范围之内。

Claims

权利要求书
1、 一种多媒体广播组播业务中多调度周期联合调度的方法， 其特征在 于， 该方法包括： 有调度周期出现数据溢出， 且出现数据溢出的调度周期之后存在与其 属于同一调度周期组的调度周期时， 将不能在出现数据溢出的调度周期内 发送的数据在与其属于同一调度周期组的后续调度周期内发送。
2、 根据权利要求 1所述的方法， 其特征在于， 该方法进一步包括： 有 调度周期出现数据溢出， 且出现数据溢出的调度周期之后不存在与其属于 同一调度周期组的调度周期时， 丟弃溢出部分的数据。
3、 根据权利要求 1所述的方法， 其特征在于， 所述将不能在出现数据 溢出的调度周期内发送的数据在与其属于同一调度周期组的后续调度周期 内发送为： 将不能在前一个调度周期内发送的数据在与其属于同一个调度 周期组的下一个调度周期内发送。
4、 根据权利要求 1或 3所述的方法， 其特征在于， 所述在同一调度周 期组的后续调度周期内发送的数据为不能在出现数据溢出的调度周期内完 整发送的数据包的整个数据包； 或为不能在出现数据溢出的调度周期内完 整发送的数据包的部分数据。
5、 根据权利要求 4所述的方法， 其特征在于， 所述在同一调度周期组 的后续调度周期内发送为： 作为所述后续调度周期内的第一个数据部分发 送； 或作为所述后续调度周期内该溢出数据对应的业务的第一个数据部分 发送。
6、 根据权利要求 1或 3所述的方法， 其特征在于， 所述数据发送由下 层网元完成， 所述下层网元为演进基站 eNB、 或无线网络控制器（RNC )、 或节点 B ( NB+ )。
7、 根据权利要求 6所述的方法， 其特征在于， 该方法进一步包括： 失 去同步的下层网元从下一个调度周期组的起始边界， 开始或重新开始与其 他下层网元同步发送业务。
8、 一种多媒体广播组播业务中多调度周期联合调度的装置， 其特征在 于， 该装置包括设置单元和数据包处理单元； 其中， 数据包处理单元， 用于在出现数据溢出且出现数据溢出的调度周期之 后存在与其属于同一调度周期组的调度周期时， 将不能在出现数据溢出的 调度周期内发送的数据在与其属于同一调度周期组的后续调度周期内发 送。
9、 根据权利要求 8所述的装置， 其特征在于， 所述数据包处理单元， 还用于在出现数据溢出且出现数据溢出的调度周期之后不存在与其属于同 一调度周期组的调度周期时， 丟弃溢出部分的数据。
10、 根据权利要求 8或 9所述的装置， 其特征在于， 该装置进一步包 括判断单元， 用于判断调度周期组中是否有调度周期出现数据溢出， 并判 断出现数据溢出的调度周期之后是否存在与其属于同一调度周期组的调度 周期， 将判断结果发送给数据包处理单元。
11、 根据权利要求 8 所述的装置， 其特征在于， 所述将不能在出现数 据溢出的调度周期内发送的数据在与其属于同一调度周期组的后续调度周 期内发送为： 将不能在前一个调度周期内发送的数据在与其属于同一个调 度周期组的下一个调度周期内发送。
12、 根据权利要求 8或 11所述的装置， 其特征在于， 所述在同一调度 周期组的后续调度周期内发送的数据为不能在出现数据溢出的调度周期内 完整发送的数据包的整个数据包； 或为不能在出现数据溢出的调度周期内 完整发送的数据包的部分数据。
13、 根据权利要求 12所述的装置， 其特征在于， 所述在同一调度周期 组的后续调度周期内发送为： 作为所述后续调度周期内的第一个数据部分 发送； 或作为所述后续调度周期内该溢出数据对应的业务的第一个数据部 分发送。
PCT/CN2010/075605 2009-08-19 2010-07-30 多媒体广播组播业务中多调度周期联合调度的方法及装置 WO2011020403A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200910090524.3 2009-08-19
CN2009100905243A CN101998242A (zh) 2009-08-19 2009-08-19 多媒体广播组播业务中多调度周期联合调度的方法及装置

Publications (1)

Publication Number Publication Date
WO2011020403A1 true WO2011020403A1 (zh) 2011-02-24

Family

ID=43606633

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2010/075605 WO2011020403A1 (zh) 2009-08-19 2010-07-30 多媒体广播组播业务中多调度周期联合调度的方法及装置

Country Status (2)

Country Link
CN (1) CN101998242A (zh)
WO (1) WO2011020403A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3197185B1 (en) * 2014-08-22 2019-10-30 Huawei Technologies Co., Ltd. Mbms group service data transmission methods, base station and user equipment

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1708041A (zh) * 2004-06-09 2005-12-14 朗迅科技公司 正交频分复用系统的复用方案
US20070189207A1 (en) * 2006-02-14 2007-08-16 Interdigital Technology Corporation Methods and systems for providing reliable multicast service in a wlan system
CN101247174A (zh) * 2007-01-22 2008-08-20 三菱电机株式会社 无线网络中利用协作中继进行通信的方法和系统
US20090109850A1 (en) * 2007-10-31 2009-04-30 Qualcomm Incorporated Methods and apparatus related to controlling traffic in a wireless communications system using shared air link traffic resources

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100574487C (zh) * 2007-09-18 2009-12-23 华为技术有限公司 一种总体消息的调度方法及装置
CN101378399B (zh) * 2008-09-28 2012-04-04 华为技术有限公司 业务数据映射和解映射方法及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1708041A (zh) * 2004-06-09 2005-12-14 朗迅科技公司 正交频分复用系统的复用方案
US20070189207A1 (en) * 2006-02-14 2007-08-16 Interdigital Technology Corporation Methods and systems for providing reliable multicast service in a wlan system
CN101247174A (zh) * 2007-01-22 2008-08-20 三菱电机株式会社 无线网络中利用协作中继进行通信的方法和系统
US20090109850A1 (en) * 2007-10-31 2009-04-30 Qualcomm Incorporated Methods and apparatus related to controlling traffic in a wireless communications system using shared air link traffic resources

Also Published As

Publication number Publication date
CN101998242A (zh) 2011-03-30

Similar Documents

Publication Publication Date Title
CA2691154C (en) A method for providing a plurality of services
KR101030678B1 (ko) 단일 주파수 모바일 통신 네트워크에서 브로드캐스트 데이터의 전달을 동기화하기 위한 방법
JP5442106B2 (ja) 無線ネットワーク内でのブロードキャストおよび／またはマルチキャストの通信方法およびデバイス
CN101741701B (zh) 同步调度方法和装置
KR101445115B1 (ko) 게이트웨이 및 기지국들 사이를 동기화하는 방법 및 대응하는 게이트웨이와 기지국
EP2219321A1 (en) Scheduling of dynamically multiplexed services in a wireless network
US8774221B2 (en) Apparatus and method for reporting buffer status of UE in mobile communication system
WO2012097690A1 (zh) 基于组的调度方法、ue及网络设备
EP2958393A1 (en) Distribution of broadcast/multicast data in telecommunications systems
KR101386155B1 (ko) 멀티미디어 브로드캐스트 멀티캐스트 서비스의 스케줄링 처리방법 및 하위 레이어 네트워크 요소
US20080192748A1 (en) Method of broadcasting in a telecommunications network in a segmentation re-assembly mode
US9386598B2 (en) Method and apparatus for synchronization processing
WO2010054545A1 (zh) 同步调度方法
WO2011020403A1 (zh) 多媒体广播组播业务中多调度周期联合调度的方法及装置
KR101714511B1 (ko) 무선 통신 시스템에서 멀티미디어 방송 데이터를 전송하는 장치 및 방법
AU2012201114B2 (en) A method for providing a plurality of services
KR101631104B1 (ko) 무선 통신 시스템에서 멀티미디어 방송 데이터를 전송하는 장치 및 방법

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 10809536

Country of ref document: EP

Kind code of ref document: A1