CN102036176A - Method and network system for synchronously recovering multimedia broadcast multicast service - Google Patents
Method and network system for synchronously recovering multimedia broadcast multicast service Download PDFInfo
- Publication number
- CN102036176A CN102036176A CN2009101797335A CN200910179733A CN102036176A CN 102036176 A CN102036176 A CN 102036176A CN 2009101797335 A CN2009101797335 A CN 2009101797335A CN 200910179733 A CN200910179733 A CN 200910179733A CN 102036176 A CN102036176 A CN 102036176A
- Authority
- CN
- China
- Prior art keywords
- data packet
- service data
- information
- network element
- lost
- Prior art date
- Legal status (The legal status 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 status listed.)
- Pending
Links
Images
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
本发明公开了多媒体广播组播业务的同步恢复的方法及网络系统，用于解决现有技术中发生丢包后无法正确同步恢复的问题。由发生业务数据包丢失的下层网元向相邻的下层网元发送获取所述丢失的业务数据包信息的请求消息；所述相邻的下层网元向所述发生业务数据包丢失的下层网元反馈所述丢失的业务数据包的信息。进一步地，所述发生业务数据包丢失的下层网元根据获取的所述丢失的业务数据包信息进行同步恢复处理。利用本发明，在实现MBMS同步发送的一组网元中，出现连续丢包的下层网元通过从相邻的一个或多个下层网元获取的同步信息进行同步恢复，避免该下层网元长时间失去同步，大大提高MBMS业务同步的鲁棒性和效率。
The invention discloses a method and a network system for synchronous recovery of multimedia broadcast and multicast services, which are used to solve the problem in the prior art that correct synchronous recovery cannot be performed after packet loss occurs. The lower-layer network element where the service data packet loss occurs sends a request message for obtaining the lost service data packet information to an adjacent lower-layer network element; the adjacent lower-layer network element sends a request message to the lower-layer network element where the service data packet loss occurs The element feeds back the information of the lost service data packet. Further, the lower-layer network element where the service data packet is lost performs synchronization recovery processing according to the acquired information about the lost service data packet. Utilizing the present invention, in a group of network elements that realize MBMS synchronous transmission, the lower layer network elements with continuous packet loss can recover synchronously through synchronization information obtained from one or more adjacent lower layer network elements, so as to avoid the long-term delay of the lower layer network elements. Time out of synchronization greatly improves the robustness and efficiency of MBMS service synchronization.
Description
Technical Field
The present invention relates to the field of wireless communication technologies, and in particular, to a method and a network system for synchronously recovering a multimedia broadcast multicast service.
Background
In order to effectively utilize mobile network resources, 3GPP (3rd Generation Partnership Project) proposes a multimedia Broadcast Multicast service MBMS (multimedia Broadcast Multicast service), which is a technology for transmitting data from a data source to a plurality of targets, and implements sharing of network (including core network and access network) resources and improves utilization of network resources (especially air interface resources). The MBMS defined by 3GPP can not only implement plain text low-rate message multicast and broadcast, but also implement broadcast and multicast of high-speed multimedia services, and provide various rich video, audio, and multimedia services, which undoubtedly follows the development trend of future mobile data, and provides better service prospects for the development of 3G.
In the 3GPP MBMS, an MBMS service may be transmitted in a multicast manner, and the multicast manner of the MBMS service is further divided into: a Single Frequency Network Multicast Broadcast MBSFN (Multicast/Broadcast over Single Frequency Network) mode and a soft combining mode. Wherein:
in the MBSFN transmission mode, the base station network element uses the same modulation and coding format in a plurality of cells, uses the same physical resource to transmit the same physical signal, and uses the same physical resource and MBSFN transmission mode to transmit a plurality of cells of the same MBMS service signal to form an MBSFN area. Features of MBMS multi-cell transmission include: 1) transmitting synchronously in the MBSFN area; 2) the user terminal is supported to combine and receive the MBSFN signals from a plurality of cells, and the gain of the received signals is improved. In the prior art, the MBSFN transmission mode is applied to MBMS transmission of dedicated carrier frequencies in an LTE (Long Term Evolution) System and a UMTS (Universal Mobile Telecommunications System) System.
In the UMTS system, base station network elements in multiple cells transmit the same service content, and a user terminal simultaneously receives MBMS service signals from multiple cells to perform soft combining reception, thereby improving reception gain. Different from the MBSFN mode, the multiple cells use different spreading codes and cell scrambling codes when transmitting the MBMS service.
In the existing MBMS technology, the following channel structures are respectively adopted in the LTE system and the UMTS system:
in the LTE system, one MBMS service is mapped to one MTCH (Multicast traffic Channel). Multiple MTCH channels can be mapped to MCH (Multicast Channel) transmission channels in a dynamic multiplexing mode through time division multiplexing, in an actual LTE (long term evolution) networking, a plurality of MBSFN services are arranged in an MBSFN (Multicast broadcast Multicast Channel) area, the MTCH of the data channels of the MBSFN services in the same MBSFN area and the MCCH (Multicast Control Channel) of the MBSFN services can be multiplexed to one MCH.
In a UMTS system, MTCHs of a group of MBMS services belonging to the same MBSFN area or MBSFN cluster or MSMS group may be mapped to the same transport channel. In the UMTS dedicated carrier frequency technique, since a plurality of cells constituting MBSFN transmission employ completely identical cell scrambling codes, a physical channel carrying MCCH is also transmitted in the MBSFN manner.
In the existing LTE technology, the multiple MBMS services multiplexed on the same transport channel may dynamically share the resources of the channel in a manner called dynamic multiplexing (dynamic multiplexing). The dynamic multiplexing method will be described in detail below.
In LTE MBMS, a concept of scheduling period, or referred to as msap (mbsfn subframe allocation pattern) scheduling length, is defined first. One scheduling period is defined in the time domain as the length of a time period, for example, 320 or 640ms, in which one transmission channel occupies several MBSFN subframe (subframe) resources.
In a scheduling period, data of one MBMS logical channel continuously occupies resources of a transmission channel mapped by the MBMS logical channel, that is, continuously occupies MBSFN subframe resources of the MCH channel, until all service data to be transmitted in the scheduling period of the service are transmitted. Data of different services can be transmitted in the same MBSFN subframe. That is, data from different logical channels are transmitted in the same MAC PDU (medium access control layer protocol data unit) through the MAC layer in series.
Specifically, one MBSFN radio subframe defined by LTE corresponds to one TTI (Transmission Time Interval), and one or more Transmission data blocks may be sent in one TTI, where each Transmission data block corresponds to one MAC PDU (medium access control layer protocol data unit). In one MAC PDU, multiple MAC SDUs (service data units) may be included, and different MAC SDUs in the same MAC PDU carry data of different MBMS logical channels.
The transmission sequence of the multiple multiplexed MBMS logical channels in a scheduling period may be notified to the user receiving end through an MCCH channel or other signaling. The MBMS logical channel includes MTCH, MCCH, MSCH (scheduling information), and the like.
As shown in fig. 1, a plurality of services dynamically multiplex channel resources in one scheduling period, and data of service S1 and service S2 are multiplexed in one scheduling period.
In order to implement synchronous transmission of MBMS service among cells of multiple network element entities (base station network elements), the prior art provides a synchronization protocol processing (SYNC) mode, and a network system corresponding to the method includes an upper network element and lower network elements (1 to N), as shown in fig. 2. The synchronous sending process of the SYNC protocol comprises the following processing steps:
step S1, the upper network element sends MBMS service data packet to each lower network element (1-N), the service data packet carries service data and carries time stamp information, data packet sequence number information, accumulated service data length information, etc. Wherein:
the upper network element identifies the same time stamp information in one or more continuous service data packets, and the data packets marked with the same time stamp form a data burst (data burst) or a synchronization Sequence (synchronization Sequence); the time stamp difference of two adjacent synchronous sequences is the length of the synchronous sequence;
the accumulated service data packet length information refers to the service data accumulated length of all service data packets in a synchronization sequence or from a certain starting point to the front of the service data packet.
At the end of each synchronization sequence, the upper network element also sends a SYNC control frame, which carries the total number of service data packets and the total length of service data of the corresponding synchronization sequence. An example of a synchronization sequence and a control frame sent by an upper network element to a lower network element is shown in fig. 3.
Step S2, the lower network element receives the synchronization sequence sent by the upper network element, and detects whether there is a loss of the service data packet and the total length of the lost service data packet by detecting the sequence number of the service data packet. Wherein:
the lower-layer network element may detect whether there is a loss of the service data packet by detecting a sequence number of a data packet of the received synchronization sequence, for example, if the sequence number of the service data packet of the synchronization sequence X received by the lower-layer network element is N-1, N +3, N +4. The lower network element further detects the difference between the accumulated data lengths carried by the data packets with the sequence numbers N and N +3, so as to know the sum of the service data lengths of the lost service data N +1 and N + 2.
The lower network element may also obtain the total number of data packets and the total length of service data of the corresponding synchronization sequence by reading the SYNC control frame. The control frame is also a marker for the end of the synchronization sequence.
Step S3, each lower-layer network element starts to sequentially send service data packets at the wireless interface for the service data carried by the service data packets in the same synchronization sequence in the scheduling period corresponding to the timestamp.
When a plurality of service data packets (from one or more synchronous sequences) mapped to one service in one scheduling period are processed by a radio link protocol (RLC), RLC segmentation and concatenation processing are carried out, and the maximum radio interface resource utilization efficiency is obtained.
Each lower network element independently completes radio link control protocol (RLC) processing of the MBMS service data packet, including RLC sequence number allocation, RLC segmentation and concatenation. The allocation of the RLC sequence number is cycled from 0 to a maximum value. Under normal conditions, each lower network element maintains the current RLC sequence number and performs the same processing according to the received data packet, and the initial RLC sequence number can be kept synchronous through configuration, so that each lower network element can keep the RLC sequence number distribution consistent in the data processing process.
In the prior art, when packet loss occurs, especially when there is no continuous packet loss, the lower network element may obtain the length of the lost data packet by detecting the length of the accumulated data packet. In this case, when performing RLC layer protocol processing, the lower network element may construct a virtual packet, where the length of the virtual packet is the length of the lost packet. The virtual data packet is subjected to RLC concatenation and fragmentation processing like other correctly received data packets.
When transmitting on the real radio interface, the TTI containing the dummy packet data will not be transmitted, but will be silent (Mute). This processing method is mute processing. By means of the mute processing, interference caused by inconsistency of data of the virtual data packet and service data correctly received by other network elements can be avoided. And, since the length of the dummy packet is consistent with that of the lost packet, the size of the space occupied by the dummy packet in the RLC PDU is consistent with that of the real packet, so that the starting position of the correctly received packet in the RLC PDU is consistent with the network element where no packet loss occurs after the lost packet. That is, by such processing, the network element used in the prior art to keep packet loss consistent with the network element without packet loss.
Considering the possibility of restarting the lower network element, after the restart, the RLC sequence number maintained for the MBMS service before the restart is lost, and at this time, the lower network element cannot determine the RLC sequence number after the RLC segmentation and concatenation processing is performed on the next received MBMS service data packet, so as to keep the sequence number consistent with the sequence number allocated after the RLC segmentation and concatenation processing is performed on the service data packet by the neighboring network element cell.
In order to solve this problem, in the prior art, a method of RLC sequence number resetting is adopted, specifically, at the beginning of a scheduling period, the RLC sequence number is allocated from 0, so that a restarted lower network element can maintain the synchronization of the RLC sequence number with other network elements again from a scheduling period. According to the relationship between the length of the synchronization sequence and the length of the scheduling period, the mapping relationship may include the following:
(11) a plurality of synchronous sequences are mapped to a scheduling period, and the length of the scheduling period is integral multiple of the length of the synchronous sequences.
(12) One synchronization sequence is mapped to a plurality of scheduling periods, and the length of the synchronization sequence is integral multiple of the scheduling periods.
By the methods (11) and (12), the plurality of lower-layer network elements receive the same service data packet, and can perform synchronous service data processing according to the content of the SYNC protocol, thereby maintaining synchronous service data transmission.
In the above description, the upper layer network element and the lower layer network element may be a combination of the following network elements, but are not limited to the following combination:
● in the MBMS service synchronous networking of the UMTS system, the upper network element is the core network element, and the lower network element is the RNC (radio network controller).
● in the MBMS service synchronous networking of LTE system, the upper network element is BMSC (broadcast multicast service center), and the lower network element is node B (E-NB, E-UTRAN NodeB).
Fig. 2 is a logical structure diagram illustrating the upper-layer network element and the lower-layer network element. The interface between the lower network elements is a logical interface or a physical interface.
In the above MBMS service multiplexing and synchronization method, considering that there is a possibility of loss and continuous data packet loss may occur in a process of transmitting data from an upper network element to a lower network element, according to the existing synchronization protocol SYNC technology, the lower network element may detect the number of lost data packets and the total length of the lost data packets, construct virtual lost data packets according to the information, and perform user plane protocol layer processing on the virtual data packets as if the data packets are not lost. However, the above method has a serious problem: that is, in consideration of the particularity of RLC processing, one service packet, or RLC SDU (RLC service data unit), occupies a space of RLC PDU (RLC protocol data unit) whose size depends on its specific location when RLC processing is performed. Specifically, in the RLC process, the number of RLC protocol LIs (length indication) occupied by one RLC SDU is uncertain, and may be 0, or 1, or 2, depending on its specific situation in the RLC PDU. Thus, the specific treatment:
● if the number of lost service data packets is 1, the lower network element can calculate the determined space occupied by RLC PDU according to its length.
● if continuous data loss occurs, according to the technology of the existing SYNC protocol, the lower network element has no way to determine the length of each of the lost packets, but only obtain the total length of the lost service packets, so that the size of the payload space of the RLC PDU actually occupied by the lost packets is not correctly calculated.
In the above problem, if there is multiplexing of multiple services, the lower network element will not be able to send data of a service that has a lost packet (after the last correctly received service data packet), and, in the case of multiplexing of multiple services on a transport channel, the lower network element will not be able to send data of other services after the service in a scheduling period in which the lost packet occurs, otherwise inter-cell interference will occur.
Disclosure of Invention
The technical problem to be solved by the present invention is to provide a method and a network system for synchronization recovery of a multimedia broadcast multicast service, which are used to solve the problem in the prior art that the synchronization recovery cannot be correctly performed after packet loss occurs.
In order to solve the above problems, the present invention provides a method for synchronously recovering multimedia broadcast multicast service, which comprises the following steps:
step A: the lower network element with the lost service data packet sends a request message for acquiring the lost service data packet information to an adjacent lower network element;
and B: and the adjacent lower layer network element feeds back the information of the lost service data packet to the lower layer network element with the service data packet loss.
The method further comprises the following steps: and C: and the lower network element with the lost service data packet carries out synchronous recovery processing according to the acquired lost service data packet information.
In step a, when it is determined that one or a plurality of consecutive service data packets are lost, a lower layer network element in which a service data packet is lost sends a request message to one or a plurality of lower layer network elements adjacent to the lower layer network element, where the request message is a first control plane message requesting to acquire information of the lost service data packet.
The information carried by the first control plane message includes: and identifying a synchronization sequence. The information carried by the first control plane message further includes: sequence number information indicating a requested data packet, or information indicating a total length of one synchronization sequence requested, or a combination thereof. The sequence number information indicating the requested data packet is a sequence number of a group of data packets; or a set of information identifying start/stop sequence numbers of lost service packets; or a set of information identifying the starting sequence number and the duration of the data packet; or the sequence number information of the last data packet received by the lower network element, where the requested data packet is a data packet after the last data packet received in the synchronization sequence. The information carried by the first control plane message further includes: information indicating the number of total service data packets requested.
In step B, if the adjacent lower layer network element has the information of the lost service data packet, sending a second control plane message to the lower layer network element where the service data packet is lost, where the second control plane message carries the following information: and the length information of part or all of the service data packets indicated by the information carried by the first control plane message is passed.
The length information of part or all of the service data packets carried by the second control plane message includes the following information: indicating the sequence number of the data packet and the length of the corresponding data packet; or, indicating a starting sequence number and an ending sequence number of a group of continuous data packets, and indicating the length of the corresponding data packet; or, indicating the starting sequence number and number of a group of continuous data packets, and indicating the length of the corresponding data packet; or, when the adjacent network element does not have the information of part or all of the lost service data packets, indicating that the length of the lost service data packet is a special value or does not carry the sequence number or length information of the lost service data packet.
If the lower network element with the service data packet loss occurs, requesting the total service data packet number and/or the total service data length information of a synchronization sequence in the first control plane message, and the second control plane message further carries the following information: and the number information of the total service data packets of the synchronization sequence and/or the length information of the total service data of the synchronization sequence.
In step C, the lower network element with the lost service data packet obtains the size and position of the space of the radio link control protocol data unit (RLC PDU) occupied by the lost service data packet in the Radio Link Control (RLC) protocol processing according to the length of the service data packet carried in the second control plane message. So that Transmission Time Intervals (TTIs) containing lost traffic data can be silently processed.
In step C, the lower network element with the lost service data packet performs synchronous recovery processing by integrating the lost service data packet information returned by a plurality of or all adjacent lower network elements according to the length of the service data packet carried in the messages from the plurality of second control planes.
The invention also provides a network system for synchronously recovering the multimedia broadcast multicast service, which comprises an upper network element and a plurality of lower network elements 1-N; the plurality of lower layer network elements comprise a lower layer network element with a lost service data packet and one or more lower layer network elements adjacent to the lower layer network element with the lost service data packet, and the lower layer network elements are called adjacent lower layer network elements; wherein,
the lower layer network element with the lost service data packet is used for sending a request message for acquiring the lost service data packet information to one or more adjacent lower layer network elements; and the adjacent lower layer network element is used for feeding back the lost service data packet information to the lower layer network element with the service data packet loss when the information of the lost service data packet exists.
And the lower network element with the lost service data packet is further used for carrying out synchronous recovery processing according to the acquired information of the lost service data packet.
The lower network element with the service data packet loss comprises:
the detection module is used for judging whether loss of one or a plurality of continuous service data packets occurs or not;
a first control layer message sending module, configured to generate a first control layer message for acquiring information of a lost service data packet when a service data packet is lost, and send the first control layer message to an adjacent lower-layer network element, where the request message is the first control layer message;
a second control layer message receiving module, configured to receive a second control layer message from an adjacent lower layer network element, where the second control layer message carries lost service data packet information that is fed back to the lower layer network element where the service data packet is lost by the adjacent lower layer network element;
and the synchronous recovery processing module is used for performing synchronous recovery processing according to the acquired lost service data packet information from the second control layer message.
The adjacent lower layer network element comprises:
a first control layer message receiving module, configured to receive a first control layer message from the lower layer network element where the service data packet loss occurs;
a service data packet retrieval module, configured to retrieve and judge whether the adjacent lower layer network element has the information of the lost service data packet according to the first control layer message;
and the second control layer message sending module is used for generating a second control layer message according to the requirement of the first control layer message when the service data packet retrieval module retrieves part or all of the information of the lost service data packet, and sending the information carrying part or all of the lost service data packet to the lower network element with the lost service data packet.
The information carried by the first control plane message includes: identifying a synchronization sequence; further still include: information indicating the sequence number of the requested data packet, or information indicating the total length of one synchronization sequence requested, or information indicating the number of total service data packets requested, or a combination thereof. The sequence number information indicating the requested data packet is a sequence number of a group of data packets; or a set of information identifying start/stop sequence numbers of lost service packets; or a set of information identifying the starting sequence number and the duration of the data packet; or the sequence number information of the last data packet received by the lower network element, where the requested data packet is a data packet after the last data packet received in the synchronization sequence.
The second control plane message carries the following information: and the length information of part or all of the service data packets indicated by the information carried by the first control plane message is passed. The length information of part or all of the service data packets carried by the second control plane message includes the following information:
indicating the sequence number of the data packet and the length of the corresponding data packet; or, indicating a starting sequence number and an ending sequence number of a group of continuous data packets, and indicating the length of the corresponding data packet; or, indicating the starting sequence number and number of a group of continuous data packets, and indicating the length of the corresponding data packet; or, when the adjacent network element does not have the information of part or all of the lost service data packets, indicating that the length of the lost service data packet is a special value or does not carry the sequence number and/or the length information of the lost service data packet.
If the lower network element with the service data packet loss occurs, requesting the total service data packet number and/or the total service data length information of a synchronization sequence in the first control plane message, and the second control plane message further carries the following information: and the number information of the total service data packets of the synchronization sequence and/or the length information of the total service data of the synchronization sequence.
And the synchronous recovery processing module is used for obtaining the length of each lost service data packet when scheduling processing is carried out according to the length of the service data packet carried in the second control plane message, and calculating the size of the space of a radio link control protocol data unit (RLC PDU) occupied by each lost service data packet in the Radio Link Control (RLC) protocol processing.
In the method and the network system for synchronously recovering the multimedia broadcast multicast service, the lower layer network element with continuous packet loss in a group of network elements for realizing the synchronous transmission of the MBMS acquires the synchronous information from one or more adjacent lower layer network elements and carries out synchronous recovery according to the synchronous information, so that the lower layer network element can be prevented from losing synchronization for a long time, and the robustness and the efficiency of the synchronization of the MBMS are greatly improved.
Drawings
Fig. 1 is a schematic diagram of resources of a plurality of MBMS services sharing a channel in a dynamic multiplexing manner;
fig. 2 is a schematic diagram of a network system for implementing multi-network element synchronous transmission of an MBMS service;
fig. 3 is a diagram illustrating a synchronization sequence and a control frame thereof for transmitting an MBMS service;
fig. 4 is a schematic diagram of a method for synchronous recovery of a multimedia broadcast multicast service according to the present invention;
fig. 5 is a schematic diagram of a network system for synchronous recovery of the mbms service according to the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is further described in detail below with reference to the accompanying drawings.
The invention provides a method and a network System for synchronously recovering Multimedia Broadcast Multicast Service (MBMS), and particularly relates to a method and a network System for synchronously recovering service data in a multi-network element content synchronous network of MBMS (multimedia broadcast multicast service) in wireless communication technologies such as UMTS (Universal Mobile Telecommunications System), 3GPP LTE (Long Term Evolution) and the like. The lower network element with the lost service data packet requests the information of the lost service data packet from the adjacent lower network element, and the lower network element with the lost service data packet carries out synchronous recovery according to the information of the lost service data packet acquired from the adjacent lower network element.
As shown in fig. 4, a schematic diagram of a method for synchronously recovering a multimedia broadcast multicast service according to the present invention is shown, where the method for synchronously recovering a multimedia broadcast multicast service includes:
step 401: the lower network element with the lost service data packet sends a request message for acquiring the lost service data packet information to an adjacent lower network element;
step 402: if the adjacent lower network element has the information of the lost service data packet, feeding back the information of the lost service data packet to the lower network element with the lost service data packet;
step 403: and the lower network element with the lost service data packet carries out synchronous recovery processing according to the acquired lost service data packet information.
In step 401, the lower network element with the lost service data packet sends a request message for acquiring the information of the lost service data packet to an adjacent lower network element.
When judging that one or more continuous service data packets are lost, one lower layer network element determines that the lower layer network element is the lower layer network element with the lost service data packets, and sends a request message to other one or more lower layer network elements adjacent to the lower layer network element to request to acquire the lost service data packet information, specifically the synchronous information of the lost service data packets. Specifically, the lower-layer network element with the lost service data packet sends a first control plane message to the adjacent lower-layer network element, and requests to acquire the information of the lost service data packet.
Further, the first control plane message may carry the following information to obtain the service data packet information that it needs to request:
● a synchronization sequence identification, which may be time stamp information of the synchronization sequence;
● sequence number information of a group of packets;
optionally, in a specific implementation, the sequence number information of the group of data packets may be a sequence number of the group of data packets, so that each lost service data packet corresponds to one sequence number; or, it may be a group of information identifying start/stop sequence numbers of the lost service data packet, where the sequence number of the lost service data packet is all service data packets between each pair of start/stop sequence numbers (start sequence number, end sequence number); or, it may be a set of information identifying the starting sequence number and the duration of the data packet, where the lost service data packet is a data packet that continues from the starting sequence number by the duration.
Or optionally, the first control plane message does not carry the sequence number information of the data packet, and at this time, the first control plane message is interpreted as the length of each data packet requesting the synchronization sequence.
Or, optionally, the sequence number information of the group of data packets may be only a starting sequence number information, and at this time, the requested data packet is the length of each data packet in the synchronization sequence from the starting sequence number of the sequence to the last data packet of the synchronization sequence.
● indicates that the total length of a synchronization sequence is requested, and optionally, information of the total number of service packets is also included.
Optionally, in a specific implementation, the total length and the total number of the data packets of the synchronization sequence indicated by the synchronization sequence identifier may be obtained through an indication bit. Or default, no data packet sequence number information is carried, and the information interpreted as the request is the total data packet length and the total data packet number of the synchronization sequence.
In step 402, the neighboring lower layer network element feeds back the lost service data packet information to the lower layer network element where the service data packet is lost.
And if the adjacent lower-layer network element has part or all of the information of the lost service data packet, sending a second control plane message to the lower-layer network element with the lost service data packet, and feeding back the information of the lost service data packet through the second control plane message.
The second control plane message carries the following information:
and the length information of part or all of the service data packets indicated by the information carried by the first control plane message is passed. Specifically, the method comprises the following steps:
indicating the sequence number of the data packet and the length of the corresponding data packet;
or, indicating a starting sequence number and an ending sequence number of a group of continuous data packets, and indicating the length of the corresponding data packet;
or, the starting sequence number and number of a group of consecutive data packets are indicated, and the length of the corresponding data packet is indicated.
And if the adjacent network element does not have the information of part or all of the lost service data packets, the adjacent network element indicates that the lengths of the service data packets are special values in the second control plane message, or the second control plane message does not carry the length information of the service data packets.
If the lower network element with the lost service data packet requests the total service data packet number or the total service data length information of one synchronization sequence in the first control plane message, the adjacent lower network element carries the total service data packet number information of the synchronization sequence in the second control plane message, optionally, the adjacent lower network element also includes the total service data length information of the synchronization sequence.
In step 403, the lower network element with the service data packet loss performs synchronization recovery processing according to the acquired lost service data packet information.
And the lower network element with the service data packet loss obtains the length of the lost partial or all service data packets according to the length of the service data packet carried in the second control plane message, so that the lower network element can calculate the size of the RLC PDU space occupied by the service data packet in the RLC protocol processing.
If the lower network element with the data packet loss obtains the length of a part of the lost data packet through the second control plane message, and the data packet with unknown length is not a continuous data packet in a synchronization sequence, the lower network element can obtain the length of a single data packet with unknown length according to a synchronization protocol (SYNC), and further obtain the size of the space of the RLC PDU occupied by the lost service data packet in the RLC protocol processing.
Optionally, in order to improve reliability, the lower layer network element with the service data packet loss may send the first control plane message to a plurality of lower layer network elements adjacent to the lower layer network element. Thus, only any one of the adjacent lower layer network elements needs to return the second control plane message, and the processing can be completed according to the recovery method of the invention; or, the lower network element with the service data packet loss integrates a plurality of or all adjacent lower network elements to complete the processing through the lost service data packet information returned by the second control plane message.
Based on the above method, as shown in fig. 5, a network system of the present invention is shown. The network system comprises an upper network element and a plurality of lower network elements (1-N).
The plurality of lower layer network elements include a lower layer network element in which a service data packet is lost, and one or more lower layer network elements adjacent to the lower layer network element in which the service data packet is lost, which are hereinafter referred to as adjacent lower layer network elements.
The lower network element with the service data packet loss comprises:
the detection module is used for judging whether loss of one or a plurality of continuous service data packets occurs or not;
and the first control layer message sending module is used for generating a first control layer message for acquiring the lost service data packet information when the service data packet is lost, and sending the first control layer message to an adjacent lower-layer network element.
The adjacent lower layer network element comprises:
a first control layer message receiving module, configured to receive a first control layer message from the lower layer network element where the service data packet loss occurs;
a service data packet retrieval module, configured to retrieve and judge whether the adjacent lower layer network element has the information of the lost service data packet according to the first control layer message;
and the second control layer message sending module is used for generating a second control layer message according to the requirement of the first control layer message when the service data packet retrieval module retrieves the information of the lost service data packet, and sending the information carrying the lost service data packet to the lower layer network element with the lost service data packet. If the first control plane message requests for the total service data packet number or the total service data length information of one synchronization sequence, the adjacent lower layer network element carries the total service data packet number information of the synchronization sequence in the second control plane message, and optionally, the adjacent lower layer network element further includes the total service data length information of the synchronization sequence.
The lower network element with the service data packet loss further comprises:
a second control layer message receiving module, configured to receive a second control layer message from an adjacent lower layer network element;
and the synchronous recovery processing module is used for performing synchronous recovery processing according to the acquired lost service data packet information from the second control layer message.
And the synchronous recovery processing module performs synchronous recovery processing according to the length of the service data packet carried in the second control plane message. Specifically, the synchronization recovery processing module may obtain the length of each lost service data packet, so that the synchronization recovery processing module may calculate the size of the RLC PDU space occupied by each lost service data packet in the RLC protocol processing and the position occupied in the RLC PDU, so that the lower layer network element where the service data packet is lost may perform silent processing (mute), that is, a TTI containing the lost service data is not sent on the radio interface. And the lost service data packet can be continuously sent and then the correctly received service data packet can be sent, and the synchronous sending between the lower network element with the service data packet loss and other network elements can not be damaged.
Example 1:
when the lower network element with service data packet loss detects that the service data packet with the sequence number of the synchronization sequence X being N, N +1, N +2 is lost in SYNC protocol processing, then:
the lower layer network element with the lost service data packet sends a first control plane message to the adjacent lower layer network element, wherein the first control plane message carries: the specific indication method of the sequence number information may be as follows:
● A set of sequence number information, such as the first control plane message carrying three sequence numbers N, N +1, N +2, to indicate a missing packet.
●, and in this example, is (N, N + 2). The initial sequence number of the lost data packet is N, and the end sequence number is N + 2.
● the missing packets have a starting sequence number plus a duration, in this example (N, 3), where the starting sequence number is N and the number of missing packets is 3 (i.e., the duration).
When the adjacent lower layer network element judges that the service data packet information lost is existed, a second control plane message is sent to the lower layer network element lost, wherein the second control plane message comprises the following information: a length of each service data packet identified in the first control plane message.
In the first embodiment, the specific information may be one of the following ways:
the sequence number of the lost data packet and the corresponding length information, specifically, the sequence number N, N +1, N +2 of the synchronization sequence X and the length of the corresponding service data packet.
The start-stop sequence number of the lost data packet and the length of the corresponding data packet, specifically, the start-stop sequence number is (N, N +2), and the length from the data packet N to the data packet N + 2.
The missing packet has a starting sequence number and a duration and the corresponding packet length, in this example, a starting packet length of N, a duration of 3, and a length of packet N to packet N + 2.
If the adjacent lower network element does not have the length of the partial data packet from the data packet N to the data packet N +2, for example, N +1, then:
in the second control plane message, the length identifier of the data packet N +1 is 0; or, the second control plane message does not carry the sequence number of the data packet N +1 or the length information thereof. Specifically, the second control plane message only carries sequence number information and length of the data packets N and N + 2.
Optionally, if the adjacent lower layer network element does not have the data packet data length of all the data packets N to N +2, the adjacent lower layer network element does not return the second control plane message.
The length of the service data packet with the sequence number of N, N +1, N +2 received by the lower layer network element with the lost service data packet can construct a virtual data packet for processing, and the length of the virtual data packet is consistent with the length of the lost data packet obtained by the real adjacent lower layer network element, so that the specific cost and length occupied by the lost data packet in the RLC processing, including the RLC header cost, LI, the specific position information of each data packet in the RLC PDU and the like, can be calculated.
If the lower-layer network element with the data packet loss obtains the length of a part of lost data packets through the second control plane message, and the data packets with unknown length are not continuous data packets in a synchronization sequence, the lower-layer network element can obtain the length of a single data packet with unknown length according to the SYNC protocol.
For example, the lengths of the data packets N and N +2 are known through the above process, and then the lower network element can know the length of N +1 according to the synchronization information carried by the SYNC protocol.
Specifically, the length of the data packet N +1 is equal to the cumulative data packet length carried by the data packet N +2 minus the cumulative data packet length carried by the data packet N.
In this way, the lower network element with the service data packet loss may perform Mute (Mute) processing according to the occupied length and position of the virtual data packets, and specifically, may not transmit the TTI containing the data packet segment on the radio interface, but may normally transmit the TTI not containing the virtual data packets.
Example two:
in the process of SYNC protocol processing, a lower-layer network element with a service data packet loss detects that a control frame of a SYNC protocol of a certain synchronization sequence is not received (a frame corresponding to type 0 in the SYNC protocol, where the control frame carries a total length of the synchronization sequence and a total number of data packets), at this time, the lower-layer network element with the service data packet loss cannot know a total number of data packets and a data length of the synchronization sequence, and cannot know whether a data packet loss exists after the service data packet is correctly received, for example, the lower-layer network element with the service data packet loss does not receive the SYNC control frame of the synchronization sequence X, and a sequence number of a last data packet of the received synchronization sequence X is N. If the sequence number of the last data packet of the synchronization sequence is M:
the lower network element with the lost service data packet sends a first control plane message to the adjacent lower network element, and the first control plane message carries: service identification information, time stamp information of the synchronization sequence, and one or more of the following information:
● indicates the total number of packets requesting the synchronization sequence;
● indicates the total length of the packet requesting the synchronization sequence;
● indicates the sequence number N of the last service data packet of the synchronization sequence received by the network element.
The adjacent lower layer network element sends a second control plane message to the lower layer network element with the service data packet loss, wherein the second control plane message comprises one or the combination of the following information:
● total number of service packets of the synchronization sequence;
● total length of service data packet of the synchronization sequence;
● the length of some or all of the packets of the synchronization sequence starting with sequence number N +1 and going to the last packet of the sequence; specifically, if the last data packet sequence number of the synchronization sequence is M, the second control plane message carries one of the following information:
(1) the start-stop sequence number of the data packet and the length of the corresponding data packet, specifically, the start-stop sequence number is (N +1, M), and the length from the data packet M +1 to the data packet M.
(2) The missing packet has a starting sequence number and a duration and the corresponding packet length, in this example, starting packet sequence number N +1, duration 10, and packet N to packet N + 10.
(3) If the adjacent lower layer network element has no length from the data packet N to the partial data packet of the data packet M, for example, N +2, then:
in the second control plane message, the length identifier of the data packet N +2 is 0; or, in the second control plane message, the sequence number and/or the length information of the data packet N +2 are not carried, specifically, in the second control plane message, only the sequence number information and the corresponding data packet length of the data packets N +1 and N +3 to M are carried;
(4) optionally, if the adjacent lower layer network element does not have the data packet lengths of all the data packets N +1 to M, the adjacent lower layer network element does not return the second control plane message.
● if the sequence number of the last data packet of the synchronization sequence is N, the second control plane message carries information indicating that the lower network element with service data packet loss has not lost the service data packet; in particular, it may be shown in the second control plane message that no service data packets are lost by means of the information bits. Alternatively, it may be indicated in the second control plane message by indicating that the number of lost packets is 0.
The lower layer network element with the service data packet loss receives the second control layer message returned by the adjacent lower layer network element, obtains the total number of the service data packets, can know whether the tail part of a synchronization sequence has packet loss, and further can know the length and the number of the lost data packets if the tail part of the synchronization sequence has packet loss.
Then, the lower layer network element with the service data packet loss may construct a virtual data packet according to the information obtained from the second control plane message, and process the virtual data packet, where the length of the virtual data packet is consistent with the length of the data packet obtained by the real adjacent lower layer network element, so as to calculate specific overhead and length occupied by the data packets in RLC processing, including RLC header overhead and LI, specific location information of each data packet in RLC PDU, and the like.
If the lower-layer network element with the data packet loss obtains the length of a part of lost data packets through the second control plane message, and the data packets with unknown length are not continuous data packets in a synchronization sequence, the lower-layer network element can obtain the length of a single data packet with unknown length according to the SYNC protocol.
In this way, the lower network element with the lost service data packet can perform Mute (Mute) processing according to the occupied length and position of the virtual data packets, specifically, the TTI containing the data packet segment is not transmitted on the radio interface, but the TTI not containing the virtual data packets is normally transmitted.
The above description is only an example of the present invention, and is not intended to limit the present invention, and it is obvious to those skilled in the art that various modifications and variations can be made in the present invention. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the scope of the claims of the present invention.
Claims (22)
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2009101797335A CN102036176A (en) | 2009-09-29 | 2009-09-29 | Method and network system for synchronously recovering multimedia broadcast multicast service |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2009101797335A CN102036176A (en) | 2009-09-29 | 2009-09-29 | Method and network system for synchronously recovering multimedia broadcast multicast service |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN102036176A true CN102036176A (en) | 2011-04-27 |
Family
ID=43888362
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2009101797335A Pending CN102036176A (en) | 2009-09-29 | 2009-09-29 | Method and network system for synchronously recovering multimedia broadcast multicast service |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102036176A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2014190519A1 (en) * | 2013-05-30 | 2014-12-04 | 华为技术有限公司 | Method, device and system for transmitting service message |
| WO2015154523A1 (en) * | 2014-09-03 | 2015-10-15 | 中兴通讯股份有限公司 | Lost data recovery processing method and device |
| WO2021142646A1 (en) * | 2020-01-15 | 2021-07-22 | Oppo广东移动通信有限公司 | Method and device for service transmission, and communication device |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070242683A1 (en) * | 2006-04-12 | 2007-10-18 | Ghyslain Pelletier | Plural telecommunications functions having sharing transaction(s) |
| US20080130580A1 (en) * | 2006-12-04 | 2008-06-05 | Qualcomm Incorporated | METHODS AND APPARATUS FOR TRANSFERRING A MOBILE DEVICE FROM A SOURCE eNB TO A TARGET eNB |
| CN101247315A (en) * | 2007-02-12 | 2008-08-20 | 上海贝尔阿尔卡特股份有限公司 | Content synchronization method and apparatus for single-frequency network transmission |
-
2009
- 2009-09-29 CN CN2009101797335A patent/CN102036176A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070242683A1 (en) * | 2006-04-12 | 2007-10-18 | Ghyslain Pelletier | Plural telecommunications functions having sharing transaction(s) |
| US20080130580A1 (en) * | 2006-12-04 | 2008-06-05 | Qualcomm Incorporated | METHODS AND APPARATUS FOR TRANSFERRING A MOBILE DEVICE FROM A SOURCE eNB TO A TARGET eNB |
| CN101247315A (en) * | 2007-02-12 | 2008-08-20 | 上海贝尔阿尔卡特股份有限公司 | Content synchronization method and apparatus for single-frequency network transmission |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2014190519A1 (en) * | 2013-05-30 | 2014-12-04 | 华为技术有限公司 | Method, device and system for transmitting service message |
| CN104335515B (en) * | 2013-05-30 | 2017-11-24 | 华为技术有限公司 | The method, apparatus and system of service message transmission |
| WO2015154523A1 (en) * | 2014-09-03 | 2015-10-15 | 中兴通讯股份有限公司 | Lost data recovery processing method and device |
| CN105450356A (en) * | 2014-09-03 | 2016-03-30 | 中兴通讯股份有限公司 | Recovery processing method and device for lost data |
| CN105450356B (en) * | 2014-09-03 | 2019-10-11 | 中兴通讯股份有限公司 | Recovery processing method and device for lost data |
| WO2021142646A1 (en) * | 2020-01-15 | 2021-07-22 | Oppo广东移动通信有限公司 | Method and device for service transmission, and communication device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CA2691154C (en) | A method for providing a plurality of services | |
| KR101030678B1 (en) | Method for Synchronizing Delivery of Broadcast Data in Single Frequency Mobile Communication Network | |
| CN101741538B (en) | Synchronous dispatching method | |
| EP2320599B1 (en) | Method and apparatus for recovery processing of synchronously transmitted service data | |
| US20080101270A1 (en) | Enhanced multicast broadcast multimedia service | |
| US8599754B2 (en) | Method, device, and system for configuring multicast broadcast single frequency network resources | |
| CN105898857B (en) | Data synchronization method and system | |
| CN101741701A (en) | Synchronous dispatching method and synchronous dispatching device | |
| US8873537B2 (en) | Synchronization method and system of control sequence numbers | |
| EP1733490A1 (en) | Method and system for transmitting and receiving broadcast service data in a wireless communication system | |
| CN101039175B (en) | Method and system for synchronizing RLC in wireless network controllers | |
| CN101981874A (en) | Method for synchronizing between gateway and base station and corresponding gateway and base station | |
| US9838851B2 (en) | Subframe processing method and device | |
| US9386598B2 (en) | Method and apparatus for synchronization processing | |
| CN102035794A (en) | Method and system for transmitting and receiving synchronizing sequence of multimedia broadcast multicast service | |
| CN101931881A (en) | Method, device and system for synchronizing business content | |
| CN102055724B (en) | Synchronous processing method for multimedia broadcast multicast service, upper layer network element and lower network element | |
| CN102036176A (en) | Method and network system for synchronously recovering multimedia broadcast multicast service | |
| CN104080173A (en) | System for processing MBMS service by base station MAC layer in LTE system | |
| CN101500191A (en) | Implementing method for multimedia broadcast multicast service resource allocation synchronization | |
| CN101651488A (en) | Synergistic method for element locations of multimedia broadcast multicasting services | |
| CN116803107A (en) | Communication control method | |
| CN101651605A (en) | Method and system for transmitting and receiving data | |
| CN101500193A (en) | Method for multimedia broadcast multicast service data synchronization between RNCs | |
| CN101998242A (en) | Method and device for multi-scheduling period united scheduling in multimedia broadcasting and multicasting business |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C02 | Deemed withdrawal of patent application after publication (patent law 2001) | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20110427 |