WO2019096145A1 - 连续数据包传输失败的规避方法及装置 - Google Patents

连续数据包传输失败的规避方法及装置 Download PDF

Info

Publication number
WO2019096145A1
WO2019096145A1 PCT/CN2018/115330 CN2018115330W WO2019096145A1 WO 2019096145 A1 WO2019096145 A1 WO 2019096145A1 CN 2018115330 W CN2018115330 W CN 2018115330W WO 2019096145 A1 WO2019096145 A1 WO 2019096145A1
Authority
WO
WIPO (PCT)
Prior art keywords
transmission
entity
layer
data packet
access layer
Prior art date
Application number
PCT/CN2018/115330
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 EP18879757.5A priority Critical patent/EP3697041A4/en
Publication of WO2019096145A1 publication Critical patent/WO2019096145A1/zh
Priority to US16/874,291 priority patent/US11277877B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/20—Arrangements for detecting or preventing errors in the information received using signal quality detector
    • H04L1/203—Details of error rate determination, e.g. BER, FER or WER
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/18—Management of setup rejection or failure
    • 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/0002—Systems modifying transmission characteristics according to link quality, e.g. power backoff by adapting the transmission rate
    • H04L1/0003—Systems modifying transmission characteristics according to link quality, e.g. power backoff by adapting the transmission rate by switching between different modulation schemes
    • 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/0009—Systems modifying transmission characteristics according to link quality, e.g. power backoff by adapting the channel coding
    • 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/1607—Details of the supervisory signal
    • H04L1/1642—Formats specially adapted for sequence numbers
    • 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/1812—Hybrid protocols; Hybrid automatic repeat request [HARQ]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0268—Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/25—Maintenance of established connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/02—Data link layer protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/08—Upper layer protocols
    • 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/1607—Details of the supervisory signal
    • H04L1/1685—Details of the supervisory signal the supervisory signal being transmitted in response to a specific request, e.g. to a polling signal
    • 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/1825—Adaptation of specific ARQ protocol parameters according to transmission conditions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/188—Time-out mechanisms
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L2001/0092—Error control systems characterised by the topology of the transmission link
    • H04L2001/0097—Relays

Definitions

  • the embodiments of the present application relate to the field of communications, and in particular, to a method and apparatus for circumventing a failure of continuous data packet transmission.
  • the motion controller is responsible for controlling a part of the machine that moves or rotates (such as a robotic arm) to perform a certain task, such as delivering a delivery or assembling a part.
  • the communication between the motion controller and the controlled part can be wired or wireless.
  • the advantage of wireless communication is that there is no need to deploy lines between the controller and the controlled unit, which reduces the cost and increases the mobility of the system. Support, the controller can move around at will.
  • some factory buildings need to be customized and reorganized according to the requirements at any time. It is more convenient to reorganize the production line equipped with wireless communication systems.
  • 5G communication systems With the development of 5G communication systems, the communication performance of wireless communication is getting better and better enough to support low latency and high reliability communication requirements in industrial control scenarios. Therefore, 5G communication will be one of the main communication technologies in the future industrial control field.
  • the requirements for communication indicators are high, and the control signaling needs to be transmitted with high reliability in a short time.
  • the controller usually periodically transmits instructions to the controlled unit to indicate how it operates. Since communication is unlikely to achieve 100% reliability, the application layer usually allows an error in one instruction at design time, but Two consecutive instructions are not allowed to have errors. If there are two consecutive control signaling loss or transmission errors, the application layer will disconnect or continue to operate according to the wrong command, which may result in equipment damage or production line shutdown, resulting in huge property or personal safety accidents.
  • the embodiment of the present invention provides a method and a device for circumventing a failure of continuous data packet transmission, which ensures that in the data transmission process, the transmission failure of two consecutive application layer data packets does not occur, and the reliability of data transmission is improved.
  • a method for circumventing a continuous packet transmission failure including:
  • the first entity of the access layer of the transmitting end maintains the transmission status of the previous data packet of the first entity of the access layer; if the transmission status of the previous data packet is a transmission failure, the transmitting end adjusts the transmission of the current data packet. parameter.
  • the first entity of the access layer of the sending end is: a radio link control layer, a service data adaptation protocol layer, a radio resource control layer, a medium access control layer, and a physical layer.
  • the data packet is a service data unit or a protocol data unit.
  • the access layer entity of the sending end maintains a transmission state of a previous data packet of the access layer entity according to at least one of the following information: the first entity of the sending end access layer maintains If the timer expires and the previous data packet has not been successfully transmitted, the transmission status of the previous data packet is considered to be a transmission failure. Otherwise, the previous data packet transmission status is considered as the transmission success; the receiving end access layer first entity sends the transmission to the transmission.
  • the indication information of the end access layer is used to indicate that the previous data packet of the first entity of the access layer of the transmitting end is a transmission success or a transmission failure; the second entity of the access end access layer sends the first entity to the first access layer of the transmitting end.
  • the indication information of the entity is used to indicate that the previous data packet of the first entity of the access layer of the transmitting end is a transmission success or a transmission failure; and the indication information sent by the second entity of the receiving end access layer to the access layer of the transmitting end is used by
  • the first entity or the second entity of the access layer of the transmitting end learns the period of the data packet according to the QoS information, if If no data packet arrives in the previous period, it is determined that the previous data packet transmission fails; the indication information of the non-access stratum or the application layer of the transmitting end to the transmitting end access layer is used to indicate the first entity of the transmitting end access layer.
  • the previous packet is a successful transmission or a transmission failure.
  • the transmission parameter includes at least one of the following: a modulation and coding scheme; a maximum hybrid automatic retransmission HARQ number; a maximum automatic retransmission ARQ times; a transmission resource period; a transmission resource location; a transmission resource size; Type of resource; logical channel priority; radio bearer priority; radio link control transmission mode; number of transmitted carriers; type of radio bearer; function of radio bearer.
  • an embodiment of the present application provides an apparatus for circumventing a continuous packet transmission failure for performing the method of the first aspect.
  • the means for circumventing the failure of a continuous data packet transmission comprises means for performing the method of any of the first aspect or the first aspect.
  • a third aspect is a computer readable storage medium having stored thereon a computer program (instructions) that, when executed on a computer, cause the computer to perform the method of any of the above aspects.
  • the present application provides a chip system including a processor for supporting a device that avoids a failure of continuous data packet transmission to implement the functions involved in the above aspects, for example, generating or processing the above method Data and/or information involved.
  • the chip system further includes a memory for storing program instructions and data necessary to circumvent the failure of the continuous data packet transmission.
  • the chip system can be composed of chips, and can also include chips and other discrete devices.
  • FIG. 1 is a schematic structural diagram of a wireless communication system according to an embodiment of the present application.
  • FIG. 2 is a structural diagram of a terminal device according to an embodiment of the present application.
  • FIG. 3 is a structural diagram of an access network device according to an embodiment of the present application.
  • FIG. 4 is a schematic flowchart of a method for circumventing a failure of continuous data packet transmission according to an embodiment of the present disclosure
  • FIG. 5 is a schematic diagram of data packet transmission according to an embodiment of the present application.
  • FIG. 6 is a schematic flowchart of a method for circumventing a failure of continuous data packet transmission according to an embodiment of the present disclosure
  • FIG. 7 is a schematic flowchart of adjusting an RLC SDU transmission state error based on RLC feedback at a receiving end according to an embodiment of the present disclosure
  • FIG. 8 is a schematic flowchart of adjusting an RLC SDU transmission state error based on feedback of a MAC layer of a receiving end according to an embodiment of the present disclosure
  • FIG. 9 is a schematic flowchart of adjusting a PDCP SDU transmission state error based on feedback of a PDCP layer at a receiving end according to an embodiment of the present disclosure
  • FIG. 10 is a schematic flowchart of another method for circumventing a failure of continuous data packet transmission according to an embodiment of the present disclosure
  • FIG. 11 is a schematic flowchart of another method for circumventing a continuous data packet transmission failure according to an embodiment of the present disclosure
  • FIG. 12 is a schematic flowchart of another method for circumventing a continuous data packet transmission failure according to an embodiment of the present disclosure
  • FIG. 13 is a schematic flowchart of another method for circumventing a continuous data packet transmission failure according to an embodiment of the present disclosure
  • FIG. 14 is a schematic flowchart of another method for circumventing a failure of continuous data packet transmission according to an embodiment of the present disclosure.
  • One in the embodiment of the present application means a single individual, and does not mean that it can only be one individual, and cannot be applied to other individuals.
  • a terminal device in the embodiment of the present application refers to a certain terminal device, and does not mean that it can be applied to only one specific terminal device.
  • system can be used interchangeably with "network”.
  • references to "one embodiment” (or “an implementation") or “an embodiment” (or “an implementation”) in this application are meant to include the particular features, structures, features, etc. described in connection with the embodiments, in at least one embodiment. . Thus, “in one embodiment” or “in an embodiment” or “an”
  • the terms "and/or” and “at least one” in the case of “A and/or B” and “at least one of A and B” in the embodiment of the present application include any one of three schemes, That is, a scheme including A but not including B, a scheme including B not including A, and a scheme including both options A and B.
  • such a phrase includes any of the six schemes, ie, includes A, but does not include the B and C schemes, including B without A and C, including C but not A and B, including A and B but not C, including B and C but not A
  • the scheme includes the schemes of A and C but not B, and the schemes of all three options A, B and C.
  • FIG. 1 shows a schematic diagram of communication between a wireless device and a wireless communication system.
  • the wireless communication system may be a system that applies various radio access technologies (RATs), such as code division multiple access (CDMA), time division multiple access (TDMA), Frequency division multiple access (FDMA), orthogonal frequency-division multiple access (OFDMA), or single carrier frequency division multiple access (SC-FDMA) and other systems .
  • RATs radio access technologies
  • CDMA code division multiple access
  • TDMA time division multiple access
  • FDMA Frequency division multiple access
  • OFDMA orthogonal frequency-division multiple access
  • SC-FDMA single carrier frequency division multiple access
  • the wireless communication system may be a long term evolution (LTE) system, a CDMA system, a wideband code division multiple access (wideband CDMA (WCDMA) system, a global system for mobile communications (GSM) system, a wireless local area network ( Wireless local area network (WLAN) system, New Radio (NR) system, various evolved or fused systems, and systems for future-oriented communication technologies.
  • LTE long term evolution
  • CDMA compact code division multiple access
  • WCDMA wideband CDMA
  • GSM global system for mobile communications
  • WLAN Wireless local area network
  • NR New Radio
  • a wireless communication system can include any number of network devices as well as terminal devices.
  • the wireless communication system may also include one or more core network devices or devices for carrying virtualized network functions, and the like.
  • the access network device 102 can provide services to the wireless device over one or more carriers.
  • the access network device and the terminal device are collectively referred to as a wireless device.
  • the access network device 102 is a device deployed in a wireless access network to provide a wireless communication function for a terminal device.
  • the access network device may include various forms of a macro base station (BS), a micro base station (also referred to as a small station), a relay station, or an access point.
  • BS macro base station
  • a micro base station also referred to as a small station
  • a relay station or an access point.
  • the name of a device with radio access capability may be different, for example, in an LTE system, called an evolved Node B (eNB or eNodeB),
  • eNB evolved Node B
  • 3G third generation
  • it Node B
  • it is simply referred to as an access network device, sometimes also referred to as a base station.
  • the wireless devices involved in the embodiments of the present application may include various handheld devices having wireless communication functions, in-vehicle devices, wearable devices, computing devices, or other processing devices connected to the wireless modem.
  • the wireless device may be referred to as a terminal device, and may also be referred to as a mobile station (MS), a terminal, a user equipment (UE), or the like.
  • the wireless device may be a subscriber unit, a cellular phone, a smart phone, a wireless data card, a personal digital assistant (PDA) computer, a tablet computer, a modem ( Modem) or modem processor, handheld, laptop computer, netbook, cordless phone or wireless local loop (WLL) station, Bluetooth device , machine type communication (MTC) terminal, etc.
  • PDA personal digital assistant
  • WLL wireless local loop
  • Bluetooth device machine type communication
  • the wireless device can support one or more wireless technologies for wireless communication, such as 5G, LTE, WCDMA, CDMA, 1X, Time Division-Synchronous Code Division Multiple Access (TS-SCDMA), GSM, 802.11 and more.
  • Wireless devices can also support carrier aggregation techniques.
  • Multiple wireless devices can perform the same or different services. For example, mobile broadband services, Enhanced Mobile Broadband (eMBB) services, and Ultra-Reliable and Low-Latency Communication (URLLC) services.
  • eMBB Enhanced Mobile Broadband
  • URLLC Ultra-Reliable and Low-Latency Communication
  • the access network device 102 is capable of performing the method provided by the embodiments of the present application.
  • the access network device 102 may include a controller or a processor 201 (hereinafter, the processor 201 is taken as an example) and a transceiver 202.
  • Controller/processor 201 is sometimes also referred to as a modem processor.
  • Modem processor 201 can include a baseband processor (BBP) (not shown) that processes the digitized received signal to extract information or data bits conveyed in the signal.
  • BBP baseband processor
  • DSPs digital signal processors
  • ICs integrated circuits
  • the transceiver 202 can be used to support the transmission and reception of information between the access network device 102 and the terminal device, and to support radio communication between the terminal devices.
  • the processor 201 can also be used to perform functions of communication between various terminal devices and other network devices.
  • the uplink signal from the terminal device is received via the antenna, coordinated by the transceiver 202, and further processed by the processor 201 to recover the traffic data and/or signaling information transmitted by the terminal device.
  • the traffic data and/or signaling messages are processed by the terminal device and modulated by the transceiver 202 to generate a downlink signal and transmitted to the UE via the antenna.
  • the access network device 102 can also include a memory 203 that can be used to store program code and/or data for the access network device 102.
  • the transceiver 202 can include separate receiver and transmitter circuits, or the same circuit can implement transceiving functions.
  • the access network device 102 can also include a communication unit 204 for supporting the access network device 102 to communicate with other network entities. For example, it is used to support the access network device 102 to communicate with a network device or the like of the core network.
  • the access network device may further include a bus.
  • the transceiver 202, the memory 203, and the communication unit 204 can be connected to the processor 201 through a bus.
  • the bus can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus.
  • PCI Peripheral Component Interconnect
  • EISA Extended Industry Standard Architecture
  • the bus may include an address bus, a data bus, a control bus, and the like.
  • FIG. 3 is a schematic diagram of a possible structure of a terminal device in the above wireless communication system.
  • the terminal device is capable of performing the method provided by the embodiment of the present application.
  • the terminal device can be any of the two terminal devices 104.
  • the terminal device includes a transceiver 301, an application processor 302, a memory 303, and a modem processor 304.
  • the transceiver 301 can condition (e.g., analog convert, filter, amplify, upconvert, etc.) the output samples and generate an uplink signal that is transmitted via an antenna to the base station described in the above embodiments. On the downlink, the antenna receives the downlink signal transmitted by the access network device. Transceiver 301 can condition (eg, filter, amplify, downconvert, digitize, etc.) the signals received from the antenna and provide input samples.
  • Modem processor 304 also sometimes referred to as a controller or processor, may include a baseband processor (BBP) (not shown) that processes the digitized received signal to extract information conveyed in the signal Or data bits.
  • BBP baseband processor
  • the BBP is typically implemented in one or more numbers within the modem processor 304 or as a separate integrated circuit (IC), as needed or desired.
  • a modem processor 304 may include an encoder 3041, a modulator 3042, a decoder 3043, and a demodulator 3044.
  • the encoder 3041 is for encoding the signal to be transmitted.
  • encoder 3041 can be used to receive traffic data and/or signaling messages to be transmitted on the uplink and to process (e.g., format, encode, or interleave, etc.) the traffic data and signaling messages.
  • Modulator 3042 is used to modulate the output signal of encoder 3041.
  • the modulator can perform symbol mapping and/or modulation processing on the encoder's output signals (data and/or signaling) and provide output samples.
  • a demodulator 3044 is used to demodulate the input signal.
  • demodulator 3044 processes the input samples and provides symbol estimates.
  • the decoder 3043 is configured to decode the demodulated input signal.
  • the decoder 3043 deinterleaves, and/or decodes the demodulated input signal and outputs the decoded signal (data and/or signaling).
  • Encoder 3041, modulator 3042, demodulator 3044, and decoder 3043 may be implemented by a composite modem processor 304. These units are processed according to the radio access technology employed by the radio access network.
  • Modem processor 304 receives digitized data representative of voice, data or control information from application processor 302 and processes the digitized data for transmission.
  • the associated modem processor can support one or more of a variety of wireless communication protocols of various communication systems, such as LTE, new air interface, Universal Mobile Telecommunications System (UMTS), high speed packet access (High Speed) Packet Access, HSPA) and more.
  • UMTS Universal Mobile Telecommunications System
  • High Speed Packet Access High Speed Packet Access
  • one or more memories may also be included in the modem processor 304.
  • the modem processor 304 and the application processor 302 may be integrated in one processor chip.
  • the memory 303 is used to store program code (sometimes referred to as programs, instructions, software, etc.) and/or data for supporting communication of the terminal device.
  • the memory 203 or the memory 303 may include one or more storage units, for example, may be a processor 201 for storing program code or a storage unit inside the modem processor 304 or the application processor 302, or may Is an external storage unit separate from the processor 201 or the modem processor 304 or the application processor 302, or may also be a storage unit including the processor 201 or the modem processor 304 or the application processor 302 and with the processor 201 or modem
  • the processor 304 or the application processor 302 is a separate component of an external storage unit.
  • the processor 201 and the modem processor 301 may be the same type of processor or different types of processors. For example, it can be implemented in a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), and a field programmable gate array ( Field Programmable Gate Array (FPGA) or other programmable logic device, transistor logic device, hardware component, other integrated circuit, or any combination thereof.
  • the processor 201 and the modem processor 301 can implement or perform various exemplary logical blocks, modules and circuits described in connection with the disclosure of the embodiments of the present application.
  • the processor may also be a combination of computing function devices, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, or a system-on-a-chip (SOC) or the like.
  • the existing communication technologies do not specifically consider the reliability of continuous application layer data packet transmission in the design process.
  • the prior art usually only designs the transmission reliability guarantee for one data packet, and makes the data through the retransmission mechanism.
  • the transmission of the package reaches a certain level of reliability.
  • the embodiment of the present application proposes a method for dynamically adjusting the reliability of a subsequent data packet transmission according to the transmission state of the previous data packet, for the feature that the application layer does not allow two consecutive data packet errors.
  • FIG. 4 is a schematic flowchart of a method for circumventing a failure of continuous data packet transmission according to an embodiment of the present disclosure, which may be applied to a network architecture as shown in FIG. 1 and a terminal device and an access network shown in FIG. 2 and FIG. 3. device.
  • the sending end in the embodiment of the present application may be a terminal device or an access network device.
  • the receiving end may be an access network device; when the sending end is an access network device, The receiving end may be a terminal device, but the application is not limited thereto.
  • Step 401 The first entity of the access layer of the transmitting end maintains a transmission state of a previous data packet of the first entity of the access layer.
  • the data packet mentioned here may be a service data unit (SDU) or a protocol data unit (PDU) of the first entity of the access layer.
  • SDU service data unit
  • PDU protocol data unit
  • the data packet is an application layer data packet
  • the communication layer is used as an initial service data unit (SDU) of the communication layer.
  • SDU initial service data unit
  • the transmission status includes a successful transmission or a transmission failure.
  • the first entity of the access layer of the sending end may be at least one of the following: a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, and a wireless chain.
  • SDAP service data adaptation protocol
  • PDCP packet data convergence protocol
  • RLC Radio link control
  • MAC media access control
  • RRC radio resource control
  • PHY physical (physical, PHY) layer.
  • the data packet of the application layer is transmitted as a SDAP SDU
  • the SDAP header is encapsulated into a SDAP PDU and delivered to the PDCP layer
  • the SDAP PDU received by the PDCP layer is transmitted as a PDCP SDU.
  • the PDCP header is encapsulated into a PDCP protocol data unit (PDU) and then delivered to the next layer of the RLC layer.
  • the PDCP PDU received by the RLC is the RLC SDU
  • the RLC SDU is encapsulated into the RLC with the RLC header.
  • PDU Since the RLC layer has a segmentation function, one RLC SDU may be segmented into multiple RLC PDUs for transmission.
  • the RLC PDUs of multiple logical channels are multiplexed at the MAC layer to form a MAC PDU. Each RLC PDU appears to the MAC layer as a MAC SDU.
  • the access layer entity of the sending end maintains a transmission status of a previous data packet of the access layer entity according to at least one of the following information:
  • the transmission state of the previous data packet is considered to be a transmission failure; otherwise, the previous data packet transmission state is considered to be a successful transmission;
  • the indication information sent by the first entity of the receiving end access layer to the access layer of the sending end is used to indicate that the previous data packet of the first entity of the access layer of the sending end is a transmission success or a transmission failure;
  • the indication information sent by the second accessing layer of the first entity of the first accessing layer of the first access entity of the transmitting end to the first entity of the first access entity of the sending end is that the transmission is successful or the transmission fails.
  • the indication information sent by the second accessing layer of the receiving end to the transmitting end access layer is used to indicate that the previous data packet of the first entity of the sending end of the sending end is a successful transmission or a transmission failure;
  • the first entity or the second entity of the sending end access layer determines, according to the sequence number of the current data packet, that the sequence number of the current data packet received is not consecutive with the sequence number of the previous data packet, and determines that the previous data packet transmission fails;
  • the first entity or the second entity of the receiving end access layer learns the period of the data packet according to the QoS information, and if no data packet arrives in the previous period, it determines that the previous data packet transmission fails;
  • the indication information of the non-access stratum or the application layer of the sending end to the transmitting end access layer is used to indicate that the previous data packet of the first entity of the sending end access layer is a transmission success or a transmission failure.
  • first entity of the access layer and the second entity of the access layer in the embodiment of the present application may be a non-access stratum entity or another protocol layer entity, which is not limited in this application.
  • Step 402 If the transmission status of the previous data packet is a transmission failure, the transmitting end adjusts a transmission parameter of the current data packet.
  • the transmission parameter may be a radio resource configuration parameter.
  • the transmission parameter includes at least one of: a modulation and coding scheme (MCS); a maximum hybrid automatic repeat request (HARQ) number; and a maximum automatic retransmission (automatic repeat request) , ARQ) times; transmission resource period; transmission resource location; transmission resource size; transmission resource type; logical channel priority; radio bearer priority; radio link control transmission mode (RLC AM or UM or TM); The number of carriers transmitted; the type of radio bearer; the function of the radio bearer (for example, whether to use repeated transmission, whether to use single or dual or multi-connection); transmit power.
  • MCS modulation and coding scheme
  • HARQ maximum hybrid automatic repeat request
  • ARQ maximum automatic retransmission
  • the MCS modulation coding table is a representation of 802.11n for characterizing the communication rate.
  • the MCS uses the factors affecting the communication rate as the column of the table, and uses the MCS index as a row to form a rate table. Therefore, each MCS The index corresponds to the physical transmission rate under a set of parameters.
  • the maximum hybrid automatic retransmission number indicates the maximum number of times the same MAC PDU is transmitted at the MAC layer.
  • the maximum number of automatic retransmissions indicates the maximum number of times the same RLC PDU is transmitted at the RLC layer.
  • the period of the transmission resource may include, for example, a period of SPS (semi-persistent scheduling) resources, that is, an interval in the time domain of two adjacent SPS resources.
  • SPS semi-persistent scheduling
  • the location of the transmission resource may include, for example, the time domain of the SPS resource and the start and end locations of the frequency domain.
  • the frequency domain location may be a carrier index or a subcarrier index or a BWP (bandwidth part) index
  • the time domain location may be a symbol index, a slot number, a subframe number, a frame number, a superframe number, and the like.
  • the size of the transmission resource may include the size of the SPS resource, the number of time domain units occupied in the time domain, or the number of frequency domain units.
  • the time domain unit may be a symbol, a time slot, a subframe, a frame, a superframe, etc.
  • the frequency domain unit may be a carrier, a subcarrier, a BWP, or the like.
  • the type of transmission resource may include, for example, an SPS resource or a GrantFree (unauthorized) resource or a dynamically scheduled resource.
  • the logical channel priority is used to indicate the priority of each logical channel when it is multiplexed at the MAC layer. Different logical channels can have the same priority.
  • the radio link control layer RLC layer has three transmission modes, namely RLC AM, RLC UM and RLC TM.
  • RLC AM acknowledged mode
  • This mode provides all RLC functions.
  • RLC UM (unacknowledged mode): This mode provides all RLC functions except retransmission and re-segmentation, thus providing an unreliable transmission service.
  • RLC TM transparent mode
  • This mode can be considered as an empty RLC. It does not do any processing on the RLC SDU. No RLC header is added because this mode only provides the passthrough function of data.
  • the types of radio bearers include a data radio bearer (DRB) and a signaling radio bearer (SRB). Further, the type of radio bearer may also include different DRB IDs and SRB IDs.
  • DRB data radio bearer
  • SRB signaling radio bearer
  • Transmit power refers to the transmit power used by the sender to transmit a MAC PDU.
  • FIG. 6 is a schematic flowchart of a method for circumventing a failure of continuous data packet transmission according to an embodiment of the present disclosure, which may be applied to a network architecture as shown in FIG. 1 and a terminal device and an access network shown in FIG. 2 and FIG. 3. device.
  • the sending end in the embodiment of the present application may be a terminal device or an access network device.
  • the receiving end may be an access network device; when the sending end is an access network device, The receiving end may be a terminal device, but the application is not limited thereto.
  • Step 601 The first entity of the access layer of the sending end acquires the transmission status of the first n data packets of the first entity of the access layer.
  • the data packet mentioned here may be a service data unit (SDU) or a protocol data unit (PDU) of the first entity of the access layer. Specifically, it may be a data packet from an application layer, and an initial service data unit (SDU) of the communication layer as a communication layer.
  • the transmission status includes a successful transmission or a transmission failure.
  • the first entity of the access layer of the sending end may be at least one of the following: a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, and a wireless chain.
  • SDAP service data adaptation protocol
  • PDCP packet data convergence protocol
  • RLC Radio link control
  • MAC media access control
  • RRC radio resource control
  • PHY physical (physical, PHY) layer.
  • Step 602 If the transmission status of the m data packets in the first n data packets is a transmission failure, the transmitting end adjusts the transmission parameters of the current data packet.
  • the transmission parameters in step 602 are the same as the transmission parameters in step 402, and will not be described again.
  • the first entity of the access layer of the transmitting end determines whether there are m data packet transmissions in the first n data packets.
  • the state is a transmission failure, where n is a positive integer and m is a positive integer less than or equal to n.
  • m data packets may be continuous data packets or non-contiguous data packets. When m data packets are consecutive data packets, m ⁇ 2. If the transmitting end determines that the transmission status of the m data packets in the first n data packets is a transmission failure, the transmitting end adjusts the transmission parameters of the current data packet (the n+1th data packet).
  • the access layer entity of the sending end acquires the transmission status of the first n data packets of the access layer entity according to at least one of the following:
  • the sender access layer The first entity maintains a plurality of counters (for example, a first counter and a second counter).
  • the first counter is used to count n data packets of the first entity of the access layer
  • the second counter is used to count the number of data packets that have failed to be transmitted in the n data packets.
  • the initial value of the first counter and the second counter is zero.
  • a threshold is set for the second counter, which may be configured by the core network device or the access network device, or the threshold may also be obtained from the application layer or the non-access layer of the terminal device.
  • the first entity of the sending end access layer obtains the transmission state of each data packet, and the obtaining method is the same as the method for obtaining the transmission state of the previous data packet in step 401, and details are not described herein again.
  • the value of the first counter is +1; when the first entity of the access layer of the transmitting end acquires the transmission state of a data packet as the transmission failure, the second counter The value is +1.
  • the transmitting end When the value of the second counter is greater than or equal to the threshold, for example, if the threshold is set to m, it is considered that the transmission state of m data packets in the first n data packets of the access layer entity of the transmitting end is a transmission failure, and the transmitting end needs to be adjusted. The transmission parameters of the current packet. When the value of the first counter is equal to n and the value of the second counter is less than the threshold m, the transmitting end still maintains the transmission parameters of the current data packet.
  • the receiving end access layer first entity sends the access layer indication information to the transmitting end, and is used to indicate whether the first n data packets of the first entity of the transmitting end access layer have m data packet transmission failures.
  • the indication information that is sent by the second entity of the first accessing layer to the first entity of the first layer of the first entity of the first access entity of the sending end, is the presence of m data packets. The transfer failed.
  • the indication information sent by the second access entity of the receiving end access layer to the access layer of the transmitting end is used to indicate whether the first n data packets of the first entity of the access layer of the transmitting end have failed to transmit m data packets.
  • the first entity or the second entity of the receiving end access layer may receive the indication information of the first entity of the receiving end access layer or the second entity of the transmitting end access layer, where the indication information includes the currently transmitted data packet.
  • the serial number and the transmission status of the packet corresponding to each serial number.
  • the first entity of the sender access layer maintains a counter, and the counter is used to count the number of accumulated data packets that failed to be transmitted. The initial value of the counter is 0. If the sequence number of the received current data packet is not continuous with the sequence number of the previous data packet, the value of the counter is +1.
  • the threshold of the setting counter is m, and when the value of the counter is greater than or equal to the threshold m, it is considered that there are transmission states of m data packets in the first n data packets of the access layer entity of the transmitting end. Failed for transmission.
  • the indication information of the non-access stratum or the application layer of the sending end to the transmitting end access layer is used to indicate whether the first n data packets of the first entity of the transmitting end access layer have m data packet transmission failures.
  • first entity of the access layer and the second entity of the access layer in the embodiment of the present application may be a non-access stratum entity or another protocol layer entity, which is not limited in this application.
  • n when the sending end is a terminal device, n may be configured by the access network device or the core network device; or n may be obtained from an application layer or a non-access stratum of the terminal device.
  • the calculation may be performed according to the survival time T of the application layer and the cycle time or transfer time t of the application layer service. .
  • T survival time
  • t the survival time
  • t the cycle time or transfer time t of the application layer service.
  • n T/t. If the result of T/t cannot be divisible, it can be rounded up or down.
  • T t is configured by the access network device or the core network device or obtained from the application layer or the non-access layer of the terminal device.
  • m may be configured by an access network device or a core network device, or obtained from an application layer or a non-access layer of the terminal device.
  • n when the sending end is an access network device, n may be configured by the core network device or reported by the terminal device.
  • the T, t is configured by the core network device or reported by the terminal device.
  • m can be configured by the core network device or reported by the terminal device.
  • the T, t is configured by the core network device or reported by the terminal device.
  • n may be configured by the core network device or configured by the access network device or obtained by the terminal device or obtained from the application layer or the non-access layer of the terminal device.
  • the embodiments of the present application are not limited to the embodiment described in FIG. 6.
  • the first entity of the access layer of the transmitting end may acquire the transmission state of each data packet of the first entity of the access layer; when the access layer is acquired within a preset time If the transmission status of s packets in an entity's data packet is a transmission failure, the sender adjusts the transmission parameters of the current data packet. Where s is a positive integer.
  • the first entity of the access layer of the transmitting end may acquire the transmission state of at least k forward packets of the first entity of the access layer; when acquiring the first entity of the access layer In the data packet, the transmission status of consecutive k data packets is transmission failure, and the transmitting end adjusts the transmission parameters of the current data packet.
  • k is a positive integer and k ⁇ 2.
  • the first entity of the access layer of the sending end acquires the transmission state of at least the first x data packets of the access layer entity; when the obtained transmission state of the first x data packets is the transmission failure, The transmitting end adjusts a transmission parameter of the current data packet.
  • x is a positive integer and x ⁇ 2.
  • Embodiment 1 Maintenance and transmission parameter adjustment of RLC SDU transmission state based on RLC feedback at the receiving end
  • FIG. 7 is a schematic flowchart of adjusting an RLC SDU transmission state error based on receiving RLC feedback provided by an embodiment of the present application.
  • the following takes the receiving end as the access network device as an example, including the following steps (but the application is not limited to this):
  • Step S701 the access network device determines, according to the quality of service (QoS) information corresponding to the bearer, whether there is a requirement for continuous data packet transmission reliability in the radio bearer establishment process. If there is a need for continuous data packet transmission reliability, two sets of resource parameters are configured. The two sets of resource parameters are different in at least the content of the RadioResourceConfigDedicated information element, which may be the maximum number of HARQ transmissions or the number of ARQ transmissions, MCS, etc., but This application is not limited to this. QoS information can be obtained from the core network or obtained from the terminal device. In the following steps, State_RLC_1 is a variable used by the sender to maintain the transmission status of the previous packet, and State_RLC_2 is a variable used by the sender to maintain the current packet transmission status.
  • QoS quality of service
  • Step S702 The RLC entity of the terminal device receives an RLC SDU1 from an upper layer (for example, a PDCP layer), and sets a transmission state variable State_RLC_1 corresponding to the RLC SDU1 to False.
  • an upper layer for example, a PDCP layer
  • Step S703 It is assumed that the RLC SDU1 is segmentally transmitted due to limited underlay scheduling resources, and is respectively encapsulated into RLC PDU1 and RLC PDU2.
  • the polling field in the RLC header of the RLC PDU2 is set.
  • Step S704 Assuming that the RLC PDU1 transmission fails, the RLC PDU2 transmission is successful.
  • the RLC entity of the access network device receives the RLC PDU2, because the polling is set, the RLC entity of the access network device generates a status report, which includes each RLC PDU (including at least RLC PDU1 and RLC PDU2). ) Whether the information was successfully received.
  • Step S705 The terminal device receives the status report sent by the access network device, and learns that the RLC PDU1 transmission fails. Therefore, it is determined that the RLC SDU1 transmission fails, and the state_RLC_1 is maintained as False.
  • the RLC layer needs to indicate that the transmission status of the RLC SDU1 is a failure indication to another protocol layer, such as an RRC layer or a MAC layer or a PHY layer or a PDCP layer.
  • another protocol layer such as an RRC layer or a MAC layer or a PHY layer or a PDCP layer.
  • each protocol layer sets the transmission parameter corresponding to the layer to The second resource parameter.
  • Step S706 The RLC entity of the terminal device receives the RLC SDU2, because State_RLC_1 is False, and therefore, for the RLC SDU2, the second resource parameter is used for transmission. Set the initial transport state variable State_RLC_2 of the corresponding RLC SDU2 to False.
  • Step S707 It is assumed that the RLC SDU 2 has no segmentation at the RLC layer, and is directly encapsulated into an RLC PDU3 and submitted to the bottom layer for transmission, wherein the polling field is set.
  • Step S708 Assuming that the RLC PDU3 transmission fails, the RLC entity of the access network device receives the RLC PDU3 because the polling field is set, and generates a status report, which includes information about whether each RLC PDU (including at least RLC PDU3) is successfully received. .
  • Step S709 The terminal device receives the status report sent by the access network device, and learns that the RLC PDU3 is successfully transmitted. Therefore, it is determined that the RLC SDU2 is successfully transmitted, and the State_RLC_2 is set to True.
  • the RLC layer needs to indicate the transmission status of the RLC SDU 2 to the other protocol layer, such as the RRC layer or the MAC layer or the PHY layer or the PDCP layer.
  • the other protocol layer such as the RRC layer or the MAC layer or the PHY layer or the PDCP layer.
  • each protocol layer sets the transmission parameter corresponding to the layer. Is the first resource parameter.
  • Embodiment 2 Maintenance and transmission parameter adjustment of RLC SDU transmission state based on feedback of the MAC layer of the receiving end
  • FIG. 8 is a schematic flowchart of adjusting an RLC SDU transmission state error based on feedback of a MAC layer of a receiving end according to an embodiment of the present application.
  • the following takes the receiving end as the access network device as an example, including the following steps (but the application is not limited to this):
  • Step 801 and step 802 are the same as step 701 and step 702 in FIG. 7, and details are not described herein again.
  • Step 803 Assume that the RLC SDU1 has no segmentation and is encapsulated as RLC PDU1.
  • the RLC PDU1 is delivered to the MAC layer for transmission.
  • the MAC layer is encapsulated as MAC PDU1.
  • Step 804 Assume that the MAC PDU1 fails to transmit x times consecutively, and x is a positive integer.
  • the MAC layer indicates the information to the RLC entity where the RLC PDU1 is located.
  • the RLC entity determines that the RLC SDU1 transmission fails, and maintains the State_RLC_1 as False.
  • x can be the maximum number of HARQ transmissions.
  • the MAC layer indicates that the RLC layer RLC PDU1 transmission fails after the MAC PDU1 reaches the maximum number of HARQ transmissions.
  • the RLC layer needs to indicate that the transmission status of the RLC SDU1 is a failure indication to another protocol layer, such as an RRC layer or a MAC layer or a PHY layer or a PDCP layer.
  • another protocol layer such as an RRC layer or a MAC layer or a PHY layer or a PDCP layer.
  • each protocol layer sets the transmission parameter corresponding to the layer to The second resource parameter.
  • Step 805 The RLC entity of the terminal device receives an RLC SDU2 from the upper layer, and sets the transmission state variable State_RLC_2 corresponding to the RLC SDU2 to False.
  • Step 806 Assume that the RLC SDU2 has no segmentation and is encapsulated as RLC PDU2.
  • the RLC PDU2 is delivered to the MAC layer for transmission.
  • the MAC layer is encapsulated as MAC PDU2.
  • Step 807 Assuming that the MAC PDU2 transmission is successful, the MAC layer indicates the information to the RLC entity where the RLC PDU2 is located, and the RLC entity determines that the RLC SDU2 is successfully transmitted, and maintains the State_RLC_2 as True.
  • the RLC layer needs to indicate the transmission status of the RLC SDU2 to the other protocol layer, such as the RRC layer or the MAC layer or the PHY layer or the PDCP layer.
  • the other protocol layer such as the RRC layer or the MAC layer or the PHY layer or the PDCP layer.
  • each protocol layer sets the transmission parameter corresponding to the layer to The first set of parameters.
  • Each RLC entity on the transmitting end maintains the transmission status of each RLC SDU in the entity.
  • the RLC entity maintains a variable State_RLC_SN for the RLC SDU whose RLC layer sequence number is SN.
  • condition that the variable State_RLC_SN is set to False in the first embodiment and the second embodiment includes at least one of the following:
  • the RLC entity of the sending end sets the polling field according to the number of sending RLC SDUs (for example, one), that is, sets the polling field when the last RLC PDU corresponding to each RLC SDU is sent, and the RLC of the receiving end.
  • the entity generates a status report each time it receives an RLC SDU.
  • the MAC layer indicates that at least one of the MAC PDUs of all the RLC PDUs corresponding to the RLC SDU is not successfully transmitted in consecutive n HARQ transmissions, and n is a positive integer, which is configured by RRC signaling of the access network device. Alternatively, n can be equal to the maximum number of HARQs.
  • the PDCP layer indicates that the RLC SDU or its corresponding PDCP SDU/PDU is not successfully transmitted
  • the RLC layer does not receive a status report containing the successful RLC SDU transmission corresponding to the SN within a timer timeout range.
  • State_RLC_SN obtained directly from a certain layer signaling (RLC Control PDU or RRC signaling or MAC CE or DCI) of the receiving end is False.
  • RLC Control PDU or RRC signaling or MAC CE or DCI the value of State_RLC_SN obtained directly from a certain layer signaling (RLC Control PDU or RRC signaling or MAC CE or DCI) of the receiving end is False.
  • the terminal device When the RLC layer does not successfully decode the RLC SDU corresponding to the SN (for example, the reordering timer expires or the SDU content cannot be identified), the terminal device generates signaling including the Stae_RLC_SN value of False, and the signaling may be RRC. Signaling or MAC control element (CE) or RLC control PDU or downlink control information (DCI).
  • CE MAC control element
  • DCI downlink control information
  • condition that the variable State_RLC_SN is set to True in the first embodiment and the second embodiment includes at least one of the following:
  • the status report of the RLC entity feedback of the peer end indicates that all the RLC PDUs corresponding to the RLC SDU are successfully received.
  • the RLC entity of the sending end sets the polling field according to the number of sending RLC SDUs (for example, one), that is, every The polling field is set when the last RLC PDU corresponding to an RLC SDU is sent;
  • the MAC layer indicates that all the MAC PDUs of the RLC PDU corresponding to the RLC SDU are successfully transmitted, and the MAC layer feeds back the transmission status of each RLC PDU to the RLC entity corresponding to each logical channel;
  • the PDCP layer indicates that the RLC SDU or its corresponding PDCP SDU/PDU is successfully transmitted
  • State_RLC_SN is obtained directly from a certain layer signaling of the receiving end (PDCP Control PDCU or RLC Control PDU or MAC CE or DCI or RRC Signaling).
  • the receiving end When the RLC layer successfully decodes an RLC SDU corresponding to a certain SN, the receiving end generates signaling including a State_RLC_SN value of True, and the signaling may be RRC signaling or MAC CE or RLC control PDU or DCI.
  • the RLC entity indicates the transmission status of each RLC SDU to other layers, such as RRC or SDAP or PDCP or MAC or PHY layer.
  • the status of the state_RLC_SN is False. If the RLC SDU whose sequence number is SN+1 is to be sent, the sender uses the second resource parameter for transmission, including:
  • the PDCP layer or the RLC layer activates the duplication of the bearer or logical channel where the RLC SDU of the SN+1 is located.
  • transmission time interval bundling for example, transmission time interval bundling, TTI bundling number, modulation and coding scheme; maximum hybrid automatic retransmission HARQ times; maximum automatic retransmission ARQ times; transmission resource period; Location of transmission resource; size of transmission resource; type of transmission resource; priority of logical channel; priority of radio bearer; transmission mode of radio link control; number of carriers transmitted; type of radio bearer; function of radio bearer, etc.
  • pre-configured parameters for example, transmission time interval bundling, TTI bundling number, modulation and coding scheme; maximum hybrid automatic retransmission HARQ times; maximum automatic retransmission ARQ times; transmission resource period; Location of transmission resource; size of transmission resource; type of transmission resource; priority of logical channel; priority of radio bearer; transmission mode of radio link control; number of carriers transmitted; type of radio bearer; function of radio bearer, etc.
  • this parameter is configured by RRC signaling and is activated when the RLC SDU transmission with sequence number SN fails.
  • Embodiment 3 is a diagrammatic representation of Embodiment 3
  • FIG. 9 is a schematic diagram of a process for adjusting a PDCP SDU transmission state error based on feedback of a PDCP layer at a receiving end according to an embodiment of the present application.
  • the transmitting end in the uplink, the terminal device is taken as an example, each PDCP entity maintains the transmission status of each PDCP SDU/PDU in the entity.
  • the PDCP entity maintains a variable State_PDCP_SN for the PDCP SDU/PDU whose PDCP layer sequence number is SN.
  • condition that the variable State_PDCP_SN is set to False includes at least one of the following:
  • the PDCP SDU/PDU transmission failure is displayed in the status report received from the peer PDCP entity.
  • the PDCP entity at the transmitting end sets the polling field in the header of each PDCP PDU, and the receiving PDCP entity receives each PDCP PDU.
  • the RLC layer indicates that the PDCP PDU transmission failure of the PDCP layer is successful
  • the PDCP layer times out the discardTimer of the PDCP SDU
  • State_PDCP_SN obtained directly from a certain layer of signaling (PDCP Control PDU or RRC signaling or MAC CE or DCI) of the opposite end is False;
  • NAS non-access stratum
  • condition that the variable State_PDCP_SN is set to True includes at least one of the following:
  • the status report of the PDCP entity feedback at the receiving end indicates that the PDCP SDU/PDU transmission is successful.
  • the RLC layer indicates that the PDCP SDU/PDU transmission is successful.
  • State_PDCP_SN obtained from a certain layer of signaling (PDCP Control PDU or MAC CE or DCI or RRC signaling) of the opposite end is True.
  • the receiving end When the PDCP layer successfully decodes a PDCP SDU corresponding to a certain SN, the receiving end generates signaling including a Stae_PDCP_SN value of True, and the signaling may be RRC signaling or MAC CE or PDCP control PDU or DCI;
  • the PDCP entity indicates the transmission status of each PDCP SDU/PDU to other layers, such as RRC or SDAP or RLC or MAC or PHY layer.
  • the transmitting end uses the second resource parameter for transmission, including:
  • the PDCP layer or the RLC layer activates the duplication of the bearer or logical channel where the PDCP SDU of the SN+1 is located.
  • pre-configured parameters including TTI bundling number, modulation and coding scheme; maximum hybrid automatic retransmission HARQ times; maximum automatic retransmission ARQ times; transmission resource period; transmission resource location; transmission resource size; transmission Type of resource; logical channel priority; radio bearer priority; radio link control transmission mode; number of transmitted carriers; type of radio bearer; function of radio bearer, etc.
  • transmission of PDCP SDU of SN+1 the parameter is determined by RRC Let the configuration be activated when the PDCP SDU with serial number SN fails to transmit.
  • Embodiment 4 is a diagrammatic representation of Embodiment 4:
  • FIG. 10 is a schematic flowchart of another method for circumventing a failure of continuous data packet transmission according to an embodiment of the present disclosure. Take the sending end as the access network device as an example, including the following steps:
  • Step 1001 The access network device obtains a period of the data packet from the core network device, where the access network device should receive one data packet in each period.
  • Step 1002 The access network device receives the data packet 1 in the period 1 and transmits according to the transmission parameter 1 (the first resource parameter), and assumes that the transmission is successful in the air interface.
  • the transmission parameter 1 the first resource parameter
  • Step 1003 The access network device sends the data packet 1 to the terminal device.
  • Step 1004 The core network device sends the data packet 2 to the access network device, but the access network device does not receive the data packet 2 in the period 2, and the access network device data packet 2 fails to be transmitted (that is, the data packet 2 is lost). .
  • Step 1005 The access network device sets the transmission status of the data packet 2 to the transmission failure, and adjusts the transmission parameter of the data packet 3 to the transmission parameter 2 (the second resource parameter).
  • Step 1006 The access network device receives the data packet 3 sent by the core network device in the period 3.
  • Step 1007 The access network device sends the data packet 3 to the terminal device.
  • Embodiment 5 is a diagrammatic representation of Embodiment 5:
  • FIG. 11 is a schematic flowchart of another method for circumventing a failure of continuous data packet transmission according to an embodiment of the present disclosure. Take the sending end as the terminal device as an example, including the following steps:
  • Step 1101 The PDCP layer of the transmitting terminal device sends the PDCP SDU1 to the access network device.
  • Step 1102 The terminal device obtains a PDCP SDU1 transmission error from the NAS layer or the application layer, and the terminal device sets the transmission state corresponding to the PDCP SDU1 as a transmission error.
  • the terminal device adjusts the transmission parameter of the PDCP SDU2 to the transmission parameter 2 (the second resource parameter) to perform the transmission of the PDCP SDU2.
  • Step 1103 The terminal device transmits the PDCP SDU2 to the access network device by using the transmission parameter 2.
  • FIG. 12 is a schematic flowchart of another method for circumventing a failure of continuous data packet transmission according to an embodiment of the present disclosure. Take the sending end as the terminal device as an example, including the following steps:
  • Step 1201 The PDCP layer of the transmitting terminal device sends the PDCP SDU1 to the access network device, and starts a timer.
  • Step 1202 The terminal device does not obtain the indication information that the PDCP SDU1 is successfully transmitted before the timer expires.
  • the terminal device sets the transmission state corresponding to the PDCP SDU1 to a transmission error, and adjusts the transmission parameter of the PDCP SDU2 to the transmission parameter 2 (the second resource parameter) to perform the transmission of the PDCP SDU2.
  • Step 1203 The terminal device transmits the PDCP SDU2 to the access network device by using the transmission parameter 2.
  • FIG. 13 is a schematic flowchart of another method for circumventing a failure of continuous data packet transmission according to an embodiment of the present disclosure. Take the sending end as the access network device as an example, including the following steps:
  • Step 1301 The transmitting end access network device successfully receives the data packet 1 sent by the core network device.
  • Step 1302 The access network device sends the data packet 1 to the terminal device.
  • Step 1303 The access network device successfully receives the data packet 3 sent by the core network device.
  • the access network device finds that the packet 2 is missing in the middle, and proves that the packet 2 is lost or the transmission fails.
  • Step 1304 The access network device sets the transmission status of the data packet 2 to the transmission failure, and adjusts the transmission parameter of the data packet 3 to the transmission parameter 2 (the second resource parameter).
  • Step 1305 The access network device transmits the data packet 3 to the terminal device according to the transmission parameter 2.
  • FIG. 14 is a schematic flowchart of another method for circumventing a failure of continuous data packet transmission according to an embodiment of the present disclosure. Take the sending end as the terminal device as an example, including the following steps:
  • Step 1401 The PDCP layer of the transmitting terminal device sends the PDCP SDU1 to the access network device.
  • Step 1402 The access network device informs the terminal device that the transmission status of the PDCP SDU1 is a transmission failure through the DCI or the MAC CE, or the access network device instructs the terminal device to use the second resource parameter to transmit the next PDCP SDU, that is, the PDCP SDU2. Not shown in the figure).
  • Step 1403 The terminal device sets the transmission state corresponding to the PDCP SDU1 to the transmission failure, and the terminal device adjusts the transmission parameter of the PDCP SDU2 to the transmission parameter 2 (the second resource parameter) to perform the transmission of the PDCP SDU2.
  • Step 1404 The terminal device transmits the PDCP SDU2 to the access network device by using the transmission parameter 2.
  • the transmission parameters of the current data packet are adjusted according to the transmission status of the previous data packet.
  • the transmitting end does not adjust the transmission parameters of the current data packet.
  • the transmission strategy of the next data packet can be quickly adjusted by the transmission state of the previous data packet, and the transmission of the latter data packet is ensured by using a higher reliability when the previous data packet transmission fails. Two consecutive packet transmissions failed.
  • the present application examples also provide a device (eg, an integrated circuit, a wireless device, a circuit module, etc.) for implementing the above method.
  • a device eg, an integrated circuit, a wireless device, a circuit module, etc.
  • the means for implementing the circumvention of continuous packet transmission failure described herein may be a stand-alone device or may be part of a larger device.
  • the device may be (i) a self-contained IC; (ii) a set having one or more 1Cs, which may include a memory IC for storing data and/or instructions; (iii) an RFIC, such as an RF receiver or RF transmitter (iv) an ASIC, such as a mobile station modem; (v) a module that can be embedded in other devices; (vi) a receiver, a cellular phone, a wireless device, a handset, or a mobile unit; (vii) other, etc. Wait.
  • a self-contained IC may include a memory IC for storing data and/or instructions; (iii) an RFIC, such as an RF receiver or RF transmitter (iv) an ASIC, such as a mobile station modem; (v) a module that can be embedded in other devices; (vi) a receiver, a cellular phone, a wireless device, a handset, or a mobile unit; (vii) other, etc. Wait.
  • the method and apparatus provided by the embodiments of the present application may be applied to a terminal device or an access network device (which may be collectively referred to as a wireless device).
  • the terminal device or access network device or wireless device may include a hardware layer, an operating system layer running on the hardware layer, and an application layer running on the operating system layer.
  • the hardware layer includes hardware such as a central processing unit (CPU), a memory management unit (MMU), and a memory (also referred to as main memory).
  • the operating system may be any one or more computer operating systems that implement business processing through a process, such as a Linux operating system, a Unix operating system, an Android operating system, an iOS operating system, or a Windows operating system.
  • the application layer includes applications such as browsers, contacts, word processing software, and instant messaging software.
  • the embodiment of the present application does not limit the specific structure of the execution subject of the method, as long as the transmission signal according to the embodiment of the present application can be executed by running a program that records the code of the method of the embodiment of the present application.
  • the method can be communicated.
  • the execution body of the method for wireless communication in the embodiment of the present application may be a terminal device or an access network device, or a function capable of calling a program and executing a program in the terminal device or the access network device. Module.
  • a computer readable medium may include, but is not limited to, a magnetic storage device (eg, a hard disk, a floppy disk, or a magnetic tape, etc.), such as a compact disc (CD), a digital versatile disc (DVD). Etc.), smart cards and flash memory devices (eg, erasable programmable read-only memory (EPROM), cards, sticks or key drivers, etc.).
  • a magnetic storage device eg, a hard disk, a floppy disk, or a magnetic tape, etc.
  • CD compact disc
  • DVD digital versatile disc
  • Etc. smart cards and flash memory devices (eg, erasable programmable read-only memory (EPROM), cards, sticks or key drivers, etc.).
  • various storage media described herein can represent one or more devices and/or other machine-readable media for storing information.
  • the term "machine-readable medium” may include, without limitation, a wireless channel and various other mediums capable of storing, containing, and/or carrying instructions and/or data.
  • the computer program product includes one or more computer instructions.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transfer to another website site, computer, server, or data center by wire (eg, coaxial cable, fiber optic, digital subscriber line (DSL), or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media.
  • the usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (such as a solid state disk (SSD)).
  • the size of the sequence numbers of the foregoing processes does not mean the order of execution sequence, and the execution order of each process should be determined by its function and internal logic, and should not be applied to this application.
  • the implementation of the embodiments constitutes any limitation.
  • the disclosed systems, devices, and methods may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • the functions may be stored in a computer readable storage medium if implemented in the form of a software functional unit and sold or used as a standalone product. Based on such understanding, the technical solution of the embodiments of the present application, or the part contributing to the prior art or the part of the technical solution, may be embodied in the form of a software product stored in a storage medium.
  • the instructions include a plurality of instructions for causing a computer device (which may be a personal computer, a server, or an access network device, etc.) to perform all or part of the steps of the methods described in the various embodiments of the embodiments of the present application.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like. .

Landscapes

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

Abstract

本申请实施例提供了一种连续数据包传输失败的规避方法及装置，涉及通信领域，其方法包括：发送端的接入层第一实体维护所述接入层第一实体的前一个数据包的传输状态，所述传输状态包括传输成功、传输失败或者丢包；如果所述前一个数据包的传输状态为传输失败，所述发送端调整当前数据包的传输参数。本申请实施例提供的方法保证在数据传输过程中，不出现连续2个应用层数据包都传输失败的情况，提高了数据传输的可靠性。

Description

连续数据包传输失败的规避方法及装置
本申请要求于2017年11月15日提交中国国家知识产权局、申请号为201711133111.X、申请名称为“连续数据包传输失败的规避方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及通信领域，并且更具体地，涉及一种连续数据包传输失败的规避方法及装置。
背景技术
工业控制场景中，运动控制(motion control)由于对通信的要求较高而挑战性比较大。运动控制器负责控制移动或旋转机器的某个部位(例如机械臂)来完成某项工作，例如递交货物或组装零件等。运动控制器与被控制的部位之间的通信方式可以采用有线通信或无线通信，无线通信的好处在于控制器与被控制单元之间无需部署线路，降低了成本，同时增加了系统对移动性的支持，被控制器可以到处随意移动。另外有些厂区厂房需要随时根据需求进行生产线的定制、改组，装备了无线通信系统的产线改组起来更方便。随着5G通信系统的发展，无线通信的通信性能越来越好，足以支持工业控制场景中的低时延高可靠类通信需求。因此5G通信会是未来工业控制领域的主要通信技术之一。
工业控制场景中对通信指标的要求较高，需要控制信令在很短时间内以很高的可靠性保证进行传输。在控制场景中，控制器通常会周期性的向被控制单元传输指令，指示其如何动作，由于通信不可能达到100％可靠性，因此应用层在设计时通常会允许某一个指令出现错误，但是不允许连续2个指令出现错误。如果连续2个控制信令出现丢失或传输错误，应用层就会断开连接或按照错误指令连续动作，这可能会导致设备损坏或者产线停产，造成巨大的财产或人身安全事故。
发明内容
本申请实施例提供一种连续数据包传输失败的规避方法及装置，保证在数据传输过程中，不出现连续2个应用层数据包都传输失败的情况，提高了数据传输的可靠性。
第一方面，提供了一种连续数据包传输失败的规避方法，包括：
发送端的接入层第一实体维护所述接入层第一实体的前一个数据包的传输状态；如果所述前一个数据包的传输状态为传输失败，所述发送端调整当前数据包的传输参数。
在一种可能的实现方式中，所述发送端的接入层第一实体为以下一种：无线链路控制层；业务数据适配协议层；无线资源控制层；介质访问控制层；物理层。
可选的，所述数据包是业务数据单元或协议数据单元。
在一种可能的实现方式中，所述发送端的接入层实体根据以下至少一种信息维护所述接入层实体的前一个数据包的传输状态：所述发送端接入层第一实体维护的定时器超时且前一个数据包还未成功传输，则认为前一个数据包的传输状态为传输失败，否则认为前一个数据包传输状态为传输成功；接收端接入层第一实体发送给发送端接入层的指示信息，用于指示所述发送端接入层第一实体的前一个数据包是传输成功或传输失败；发送端接入层第二实体发送给发送端接入层第一实体的指示信息，用于指示所述发送端接入层第一实体的前一个数据包是传输成功或传输失败；接收端接入层第二实体发送给发送端接入层的指示信息，用于指示所述发送端接入层第一实体的前一个数据包是传输成功或传输失败；发送端接入层第一实体或第二实体根据当前数据包的序号，若接收的当前数据包的序号与前一个数据包的序号不连续，判断前一个数据包传输失败；发送端接入层第一实体或第二实体根据QoS信息获知数据包的周期，若在前一个周期内没有数据包到达，判断前一个数据包传输失败；发送端非接入层或应用层给发送端接入层的指示信息，用于指示所述发送端接入层第一实体的前一个数据包是传输成功或传输失败。
可选的，所述传输参数包括以下至少一项：调制和编码方案；最大混合自动重传HARQ次数；最大自动重传ARQ次数；传输资源的周期；传输资源的位置；传输资源的大小；传输资源的类型；逻辑信道优先级；无线承载优先级；无线链路控制传输模式；传输的载波数；无线承载的类型；无线承载的功能。
第二方面，本申请的实施例提供一种规避连续数据包传输失败的装置，用于执行第一方面的方法。具体地，所述规避连续数据包传输失败的装置包括用于执行第一方面或第一方面的任意一种实现方式中的方法的单元。
第三方面，一种计算机可读存储介质，其上储存计算机程序(指令)，当该程序(指令)在计算机上运行时，使得该计算机执行上述任一方面所述的方法。
第四方面，本申请提供了一种芯片系统，该芯片系统包括处理器，用于支持规避连续数据包传输失败的装置实现上述方面中所涉及的功能，例如，例如生成或处理上述方法中所涉及的数据和/或信息。在一种可能的设计中，所述芯片系统还包括存储器，所述存储器，用于保存规避连续数据包传输失败的装置必要的程序指令和数据。该芯片系统，可以由芯片构成，也可以包含芯片和其他分立器件。
附图说明
图1为本申请实施例提供的一种无线通信系统的架构示意图；
图2为本申请实施例提供的一种终端设备结构图；
图3为本申请实施例提供的一种接入网设备结构图；
图4为本申请实施例提供的一种连续数据包传输失败的规避方法的流程示意图；
图5为本申请实施例提供的一种数据包传输示意图；
图6为本申请实施例提供的一种连续数据包传输失败的规避方法的流程示意图；
图7为本申请实施例提供的一种基于接收端RLC反馈的RLC SDU传输状态错误进行的调整的流程示意图；
图8为本申请实施例提供的一种基于接收端MAC层反馈的RLC SDU传输状态错 误进行调整的流程示意图；
图9为本申请实施例提供的一种基于接收端PDCP层反馈的PDCP SDU传输状态错误进行调整的流程示意图；
图10为本申请实施例提供的另一种连续数据包传输失败的规避方法的流程示意图；
图11为本申请实施例提供的另一种连续数据包传输失败的规避方法的流程示意图；
图12为本申请实施例提供的另一种连续数据包传输失败的规避方法的流程示意图；
图13为本申请实施例提供的另一种连续数据包传输失败的规避方法的流程示意图；
图14为本申请实施例提供的另一种连续数据包传输失败的规避方法的流程示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述。需要说明的是，在不冲突的情况下，本申请各个实施例中的技术方案或特征可以相互组合。
本申请实施例中的“一个”意味着单个个体，并不代表只能是一个个体，不能应用于其他个体中。例如，本申请实施例中的“一个终端设备”指的是针对某一个终端设备，并不意味着只能应用于一个特定的终端设备。本申请中，术语“系统”可以和“网络”相互替换使用。
本申请中的“一个实施例”(或“一个实现”)或“实施例”(或“实现”)的引用意味着连同实施例描述的特定特征、结构、特点等包括在至少一个实施例中。因此，说明书的各个位置中出现的“在一个实施例中”或“在实施例中”，并不表示都指代相同实施例。
进一步地，本申请实施例中的“A和/或B”和“A和B中至少一个”的情况下使用术语“和/或”和“至少一个”包括三种方案中的任一种，即，包括A但不包括B的方案、包括B不包括A的方案、以及两个选项A和B都包括的方案。作为另一示例，在“A、B、和/或C”和“A、B、和/或C中至少一个”的情况下，这样的短语包括六种方案中的任一种，即，包括A但不包括B和C的方案、包括B不包括A和C的方案、包括C但不包括A和B的方案，包括A和B但不包括C的方案，包括B和C但不包括A的方案，包括A和C但不包括B的方案，以及三个选项A、B和C都包括的方案。如本领域和相关领域普通技术人员所容易理解的，对于其他类似的描述，本申请实施例均可以按照上述方式理解。
图1示出了无线设备与无线通信系统的通信示意图。所述无线通信系统可以是应用各种无线接入技术(radio access technology，RAT)的系统，例如码分多址(code  division multiple access，CDMA)、时分多址(time division multiple access，TDMA)、频分多址(frequency division multiple access，FDMA)、正交频分多址(orthogonal frequency-division multiple access，OFDMA)、或单载波频分多址(single carrier FDMA，SC-FDMA)和其它系统等。例如无线通信系统可以是长期演进(long term evolution，LTE)系统，CDMA系统，宽带码分多址(wideband CDMA，WCDMA)系统，全球移动通信(global system for mobile communications，GSM)系统，无线局域网(wireless local area network,WLAN)系统，新空口(New Radio,NR)系统，各种演进或者融合的系统，以及面向未来的通信技术的系统。本申请实施例描述的系统架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
为简明起见，图1中示出了一个网络设备102(例如接入网设备)，以及两个无线设备104(例如终端设备)的通信。一般而言，无线通信系统可以包括任意数目的网络设备以及终端设备。无线通信系统还可以包括一个或多个核心网设备或用于承载虚拟化网络功能的设备等。所述接入网设备102可以通过一个或者多个载波为无线设备提供服务。本申请中又将接入网设备和终端设备统称为无线装置。
本申请中，所述接入网设备102是一种部署在无线接入网中用以为终端设备提供无线通信功能的装置。所述接入网设备可以包括各种形式的宏基站(base station，BS)，微基站(也称为小站)，中继站，或接入点等。在采用不同的无线接入技术的系统中，具备无线接入功能的设备的名称可能会有所不同，例如，在LTE系统中，称为演进的节点B(evolved NodeB，eNB或者eNodeB),在第三代(3rd generation，3G)系统中，称为节点B(Node B)等。为方便描述，为方便描述，本申请中，简称为接入网设备，有时也称为基站。
本申请实施例中所涉及到的无线设备可以包括各种具有无线通信功能的手持设备、车载设备、可穿戴设备、计算设备或连接到无线调制解调器的其它处理设备。所述无线设备可以称为终端设备，也可以称为移动台(mobile station,简称MS)，终端(terminal)，用户设备(user equipment，UE)等。所述无线设备可以是包括用户单元(subscriber unit)、蜂窝电话(cellular phone)、智能电话(smart phone)、无线数据卡、个人数字助理(personal digital assistant，PDA)电脑、平板型电脑、调制解调器(modem)或调制解调器处理器(modem processor)、手持设备(handheld)、膝上型电脑(laptop computer)、上网本、无绳电话(cordless phone)或者无线本地环路(wireless local loop，WLL)台、蓝牙设备、机器类型通信(machine type communication,MTC)终端等。为方便描述，本申请中，简称为终端设备或UE。
无线设备可以支持用于无线通信的一种或多种无线技术，例如5G,LTE,WCDMA,CDMA,1X,时分-同步码分多址(Time Division-Synchronous Code Division Multiple Access,TS-SCDMA),GSM,802.11等等。无线设备也可以支持载波聚合技术。
多个无线设备可以执行相同或者不同的业务。例如，移动宽带业务，增强移动宽带(Enhanced Mobile Broadband，eMBB)业务，终端设极高可靠极低时延通信(Ultra-Reliable and Low-Latency Communication，URLLC)业务等等。
进一步地，上述接入网设备102的一种可能的结构示意图可以如图2所示。该接入网设备102能够执行本申请实施例提供的方法。其中，该接入网设备102可以包括：控制器或处理器201(下文以处理器201为例进行说明)以及收发器202。控制器/处理器201有时也称为调制解调器处理器(modem processor)。调制解调器处理器201可包括基带处理器(baseband processor，BBP)(未示出)，该基带处理器处理经数字化的收到信号以提取该信号中传达的信息或数据比特。如此，BBP通常按需或按期望实现在调制解调器处理器201内的一个或多个数字信号处理器(digital signal processor，DSP)中或实现为分开的集成电路(integrated circuit，IC)。
收发器202可以用于支持接入网设备102与终端设备之间收发信息，以及支持终端设备之间进行无线电通信。所述处理器201还可以用于执行各种终端设备与其他网络设备通信的功能。在上行链路，来自终端设备的上行链路信号经由天线接收，由收发器202进行调解，并进一步处理器201进行处理来恢复终端设备所发送的业务数据和/或信令信息。在下行链路上，业务数据和/或信令消息由终端设备进行处理，并由收发器202进行调制来产生下行链路信号，并经由天线发射给UE。所述接入网设备102还可以包括存储器203，可以用于存储该接入网设备102的程序代码和/或数据。收发器202可以包括独立的接收器和发送器电路，也可以是同一个电路实现收发功能。所述接入网设备102还可以包括通信单元204，用于支持所述接入网设备102与其他网络实体进行通信。例如,用于支持所述接入网设备102与核心网的网络设备等进行通信。
可选的，接入网设备还可以包括总线。其中，收发器202、存储器203以及通信单元204可以通过总线与处理器201连接。例如，总线可以是外设部件互连标准(Peripheral Component Interconnect，PCI)总线或扩展工业标准结构(Extended Industry Standard Architecture，EISA)总线等。所述总线可以包括地址总线、数据总线、以及控制总线等。
图3为上述无线通信系统中，终端设备的一种可能的结构示意图。该终端设备能够执行本申请实施例提供的方法。该终端设备可以是两个终端设备104中的任一个。所述终端设备包括收发器301，应用处理器(application processor)302，存储器303和调制解调器处理器(modem processor)304。
收发器301可以调节(例如，模拟转换、滤波、放大和上变频等)该输出采样并生成上行链路信号，该上行链路信号经由天线发射给上述实施例中所述的基站。在下行链路上，天线接收接入网设备发射的下行链路信号。收发器301可以调节(例如，滤波、放大、下变频以及数字化等)从天线接收的信号并提供输入采样。
调制解调器处理器304有时也称为控制器或处理器，可包括基带处理器(baseband processor,BBP)(未示出)，该基带处理器处理经数字化的收到信号以提取该信号中传达的信息或数据比特。BBP通常按需或按期望实现在调制解调器处理器304内的一个或多个数字中或实现为分开的集成电路(IC)。
在一个设计中，调制解调器处理器(modem processor)304可包括编码器3041，调制器3042，解码器3043，解调器3044。编码器3041用于对待发送信号进行编码。例如，编码器3041可用于接收要在上行链路上发送的业务数据和/或信令消息，并对 业务数据和信令消息进行处理(例如，格式化、编码、或交织等)。调制器3042用于对编码器3041的输出信号进行调制。例如，调制器可对编码器的输出信号(数据和/或信令)进行符号映射和/或调制等处理，并提供输出采样。解调器3044用于对输入信号进行解调处理。例如，解调器3044处理输入采样并提供符号估计。解码器3043用于对解调后的输入信号进行解码。例如，解码器3043对解调后的输入信号解交织、和/或解码等处理，并输出解码后的信号(数据和/或信令)。编码器3041、调制器3042、解调器3044和解码器3043可以由合成的调制解调处理器304来实现。这些单元根据无线接入网采用的无线接入技术来进行处理。
调制解调器处理器304从应用处理器302接收可表示语音、数据或控制信息的数字化数据，并对这些数字化数据处理后以供传输。所属调制解调器处理器可以支持多种通信系统的多种无线通信协议中的一种或多种，例如LTE,新空口，通用移动通信系统(Universal Mobile Telecommunications System，UMTS)，高速分组接入(High Speed Packet Access，HSPA)等等。可选的，调制解调器处理器304中也可以包括一个或多个存储器。
可选的，该调制解调器处理器304和应用处理器302可以是集成在一个处理器芯片中。存储器303用于存储用于支持所述终端设备通信的程序代码(有时也称为程序，指令，软件等)和/或数据。
需要说明的是，该存储器203或存储器303可以包括一个或多个存储单元，例如，可以是用于存储程序代码的处理器201或调制解调器处理器304或应用处理器302内部的存储单元，或者可以是与处理器201或调制解调器处理器304或应用处理器302独立的外部存储单元，或者还可以是包括处理器201或调制解调器处理器304或应用处理器302内部的存储单元以及与处理器201或调制解调器处理器304或应用处理器302独立的外部存储单元的部件。
处理器201和调制解调器处理器301可以是相同类型的处理器，也可以是不同类型的处理器。例如可以实现在中央处理器(Central Processing Unit，CPU)，通用处理器，数字信号处理器(Digital Signal Processor，DSP)，专用集成电路(Application-Specific Integrated Circuit，ASIC)，现场可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件、其他集成电路、或者其任意组合。处理器201和调制解调器处理器301可以实现或执行结合本申请实施例公开内容所描述的各种示例性的逻辑方框，模块和电路。所述处理器也可以是实现计算功能器件的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合或者片上系统(system-on-a-chip，SOC)等等。
本领域技术人员能够理解，结合本申请所公开的诸方面描述的各种解说性逻辑块、模块、电路和算法可被实现为电子硬件、存储在存储器中或另一计算机可读介质中并由处理器或其它处理设备执行的指令、或这两者的组合。作为示例，本文中描述的设备可用在任何电路、硬件组件、IC、或IC芯片中。本申请所公开的存储器可以是任何类型和大小的存储器，且可被配置成存储所需的任何类型的信息。为清楚地解说这种可互换性，以上已经以其功能性的形式一般地描述了各种解说性组件、框、模块、电路和步骤。此类功能性如何被实现取决于具体应用、设计选择和/或加诸于整体系统上 的设计约束。本领域技术人员可针对每种特定应用以不同方式来实现所描述的功能性，但此类实现决策不应被解读为致使脱离本申请的范围。
现有通信技术包括5G技术在设计过程中，并没有特别考虑连续应用层数据包传输的可靠性，现有技术通常只是针对一个数据包进行传输可靠性保证的设计，通过重传机制让该数据包的传输达到一定的可靠性。本申请实施例针对应用层不允许连续2个数据包出错的特点，提出了一种根据前一个数据包传输状态来动态调整后一个数据包传输可靠性的方法。下面将结合附图，对本申请实施例所提供的方案进行更为详细的描述。
图4为本申请实施例提供的一种连续数据包传输失败的规避方法的流程示意图，其可以应用于如图1所示的网络架构以及图2、图3所示的终端设备和接入网设备。需要说明的是，本申请实施例中的发送端可以是终端设备也可以是接入网设备，当发送端为终端设备时，接收端可以为接入网设备；当发送端为接入网设备时，接收端可以为终端设备，但本申请并不局限于此。
步骤401：发送端的接入层第一实体维护所述接入层第一实体的前一个数据包的传输状态。
这里说的数据包是可以是接入层第一实体的业务数据单元(service data unit，SDU)或协议数据单元(protocol data unit，PDU)。
可选的，数据包是应用层的数据包，到了通信层会作为通信层的初始业务数据单元(service data unit，SDU)。传输状态包括传输成功或传输失败。
可选的，发送端的接入层第一实体可以是以下至少一种：业务数据适配协议(service data adaptation protocol，SDAP)层；分组数据汇聚协议(packet data convergence protocol，PDCP)层；无线链路控制(radio link control，RLC)层；媒体接入控制(media access control，MAC)层；无线资源控制层(radio resource control，RRC)层；物理(physical，PHY)层。
以图5为例，例如，应用层的数据包作为SDAP SDU进行传输，加上SDAP头(header)后封装成SDAP PDU递交给PDCP层，PDCP层收到的SDAP PDU即作为PDCP SDU进行传输，加上PDCP头(header)后封装成PDCP协议数据单元(protocol data unit，PDU)递交给下一层RLC层，RLC收到的PDCP PDU即为RLC SDU，RLC SDU加上RLC header后封装成RLC PDU。RLC层由于有分段功能，因此1个RLC SDU可能被分段成多个RLC PDU进行传输。多个逻辑信道的RLC PDU在MAC层复用组成了一个MAC PDU。每个RLC PDU在MAC层看来都是一个MAC SDU。
可选的，所述发送端的接入层实体根据以下至少一种信息维护所述接入层实体的前一个数据包的传输状态：
所述发送端接入层第一实体维护的定时器超时且前一个数据包还未成功传输，则认为前一个数据包的传输状态为传输失败，否则认为前一个数据包传输状态为传输成功；
接收端接入层第一实体发送给发送端接入层的指示信息，用于指示所述发送端接入层第一实体的前一个数据包是传输成功或传输失败；
发送端接入层第二实体发送给发送端接入层第一实体的指示信息，用于指示所述发送端接入层第一实体的前一个数据包是传输成功或传输失败；
接收端接入层第二实体发送给发送端接入层的指示信息，用于指示所述发送端接入层第一实体的前一个数据包是传输成功或传输失败；
发送端接入层第一实体或第二实体根据当前数据包的序号，若接收的当前数据包的序号与前一个数据包的序号不连续，判断前一个数据包传输失败；
发送端接入层第一实体或第二实体根据QoS信息获知数据包的周期，若在前一个周期内没有数据包到达，判断前一个数据包传输失败；
发送端非接入层或应用层给发送端接入层的指示信息，用于指示所述发送端接入层第一实体的前一个数据包是传输成功或传输失败。
需要说明的是，本申请实施例中的接入层第一实体、接入层第二实体可以是非接入层实体或者其他协议层实体，本申请并不限定。
步骤402：如果所述前一个数据包的传输状态为传输失败，所述发送端调整当前数据包的传输参数。其中，传输参数可以是无线资源配置参数。
可选的，所述传输参数包括以下至少一项：调制和编码方案(modulation and coding scheme，MCS)；最大混合自动重传(hybrid automatic repeat request,HARQ)次数；最大自动重传(automatic repeat request,ARQ)次数；传输资源的周期；传输资源的位置；传输资源的大小；传输资源的类型；逻辑信道优先级；无线承载优先级；无线链路控制传输模式(RLC AM或UM或TM)；传输的载波数；无线承载的类型；无线承载的功能(例如是否采用重复传输，采用单连接还是双连接还是多连接)；发送功率。
其中，MCS调制编码表是802.11n为表征通讯速率而提出的一种表示形式，MCS将影响通讯速率的因素作为表的列，将MCS索引作为行，形成一张速率表，因此，每一个MCS索引对应了一组参数下的物理传输速率。
最大混合自动重传次数表示同一个MAC PDU在MAC层被传输的最大次数。
最大自动重传次数表示同一个RLC PDU在RLC层被传输的最大次数。
传输资源的周期可以包括例如SPS(semi-persistent scheduling，半静态调度)资源的周期，也即相邻2个SPS资源的时域上的间隔。例如原本SPS周期是2，后续数据包的SPS周期是1。
传输资源的位置可以包括例如SPS资源的时域和频域的起始位置和终止位置。具体地，频域位置可以是载波索引或子载波索引或BWP(bandwidth part，带宽)索引，时域位置可以是符号索引、时隙号、子帧号、帧号、超帧号等。
传输资源的大小可以包括SPS资源的大小、在时域上占用的时域单位的数量或频域单位的数量。具体地，时域单位可以是符号、时隙、子帧、帧、超帧等；频域单位可以是载波、子载波、BWP等。
传输资源的类型可以包括例如SPS资源或GrantFree(免授权)资源或动态调度资源。
逻辑信道优先级用于指示每个逻辑信道在MAC层进行复用时的优先级。不同逻辑信道可以具有相同的优先级。
无线链路控制层RLC层有三种传输模式，分别是RLC AM、RLC UM和RLC TM。
其中，RLC AM(acknowledged mode)：通过出错检测和重传，提供了一种可靠的传输服务。该模式提供了所有的RLC功能。
RLC UM(unacknowledged mode)：该模式提供除重传和重分段外的所有RLC功能，因此提供了一种不可靠的传输服务。
RLC TM(transparent mode)：该模式可以认为是空的RLC，不对RLC SDU做任何处理，没有添加RLC头(header)，因为这种模式下只提供数据的透传(passthrough)功能。
无线承载的类型包括数据无线承载(data radio bearer，DRB)和信令无线承载(signaling radio bearer，SRB)。进一步，无线承载的类型还可以包括不同的DRB ID和SRB ID。
发送功率是指发送端在传输一个MAC PDU采用的发送功率。
图6为本申请实施例提供的一种连续数据包传输失败的规避方法的流程示意图，其可以应用于如图1所示的网络架构以及图2、图3所示的终端设备和接入网设备。需要说明的是，本申请实施例中的发送端可以是终端设备也可以是接入网设备，当发送端为终端设备时，接收端可以为接入网设备；当发送端为接入网设备时，接收端可以为终端设备，但本申请并不局限于此。
步骤601：发送端的接入层第一实体获取所述接入层第一实体的前n个数据包的传输状态。
这里说的数据包可以是接入层第一实体的业务数据单元(service data unit，SDU)或协议数据单元(protocol data unit，PDU)。其中具体可以是来自应用层的数据包，到了通信层作为通信层的初始业务数据单元(service data unit，SDU)。传输状态包括传输成功或传输失败。
可选的，发送端的接入层第一实体可以是以下至少一种：业务数据适配协议(service data adaptation protocol，SDAP)层；分组数据汇聚协议(packet data convergence protocol，PDCP)层；无线链路控制(radio link control，RLC)层；媒体接入控制(media access control，MAC)层；无线资源控制层(radio resource control，RRC)层；物理(physical，PHY)层。
步骤602：如果所述前n个数据包中存在m个数据包的传输状态为传输失败，发送端调整当前数据包的传输参数。
步骤602中的传输参数与步骤402中的传输参数相同,再次不再赘述。
需要说明的是，发送端的接入层第一实体在获取到接入层第一实体的前n个数据包的传输状态之后，将判断该前n个数据包中是否存在m个数据包的传输状态为传输失败，其中，n为正整数，m为小于或等于n的正整数。m个数据包可以为连续的数据包，也可以为非连续的数据包，当m个数据包为连续的数据包时，m≥2。若发送端确定出前n个数据包中存在m个数据包的传输状态为传输失败，则所述发送端调整当前数据包(第n+1个数据包)的传输参数。
可选的，所述发送端的接入层实体根据以下至少一种获取所述接入层实体的前n个数据包的传输状态：
(1)发送端接入层第一实体维护有多个计数器(例如第一计数器和第二计数器)。其中，第一计数器用于统计接入层第一实体的n个数据包，第二计数器用于统计n个数据包中累计的传输失败的数据包个数。在本申请的一个实施方式中，第一计数器和第二计数器的初始值为0。为第二计数器设置一个阈值，该阈值可以由核心网设备或接入网设备配置，或者，该阈值也可以从终端设备的应用层或非接入层获得。发送端接入层的第一实体获取每一个数据包的传输状态，获取方法同步骤401中获取前一个数据包的传输状态的获取方法，在此不再赘述。每获取到接入层第一实体的一个数据包时，第一计数器的值+1；当发送端接入层的第一实体获取到一个数据包的传输状态为传输失败时，第二计数器的值+1。当第二计数器的值大于或者等于阈值时，例如，设置阈值为m，则认为发送端接入层实体的前n个数据包中存在m个数据包的传输状态为传输失败，发送端需要调整当前数据包的传输参数。当第一计数器的值等于n，且第二计数器的值小于阈值m时，则发送端仍然保持当前数据包的传输参数。
(2)接收端接入层第一实体发送给发送端接入层指示信息，用于指示所述发送端接入层第一实体的前n个数据包是否存在m个数据包传输失败。
(3)发送端接入层第二实体发送给发送端接入层第一实体的指示信息，用于指示所述发送端接入层第一实体的前n个数据包是否存在m个数据包传输失败。
(4)接收端接入层第二实体发送给发送端接入层的指示信息，用于指示所述发送端接入层第一实体的前n个数据包是否存在m个数据包传输失败。
(5)发送端接入层第一实体或第二实体可以接收接收端接入层第一实体或发送端接入层第二实体的指示信息，所述指示信息中包括当前已传输的数据包的序号和每个序号对应的数据包的传输状态。发送端接入层第一实体维护有计数器，计数器用于统计累计的传输失败的数据包个数，计数器的初始值为0。若接收的当前数据包的序号与前一个数据包的序号不连续，则计数器的值+1。在本申请的一个实施例中，设置计数器的阈值为m，当计数器的值大于或等于阈值m时，则认为发送端接入层实体的前n个数据包中存在m个数据包的传输状态为传输失败。
(6)发送端非接入层或应用层给发送端接入层的指示信息，用于指示所述发送端接入层第一实体的前n个数据包是否存在m个数据包传输失败。
需要说明的是，本申请实施例中的接入层第一实体、接入层第二实体可以是非接入层实体或者其他协议层实体，本申请并不限定。
可选的，当发送端为终端设备时，n可以由接入网设备或核心网设备配置；或者n可以从终端设备的应用层或非接入层获得。
在本申请的一个实施例中，当发送端为终端设备时，可以根据应用层的生存时间(survival time)T和应用层业务(service)的发送周期(cycle time或transfer time)t计算获得n。例如，n＝T/t。若T/t的结果不能整除，则可以向上或向下取整。其中T，t由接入网设备或核心网设备配置或从终端设备的应用层或非接入层获得。此时，m可以由接入网设备或核心网设备配置，或者从终端设备的应用层或非接入层获得。
可选的，当发送端为接入网设备时，n可以由核心网设备配置或由终端设备上报获得。
在本申请的另一个实施例中，当发送端为接入网设备时，n同样可以根据应用层 的生存时间T和应用层业务的发送周期t计算得来。例如，n＝T/t。同样地，若不能整除，则可以向上或向下取整。其中T，t由核心网设备配置或由终端设备上报获得。此时，m可以由核心网设备配置或由终端设备上报获得。
在本申请的另一个实施例中，m同样可以根据应用层的生存时间T和应用层业务的发送周期t计算得来。例如，m＝T/t。同样地，若不能整除，则可以向上或向下取整。其中T，t由核心网设备配置或由终端设备上报获得。此时，n可以由核心网设备配置或接入网设备配置或由终端设备上报获得或从终端设备的应用层或非接入层获得。
需要说明的是，本申请的实施例并不局限于图6所描述的实施例。例如，根据本申请实施例提供的方法，发送端的接入层第一实体可以获取接入层第一实体的每个数据包的传输状态；在预设的时间内，当获取的接入层第一实体的数据包中存在s个数据包的传输状态为传输失败，则发送端调整当前数据包的传输参数。其中s为正整数。
再例如，根据本申请实施例提供的方法，发送端的接入层第一实体可以获取接入层第一实体的向前的至少k个数据包的传输状态；当获取的接入层第一实体的数据包中存在连续k个数据包的传输状态为传输失败，则发送端调整当前数据包的传输参数。其中，k为正整数，且k≥2。
可选的，k可以为2、3或4。即当获取的接入层第一实体的数据包中存在连续的2个、3个或者4个数据包的传输状态为传输失败，则发送端调整当前数据包的传输参数。即当k＝2时，发送端调整当前第3个数据包的传输参数；当k＝3时，发送端调整当前第4个数据包的传输参数；当k＝4时，发送端调整当前第5个数据包的传输参数。
再例如，根据本申请实施例提供的方法，发送端的接入层第一实体获取接入层实体至少前x个数据包的传输状态；当获取的前x个数据包的传输状态为传输失败，所述发送端调整当前数据包的传输参数。其中，x为正整数，且x≥2。
可选的，x可以为2、3或4。即当获取的接入层第一实体的前2个或者前3个或者前4个数据包的传输状态为传输失败时，发送端调整当前数据包的传输参数。即当x＝2时，发送端的接入层第一实体传输序列号PDCP PDU为#i的数据包时，判断之前的2个数据包，即序列号为PDCP PDU #(i-1)、PDCP PDU #(i-2)的数据包的传输状态；若这两个序列号数据包的传输状态都是传输失败，则发送端调整PDCP PDU #i的数据包的传输参数。当x＝3或x＝4时与x＝2的情况相类似，在此不再赘述。
实施例一：基于接收端RLC反馈的RLC SDU传输状态的维护及传输参数调整
图7示出了本申请实施例提供的一种基于接收端RLC反馈的RLC SDU传输状态错误进行的调整的流程示意图。以下以接收端为接入网设备为例，包括如下步骤(但本申请并不限于此)：
步骤S701：可选的，接入网设备在无线承载建立过程中通过该承载对应的服务质量(quality of service，QoS)信息判断是否存在连续数据包传输可靠性的需求。如果存在连续数据包传输可靠性的需求，则配置两套资源参数，这两套资源参数至少在RadioResourceConfigDedicated information element的内容中有差异，具体可以是最大HARQ传输次数或ARQ传输次数，MCS等，但本申请并不局限于此。QoS信息可以 从核心网获得，或者从终端设备获得。在以下步骤中，State_RLC_1是发送端用于维护前一个数据包的传输状态的变量，State_RLC_2是发送端用于维护当前数据包传输状态的变量。
步骤S702：终端设备的RLC实体从上层(例如PDCP层)收到一个RLC SDU1，将RLC SDU1对应的传输状态变量State_RLC_1设置为False。
步骤S703：假设RLC SDU1由于底层调度资源有限而被分段传输，分别封装为RLC PDU1和RLC PDU2。RLC PDU2的RLC header中的轮询(polling)域被置位。
步骤S704：假设RLC PDU1传输失败，RLC PDU2传输成功。接入网设备的RLC实体收到RLC PDU2时，因为polling置位，接入网设备的RLC实体会生成一个状态报告(status report)，其中包含了每个RLC PDU(至少包括RLC PDU1和RLC PDU2)是否成功接收的信息。
步骤S705：终端设备收到接入网设备发送的状态报告，获知RLC PDU1传输失败，因此判断RLC SDU1传输失败，维持State_RLC_1为False。
可选的，RLC层需要将RLC SDU1的传输状态为失败指示给其他协议层，例如RRC层或MAC层或PHY层或PDCP层，各个协议层收到指示后将本层对应的传输参数置为第二资源参数。
步骤S706：终端设备的RLC实体收到RLC SDU2，因为State_RLC_1为False，因此针对RLC SDU2，采用第二资源参数进行传输。将对应的RLC SDU2的初始传输状态变量State_RLC_2设置为False。
步骤S707：假设RLC SDU 2在RLC层没有分段，其直接封装成RLC PDU3递交给底层进行传输，其中polling域被置位。
步骤S708：假设RLC PDU3传输失败，接入网设备的RLC实体收到RLC PDU3时因为polling域被置位，生成状态报告，其中包含了每个RLC PDU(至少包括RLC PDU3)是否成功接收的信息。
步骤S709：终端设备收到接入网设备发送的状态报告，获知RLC PDU3传输成功，因此判断RLC SDU2传输成功，将State_RLC_2置为True。
可选的，RLC层需要将RLC SDU 2的传输状态为成功指示给其他协议层，例如RRC层或MAC层或PHY层或PDCP层，各个协议层收到指示后将本层对应的传输参数置为第一资源参数。
实施例二：基于接收端MAC层反馈的RLC SDU传输状态的维护及传输参数调整
图8示出了本申请实施例提供的一种基于接收端MAC层反馈的RLC SDU传输状态错误进行调整的流程示意图。以下以接收端为接入网设备为例，包括如下步骤(但本申请并不限于此)：
其中，步骤801和步骤802与图7中的步骤701和步骤702相同，在此不再赘述。
步骤803：假设RLC SDU1没有分段，封装为RLC PDU1。将RLC PDU1递交给MAC层传输。在MAC层被封装为MAC PDU1。
步骤804：假设MAC PDU1连续传输x次失败，x为正整数。MAC层会把该信息指示给RLC PDU1所在的RLC实体，RLC实体判断RLC SDU1传输失败，维持 State_RLC_1为False。
可选的，x可以是最大HARQ传输次数。MAC层在MAC PDU1在达到最大HARQ传输次数后指示RLC层RLC PDU1传输失败。
可选的，RLC层需要将RLC SDU1的传输状态为失败指示给其他协议层，例如RRC层或MAC层或PHY层或PDCP层，各个协议层收到指示后将本层对应的传输参数置为第二资源参数。
步骤805：终端设备的RLC实体从上层收到一个RLC SDU2，将RLC SDU2对应的传输状态变量State_RLC_2设置为False。
步骤806：假设RLC SDU2没有分段，封装为RLC PDU2。将RLC PDU2递交给MAC层传输。在MAC层被封装为MAC PDU2。
步骤807：假设MAC PDU2传输成功，MAC层会把该信息指示给RLC PDU2所在的RLC实体，RLC实体判断RLC SDU2传输成功，维持State_RLC_2为True。
可选的，RLC层需要将RLC SDU2的传输状态为成功指示给其他协议层，例如RRC层或MAC层或PHY层或PDCP层，各个协议层收到指示后将本层对应的传输参数置为第一套参数。
可选的，除了上述RLC SDU的传输状态的指示方法，还包括其他指示方法，例如：
发送端(上行以终端设备为例)的每一个RLC实体维护该实体中每一个RLC SDU的传输状态，例如RLC实体针对RLC层序列号为SN的RLC SDU，维护一个变量State_RLC_SN。
可选的，实施例一和实施例二中变量State_RLC_SN置为False的条件包含以下至少一项：
1)初始置位为False，例如从PDCP层获得对应SN的RLC SDU或将该RLC SDU对应的第一个RLC PDU递交给MAC层；
2)从对端RLC实体收到的状态中指示该RLC SDU所对应的所有RLC PDU中至少有一个接收失败；
可选的，发送端的RLC实体按照发送RLC SDU的数量(例如，1个)将polling域置位，即在每一个RLC SDU所对应的最后一个RLC PDU发送时将polling域置位，接收端的RLC实体每接收到一个RLC SDU就生成一个状态报告。
3)MAC层指示该RLC SDU对应的所有RLC PDU所在的MAC PDU至少有一个在连续n次HARQ传输中未传输成功，n为正整数，由接入网设备的RRC信令配置。可选的，n可以等于最大HARQ次数。
4)PDCP层指示该RLC SDU或其对应的PDCP SDU/PDU未传输成功；
5)RLC层在一个定时器超时范围内没有收到包含了该SN对应的RLC SDU传输成功的状态报告
6)直接从接收端的某一层信令(RLC控制PDU或RRC信令或MAC CE或DCI)中获得State_RLC_SN的值为False。终端设备在RLC层没有成功解码出某一个SN对应的RLC SDU时(例如，reordering定时器超时或者对SDU内容无法识别等原因)，生成包含Stae_RLC_SN值为False的信令，该信令可以是RRC信令或MAC控制元 素(control element，CE)或RLC控制PDU或下行控制信息(downlink control information，DCI)。
可选的，实施例一和实施例二中变量State_RLC_SN置为True的条件包含以下至少一项：
1)对端的RLC实体反馈的状态报告显示该RLC SDU对应的RLC PDU全部接收成功，可选的，发送端的RLC实体按照发送RLC SDU的数量(例如1个)将polling域置位，即在每一个RLC SDU所对应的最后一个RLC PDU发送时将polling域置位；
2)MAC层指示该RLC SDU对应的RLC PDU所在的MAC PDU全部传输成功，MAC层向每个逻辑信道对应的RLC实体反馈其每个RLC PDU的传输状态；
3)PDCP层指示该RLC SDU或其对应的PDCP SDU/PDU传输成功；
4)直接从接收端的某一层信令(PDCP控制PDCU或RLC控制PDU或MAC CE或DCI或RRC信令)中获得State_RLC_SN的值为True。
接收端在RLC层成功解码出某一个SN对应的RLC SDU时，生成包含State_RLC_SN值为True的信令，该信令可以是RRC信令或MAC CE或RLC控制PDU或DCI。
可选的，RLC实体将每个RLC SDU的传输状态指示给其他层，例如RRC或SDAP或PDCP或MAC或PHY层。
在State_RLC_SN状态为False，若序列号为SN+1的RLC SDU要发送时，发送端采用第二资源参数进行传输,包括：
1)PDCP层或RLC层激活SN+1的RLC SDU所在的承载或逻辑信道的复用(duplication)
2)按照预配置的参数(例如，捆绑传输时间间隔(transmission time interval bundling，TTI bundling)数，调制和编码方案；最大混合自动重传HARQ次数；最大自动重传ARQ次数；传输资源的周期；传输资源的位置；传输资源的大小；传输资源的类型；逻辑信道优先级；无线承载优先级；无线链路控制传输模式；传输的载波数；无线承载的类型；无线承载的功能等)传输SN+1的RLC SDU，该参数由RRC信令配置，在序号为SN的RLC SDU传输失败时激活。
实施例三：
图9为图7类似，示出了本申请实施例提供的一种基于接收端PDCP层反馈的PDCP SDU传输状态错误进行调整的流程示意图。发送端(上行以终端设备为例)每一个PDCP实体维护该实体中每一个PDCP SDU/PDU的传输状态，例如PDCP实体针对PDCP层序列号为SN的PDCP SDU/PDU，维护一个变量State_PDCP_SN。
可选的，变量State_PDCP_SN置为False的条件包含以下至少一项：
1)初始置位为False，例如从上层(SDAP或IP层或应用层)获得一个PDCP SDU或将该PDCP SDU对应的PDCP PDU(其序列号为SN)递交给RLC层；
2)从对端PDCP实体收到状态报告中显示该PDCP SDU/PDU传输失败，发送端 的PDCP实体在每一个PDCP PDU的header中将polling域置位，接收端PDCP实体每接收到一个PDCP PDU就生成一个状态报告；
3)RLC层指示PDCP层当前PDCP PDU传输失败；
4)PDCP层针对该PDCP SDU的discardTimer超时；
5)直接从对端的某一层信令(PDCP控制PDU或RRC信令或MAC CE或DCI)中获得State_PDCP_SN的值为False；
6)非接入(non-access stratum，NAS)层或者应用层或者IP层的指示
可选的，变量State_PDCP_SN置为True的条件包含以下至少一项：
1)接收端的PDCP实体反馈的状态报告显示该PDCP SDU/PDU传输成功，
2)RLC层指示该PDCP SDU/PDU传输成功
3)直接从对端的某一层信令(PDCP控制PDU或MAC CE或DCI或RRC信令)中获得State_PDCP_SN的值为True。接收端在PDCP层成功解码出某一个SN对应的PDCP SDU时，生成包含Stae_PDCP_SN值为True的信令，该信令可以是RRC信令或MAC CE或PDCP控制PDU或DCI；
4)NAS层或者应用层或者IP层的指示信息。
可选的，PDCP实体将每个PDCP SDU/PDU的传输状态指示给其他层，例如RRC或SDAP或RLC或MAC或PHY层。
类似地，在State_PDCP_SN状态为False，若序列号为SN+1的PDCP SDU要发送时，发送端采用第二资源参数进行传输,包括：
1、PDCP层或RLC层激活SN+1的PDCP SDU所在的承载或逻辑信道的复用(duplication)。
2、按照预配置的参数(可包括TTI bundling数，调制和编码方案；最大混合自动重传HARQ次数；最大自动重传ARQ次数；传输资源的周期；传输资源的位置；传输资源的大小；传输资源的类型；逻辑信道优先级；无线承载优先级；无线链路控制传输模式；传输的载波数；无线承载的类型；无线承载的功能等)传输SN+1的PDCP SDU，该参数由RRC信令配置，在序列号为SN的PDCP SDU传输失败时激活。
实施例四：
图10为本申请实施例提供的另一种连续数据包传输失败的规避方法的流程示意图。以发送端为接入网设备为例，具体包括如下步骤：
步骤1001：接入网设备从核心网设备获得数据包的周期，其中，接入网设备在每个周期内都应该接收到一个数据包。
步骤1002：接入网设备在周期1内收到数据包1，按照传输参数1(第一资源参数)来传输，假设在空口传输成功。
步骤1003：接入网设备将数据包1发送给终端设备
步骤1004：核心网设备向接入网设备发送数据包2，但接入网设备在周期2内没有收到数据包2，则接入网设备数据包2传输失败(即数据包2丢包)。
步骤1005：接入网设备将数据包2的传输状态设置为传输失败，并调整数据包3的传输参数为传输参数2(第二资源参数)。
步骤1006：接入网设备在周期3内接收核心网设备发送的数据包3。
步骤1007：接入网设备将数据包3发送给终端设备。
实施例五：
图11为本申请实施例提供的另一种连续数据包传输失败的规避方法的流程示意图。以发送端为终端设备为例，具体包括如下步骤：
步骤1101：发送端终端设备的PDCP层发送PDCP SDU1给接入网设备。
步骤1102：终端设备从NAS层或应用层获得指示PDCP SDU1传输错误，终端设备将PDCP SDU1对应的传输状态设置为传输错误。终端设备调整PDCP SDU2的传输参数为传输参数2(第二资源参数)，来进行PDCP SDU2的传输。
步骤1103：终端设备使用传输参数2向接入网设备传输PDCP SDU2。
实施例六：
图12为本申请实施例提供的另一种连续数据包传输失败的规避方法的流程示意图。以发送端为终端设备为例，具体包括如下步骤：
步骤1201：发送端终端设备的PDCP层发送PDCP SDU1给接入网设备，同时启动定时器。
步骤1202：终端设备在定时器超时前未获得PDCP SDU1成功传输的指示信息。终端设备将PDCP SDU1对应的传输状态设置为传输错误，调整PDCP SDU2的传输参数为传输参数2(第二资源参数)，来进行PDCP SDU2的传输。
步骤1203：终端设备使用传输参数2向接入网设备传输PDCP SDU2。
实施例七：
图13为本申请实施例提供的另一种连续数据包传输失败的规避方法的流程示意图。以发送端为接入网设备为例，具体包括如下步骤：
步骤1301：发送端接入网设备成功接收核心网设备发送的数据包1。
步骤1302：接入网设备将数据包1发送给终端设备。
步骤1303：接入网设备成功接收核心网设备发送的数据包3。接入网设备发现中间遗漏了数据包2，证明数据包2丢包或传输失败。
步骤1304：接入网设备将数据包2的传输状态设置为传输失败，同时将数据包3的传输参数调整为传输参数2(第二资源参数)。
步骤1305：接入网设备根据传输参数2将数据包3传输给终端设备。
实施例八：
图14为本申请实施例提供的另一种连续数据包传输失败的规避方法的流程示意图。以发送端为终端设备为例，具体包括如下步骤：
步骤1401：发送端终端设备的PDCP层发送PDCP SDU1给接入网设备。
步骤1402：接入网设备通过DCI或MAC CE告诉终端设备PDCP SDU1的传输状态为传输失败；或者接入网设备指示终端设备将下一个PDCP SDU也即PDCP SDU2 采用第二资源参数来进行传输(图中未示出)。
步骤1403：终端设备将PDCP SDU1对应的传输状态设置为传输失败，终端设备调整PDCP SDU2的传输参数为传输参数2(第二资源参数)来进行PDCP SDU2的传输。
步骤1404：终端设备使用传输参数2向接入网设备传输PDCP SDU2。
应当注意的是，本申请实施例中的所有实体也可以换成其他实体，SDU也可以是PDU，本申请对此不做限定。在本申请的实施例提供的方法中，都是根据前一数据包的传输状态为传输错误而调整当前数据包的传输参数。当前一数据包的传输状态为传输正确时，发送端不调整当前数据包的传输参数。
根据本申请实施例的方法，能够通过前一个数据包的传输状态快速调整后一个数据包的传输策略，在前一个数据包传输失败时采用更高的可靠性保证后面一个数据包的传输，避免连续2个数据包传输失败。
本申请示例还提供一种装置(例如，集成电路、无线设备、电路模块等)用于实现上述方法。实现本文描述的规避连续数据包传输失败的装置可以是自立设备或者可以是较大设备的一部分。设备可以是(i)自立的IC；(ii)具有一个或多个1C的集合，其可包括用于存储数据和/或指令的存储器IC；(iii)RFIC，诸如RF接收机或RF发射机/接收机；(iv)ASIC，诸如移动站调制解调器；(v)可嵌入在其他设备内的模块；(vi)接收机、蜂窝电话、无线设备、手持机、或者移动单元；(vii)其他等等。
本申请实施例提供的方法和装置，可以应用于终端设备或接入网设备(可以统称为无线设备)。该终端设备或接入网设备或无线设备可以包括硬件层、运行在硬件层之上的操作系统层，以及运行在操作系统层上的应用层。该硬件层包括中央处理器(central processing unit，CPU)、内存管理单元(memory management unit，MMU)和内存(也称为主存)等硬件。该操作系统可以是任意一种或多种通过进程(process)实现业务处理的计算机操作系统，例如，Linux操作系统、Unix操作系统、Android操作系统、iOS操作系统或windows操作系统等。该应用层包含浏览器、通讯录、文字处理软件、以及即时通信软件等应用。并且，在本申请实施例中，本申请实施例并不限定方法的执行主体的具体结构，只要能够通过运行记录有本申请实施例的方法的代码的程序，以根据本申请实施例的传输信号的方法进行通信即可，例如，本申请实施例的无线通信的方法的执行主体可以是终端设备或接入网设备，或者，是终端设备或接入网设备中能够调用程序并执行程序的功能模块。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请实施例的范围。
此外，本申请实施例的各个方面或特征可以实现成方法、装置或使用标准编程和/ 或工程技术的制品。本申请中使用的术语“制品”涵盖可从任何计算机可读器件、载体或介质访问的计算机程序。例如，计算机可读介质可以包括，但不限于:磁存储器件(例如，硬盘、软盘或磁带等)，光盘(例如，压缩盘(compact disc，CD)、数字通用盘(digital versatile disc，DVD)等)，智能卡和闪存器件(例如，可擦写可编程只读存储器(erasable programmable read-only memory，EPROM)、卡、棒或钥匙驱动器等)。另外，本文描述的各种存储介质可代表用于存储信息的一个或多个设备和/或其它机器可读介质。术语“机器可读介质”可包括但不限于，无线信道和能够存储、包含和/或承载指令和/或数据的各种其它介质。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘Solid State Disk(SSD))等。
应理解，在本申请实施例的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请实施例的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式 体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者接入网设备等)执行本申请实施例各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请实施例的具体实施方式，但本申请实施例的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请实施例揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请实施例的保护范围之内。

Claims (22)

  1. 一种连续数据包传输失败的规避方法，其特征在于，所述方法包括：
    发送端的接入层第一实体维护所述接入层第一实体的前一个数据包的传输状态；
    如果所述前一个数据包的传输状态为传输失败，所述发送端调整当前数据包的传输参数。
  2. 根据权利要求1所述的方法，其特征在于，所述发送端的接入层第一实体为以下一种：
    无线链路控制层；
    业务数据适配协议层；
    无线资源控制层；
    介质访问控制层；
    物理层。
  3. 根据权利要求1或2所述的方法，其特征在于，所述数据包是业务数据单元或协议数据单元。
  4. 根据权利要求1-3中任一项所述的方法，其特征在于，所述发送端的接入层实体根据以下至少一种信息维护所述接入层实体的前一个数据包的传输状态：
    所述发送端接入层第一实体维护的定时器超时且前一个数据包还未成功传输，则认为前一个数据包的传输状态为传输失败，否则认为前一个数据包传输状态为传输成功；
    接收端接入层第一实体发送给发送端接入层的指示信息，用于指示所述发送端接入层第一实体的前一个数据包是传输成功或传输失败；
    发送端接入层第二实体发送给发送端接入层第一实体的指示信息，用于指示所述发送端接入层第一实体的前一个数据包是传输成功或传输失败；
    接收端接入层第二实体发送给发送端接入层的指示信息，用于指示所述发送端接入层第一实体的前一个数据包是传输成功或传输失败；
    发送端接入层第一实体或第二实体根据当前数据包的序号，若接收的当前数据包的序号与前一个数据包的序号不连续，判断前一个数据包传输失败；
    发送端接入层第一实体或第二实体根据服务质量QoS信息获知数据包的周期，若在前一个周期内没有数据包到达，判断前一个数据包传输失败；
    发送端非接入层或应用层给发送端接入层的指示信息，用于指示所述发送端接入层第一实体的前一个数据包是传输成功或传输失败。
  5. 根据权利要求1-4中任一项所述的方法，其特征在于，所述传输参数包括以下至少一项：
    调制和编码方案；
    最大混合自动重传HARQ次数；
    最大自动重传ARQ次数；
    传输资源的周期；
    传输资源的位置；
    传输资源的大小；
    传输资源的类型；
    逻辑信道优先级；
    无线承载优先级；
    无线链路控制传输模式；
    传输的载波数；
    无线承载的类型；
    无线承载的功能；
    发送功率。
  6. 一种规避连续数据包传输失败的装置，其特征在于，所述装置包括：
    维护单元，用于维护所述接入层第一实体的前一个数据包的传输状态；
    调整单元，用于当所述前一个数据包的传输状态为传输失败，调整当前数据包的传输参数。
  7. 根据权利要求6所述的装置，其特征在于，所述接入层第一实体为以下一种：
    无线链路控制层；
    业务数据适配协议层；
    无线资源控制层；
    介质访问控制层；
    物理层。
  8. 根据权利要求6或7所述的装置，其特征在于，所述数据包是业务数据单元或协议数据单元。
  9. 根据权利要求6-8中任一项所述的装置，其特征在于，所述维护单元根据以下至少一种信息维护所述接入层实体的前一个数据包的传输状态：
    所述装置接入层第一实体维护的定时器超时且前一个数据包还未成功传输，则认为前一个数据包的传输状态为传输失败，否则认为前一个数据包的传输状态为传输成功；
    接收端接入层第一实体发送给装置接入层的指示信息，用于指示所述装置接入层第一实体的前一个数据包是传输成功或传输失败；
    所述装置接入层第二实体发送给装置接入层第一实体的指示信息，用于指示所述装置接入层第一实体的前一个数据包是传输成功或传输失败；
    接收端接入层第二实体发送给装置接入层的指示信息，用于指示所述装置接入层第一实体的前一个数据包是传输成功或传输失败；
    所述装置接入层第一实体或第二实体发送给装置接入层第一实体的指示信息，根据数据包的序号，若接收的当前数据包的序号与前一个数据包的序号不连续，判断前一个数据包传输失败；
    所述装置接入层第一实体或第二实体发送给发送端接入层第一实体的指示信息，根据服务质量QoS信息获知数据包的周期，若数据包在前一个周期内没有到达，判断前一个数据包传输失败；
    所述装置非接入层或应用层发送给装置接入层的指示信息，用于指示所述装置接入层第一实体的前一个数据包是传输成功或传输失败。
  10. 根据权利要求6-9中任一项所述的装置，其特征在于，所述传输参数包括以下至少一项：
    调制和编码方案；
    最大混合自动重传HARQ次数；
    最大自动重传ARQ次数；
    传输资源的周期；
    传输资源的位置；
    传输资源的大小；
    传输资源的类型；
    逻辑信道优先级；
    无线承载优先级；
    无线链路控制传输模式；
    传输的载波数；
    无线承载的类型；
    无线承载的功能；
    发送功率。
  11. 一种连续数据包传输失败的规避方法，其特征在于，所述方法包括：
    发送端的接入层第一实体获取所述接入层第一实体的前n个数据包的传输状态；
    若所述前n个数据包中存在m个数据包的传输状态为传输失败，所述发送端调整当前数据包的传输参数；
    其中，m和n为正整数，且m≤n。
  12. 根据权利要求11所述的方法，其特征在于，所述发送端的接入层实体根据以下至少一种获取所述接入层实体的前n个数据包的传输状态：
    当所述发送端接入层第一实体维护的计数器统计的传输失败的数据包的个数大于或等于m时，则认为所述前n个数据包中存在m个数据包的传输状态为传输失败；或者
    接收端接入层第一实体发送给发送端接入层的指示信息，用于指示所述发送端接入层第一实体的前n个数据包是否存在m个数据包传输失败；或者
    发送端接入层第二实体发送给发送端接入层第一实体的指示信息，用于指示所述发送端接入层第一实体的前n个数据包是否存在m个数据包传输失败；或者
    接收端接入层第二实体发送给发送端接入层的指示信息，用于指示所述发送端接入层第一实体的前n个数据包是否存在m个数据包传输失败；或者
    发送端非接入层或应用层给发送端接入层的指示信息，用于指示所述发送端接入层第一实体的前n个数据包是否存在m个数据包传输失败。
  13. 根据权利要求11或12所述的方法，其特征在于，所述n由接入网设备或核心网设备配置，或者所述n从终端设备的应用层或非接入层获得。
  14. 一种连续数据包传输失败的规避方法，其特征在于，所述方法包括：
    发送端的接入层第一实体获取所述接入层第一实体的向前的至少k个数据包的传输状态；
    当获取的接入层第一实体的数据包中存在连续k个数据包的传输状态为传输失败时，所述发送端调整当前数据包的传输参数；
    其中，k为正整数，且k≥2。
  15. 一种连续数据包传输失败的规避方法，其特征在于，所述方法包括：
    发送端的接入层第一实体获取所述接入层第一实体的至少前x个数据包的传输状态；
    当所述前x个数据包的传输状态为传输失败，所述发送端调整当前数据包的传输参数；
    其中，x为正整数，且x≥2。
  16. 一种连续数据包传输失败的规避装置，其特征在于，所述装置包括：
    获取单元，用于获取所述接入层第一实体的前n个数据包的传输状态；
    调整单元，用于当所述前n个数据包中存在m个数据包的传输状态为传输失败，调整当前数据包的传输参数；
    其中，m和n为正整数，且m≤n。
  17. 根据权利要求16所述的装置，其特征在于，所述接入层实体根据以下至少一种获取所述接入层实体的前n个数据包的传输状态：
    当所述装置接入层第一实体维护的计数器统计的传输失败的数据包的个数大于或等于m时，则认为所述前n个数据包中存在m个数据包的传输状态为传输失败；或者
    接收端接入层第一实体发送给发送端接入层的指示信息，用于指示所述发送端接入层第一实体的前n个数据包是否存在m个数据包传输失败；或者
    所述装置接入层第二实体发送给发送端接入层第一实体的指示信息，用于指示所述发送端接入层第一实体的前n个数据包是否存在m个数据包传输失败；或者
    接收端接入层第二实体发送给发送端接入层的指示信息，用于指示所述发送端接入层第一实体的前n个数据包是否存在m个数据包传输失败；或者
    发送端非接入层或应用层给发送端接入层的指示信息，用于指示所述发送端接入层第一实体的前n个数据包是否存在m个数据包传输失败。
  18. 根据权利要求16或17所述的装置，其特征在于，所述n由接入网设备或核心网设备配置，或者所述n从终端设备的应用层或非接入层获得。
  19. 一种连续数据包传输失败的规避装置，其特征在于，所述装置包括：
    获取单元，用于获取所述接入层第一实体的向前的至少k个数据包的传输状态；
    调整单元，用于当获取的接入层第一实体的数据包中存在连续k个数据包的传输状态为传输失败时，调整当前数据包的传输参数；其中，k为正整数，且k≥2。
  20. 一种连续数据包传输失败的规避装置，其特征在于，所述装置包括：
    获取单元，用于获取所述接入层第一实体的至少前x个数据包的传输状态；
    调整单元，用于当所述前x个数据包的传输状态为传输失败，调整当前数据包的传输参数；其中，x为正整数，且x≥2。
  21. 一种计算机可读存储介质，包括指令，当其在计算机上运行时，使得计算机执行如权利要求1-5中任一项所述的方法。
  22. 一种计算机可读存储介质，包括指令，当其在计算机上运行时，使得计算机执行如权利要求11-15中任一项所述的方法。
PCT/CN2018/115330 2017-11-15 2018-11-14 连续数据包传输失败的规避方法及装置 WO2019096145A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP18879757.5A EP3697041A4 (en) 2017-11-15 2018-11-14 PROCESS AND DEVICE FOR AVOIDING CONSEQUENTIAL FAILURES IN TRANSMISSION OF DATA PACKAGES
US16/874,291 US11277877B2 (en) 2017-11-15 2020-05-14 Method and apparatus for avoiding failure of transmitting consecutive data packets

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201711133111.XA CN109788509B (zh) 2017-11-15 2017-11-15 连续数据包传输失败的规避方法及装置
CN201711133111.X 2017-11-15

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/874,291 Continuation US11277877B2 (en) 2017-11-15 2020-05-14 Method and apparatus for avoiding failure of transmitting consecutive data packets

Publications (1)

Publication Number Publication Date
WO2019096145A1 true WO2019096145A1 (zh) 2019-05-23

Family

ID=66495629

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/115330 WO2019096145A1 (zh) 2017-11-15 2018-11-14 连续数据包传输失败的规避方法及装置

Country Status (4)

Country Link
US (1) US11277877B2 (zh)
EP (1) EP3697041A4 (zh)
CN (1) CN109788509B (zh)
WO (1) WO2019096145A1 (zh)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113950158A (zh) * 2020-07-15 2022-01-18 诺基亚技术有限公司 重新配置用于传输的资源
CN114342287A (zh) * 2019-09-29 2022-04-12 华为技术有限公司 一种数据传输方法及装置
EP4084379A4 (en) * 2020-01-07 2023-01-04 Guangdong Oppo Mobile Telecommunications Corp., Ltd. METHOD AND APPARATUS FOR ACTIVATING OR DEACTIVATING RELIABLE TRANSMISSION
EP4149163A4 (en) * 2020-05-28 2023-11-08 Huawei Technologies Co., Ltd. COMMUNICATION METHOD AND DEVICE

Families Citing this family (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113424497A (zh) * 2019-02-13 2021-09-21 瑞典爱立信有限公司 为延迟关键业务减少连续分组丢失的系统和方法
CN110708723B (zh) * 2019-09-18 2022-12-30 华为终端有限公司 一种数据传输方法及装置
CN110662257B (zh) * 2019-09-29 2021-04-27 京信通信系统（中国）有限公司 报文传输方法、装置、计算机设备和存储介质
CN112865930A (zh) * 2019-11-27 2021-05-28 上海华为技术有限公司 一种发送轮询报文的方法、相关装置和系统
CN113708889A (zh) * 2020-05-22 2021-11-26 维沃移动通信有限公司 数据传输方法和设备
CN113709887A (zh) * 2020-05-22 2021-11-26 维沃移动通信有限公司 数据发送方法和设备
CN113709804A (zh) * 2020-05-22 2021-11-26 维沃移动通信有限公司 数据传输方法、终端设备和网络设备
CN113922930B (zh) * 2020-07-09 2024-05-28 中国移动通信有限公司研究院 数据传输方法及设备
CN114125907B (zh) * 2020-08-28 2024-10-18 上海华为技术有限公司 一种可靠性保障方法及相关装置
DE102021207634A1 (de) * 2021-07-16 2023-01-19 Robert Bosch Gesellschaft mit beschränkter Haftung Verfahren und Vorrichtung zum Betreiben eines Kommunikationssystems zur Optimierung von Parametern des Kommunikationssystems
WO2023240495A1 (zh) * 2022-06-15 2023-12-21 Oppo广东移动通信有限公司 一种数据传输方法及装置、通信设备
CN117812253A (zh) * 2022-09-30 2024-04-02 华为技术有限公司 一种通信方法及装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102404097A (zh) * 2010-09-14 2012-04-04 华为技术有限公司 发送报文的方法和装置
WO2012155821A1 (zh) * 2011-05-17 2012-11-22 华为终端有限公司 差错控制的方法、接收端、发送端和系统
CN106817318A (zh) * 2015-11-30 2017-06-09 中国电信股份有限公司 鲁棒包头压缩状态协商方法、发送端以及系统

Family Cites Families (22)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6961309B2 (en) * 2001-04-25 2005-11-01 International Business Machines Corporation Adaptive TCP delayed acknowledgment
GB2404539B (en) * 2003-07-31 2006-06-14 Fujitsu Ltd Adaptive modulation and coding
CN1780199A (zh) * 2004-11-17 2006-05-31 北京三星通信技术研究有限公司 判定数据包编码、译码方式的方法
CN101084639A (zh) * 2004-12-17 2007-12-05 艾利森电话股份有限公司 蜂窝网络中的设备和方法
CN101098177A (zh) * 2006-06-28 2008-01-02 华为技术有限公司 无线通信系统的数据传输方法
CN101277174A (zh) * 2007-03-30 2008-10-01 华为技术有限公司 基于服务质量的数据重传的方法及其装置和无线通信系统
US8355402B2 (en) * 2007-09-14 2013-01-15 Zte (Usa) Inc. Enhancement of path quality of service in multi-hop packet communication networks
KR101717526B1 (ko) * 2010-01-07 2017-03-17 엘지전자 주식회사 무선 통신 시스템에서 ｍａｃ 프로토콜 데이터 유닛 처리 방법
CN102647803A (zh) * 2011-02-21 2012-08-22 电信科学技术研究院 一种传输消息的方法、系统和设备
US8576709B2 (en) * 2011-05-25 2013-11-05 Futurewei Technologies, Inc. System and method for monitoring dropped packets
WO2013120245A1 (en) * 2012-02-13 2013-08-22 St-Ericsson Sa Method and apparatus for uplink data transmission, user equipment, computer program and storage medium
CN103326832B (zh) * 2012-03-19 2017-11-24 华为技术有限公司 数据包发送方法、参数配置方法及装置
US9152459B2 (en) * 2012-04-23 2015-10-06 Marvell World Trade Ltd. Adjusting thread priority to improve throughput between peer-to-peer (P2P) devices
US9585054B2 (en) * 2012-07-19 2017-02-28 Interdigital Patent Holdings, Inc. Method and apparatus for detecting and managing user plane congestion
CN104244445A (zh) * 2013-06-13 2014-12-24 华为技术有限公司 数据包传输方法、接入点及无线通信系统
ES2773348T3 (es) * 2014-01-29 2020-07-10 Huawei Tech Co Ltd Procedimiento de procesamiento de datos, dispositivo y sistema de comunicación
CN105450357B (zh) * 2014-09-24 2019-02-01 中兴通讯股份有限公司 编码参数的调整、反馈信息的处理方法及装置
CN104486166A (zh) * 2014-12-31 2015-04-01 北京理工大学 一种基于QoS的网络化控制系统采样周期调整方法
CN105025524B (zh) * 2015-06-09 2018-11-13 北京邮电大学 一种多路径并行传输数据调度方法及传输控制协议
US10396942B2 (en) * 2016-03-29 2019-08-27 Samsung Electronics Co., Ltd. Method and apparatus for transmitting and receiving data in a communication system
WO2017194326A1 (en) * 2016-05-13 2017-11-16 Sony Corporation Apparatuses and methods for using arq processes in a relay device
US10567286B2 (en) * 2016-08-09 2020-02-18 Qualcomm Incorporated Congestion control for LTE-V2V

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102404097A (zh) * 2010-09-14 2012-04-04 华为技术有限公司 发送报文的方法和装置
WO2012155821A1 (zh) * 2011-05-17 2012-11-22 华为终端有限公司 差错控制的方法、接收端、发送端和系统
CN106817318A (zh) * 2015-11-30 2017-06-09 中国电信股份有限公司 鲁棒包头压缩状态协商方法、发送端以及系统

Non-Patent Citations (1)

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

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114342287A (zh) * 2019-09-29 2022-04-12 华为技术有限公司 一种数据传输方法及装置
EP4030650A4 (en) * 2019-09-29 2022-12-14 Huawei Technologies Co., Ltd. DATA TRANSMISSION METHOD AND DEVICE
EP4084379A4 (en) * 2020-01-07 2023-01-04 Guangdong Oppo Mobile Telecommunications Corp., Ltd. METHOD AND APPARATUS FOR ACTIVATING OR DEACTIVATING RELIABLE TRANSMISSION
EP4149163A4 (en) * 2020-05-28 2023-11-08 Huawei Technologies Co., Ltd. COMMUNICATION METHOD AND DEVICE
CN113950158A (zh) * 2020-07-15 2022-01-18 诺基亚技术有限公司 重新配置用于传输的资源
EP3940980A1 (en) * 2020-07-15 2022-01-19 Nokia Technologies Oy Reconfiguring resources for transmission
US11523402B2 (en) 2020-07-15 2022-12-06 Nokia Technologies Oy Reconfiguring resources for transmission
CN113950158B (zh) * 2020-07-15 2023-02-14 诺基亚技术有限公司 用于通信的装置、方法及计算机可读存储介质

Also Published As

Publication number Publication date
CN109788509B (zh) 2023-03-10
EP3697041A4 (en) 2020-12-23
US11277877B2 (en) 2022-03-15
US20200275509A1 (en) 2020-08-27
CN109788509A (zh) 2019-05-21
EP3697041A1 (en) 2020-08-19

Similar Documents

Publication Publication Date Title
WO2019096145A1 (zh) 连续数据包传输失败的规避方法及装置
US10805430B2 (en) Evolved data compression scheme signaling
ES2906704T3 (es) Procedimiento y aparato para el procesamiento de un paquete en un sistema de comunicación inalámbrica
US11445403B2 (en) Method for processing data in consideration of TCP/IP
EP3332604B1 (en) Method, apparatus and computer readable medium for packet data convergence protocol (pdcp) reordering with enhanced component carriers
CN111316714B (zh) 无线通信系统中的无线通信的方法和装置
CN111480359B (zh) 用于发送数据单元的通信设备、处理设备及方法
US12047807B2 (en) Method for processing data in consideration of TCP/IP
US20200267793A1 (en) Method and system for handling packet duplication and resumption of rbs in wireless communication system
EP3445020B1 (en) Method and apparatus for performing efficient layer 2 function in mobile communication system
JP2018507636A (ja) コードブロッククラスタレベルｈａｒｑ
WO2017023438A1 (en) Methods and apparatuses for media access control (mac) segmentation and packet data convergence protocol (pdcp) delivery notification (ack) with enhanced component carriers (ecc)
KR20200000283A (ko) 이동통신 시스템에서 무선 링크 실패 보고 방법 및 장치
US20220224446A1 (en) Data transmission method and apparatus
EP3703416B1 (en) Method and device for transmitting data in case of pdcp version change in wireless communication system
US11799597B2 (en) Method and apparatus for packet duplication and retransmission
WO2018059983A1 (en) Communications devices, method and mobile communications system
CN115398966A (zh) 下一代移动通信系统中下行rrc分段消息处理方法及装置
US10477424B2 (en) Device and method of handling aggregation of cellular network and wireless local area network
CN110708723A (zh) 一种数据传输方法及装置
US20230139331A1 (en) Radio link control for mixed numerology standalone carrier aggregation
EP4290794A1 (en) Survival time processing method, and terminal device
CN117501764A (zh) 在多播和广播服务（mbs）系统中的一个或多个多播无线电承载（mrb）路径处应用网络译码

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2018879757

Country of ref document: EP

Effective date: 20200514