WO2015154523A1 - 丢失数据的恢复处理方法及装置 - Google Patents

丢失数据的恢复处理方法及装置 Download PDF

Info

Publication number
WO2015154523A1
WO2015154523A1 PCT/CN2014/094558 CN2014094558W WO2015154523A1 WO 2015154523 A1 WO2015154523 A1 WO 2015154523A1 CN 2014094558 W CN2014094558 W CN 2014094558W WO 2015154523 A1 WO2015154523 A1 WO 2015154523A1
Authority
WO
WIPO (PCT)
Prior art keywords
synchronization
base station
message
packet
sequence
Prior art date
Application number
PCT/CN2014/094558
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 WO2015154523A1 publication Critical patent/WO2015154523A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received

Definitions

  • the present invention relates to the field of communications, and more specifically, to a method and device for recovering and processing lost data.
  • LTE Long Term Evolution
  • the Multimedia Broadcast Multicast Service (MBMS) synchronization protocol stipulates that the receiver needs to detect the continuity of the synchronization frame through the synchronization information carried by the synchronization frame. When detecting continuity, it is necessary to reorder the synchronization frame to detect whether the synchronization frame is lost (in related technologies, the data packet sequence number generally starts from 0).
  • the receiving end should stop transmitting the wireless subframes affected by the loss of the synchronization frame after discovering that the synchronization frame is lost; it is impossible to determine which wireless subframes are affected.
  • MCH Multicast Channel
  • MCH scheduling period MCH scheduling period
  • the present invention provides a method and device for restoring lost data, so as to at least solve the above-mentioned problems.
  • a method for recovering and processing lost data including: a first base station receives a synchronization message; the first base station identifies a lost data message in the synchronization message; A base station sends a request message for requesting to send the data packet to the second base station.
  • the method further includes: the first base station selects the second base station from a plurality of base stations according to a preset rule , And send the request message to the selected second base station.
  • the preset rule includes at least one of the following: (1) selecting the second base station from base stations in the same MBSFN area of the multicast/multicast single frequency network as the first base station; (2) ) Select the second base station from the base stations that are in the same multicast/multicast single frequency network MBSFN synchronization area as the first base station; (3) Select the second base station from the same multimedia broadcast multicast as the first base station The second base station is selected among the base stations in the service MBMS service area; (4) the second base station is selected from the base stations meeting any one of the conditions (1)-(3) from the neighbor cell list.
  • the method further includes: the first base station starts a timer; after the timer expires, the first base station When a base station does not receive the data message sent by the second base station, it sends the synchronization message to the air interface for processing; the first base station receives the second base station before the timer expires When sending the data message, add the data message sent by the second base station to the synchronization message.
  • the method further includes: after the timer expires, when the first base station receives the data message sent by the second base station, discarding the data message sent by the first base station Text.
  • the method further includes: the second base station judges whether the data message is stored locally; if so, then Send the data message to the first base station; otherwise, it is forbidden to process the request message.
  • the first base station identifying the missing data message in the synchronization message includes: when the first synchronization sequence in which the synchronization message received by the first base station includes a control packet, the first base station A base station uniformly sorts the packet sequence numbers in the first synchronization sequence, where the packet sequence number includes: the packet sequence number of the data packet and the packet sequence number of the control packet; The data packet corresponding to the missing packet sequence number in the sorting result is regarded as the missing data packet.
  • the control packet of the second synchronization sequence and the third synchronization sequence are acquired
  • the control packet for the first synchronization sequence, the second synchronization sequence, and the third synchronization sequence are in the same synchronization period, and the second synchronization sequence is the previous synchronization sequence of the first synchronization sequence
  • the total number of packets, P is the packet sequence number of the control packet of the third synchronization
  • the synchronization message carries the following information: synchronization period count information, and the synchronization period count information is used to determine the synchronization period to which the synchronization message belongs.
  • the synchronization cycle count information is carried in the following fields of the synchronization message: a dedicated field of the synchronization cycle count information, and an extension field of the synchronization message.
  • the method further includes: acquiring designated information of the data message, and the designated information is used to uniquely identify the data. Message; carrying the specified information in the request message.
  • the designated information includes at least one of the following: the packet sequence number of the data message in the synchronization message; and the packet length of the data message.
  • the specified information includes: synchronization period count information, and the synchronization period count information is used to determine the synchronization period to which the synchronization message belongs.
  • a device for recovering and processing lost data which is applied to a first base station, and includes: a receiving module configured to receive a synchronization message; and an identification module configured to identify the synchronization message
  • the first sending module is configured to send a request message for requesting to send the data message to the second base station.
  • the device further includes: a selection module, configured to select the second base station from a plurality of base stations according to a preset rule; and a second sending module, configured to send the request message to the selected second base station.
  • a selection module configured to select the second base station from a plurality of base stations according to a preset rule
  • a second sending module configured to send the request message to the selected second base station.
  • the receiving module is configured to receive a synchronization message when the synchronization message carries the following information: synchronization cycle count information, and the synchronization cycle count information is used to determine the synchronization to which the synchronization message belongs cycle.
  • the technical solution of the base station requesting the lost data message from another base station is adopted, which solves the problem of the discontinuity of the multicast service caused by the loss of the synchronization frame in the related technology.
  • the experience problem is that the base station can receive the lost data message sent by another base station before the Uu side scheduling time arrives, restore the lost synchronization sequence, and avoid the discontinuity of the multicast service caused by silence.
  • FIG. 1 is a flowchart of a method for recovering and processing lost data according to an embodiment of the present invention
  • FIG. 2 is a flowchart of a method for recovering and processing lost data according to a preferred embodiment of the present invention
  • FIG. 3 is still another flowchart of the method for recovering and processing lost data according to a preferred embodiment of the present invention
  • FIG. 5 is another flowchart of a method for recovering and processing lost data according to a preferred embodiment of the present invention.
  • FIG. 6 is a schematic diagram of the SYNC PDU Type 0 format in related technologies
  • FIG. 7 is a schematic diagram of the SYNC PDU Type 1 format in related technologies
  • FIG. 8 is a schematic diagram of the SYNC PDU Type 2 format in related technologies
  • FIG. 9 is a schematic diagram of the SYNC PDU Type 3 format in related technologies.
  • Fig. 10 is a schematic diagram of sending two synchronization sequences according to an embodiment of the present invention.
  • FIG. 11 is a schematic diagram of sending two synchronization sequences out of order according to an embodiment of the present invention.
  • FIG. 12 is a schematic diagram of processing synchronization sequence disorder in the related art.
  • Figure 13 is a schematic diagram of a SYNC PDU Type 0 format according to an embodiment of the present invention.
  • Fig. 14 is another schematic diagram of a SYNC PDU Type 0 format according to an embodiment of the present invention.
  • Fig. 15 is a schematic diagram of a SYNC PDU Type 1 format according to an embodiment of the present invention.
  • Fig. 16 is a schematic diagram of a SYNC PDU Type 2 format according to an embodiment of the present invention.
  • Fig. 17 is a schematic diagram of a SYNC PDU Type 3 format according to an embodiment of the present invention.
  • Figure 18 is a schematic diagram of a method for sending two synchronization sequences according to a preferred embodiment of the present invention.
  • FIG. 19 is a schematic diagram of two adjacent synchronization sequences having two adjacent synchronization periods out of order according to an embodiment of the present invention.
  • 20 is a schematic diagram of processing after two adjacent synchronization sequences are out of order according to an embodiment of the present invention.
  • 21 is a structural block diagram of a device for recovering and processing lost data according to an embodiment of the present invention.
  • Fig. 22 is another structural block diagram of the device for recovering and processing lost data according to an embodiment of the present invention.
  • FIG. 1 is a flowchart of the method for recovering and processing lost data according to an embodiment of the present invention. As shown in FIG. 1, the method includes the following steps:
  • Step S102 the first base station receives the synchronization message
  • Step S104 the first base station identifies the missing data message in the synchronization message
  • Step S106 The first base station sends a request message for requesting to send the data message to the second base station.
  • the technical solution of the first base station after confirming the lost data message in the received synchronization message and then requesting the lost data message from another base station is adopted, which solves the problem of the loss of the synchronization frame in the related technology.
  • the user experience is affected by the discontinuity of the multicast service.
  • the base station can receive the lost data message sent by another base station before the scheduling time on the Uu side arrives, restore the lost synchronization sequence, and avoid the multiplication caused by silence. Broadcasting business is not continuous.
  • step S106 that is, before the first base station sends to the second base station a request message for requesting to send the data message
  • the method further includes: the first base station selects from a plurality of base stations according to a preset rule The second base station, and the request message is sent to the selected second base station.
  • the foregoing preset rule includes at least one of the following: (1) From the same multicast/multicast single frequency network as the first base station (Multicast Broadcast Single Frequency Network, (Referred to as MBSFN) area base stations, select the second base station; (2) select the second base station from the base stations in the same multicast/multicast single frequency network MBSFN synchronization area as the first base station; (3) Select the second base station from the base stations that are in the same MBMS service area of the multimedia broadcast multicast service as the first base station; (4) From the neighbor cell list, select the one that meets any of the conditions (1)-(3)
  • the base station selects the above-mentioned second base station, that is, the eNB selects the eNB that sends the lost message reverse transmission request.
  • the first base station after the first base station sends a request message for requesting transmission of the data message to the second base station, the following processing procedure may be performed: the first base station starts a timer After the timer expires, when the first base station does not receive the data message sent by the second base station, it sends the synchronization message to the air interface for processing; the first base station receives it before the timer expires For the data message sent by the second base station, the data message sent by the second base station is added to the synchronization message.
  • the above method further includes: after the timer expires, when the first base station receives the data message sent by the second base station, discarding the data message sent by the first base station.
  • the above-mentioned first base station recognizes the missing data message in the above-mentioned synchronization message, which can be implemented in the following ways (the embodiment of the present invention mainly divides into two situations, and the main basis is to determine the above-mentioned first synchronization message. Whether the control packet is received in the sequence):
  • the first base station When the first synchronization sequence where the synchronization message received by the first base station includes a control packet, the first base station uniformly sorts the packet sequence numbers in the first synchronization sequence, where the packet sequence number includes: The packet sequence number and the packet sequence number of the control packet; when there is a discontinuity in the packet sequence number in the sorting result, the data packet corresponding to the missing packet sequence number in the sorting result is regarded as the above-mentioned missing data message, because each control message in the MBMS synchronization protocol The sequence numbers of the packets are the same. Therefore, when there is a discontinuity in the packet sequence numbers, the missing data packets can be determined based on the missing packet sequence numbers.
  • the first synchronization sequence received by the first base station the above first synchronization sequence actually contains six packets: five data packets, the packet sequence numbers are 0, 1 ,2,3,4, there is also a control packet, the packet sequence number is 5, but the first base station actually received the data packet number 0,1,2, the synchronization sequence of the control packet number 5, that is, the first
  • the first synchronization sequence received by the base station loses the data packets with the data packet numbers 3 and 4.
  • the above technical solution provided by the embodiment of the present invention is adopted to identify 0, 1, 2, and 0 in the sorting result. 5. If the packet sequence number is interrupted, and the missing packet sequence numbers are 3 and 4, then the data packet with the packet sequence number 3 and 4 is the lost packet in the first synchronization sequence.
  • the control packet of the second synchronization sequence and the control packet of the third synchronization sequence are acquired , wherein the first synchronization sequence, the second synchronization sequence, and the third synchronization sequence are in the same synchronization period, and the second synchronization sequence is the previous synchronization sequence of the first synchronization sequence, and the third synchronization sequence is the aforementioned
  • the total number of data packets indicated by the total data packet data field in the control packet of the second synchronization sequence, Z is the total number of data packets indicated by the total data packet data field in the control packet of the second synchronization sequence, and P
  • the control packet of the fourth synchronization sequence is acquired, where the first synchronization sequence and the fourth synchronization sequence.
  • the synchronization sequence is located in the same synchronization period, and the fourth synchronization sequence is the synchronization sequence after the first synchronization sequence;
  • the embodiment of the present invention also provides the following technical solution to determine the missing data packet: the sequence number of the first data packet in the above sorting result is sequentially subtracted by 1 and continuously subtracted X times, and then the first data packet is determined sequentially.
  • the above-mentioned technical solutions of continuously adding X times and continuously subtracting X times can be used in combination according to actual needs.
  • a synchronization sequence does not receive a control message, only the information carried in the synchronization sequence data message cannot determine whether the data message is lost before the control message. It is necessary to combine the control message of the next synchronization sequence and the previous synchronization sequence. The message information is used to calculate the total number of messages in the synchronization sequence.
  • the first synchronization sequence and the third synchronization sequence receive the control message, and the third and the first synchronization sequence control message’s total number of data packets (total packet num, also known as Subtract Total Number Of Packet) to obtain the total number of data packets of the second synchronization sequence, then subtract the packet number (Packet Number, referred to as packet num) of the last data packet of the second synchronization sequence, and then subtract the aforementioned synchronization
  • the packet sequence number of the lost packet is based on the packet sequence number of the last data packet of the second synchronization sequence. Increase (decrease) automatically, and increase (decrease) by one each time. The packet sequence number of the lost packet is incremented (decremented) by one each time according to the obtained value.
  • the first synchronization sequence and the second synchronization sequence belong to the first two synchronization sequences of the synchronization cycle.
  • the first synchronization sequence loses the control message, the second synchronization sequence exists and the control message is received, and the Total Number Of Packet of the second control message Subtract the Packet Number of the last data message of the first synchronization sequence, and then subtract the packet sequence number of the control packet of the next synchronization sequence after the above synchronization sequence.
  • the resulting value represents the number of data packets lost before the second synchronization sequence control message.
  • the packet sequence number of the lost packet is incremented (decremented) by one each time according to the obtained value.
  • the packet sequence number of the lost packet is increased (decreased) by one according to the packet sequence number of the last data message in the first synchronization sequence, and each time it is increased (decreased) by one.
  • the control message refers to the Type0 and Type3 messages in the synchronization protocol; the data message refers to the Type1 in the synchronization protocol. , Type2 packets.
  • the following example illustrates the above-mentioned technical solution for identifying lost data packets in synchronization packets: After receiving the synchronization packets, the eNB needs to sort the synchronization packets, and according to the sorting result, combined with Type0 or Type3, the identified missing Type1 packets Text.
  • the eNB parses the Timestamp and Packet Number contained in the Type1 packet header, and the timestamp Timestamp contained in the Type0 or Type3 packet header, the packet sequence number Packet Number, the total number of packets Total Number Of Packet, and the same Type1 And Type0 or Type3 belongs to a synchronization sequence.
  • the synchronization messages of a synchronization sequence are sorted in ascending order of Packet Number. If the Packet Number is identified as discontinuous, the Type 1 packet is considered to be lost, and the unreceived Packet Number is considered to be the Type 1 packet.
  • the eNB does not receive the synchronization sequence Type0 or Type3, it needs to use the previous synchronization sequence of the synchronization sequence and the Total Number of the Type0 or Type3 of the latter synchronization sequence To Packet is used to determine whether the Type1 of the synchronization sequence is lost, and the Packet Number that is not received is considered to be the Packet Number of the Type1 packet.
  • the method before the first base station sends the request message for requesting the sending of the data packet to the second base station, the method further includes: acquiring the specified information of the data packet, and the specified Information is used to uniquely identify the data message; the designated information is carried in the request message, where the designated information includes at least one of the following: the packet sequence number of the data message in the synchronization message; the data message The length of the packet; the specified information includes: synchronization cycle count information, which is used to determine the synchronization cycle to which the synchronization message belongs.
  • the embodiment of the present invention actually provides a recovery method for the eNB to detect the loss of the SYNC PDU.
  • This method can greatly improve the discontinuity of the eMBMS service caused by packet loss on the core network side, ensure the continuity of the eMBMS service, encapsulate the lost message information as a lost message reverse transmission request, and send it to the same MBMS via X2
  • Other eNBs in the service area (only for example, but not limited to the embodiment of the present invention), request other eNBs to back-transmit the synchronization message lost by the eNB, and start a timer (Timer), the duration is up to the MSP corresponding to the synchronization sequence Starting moment.
  • Lost packet information refers to the packet number (Packet Number), length of the packet (Length of the Packet), and synchronization cycle count of the lost packet.
  • the eNB After receiving a back-transmission request for lost packets from other eNBs, the eNB parses out the Packet Number, Length of the Packet, and synchronization period count of the lost packet; judges whether the packet is cached in the memory: if the packet is not cached If the message is stored in the memory, the request is not processed; if the message is buffered in the memory, the message is encapsulated and the lost message back-transmission response is sent to the eNB requesting the lost message via X2.
  • the eNB did not receive the loss message reverse transmission response from other eNBs.
  • the synchronization sequence was sent to the air interface for processing; if before the Timer timeout, it received the loss message response from other eNBs. Send the response and insert the missing message into the sorted synchronization sequence: if all the synchronization sequences are received, the synchronization sequence is sent to the air interface for processing; if not all are received, continue to wait.
  • the existing synchronization sequence is sent to the air interface for processing; after the Timer has timed out, if a back-transmission response of the lost message from other eNBs is received, it will be discarded.
  • BMSC Broadcast-Multicast Service Center (Broadcast-Multicast Service). Centre)
  • MBMS GW is the abbreviation of Multimedia Broadcast Multicast Service-Gateway
  • eNB A is the abbreviation of Base Station A
  • eNB B is the abbreviation of Base Station B.
  • Fig. 2 is a flowchart of a method for recovering lost data according to a preferred embodiment of the present invention, as shown in Fig. 2: To
  • Step S202 The BMSC sends a synchronization sequence to the MBMS GW.
  • Step S204-Step S206 The MBMS GW sends a multicast synchronization sequence to eNB A and eNB B according to the multicast protocol.
  • Step S208 After the eNB A receives the synchronization sequence, after sorting, it detects that the synchronization message is lost, constructs the lost message information, and generates a lost message reverse transmission request.
  • Step S210 eNB A determines that the eNB that sends the back-transmission request of the lost packet is eNB B according to the strategy.
  • Step S212 eNB A sends a loss message reverse transmission request to eNB B through X2.
  • Step S214 eNB A starts a Timer, which times out before the next MSP corresponding to the timestamp of the lost message, and reserves the eNB Uu scheduling delay.
  • Step S216 eNB B, after X2 receives the eNB A's back-transmission request of the missing message, detects the requested message and buffers it in the memory.
  • Step S218 eNB B sends the buffered message to the eNB A via X2 to form a lost message back-transmission response.
  • Step S220 When the eNB A receives the back-transmission response of the lost message, and the Timer does not time out, the lost message is parsed out, the synchronization sequence is collected, and the synchronization sequence is sent to Uu.
  • FIG. 3 is another flowchart of the method for recovering lost data according to a preferred embodiment of the present invention, as shown in Fig. 3:
  • Step S302 The BMSC sends the synchronization sequence to the MBMS GW.
  • Step S304-Step S306 MBMS GW sends synchronization sequence to eNB A, eNB B, and multicast according to the multicast protocol.
  • Step S308 After the eNB A receives the synchronization sequence, after sorting, it detects that the synchronization message is lost, constructs the lost message information, and generates a lost message reverse transmission request.
  • Step S310 eNB A determines that the eNB that sends the back-transmission request of the lost message is eNB B according to the strategy.
  • Step S312 eNB A sends a loss message reverse transmission request to eNB B through X2.
  • Step S314 eNB A starts a Timer, which times out before the next MSP corresponding to the timestamp of the lost message, and reserves the eNB Uu scheduling delay.
  • Step S316 After X2 receives the lost packet back-transmission request from eNB A, eNB B buffers part of the requested packet in the memory.
  • Step S318 eNB B sends the back-transmission response of the buffered message to the eNB A through X2.
  • Step S320 When the eNB A receives the back-transmission response of the lost message, the Timer does not time out, and the lost message is parsed, the synchronization sequence is not received, and the wait continues.
  • Step S322 When the eNB Timer times out, the existing synchronization sequence is issued Uu for processing.
  • Fig. 4 is another flowchart of the method for recovering lost data according to a preferred embodiment of the present invention, as shown in Fig. 4:
  • Step S402 The BMSC sends a synchronization sequence: to the MBMS GW.
  • Step S404-Step S406 MBMS GW sends synchronization sequence to eNB A, eNB B, and multicast according to the multicast protocol.
  • Step S408 After the eNB A receives the synchronization sequence, after sorting, it detects that the synchronization message is lost, constructs the lost message information, and generates a lost message reverse transmission request.
  • Step S410 eNB A determines that the eNB that sends the back-transmission request of the lost message is eNB B according to the strategy.
  • Step S412 eNB A sends a loss message reverse transmission request to eNB B through X2.
  • Step S414 eNB A starts a Timer, which times out before the next MSP corresponding to the timestamp of the lost message, and reserves the eNB Uu scheduling delay.
  • Step S416 eNB B, after X2 receives the eNB A's back-transmission request of the missing message, detects the requested message and buffers it in the memory.
  • Step S418 eNB B sends the buffered message to the eNB A via X2 to form a lost message back-transmission response.
  • Step S420 The eNB A Timer times out, and does not receive a back-transmission response of the missing message, and sends the existing synchronization sequence to Uu for processing.
  • Step S422 After the eNB A Timer times out, it receives a back-transmission response of the missing message from the eNB B, and discards the back-transmission response of the missing message.
  • Fig. 5 is another flowchart of the method for recovering lost data according to a preferred embodiment of the present invention, as shown in Fig. 5:
  • Step S502 The BMSC sends the synchronization sequence to the MBMS GW.
  • Step S504-Step S506 MBMS GW sends synchronization sequence to eNB A, eNB B, and multicast according to the multicast protocol.
  • Step S508 After the eNB A receives the synchronization sequence, after sorting, it detects that the synchronization message is lost, constructs the lost message information, and generates a lost message reverse transmission request.
  • Step S510 According to the strategy, eNB A determines that the eNB that sends the back-transmission request of the lost message is eNB B.
  • Step S512 eNB A sends a loss message reverse transmission request to eNB B through X2.
  • Step S514 eNB A starts a Timer, which times out before the next MSP corresponding to the timestamp of the lost message, and reserves the eNB Uu scheduling delay.
  • Step S516 After X2 receives the lost message back-transmission request from eNB A, eNB B detects that the requested message is not cached in the memory, and does not send a back-transmission response to the lost message.
  • Step S518 eNB A Timer times out, and does not receive the back-transmission response of the missing message, and sends the existing synchronization sequence to Uu for processing.
  • the aforementioned synchronization message carries the following information: synchronization cycle count information, which is used to determine the synchronization cycle to which the aforementioned synchronization message belongs.
  • the aforementioned synchronization cycle count information is carried below the synchronization message Field: the dedicated field of the synchronization period count information and the extension field of the synchronization message.
  • the embodiment of the present invention adds the synchronization period count of the transmitting end to the synchronization information of the synchronization frame, and the receiving end determines which synchronization period the synchronization frame belongs to according to the synchronization period count, thereby solving the problem of the synchronization sequence message in a synchronization period.
  • the reordering problem cannot be performed correctly after the disorder arrives in other synchronization periods.
  • SYNC PDU Type 0 format As shown in Figures 6, 7, 8, and 9, in related technologies, SYNC PDU Type 0 format; SYNC PDU Type 1 format; SYNC PDU Type 2 format; SYNC PDU Type 3 format; when the above Type 0, Type 1, Type To 2.
  • Type 3 is out of order, as shown in Figure 10, the BMSC sends two synchronization sequences. As shown in Figure 11, two adjacent synchronization sequences in two adjacent synchronization periods are out of order on the eNB side.
  • FIG. 18 is a schematic diagram of a method for sending two synchronization sequences according to a preferred embodiment of the present invention.
  • FIG. 19 is a diagram of two adjacent synchronization periods in the new method according to an embodiment of the present invention.
  • FIG. 20 is a schematic diagram of processing after two adjacent synchronization sequences are out of sequence according to an embodiment of the present invention.
  • the BMSC sends a synchronization sequence in sequence in the synchronization period N.
  • the synchronization sequence has 3 Type1 messages and one Type3 message.
  • the Packet Number is 0, 1, 2, 3, the Time Stamp is 50, and the Synchronization Period and Counter are all Is N ( Figure 18).
  • the BMSC sends a synchronization sequence in sequence in the next synchronization cycle N+1.
  • the synchronization sequence has 3 Type1 messages and one Type3 message.
  • the Packet Number is 0, 1, 2, 3, and the Time Stamp is 10, Synchronisation Period Counters are all N+1 ( Figure 18).
  • the eNB received two out-of-sequence synchronization sequences, a total of 8 synchronization frames, the synchronization frame in step 2 was out of sequence to the synchronization period N, and the synchronization frame in step 1 was out of sequence to the synchronization period N+1 ( Figure 19) .
  • the eNB divides it into synchronization sequences of two synchronization periods according to the Synchronisation Period Counter.
  • the eNB divides two different synchronization sequences according to the Time Stamp.
  • the eNB reorders the synchronization frames according to Packet Number to obtain two complete synchronization sequences ( Figure 20).
  • a device for recovering lost data is also provided, which is applied to the first base station and is used to implement the above-mentioned embodiments and preferred implementations. Those that have been explained will not be repeated.
  • the following is related to the device
  • the module is described.
  • the term "module" can implement a combination of software and/or hardware with predetermined functions.
  • the devices described in the following embodiments are preferably implemented by software, implementation by hardware or a combination of software and hardware is also possible and conceived.
  • Fig. 21 is a structural block diagram of a device for recovering lost data according to an embodiment of the present invention. As shown in Figure 21, the device includes:
  • the receiving module 210 is configured to receive synchronization messages
  • the identification module 212 is configured to identify the lost data message in the aforementioned synchronization message
  • the first sending module 214 is configured to send a request message for requesting to send the foregoing data message to the second base station.
  • the technical solution of the base station requesting the lost data message from another base station after confirming that the data message is lost is adopted, which solves the discontinuity of the multicast service after the synchronization frame is lost in the related technology.
  • the base station can receive the lost data message sent by another base station before the Uu side scheduling time arrives, restore the lost synchronization sequence, and avoid the discontinuity of multicast services caused by silence.
  • the foregoing apparatus further includes: a selection module 216, configured to select the foregoing second base station according to a preset rule;
  • the second sending module 218 is connected to the selection module 216, and is used to send the above request message to the selected second base station.
  • the embodiment of the present invention provides a further improvement to the above technical solution in that the receiving module 210 is configured to receive the synchronization message when the synchronization message carries the following information: synchronization period count information, and the synchronization period count information is used to determine the foregoing synchronization message.
  • the functional units in the various embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the above-mentioned integrated unit can be implemented in the form of hardware or software functional unit.
  • the embodiment of the present invention achieves the following beneficial effects: it solves the problem that the user experience is affected by the discontinuity of the multicast service after the synchronization frame is lost in the related technology, and the base station can receive before the scheduling time on the Uu side arrives. When the lost data message sent by another base station arrives, the lost synchronization sequence is restored, and the discontinuity of the multicast service caused by silence is avoided.
  • modules or steps of the present invention can be implemented by a general computing device, and they can be concentrated on a single computing device or distributed in a network composed of multiple computing devices.
  • they can be implemented with program codes executable by a computing device, so that they can be stored in a storage device for execution by the computing device, and in some cases, they can be executed in a different order than here.
  • the technical solution of the base station requesting the lost data packet from another base station after confirming that the data packet is lost is adopted, which solves the problem of multicasting after the synchronization frame is lost in the related technology.
  • the user experience is affected by the service discontinuity.
  • the base station can receive the lost data message sent by another base station before the scheduling time on the Uu side arrives, restore the lost synchronization sequence, and avoid the multicast service interruption caused by silence. continuous.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本发明提供了一种丢失数据的恢复处理方法及装置，其中，所述恢复处理方法包括：第一基站接收同步报文；所述第一基站识别所述同步报文中丢失的数据报文；所述第一基站向第二基站发送用于请求发送所述数据报文的请求消息。采用本发明提供的上述技术方案，解决了相关技术中在丢失了同步帧之后，多播业务不连续导致的影响用户体验的问题，基站能够在Uu侧调度时刻到来前接收到了另一个基站发送的丢失的数据报文，恢复了丢失的同步序列，避免了因静默导致的多播业务不连续。

Description

丢失数据的恢复处理方法及装置 技术领域
本发明涉及通信领域，更具体地说，涉及一种丢失数据的恢复处理方法及装置。
背景技术
在长期演进(Long Term Evolution，简称为LTE)商用网络中，核心网传输丢包普遍存在。
为保证无线侧用户数据传输的实时性和准确性，多媒体广播多播业务(Multimedia Broadcast Multicast Service，简称为MBMS)同步协议规定接收端需要通过同步帧携带的同步信息检测同步帧的连续性。检测连续性时，需要重排序同步帧以检测同步帧是否丢失(相关技术中数据包序号一般从0开始编号)。
为保证eNB在相同的多播子帧传输同样的用户数据，接收端在发现丢失了同步帧后，应该停止传输由于丢失了同步帧而影响到的无线子帧；在无法确定影响到了哪些无线子帧时，应该停止传输相关的多播信道(Multicast Channel，简称为MCH)，直到本多播信道调度周期或MCH调度周期(MCH scheduling period，简称为MSP)结束。此时MCH传输的多播业务将产生不连续，严重影响多播业务的用户体验。
针对相关技术中在丢失了同步帧之后，多播业务不连续导致的影响用户体验的问题，目前尚未提出有效的解决方案。
发明内容
本发明提供了一种丢失数据的恢复处理方法及装置，以至少解决上述问题。
根据本发明的一个实施例，提供了一种丢失数据的恢复处理方法，包括：第一基站接收同步报文；所述第一基站识别所述同步报文中丢失的数据报文；所述第一基站向第二基站发送用于请求发送所述数据报文的请求消息。
优选地，所述第一基站向第二基站发送用于请求发送所述数据报文的请求消息之前，还包括：所述第一基站按照预设规则从多个基站中选择所述第二基站，并将所述请求消息发送至选择的第二基站。
优选地，所述预设规则包括以下至少之一：(1)从与所述第一基站处于同一个多播/组播单频网络MBSFN区域的基站中，选择所述第二基站；(2)从与所述第一基站处于同一个多播/组播单频网络MBSFN同步区域的基站中，选择所述第二基站；(3)从与所述第一基站处于同一个多媒体广播多播业务MBMS服务区域的基站中，选择所述第二基站；(4)从邻区列表中选择符合条件(1)-(3)中任一条件的基站中选择所述第二基站。
优选地，所述第一基站向第二基站发送用于请求发送所述数据报文的请求消息之后，还包括：所述第一基站启动定时器；在所述定时器超时后，所述第一基站未收到所述第二基站发送的所述数据报文时，将所述同步报文下发至空口处理；所述第一基站在所述定时器超时前收到所述第二基站发送的所述数据报文时，将所述第二基站发送的所述数据报文添加到所述同步报文中。
优选地，所述方法还包括：在所述定时器超时后，所述第一基站收到所述第二基站发送的所述数据报文时，丢弃所述第一基站发送的所述数据报文。
优选地，所述第一基站向第二基站发送用于请求发送所述数据报文的请求消息之后，还包括：所述第二基站判断本地是否存储有所述数据报文；如果是，则将所述数据报文发送给所述第一基站；否则，禁止处理所述请求消息。
优选地，所述第一基站识别所述同步报文中丢失的数据报文，包括：在所述第一基站接收到的所述同步报文所在第一同步序列包含控制包时，所述第一基站对所述第一同步序列中的包序号进行统一排序，其中，所述包序号包括：数据包的包序号和控制包的包序号；在排序结果中所述包序号存在间断时，将排序结果中缺失包序号所对应的数据包作为所述丢失的数据报文。
优选地，在所述第一同步序列不包含控制包时，如果所述第一同步序列不是当前同步周期内接收到的首个同步序列，则获取第二同步序列的控制包以及第三同步序列的控制包，其中，所述第一同步序列、所述第二同步序列与所述第三同步序列位于同一同步周期，且所述第二同步序列为所述第一同步序列的前一个同步序列，所述第三同步序列为所述第一同步序列的后一个同步序列；根据以下公式确定所述第一同步序列中最后一个数据包至控制包所丢失的数据报文的数量X：X＝Y-Z-P，其中，Y为所述第三同步序列的控制包中总数据包数据字段所指示的数据包总量，Z为所述第二同步序列的控制包中总数据包数据字段所指示的数据包总量，P为所述第三同步序列的控制包的包序号；将所述排序结果中最后一个数据包序号依次加1并连续加X次，进而依次确定所述第一同步序列中丢失的数据报文。
优选地，在所述第一同步序列不包含控制包，且所述第一同步序列为当前同步周期内接收到的首个同步序列时，则获取第四同步序列的控制包，其中，所述第一同步序列与所述第四同步序列位于同一同步周期，所述第四同步序列为所述第一同步序列的后一个同步序列；根据以下公式确定所述第一同步序列中最后一个数据包至控制包所丢失的数据报文的数量A：A＝B-P，其中，B为所述第四同步序列的控制包的总数据包数据字段所指示的数据包总量，P为所述第四同步序列的控制包的包序号；将所述排序结果中最后一个数据包序号依次加1并连续加A次，进而依次确定所述第一同步序列中丢失的数据报文对应的包序号。
优选地，所述同步报文中携带有以下信息：同步周期计数信息，该同步周期计数信息用于确定所述同步报文所归属的同步周期。
优选地，所述同步周期计数信息携带于所述同步报文的以下字段：所述同步周期计数信息的专用字段、所述同步报文的扩展字段。
优选地，所述第一基站向第二基站发送用于请求发送所述数据报文的请求消息之前，还包括：获取所述数据报文的指定信息，该指定信息用于唯一识别所述数据报文；将所述指定信息携带于所述请求消息中。
优选地，所述指定信息包括以下至少之一：所述数据报文在所述同步报文中的包序号；所述数据报文的包长度。
优选地，所述指定信息包括：同步周期计数信息，该同步周期计数信息用于确定所述同步报文所归属的同步周期。
根据本发明的另一个实施例，还提供了一种丢失数据的恢复处理装置，应用于第一基站，包括：接收模块，设置为接收同步报文；识别模块，设置为识别所述同步报文中丢失的数据报文；第一发送模块，设置为向第二基站发送用于请求发送所述数据报文的请求消息。
优选地，所述装置还包括：选择模块，设置为按照预设规则从多个基站中选择所述第二基站；第二发送模块，设置为将所述请求消息发送至选择的第二基站。
优选地，所述接收模块，设置为在所述同步报文中携带有以下信息时，接收同步报文：同步周期计数信息，该同步周期计数信息用于确定所述同步报文所归属的同步周期。
通过本发明，采用基站在确认丢失了数据报文之后，向另一个基站请求丢失的数据报文的技术方案，解决了相关技术中在丢失了同步帧之后，多播业务不连续导致的影响用户体验的问题，基站能够在Uu侧调度时刻到来前接收到了另一个基站发送的丢失的数据报文，恢复了丢失的同步序列，避免了因静默导致的多播业务不连续。
附图说明
此处所说明的附图用来提供对本发明的进一步理解，构成本申请的一部分，本发明的示意性实施例及其说明用于解释本发明，并不构成对本发明的不当限定。在附图中：
图1为根据本发明实施例的丢失数据的恢复处理方法的流程图；
图2为根据本发明优选实施例的丢失数据的恢复处理方法的流程图；
图3为根据本发明优选实施例的丢失数据的恢复处理方法的再一流程图；
图4为根据本发明优选实施例的丢失数据的恢复处理方法的又一流程图；
图5为根据本发明优选实施例的丢失数据的恢复处理方法的又一流程图；
图6为相关技术中的SYNC PDU Type 0格式的示意图；
图7为相关技术中的SYNC PDU Type 1格式的示意图；
图8为相关技术中的SYNC PDU Type 2格式的示意图；
图9为相关技术中的SYNC PDU Type 3格式的示意图；
图10为根据本发明实施例的发送两个同步序列的示意图；
图11为根据本发明实施例的发送两个同步序列发生乱序的示意图；
图12为相关技术中的同步序列乱序的处理示意图；
图13为根据本发明实施例的SYNC PDU Type 0格式的示意图；
图14为根据本发明实施例的SYNC PDU Type 0格式的另一示意图；
图15为根据本发明实施例的SYNC PDU Type 1格式的示意图；
图16为根据本发明实施例的SYNC PDU Type 2格式的示意图；
图17为根据本发明实施例的SYNC PDU Type 3格式的示意图；
图18为根据本发明优选实施例的两个同步序列的发送方法的示意图；
图19为根据本发明实施例的相邻两个同步周期相邻两个同步序列发生了乱序的示意图；
图20为根据本发明实施例的两个相邻同步序列发生乱序后的处理示意图；
图21为根据本发明实施例的丢失数据的恢复处理装置的结构框图；
图22为根据本发明实施例的丢失数据的恢复处理装置的另一结构框图。
具体实施方式
下文中将参考附图并结合实施例来详细说明本发明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
本发明的其它特征和优点将在随后的说明书中阐述，并且，部分地从说明书中变得显而易见，或者通过实施本发明而了解。本发明的目的和其他优点可通过在所写的说明书、权利要求书、以及附图中所特别指出的结构来实现和获得。
本发明实施例提供了一种丢失数据的恢复处理方法，图1为根据本发明实施例的丢失数据的恢复处理方法的流程图，如图1所示，该方法包括如下步骤：
步骤S102：第一基站接收同步报文；
步骤S104：上述第一基站识别上述同步报文中丢失的数据报文；
步骤S106：上述第一基站向第二基站发送用于请求发送上述数据报文的请求消息。
通过上述各个步骤，采用第一基站在确认接收到的同步报文中丢失的数据报文之后，向另一个基站请求丢失的数据报文的技术方案，解决了相关技术中在丢失了同步帧之后，多播业务不连续导致的影响用户体验的问题，基站能够在Uu侧调度时刻到来前接收到了另一个基站发送的丢失的数据报文，恢复了丢失的同步序列，避免了因静默导致的多播业务不连续。
可选地，在步骤S106之前，即在上述第一基站向第二基站发送用于请求发送上述数据报文的请求消息之前，还包括：上述第一基站按照预设规则从多个基站中选择上述第二基站，并将上述请求消息发送至选择的第二基站。
在本发明实施例的一个可选实施例中，上述预设规则包括以下至少之一：(1)从与上述第一基站处于同一个多播/组播单频网络(Multicast Broadcast Single Frequency Network，简称MBSFN)区域的基站中，选择上述第二基站；(2)从与上述第一基站处于同一个多播/组播单频网络MBSFN同步区域的基站中，选择上述第二基站；(3)从与上述第一基站处于同一个多媒体广播多播业务MBMS服务区域的基站中，选择上述第二基站；(4)从邻区列表中选择符合条件(1)-(3)中任一条件的基站中选择上述第二基站，即eNB选择发送丢失报文反传请求的eNB，有如下四种策略：属于同一个MBSFN区域；属于同一个MBSFN同步区域；属于同一个MBMS服务区域；从邻区列表中选择符合1、或2、或3、情况的eNB。
在本发明实施例的另一个可选实施例中，上述第一基站向第二基站发送用于请求发送上述数据报文的请求消息之后，还可以执行以下处理过程：上述第一基站启动定时器；在上述定时器超时后，上述第一基站未收到上述第二基站发送的上述数据报文时，将上述同步报文下发至空口处理；上述第一基站在上述定时器超时前收到上述第二基站发送的上述数据报文时，将上述第二基站发送的上述数据报文添加到上述同步报文中。
为了使得上述技术方案更加完整，上述方法还包括：在上述定时器超时后，上述第一基站收到上述第二基站发送的上述数据报文时，丢弃上述第一基站发送的上述数据报文。
在本发明实施例中，上述第一基站识别上述同步报文中丢失的数据报文，可以通过以下方式实现(本发明实施例中主要分了两种情况，其主要依据为判断上述第一同步序列中是否接收到了控制包)：
第一种情况
在上述第一基站接收到的上述同步报文所在第一同步序列包含控制包时，上述第一基站对上述第一同步序列中的包序号进行统一排序，其中，上述包序号包括：数据包的包序号和控制包的包序号；在排序结果中上述包序号存在间断时，将排序结果中缺失包序号所对应的数据包作为上述丢失的数据报文，由于在MBMS同步协议中各个控制报文的包序号是相同的，因此，在包序号存在间断时，便可以根据缺失的包序号确定丢失的数据报文。
以下结合一个示例对上述技术方案进行说明，例如：第一基站接收到的第一同步序列，上述第一同步序列实际上是包含了六个包：五个数据包，包序号依次为0,1,2,3,4，还有一个控制包，包序号为5，然而第一基站实际上接收到的是数据包编号为0,1,2，控制包编号为5的同步序列，即第一基站接收到的第一同步序列丢失了数据包编号为3,4的数据包，那么在这种情况下，采用本发明实施例提供的上述技术方案，识别出排序结果中0,1,2,5，存在包序号间断的情况，且缺失的包序号为3,4，那么包序号为3,4的数据包就是第一同步序列中丢失的报文。
第二种情况
1)在上述第一同步序列不包含控制包时，如果上述第一同步序列不是当前同步周期内接收到的首个同步序列，则获取第二同步序列的控制包以及第三同步序列的控制包，其中，上述第一同步序列、上述第二同步序列与上述第三同步序列位于同一同步周期，且上述第二同步序列为上述第一同步序列的前一个同步序列，上述第三同步序列为上述第一同步序列的后一个同步序列；根据以下公式确定上述第一同步序列中最后一个数据包至控制包所丢失的数据报文的数量X：X＝Y-Z-P，其中，Y为上述第三同步序列的控制包中总数据包数据字段所指示的数据包总量，Z为上述第二同步序列的控制包中总数据包数据字段所指示的数据包总量，P为上述第三同步序列的控制包的包序号；将上述排序结果中最后一个数据包序号依次加1并连续加X次，进而依次确定上述第一同步序列中丢失的数据报文。
2)在第一同步序列不包含控制包，且第一同步序列为当前同步周期内接收到的首个同步序列时，则获取第四同步序列的控制包，其中，第一同步序列与第四同步序列位于同一同步周期，第四同步序列为第一同步序列的后一个同步序列；根据以下公式确定第一同步序列中最后一个数据包至控制包所丢失的数据报文的数量A：A＝B-P，其中，B为第四同步序列的控制包的总数据包数据字段所指示的数据包总量，P为第四同步序列的控制包的包序号；将上述排序结果中最后一个数据包序号依次加1并连续加A次，进而依次确定第一同步序列中丢失的数据报文对应的包序号。
为了适应实际的需要，本发明实施例还提供了以下技术方案来确定丢失的数据报文：将上述排序结果中第一个数据包序号依次减1并连续减X次，进而依次确定上述第一同步序列中丢失的数据报文，可选地，在具体实施过程中，上述连续加X次和连续减X次的技术方案可以根据实际需要结合使用。
以下结合另两个优选示例对上述技术方案进行说明：
优选示例一
若一个同步序列未收到控制报文，仅通过该同步序列数据报文携带的信息无法确定控制报文前是否丢失了数据报文，需要结合该同步序列后一个与前一个同步序列的控制报文信息来计算出该同步序列的报文总个数。则当三个同步序列同属于同一个同步周期，第一同步序列、第三同步序列收到了控制报文，第三、第一同步序列控制报文的数据报文总数(total packet num，又称为Total Number Of Packet)相减，得到第二同步序列的数据报文总数，再减去第二同步序列最后一个数据报文的包序号(Packet Number，简称为packet num)，再减去上述同步序列后一个同步序列的控制包的包序号，所得值表示第二同步序列控制报文前丢失的数据报文数，丢包报文的包序号按第二同步序列最后一个数据报文的包序号自增(减)，每次自增(减)一。丢包报文的包序号按所得值每次自增(减)一。
优选示例二
第一同步序列、第二同步序列属于同步周期的头两个同步序列，第一同步序列丢失了控制报文，第二同步序列存在收到了控制报文，第二控制报文的Total Number Of Packet减去第一同步序列最后一个数据报文的Packet Number，再减去上述同步序列后一个同步序列的控制包的包序号，所得值表示第二同步序列控制报文前丢失的数据报文数，丢包报文的包序号按所得值每次自增(减)一。丢包报文的包序号按第一同步序列最后一个数据报文的包序号自增(减)，每次自增(减)一。
需要说明的是，本发明实施例中的总包数字段是携带于同步序列的控制报文中的，控制报文指同步协议中的Type0、Type3报文；数据报文指同步协议中的Type1、Type2报文。
以下举例说明上述识别同步报文中丢失的数据报文的技术方案：eNB收到同步报文后，需要对同步报文进行排序，根据排序结果，结合Type0或者Type3，识别出的丢失的Type1报文。
具体的，eNB解析Type1报文头中包含的Timestamp、Packet Number以及Type0或者Type3报文头中包含的时间戳Timestamp、数据包序号Packet Number、总的数据包的数量Total Number Of Packet，相同的Type1以及Type0或Type3属于一个同步序列，一个同步序列的同步报文按照Packet Number升序排序，若识别出Packet Number不连续，则认为该Type1报文丢失，未收到的Packet Number认为就是该Type1报文的Packet Number；若eNB没有收到该同步序列Type0或Type3，则需要借助该同步序列的前一个同步序列以及后一个同步序列的Type0或者Type3中的Total Number Of  Packet来判断该同步序列的Type1是否丢失，未收到的Packet Number认为就是该Type1报文的Packet Number。
在本发明实施例的又一个可选实施例中，上述第一基站向第二基站发送用于请求发送上述数据报文的请求消息之前，还包括：获取上述数据报文的指定信息，该指定信息用于唯一识别上述数据报文；将上述指定信息携带于上述请求消息中，其中，上述指定信息包括以下至少之一：上述数据报文在上述同步报文中的包序号；上述数据报文的包长度；上述指定信息包括：同步周期计数信息，该同步周期计数信息用于确定上述同步报文所归属的同步周期。
综上所述，本发明实施例实际上提供了一种eNB检测到SYNC PDU丢失的恢复办法。该方法可以极大提高因核心网侧传输丢包导致的eMBMS业务的不连续性保证eMBMS业务的连续性，将丢失报文信息封装为丢失报文反传请求，通过X2发送至同属于一个MBMS服务区的其他eNB(仅做举例说明，但不限定本发明实施例)，请求其他eNB反传本eNB丢失的同步报文，并启动定时器(Timer)，时长截至到该同步序列对应的MSP起始时刻。丢失报文信息是指丢失报文的数据包序号(Packet Number)、数据包长度(Length of the Packet)、同步周期计数。
eNB收到了其他eNB发来的丢失报文反传请求后，解析出丢失报文的Packet Number、Length of the Packet、同步周期计数；判断该报文是否缓存于内存中：若该报文未缓存于内存中，则不处理该请求；若该报文缓存于内存中，将此报文封装丢失报文反传响应在通过X2发送给请求丢失报文的eNB。
eNB在Timer超时前，未收到其他eNB发来的丢失报文反传响应，Timer超时后将同步序列下发至空口处理；若在Timer超时前，收到其他eNB发来的丢失报文反传响应，将丢失报文插入到经过排序的同步序列中：若同步序列全部收齐，则将同步序列下发至空口处理；若尚未全部收齐，继续等待。
在Timer超时后，将现有同步序列下发至空口处理；若在Timer超时后，收到其他eNB发来的丢失报文反传响应，则丢弃之。
为了更好的理解上述丢失数据后的恢复过程，以下结合优选实施例进行说明，但不限定本发明，需要说明的是，以下实施例中出现的BMSC为广播组播业务中心(Broadcast-Multicast Service Centre)的简称，MBMS GW为多媒体广播多播业务-网关的简称，eNB A为基站A的简称，eNB B为基站B的简称。
图2为根据本发明优选实施例的丢失数据的恢复方法的流程图，如图2所示：
步骤S202：BMSC向MBMS GW发送同步序列。
步骤S204-步骤S206：：MBMS GW根据组播协议向eNB A、eNB B发送组播同步序列。
步骤S208：eNB A收到同步序列后，排序后，检测到同步报文出现丢失，构造丢失报文信息，生成丢失报文反传请求。
步骤S210：eNB A按照策略，确定发送丢失报文反传请求的eNB分别为eNB B。
步骤S212：eNB A通过X2向eNB B发送丢失报文反传请求。
步骤S214：eNB A启动Timer，该Timer在丢失报文的timestamp对应的下一个MSP前超时，预留出eNB Uu调度时延。
步骤S216：eNB B在X2收到eNB A的丢失报文反传请求后，检测请求的报文缓存于内存中。
步骤S218：eNB B将缓存报文组成丢失报文反传响应通过X2发送给eNB A。
步骤S220：eNB A收到失报文反传响应时，Timer未超时，解析出丢失报文，收齐同步序列，下发到Uu。
图3为根据本发明优选实施例的丢失数据的恢复方法的再一流程图，如图3所示：
步骤S302：BMSC向MBMS GW发送同步序列。
步骤S304-步骤S306：MBMS GW根据组播协议向eNB A、eNB B、组播同步序列。
步骤S308：eNB A收到同步序列后，排序后，检测到同步报文出现丢失，构造丢失报文信息，生成丢失报文反传请求。
步骤S310：eNB A按照策略，确定发送丢失报文反传请求的eNB分别为eNB B。
步骤S312：eNB A通过X2向eNB B发送丢失报文反传请求。
步骤S314：eNB A启动Timer，该Timer在丢失报文的timestamp对应的下一个MSP前超时，预留出eNB Uu调度时延。
步骤S316：eNB B在X2收到eNB A的丢失报文反传请求后，检测请求的报文部分缓存于内存中。
步骤S318：eNB B将缓存报文组成丢失报文反传响应通过X2发送给eNB A(。
步骤S320：eNB A收到失报文反传响应时，Timer未超时，解析出丢失报文，未收齐同步序列，继续等待。
步骤S322：eNB Timer超时时，将现有同步序列下发Uu处理。
图4为根据本发明优选实施例的丢失数据的恢复方法的又一流程图，如图4所示：
步骤S402：BMSC向MBMS GW发送同步序列:。
步骤S404-步骤S406：MBMS GW根据组播协议向eNB A、eNB B、组播同步序列。
步骤S408：eNB A收到同步序列后，排序后，检测到同步报文出现丢失，构造丢失报文信息，生成丢失报文反传请求。
步骤S410：eNB A按照策略，确定发送丢失报文反传请求的eNB分别为eNB B。
步骤S412：eNB A通过X2向eNB B发送丢失报文反传请求。
步骤S414：eNB A启动Timer，该Timer在丢失报文的timestamp对应的下一个MSP前超时，预留出eNB Uu调度时延。
步骤S416：eNB B在X2收到eNB A的丢失报文反传请求后，检测请求的报文缓存于内存中。
步骤S418：eNB B将缓存报文组成丢失报文反传响应通过X2发送给eNB A。
步骤S420：eNB A Timer超时，未收到失报文反传响应，将现有同步序列下发Uu处理。
步骤S422：eNB A Timer超时后，收到了eNB B的失报文反传响应，丢弃该失报文反传响应。
图5为根据本发明优选实施例的丢失数据的恢复方法的又一流程图，如图5所示：
步骤S502：BMSC向MBMS GW发送同步序列。
步骤S504-步骤S506：MBMS GW根据组播协议向eNB A、eNB B、组播同步序列。
步骤S508：eNB A收到同步序列后，排序后，检测到同步报文出现丢失，构造丢失报文信息，生成丢失报文反传请求。
步骤S510：eNB A按照策略，确定发送丢失报文反传请求的eNB分别为eNB B。
步骤S512：eNB A通过X2向eNB B发送丢失报文反传请求。
步骤S514：eNB A启动Timer，该Timer在丢失报文的timestamp对应的下一个MSP前超时，预留出eNB Uu调度时延。
步骤S516：eNB B在X2收到eNB A的丢失报文反传请求后，检测请求的报文未缓存于内存中，不发送失报文反传响应。
步骤S518：eNB A Timer超时，未收到失报文反传响应，将现有同步序列下发Uu处理。
相关技术中，接收端发生了一个同步周期内的同步序列报文在其他同步周期乱序到达时，依据相关同步信息，无法正确的进行重排序。原因在于，同步序列所携带的同步信息无法判断出特定的同步帧归属于哪一个同步周期，即现有技术中还存在同步序列无法判断特定的帧归属于哪个同步周期，为了解决上述技术问题，本发明实施例还提供了以下技术方案：
上述同步报文中携带有以下信息：同步周期计数信息，该同步周期计数信息用于确定上述同步报文所归属的同步周期，可选地，上述同步周期计数信息携带于上述同步报文的以下字段：上述同步周期计数信息的专用字段、上述同步报文的扩展字段。
即本发明实施例是在同步帧的同步信息中增加发送端的同步周期计数，接收端依据同步周期计数来确定同步帧归属于哪一个同步周期，从而解决了一个同步周期内的同步序列报文在其他同步周期内乱序到达后无法正确的进行重排序问题。
为了更好的理解上述添加同步周期计数后如何能够解决其要解决的技术问题的过程，以下结合优选实施例进行说明。
如图6、7、8、9所示，相关技术中，SYNC PDU Type 0格式；SYNC PDU Type 1格式；SYNC PDU Type 2格式；SYNC PDU Type 3格式；当上述Type 0、Type 1、Type  2、Type 3发生乱序时，如图10所示，BMSC发送了两个同步序列，如图11所示，相邻两个同步周期相邻两个同步序列在eNB侧发生了乱序。
相关技术中的处理方式如图12所示，而本发明实施例提供的上述技术方案，添加过同步周期计数后的Type 0格式；Type 1格式；Type 2格式以及Type 3格式，如图13-17所示。
图18为根据本发明优选实施例的两个同步序列的发送方法的示意图，图19为根据本发明实施例的新方法下相邻两个同步周期相邻两个同步序列在eNB侧发生了乱序的情况，图20为根据本发明实施例的两个相邻同步序列发生乱序后的处理示意图。
以下结合一个示例对上述技术方案进行简单说明。
需要说明的是，发送端相对于同步周期起始时间点经过的同步周期数，取值范围:0–2m*8-1，m的单位为octets。域长度:对于Type0，m＝0.5，对于Type1、Type2、Type3，m＝4。
BMSC在同步周期N按序发送了一个同步序列，该同步序列有3个Type1报文、一个Type3报文，Packet Number分别为0、1、2、3，Time Stamp均为50，Synchronisation Period Counter均为N(图18)。
BMSC在下一个同步周期N+1按序发送了一个同步序列，该同步序列有3个Type1报文、一个Type3报文，Packet Number分别为0、1、2、3，Time Stamp均为10，Synchronisation Period Counter均为N+1(图18)。
eNB收到了发生乱序的两个同步序列，共8个同步帧，步骤2中的同步帧乱序到了同步周期N中，步骤1的同步帧乱序到了同步周期N+1中(图19)。
eNB根据Synchronisation Period Counter将其划分为两个同步周期的同步序列。
eNB根据Time Stamp划分出两个不同的同步序列。
eNB在两个同步序列内部，分别根据Packet Number重排序同步帧，得出两个完整的同步序列(图20)。
从图12与图20对比发现，该方法成功解决了一个同步周期内的同步序列报文在其他同步周期内乱序到达后无法正确的进行重排序问题。
在本实施例中还提供了一种丢失数据的恢复装置，应用于第一基站，用于实现上述实施例及优选实施方式，已经进行过说明的不再赘述，下面对该装置中涉及到的模块进行说明。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。图21为根据本发明实施例的丢失数据的恢复装置的结构框图。如图21所示，该装置包括：
接收模块210，设置为接收同步报文；
识别模块212，设置为识别上述同步报文中丢失的数据报文；
第一发送模块214，设置为向第二基站发送用于请求发送上述数据报文的请求消息。
通过上述各个模块的综合作用，采用基站在确认丢失了数据报文之后， 向另一个基站请求丢失的数据报文的技术方案，解决了相关技术中在丢失了同步帧之后，多播业务不连续导致的影响用户体验的问题，基站能够在Uu侧调度时刻到来前接收到了另一个基站发送的丢失的数据报文，恢复了丢失的同步序列，避免了因静默导致的多播业务不连续。
可选地，如图22所示，上述装置还包括：选择模块216，设置为按照预设规则选择上述第二基站；
第二发送模块218，选择模块216连接，与用于将上述请求消息发送至选择的第二基站。
本发明实施例对上述技术方案的进一步改进在于，接收模块210，设置为在上述同步报文中携带有以下信息时，接收同步报文：同步周期计数信息，该同步周期计数信息用于确定上述数据报文所归属的同步周期。
另外，在本发明各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
需要说明的是，本发明的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的对象在适当情况下可以互换，以便这里描述的本发明的实施例能够以除了在这里图示或描述的那些以外的顺序实施。此外，术语“包括”和“具有”以及他们的任何变形， 意图在于覆盖不排他的包含，例如，包含了一系列步骤或单元的过程、方法、系统、产品或设备不必限于清楚地列出的那些步骤或单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或单元。
综上所述，本发明实施例实现了以下有益效果：解决了相关技术中在丢失了同步帧之后，多播业务不连续导致的影响用户体验的问题，基站能够在Uu侧调度时刻到来前接收到了另一个基站发送的丢失的数据报文，恢复了丢失的同步序列，避免了因静默导致的多播业务不连续。
显然，本领域的技术人员应该明白，上述的本发明的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本发明不限制于任何特定的硬件和软件结合。
以上仅为本发明的优选实施例而已，并不用于限制本发明，对于本领域的技术人员来说，本发明可以有各种更改和变化。凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。
工业实用性
基于本发明实施例提供的上述技术方案，采用基站在确认丢失了数据报文之后，向另一个基站请求丢失的数据报文的技术方案，解决了相关技术中在丢失了同步帧之后，多播业务不连续导致的影响用户体验的问题，基站能够在Uu侧调度时刻到来前接收到了另一个基站发送的丢失的数据报文，恢复了丢失的同步序列，避免了因静默导致的多播业务不连续。

Claims (17)

  1. 一种丢失数据的恢复处理方法，包括：
    第一基站接收同步报文；
    所述第一基站识别所述同步报文中丢失的数据报文；
    所述第一基站向第二基站发送用于请求发送所述数据报文的请求消息。
  2. 根据权利要求1所述的方法，其中，所述第一基站向第二基站发送用于请求发送所述数据报文的请求消息之前，还包括：
    所述第一基站按照预设规则从多个基站中选择所述第二基站，并将所述请求消息发送至选择的第二基站。
  3. 根据权利要求2所述的方法，其中，所述预设规则包括以下至少之一：
    (1)从与所述第一基站处于同一个多播/组播单频网络MBSFN区域的基站中，选择所述第二基站；
    (2)从与所述第一基站处于同一个多播/组播单频网络MBSFN同步区域的基站中，选择所述第二基站；
    (3)从与所述第一基站处于同一个多媒体广播多播业务MBMS服务区域的基站中，选择所述第二基站；
    (4)从邻区列表中选择符合条件(1)-(3)中任一条件的基站中选择所述第二基站。
  4. 根据权利要求1所述的方法，其中，所述第一基站向第二基站发送用于请求发送所述数据报文的请求消息之后，还包括：
    所述第一基站启动定时器；
    在所述定时器超时后，所述第一基站未收到所述第二基站发送的所述数据报文时，将所述同步报文下发至空口处理；
    所述第一基站在所述定时器超时前收到所述第二基站发送的所述数据报文时，将所述第二基站发送的所述数据报文添加到所述同步报文中。
  5. 根据权利要求4所述的方法，其中，所述方法还包括：在所述定时器超时后，所述第一基站收到所述第二基站发送的所述数据报文时，丢弃所述第一基站发送的所述数据报文。
  6. 根据权利要求1所述的方法，其中，所述第一基站向第二基站发送用于请求发送所述数据报文的请求消息之后，还包括：
    所述第二基站判断本地是否存储有所述数据报文；如果是，则将所述数据报文发送给所述第一基站；否则，禁止处理所述请求消息。
  7. 根据权利要求1所述的方法，其中，所述第一基站识别所述同步报文中丢失的数据报文，包括：
    在所述第一基站接收到的所述同步报文所在第一同步序列包含控制包时，所述第一基站对所述第一同步序列中的包序号进行统一排序，其中，所述包序号包括：数据包的包序号和控制包的包序号；
    在排序结果中所述包序号存在间断时，将排序结果中缺失包序号所对应的数据包作为所述丢失的数据报文。
  8. 根据权利要求7所述的方法，其中，
    在所述第一同步序列不包含控制包时，如果所述第一同步序列不是当前同步周期内接收到的首个同步序列，则获取第二同步序列的控制包以及第三同步序列的控制包，其中，所述第一同步序列、所述第二同步序列与所述第三同步序列位于同一同步周期，且所述第二同步序列为所述第一同步序列的前一个同步序列，所述第三同步序列为所述第一同步序列的后一个同步序列；
    根据以下公式确定所述第一同步序列中最后一个数据包至控制包所丢失的数据报文的数量X：
    X＝Y-Z-P，其中，Y为所述第三同步序列的控制包中总数据包数据字段所指示的数据包总量，Z为所述第二同步序列的控制包中总数据包数据字段所指示的数据包总量，P为所述第三同步序列的控制包的包序号；
    将所述排序结果中最后一个数据包序号依次加1并连续加X次，进而依次确定所述第一同步序列中丢失的数据报文。
  9. 根据权利要求7所述的方法，其中，
    在所述第一同步序列不包含控制包，且所述第一同步序列为当前同步周期内接收到的首个同步序列时，则获取第四同步序列的控制包，其中，所述第一同步序列与所述第四同步序列位于同一同步周期，所述第四同步序列为所述第一同步序列的后一个同步序列；
    根据以下公式确定所述第一同步序列中最后一个数据包至控制包所丢失的数据报文的数量A：
    A＝B-P，其中，B为所述第四同步序列的控制包的总数据包数据字段所指示的数据包总量，P为所述第四同步序列的控制包的包序号；
    将所述排序结果中最后一个数据包序号依次加1并连续加A次，进而依次确定所述第一同步序列中丢失的数据报文对应的包序号。
  10. 根据权利要求1至9中任一项所述的方法，其中，所述同步报文中携带有以下信息：
    同步周期计数信息，该同步周期计数信息用于确定所述同步报文所归属的同步周期。
  11. 根据权利要求10所述的方法，其中，所述同步周期计数信息携带于所述同步报文的以下字段：
    所述同步周期计数信息的专用字段、所述同步报文的扩展字段。
  12. 根据权利要求1所述的方法，其中，所述第一基站向第二基站发送用于请求发送所述数据报文的请求消息之前，还包括：
    获取所述数据报文的指定信息，该指定信息用于唯一识别所述数据报文；
    将所述指定信息携带于所述请求消息中。
  13. 根据权利要求12所述的方法，其中，所述指定信息包括以下至少之一：
    所述数据报文在所述同步报文中的包序号；所述数据报文的包长度。
  14. 根据权利要求12或13所述的方法，其中，所述指定信息还包括：
    同步周期计数信息，该同步周期计数信息用于确定所述同步报文所归属的同步周期。
  15. 一种丢失数据的恢复处理装置，应用于第一基站，包括：
    接收模块，设置为接收同步报文；
    识别模块，设置为识别所述同步报文中丢失的数据报文；
    第一发送模块，设置为向第二基站发送用于请求发送所述数据报文的请求消息。
  16. 根据权利要求15所述的装置，其中，所述装置还包括：
    选择模块，设置为按照预设规则从多个基站中选择所述第二基站；
    第二发送模块，设置为将所述请求消息发送至选择的第二基站。
  17. 根据权利要求15或16所述的方法，其中，所述接收模块，设置为在所述同步报文中携带有以下信息时，接收同步报文：同步周期计数信息，该同步周期计数信息用于确定所述同步报文所归属的同步周期。
PCT/CN2014/094558 2014-09-03 2014-12-22 丢失数据的恢复处理方法及装置 WO2015154523A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410447183.1 2014-09-03
CN201410447183.1A CN105450356B (zh) 2014-09-03 2014-09-03 丢失数据的恢复处理方法及装置

Publications (1)

Publication Number Publication Date
WO2015154523A1 true WO2015154523A1 (zh) 2015-10-15

Family

ID=54287258

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/094558 WO2015154523A1 (zh) 2014-09-03 2014-12-22 丢失数据的恢复处理方法及装置

Country Status (2)

Country Link
CN (1) CN105450356B (zh)
WO (1) WO2015154523A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107734547A (zh) * 2016-08-12 2018-02-23 中兴通讯股份有限公司 状态报告生成和系统，及状态报告接收方法
CN112737737A (zh) * 2019-10-28 2021-04-30 华为技术有限公司 一种确认报文的处理方法和通信装置以及存储介质

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102036176A (zh) * 2009-09-29 2011-04-27 中兴通讯股份有限公司 一种多媒体广播组播业务的同步恢复的方法及网络系统
CN102624485A (zh) * 2009-09-29 2012-08-01 华为技术有限公司 处理子帧的方法和设备

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101500341B (zh) * 2008-02-02 2011-02-02 上海贝尔阿尔卡特股份有限公司 基于窗的内容同步的网关和基站及其方法
CN102035794A (zh) * 2009-09-29 2011-04-27 中兴通讯股份有限公司 多媒体广播组播业务的同步序列发送和接收方法及系统
CN102014339A (zh) * 2009-10-27 2011-04-13 大唐移动通信设备有限公司 一种配置mbms同步的方法、设备和系统
CN102143130B (zh) * 2010-06-30 2013-11-06 华为技术有限公司 一种快速频道切换时获取关键信息的方法、装置和系统
CN102368700B (zh) * 2011-10-25 2014-10-22 曙光信息产业(北京)有限公司 一种分布式系统中消息的传递方法

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102036176A (zh) * 2009-09-29 2011-04-27 中兴通讯股份有限公司 一种多媒体广播组播业务的同步恢复的方法及网络系统
CN102624485A (zh) * 2009-09-29 2012-08-01 华为技术有限公司 处理子帧的方法和设备

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107734547A (zh) * 2016-08-12 2018-02-23 中兴通讯股份有限公司 状态报告生成和系统，及状态报告接收方法
CN112737737A (zh) * 2019-10-28 2021-04-30 华为技术有限公司 一种确认报文的处理方法和通信装置以及存储介质
CN112737737B (zh) * 2019-10-28 2022-10-11 华为技术有限公司 一种确认报文的处理方法和通信装置以及存储介质

Also Published As

Publication number Publication date
CN105450356A (zh) 2016-03-30
CN105450356B (zh) 2019-10-11

Similar Documents

Publication Publication Date Title
JP5296102B2 (ja) ウィンドウベースのコンテンツ同期化のためのゲートウェイ、基地局および方法
CN101741538B (zh) 同步调度方法
CN101174969A (zh) 在单频移动通信网络中分发数据分组的方法及装置和网络
KR101445115B1 (ko) 게이트웨이 및 기지국들 사이를 동기화하는 방법 및 대응하는 게이트웨이와 기지국
EP2320599B1 (en) Method and apparatus for recovery processing of synchronously transmitted service data
US9226266B2 (en) Method for determining delay parameters for user data flow synchronization for eMBMS
EP2958393A1 (en) Distribution of broadcast/multicast data in telecommunications systems
US10390185B2 (en) Subframe processing method and device
EP2179604A2 (en) Method, device and system for synchronization in wireless networks
CN101741701A (zh) 同步调度方法和装置
CN102932743A (zh) 多媒体广播组播业务数据的传输控制方法、装置和系统
WO2009092277A1 (zh) 多媒体业务数据发送和接收方法、基站设备和用户设备
CN102035794A (zh) 多媒体广播组播业务的同步序列发送和接收方法及系统
US9386598B2 (en) Method and apparatus for synchronization processing
CN101741499B (zh) 同步调度方法
WO2015154523A1 (zh) 丢失数据的恢复处理方法及装置
CN107889217B (zh) 业务会话发送、接收方法、装置及系统
CN105635983B (zh) 恢复挂起业务的通知、指示信息处理方法及装置
WO2015154522A1 (zh) 丢失数据报文的识别方法及装置
US8797937B2 (en) System and method for providing multicast and broadcast service supporting macro diversity
CN101651488A (zh) 一种多媒体广播组播业务网元间的协同方法
CN105491535B (zh) 一种数据发送方法和设备
KR102405504B1 (ko) 향상된 mbms 기반의 신호 송수신 방법

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

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

Country of ref document: EP

Kind code of ref document: A1