WO2010133184A1 - 一种数据传送方法、装置和通信系统 - Google Patents

一种数据传送方法、装置和通信系统 Download PDF

Info

Publication number
WO2010133184A1
WO2010133184A1 PCT/CN2010/073066 CN2010073066W WO2010133184A1 WO 2010133184 A1 WO2010133184 A1 WO 2010133184A1 CN 2010073066 W CN2010073066 W CN 2010073066W WO 2010133184 A1 WO2010133184 A1 WO 2010133184A1
Authority
WO
WIPO (PCT)
Prior art keywords
data unit
data
unit
identifier
upper layer
Prior art date
Application number
PCT/CN2010/073066
Other languages
English (en)
French (fr)
Inventor
肖瑞杰
梁柏熙
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP10777387.1A priority Critical patent/EP2429143B1/en
Publication of WO2010133184A1 publication Critical patent/WO2010133184A1/zh
Priority to US13/302,855 priority patent/US8526513B2/en

Links

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
    • H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0015—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the adaptation strategy
    • H04L1/0017—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the adaptation strategy where the mode-switching is based on Quality of Service requirement
    • H04L1/0018—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the adaptation strategy where the mode-switching is based on Quality of Service requirement based on latency requirement
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1835—Buffer management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1854—Scheduling and prioritising arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/1874—Buffer management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/1887—Scheduling and prioritising arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H04L47/245—Traffic characterised by specific attributes, e.g. priority or QoS using preemption
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
    • H04L67/61—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources taking into account QoS or priority requirements

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a data transmission method, apparatus, and communication system.
  • INP impulse noise protection
  • INP technology mainly corrects the errors generated in the transmitted data by using error correction codes, such as using the additional coding gain provided by Reed-Solomon (RS).
  • RS Reed-Solomon
  • the physical layer retransmission scheme includes the Transport Protocol Specific Transmission Convergence Layer (TPS-TC).
  • TPS-TC Transport Protocol Specific Transmission Convergence Layer
  • PMS-TC Physical Media-Specific Transmission Convergence Layer
  • PMD Physical Media Dependent Layer
  • the retransmission scheme can retransmit the data corrupted by the impulse noise, thereby reducing the bit error rate of the line and improving service stability.
  • the inventors of the present invention found that although the retransmission scheme mitigates the influence of the ultra-long impulse noise on the system to some extent, and improves the service stability of the system, it also brings A large delay (Delay) is obtained.
  • the retransmission system located at the PMS-TC layer has an additional delay of about 10 ms or more, and the maximum data delay is even more than 20 ms.
  • Such a delay requires a bit error rate.
  • the impact is small.
  • QoE Quality of Experience
  • Embodiments of the present invention provide a data transmission method, apparatus, and communication system, which can meet different delay requirements of different services and different INP protection level requirements.
  • a data transfer method includes:
  • a data transfer method includes:
  • the data unit is stored in the receiving end retransmission buffer.
  • a data transfer method includes:
  • the data unit is submitted to the upper layer so that the upper layer processes the data unit according to the additional identifier.
  • a transmitting device includes:
  • a monitoring unit configured to monitor a time delay of data transmission
  • the blocking information sending unit is configured to: when the monitoring unit determines that the delay is greater than the first delay threshold, send the blocking information, where the blocking information is used to block the low priority data sent by the upper layer;
  • a receiving unit configured to receive high priority data sent by an upper layer
  • An encapsulating unit configured to encapsulate high-priority data received by the receiving unit into a data unit, and identify an identifier that indicates that retransmission is not required
  • a sending unit configured to send the data unit encapsulated by the encapsulating unit to the receiving end.
  • a receiving device includes:
  • a receiving unit configured to receive a data unit sent by the sending end
  • An identifier identifying unit configured to determine whether the data unit received by the receiving unit includes an identifier indicating that retransmission is not required;
  • a new and old judging unit configured to determine, when the identifier identifying unit determines that the data unit does not include an identifier indicating that retransmission is not required, determining whether the data unit is a new data unit;
  • a storage unit configured to: when the identifier identifying unit determines that the data unit includes an identifier indicating that retransmission is not required, or when the new and old judging unit judges that the data unit is a new data unit, storing the data unit The receiving end retransmits the cache;
  • a correctness determining unit configured to determine whether the data unit is erroneous when the new and old determining unit determines that the data unit is not a new data unit
  • a timeout determining unit configured to: when the correctness determining unit determines that the data unit has no error, determine whether the data unit times out;
  • a discarding unit configured to discard the data unit when the correctness determining unit determines that the data unit has an error, or discard the data unit when the timeout determining unit determines that the data unit times out.
  • a receiving device includes:
  • An additional identifier unit configured to add an identifier to the data unit identifier in the receiving end retransmission buffer by monitoring the delay state, where the additional identifier indicates a processing manner after the upper layer receives the data unit; and the submitting unit is configured to attach The data unit identified by the identification unit is submitted to the upper layer, so that the upper layer processes the data unit according to the additional identifier.
  • a communication system comprising:
  • the sending end device is configured to monitor the delay of the data transmission process, and if the delay is greater than the first delay threshold, send blocking information for blocking the low priority data sent by the upper layer, and receive the high priority sent by the upper layer.
  • Data, the lost priority data is encapsulated into a data unit, and the identifier indicating that the retransmission is not required is sent, and the data unit is sent to the receiving end device;
  • a receiving end device configured to receive a data unit sent by the sending end device, and determine the data unit package When the identifier indicating that retransmission is not required is included, the data unit is stored in the retransmission buffer of the receiving end.
  • the embodiment of the present invention determines whether to send blocking information for blocking low-level data sent by the upper layer by monitoring the delay of the data in the transmission process, so as to avoid data overflow in the retransmission buffer of the transmitting end, thereby achieving low priority. Higher IN protection of the level data.
  • the sender can continue to receive the high priority data, and when the high priority data is encapsulated, the identifier is represented.
  • the identifier of the retransmission is not required, so that the receiving end does not request retransmission of the high priority data, thereby ensuring the low latency requirement of the high priority data, that is, the embodiment of the present invention can be used. Meet different delay requirements of different services and different INP protection level requirements, and improve the QoE of users' integrated services.
  • Embodiment 1 is a flowchart of a method provided by Embodiment 1 of the present invention.
  • Embodiment 2 is a flow chart of a method provided by Embodiment 2 of the present invention.
  • FIG. 3 is a schematic diagram of a method for transmitting a method according to Embodiment 3 of the present invention.
  • FIG. 4 is a schematic diagram of processing of a transmitting end in a method provided by Embodiment 3 of the present invention.
  • FIG. 5 is a schematic diagram of a retransmission buffer of a transmitting end in a method provided by Embodiment 3 of the present invention
  • FIG. 6 is a flowchart of processing of a data unit of a transmitting end according to Embodiment 3 of the present invention
  • FIG. 7 is a flowchart of processing of a data unit at a receiving end according to Embodiment 3 of the present invention.
  • FIG. 8 is a schematic diagram of processing of a receiving end in a method according to Embodiment 3 of the present invention.
  • FIG. 9 is a schematic diagram of a receiving end retransmission buffer in a method according to Embodiment 3 of the present invention.
  • FIG. 10 is a flowchart of another receiving end data unit processing according to Embodiment 3 of the present invention; A schematic diagram of the structure of the sending device provided;
  • FIG. 12 is a schematic structural diagram of a receiving end device according to an embodiment of the present invention.
  • FIG. 13 is a schematic structural diagram of a communication system according to an embodiment of the present invention.
  • Embodiments of the present invention provide a data transmission method. Embodiments of the present invention also provide corresponding apparatus and communication systems. The details are described below separately. Embodiment 1
  • a data transmission method includes: monitoring a delay of a data during transmission; if the delay is less than or equal to the first delay threshold, processing is performed according to an existing scheme, and if the delay is greater than the first delay threshold, sending Blocking information for blocking low-priority data sent by the upper layer. Since the low-priority data is blocked by the blocking information at this time, only the high-priority data sent by the upper layer is received at this time, after receiving the high-priority data, The high priority data is encapsulated into a data unit, and the identifier indicating that the retransmission is not required is identified, and then the data unit is sent to the receiving end, so that the receiving end receives the identifier indicating the data unit that does not need to be retransmitted.
  • the first delay threshold may be preset, or may be set according to the system in the process of running, and so on.
  • the first delay preset in the embodiment of the present invention is preset.
  • the specific process can be: ⁇ :
  • step 102 is performed.
  • the delay of the data in the transmission process may be monitored by monitoring the storage state of the space in the retransmission buffer of the sender, for example, determining whether the amount of data stored in the retransmission buffer of the sender is greater than a preset threshold, and if so, Indicates that the delay is greater than the preset threshold. If not, the delay is not greater than the preset threshold.
  • the blocking information is used to block the low-priority data sent by the upper layer (that is, the upper layer of the TPS-TC layer); the blocking information may specifically be a hardware blocking signal, a blocking data, or a blocking flag.
  • the embodiment of the present invention determines When the space of the retransmission buffer of the transmitting end is full, the blocking information is sent to temporarily stop receiving the low priority data, thereby ensuring a higher INP protection level for the low priority data.
  • the priority of the data may be preset by the operator, for example, if the service is sensitive to delay, but has no requirement for the bit error rate, such as VoIP (VoIP over IP).
  • VoIP Voice IP over IP
  • step 102 Since the low priority data has been blocked in step 102, only the high priority data sent by the upper layer can be received at this time; that is, the reception will be temporarily stopped and the delay is not sensitive, but a lower error is required. Low-priority data of the code rate, and in order to ensure delay-sensitive, low-latency demand for high-priority data that does not require any bit error rate, will continue to maintain normal reception of high-priority data, but this When the received high priority data is encapsulated into data units, it is not stored in the sender retransmission buffer, but is directly transmitted after the identifiers indicating that the data units are not required to be retransmitted (see step 104). To the receiving end, in this way, while ensuring the low latency requirement of the high priority data, it does not cause a data overflow situation as described in step 102.
  • the identifier indicating that the retransmission is not required may be a specific service sequence number (SID, Sequence Identifier), such as 255, or may be another SID negotiated by the sender and the receiver, or may be Identification by a separate additional identifier (Flag) in the data unit;
  • SID Service Sequence Number
  • Flag separate additional identifier
  • the IDLE can also be used at this time.
  • the data is encapsulated into a data unit, and the identifier indicating that the retransmission is not required is sent to the receiving end. That is to say, the data unit having the indication that the retransmission identifier is not required is only used to carry the high priority data and the null data, and the data unit having the indication that the retransmission identifier is not required will not be buffered into the transmitting end. In the retransmission buffer (see the description in step 103), the receiving end does not request retransmission of such data units.
  • the transmitted data may have a large error rate, but from another point of view, it can satisfy Smaller delays.
  • high-priority data and null data can be separately encapsulated or encapsulated in the same data unit, that is, the data unit may include high-priority data. And empty data, and may only include high priority data or null data;
  • the type information of the service and the SID information of the data unit may be identified by multiplexing the information of the same field in the data unit or by using different fields of the data unit.
  • the embodiment of the present invention determines whether to send blocking information for blocking low-priority data sent by the upper layer by monitoring the delay of the data in the transmission process, so as to avoid data overflow in the retransmission buffer of the transmitting end, thereby realizing Higher INP protection for low priority data.
  • the sender can continue to receive high priority data, and when encapsulating high priority data, The identifier indicates that the identifier does not need to be retransmitted, so that the receiving end does not apply for retransmission when receiving the high priority data, thereby ensuring low delay requirement of high priority data, that is, using the present
  • the embodiments of the invention can meet different delay requirements of different services and different INP protection level requirements, and improve the QoE of the user's integrated services. For example, a service that is more sensitive to delay but does not require a bit error rate can adopt a lower INP protection level. When a certain delay threshold is exceeded, no retransmission is performed. The delay is not sensitive but the bit error rate is required. Lower services can use higher ITP protection levels and require retransmission.
  • Embodiment 2 Embodiment 2
  • a data transmission method which receives a data unit sent by a transmitting end, and stores the data unit in a receiving end retransmission buffer when determining that the data unit includes an identifier indicating that retransmission is not required. That is to say, it is not necessary to determine whether the data unit is correct or needs to be retransmitted, etc., but directly store the data unit in the retransmission buffer of the receiving end, so that the number of retransmission requests at the receiving end can be reduced and the class can be reduced.
  • the delay of the data unit ie, including the data unit indicating that the retransmission identifier is not required).
  • the data unit needs to be processed to determine whether to store the data unit in the retransmission buffer of the receiving end, as shown in FIG. 2
  • the process is as follows:
  • the identifier indicating that the retransmission is not required may be a specific SID, such as 255, or may be another SID negotiated by the sender and the receiver, or may be a data unit.
  • the receiving end does not apply for retransmission, but directly stores it in the receiving end retransmission buffer.
  • Step 203 Since the retransmission is not performed, the transmitted data may have a large error rate, but it can satisfy a small delay. Therefore, the data unit having the indication that the retransmission identifier is not required is only used for the high load. Priority data and null data.
  • the data unit is stored in the retransmission buffer of the receiving end. It should be noted that, when the data unit is stored in the retransmission buffer of the receiving end, the method further includes: if the receiving end retransmission buffer has been saved, the corresponding a data unit, that is, if the data unit to be stored is a retransmitted data unit, the existing data unit in the cache is replaced;
  • Determine whether the data unit is a new data unit that is, determine whether the data unit is a new data unit or a retransmitted data unit, for example, may be determined according to a SID of the data unit, and if it is a new data unit, perform steps.
  • 203 that is, the data unit is stored in the receiving end retransmission buffer, otherwise, if it is a retransmitted data unit, step 205 is performed;
  • step 205 determine whether the data unit is wrong, if there is an error, step 206 is performed, if there is no error, step 207 is performed;
  • step 207 Determine whether the data unit is timed out. For example, the data unit may be determined according to the SID of the data unit. If the timeout is performed, step 206 is performed to discard the data unit. If there is no timeout, step 203 is performed, that is, the data unit is Stored in the receiver retransmission cache.
  • the processing of the data unit in the retransmission buffer of the receiving end can be as follows:
  • the monitoring of the delay state is performed by adding an identifier to the data unit identifier in the retransmission buffer of the receiving end, where the additional identifier indicates a processing manner after the upper layer receives the data unit; for example, the following method may be adopted:
  • the data unit is identified. Indicates a normal additional identifier, such as Flag_C; when it is determined that a new data unit needs to be submitted to the upper layer, and the data unit is determined to be incorrect, an additional indication that the high priority service data is reserved and the low priority service data is discarded is discarded for the data unit identifier Identification, such as Flag_H; If the receiving end retransmits the data unit in the cache that has not been modified within the high-priority service delay threshold, on the other hand, when it is determined that a new data unit needs to be submitted to the upper layer, the high-priority service is reserved for the data unit identifier.
  • the data discards the additional identifier of the low priority service data, such as Flag_H. On the other hand, it determines the uncorrected data unit in the high priority threshold, and determines the uncorrected data unit in the high priority service delay threshold. When a commit is required, an additional identifier indicating that the low priority service data is reserved and the high priority service data is discarded, such as Flag_L, is identified for the data unit identifier.
  • the data unit in the cache is identified as indicating a normal additional identifier, the data unit is removed from the receiver retransmission buffer and submitted to the upper layer;
  • the data unit in the cache is identified as an additional identifier indicating that the high priority service data is reserved and the low priority service data is discarded, the data unit is copied and submitted to the upper layer; that is, the data unit is still cached in the retransmission buffer at this time. (ie, not removed from the receiving retransmission buffer), these data units are uncorrected data units within the high priority service delay threshold, and the delay of these data units can still be exceeded before the low priority service delay threshold Corrected the correct data unit being retransmitted;
  • the data unit in the cache is identified as an additional identifier indicating that the low priority service data is retained and the high priority service data is discarded, the data unit is removed from the receiver retransmission buffer and submitted to the upper layer.
  • the additional identifier of the data unit is a normal additional identifier, such as Flag_C
  • all data is retained, that is, high priority data and low priority data; otherwise, according to the additional identifier
  • the indication is processed, and only one of the high priority data and the low priority data is reserved. For example, if it is Flag_L, only the low priority data is retained, and the high priority data is discarded. If it is Flag_H, only the reservation is retained. High priority data, while dropping low priority data.
  • the delay of the data unit is greater than or equal to the high priority service delay threshold
  • the data unit in the retransmission buffer of the receiving end will start to be submitted to the upper layer for processing, if the receiving end retransmits at this time.
  • the data unit in the cache has been modified within the preset time (ie high priority service delay threshold), and if the data unit is correct, it means that the data unit submitted to the upper layer is the correct data, so it can be retained.
  • the data unit in the retransmission buffer of the receiving end is not corrected within the preset time (ie, the high priority service delay threshold), and the delay of the data unit in the retransmission buffer of the receiving end is higher than any one
  • the delay threshold high-priority service delay threshold or low-priority service delay threshold
  • the data unit will be submitted twice to the upper layer, and the first commit is the delay in the data unit.
  • the high-priority service delay threshold is exceeded, the above-mentioned "data unit in the retransmission buffer of the receiving end is not corrected within the preset time", so the receiving end of the retransmission layer will data on the one hand.
  • the unit submits to the upper layer, on the one hand, the wrong data unit and the data unit behind the data unit are moved into the extended memory area of the receiving end retransmission buffer, so as to provide the opportunity for these erroneous data units to be corrected again, due to this
  • the high priority data is not retransmitted even if an error occurs, the low priority data can be retransmitted, and the correct data may be obtained in the second commit, so the high priority data is retained and the low priority is discarded.
  • Level 2 data when the delay of the data unit in the retransmission buffer at the receiving end is greater than or equal to the low priority service data delay threshold, since the high priority data has been retained at the time of the first commit, No need to repeat the reservation, so the high priority data unit is directly discarded, and the low priority data is received at this time because it has been retransmitted. It may be the correct data after retransmission, so keep it. It should be noted that the above description is only an example, and does not exclude that it can be defined before the high priority service delay threshold is not exceeded or before the low priority service delay threshold is exceeded, for example, as long as the data unit is stored in the receiving. The end retransmission cache, then submit immediately, and so on.
  • a new data unit that needs to be submitted is submitted when the high priority service delay threshold is greater than or equal to, and a new required submission is submitted when the low priority service delay is greater than or equal to Uncorrected data unit.
  • processing of the data unit in the retransmission buffer of the receiving end can also be used as an independent solution, that is, the data unit can also be placed before being placed in the buffer unit of the receiving end.
  • the monitoring of the delay state is performed by adding an identifier to the data unit identifier in the retransmission buffer of the receiving end, and then submitting the data unit to the upper layer, that is, submitting from the retransmission layer to The TPS-TC layer, so that the upper layer processes the data unit according to the additional identifier, where the additional identifier indicates the processing mode after the upper layer receives the data unit.
  • the additional identifier indicates the processing mode after the upper layer receives the data unit.
  • the receiving end of the embodiment does not need to determine whether the data unit is correct or needs to be retransmitted, etc. Instead, the data unit is directly stored in the retransmission buffer of the receiving end, so that the number of retransmissions of the receiving end and the delay of the data unit can be reduced, and further, the receiving end can also monitor the delay state. Adding an identifier to the data unit identifier in the retransmission buffer of the receiving end, so as to instruct the upper layer to reserve or discard data of different priority levels after receiving the data unit.
  • the first type is a service with low bit error rate requirement and low delay requirement, that is, the INP protection level.
  • the service with lower demand, but more sensitive to delay, such as VoIP (voice over IP), can set the priority level of the first type of service to high priority;
  • the second type is low error rate.
  • a service with low latency and jitter requirements, that is, a higher demand for the INP protection level, but a service that is not sensitive to delay, such as a video service may set the priority level of the second type of service to a lower priority.
  • the transfer process can be as follows:
  • the service distinguishing module stores different priority services in the low priority service cache and the high priority service cache, respectively, and then through different
  • the service interface is input to the TPS-TC layer, and the service data is encapsulated into a data unit by the TPS-TC layer data processing module, and the SID is identified and sent to the receiving end of the retransmission layer by the transmitting end of the retransmission layer, and at the same time
  • the receiving end does not correctly receive the data unit, the data unit may be retransmitted, and the data unit needs to be stored in the transmitting end retransmission buffer.
  • the receiving end may return to indicate that the receiving data unit succeeds or The failed response message is sent to the sending end. If the sending end receives the response message indicating that the receiving data unit is successful, the corresponding data unit saved in the retransmission buffer of the transmitting end may be deleted, if the transmitting end receives the failure indicating that the receiving data unit fails. In response to the message, the corresponding data unit is extracted from the sender buffer for retransmission. It should be noted that, in the retransmission layer, the PMS-TC layer is included, and when the layers perform data or information transmission, the receiver may also return a feedback message to the sender according to the specific receiving situation or processing situation.
  • the delay monitoring module of the transmitting end of the retransmission layer retransmits by monitoring the transmitting end.
  • the storage state of the space in the cache is used to monitor the delay of the data in the transmission process. For example, it is determined whether the amount of data stored in the retransmission buffer of the sender is greater than a preset threshold. If yes, the delay is greater than a preset threshold. No, the delay is not greater than the preset threshold; when the delay is less than or equal to the preset threshold, the data is transmitted according to the normal flow (see the previous description). When the delay is greater than the preset threshold, the retransmission is performed.
  • the data processing module of the layer sends a data congestion indication to the congestion control module of the TPS-TC layer, and after receiving the data congestion indication, the congestion control module sends blocking information to the lower priority data interface, for example, to the r layer in FIG.
  • the low-priority r interface sends the blocking information, that is, temporarily stops receiving the low-priority data, so as to prevent the data in the retransmission buffer from being retransmitted and causing the transmitted data to be erroneous or lost, thereby implementing the lower priority data.
  • the purpose of the high INP protection level is, temporarily stops receiving the low-priority data, so as to prevent the data in the retransmission buffer from being retransmitted and causing the transmitted data to be erroneous or lost, thereby implementing the lower priority data.
  • the reception of high-priority data is not stopped at this time, because high-priority data does not need to adopt a too high INP protection level, after receiving high-priority data.
  • the so-called special data unit refers to the identifier that the data unit is identified as not requiring retransmission, and is not stored in the retransmission buffer of the receiving end. Instead, it is sent directly to the receiving end. After the receiving end receives it, it does not apply for retransmission of such data unit.
  • the transmitted data may have a large error rate, but from another point of view, it can satisfy a small delay. , meets the low latency requirements of high priority data that does not require any bit error rate.
  • the service is not distinguished between the transmitting end and the receiving end of the retransmission layer, and all service data is randomly stored in the data unit, that is, the retransmission layer still adopts a single delay channel.
  • the data is transmitted, and all data retransmission requests and data transmissions are still performed at the retransmission layer instead of retransmission over the TPS-TC layer.
  • the retransmission layer monitors the data during the retransmission layer transmission process.
  • the delay changes, and the information about the delay variation is fed back to the TPS-TC layer, and the TPS-TC layer processes the services of different priorities according to the information about the delay variation fed back by the retransmission layer, and the retransmission layer
  • the data processing module of the retransmission layer may send a data blocking indication to the congestion control module of the TPS-TC layer, and the congestion control module stops transmitting the blocking information after receiving the solution data blocking indication.
  • you can also start the timer when sending blocking information wait for the scheduled time to elapse, stop The blocking information is sent, so that the function of receiving the low priority service is restored.
  • the processing flow of the data unit at the transmitting end can be as follows:
  • step A303 determining whether the delay is timed out, if not, the process ends; if yes, executing step A304;
  • step A304 after adding the pointer tail Buffer Tail and the delay delay to 1, perform step A305;
  • A305 Determine whether the pointer header Buffer Header is equal to the pointer tail Buffer Tail. If not, the flow ends; if yes, it means that there is no data unit in the buffer of the sender end, and the space is sufficient, so the delay Delay is set to 0, and the data jam indication is The ID (Datapath_L Block Flag) is set to 0 and the process ends.
  • A306 determining whether the difference between the pointer head Buffer Header and the pointer tail Buffer Tail is greater than a preset threshold value of Delay_TH, if yes, executing step A307; if not, executing step A309;
  • A308 adding delay 1 to the delay, and identifying the SID of the data unit with "255", and then sending the data unit to the receiving end, and the process ends.
  • A309. Determine whether the SID of the data unit pointed to by the pointer is less than "244". If yes, after adding the SID of the data unit to 1, perform step S310; if not, set the SID of the data unit to 0, Step A310;
  • the SID of the data unit that can be retransmitted is 0 to 244.
  • A310 The data unit is stored in the retransmission buffer of the sending end, and after the pointer Buffer Header and the delay delay are both added, the data unit is sent to the receiving end, and the process ends.
  • path A is a process for processing a data unit stored in a retransmission buffer of the transmitting end, including a receiving end. Acknowledge the processing of receiving the correct, delay timeout, and sending the unblocking indication; path B is the sending process of the normal data unit (ie, the data unit that can be retransmitted), and path C is a special data unit, that is, including no need to be heavy.
  • the data unit of the identified identifier such as the sending process of the data unit with SID 255.
  • the receiving end of the retransmission layer After the receiving end of the retransmission layer receives the data unit sent by the transmitting end, when determining that the data unit is a special data unit, that is, when determining that the data unit includes an identifier indicating that retransmission is not required, it is not necessary to determine whether the data unit is correct or needs to be Retransmission, etc., directly store the data unit in the receiving end retransmission buffer. For a normal data unit, it is necessary to determine whether the data unit is correct or whether retransmission is required to determine whether the data unit is stored in the retransmission buffer of the receiving end or discarded. As shown in FIG. 7, the specific process may be as follows.
  • the B30K receives the data unit from the PMD-TC layer, and adds 1 delay delay H of the high priority data and the delay Delay_L of the low priority data, and then performs step B302;
  • step B301 If the received data unit is a special data unit in step B301, for example, the SID of the data unit is 255, then in step B302, it can be determined that the SID of the data unit is greater than the pointer pointed by the pointer head Buffer Header.
  • the SID of the data unit (because the SID of the normal data unit is at most 244), therefore, as long as step 302 is performed, it can be simultaneously implemented to "determine whether the data unit includes An operation indicating an identifier that does not need to be retransmitted.
  • step B302 may be added before step B302 to "determine whether the data unit includes a representation that no retransmission is required.
  • Step B305 The SID is looped from 0 to 244, that is, if the SID of the previous data unit has reached the maximum value of 244, the SID of the next new data unit will be set to 0), and if so, the step is executed to perform step B303; Step B305;
  • step B305 determining whether the received data unit is wrong, and if so, discarding the data unit, and if not, executing step B306;
  • the delay monitoring module of the retransmission layer instructs the retransmission layer data processing module to identify different additional identifiers of the data unit by monitoring the state of the retransmission buffer space occupancy of the receiving end. Then, the additional identification information and the data unit are sent to the TPS-TC layer data processing module for processing, and the TPS-TC layer data processing module processes the data unit according to the additional identifier, and is configured by a different service interface, such as the r interface in FIG. Submitted to the upper layer r, the data is classified by the service distinguishing module, and stored in the low priority service cache and the high priority service buffer according to the priority identifier, respectively, to ⁇ ! Send to the interface module. It should be noted that, in the retransmission layer, the PMS-TC layer is included, and when the data is transmitted by each layer, the receiver may also return a feedback message to the sender according to the specific receiving situation or processing situation.
  • the priority of the data in the data unit is not identified, but the additional identification information of the retransmission layer is combined with the data element of the different data unit type on the retransmission layer (ie, Different priority business data) are processed. Therefore, the retransmission layer not only transmits the data unit to the TPS-TC layer, but also needs to transmit the additional identifier of the data unit to the TPS-TC layer. If the additional identifier is represented by Flag, the Flag can be divided into three types, namely Flag_H.
  • the TPS-TC layer performs different processing on the received data unit according to different additional identifiers after receiving the data unit and the additional identifier, for example, if the additional identifier of the data unit is Flag_H , then keep high Priority data, discarding low-priority data; if the additional identifier of the data unit is Flag L, the low-priority data is retained, and the high-priority data is discarded; if the additional identifier of the data unit is Flag_C, all the data is retained.
  • additional identifier refer to the second embodiment, and details are not described herein again.
  • the retransmission buffer at the receiving end is divided into two parts, a basic buffer (Base Buffer) and an extended buffer (Extended Buffer).
  • two sets of delay thresholds are set according to delay requirements of different priority services. They are Delay_TH and Delay_TL, respectively, where Dealy_TH is set according to the delay requirement of the high priority data, and is used to monitor the space occupation state of the basic buffer area; Delay_TL is set according to the delay requirement of the low priority data, and is used.
  • the two pointer tails Buffer Tail-B and Buffer Tail-E should be coincident;
  • the uncorrected data unit will be stored in the extended buffer area.
  • the two pointers are Buffer Tail_B and Buffer Tail— E is not equal; wherein, the pointer head points to the latest received data unit, and the pointer tail points to the earliest received data unit; then, the delay of the high priority data Delay-H should be equal to the pointer header Buffer Header and the pointer tail Buffer Tail—
  • the difference of B, and the delay of the low priority data Delay_IjS is equal to the difference between the pointer Buffer Header and the pointer end Buffer Tail_E; the receiving end will retransmit the buffered pointer and tail of the buffer according to the receiving end and the two delay thresholds
  • the configuration performs different operations on different data and sets different additional flags for the data unit. As shown in Figure 10, the processing flow of the data unit at the receiving end can be as follows:
  • step C301 determining whether the pointer tail Buffer Tail - B and the pointer tail Buffer Tail - E are equal, if yes, proceed to step C302, if not, proceed to step C306;
  • step C301 it is determined that there is a data unit that is not modified in the extension value Delay_H of the high-priority service in the retransmission buffer of the receiving end, and if there is a high-priority service delay threshold in the retransmission buffer of the receiving end, If the data unit is not corrected in Delay_H, then the pointer tail Buffer Tail-B and the pointer tail Buffer D1_£ are not equal. If there is no unresolved data in the high-priority service delay threshold Delay_H in the retransmission buffer of the receiving end Unit, then the pointer tail Buffer Tail_B and the pointer tail Buffer Tail—E is not equal;
  • step C302. Determine whether a new data unit needs to be submitted to the upper layer. If yes, execute step C303. If no, the process ends. Specifically, it may be determined whether the delay 061 & ⁇ 1 of the high priority data is greater than Dealy_TH, and if not, No new data unit needs to be submitted to the upper layer, the process ends, and if so, it means that a new data unit needs to be submitted to the upper layer, and step C303 is performed;
  • step C303 determining whether the new data unit that needs to be submitted to the upper layer is correct, if yes, executing step C304, if not, executing step C305; specifically, determining whether the data unit pointed to by the pointer tail Buffer Tail_B is incorrect, if not, Representing the new data unit that needs to be submitted to the upper layer is correct, executing step C304, and if so, representing the new data unit error that needs to be submitted to the upper layer, executing step C305;
  • Flag_C that is, the data unit identifier pointed to by the pointer tail Buffer Tail_B, and submit the data unit to the upper layer, that is, the TPS-TC layer, and then the tail of the pointer Buffer Ding & 11_8 and Buffer Tail-E are both added 1, Delay_H and Delay-L are both decremented by 1, and the process ends;
  • Flag_H is the pointer tail.
  • Buffer Tail The data unit pointed to by B is marked with Flag_H, and the data unit is submitted to the upper layer, that is, the TPS-TC layer, and then the pointer tail Buffer Tail_B is incremented by 1, Delay-H minus 1 , and the process ends;
  • step C306. Determine whether a new data unit needs to be submitted to the upper layer. If yes, execute step C307 on the one hand and step C308 on the other hand. If no, execute step C308. Specifically, determine the delay of the high priority data. Whether _ ⁇ is greater than Dealy_TH, and if so, it means that there is a new data unit that needs to be submitted to the upper layer, so on the one hand, step C307 is performed, on the other hand, step C308 is performed; if not, it means that no new data unit needs to be submitted to the upper layer, so only execution is performed. Step C308;
  • step C307 for the new data unit identifier that needs to be submitted to the upper layer, Flag_H, that is, the data unit identifier pointed to by the pointer tail Buffer Tail-B, and the data unit is submitted to the upper layer, that is, the TPS-TC layer. Then, the pointer tail buffer is 11_8 plus 1, and Delay_H is subtracted by 1. It should be noted that the execution order of step C307 and step C308 may be in no particular order.
  • step C308. Determine whether the uncorrected data unit (that is, the data unit stored in the extended buffer area) is correct. If yes, execute step C310. If not, execute step C309; specifically, determine that the pointer tail Buffer is ⁇ 1_£ Whether the data unit pointed to is wrong, and if so, the number that has not been corrected According to the unit error, then step C309 is performed, if not, it represents that the uncorrected data unit is correct, and then step C310 is performed;
  • step C309 determining whether the uncorrected data unit needs to be submitted to the upper layer, and if yes, executing step C310; if not, the process ends; specifically, determining whether the delay Delay_L of the low priority data is greater than Dealy_TL, and if so, representing The uncorrected data unit needs to be submitted to the upper layer, and then step C310 is performed; if not, the uncorrected data unit does not need to be submitted to the upper layer, and the process may end;
  • the TPS-TC layer will make a reservation or discard of the data unit based on the additional identification.
  • the scheme for processing the data unit in the retransmission buffer of the receiving end may also be used as an independent solution, that is, the implementation of the scheme described in steps C301 to C309 is also the same.
  • the object of embodiments of the invention may be implemented.
  • the embodiment of the present invention determines whether to send blocking information for blocking low-priority data sent by the upper layer by monitoring the delay of the data in the transmission process, so as to avoid data overflow in the retransmission buffer of the transmitting end, thereby realizing Higher INP protection for low priority data.
  • the sender can continue to receive high priority data, and when encapsulating high priority data, The identifier indicates that the identifier does not need to be retransmitted, so that when receiving the high priority data, the receiving end does not need to determine whether the data unit is correct or needs to be retransmitted, etc., but directly stores the data unit in the receiving.
  • the end retransmission buffer in this way, can reduce the number of retransmission requests at the receiving end and reduce the delay of the data unit of the type, thereby ensuring the low latency requirement of the high priority data.
  • the receiving end may further add an identifier to the data unit identifier in the retransmission buffer of the receiving end by monitoring the delay state, so as to indicate that the upper layer reserves or discards data of different priority levels after receiving the data unit. Therefore, the data transmission process that can distinguish the service type is completed by the sender, for example, a service that is sensitive to delay but does not require a bit error rate can adopt a lower INP protection level, and does not perform after a certain delay.
  • the embodiment of the present invention further provides a transmitting end 400.
  • the transmitting end device 400 includes a monitoring unit 401, a blocking information sending unit 402, a receiving unit 403, and a packaging unit. 404 and transmitting unit 405; It should be noted that, in order to better explain the relationship between the various units, the upper layer device 700 is also shown in FIG. 11;
  • the monitoring unit 401 is configured to monitor the delay of the data in the transmission process. Specifically, the delay of the data in the transmission process may be monitored by monitoring the storage state of the space in the retransmission buffer of the transmitting end, for example, determining the retransmission buffer in the sending end. Whether the amount of saved data is greater than a preset threshold, if yes, indicating that the delay is greater than a preset threshold, and if not, indicating that the delay is not greater than a preset threshold;
  • the blocking information sending unit 402 is configured to: when the monitoring unit 401 determines that the delay is greater than the first delay threshold
  • the blocking information is sent, where the blocking information is used to block the low-priority data sent by the upper-layer device 700, and the blocking information may be specifically hardware.
  • the receiving unit 403 is configured to receive high priority data sent by the upper layer device 700.
  • the encapsulating unit 404 is configured to encapsulate the high-priority data received by the receiving unit 403 into a data unit, and identify an identifier that indicates that the retransmission is not required; wherein the identifier that does not need to be retransmitted may be a specific one.
  • the SID such as 255, may also be other SIDs negotiated by the sender and the receiver, or may be identified by an independent Flag in the data unit;
  • the sending unit 405 is configured to send the data unit encapsulated by the encapsulating unit 404 to the receiving end.
  • the transmitting device 400 may further include an empty data encapsulating unit;
  • the null data encapsulating unit is configured to encapsulate the null data into a data unit, and identify an identifier indicating that no retransmission is needed. It should be noted that the empty data encapsulation unit and the encapsulation unit 404 can be the same entity.
  • the sending unit 405 is further configured to send the data unit encapsulated by the null data encapsulating unit to the receiving end.
  • the delay in the transmission process is used to determine whether the blocking information sending unit 402 sends the blocking information for blocking the low priority data to the upper layer device 700, so as to prevent the transmitting device 400 from retransmitting the data overflow in the buffer, thereby achieving low
  • the higher INP protection of the priority data at the same time, because only the low priority data is blocked at this time, the receiving unit 403 of the transmitting device 400 can continue to receive the high priority data, and the high priority in the encapsulating unit 404
  • the data is encapsulated, it indicates that the identifier does not need to be retransmitted, so that the receiving end does not apply for retransmission when receiving the high priority data, thereby ensuring low delay requirement of high priority data.
  • the embodiment of the present invention can meet different delay requirements of different services and different INP protection level requirements, and improve the QoE of the user's integrated service.
  • a service that is more sensitive to delay but does not require a bit error rate can adopt a lower INP protection level.
  • Lower services can use higher ITP protection levels and require retransmission.
  • the embodiment of the present invention further provides a receiving end device.
  • the receiving end device includes a receiving unit 501, an identifier identifying unit 502, and a storage unit 503;
  • the receiving unit 501 is configured to receive a data unit sent by the sending end.
  • the identifier identifying unit 502 is configured to determine whether the data unit received by the receiving unit 501 includes an identifier indicating that retransmission is not required;
  • the storage unit 503 is configured to store the data unit in the receiving end retransmission buffer when the identifier identifying unit 502 determines that the data unit includes an identifier indicating that retransmission is not required.
  • the identifier indicating that the retransmission is not required may be a specific SID, such as 255, or may be another SID negotiated by the sender and the receiver, or may be an independent additional identifier in the data unit. As shown in FIG. 12, it may further include a new and old judgment unit 504, a correctness judgment unit 505, a discarding unit 506, and a timeout judging unit 507;
  • the old and new judging unit 504 is configured to: when the identifier identifying unit 502 determines that the data unit does not include an identifier indicating that retransmission is not required, determine whether the data unit is a new data unit; that is, determine whether the data unit is a new data unit or a retransmission
  • the data unit may be determined according to the SID of the data unit.
  • the storage unit 503 is configured to store the data unit in the retransmission buffer of the receiving end when the new and old determining unit 504 determines that the data unit is a new data unit.
  • the timeout determining unit 507 determines the said When the data unit does not time out, the data unit is stored in the receiving end retransmission buffer; the correctness determining unit 505 is configured to determine whether the data unit is wrong when the new and old determining unit 504 determines that the data unit is not a new data unit. ;
  • the discarding unit 506 is configured to discard the data unit when the correctness determining unit 505 determines that the data unit has an error, or discard the data unit when the timeout determining unit 507 determines that the data unit times out;
  • the timeout determining unit 507 is configured to determine whether the data unit has timed out when the correctness determining unit 505 determines that the data unit has no error.
  • the receiving end device may further include an additional identifying unit and a submitting unit;
  • An additional identifier unit is configured to add an identifier to the data unit identifier in the receiving end retransmission buffer by monitoring the delay state, where the additional identifier indicates a processing manner after the upper layer receives the data unit; for example:
  • an additional identifier indicating normality is indicated for the data unit, such as Flag_C; when it is determined that a new data unit needs to be submitted to the upper layer, And determining the data unit error, adding an additional identifier indicating that the high priority service data is reserved and discarding the low priority service data, such as Flag_H; if present, determining that a new data unit is needed When submitting to the upper layer, an additional identifier indicating that high priority service data is reserved and low priority service data is discarded for this data unit identifier, such as Flag_H, on the other hand, is determined for the uncorrected data unit within the high priority threshold.
  • an additional identifier indicating that the low priority service data is reserved and the high priority service data is discarded is discarded for the data unit identifier, such as Flag_L 0
  • a submitting unit configured to submit the data unit after the identifier of the additional identifier unit to the upper layer, so that the upper layer processes the data unit according to the additional identifier. For example, when the data unit in the cache is identified as indicating a normal additional identifier, the data unit is removed from the receiving end retransmission buffer and submitted to the upper layer; when the data unit in the cache is identified, the high priority service data is reserved.
  • the data unit When discarding the additional identifier of the low priority service data, the data unit is copied and submitted to the upper layer; that is, the data unit will still be Cached in the retransmission buffer (ie, not removed from the retransmission buffer of the receiving end), these data units are uncorrected data units within the high priority service time delay value, and the time of these data units exceeds the low priority
  • the correct data unit that can still be retransmitted before the service delay threshold is modified; when the data unit in the cache is identified as an additional identifier indicating that the low priority service data is reserved and the high priority service data is discarded, the data unit is heavy from the receiving end Move out of the cache and submit to the upper layer.
  • the additional identifier of the data unit is a normal additional identifier, such as Flag_C
  • all data is retained, that is, high priority data and low priority data; otherwise, according to the indication on the additional identifier Processing, only one of high priority data and low priority data is reserved. For example, if it is Flag_L, only low priority data is retained, and high priority data is discarded. If it is Flag_H, only high priority is reserved. Level data, and discard low priority data.
  • the embodiment of the present invention further provides another receiving end device, including an additional identifying unit and a submitting unit;
  • An additional identifier unit configured to add an identifier to the data unit identifier in the receiving end retransmission buffer by monitoring the delay state, where the additional identifier indicates a processing manner after the upper layer receives the data unit; and the submitting unit is configured to attach The data unit identified by the identification unit is submitted to the upper layer, so that the upper layer processes the data unit according to the additional identifier.
  • the receiving unit 501 of the receiving device of the present embodiment does not need to determine the data unit if the identifier identifying unit 502 determines that the data unit includes an identifier indicating that retransmission is not required. Whether it is correct or whether it needs to be retransmitted, etc., but the storage unit 503 directly stores the data unit in the retransmission buffer of the receiving end, so that the number of retransmission requests of the receiving end device and the delay of the data unit can be reduced.
  • the additional identifier unit of the receiving end device may further add an identifier to the data unit identifier in the receiving end retransmission buffer by monitoring the delay state, so as to indicate that the upper layer receives data of different priority levels after receiving the data unit.
  • the process of retaining or discarding is performed to cooperate with the transmitting device to complete a data transmission process that can distinguish the service type. For example, a service that is more sensitive to delay but does not require a bit error rate can adopt a lower IP protection level. Retransmission is not performed after a certain delay, and is not sensitive to delay but requires a higher bit error rate. Low-level services can adopt higher levels of the same INP protection level, and need to be retransmitted to achieve different industries. The different delay requirements and the purpose of different INP protection level requirements, improve the QoE of the user's integrated services.
  • the embodiment of the present invention further provides a communication system.
  • the communication system includes any of the transmitting end device 601 and any receiving end provided by the embodiment of the present invention.
  • the transmitting end device 601 is configured to monitor the delay of the data in the transmission process. If the delay is greater than the first delay threshold (in the embodiment of the present invention, the preset delay preset), the sending is performed.
  • the blocking information may specifically be a hardware blocking signal, a blocking data, or a blocking flag;
  • the receiving end device 602 is configured to receive the data unit sent by the sending end device 601, and determine that the data unit includes an identifier that does not need to be retransmitted, and store the data unit in the receiving end retransmission buffer.
  • the receiving end device 602 is further configured to: add an identifier to the data unit identifier in the retransmission buffer of the receiving end by monitoring the delay state, where the additional identifier indicates a processing manner after the upper layer receives the data unit, and The data unit is submitted to the upper layer so that the upper layer processes the data unit according to the additional identifier.
  • the transmitting end device 601 may include a monitoring unit 401, a blocking information sending unit 402, a receiving unit 403, an encapsulating unit 404, and a sending unit 405.
  • the transmitting end device 601 may further include an empty data encapsulating unit.
  • the receiving device 602 may include a receiving unit 501, an identifier identifying unit 502, and a storage unit 503.
  • the receiving device 602 may further include a new and old determining unit 504, a correctness determining unit 505, a discarding unit 506, and a timeout determining unit 507; further,
  • the receiving device 602 can also include an additional identification unit and a submitting unit.
  • the sender device 601 of the embodiment of the present invention can determine whether to send blocking information for blocking low-level data sent by the upper layer by monitoring the delay of the data in the transmission process, so as to avoid the sending end. Retransmit the data overflow in the cache, thus achieving a higher INP for low priority data Protection, at the same time, since only the low priority data is blocked at this time, the transmitting device 601 can continue to receive the high priority data, and when the high priority data is encapsulated, the identifier indicates that the retransmission is not required.
  • the identifier is such that when receiving the high priority data, the receiving device 602 does not need to determine whether the data unit is correct or needs to be retransmitted, etc., but directly stores the data unit in the receiving end retransmission buffer. In this way, the number of retransmission requests at the receiving end and the delay of the data unit can be reduced, thereby ensuring low latency requirements for high priority data. Further, the receiving end device 602 may further add an identifier to the data unit identifier in the retransmission buffer of the receiving end by monitoring the delay state, so as to indicate that the upper layer reserves or discards data of different priority levels after receiving the data unit. Processing, so that the sender device 601 can complete the data transmission process that can distinguish the service type.
  • a service that is more sensitive to delay but does not require a bit error rate can adopt a lower INP protection level.
  • the service that is insensitive to the delay but has a lower bit error rate can adopt a higher level of the same INP protection level, and needs to be retransmitted to achieve different delay requirements and different INPs for different services.
  • the purpose of the protection level requirement is to improve the QoE of the user's integrated service.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Quality & Reliability (AREA)
  • Communication Control (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Detection And Prevention Of Errors In Transmission (AREA)

Description

一种数据传送方法、 装置和通信系统
本申请要求于 2010 年 5 月 22 日提交中国专利局、 申请号为 200910202946.5, 发明名称为"一种数据传送方法、 装置和通信系统"的中国专 利申请的优先权， 其全部内容通过引用结合在本申请中。
技术领域
本发明涉及通信技术领域，具体涉及一种数据传送方法、装置和通信系统。
背景技术
在原有的数字用户系统（DSL, Digital subscriber line) 中， 由于受脉冲噪 声的影响， 线路中的数据常常会出现误码的情况， 为了保证 DSL系统的稳定 性， 脉冲噪声保护 （INP， Impulse noise protection )技术应运而生， INP技术 主要通过使用纠错码来纠正在发送的数据中所产生的误码，例如利用里德 -所 罗门 （RS， Reed-Solomon )编码额外提供的编码增益， 来削减脉冲噪声所产 生的影响， 从而提高 DSL系统的稳定性。 但是随着带宽的增大， 以及速率的 提高， 若仍然使用原有的 RS编码方案， 则需要使用具有较多的校验字节 （即 冗余）和长度较小的 RS码字， 此时， RS编码的净增益将会变为负值， 不利 于速率的提高， 而且系统所提供的 INP保护无法应对超长脉冲噪声的影响。
为更好的应对超长脉冲噪声对 xDSL系统的影响，物理层的重传方案应运 而生， 目前的重传方案有传送协议相关汇聚子层（TPS-TC, Transport Protocol Specific Transmission Convergence Layer)、物理媒质相关汇聚子层（ PMS-TC, Physical Media-Specific Transmission Convergence Layer) 和物理介质关联层接 口 （PMD， Physical Media Dependent Layer )层的重传机制。 重传方案能够对 脉冲噪声所破坏的数据进行重新发送，从而降低线路的误码率，提高业务稳定 性。
在对现有技术的研究和实践过程中，本发明的发明人发现， 虽然重传方案 在一定程度上緩解了超长脉冲噪声对系统的影响， 提高了系统的业务稳定性， 但同时也带来了较大的时延 ( Delay ) ， 例如位于 PMS-TC层的重传系统额外 增加的时延大约在 10ms以上， 最大数据延迟甚至达到 20ms以上， 这样的延 迟对于误码率要求髙、 时延要求低的业务来说， 影响不大。但是对于误码率要 求低、时延要求高的业务来说，则会严重地降低用户的体验质量（QoE， Quality of experience )。 发明内容
本发明实施例提供一种数据传送方法、装置和通信系统，可以满足不同业 务的不同时延需求和不同 INP保护等级需求。
一种数据传送方法， 包括：
监控数据在传输过程中的时延；
若时延大于第一时延阈值， 则发送阻塞信息， 所述阻塞信息用于堵塞上层 发送的低优先级数据；
接收上层发送的高优先级数据；
将所述高优先级数据封装成数据单元， 并标识上表示不需要重传的标识； 将数据单元发送给接收端。
一种数据传送方法， 包括：
接收发送端发送的数据单元；
确定所述数据单元包括表示不需要重传的标识时，将所述数据单元存入接 收端重传緩存中；
确定所述数据单元不包括表示不需要重传的标识时，判断所述数据单元是 否新的数据单元；
若是， 将所述数据单元存入接收端重传緩存中；
若否， 判断所述数据单元是否错误， 若有错误， 丢弃所述数据单元， 若没 有错误， 进一步判断所述数据单元是否超时， 若超时， 丢弃所述数据单元， 若 没有超时， 将所述数据单元存入接收端重传緩存中。
一种数据传送方法， 包括：
通过对时延状态的监控为接收端重传緩存中的数据单元标识上附加标识， 所述附加标识指示上层接收到数据单元后的处理方式；
将数据单元提交到上层， 以便上层根据附加标识对所述数据单元进行处 理。
一种发送端设备， 包括：
监控单元， 用于监控数据在传输过程中的时延；
阻塞信息发送单元， 用于当监控单元确定时延大于第一时延阈值时，发送 阻塞信息， 所述阻塞信息用于堵塞上层发送的低优先级数据；
接收单元， 用于接收上层发送的高优先级数据； 封装单元， 用于将所述接收单元接收到的高优先级数据封装成数据单元， 并标识上表示不需要重传的标识；
发送单元， 用于将封装单元封装后的数据单元发送给接收端。
一种接收端设备， 包括：
接收单元， 用于接收发送端发送的数据单元；
标识识别单元，用于确定所述接收单元接收到的数据单元是否包括表示不 需要重传的标识；
新旧判断单元，用于当所述标识识别单元确定所述数据单元不包括表示不 需要重传的标识时， 判断所述数据单元是否新的数据单元；
存储单元，用于当所述标识识别单元确定所述数据单元包括表示不需要重 传的标识时，或者当所述新旧判断单元判断数据单元为新的数据单元时，将所 述数据单元存入接收端重传緩存中；
正确性判断单元，用于当所述新旧判断单元判断数据单元不是新的数据单 元时， 判断所述数据单元是否错误；
超时判断单元， 用于当所述正确性判断单元判断所述数据单元没有错误 时， 判断所述数据单元是否超时；
丢弃单元，用于当所述正确性判断单元判断所述数据单元有错误时，丢弃 所述数据单元，或者当所述超时判断单元判断所述数据单元超时时，丢弃所述 数据单元。
一种接收端设备， 包括：
附加标识单元，用于通过对时延状态的监控为接收端重传緩存中的数据单 元标识上附加标识， 所述附加标识指示上层接收到数据单元后的处理方式； 提交单元，用于将附加标识单元标识后的数据单元提交到上层， 以便上层 根据附加标识对所述数据单元进行处理。
一种通信系统， 包括：
发送端端设备， 用于监控数据在传输过程中的时延， 若时延大于第一时延 阈值， 则发送用于堵塞上层发送的低优先级数据的阻塞信息，接收上层发送的 高优先级数据，将所迷髙优先级数据封装成数据单元， 并标识上表示不需要重 传的标识， 将数据单元发送给接收端设备；
接收端设备， 用于接收发送端设备发送的数据单元， 确定所述数据单元包 括表示不需要重传的标识时， 将所述数据单元存入接收端重传緩存中。
本发明实施例通过监控数据在传输过程中的时延，来确定是否发送用于堵 塞上层发送的低优先级数据的阻塞信息， 以避免发送端重传缓存中数据溢出， 从而实现了对低优先级数据的较高 IN 保护， 同时， 由于此时只对低优先级数 据进行堵塞， 因此发送端还可以继续接收高优先级数据， 并且在对高优先级数 据进行封装时，对其标识上表示不需要重传的标识 ,使得接收端在接收到该高 优先级数据时不会对其申请重传，从而保证了高优先级数据的低时延需求， 也 就是说，采用本发明实施例可以满足不同业务的不同时延需求和不同 INP保护 等级需求， 提高了用户的综合业务的 QoE。
附图说明
图 1是本发明实施例一所提供的方法的流程图；
图 2是本发明实施例二所提供的方法的流程图；
图 3是本发明实施例三所提供的方法传送示意图；
图 4是本发明实施例三所提供的方法中发送端的处理示意图；
图 5是本发明实施例三所提供的方法中发送端重传緩存的示意图； 图 6是本发明实施例三所提供的发送端数据单元处理流程图；
图 7是本发明实施例三所提供的接收端数据单元处理流程图；
图 8是本发明实施例三所提供的方法中接收端的处理示意图
图 9是本发明实施例三所提供的方法中接收端重传緩存的示意图； 图 10是本发明实施例三所提供的另一个接收端数据单元处理流程图； 图 11是本发明实施例所提供的发送端设备的结构示意图；
图 12是本发明实施例所提供的接收端设备的结构示意图；
图 13是本发明实施例所提供的通信系统的结构示意图。
具体实施方式
下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清 楚、 完整地描述， 显然， 所描述的实施例仅仅是本发明一部分实施例， 而不是 全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有作出创造 性劳动前提下所获得的所有其他实施例， 都属于本发明保护的范围。
本发明实施例提供一种数据传送方法。本发明实施例还提供相应的装置和 通信系统。 以下分别进行详细说明。 实施例一、
本实施例将从发送端的角度进行描述。
一种数据传送方法， 包括： 监控数据在传输过程中的时延， 若时延小于等 于第一时延阈值， 则按现有的方案进行处理， 若时延大于第一时延阈值， 则发 送用于堵塞上层发送的低优先级数据的阻塞信息，由于此时低优先级数据被阻 塞信息所阻挡， 因此此时只接收到上层发送的高优先级数据，在接收到高优先 级数据后，将高优先级数据封装成数据单元，并标识上表示不需要重传的标识， 然后将数据单元发送给接收端，使得接收端在接收到该标识有表示不需要重传 的标识的数据单元后，不会对其申请重传。其中，第一时延阈值可以是预置的， 也可以根据系统在运行的过程中进行自行的调整来设置， 等等， 为了描述方便 本发明实施例的第一时延预置均以预置为例进行说明。 如图 1所示， 具体流程 可以: ^下：
101、 监控数据在传输过程中的时延， 若时延小于等于预置的时延阁值， 则按现有的方案进行处理； 若时延大于预置的时延阔值， 则执行步骤 102; 具体可以通过监控发送端重传缓存中空间的存储状态来监控数据在传输 过程中的时延，例如，确定发送端重传緩存中保存的数据量是否大于预置的阔 值，若是，则表示时延大于预置的阈值，若否，则表示时延不大于预置的阔值。
102、 发送阻塞信息， 所述阻塞信息用于堵塞上层（即 TPS-TC层的上层） 发送的低优先级数据； 该阻塞信息具体可以为硬件阻塞信号、 阻塞数据或阻塞 标志等；
这是因为， 如果此时还继续接收低优先级数据的话， 那么， 发送端重传緩 存的空间将会不足， 即可能会出现数据溢出的情况，如果这些溢出的数据又恰 巧没有被接收端正确接收的话， 则此时无法进行重传（因为发送端重传緩存中 没有保存这些数据），将会出现数据出错或丢失的情况，即无法体现 INP保护的 功能， 因此， 本发明实施例在确定发送端重传緩存的空间较满时， 发送阻塞信 息， 以暂时停止对低优先级数据的接收，从而来保证对低优先级数据实现较高 INP保护等级。
需说明的是， 其中， 数据的优先级可以由运营商进行预置， 例如， 如果是 对时延比较敏感，但对误码率没有什么要求的业务，比如网络电话（ VoIP, Voice over IP ) 和实时视频通话等， 则可以将其业务数据设置为高优先级（ High priority )数据； 如果是对时延不敏感， 但需要较低误码率的业务， 比如视频业 务等， 则可以将其业务数据设置为低优先级（ Low Priority )数据。
103、 接收上层， 即 TPS-TC层的上层发送的高优先级数据；
由于在步骤 102中低优先级数据已经被堵塞， 因此此时只能接收到上层发 送的高优先级数据； 也就是说， 此时将会暂时停止接收对时延不敏感， 但需要 较低误码率的低优先级数据， 而为了保证对时延敏感，但对误码率没有什么要 求的高优先级数据的低时延需求， 将会继续保持对高优先级数据的正常接收， 只是此时将接收到的高优先级数据封装成数据单元后，并不存入发送端重传緩 存中， 而是对这些数据单元标识上表示不需要重传的标识（参见步骤 104 )后， 直接传送给接收端， 这样， 在保证高优先级数据的低时延需求的同时， 也不会 造成如步骤 102中所说的可能会出现数据溢出的情况。
104、 将所述高优先级数据封装成数据单元， 并标识上表示不需要重传的 标识；
其中，该表示不需要重传的标识具体可以为某个特殊的业务序列号（ SID, Sequence Identifier ), 比如 255, 或者也可以是经发送端与接收端协商而定的其 它 SID, 或者也可以用数据单元中独立的附加标识（Flag )来标识；
需说明的是， 若步骤 103中没有接收到高优先级数据， 或者接收到高优先 级数据不足， 为了保证发送端与接收端之间数据传送的连续性，此时还可以将 空 （IDLE )数据封装成数据单元， 并标识上表示不需要重传的标识后， 发送 给接收端。也就是说，这种具有表示不需要重传标识的数据单元只用于承载高 优先级数据和空数据， 而且，这种具有表示不需要重传标识的数据单元将不会 被緩存入发送端重传緩存中（可参见步骤 103中的说明）， 同时， 接收端也不会 对此类数据单元申请重传。由于这种具有表示不需要重传标识的数据单元所承 栽的数据都不会进行重传， 所以传送的数据可能会出现较大的误码率，但从另 一个角度来说， 却可以满足较小的时延。 另外， 还有一点需要说明的是， 需说 明的是， 高优先级数据和空数据可以分别进行独立的封装，也可以封装在同一 个数据单元中， 即数据单元里可能包括有高优先级数据和空数据，也可能只包 括高优先级数据或空数据；
105、 将数据单元发送给接收端， 该数据单元中包括有业务的类型信息和 数据单元的 SID信息， 以便接收端接收到数据单元后可以依据这些信息进行处 理。
需说明的是， 业务的类型信息和数据单元的 SID信息可以复用数据单元中 同一字段的信息进行标识或者采用数据单元的不同字段进行标识。
由上可知，本发明实施例通过监控数据在传输过程中的时延， 来确定是否 发送用于堵塞上层发送的低优先级数据的阻塞信息，以避免发送端重传緩存中 数据溢出， 从而实现了对低优先级数据的较高 INP保护， 同时， 由于此时只对 低优先级数据进行堵塞， 因此发送端还可以继续接收高优先级数据， 并且在对 高优先级数据进行封装时，对其标识上表示不需要重传的标识，使得接收端在 接收到该高优先级数据时不会对其申请重传，从而保证了高优先级数据的低时 延需求，也就是说，采用本发明实施例可以满足不同业务的不同时延需求和不 同 INP保护等级需求， 提高了用户的综合业务的 QoE。 例如， 对于对时延较为 敏感但对误码率没有要求的业务可以采用较低的 INP保护等级， 在超过某个时 延阈值时不再进行重传，对于时延不敏感但误码率要求较低的业务可以采用较 高的同 INP保护等级， 需要进行重传。 实施例二、
本实施例将从接收端的角度进行描述。
一种数据传送方法，接收发送端发送的数据单元，在确定数据单元包括表 示不需要重传的标识时， 将该数据单元存入接收端重传緩存中。 也就是说， 不 需要判断该数据单元是否正确或者是否需要重传等等，而是直接将该数据单元 存入接收端重传緩存中，这样，可以减少接收端重传申请数量以及减少该类数 据单元（即包括表示不需要重传标识的数据单元） 的时延。
另夕卜，如果确定数据单元不包括表示不需要重传的标识时， 则还需要对该 数据单元做一定的处理后才确定是否将该数据单元存入接收端重传缓存中，参 见图 2, 以下将进行简略说明， 流程如下：
201、 接收发送端发送的数据单元；
202、 判断接收到的数据单元是否包括表示不需要重传的标识， 若是， 则 执行步骤 203, 若否， 则执行步骤 204;
其中， 该表示不需要重传的标识具体可以为某个特殊的 SID, 比如 255, 或者也可以是经发送端与接收端协商而定的其它 SID, 或者也可以用数据单元 中独立的附加标识来标识；
对此类数据单元，接收端不会申请重传， 而是直接存入接收端重传缓存中
(步骤 203 )。 由于不会进行重传， 所以传送的数据可能会出现较大的误码率， 但却可以满足较小的时延， 因此，这种具有表示不需要重传标识的数据单元只 用于承载高优先级数据和空数据。
203、 将该数据单元存入接收端重传缓存中； 需说明的， 这里所说的将该 数据单元存入接收端重传緩存中还包括：如果接收端重传緩存中已经保存有相 应的数据单元， 即如果该需要存入的数据单元是重传的数据单元的话， 则替换 緩存中现有的数据单元；
204、 判断该数据单元是否新的数据单元， 即判断该数据单元是新的数据 单元还是重传的数据单元， 比如可以根据数据单元的 SID来进行判断， 若为新 的数据单元， 则执行步骤 203， 即将所述数据单元存入接收端重传緩存中， 否 则， 若为重传的数据单元， 则执行步骤 205;
205、 判断该数据单元是否错误， 若有错误， 则执行步骤 206， 若无错误， 则执行步骤 207;
206、 丢弃所述数据单元；
207、 判断所述数据单元是否超时， 比如， 可以根据数据单元的 SID来进 行判断， 若超时， 执行步骤 206， 即丢弃所述数据单元； 若没有超时， 则执行 步骤 203， 即将所述数据单元存入接收端重传缓存中。
对接收端重传緩存中的数据单元的处理可以如下：
通过对时延状态的监控为接收端重传緩存中的数据单元标识上附加标识， 所述附加标识指示上层接收到数据单元后的处理方式； 例如，可以采用如下方 法：
( 1 )判断接收端重传缓存中是否存在高优先级业务时延阈值内未被修正 的数据单元；
若接收端重传缓存中不存在高优先级业务时延阈值内未被修正的数据单 元， 则在确定有新数据单元需要提交到上层， 且确定该数据单元正确时， 为该 数据单元标识上表示正常的附加标识， 比如 Flag_C; 在确定有新数据单元需要 提交到上层，且确定该数据单元错误时， 为该数据单元标识上表示保留高优先 级业务数据而丢弃低优先级业务数据的附加标识， 比如 Flag_H; 若接收端重传缓存中存在高优先级业务时延阈值内未被修正的数据单元， 则一方面在确定有新数据单元需要提交到上层时，为此数据单元标识上表示保 留高优先级业务数据而丢弃低优先级业务数据的附加标识， 比如 Flag_H, 另一 方面对高优先级阔值内未被修正的数据单元进行判断，在确定高优先级业务时 延阈值内未被修正的数据单元需要提交时，为该数据单元标识上表示保留低优 先级业务数据而丢弃高优先级业务数据的附加标识， 比如 Flag_L。
( 2 )将数据单元提交到上层， 即从重传层提交到 TPS-TC层， 以便上层根 据附加标识对所述数据单元进行处理； 具体可以如下：
当緩存中的数据单元被标识上表示正常的附加标识时，将数据单元从接收 端重传緩存中移出并提交到上层；
当緩存中的数据单元被标识上表示保留高优先级业务数据而丢弃低优先 级业务数据的附加标识时， 复制数据单元并提交到上层； 即此时数据单元仍然 会被缓存在重传缓存中 （即不从接收端重传緩存中移出）， 这些数据单元就是 高优先級业务时延阈值内未被修正的数据单元，这些数据单元的时延在超出低 优先级业务时延阈值前仍可以被重传的正确数据单元修正；
当緩存中的数据单元被标识上表示保留低优先级业务数据而丢弃高优先 级业务数据的附加标识， 将数据单元从接收端重传緩存中移出并提交到上层。
上层在接收到提交的数据单元后，如果数据单元的附加标识为正常的附加 标识， 比如 Flag— C，则保留全部数据， 即高优先级数据和低优先级数据； 否则， 按照附加标识上的指示进行处理，只保留高优先级数据和低优先级数据中的一 种， 比如， 如果是 Flag_L， 则只保留低优先级数据， 而丢弃高优先级数据， 如 果是 Flag— H, 则只保留高优先级数据， 而丢弃低优先级数据。
这是因为，一般的，当数据单元的时延大于等于高优先级业务时延阈值时， 接收端重传緩存中的数据单元将会开始被提交到上层进行处理，如果此时接收 端重传緩存中的数据单元已经在预置的时间（即高优先级业务时延阈值）内被 修正，且数据单元正确的话， 则意味着所提交给上层的数据单元都是正确的数 据， 所以可以保留全部数据； 而如果接收端重传緩存中的数据单元没有在预置 的时间内 （即高优先级业务时延阈值）被修正， 同时接收端重传緩存中数据单 元的时延高于任意一个时延阈值（高优先级业务时延阈值或低优先级业务时延 阔值）， 则数据单元将会被提交两次给上层， 第一次提交是在数据单元的时延 超过高优先级业务时延阈值时， 由于前面所说的 "接收端重传緩存中的数据单 元没有在预置的时间内被修正"， 所以此时重传层的接收端一方面会将数据单 元提交到上层，一方面会将错误的数据单元以及该数据单元后面的数据单元移 入接收端重传緩存中的扩展存储区，以提供给这些错误的数据单元再一次被纠 正的机会， 由于此时高优先级数据即使发生错误不会进行重传， 而低优先级数 据则可以进行重传， 可能在第二次提交时可以得到正确的数据， 所以此时保留 高优先级数据而丢弃低优先级数据；第二次提交是在接收端重传緩存中的数据 单元的时延大于等于低优先级业务数据时延阈值时，由于高优先级数据在第一 次提交时已经被保留了， 所以无需重复保留， 于是将高优先级数据单元直接丢 弃， 而低优先级数据由于已经进行了重传， 所以此时接收到的可能是经过重传 后的正确数据， 所以进行保留。 需说明的是， 上面所描述的仅仅是例子， 并不 排除可以定义在未超过高优先级业务时延阈值之前或未超过低优先级业务时 延阈值之前进行提交，比如只要数据单元存入接收端重传緩存中，则即刻提交， 等等。为了描述方便，在本发明实施例中将均以在大于等于高优先级业务时延 阈值时提交新的需要提交的数据单元，在大于等于低优先级业务时延罔值时提 交新的需要提交的未修正的数据单元。关于这一点在后续的实施例将会进行详 细描述， 在此不再资述。
需说明的是，本发明实施例所提供的 "对接收端重传缓存中的数据单元的 处理"的方案也可以作为一个独立的方案， 即数据单元在放进接收端缓存单元 中之前也可以继续沿用现有技术的方案。只是在数据单元放入接收端重传緩存 中后， 通过对时延状态的监控为接收端重传緩存中的数据单元标识上附加标 识， 然后将数据单元提交到上层， 即从重传层提交到 TPS-TC层， 以便上层根 据附加标识对所述数据单元进行处理，其中， 附加标识指示上层接收到数据单 元后的处理方式， 具体实施可参见本实施例中的有关描述， 在此不再赘述。
由上可知，本实施例的接收端在接收发送端发送的数据单元后，若确定数 据单元包括表示不需要重传的标识，则不需要判断该数据单元是否正确或者是 否需要重传等等， 而是直接将该数据单元存入接收端重传緩存中， 这样， 可以 减少接收端重传申请数量以及减少该类数据单元的时延，进一步的，接收端还 可以通过对时延状态的监控为接收端重传缓存中的数据单元标识上附加标识， 以便指示上层在接收到数据单元后对不同优先等级的数据作出保留或丢弃的 处理， 从而配合发送端完成可以区分业务类型的数据传送过程， 例如， 对于对 时延较为敏感但对误码率没有要求的业务可以采用较低的 ΙΝΡί呆护等级， 在超 过一定的时延后不进行重传，对于时延不敏感但误码率要求较低的业务可以采 用较高的同 ΙΝΡ保护等级， 需要进行重传， 实现了可以满足不同业务的不同时 延需求和不同 ΙΝΡ保护等级需求的目的， 提高用户的综合业务的 QoE。 实施例三、
4艮据实施例一和实施例二所描述的方法，本实施例将举例作进一步详细说 明。
首先，根据业务对时延和误码率的不同要求，可以将不同的业务划分为主 要的两类， 第一类是误码率要求不高、 时延要求低的业务， 即对 INP保护等级 需求较低， 但对时延比较敏感的业务， 比如网络电话（VoIP, Voice over IP ) 等， 可以将第一类业务的优先级等级设置为高优先级； 第二类是低误码率， 时 延和抖动要求不高的业务， 即对 INP保护等级需求较高， 但对时延不敏感的业 务， 比如视频业务等， 可以将第二类业务的优先级等级设置为低优先级。 参见 图 3 , 传送的过程可以如下：
(一）发送端
参见图 4, 在 TPS-TC层之上（即 TPS-TC层的上层）， 业务区分模块将不同 优先级的业务分别存入低优先级业务緩存和高优先级业务緩存中，然后通过不 同的业务接口输入到 TPS-TC层， 由 TPS-TC层数据处理模块将业务数据封装成 数据单元， 并标识上 SID后经重传层的发送端发送给重传层的接收端， 同时为 了使得在接收端未正确接收到数据单元时， 可以对这些数据单元进行重发，还 需要将这些数据单元存入发送端重传緩存中，在该传送过程中，接收端可以返 回表示接收数据单元成功或失败的响应消息给发送端，如果发送端接收到表示 接收数据单元成功的响应消息，则可以将保存在发送端重传緩存中相应的数据 单元删除，如果发送端接收到表示接收数据单元失败的响应消息， 则从发送端 缓存中提取相应的数据单元进行重传。需说明的是，其中，重传层包括 PMS-TC 层， 另外， 各层在进行数据或信息传送时， 接收者还可以根据具体的接收情况 或处理情况返回反馈消息给发送者。
在该传送过程中，重传层的发送端的时延监控模块会通过监控发送端重传 缓存中空间的存储状态来监控数据在传输过程中的时延，例如，确定发送端重 传緩存中保存的数据量是否大于预置的阈值，若是， 则表示时延大于预置的阈 值， 若否， 则表示时延不大于预置的阔值； 当时延小于等于预置的阈值时， 数 据按照正常的流程进行传送（参见前面的描述）， 当时延大于预置的阔值时， 重传层的数据处理模块发送数据堵塞指示给 TPS-TC层的堵塞控制模块， 堵塞 控制模块接收到该数据堵塞指示后 , 向上层的低优先级数据接口发送阻塞信 息， 比如向图 4中的 r层的低优先级 r接口发送阻塞信息， 即暂时停止接收低优 先级数据，以防止发送端重传緩存中出现数据溢出而导致传送的数据出错或丢 失的情况， 从而实现对低优先级数据采用较高 INP保护等级的目的。 但是， 为 了减小高优先级数据的时延，此时并不停止对高优先级数据的接收， 因为高优 先级数据并不需要采用太高的 INP保护等级， 在接收到高优先级数据后， 将高 优先级数据封装成一种特殊的数据单元， 所谓特殊的数据单元，指的是这种数 据单元被标识上表示不需要重传的标识， 而且也不存入接收端重传緩存中， 而 是直接发送给接收端， 接收端接收到后， 也不会对此类数据单元申请重传。 当 然， 由于这种特殊的数据单元所承载的数据都不会进行重传， 所以传送的数据 可能会出现较大的误码率，但从另一个角度来说， 却可以满足较小的时延， 符 合对误码率没什么要求的高优先级数据的低时延需求。
需说明的是， 为了进一步减小时延，在重传层的发送端和接收端并不对业 务进行区分， 所有的业务数据随机存放在数据单元中，也即重传层仍然采用单 延迟通道的方式传送数据，同时所有数据的重传申请和数据发送仍然在重传层 进行而不是在 TPS-TC层之上发起重传， 在传送的过程中， 重传层监控数据在 重传层传输过程的时延变化， 并将该有关时延变化的信息反馈给 TPS-TC层， TPS-TC层依据重传层反馈的该有关时延变化的信息来对不同优先级的业务进 行处理， 重传层向 TPS-TC层反馈的有关时延变化的信息包发送端发送的数据 堵塞指示和接收端数据丢弃标识信息等。
另外， 还需说明的是， 若发送端重传缓存中的空间恢复充裕时， 例如发送 端重传緩存中的数据的时延小于预置的 I ' 值时，或者发送端重传緩存中的数据 的时延等于 0时， 重传层的数据处理模块可以发送解数据堵塞指示给 TPS-TC层 的堵塞控制模块， 堵塞控制模块接收到该解数据堵塞指示后停止发送阻塞信 息。 当然， 也可以在发送阻塞信息时启动定时器， 等待预定的时间过后， 停止 发送阻塞信息， 使得接收低优先级业务的功能恢复正常。
下面将举例进行说明，参见图 5,假设发送端重传緩冲区的指针头为 Buffer Header, 该 Buffer Header指向最新的数据单元， 指针尾为 Buffer Tail, 该 Buffer Tail指向最早的 "未得到确认" 的数据单元， 预置的阈值为 Delay— TH, 那么， 数据在发送端的时延等于指针头减去指针尾再加上特殊数据单元个数 ( Num— special DTU ) , 即 Delay=Buf er Header - Buffer Tail + Num_special DTU。 另外， 数据在发送端的闹值 Delay_TH可以是业务要求的时延减去接收 端的时延。 那么， 如图 6所示， 发送端的数据单元的处理流程可以如下：
A301、 判断数据单元是否是新的数据单元， 若否， 执行步骤 A302, 若是， 则执行步骤 A306;
A302、 判断指针尾 Buffer Tail所指向的数据单元是否正确， 若否， 执行步 骤 A303 , 若是， 则执行步骤 A304;
A303、 判断时延 Delay是否超时， 若否， 则流程结束； 若是， 则执行步骤 A304;
A304、 将指针尾 Buffer Tail和时延 Delay均加上 1后， 执行步骤 A305;
A305、 判断指针头 Buffer Header是否等于指针尾 Buffer Tail, 若否， 则流 程结束； 若是， 则表示发送端緩存中没有数据单元， 空间充裕， 于是将时延 Delay置为 0， 同时将数据堵塞指示的标识（ Datapath_L Block Flag )设为 0， 流 程结束。
需说明的是， 在本发明实施例中， 假设 Datapath_L Block Flag为 0时， 表示 数据堵塞指示无效， 即停止发送阻塞信息， Datapath_L Block Flag为 1时， 表示 数据堵塞指示有效， 即发送阻塞信息。
A306、 判断指针头 Buffer Header与指针尾 Buffer Tail的差是否大于预置的 阈值为 Delay— TH， 若是， 执行步骤 A307; 若否， 执行步骤 A309;
A307、 判断 Datapath_L Block Flag是否设为l , 若是， 执行步驟 A308, 若 否， 则将 Datapath_L Block Flag设为 1后 , 执行步骤 A309；
A308、 将时延 Delay加 1， 并对数据单元标识上 "255" 的 SID, 然后发送 数据单元给接收端， 流程结束。
A309、 判断指针头所指向的数据单元的 SID是否小于 "244" ， 若是， 将 数据单元的 SID加 1后， 执行步棘 A310; 若否， 将数据单元的 SID置为 0后， 执 行步骤 A310;
需说明的是，在本发明实施例中均假设普通的数据单元， 即可以进行重传 的数据单元的 SID为 0 ~ 244。
A310、将数据单元存放入发送端重传緩存中，将指针头 Buffer Header和时 延 Delay均加上 1后， 发送数据单元给接收端， 流程结束。
在该流程中， 一共有 3条路径， 即路径 A、路径 B和路径 C, 参见图 6, 其中， 路径 A为对存入发送端重传緩存中的数据单元进行处理的流程， 包括接收端确 认接收正确、 时延超时和发送解堵塞指示的处理操作； 路径 B为普通的数据单 元（即可以进行重传的数据单元） 的发送流程， 路径 C为特殊的数据单元， 即 包括不需要重传标识的数据单元， 比如 SID为 255的数据单元的发送流程。
(二）接收端
重传层的接收端接收发送端发送的数据单元后，在确定数据单元为特殊数 据单元时， 即确定数据单元包括表示不需要重传的标识时， 不需要判断该数据 单元是否正确或者是否需要重传等等，直接将该数据单元存入接收端重传緩存 中。 而对于普通的数据单元， 则需要判断该数据单元是否正确或者是否需要重 传等来确定是将该数据单元存入接收端重传緩存中还是丢弃， 如图 7所示， 具 体流程可以如下， 需说明的是， 在本来流程中将会涉及到指针头和指针尾， 以 及高优先级数据的时延 Delay_H和低优先级数据的时延 Delay_U描述，关于这 点， 在本实施例后续的描述中将会作详细（可参见图 9 )说明， 为了描述方便， 在此不再赘述。
B30K 从 PMD-TC层接收数据单元， 将高优先级数据的时延 Delay_H和低 优先级数据的时延 Delay_L都加上 1 , 然后执行步骤 B302；
B302、 判断接收到的数据单元的 SID是否大于指针头 Buffer Header所指向 的数据单元的 SID, 若是， 则执行步骤 B303; 若否， 则执行步骤 B304;
B303、 将指针头 Buffer Header加 1后， 将接收到的数据单元存入接收端重 传缓存中， 流程结束。
如果在步骤 B301中， 接收到的数据单元是特殊的数据单元， 例如该数据 单元的 SID为 255， 那么， 在步骤 B302中， 肯定可以得出数据单元的 SID是大于 指针头 Buffer Header所指向的数据单元的 SID的（因为普通的数据单元的 SID最 大为 244 ) , 因此， 只要执行步骤 302就可以同时实现 "确定数据单元是否包括 表示不需要重传的标识" 的操作。 当然， 如果特殊的数据单元是用其他的标识 来表示不需要重传的， 则可以在步骤 B302之前增加一个 "确定数据单元是否 包括表示不需要重传的标识" 的步骤， 如果包括了表示不需要重传的标识， 则 执行步骤 B303; 如果不包括了表示不需要重传的标识， 则执行步骤 B302;
B304、 判断接收到的数据单元的 SID是否为 0， 即是否进入一个新的循环
( SID由 0至 244进行循环 , 即若前一个数据单元的 SID已经达到最大值 244 , 则 下一个新的数据单元的 SID将设为 0 ) ， 若是， 则执行步驟执行步骤 B303; 若 否执行步骤 B305;
B305、 判断接收到的数据单元是否错误， 若是， 则将数据单元丢弃， 若 否， 则执行步骤 B306;
B306、 判断接收到的数据单元的 SID是否小于等于指针尾 Buffer Tail E, 即判断数据单元的是否已经过时， 若是， 将数据单元丢弃， 流程结束； 若否， 则意味着该数据单元为重传的且有效的数据单元，因此替换接收端重传緩存中 相应的数据单元， 即更新接收端重传緩存中相应的数据单元， 流程结束。
在重传层的接收端， 如图 8所示， 重传层的时延监控模块通过对接收端重 传缓存空间占用状态的监控，指示重传层数据处理模块对数据单元标识不同的 附加标识， 然后附加标识信息和数据单元一 送给 TPS-TC层数据处理模块 进行处理， TPS-TC层数据处理模块根据附加标识对数据单元进行处理后， 由 不同的业务接口， 比如图 8中 r接口提交给上层 r层， 由业务区分模块将数据分 类后， 依据优先级标识分别存放在低优先级业务緩存和高优先级业务緩冲中， 以^！送给接口模块。 需说明的是， 其中， 重传层包括 PMS-TC层， 另外， 各 层在进行数据或信息传送时，接收者还可以根据具体的接收情况或处理情况返 回反馈消息给发送者。
需说明的是，在重传层并不识别数据单元中承栽数据的优先级， 而是在重 传层之上结合重传层标识的附加标识信息对不同数据单元类型的数据单元（即 具有不同优先级的业务数据）进行处理。 所以， 重传层不仅仅向 TPS-TC层传 送数据单元， 同时还需要将数据单元的附加标识传送给 TPS-TC层； 假设附加 标识用 Flag表示， 则 Flag可以分为三种， 分别是 Flag_H、 FlagJ^^Flag—C , 然 后 TPS-TC层在接收到数据单元和附加标识后， 依据不同的附加标识对收到的 数据单元做出不同的处理， 例如， 若数据单元的附加标识为 Flag_H, 则保留高 优先级数据， 丢弃低优先级数据； 若数据单元的附加标识为 Flag L, 则保留低 优先级数据， 丢弃高优先级数据； 若数据单元的附加标识为 Flag_C, 则保留全 部数据。 关于附加标识的描述可参见实施例二， 在此不再赘述。
下面将举例作进一步详细说明。
参见图 9, 假设接收端重传緩存分为两部分， 基本緩存区 （Base Buffer ) 和扩展緩存区 （ Extended Buffer ) , 另外， 依据不同优先级业务的时延需求设 置两組时延阔值， 分别是 Delay_TH和 Delay_TL， 其中， Dealy_TH是根据高优 先级数据的时延需求进行设置的， 用于监控基本緩存区的空间占用状态； Delay_TL是根据低优先级数据的时延需求进行设置的，用于监控扩展缓存区的 空间占用状态， 其中， Dealy_TH小于 Delay_TL; 相应地， 该接收端重传緩存 中也存在一个指针头和两个指针尾， 在此假设指针头为 Buffer Header, 基本緩 存区对应的指针尾为 Buffer Tail_B， 扩展緩存区对应的指针尾为 Buffer Tail_E， 在正常的情况下，即在接收端重传缓存中的数据单元在高优先级数据的时延值 内已经被修正的情况下， 两个指针尾 Buffer Tail— B和 Buffer Tail— E应该是重合 的； 当接收端重传緩存中存在高优先级业务时延阈值 Delay_H内未被修正的数 据单元时，该未被修正的数据单元将被存入扩展缓存区，此时两个指针尾 Buffer Tail— B和 Buffer Tail— E不相等； 其中， 指针头指向最新接收到的数据单元， 指 针尾指向最早接收到的数据单元； 那么， 高优先级数据的时延 Delay— H应该等 于指针头 Buffer Header与指针尾 Buffer Tail— B的差， 而低优先级数据的时延 Delay_IjS该等于指针头 Buffer Header与指针尾 Buffer Tail_E的差；接收端将依 据接收端重传緩存的指针头和指针尾和这两个时延阈值的配置对不同的数据 执行不同的操作， 并为数据单元设置不同的附加标志。 如图 10所示， 接收端的 数据单元的处理流程可以如下：
C301、 判断指针尾 Buffer Tail— B和指针尾 Buffer Tail— E是否相等， 若是， 则执行步骤 C302, 若否， 则执行步骤 C306;
需说明的是， 步骤 C301相当于判断接收端重传缓存中是否存在高优先级 业务时延阔值 Delay_H内未被修正的数据单元， 若接收端重传緩存中存在高优 先级业务时延阈值 Delay_H内未被修正的数据单元， 则指针尾 Buffer Tail— B和 指针尾 Buffer丁^1_£不相等， 若接收端重传缓存中不存在高优先级业务时延阈 值 Delay_H内未被修正的数据单元， 则指针尾 Buffer Tail_B和指针尾 Buffer Tail— E不相等；
C302、 判断是否有新数据单元需要提交到上层， 若是， 则执行步骤 C303, 若否， 则流程结束； 具体可以判断高优先级数据的时延 061& ^1是否大于 Dealy_TH, 若否， 则代表没有新数据单元需要提交到上层， 流程结束， 若是， 则代表有新数据单元需要提交到上层， 执行步骤 C303;
C303、 判断该需要提交到上层的新的数据单元是否正确， 若是， 则执行 步骤 C304, 若否， 则执行步骤 C305; 具体可以判断指针尾 Buffer Tail_B所指向 的数据单元是否错误， 若否， 则代表该需要提交到上层的新的数据单元正确， 执行步骤 C304， 若是， 则代表该需要提交到上层的新的数据单元错误， 执行 步骤 C305;
C304、 为该需要提交到上层的新的数据单元标识上 Flag_C, 即为指针尾 Buffer Tail_B所指向的数据单元标识上 Flag_C， 并将该数据单元提交给上层， 即 TPS-TC层， 然后指针尾 Buffer 丁&11_8和 Buffer Tail— E都加 1 , Delay_H和 Delay— L均减去 1， 流程结束；
C305. 为该需要提交到上层的新的数据单元标识上 Flag_H, 即为指针尾
Buffer Tail— B所指向的数据单元标识上 Flag_H， 并将该数据单元提交给上层， 即 TPS-TC层， 然后指针尾 Buffer Tail_B加 1， Delay— H减去 1 , 流程结束；
C306、 判断是否有新数据单元需要提交到上层， 若是， 则一方面执行步 骤 C307, 另一方面执行步骤 C308, 若否， 则执行步骤 C308; 具体可以判断高 优先级数据的时延 1^1 _^是否大于 Dealy_TH, 若是， 则代表有新数据单元需 要提交到上层， 于是一方面执行步骤 C307, 另一方面执行步骤 C308; 若否， 则代表没有新数据单元需要提交到上层， 于是只执行步骤 C308;
需说明的是， 在执行步骤 C307和 C308时， 顺序可以不分先后；
C307、 为该需要提交到上层的新的数据单元标识上 Flag— H， 即为指针尾 Buffer Tail— B所指向的数据单元标识上 Flag_H， 并将该数据单元提交给上层， 即 TPS-TC层， 然后指针尾 Buffer丁 11_8加1， Delay_H减去 1 ; 需说明的是， 步 骤 C307和步骤 C308的执行顺序可以不分先后。
C308、 判断未被修正的数据单元（即存放在扩展緩存区中的数据单元） 是否正确， 若是， 则执行步骤 C310, 若否， 则执行步骤 C309; 具体可以判断 指针尾 Buffer了^1_£所指向的数据单元是否错误， 若是， 则代表未被修正的数 据单元错误， 于是执行步驟 C309, 若否， 则代表未被修正的数据单元正确， 于是执行步骤 C310;
C309、 判断该未被修正的数据单元是否需要被提交到上层， 若是， 则执 行步骤 C310; 若否， 则流程结束； 具体可以判断低优先级数据的时延 Delay_L 是否大于 Dealy_TL, 若是， 则代表该未被修正的数据单元需要被提交到上层， 于是执行步骤 C310; 若否， 则代表该未被修正的数据单元不需要被提交到上 层， 流程可以结束；
C310、 为该未修正的数据单元标识上 Flag_L， 即为指针尾 Buffer Tail— E所 指向的数据单元标识上 Flag_L， 并将该数据单元提交给上层， 即 TPS-TC层， 然后指针尾 Buffer Tail— E加 1， Delay_L减去 1， 流程结束。
此后， TPS-TC层将根据附加标识对该数据单元作出保留或丟弃的处理。 需说明的是， 以上所描述的方案中，有关对接收端重传緩存中的数据单元 的处理的方案也可以作为一个独立的方案， 即只实施步骤 C301至步骤 C309中 所描述的方案也同样可以实施本发明实施例的目的。
由上可知，本发明实施例通过监控数据在传输过程中的时延， 来确定是否 发送用于堵塞上层发送的低优先级数据的阻塞信息，以避免发送端重传缓存中 数据溢出， 从而实现了对低优先级数据的较高 INP保护， 同时， 由于此时只对 低优先级数据进行堵塞， 因此发送端还可以继续接收高优先级数据， 并且在对 高优先级数据进行封装时，对其标识上表示不需要重传的标识，使得接收端在 接收到该高优先级数据时，不需要判断该数据单元是否正确或者是否需要重传 等等， 而是直接将该数据单元存入接收端重传緩存中， 这样， 可以减少接收端 重传申请数量以及减少该类数据单元的时延，从而保证了高优先级数据的低时 延需求。进一步的，接收端还可以通过对时延状态的监控为接收端重传緩存中 的数据单元标识上附加标识，以便指示上层在接收到数据单元后对不同优先等 级的数据作出保留或丢弃的处理，从而配合发送端完成可以区分业务类型的数 据传送过程，例如，对于对时延较为敏感但对误码率没有要求的业务可以采用 较低的 INP保护等级， 在超过一定的时延后不进行重传， 对于时延不敏感但误 码率要求较低的业务可以采用较高的同 INP保护等级， 需要进行重传， 实现了 可以满足不同业务的不同时延需求和不同 INP保护等级需求的目的， 提高用户 的综合业务的 QoE。 实施例四、
为了更好地实施以上方法， 本发明实施例还相应地提供一种发送端 400, 如图 11所示， 该发送端设备 400包括监控单元 401、 阻塞信息发送单元 402、 接 收单元 403、 封装单元 404和发送单元 405; 需说明的是， 为了更好地说明各个 单元之间的关系， 图 11中还给出了上层设备 700;
监控单元 401 , 用于监控数据在传输过程中的时延； 具体可以通过监控发 送端重传緩存中空间的存储状态来监控数据在传输过程中的时延，例如，确定 发送端重传緩存中保存的数据量是否大于预置的阈值，若是， 则表示时延大于 预置的阔值， 若否， 则表示时延不大于预置的阔值；
阻塞信息发送单元 402, 用于当监控单元 401确定时延大于第一时延阈值
(在本发明实施例中， 即指的是预置的时延预置） 时， 发送阻塞信息， 其中， 阻塞信息用于堵塞上层设备 700发送的低优先级数据， 该阻塞信息具体可以为 硬件阻塞信号、 阻塞数据或阻塞标志等； 需说明的是， 其中， 数据的优先级可 以由运营商进行预置， 例如， 如果是对时延比较敏感， 但对误码率没有什么要 求的业务， 比如 VoIP和实时视频通话等， 则可以将其业务数据设置为高优先级 数据； 如果是对时延不敏感， 但需要较低误码率的业务， 比如视频业务等， 则 可以将其业务数据设置为低优先级数据；
接收单元 403， 用于接收上层设备 700发送的高优先级数据；
封装单元 404， 用于将接收单元 403接收到的高优先级数据封装成数据单 元， 并标识上表示不需要重传的标识； 其中， 该表示不需要重传的标识具体可 以为某个特殊的 SID, 比如 255，或者也可以是经发送端与接收端协商而定的其 它 SID， 或者也可以用数据单元中独立的 Flag来标识；
发送单元 405， 用于将封装单元 404封装后的数据单元发送给接收端。 该发送端设备 400还可以包括空数据封装单元；
所述空数据封装单元， 用于将空数据封装成数据单元， 并标识上表示不需 要重传的标识。 需说明的是， 空数据封装单元与封装单元 404可以为同一个实 体。
此时， 发送单元 405, 还用于将空数据封装单元封装后的数据单元发送给 接收端。
以上各个单元的实施具体可参见前面实施例， 在此不再赘述。 传输过程中的时延， 来确定是否让阻塞信息发送单元 402发送用于堵塞低优先 级数据的阻塞信息给上层设备 700， 以避免发送端设备 400重传緩存中数据溢 出， 从而实现了对低优先级数据的较高 INP保护， 同时， 由于此时只对低优先 级数据进行堵塞，因此发送端设备 400的接收单元 403还可以继续接收高优先级 数据， 并且在封装单元 404对高优先级数据进行封装时， 对其标识上表示不需 要重传的标识，使得接收端在接收到该高优先级数据时不会对其申请重传，从 而保证了高优先级数据的低时延需求，也就是说，采用本发明实施例可以满足 不同业务的不同时延需求和不同 INP保护等级需求， 提高了用户的综合业务的 QoE。 例如， 对于对时延较为敏感但对误码率没有要求的业务可以采用较低的 INP保护等级， 在超过某个时延阈值时不再进行重传， 对于时延不敏感但误码 率要求较低的业务可以采用较高的同 INP保护等级， 需要进行重传。
实施例五、
相应地， 本发明实施例还提供一种接收端设备， 如图 12所示， 该接收端设 备包括接收单元 501、 标识识别单元 502和存储单元 503;
接收单元 501， 用于接收发送端发送的数据单元；
标识识别单元 502,用于确定接收单元 501接收到的数据单元是否包括表示 不需要重传的标识；
存储单元 503，用于当标识识别单元 502确定所述数据单元包括表示不需要 重传的标识时， 将该数据单元存入接收端重传緩存中。 其中， 该表示不需要重 传的标识具体可以为某个特殊的 SID，比如 255，或者也可以是经发送端与接收 端协商而定的其它 SID， 或者也可以用数据单元中独立的附加标识来标识； 如图 12所示， 还可以包括新旧判断羊元 504、正确性判断单元 505、丢弃单 元 506和超时判断单元 507;
新旧判断单元 504，用于当标识识别单元 502确定该数据单元不包括表示不 需要重传的标识时， 判断该数据单元是否新的数据单元； 即判断该数据单元是 新的数据单元还是重传的数据单元，比如可以根据数据单元的 SID来进行判断； 所述存储单元 503，用于当新旧判断单元 504判断数据单元为新的数据单元 时， 将该数据单元存入接收端重传缓存中， 或者当超时判断单元 507判断所述 数据单元没有超时时， 将所述数据单元存入接收端重传缓存中； 正确性判断单元 505 ,用于当新旧判断单元 504判断数据单元不是新的数据 单元时， 判断所述数据单元是否错误；
丢弃单元 506， 用于当正确性判断单元 505判断所述数据单元有错误时，丢 弃所述数据单元， 或者当超时判断单元 507判断所述数据单元超时时， 丢弃所 述数据单元；
超时判断单元 507，用于当所述正确性判断单元 505判断所述数据单元没有 错误时， 判断所述数据单元是否超时。
该接收端设备还可以包括附加标识单元和提交单元；
附加标识单元 ,用于通过对时延状态的监控为接收端重传緩存中的数据单 元标识上附加标识， 所述附加标识指示上层接收到数据单元后的处理方式； 例 如：
可以判断接收端重传緩存中是否存在高优先级业务时延阈值内未被修正 的数据单元；
若不存在， 则在确定有新数据单元需要提交到上层， 且确定该数据单元正 确时， 为该数据单元标识上表示正常的附加标识， 比如 Flag_C; 在确定有新数 据单元需要提交到上层，且确定该数据单元错误时， 为该数据单元标识上表示 保留高优先级业务数据而丢弃低优先级业务数据的附加标识， 比如 Flag— H; 若存在， 则一方面在确定有新数据单元需要提交到上层时， 为此数据单元 标识上表示保留高优先级业务数据而丢弃低优先级业务数据的附加标识，比如 Flag_H, 另一方面对高优先级阈值内未被修正的数据单元进行判断，在确定高 优先级业务时延阁值内未被修正的数据单元需要提交时，为该数据单元标识上 表示保留低优先级业务数据而丟弃高优先级业务数据的附加标识， 比如 Flag_L0
具体可参见前面实施例， 在此不再赘述；
提交单元，用于将附加标识单元标识后的数据单元提交到上层， 以便上层 根据附加标识对所述数据单元进行处理。例如， 当緩存中的数据单元被标识上 表示正常的附加标识时， 将数据单元从接收端重传緩存中移出并提交到上层； 当缓存中的数据单元被标识上表示保留高优先级业务数据而丢弃低优先级业 务数据的附加标识时， 复制数据单元并提交到上层； 即此时数据单元仍然会被 缓存在重传緩存中 （即不从接收端重传缓存中移出）， 这些数据单元就是高优 先级业务时延阔值内未被修正的数据单元，这些数据单元的时^ ^超出低优先 级业务时延阈值前仍可以被重传的正确数据单元修正；当缓存中的数据单元被 标识上表示保留低优先级业务数据而丢弃高优先级业务数据的附加标识，将数 据单元从接收端重传緩存中移出并提交到上层。
上层在接收到提交的数据单元后 ,如果数据单元的附加标识为正常的附加 标识， 比如 Flag_C，则保留全部数据， 即高优先级数据和低优先级数据； 否则， 按照附加标识上的指示进行处理，只保留高优先级数据和低优先级数据中的一 种， 比如， 如果是 Flag_L， 则只保留低优先级数据， 而丢弃高优先级数据， 如 果是 Flag— H, 则只保留高优先级数据， 而丢弃低优先级数据。
需说明的是，本发明实施例还提供另一种接收端设备， 包括附加标识单元 和提交单元；
附加标识单元，用于通过对时延状态的监控为接收端重传緩存中的数据单 元标识上附加标识， 所述附加标识指示上层接收到数据单元后的处理方式； 提交单元，用于将附加标识单元标识后的数据单元提交到上层， 以便上层 根据附加标识对所述数据单元进行处理。
也就是说，可以只对现有技术中的接收端设备作改进， 而仍沿用现有的发 送端设备。
以上各个单元的实施具体可参见前面实施例， 在此不再赘述。
由上可知， 本实施例的接收端设备的接收单元 501在接收发送端设备发送 的数据单元后，若标识识别单元 502确定数据单元包括表示不需要重传的标识， 则不需要判断该数据单元是否正确或者是否需要重传等等， 而是由存储单元 503直接将该数据单元存入接收端重传緩存中， 这样， 可以减少接收端设备重 传申请数量以及减少该类数据单元的时延， 进一步的，接收端设备的附加标识 单元还可以通过对时延状态的监控为接收端重传緩存中的数据单元标识上附 加标识，以便指示上层在接收到数据单元后对不同优先等级的数据作出保留或 丢弃的处理，从而配合发送端设备完成可以区分业务类型的数据传送过程， 例 如， 对于对时延较为敏感但对误码率没有要求的业务可以采用较低的 I P保护 等级，在超过一定的时延后不进行重传，对于时延不敏感但误码率要求较低的 业务可以采用较高的同 INP保护等级， 需要进行重传， 实现了可以满足不同业 务的不同时延需求和不同 INP保护等级需求的目的， 提高用户的综合业务的 QoE„ 实施例六、
相应地， 本发明实施例还提供一种通信系统， 如图 13所示， 该通信系统包 括本发明实施例提供的任一种发送端端设备 601和本发明实施例提供的任一种 接收端设备 602;
发送端端设备 601 , 用于监控数据在传输过程中的时延， 若时延大于第一 时延阈值（在本发明实施例中， 即指的是预置的时延预置）， 则发送用于堵塞 上层发送的低优先级数据的阻塞信息，接收上层发送的高优先级数据，将该高 优先级数据封装成数据单元， 并标识上表示不需要重传的标识，将数据单元发 送给接收端设备 602; 其中， 该阻塞信息具体可以为硬件阻塞信号、 阻塞数据 或阻塞标志等；
接收端设备 602,用于接收发送端设备 601发送的数据单元， 确定该数据单 元包括表示不需要重传的标识时， 将该数据单元存入接收端重传緩存中。
其中， 所述接收端设备 602, 还用于通过对时延状态的监控为接收端重传 緩存中的数据单元标识上附加标识，所述附加标识指示上层接收到数据单元后 的处理方式，将数据单元提交到上层， 以便上层根据附加标识对所述数据单元 进行处理。 具体可参见前面实施例， 在此不再赘述。
其中， 发送端端设备 601可以包括监控单元 401、 阻塞信息发送单元 402、 接收单元 403、封装单元 404和发送单元 405，发送端端设备 601还可以包括空数 据封装单元；
接收端设备 602可以包括接收单元 501、 标识识别单元 502和存储单元 503 , 该接收端设备 602还可以包括新旧判断单元 504、 正确性判断单元 505、 丢弃单 元 506和超时判断单元 507; 进一步的， 该接收端设备 602还可以包括附加标识 单元和提交单元。
以上各个单元的实施具体可参见前面实施例， 在此不再赘述。
综上， 由上可知， 本发明实施例的发送端设备 601可以通过监控数据在传 输过程中的时延，来确定是否发送用于堵塞上层发送的低优先级数据的阻塞信 息 ,以避免发送端重传緩存中数据溢出 ,从而实现了对低优先级数据的较高 INP 保护， 同时， 由于此时只对低优先级数据进行堵塞， 因此发送端设备 601还可 以继续接收高优先级数据， 并且在对高优先级数据进行封装时，对其标识上表 示不需要重传的标识， 使得接收端设备 602在接收到该高优先级数据时， 不需 要判断该数据单元是否正确或者是否需要重传等等，而是直接将该数据单元存 入接收端重传緩存中， 这样，可以减少接收端重传申请数量以及减少该类数据 单元的时延， 从而保证了高优先级数据的低时延需求。 进一步的， 接收端设备 602还可以通过对时延状态的监控为接收端重传緩存中的数据单元标识上附加 标识，以便指示上层在接收到数据单元后对不同优先等级的数据作出保留或丢 弃的处理， 从而配合发送端设备 601完成可以区分业务类型的数据传送过程， 例如， 对于对时延较为敏感但对误码率没有要求的业务可以采用较低的 INP保 护等级，在超过一定的时延后不进行重传，对于时延不敏感但误码率要求较低 的业务可以采用较高的同 INP保护等级， 需要进行重传， 实现了可以满足不同 业务的不同时延需求和不同 INP保护等级需求的目的， 提高用户的综合业务的 QoE. 本领域普通技术人员可以理解上述实施例的各种方法中的全部或部分步 骤是可以通过程序来指令相关的硬件来完成，该程序可以存储于一计算机可读 存储介质中， 存储介质可以包括： 只读存储器（ROM, Read Only Memory )、 随才; ¾·取记忆体 ( RAM, Random Access Memory ) , 磁盘或光盘等。
以上对本发明实施例所提供的一种数据传送方法、装置和通信系统进行了 详细介绍，本文中应用了具体个例对本发明的原理及实施方式进行了阐述， 以 上实施例的说明只是用于帮助理解本发明的方法及其核心思想； 同时，对于本 领域的一般技术人员，依据本发明的思想，在具体实施方式及应用范围上均会 有改变之处， 综上所述， 本说明书内容不应理解为对本发明的限制。

Claims

权 利 要 求
1、 一种数据传送方法， 其特征在于， 包括：
监控数据在传输过程中的时延；
若时延大于第一时延阈值， 则发送阻塞信息， 所述阻塞信息用于堵塞上层 发送的低优先级数据；
接收上层发送的高优先级数据；
将所述高优先级数据封装成数据单元， 并标识上表示不需要重传的标识； 将数据单元发送给接收端。
2、 根据权利要求 1所述的方法， 其特征在于，
所述监控数据在传输过程中的时延包括：确定发送端重传緩存中保存的数 据量是否大于预置的阈值； 若是， 则表示时延大于预置的阈值； 若否， 则表示 时延不大于预置的阈值；
所述标识上表示不需要重传的标识包括：标识上表示不需要重传的业务序 列号； 或者， 标识上表示不需要重传的附加标识。
3、 根据权利要求 1或 2所述的方法， 其特征在于， 所述发送阻塞信息后还 包括：
将空数据封装成数据单元， 并标识上表示不需要重传的标识。
4、 一种数据传送方法， 其特征在于， 包括：
接收发送端发送的数据单元；
确定所述数据单元包括表示不需要重传的标识时，将所述数据单元存入接 收端重传緩存中；
确定所述数据单元不包括表示不需要重传的标识时，判断所述数据单元是 否新的数据单元；
若是， 将所述数据单元存入接收端重传緩存中；
若否， 判断所述数据单元是否错误， 若有错误， 丢弃所述数据单元， 若没 有错误， 进一步判断所述数据单元是否超时， 若超时， 丢弃所述数据单元， 若 没有超时， 将所述数据单元存入接收端重传緩存中。
5、 根据权利要求 4所述的方法， 其特征在于， 还包括：
通过对时延状态的监控为接收端重传缓存中的数据单元标识上附加标识， 所述附加标识指示上层接收到数据单元后的处理方式； 将数据单元提交到上层， 以便上层根据附加标识对所述数据单元进行处 理。
6、根据权利要求 5所述的方法， 其特征在于， 所述通过对时延状态的监控 为接收端重传緩存中的数据单元标识上附加标识包括：
判断接收端緩存中是否存在高优先级业务时延阈值内未被修正的数据单 元；
若不存在， 则在确定有新数据单元需要提交到上层， 且确定该数据单元正 确时， 为该数据单元标识上表示正常的附加标识；在确定有新数据单元需要提 交到上层，且确定该数据单元错误时， 为该数据单元标识上表示保留高优先级 业务数据而丢弃低优先级业务数据的附加标识；
若存在， 则一方面在确定有新数据单元需要提交到上层时， 为此数据单元 标识上表示保留高优先级业务数据而丢弃低优先级业务数据的附加标识，另一 方面对高优先级阈值内未被修正的数据单元进行判断，在确定高优先级业务时 延阈值内未被修正的数据单元需要提交时，为该数据单元标识上表示保留低优 先級业务数据而丢弃高优先级业务数据的附加标识。
7、根据权利要求 6所述的方法， 其特征在于， 所述将数据单元提交到上层 包括：
当緩存中的数据单元被标识上表示正常的附加标识时，将数据单元从接收 端重传緩存中移出并提交到上层；
当緩存中的数据单元被标识上表示保留高优先级业务数据而丢弃低优先 级业务数据的附加标识时， 复制数据单元并提交到上层；
当緩存中的数据单元被标识上表示保留低优先级业务数据而丢弃高优先 级业务数据的附加标识， 将数据单元从接收端重传緩存中移出并提交到上层。
8、 一种数据传送方法， 其特征在于， 包括：
通过对时延状态的监控为接收端重传緩存中的数据单元标识上附加标识， 所述附加标识指示上层接收到数据单元后的处理方式；
将数据单元提交到上层， 以便上层根据附加标识对所述数据单元进行处 理。
9、根据权利要求 8所述的方法， 其特征在于， 所述通过对时延状态的监控 为接收端重传緩存中的数据单元标识上附加标识包括： 判断接收端緩存中是否存在高优先级业务时延阂值内未被修正的数据单 元；
若不存在， 则在确定有新数据单元需要提交到上层， 且确定该数据单元正 确时， 为该数据单元标识上表示正常的附加标识；在确定有新数据单元需要提 交到上层，且确定该数据单元错误时， 为该数据单元标识上表示保留高优先级 业务数据而丢弃低优先级业务数据的附加标识；
若存在， 则一方面在确定有新数据单元需要提交到上层时， 为此数据单元 标识上表示保留高优先级业务数据而丢弃低优先级业务数据的附加标识，另一 方面对高优先级阈值内未被修正的数据单元进行判断，在确定高优先级业务时 延阈值内未被修正的数据单元需要提交时，为该数据单元标识上表示保留低优 先级业务数据而丢弃高优先级业务数据的附加标识。
10、根据权利要求 8或 9所述的方法， 其特征在于， 所述将数据单元提交到 上层包括：
当緩存中的数据单元被标识上表示正常的附加标识时，将数据单元从接收 端重传緩存中移出并提交到上层；
当緩存中的数据单元被标识上表示保留高优先级业务数据而丢弃低优先 级业务数据的附加标识时， 复制数据单元并提交到上层；
当緩存中的数据单元被标识上表示保留低优先级业务数据而丢弃高优先 级业务数据的附加标识， 将数据单元从接收端重传緩存中移出并提交到上层。
11、 一种发送端设备， 其特征在于， 包括：
监控单元， 用于监控数据在传输过程中的时延；
阻塞信息发送单元， 用于当监控单元确定时延大于第一时延阔值时，发送 阻塞信息， 所述阻塞信息用于堵塞上层发送的低优先级数据；
接收单元， 用于接收上层发送的业务数据；
封装单元，用于将所述接收单元接收到的数据封装成数据单元， 并标识上 表示不需要重传的标识；
发送单元， 用于将封装单元封装后的数据单元发送给接收端。
12、 根据权利要求 11所述的发送端设备， 其特征在于， 还包括： 空数据封装单元， 用于将空数据封装成数据单元， 并标识上表示不需要重 传的标识； 所迷发送单元， 还用于将空数据封装单元封装后的数据单元发送给接收 端。
13、 一种接收端设备， 其特征在于， 包括：
接收单元， 用于接收发送端发送的数据单元；
标识识别单元，用于确定所述接收单元接收到的数据单元是否包括表示不 需要重传的标识； 需要重传的标识时， 判断所述数据单元是否新的数据单元；
存储单元，用于当所述标识识別单元确定所述数据单元包括表示不需要重 传的标识时，或者当所述新旧判断单元判断数据单元为新的数据单元时，将所 述数据单元存入接收端重传緩存中；
正确性判断单元，用于当所述新旧判断单元判断数据单元不是新的数据单 元时， 判断所述数据单元是否错误；
超时判断单元， 用于当所述正确性判断单元判断所述数据单元没有错误 时， 判断所述数据单元是否超时；
丢弃单元，用于当所述正确性判断单元判断所述数据单元有错误时，丢弃 所述数据单元，或者当所述超时判断单元判断所述数据单元超时时，丢弃所述 数据单元。
14、根据权利要求 13所述的接收端设备， 其特征在于， 还包括附加标识单 元和提交单元：
附加标识单元，用于通过对时延状态的监控为接收端重传緩存中的数据单 元标识上附加标识， 所述附加标识指示上层接收到数据单元后的处理方式； 提交单元，用于将附加标识单元标识后的数据单元提交到上层， 以便上层 根据附加标识对所述数据单元进行处理。
15、 一种接收端设备， 其特征在于， 包括：
附加标识单元，用于通过对时延状态的监控为接收端重传緩存中的数据单 元标识上附加标识， 所述附加标识指示上层接收到数据单元后的处理方式； 提交单元，用于将附加标识单元标识后的数据单元提交到上层， 以便上层 根据附加标识对所述数据单元进行处理。
16、 一种通信系统， 其特征在于， 包括： 发送端端设备， 用于监控数据在传输过程中的时延， 若时延大于第一时延 阈值， 则发送用于堵塞上层发送的低优先级数据的阻塞信息，接收上层发送的 高优先级数据，将所迷高优先级数据封装成数据单元， 并标识上表示不需要重 传的标识， 将数据单元发送给接收端设备；
接收端设备， 用于接收发送端设备发送的数据单元， 确定所述数据单元包 括表示不需要重传的标识时， 将所述数据单元存入接收端重传缓存中。
17、 根据权利要求 16所述的通信系统， 其特征在于， 包括：
所述接收端设备，还用于通过对时延状态的监控为接收端重传緩存中的数 据单元标识上附加标识， 所述附加标识指示上层接收到数据单元后的处理方 式，将数据单元提交到上层，以便上层根据附加标识对所述数据单元进行处理。
PCT/CN2010/073066 2009-05-22 2010-05-21 一种数据传送方法、装置和通信系统 WO2010133184A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP10777387.1A EP2429143B1 (en) 2009-05-22 2010-05-21 Method, device and communication system for transmitting data
US13/302,855 US8526513B2 (en) 2009-05-22 2011-11-22 Method and apparatus for transmitting data, and communication system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200910202946.5 2009-05-22
CN200910202946.5A CN101895403B (zh) 2009-05-22 2009-05-22 一种数据传送方法、装置和通信系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US13/302,855 Continuation US8526513B2 (en) 2009-05-22 2011-11-22 Method and apparatus for transmitting data, and communication system

Publications (1)

Publication Number Publication Date
WO2010133184A1 true WO2010133184A1 (zh) 2010-11-25

Family

ID=43104482

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2010/073066 WO2010133184A1 (zh) 2009-05-22 2010-05-21 一种数据传送方法、装置和通信系统

Country Status (4)

Country Link
US (1) US8526513B2 (zh)
EP (1) EP2429143B1 (zh)
CN (1) CN101895403B (zh)
WO (1) WO2010133184A1 (zh)

Families Citing this family (37)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9049233B2 (en) 2012-10-05 2015-06-02 Cisco Technology, Inc. MPLS segment-routing
US10411997B1 (en) 2012-12-27 2019-09-10 Sitting Man, Llc Routing methods, systems, and computer program products for using a region scoped node identifier
US10404583B1 (en) 2012-12-27 2019-09-03 Sitting Man, Llc Routing methods, systems, and computer program products using multiple outside-scope identifiers
US10587505B1 (en) 2012-12-27 2020-03-10 Sitting Man, Llc Routing methods, systems, and computer program products
US10419335B1 (en) 2012-12-27 2019-09-17 Sitting Man, Llc Region scope-specific outside-scope indentifier-equipped routing methods, systems, and computer program products
US10374938B1 (en) 2012-12-27 2019-08-06 Sitting Man, Llc Routing methods, systems, and computer program products
US10447575B1 (en) 2012-12-27 2019-10-15 Sitting Man, Llc Routing methods, systems, and computer program products
US10411998B1 (en) 2012-12-27 2019-09-10 Sitting Man, Llc Node scope-specific outside-scope identifier-equipped routing methods, systems, and computer program products
US10419334B1 (en) 2012-12-27 2019-09-17 Sitting Man, Llc Internet protocol routing methods, systems, and computer program products
US10212076B1 (en) 2012-12-27 2019-02-19 Sitting Man, Llc Routing methods, systems, and computer program products for mapping a node-scope specific identifier
US10904144B2 (en) 2012-12-27 2021-01-26 Sitting Man, Llc Methods, systems, and computer program products for associating a name with a network path
US10397101B1 (en) 2012-12-27 2019-08-27 Sitting Man, Llc Routing methods, systems, and computer program products for mapping identifiers
US10476787B1 (en) 2012-12-27 2019-11-12 Sitting Man, Llc Routing methods, systems, and computer program products
US10404582B1 (en) 2012-12-27 2019-09-03 Sitting Man, Llc Routing methods, systems, and computer program products using an outside-scope indentifier
US10397100B1 (en) 2012-12-27 2019-08-27 Sitting Man, Llc Routing methods, systems, and computer program products using a region scoped outside-scope identifier
US9537718B2 (en) 2013-03-15 2017-01-03 Cisco Technology, Inc. Segment routing over label distribution protocol
WO2015111588A1 (ja) * 2014-01-22 2015-07-30 株式会社リコー データ伝送システム、端末装置、プログラムおよびデータ伝送方法
US9762488B2 (en) 2014-03-06 2017-09-12 Cisco Technology, Inc. Segment routing extension headers
US9807001B2 (en) 2014-07-17 2017-10-31 Cisco Technology, Inc. Segment routing using a remote forwarding adjacency identifier
US20160119165A1 (en) * 2014-10-27 2016-04-28 Netsnapper Technologies Sarl Methods and systems to manage network connections
CN104378308A (zh) * 2014-11-19 2015-02-25 盛科网络（苏州）有限公司 报文发送速率检测方法及装置
US10341221B2 (en) 2015-02-26 2019-07-02 Cisco Technology, Inc. Traffic engineering for bit indexed explicit replication
CN106470500B (zh) * 2015-08-18 2019-08-27 富士通株式会社 数据传输方法、装置和节点
US10263881B2 (en) * 2016-05-26 2019-04-16 Cisco Technology, Inc. Enforcing strict shortest path forwarding using strict segment identifiers
US11032197B2 (en) 2016-09-15 2021-06-08 Cisco Technology, Inc. Reroute detection in segment routing data plane
CN106874223B (zh) * 2017-01-24 2021-04-20 合肥兆芯电子有限公司 数据传输方法、存储器存储装置及存储器控制电路单元
CN107197392B (zh) * 2017-05-24 2019-05-28 中广热点云科技有限公司 在弹幕视频流传输过程中的丢包方法及丢包装置
CN109218352B (zh) * 2017-06-30 2020-08-14 华为技术有限公司 一种区块链网络中交易信息的共识确认方法及装置
CN108111436B (zh) * 2017-11-30 2023-04-18 浙江宇视科技有限公司 一种网络设备缓存调度方法及系统
CN109991967A (zh) * 2017-12-29 2019-07-09 深圳市优必选科技有限公司 一种机器人运动的控制方法、系统及终端设备
CN111124794B (zh) * 2018-11-01 2023-07-07 百度在线网络技术（北京）有限公司 数据处理系统的监测方法、装置以及计算机设备
US11140074B2 (en) 2019-09-24 2021-10-05 Cisco Technology, Inc. Communicating packets across multi-domain networks using compact forwarding instructions
CN111277319B (zh) * 2020-01-20 2022-08-16 中国电子科技集团公司电子科学研究院 星地间数据传输方法及装置
CN111654523A (zh) * 2020-04-28 2020-09-11 珠海格力电器股份有限公司 一种数据处理方法、装置、存储介质及服务器
CN112333250B (zh) * 2020-10-26 2022-03-01 天津市城市规划设计研究总院有限公司 智能楼宇中物联网数据包的应答方法和系统
CN112422253B (zh) * 2020-10-27 2022-01-28 北京邮电大学 实时同频同时全双工的可靠传输方法及装置
CN116150221B (zh) * 2022-10-09 2023-07-14 浙江博观瑞思科技有限公司 服务于企业电商运营管理的信息交互方法及系统

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1352862A (zh) * 1999-01-14 2002-06-05 艾利森电话股份有限公司 用于网络业务中各种类型语音的优先级传输
US20070033496A1 (en) * 2005-07-14 2007-02-08 Hitachi, Ltd. System and method for adjusting BER/PER to increase network stream-based transmission rates
CN101155014A (zh) * 2006-09-28 2008-04-02 华为技术有限公司 一种数据混合自动请求重传方法及装置
CN101321046A (zh) * 2006-09-13 2008-12-10 美国博通公司 xDSL系统内传送数据的方法、装置和系统

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6856628B1 (en) * 2000-10-26 2005-02-15 Motorola, Inc. Method and apparatus for tunneling packets in a packet data system
US7120113B1 (en) * 2001-07-16 2006-10-10 Juniper Networks, Inc. Systems and methods for limiting low priority traffic from blocking high priority traffic
CN1297097C (zh) 2003-04-09 2007-01-24 华为技术有限公司 提高网络拥塞时数据传输性能的方法
EP1507352B1 (en) * 2003-08-14 2007-01-31 Matsushita Electric Industrial Co., Ltd. Time monitoring of packet retransmissions during soft handover
TWI296083B (en) * 2003-09-29 2008-04-21 Sharp Kk Communication controller, host-side controller, communication system, usb system, communication equipment, communication method, packet-based communication method, packet-based communication program, and storage medium
US8381055B2 (en) * 2006-09-13 2013-02-19 Broadcom Corporation System for communicating data in xDSL using data retransmission
JP5346956B2 (ja) * 2008-01-03 2013-11-20 イカノス テクノロジー エルティーディー 汎用認識インパルスノイズ保護

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1352862A (zh) * 1999-01-14 2002-06-05 艾利森电话股份有限公司 用于网络业务中各种类型语音的优先级传输
US20070033496A1 (en) * 2005-07-14 2007-02-08 Hitachi, Ltd. System and method for adjusting BER/PER to increase network stream-based transmission rates
CN101321046A (zh) * 2006-09-13 2008-12-10 美国博通公司 xDSL系统内传送数据的方法、装置和系统
CN101155014A (zh) * 2006-09-28 2008-04-02 华为技术有限公司 一种数据混合自动请求重传方法及装置

Non-Patent Citations (1)

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

Also Published As

Publication number Publication date
US8526513B2 (en) 2013-09-03
EP2429143B1 (en) 2015-11-04
CN101895403A (zh) 2010-11-24
EP2429143A4 (en) 2012-07-25
EP2429143A1 (en) 2012-03-14
CN101895403B (zh) 2013-08-28
US20120063526A1 (en) 2012-03-15

Similar Documents

Publication Publication Date Title
WO2010133184A1 (zh) 一种数据传送方法、装置和通信系统
EP1543644B1 (en) Method and devices for error tolerant data transmission, wherein retransmission of erroneous data is performed up to the point where the remaining number of errors is acceptable
US7746786B2 (en) Retransmission control method and device
US8402343B2 (en) Reliable packet cut-through
US8134993B2 (en) Method and apparatus for polling transmission status in a wireless communication system
JP3634800B2 (ja) パリティチェック結合を用いたハイブリッド自動再送要求を実施するシステム及び方法
RU2469482C2 (ru) Способ и система для передачи данных в сети передачи данных
US20090319850A1 (en) Local drop control for a transmit buffer in a repeat transmission protocol device
EP1876747A1 (en) Method and apparatus for handling transmission errors in a wireless communications system
RU2456751C2 (ru) Способ повторной передачи данных и устройство беспроводной связи
US8553721B2 (en) Channel bonding and packet fragment retransmission method and apparatus
JP2002158712A (ja) パケット・データ・システムでパケットをトンネルする方法と装置
US8381057B2 (en) Seamless change of retransmission and rescheduling queues in a communication system
WO2012083624A1 (zh) 一种半静态调度业务资源释放方法及系统
WO2013107408A1 (zh) 数据传输的方法及装置
JP2007028623A (ja) ネットワークストリームベースの伝送速度を加速するためにｂｅｒ／ｐｅｒを調整するためのシステムおよび方法
US8989239B2 (en) Systems and methods for retransmission with on-line reconfiguration
KR102255051B1 (ko) 데이터 처리 방법 및 장치
KR20060060488A (ko) 통신 시스템에서 데이터 재전송 장치 및 방법
CN113765626B (zh) 一种移动通信系统的数据传输方法和装置
WO2014117543A1 (zh) 一种基于信道激活检测的传输方法及装置
WO2015032048A1 (zh) 一种移动终端内部通信方法
WO2011015071A1 (zh) 一种无线链路控制层的数据发送方法及系统
WO2010022665A1 (zh) 一种实现物理层重传的方法、装置及系统
JP5003611B2 (ja) 無線通信の再送制御方法及び無線通信装置

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2010777387

Country of ref document: EP