WO2018202186A1 - 一种数据传输的处理方法和装置 - Google Patents

一种数据传输的处理方法和装置 Download PDF

Info

Publication number
WO2018202186A1
WO2018202186A1 PCT/CN2018/085742 CN2018085742W WO2018202186A1 WO 2018202186 A1 WO2018202186 A1 WO 2018202186A1 CN 2018085742 W CN2018085742 W CN 2018085742W WO 2018202186 A1 WO2018202186 A1 WO 2018202186A1
Authority
WO
WIPO (PCT)
Prior art keywords
rlc
pdu
status report
mac
entity
Prior art date
Application number
PCT/CN2018/085742
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
Priority claimed from CN201710687319.XA external-priority patent/CN108809510B/zh
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2018202186A1 publication Critical patent/WO2018202186A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • 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

Definitions

  • the embodiments of the present invention relate to communication technologies, and in particular, to a method and an apparatus for processing data transmission.
  • GSM Global System of Mobile communication
  • CDMA Code Division Multiple Access
  • TDMA Time Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • OFDMA Orthogonal Frequency-Division Multiple Access
  • SC-FDMA single carrier FDMA
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • UMTS Universal Mobile Telecommunications System
  • the new wireless access network can provide a higher transmission rate than the LTE network, and the new wireless access network is also called a 5G network, a next generation network, and the like.
  • the Long Term Evolution (LTE) network has a faster transmission rate, and its highest theoretical transmission rate can reach tens of gigabytes per second (Gigabyte, Gb for short).
  • the new communication system is a 5G or a next-generation communication system, including a next-generation core network (NG Core) and a base station (gNB), where the gNB generally includes a Radio Resource Control (RRC) layer and packet data aggregation. Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, Media Access Control (MAC) layer, and Physical Layer (PHY).
  • RRC Radio Resource Control
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control
  • MAC Media Access Control
  • PHY Physical Layer
  • the gNB may also adopt a Centralized Unit (CU) and a Distributed Unit (DU) architecture, and the CU and the DU communicate by wire or wirelessly, and the DU communicates with the terminal device through an air interface.
  • the terminal device moves in different cells under the same or different DUs.
  • the gNB adopts the CU-DU architecture, there are many possibilities for dividing the CU and the DU function.
  • One of the functional division manners may be: the CU includes an RRC layer and a PDCP layer, and the DU includes an RLC layer, a MAC layer, and a PHY layer.
  • the CU device is generally responsible for centralized radio resources and connection management control.
  • the DU device generally includes a distributed user plane processing function, and mainly processes layer 2 (Layer 2) functions with high physical layer functions and real-time requirements.
  • Layer 2 Layer 2
  • the CU device handles the functions of the wireless high-layer protocol stack, such as the RRC layer, the PDCP layer, etc., and can even support partial core network functions to sink to the access network, which is called an edge computing network, and can satisfy future communication networks for emerging services such as video and online shopping. , virtual / augmented reality for higher requirements for network latency.
  • the wireless high-layer protocol stack such as the RRC layer, the PDCP layer, etc.
  • the CU covers the high-level protocol stack of the radio access network and some functions of the core network, while the DU covers the physical layer of the baseband processing and the functions of the layer 2, the CU can be deployed in a centralized manner, and the DU deployment depends on the actual network environment, the core urban area, Areas with high traffic density, small station spacing, and limited space in the computer room, such as colleges and universities, large-scale performance venues, etc., DU can also be distributed in a centralized manner, while the traffic is sparse, and the station spacing is relatively large, such as the suburbs. In areas such as mountains, DUs can be distributed in a distributed manner.
  • FIG. 1 it is a schematic structural diagram of a MAC PDU in an LTE system in the prior art.
  • a MAC protocol data unit PDU
  • RB Radio Bearer
  • LCH logical channel
  • one RLC PDU may include multiple cascaded RLC Service Data Units (SDUs), but only in the header of the RLC PDU (RLC)
  • next generation communication system As shown in FIG. 2, it is a schematic structural diagram of a MAC PDU of a next generation communication system in the prior art, and the next generation communication system may be a 5G communication system, and the RLC layer in the NR is not cascaded.
  • a MAC PDU there are multiple RLC PDUs corresponding to one RB or one LCH, for example, LCH1 corresponds to three RLC PDUs: RLC PDU1, RLC PDU2, and RLC PDU3, and the multiple RLC SDUs are not cascaded, each The RLC PDU has an RLC header, and each packet header has a polling bit, which has many effects on the Polling bit.
  • some of the RLC PDUs have a Polling bit of 1, some.
  • the polling bit of the RLC PDU is zero, so that after receiving the MAC PDU, the receiving end does not know how to send a status report to multiple RLC PDUs corresponding to the LCH.
  • a method and apparatus for processing data transmission are provided to address the problem of how to transmit a status report in a next generation communication system.
  • a first aspect of the present invention provides a method for processing a status report, including: a sender generates a MAC PDU, where the MAC PDU includes one or more RLC PDUs, where a status report transmission request in a header of one or more RLC PDUs is set For the activation, the sending end sends the MAC PDU to the receiving end, so that the receiving end parses the status report sending request in the header of the at least one RLC PDU and determines that the MAC PDU sends a status report when it is activated.
  • the RLC layer of the sending end sets the status report sending request in the header of the one or more RLC PDUs sent by the sending end to be activated, and sends the RLC PDU carrying the status report sending request to the sending.
  • the MAC layer of the end sets the status report sending request in the header of the one or more RLC PDUs sent by the sending end to be activated, and sends the RLC PDU carrying the status report sending request to the sending.
  • the RLC layer of the sending end determines that a status report sending request needs to be sent, and notifies the MAC layer of the sending end to send a status report in the header of the one or more RLC PDUs in the next MAC PDU to be sent.
  • the request is set to active.
  • the RLC layer of the sending end determines that a status report sending request needs to be sent, and notifies the MAC layer of the sending end to select an RLC PDU from the one or more RLC PDUs in the next MAC PDU to be sent and select the RLC PDU.
  • the sequence number of the RLC PDU is notified to the RLC layer of the sending end; the RLC layer of the sending end sets the status report sending request in the header of the RLC PDU corresponding to the sequence number to be activated;
  • the RLC layer sends the RLC PDU carrying the status report transmission request to the MAC layer of the sender.
  • each time the RLC entity sends an RLC SDU the value of the counter SDU_WITHOUT_POLL is incremented by 1.
  • the polling bit in the RLC header of the last generated RLC PDU is set to 1.
  • polling is equal to 0
  • SDU_WITHOUT_POLL is equal to 0.
  • SDU_WITHOUT_POLL is re-accumulated from 1.
  • the counter of the number of RLC PDUs that have been sent by the RLC layer of the sending end may also be a counter that has sent the number of RLC SDUs.
  • the counter of the RLC layer that has been sent by the RLC layer of the sending end may also be a counter that has sent the RLC SDU data volume.
  • the RLC layer of the sending end sends the RLC PDU carrying the status report sending request to the MAC layer of the sending end, and saves the RLC layer saved by the sending end.
  • the counter of the number of RLC PDUs and the counter that has sent the RLC PDU data amount are set to zero, and the restart status report transmits a request retransmission timer.
  • the RLC layer of the sending end when the RLC layer of the sending end sends the RLC PDU carrying the status report sending request to the MAC layer of the sending end, perform at least one of: performing the The RLC layer stores a counter that has transmitted the number of RLC PDUs, a counter that has sent the RLC PDU data amount, and a restart status report transmission request retransmission timer.
  • the RLC layer of the sending end saves the RLC layer of the sending end when the MAC layer of the sending end sends the RLC PDU with the status report sending request to be activated.
  • the counter that sends the number of RLC PDUs and the counter that has sent the RLC PDU data amount are set to zero, and the restart status report sends a request retransmission timer.
  • the RLC layer of the sending end performs at least one of the following: the RLC of the sending end, when the MAC layer of the sending end is configured to send the status report sending request to the activated RLC PDU.
  • the layer sets its saved counter that has sent the number of RLC PDUs, the counter that has sent the RLC PDU data amount to zero, and the restart status report to send a request retransmission timer.
  • the MAC layer of the sending end notifies the RLC layer of the sending end that the carrying status report sending request is set to be an activated RLC PDU when the carrying status report sending request is sent to the activated RLC PDU. send.
  • the MAC layer of the sending end determines one radio bearer in the MAC PDU or any RLC PDU corresponding to one logical channel or one radio bearer in the MAC PDU or multiple RLC PDUs corresponding to one logical channel.
  • the status report transmission request of the last RLC PDU or one of the plurality of RLC PDUs corresponding to one radio bearer or one logical channel corresponding to the RLC PDU is not activated.
  • the MAC layer of the sending end notifies the RLC layer of the RLC PDU of the sequence number SN of the RLC PDU when the carrying status report sending request is sent to the RLC PDU, where the SN is The status report sends a request to the SN of the activated RLC PDU, or the SN is a SN of the last RLC PDU in the MAC PDU to which the status report transmission request is set to the active RLC PDU, or the SN is a status report transmission.
  • the SN of any one of the RLC PDUs within the MAC PDU to which the activated RLC PDU belongs is requested.
  • the MAC layer of the sending end notifies the sending end of the RLC PDU of the RLC layer of the RLC layer when the carrying status report sending request is sent to the RLC PDU, and notifies the sending
  • the RLC layer current status report transmission request of the terminal is set to be active.
  • a second aspect of the present invention provides a processing apparatus for status reporting, comprising: a MAC entity, configured to generate a MAC PDU, the MAC PDU including one or more RLC PDUs, wherein a status report in a header of one or more RLC PDUs
  • the sending request is set to be activated; the MAC entity is further configured to send the MAC PDU to the receiving end, so that the receiving end parses the status report in the header of the at least one RLC PDU and determines that the MAC address is determined to be the MAC address.
  • the PDU sends a status report.
  • the device further includes: an RLC entity, configured to: activate a status report sending request in a header of the one or more RLC PDUs that it sends, and carry the status report sending request The RLC PDU is sent to the MAC entity.
  • an RLC entity configured to: activate a status report sending request in a header of the one or more RLC PDUs that it sends, and carry the status report sending request The RLC PDU is sent to the MAC entity.
  • the device further includes: an RLC entity, configured to determine that a status report sending request needs to be sent, and notify the MAC entity in a header of the one or more RLC PDUs in the next MAC PDU to be sent.
  • the status report send request is set to active.
  • the device further includes: an RLC entity, configured to determine that a status report sending request needs to be sent, and notify the MAC entity to select one RLC PDU from the one or more RLC PDUs in the next MAC PDU to be sent. Notifying the RLC entity of the sequence number of the selected RLC PDU; wherein the RLC entity is further configured to enable the status report sending request in the header of the RLC PDU corresponding to the sequence number to be activated, The status report sends the requested RLC PDU to the MAC entity.
  • an RLC entity configured to determine that a status report sending request needs to be sent, and notify the MAC entity to select one RLC PDU from the one or more RLC PDUs in the next MAC PDU to be sent. Notifying the RLC entity of the sequence number of the selected RLC PDU; wherein the RLC entity is further configured to enable the status report sending request in the header of the RLC PDU corresponding to the sequence number to be activated, The status report sends the requested RLC PDU to the MAC
  • the RLC entity is further configured to: when the RLC PDU carrying the status report sending request is sent to the MAC entity, save the RLC entity with a counter that has sent the number of RLC PDUs and has sent the RLC.
  • the counter of the PDU data amount is set to zero, and the restart status report sends a request retransmission timer.
  • the RLC entity is further configured to: when the RLC PDU carrying the status report sending request is sent to the MAC entity, perform at least one of: saving the RLC PDU by the RLC entity The counter, the counter that has sent the RLC PDU data amount, and the restart status report send a request retransmission timer.
  • the RLC entity is further configured to: when the MAC entity sends the RLC PDU that sends the status report sending request to be activated, the RLC entity saves the counter of the number of RLC PDUs that have been sent and has sent the RLC.
  • the counter of the PDU data amount is set to zero, and the restart status report sends a request retransmission timer.
  • the RLC entity is further configured to: when the MAC entity sends the RLC PDU that sends the status report sending request to be activated, perform at least one of: the number of RLC PDUs that have been sent by the RLC entity.
  • the counter, the counter that has sent the RLC PDU data amount, and the restart status report send a request retransmission timer.
  • the MAC entity is further configured to notify the RLC entity that the RLC entity has sent the carrying status report sending request to the activated RLC PDU when the RLC PDU with the carrying status report sending request is sent.
  • the MAC entity is further configured to determine, in the MAC PDU, one radio bearer or any one RLC PDU corresponding to one logical channel or one radio bearer in the MAC PDU or multiple RLC PDUs corresponding to one logical channel.
  • the status report transmission request of the last RLC PDU or one of the plurality of RLC PDUs corresponding to one radio bearer or one logical channel corresponding to the RLC PDU that is not segmented is activated.
  • the MAC entity is further configured to notify the RLC entity of a sequence number SN of an RLC PDU when the RLC PDU that carries the status report sending request is sent to be activated, where the SN is a status report sending request.
  • a third aspect of the present invention provides a method for processing a status report, including: receiving, by a receiving end, a MAC PDU sent by a transmitting end, where the MAC PDU includes one or more RLC PDUs, where a header of one or more RLC PDUs is included.
  • the status report sending request is set to be activated; when the receiving end determines that the status report sending request of the at least one RLC PDU in the MAC PDU is set to be activated, generating a status report according to the status report sending request to be activated; the receiving end Send a status report to the sender.
  • the generating the status report according to the status report sending request to be activated includes: determining, according to the status report sending request, that the status of the status report sending request of the last RLC PDU in the MAC PDU is Activate to generate a status report based on the serial number (SN) of the last RLC PDU.
  • one of the radio bearers or one RLC PDU corresponding to one logical channel or one radio bearer in the MAC PDU or the last RLC PDU or the MAC of the multiple RLC PDUs corresponding to one logical channel A status report transmission request of the last one of the plurality of RLC PDUs corresponding to one radio bearer or one logical channel in the PDU that is not segmented is deactivated.
  • a fourth aspect of the present invention provides a processing apparatus for a status report, including: a receiver, configured to receive a MAC PDU sent by a transmitting end, where the MAC PDU includes one or more RLC PDUs, where one or more RLC PDUs The status report sending request in the packet header is activated; the processor is configured to: when the status report sending request of the at least one RLC PDU in the MAC PDU is determined to be activated, generate a status report according to the status report sending request to be activated; The sender sends a status report to the sender.
  • the generating, by the processor, the generating the status report according to the status report sending request the method further includes: the processor, configured to determine, according to the status report, that the sending request is set to an active state, determining a last one of the MAC PDUs The status of the RLC PDU report request is activated, and a status report is generated based on the sequence number (SN) of the last RLC PDU.
  • the processor configured to determine, according to the status report, that the sending request is set to an active state, determining a last one of the MAC PDUs The status of the RLC PDU report request is activated, and a status report is generated based on the sequence number (SN) of the last RLC PDU.
  • one of the radio bearers or one RLC PDU corresponding to one logical channel or one radio bearer in the MAC PDU or the last RLC PDU or the MAC of the multiple RLC PDUs corresponding to one logical channel A status report transmission request of the last one of the plurality of RLC PDUs corresponding to one radio bearer or one logical channel in the PDU that is not segmented is deactivated.
  • the receiving end determines that the MAC PDU transmission status report is determined as long as the status report transmission request in the header of the at least one RLC PDU is parsed.
  • FIG. 1 is a schematic structural diagram of a MAC PDU of an LTE system in the prior art
  • FIG. 2 is a schematic structural diagram of a MAC PDU of a next generation communication system in the prior art
  • FIG. 3 is a schematic diagram of a communication system according to an embodiment of the present invention.
  • FIG. 4 is a schematic structural diagram of another communication system according to another embodiment of the present invention.
  • FIG. 5 is a schematic flowchart of a method for processing a status report according to an embodiment of the present invention
  • FIG. 5a is a schematic diagram of a state process of transmitting an RLC SDU according to another embodiment of the present invention.
  • FIG. 5b is a schematic diagram of another state process of transmitting an RLC SDU according to another embodiment of the present invention.
  • FIG. 5c is a schematic diagram of another state process of transmitting an RLC SDU according to another embodiment of the present invention.
  • FIG. 5 is a schematic diagram of another state process of transmitting an RLC SDU according to another embodiment of the present invention.
  • FIG. 5e is a schematic diagram of another state process of transmitting an RLC SDU according to another embodiment of the present invention.
  • FIG. 5f is a schematic diagram of another state process of transmitting an RLC SDU according to another embodiment of the present invention.
  • FIG. 6 is a schematic structural diagram of a device for processing a status report according to another embodiment of the present invention.
  • FIG. 7 is a schematic flowchart diagram of another method for processing a status report according to an embodiment of the present invention.
  • FIG. 8 is a schematic structural diagram of another apparatus for processing a status report according to another embodiment of the present invention.
  • FIG. 9 is a process state diagram of a method for triggering an RLC Polling according to another embodiment of the present invention.
  • FIG. 10 is a process state diagram of another method for triggering RLC Polling according to another embodiment of the present invention.
  • FIG. 11 is a process state diagram of another method for triggering an RLC Polling according to another embodiment of the present invention.
  • FIG. 12 is a process state diagram of another method for triggering an RLC Polling according to another embodiment of the present invention.
  • FIG. 13 is a process state diagram of another method for triggering an RLC Polling according to another embodiment of the present invention.
  • FIG. 14 is a process state diagram of another method for triggering an RLC Polling according to another embodiment of the present invention.
  • FIG. 15 is a process state diagram of another method for triggering an RLC Polling according to another embodiment of the present invention.
  • FIG. 16 is a schematic diagram of a data structure of an RLC control PDU according to an embodiment of the present invention.
  • FIG. 17 is a schematic structural diagram of an RLC status report according to another embodiment of the present invention.
  • FIG. 17a is a schematic structural diagram of another RLC status report format according to another embodiment of the present invention.
  • FIG. 18 is a schematic structural diagram of another RLC status report according to another embodiment of the present invention.
  • FIG. 18a is a schematic structural diagram of another RLC status report format according to another embodiment of the present invention.
  • FIG. 19 is a schematic structural diagram of another RLC status report according to another embodiment of the present invention.
  • FIG. 19a is a schematic structural diagram of another RLC status report format according to another embodiment of the present invention.
  • FIG. 20 is a schematic structural diagram of another RLC status report according to another embodiment of the present invention.
  • 20a is a schematic structural diagram of another RLC status report format according to another embodiment of the present invention.
  • FIG. 21 is a schematic structural diagram of another RLC status report according to another embodiment of the present invention.
  • 21a is a schematic structural diagram of another RLC status report format according to another embodiment of the present invention.
  • FIG. 21b is a schematic structural diagram of another RLC status report format according to another embodiment of the present invention.
  • FIG. 22 is a schematic structural diagram of another RLC status report according to another embodiment of the present invention.
  • FIG. 22 is a schematic structural diagram of another RLC status report format according to another embodiment of the present invention.
  • FIG. 23 is a schematic structural diagram of a packet header of an RLC PDU according to an embodiment of the present invention.
  • FIG. 24 is a schematic structural diagram of a packet header of an RLC PDU according to an embodiment of the present invention.
  • 25 is a schematic structural diagram of another packet header of an RLC PDU according to another embodiment of the present invention.
  • FIG. 26 is a schematic diagram of another process for configuring a token bucket state according to another embodiment of the present invention.
  • FIG. 27 is a schematic diagram of a process of changing a Bj state according to another embodiment of the present invention.
  • FIG. 28 is a schematic diagram of a process of changing a Bj state according to another embodiment of the present invention.
  • FIG. 29 is a schematic diagram of coexistence of semi-persistent scheduling resources and dynamic scheduling resources according to another embodiment of the present invention.
  • a “module” as referred to herein generally refers to a program or instruction stored in a memory that is capable of performing certain functions;
  • "unit” as referred to herein generally refers to a functional structure that is logically divided, the "unit” It can be implemented by pure hardware or a combination of hardware and software.
  • Multiple as referred to herein means two or more. "and/or”, describing the association relationship of the associated objects, indicating that there may be three relationships, for example, A and/or B, which may indicate that there are three cases where A exists separately, A and B exist at the same time, and B exists separately.
  • the character "/" generally indicates that the contextual object is an "or" relationship.
  • LTE networks also known as 5G networks, next generation Network, etc.
  • the terminal device may be a wireless terminal or a wired terminal, and the wireless terminal may be a device that provides voice and/or data connectivity to the receiving end, a handheld device with wireless connection function, or a wireless modem connected to the wireless modem. Other processing equipment.
  • the wireless terminal can communicate with one or more core networks via a radio access network (eg, RAN, Radio Access Network), which can be a mobile terminal, such as a mobile phone (or "cellular" phone) and with a mobile terminal
  • RAN Radio Access Network
  • the computers for example, can be portable, pocket-sized, handheld, computer-integrated or in-vehicle mobile devices that exchange language and/or data with the wireless access network.
  • a wireless terminal may also be called a system, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, an access point, or an access point.
  • Remote Terminal Access Terminal, User Terminal, User Equipment, or User Agent.
  • a base station may refer to a device in an access network that communicates with a wireless terminal over one or more sectors over an air interface, such as an access network device of a new wireless access network, the new wireless access network
  • the access network device is also referred to as a base station (gNB), an NR Node (node), or an NR BS (Base Station), which is not limited herein, but is conveniently referred to herein as gNB for convenience of description.
  • FIG. 3 it is a schematic diagram of a communication system including an access network device 31 and a terminal device 32, which may be a new wireless access network, such as the above.
  • the new radio access network is also referred to as a 5G network, a next generation network, etc.
  • the access network device 31 may be a gNB of a 5G communication system.
  • the access network device 31 includes a three-layer structure: layer one is a physical layer (PHY layer), layer two is a medium access control layer (MAC layer), a radio link control layer (RLC layer), and a packet data convergence protocol layer. (PDCP layer), layer 3 is the radio resource control layer (RRC layer), where the PHY layer is the lowest layer of the radio access system, which uses the transport channel as an interface to provide services to the upper layer.
  • the PHY layer, the MAC layer, the RLC layer, the PDCP layer, and the RRC layer of the access network device 31 are provided with a receiving entity and a sending entity for each bearer, respectively, for receiving and transmitting data, but for description Conveniently, the following descriptions are all described by sending or receiving at each layer.
  • the data received by the access network device 31 from the terminal device 32 is processed through the PHY layer, the MAC layer, the RLC layer, the PDCP layer, and the RRC layer of the access network device 31 in sequence.
  • the PHY layer processes the received data into a PHY service data unit ( a Service Data Unit (SDU), the PHY layer transmitting the PHY SDU to the MAC layer; the MAC layer receiving the PYH SDU, and then processing the PYH SDU as a MAC SDU, the MAC layer Transmitting the MAC SDU to the RLC layer; the RLC layer receives the MAC SDU, and then processes the MAC SDU into an RLC SDU, where the RLC layer sends the RLC SDU to the PDCP layer; the PDCP Receiving, by the layer, the RLC SDU, and then processing the RLC SDU into a signaling PDCP
  • the data sent by the access network device 31 sequentially passes through the PDCP layer, the RLC layer, the MAC layer, and the PHY layer, and then is sent to the terminal device 32.
  • the PDCP layer processes data into a PDCP Protocol Data Unit (PDU), and then sends the PDCP PDU to the RLC layer;
  • the RLC layer receives The PDCP PDU, which then processes the PDCP PDU as an RLC PDU, the RLC layer sends the RLC PDU to the MAC layer;
  • the MAC layer receives the RLC PDU, and then processes the RLC PDU as a MAC PDU, the MAC layer transmitting the MAC PDU to the PHY layer;
  • the PHY layer receiving the MAC PDU, and then processing the MAC PDU as a PHY PDU, the PHY layer sending the PHY PDU To the terminal device 32.
  • the terminal device 32 includes a PHY layer, a MAC layer, an RLC layer, and a PDCP layer, and each layer included in the terminal device 32 is provided with a receiving entity and a sending entity for receiving and transmitting data for each bearer. However, for convenience of description, the following description is described by transmitting or receiving at each layer. .
  • the data sent by the terminal device 32 to the access network device 31 is processed by the PDCP layer, the RLC layer, the MAC layer, and the PHY layer of the terminal device 32 in sequence.
  • the PDCP layer of the terminal device 32 processes the data as a PDCP PDU, and then transmits the PDCP PDU to the RLC layer; the RLC layer receives the PDCP PDU, and then processes the PDCP PDU into an RLC PDU.
  • the RLC layer sends the RLC PDU to the MAC layer; the MAC layer receives the RLC PDU, and then processes the RLC PDU into a MAC PDU, and the MAC layer sends the MAC PDU to the The PHY layer receives the MAC PDU, and then processes the MAC PDU into a PHY PDU, and the PHY layer sends the PHY PDU to a processor in the terminal device 31 for processing.
  • the data received by the terminal device 32 from the access network device 31 is processed through the PHY layer, the MAC layer, the RLC layer, and the PDCP layer of the terminal device 32 in sequence.
  • the PHY layer data is processed as a PHY SDU, and then the PHY SDU is transmitted to the MAC layer;
  • the MAC layer receives the PYH SDU, and then processes the PYH SDU into a MAC SDU, the MAC layer sends the MAC SDU to the RLC layer;
  • the RLC layer receives the MAC SDU, and then processes the MAC SDU into an RLC SDU, and the RLC layer sends the RLC SDU to
  • the PDCP layer receives the RLC SDU, and then processes the RLC SDU into a PDCP SDU, and the PDCP layer sends the PDCP SDU to a higher layer of the access network device 31 for processing.
  • the communication system is a 4G or next generation communication system, including an access network device 41, a terminal device 42, and a next generation core network (NG Core). 43.
  • the access network device 41 is a 4G gNB
  • the access network device 41 includes a centralized unit (CU) 411 and a distributed unit (DU) 412, and the CU 411 and the DU 412 communicate by wire or wirelessly.
  • the DU 412 communicates with the terminal device 42 through an air interface.
  • the RRC layer and the PDCP layer function are located on the CU 411, and the RLC layer, the MAC layer, and the PHY layer function are located on the DU 412.
  • FIG. 5 is a schematic flowchart of a method for processing a status report according to an embodiment of the present invention.
  • the communication system includes an access network device and a terminal device, and the access network device communicates with the terminal device through an air interface, and the connection is performed.
  • the network access device may be a gNB in a 5G communication system or a base station of a next-generation communication system, and the gNB may adopt the architecture of the gNB of FIG. 3 or FIG. 4, and one of the access network device and the terminal device is a transmitting end, The other party is the receiving end. For example, when the access network device is the transmitting end, the terminal device is the receiving end, and vice versa.
  • Step 51 The sender generates a MAC PDU, where the MAC PDU includes one or more RLC PDUs, where a status report transmission request in a header of one or more RLC PDUs is activated.
  • each RLC PDU has an RLC header
  • each RLC header includes a sequence number (SN) of a polling bit and an RLC PDU.
  • Step 52 The sending end sends the MAC PDU to the receiving end, so that the receiving end resolves that the status report sending request in the header of the at least one RLC PDU is determined to be the MAC PDU sending status report when activated.
  • the RLC layer of the transmitting end sets the status report sending request in the header of the one or more RLC PDUs that it sends, and will carry the status report sending request.
  • the RLC PDU is sent to the MAC layer of the sender.
  • the RLC layer of the transmitting end determines that a status report sending request needs to be sent, and notifies the MAC layer of the sending end of the one or more RLC PDUs in the MAC PDU to be sent next time.
  • the status report send request in the header is activated.
  • the RLC layer of the sending end further notifies the sequence number of the one or more RLC PDUs in the MAC PDU that needs to be sent by the MAC layer of the sending end, and indicates that the MAC layer of the sending end is connected to one or more RLCs.
  • the status report transmission request in the header of the PDU is set to be activated, and the MAC layer determines that the particular RLC PDU is set to 1, for example, arbitrarily determined or the last RLC PDU.
  • the RLC layer of the sending end when the RLC layer of the sending end is configured to send the RLC PDU that the carrying status report sending request is activated to, the RLC layer of the sending end receives the sending end of the RLC layer.
  • the MAC layer sends a notification message that the RLC PDU SN with the polling bit is set to 1 and the RLC PDU has been sent, and the RLC layer of the transmitting end saves the counter (PDU_WITHOUT_POLL) of the number of RLC PDUs that have been sent and already
  • the counter (BYTE_WITHOUT_POLL) that sends the RLC PDU data amount is set to zero, and the restart status report sends a request retransmission timer (t-PollRetransmit).
  • the RLC layer of the sending end when the RLC layer of the sending end is configured to send the RLC PDU that the carrying status report sending request is activated to, the RLC layer of the sending end receives the sending end of the RLC layer.
  • the notification information that is sent by the MAC layer and has an RLC PDU SN with a polling bit set to 1 and the RLC PDU has been sent, and at least one of the following: the RLC layer of the sending end saves the number of RLC PDUs that have been saved by the RLC layer.
  • the counter PDU_WITHOUT_POLL
  • the counter BYTE_WITHOUT_POLL
  • t-PollRetransmit the restart status report send request retransmission timer
  • the MAC layer of the sending end notifies that the RLC layer of the sending end has sent the carrying status report sending request to the activated RLC PDU when the RLC PDU that sends the status report sending request is sent to be activated.
  • the MAC layer of the sender notifies the RLC layer of the sender that there is an RLC PDU SN with a polling bit set to 1 and the RLC PDU has been sent.
  • the MAC layer of the sending end notifies the RLC layer of the RLC PDU of the sequence number SN of the RLC PDU when the carrying status report sending request is sent to the RLC PDU, where the SN is a status report.
  • Sending a request to be the SN of the activated RLC PDU, or the SN is a SN of the last RLC PDU in the MAC PDU to which the status report transmission request is set to the activated RLC PDU, or the SN is a status report transmission request The SN of any RLC PDU within the MAC PDU to which the activated RLC PDU belongs.
  • the RLC layer of the transmitting end determines that a status report sending request needs to be sent, and notifies the MAC layer of the sending end to select one of the one or more RLC PDUs in the next MAC PDU to be sent. And the RLC PDU notifies the RLC layer of the selected RLC PDU to the RLC layer of the sending end; the RLC layer of the sending end sets the status report sending request in the header of the RLC PDU corresponding to the serial number to be activated; The RLC layer of the sending end sends the RLC PDU carrying the status report sending request to the MAC layer of the sending end.
  • the counter of the number of RLC PDUs that have been sent by the RLC layer of the transmitting end may also be a counter that has sent the number of RLC SDUs.
  • the counter of the RLC layer that has been sent by the RLC layer of the transmitting end may also be a counter that has sent the RLC SDU data amount.
  • the base station when the RLC entity is established, the base station configures a threshold K for SDU_WITHOUT_POLL through an RRC message, and the initial value of SDU_WITHOUT_POLL is 0.
  • the RLC entity sends out an RLC SDU, and the transmitting end RLC calculates SDU_WITHOUT_POLL, the counter is used.
  • the value of SDU_WITHOUT_POLL is incremented by 1 until SDU_WITHOUT_POLL is equal to the threshold K (ie, the SDU number counter is equal to K), and the polling bit in the RLC header of one RLC PDU generated corresponding to the last RLC SDU is set to 1, and the last is sent.
  • the polling is equal to 0, and the SDU_WITHOUT_POLL is equal to 0.
  • the SDU_WITHOUT_POLL is re-accumulated from 1.
  • the RLC entity sends the RLC SDU to the MAC entity, and the RLC SDU processes the RLC SDU to form one or more RLC PDUs, and then sends the RLC PDU to the MAC entity.
  • the RLC entity sends an RLC SDU it means that the RLC entity starts processing the RLC SDU and prepares to send the RLC SDU.
  • the base station configures a threshold K for the SDU_WITHOUT_POLL through the RRC message, and the initial value of the SDU_WITHOUT_POLL is 0.
  • the RLC entity increments the SDU_WITHOUT_POLL by one for each RLC SDU, and if the SDU_WITHOUT_POLL exceeds the threshold K,
  • the RLC entity triggers polling, and sets the polling bit in the RLC header of one RLC PDU generated corresponding to the last RLC SDU, that is, notifies the receiving end to send an RLC status report.
  • FIG. 5 is a schematic diagram of a state process of transmitting an RLC SDU according to another embodiment of the present invention.
  • the threshold K of the SDU_WITHOUT_POLL is configured as 1000, and when the RLC entity of the sending end finds that the SDU_WITHOUT_POLL is equal to the threshold 1000 (ie, the SDU number counter) If it is equal to 1000), the Polling bit in the RLC header is set to 1. After the RLC SN is sent as the RLC PDU corresponding to the threshold 1000, polling is equal to 0, SDU_WITHOUT_POLL is equal to 0, and when the next RLC SDU is sent, SDU_WITHOUT_POLL is restarted from 1 Grand total.
  • the RLC SDU with the RLC SN equal to 999 is divided into two segments, both of which use the same RLC SN.
  • the SDU_WITHOUT_POLL is increased from 998 to 999.
  • the RLC entity finds that this is the second segment of the same RLC SDU, and does not increase SDU_WITHOUT_POLL, and the value is still 999.
  • the RLC entity of the sending end finds that SDU_WITHOUT_POLL is equal to the threshold 1000 (ie, the SDU number counter is equal to 1000)
  • the RLC header is The Polling bit is set to 1.
  • polling is equal to 0, and SDU_WITHOUT_POLL is equal to 0.
  • SDU_WITHOUT_POLL is re-accumulated from 1.
  • the processing of the Polling has the following four modes.
  • Method 1 The polling bit of each RLC segment is set to 1
  • the RLC SDU with the RLC SN equal to 1000 is divided into three segments, all of which use the same segment.
  • SDU_WITHOUT_POLL is equal to 0.
  • SDU_WITHOUT_POLL is equal to 0.
  • SDU_WITHOUT_POLL is re-accumulated from 1.
  • the RLC SDU with an RLC SN equal to 1000 is divided into three segments, all of which use the same segment.
  • SDU_WITHOUT_POLL is equal to 0.
  • SDU_WITHOUT_POLL is equal to 0.
  • SDU_WITHOUT_POLL is re-accumulated from 1.
  • the RLC SDU with the RLC SN equal to 1000 is divided into three segments, all of which use the same segment.
  • SDU_WITHOUT_POLL is equal to 0.
  • SDU_WITHOUT_POLL is equal to 0.
  • SDU_WITHOUT_POLL is re-accumulated from 1.
  • Method 4 Optional one RLC segment polling bit is set to 1
  • the RLC SDU with the RLC SN equal to 1000 is divided into three segments, all of which use the same segment.
  • mode 2 if mode 2 is selected, the receiving end can be triggered to send an RLC status report in time, and the behavior of the receiving end does not need to be modified.
  • the RLC layer of the sending end sends the RLC PDU carrying the status report sending request to the MAC layer of the sending end, and the The counter that has saved the number of RLC PDUs stored in the RLC layer and the counter that has sent the RLC PDU data amount are set to zero, and the restart status report transmits a request retransmission timer.
  • the RLC layer of the transmitting end when the RLC layer of the transmitting end sends the RLC PDU carrying the status report sending request to the MAC layer of the sending end, perform at least one of the following: The counter of the RLC layer that has been sent by the RLC layer of the transmitting end, the counter that has sent the RLC PDU data amount, and the restart status report send request retransmission timer.
  • the MAC layer of the sending end determines one radio bearer in the MAC PDU or any RLC PDU corresponding to one logical channel or one radio bearer or one logical channel in the MAC PDU.
  • a status report transmission request of the last one of the plurality of RLC PDUs or the last one of the plurality of RLC PDUs corresponding to one of the plurality of RLC PDUs corresponding to one of the plurality of RLC PDUs in the MAC PDU is activated.
  • the receiving end determines that the MAC PDU is sent as the status report when the status report sending request in the header of the at least one RLC PDU is parsed, and the receiving end does not include multiple RLCs because the MAC PDU includes multiple RLCs. PDU, and the header of each RLC PDU includes different polling bit values, which affects the receiving end is not sure how to send a status report.
  • FIG. 6 is a schematic structural diagram of a device for processing a status report according to another embodiment of the present invention.
  • the communication system includes an access network device and a terminal device, and the access network device communicates with the terminal device through an air interface.
  • the access network device may be a gNB in a 5G communication system or a base station of a next-generation communication system, and the gNB may adopt the architecture of the gNB of FIG. 3 or FIG. 4, and one of the access network device and the terminal device is sent.
  • the other end is the receiving end. For example, when the access network device is the transmitting end, the terminal device is the receiving end, and vice versa.
  • the sending end is a processing device of the status report
  • the processing device of the status report includes a PYH entity 61, a MAC entity 62, an RLC entity 63, and a PDCP entity 64.
  • the processing functions of the PYH entity 61, the MAC entity 62, the RLC entity 63, and the PDCP entity 64 are performed by a processor, which may be an erasable editable logic device (Erasable Programmable Logic) Device, EPLD), Field Programmable Gate Array (FPGA), Digital Signal Processor (DSP) chip, Application Specific Integrated Circuit (ASIC), or other programmable logic device , discrete gates or transistor logic devices, discrete hardware components, etc.
  • a processor which may be an erasable editable logic device (Erasable Programmable Logic) Device, EPLD), Field Programmable Gate Array (FPGA), Digital Signal Processor (DSP) chip, Application Specific Integrated Circuit (ASIC), or other programmable logic device , discrete gates or transistor logic devices, discrete hardware components, etc.
  • a processor which may be an erasable editable logic device (Erasable Programmable Logic) Device, EPLD), Field Programmable Gate Array (FPGA), Digital Signal Processor (DSP
  • the receiving and transmitting function distributions of the PYH entity 61, the MAC entity 62, the RLC entity 63, and the PDCP entity 64 are performed by a receiver and a transmitter.
  • the processing device of the status report further includes a memory for storing code or instruction information, and may also store information of a device type.
  • the memory can include a Read-Only Memory (ROM) and a Random Access Memory (RAM) for providing instructions and data to the processor.
  • a portion of the memory may also include a non-volatile random access memory.
  • the MAC entity 62 is configured to generate a MAC PDU, where the MAC PDU includes one or more RLC PDUs, where a status report transmission request in a header of one or more RLC PDUs is set to be activated.
  • LCH1 corresponds to three RLC PDUs: RLC PDU1, RLC PDU2 And the RLC PDU3, the multiple RLC SDUs are not concatenated, and each RLC PDU has an RLC header, and each RLC header includes a sequence number (SN) of the polling bit and the RLC PDU.
  • the MAC entity 62 is further configured to send the MAC PDU to the receiving end, so that the receiving end parses the status report in the header of the at least one RLC PDU and determines that the MAC PDU sends a status report when the request is sent to be activated. .
  • the RLC entity 63 activates a status report transmission request in a header of the one or more RLC PDUs it transmits, and will carry the status report transmission request.
  • the RLC PDU is sent to the MAC entity 62.
  • the RLC entity 63 determines that a status report transmission request needs to be sent, and notifies the MAC entity 62 of the header of the one or more RLC PDUs in the next MAC PDU to be transmitted.
  • the status report send request is set to active.
  • the RLC entity 63 is further configured to notify the MAC entity 62 of the sequence number of the one or more RLC PDUs in the MAC PDU that needs to be sent next, and instruct the MAC entity 62 to pair one or more RLC PDUs.
  • the status report transmission request in the header is set to be activated, and the MAC entity 62 of the sender determines that the particular RLC PDU is set to 1, for example, arbitrarily determined or the last RLC PDU.
  • the RLC entity 63 learns that the MAC entity 62 of the sending end sends the carrying status report sending request to the activated RLC PDU, for example, the RLC entity 63 receives the MAC entity 62 of the sending end.
  • the RLC entity 63 learns that the MAC entity 62 of the sending end sends the carrying status report sending request to the activated RLC PDU, for example, the RLC entity 63 receives the MAC entity 62 of the sending end.
  • the notification information that is sent by the RLC PDU SN with the polling bit set to 1 and the RLC PDU has been sent performs at least one of the following: the counter (PDU_WITHOUT_POLL) that the RLC entity 63 has saved the number of RLC PDUs that have been sent, has been sent.
  • the counter of the RLC PDU data amount (BYTE_WITHOUT_POLL) is set to zero and the restart status report sends a request retransmission timer (t-PollRetransmit).
  • the MAC entity 62 of the sending end notifies the RLC entity 63 that the RLC PDU has been sent to the active RLC PDU by sending the status report sending request to the RLC PDU.
  • the MAC entity 62 of the sender informs the RLC entity 63 that there is an RLC PDU SN with a polling bit set to 1 and that the RLC PDU has been transmitted.
  • the MAC entity 62 of the sending end notifies the RLC entity 63 of the sequence number SN of an RLC PDU when the RLC PDU carrying the status report sending request is set to be activated, where the SN is a status report sending request.
  • the SN of the activated RLC PDU, or the SN is a SN of the last RLC PDU in the MAC PDU to which the status report transmission request is set to the activated RLC PDU, or the SN is a status report transmission request is activated.
  • the RLC entity 63 determines that a status report transmission request needs to be sent, and notifies the MAC entity 62 of the sender from the one or more RLC PDUs of the MAC PDU to be transmitted next time. Selecting an RLC PDU and notifying the RLC entity 63 of the sequence number of the selected RLC PDU; the RLC entity 63 is configured to activate the status report sending request in the header of the RLC PDU corresponding to the sequence number; the RLC entity 63. Send the RLC PDU carrying the status report sending request to the MAC entity 62 of the sending end.
  • the RLC entity 63 when the RLC entity 63 that carries the status report sending request is sent to the MAC entity 62 of the sending end, the RLC entity 63 saves the RLC entity 63.
  • the counter that sends the number of RLC PDUs and the counter that has sent the RLC PDU data amount are set to zero, and the restart status report sends a request retransmission timer.
  • the RLC entity 63 when the RLC entity 63 that carries the status report sending request is sent to the MAC entity 62 of the sending end, the RLC entity 63 performs at least one of: The RLC entity 63 holds a counter that has transmitted the number of RLC PDUs, a counter that has sent the RLC PDU data amount, and a restart status report transmission request retransmission timer.
  • the MAC entity 62 of the sending end determines one radio bearer in the MAC PDU or any RLC PDU corresponding to one logical channel or a radio bearer or a logic in the MAC PDU.
  • a status report transmission request of the last one of the plurality of RLC PDUs corresponding to the channel or one of the plurality of RLC PDUs corresponding to one radio bearer or one of the logical channels is not activated.
  • the receiving end determines that the MAC PDU is sent as the status report when the status report sending request in the header of the at least one RLC PDU is parsed, and the receiving end does not include multiple RLCs because the MAC PDU includes multiple RLCs. PDU, and the header of each RLC PDU includes different polling bit values, which affects the receiving end is not sure how to send a status report.
  • FIG. 7 is a schematic flowchart diagram of another method for processing a status report according to an embodiment of the present invention.
  • the communication system includes an access network device and a terminal device, and the access network device communicates with the terminal device through an air interface.
  • the access network device may be a gNB in a 5G communication system or a base station of a next-generation communication system, and the gNB may adopt the architecture of the gNB of FIG. 3 or FIG. 4, and one of the access network devices and the terminal device is a transmitting end.
  • the other party is the receiving end. For example, when the access network device is the transmitting end, the terminal device is the receiving end, and vice versa.
  • Step 71 The receiving end receives a MAC PDU sent by the sending end, where the MAC PDU includes one or more RLC PDUs, where the status report sending request in the header of the one or more RLC PDUs is activated.
  • Step 72 When the receiving end determines that the status report sending request of the at least one RLC PDU in the MAC PDU is set to be activated, the status report is sent to the active state according to the status report to generate a status report.
  • Step 73 The receiving end sends a status report to the sending end.
  • the generating the status report according to the status report sending request to be activated includes: determining, according to the status report, that the sending request is set to an active state, determining a status of a last RLC PDU in the MAC PDU. The status of the report transmission request is activated, and a status report is generated based on the sequence number (SN) of the last RLC PDU.
  • one of the radio bearers or one RLC PDU corresponding to one logical channel or one of the plurality of RLC PDUs corresponding to one radio bearer or one logical channel in the MAC PDU The RLC PDU or a status report transmission request of the last one of the plurality of RLC PDUs corresponding to one radio bearer or one logical channel corresponding to one logical channel is not activated.
  • the receiving end determines that the MAC PDU is sent as the status report when the status report sending request in the header of the at least one RLC PDU is parsed, and the receiving end does not include multiple RLCs because the MAC PDU includes multiple RLCs. PDU, and the header of each RLC PDU includes different polling bit values, which affects the receiving end is not sure how to send a status report.
  • FIG. 8 is a schematic structural diagram of another apparatus for processing a status report according to another embodiment of the present invention.
  • the communication system includes an access network device and a terminal device, and the access network device communicates with the terminal device through an air interface.
  • the access network device may be a gNB in a 5G communication system or a base station of a next-generation communication system, and the gNB may adopt the architecture of the gNB of FIG. 3 or FIG. 4, and one of the access network devices and the terminal device is The transmitting end, and the other party is the receiving end. For example, when the access network device is the transmitting end, the terminal device is the receiving end, and vice versa.
  • the receiving end is a processing device for the status report
  • the data transmission device includes a receiver 81, a processor 82, a transmitter 83, and a memory 84, wherein the receiver 81 and the processor 82
  • the transmitter 83 and the memory 84 communicate with each other via a bus.
  • the processor 82 may be an EPLD, an FPGA, a DSP chip, an ASIC, or other programmable logic device, a discrete gate or a transistor logic device, a discrete hardware component, or the like.
  • the memory 84 is used to store code or instruction information, and may also store information of a device type.
  • the memory 84 can include ROM and RAM for providing instructions and data to the processor 82.
  • a portion of the memory 84 may also include a non-volatile random access memory.
  • the receiver 81 is configured to receive a MAC PDU sent by the sending end, where the MAC PDU includes one or more RLC PDUs, where a status report sending request in a header of one or more RLC PDUs is activated;
  • the processor 82 is configured to: when it is determined that the status report sending request of the at least one RLC PDU in the MAC PDU is set to be activated, generate a status report according to the status report sending request to be activated;
  • the transmitter 83 sends a status report to the sender.
  • the processor 82 is configured to determine, according to the status report sending request, that the status of the status report sending request of the last RLC PDU in the MAC PDU is activated, according to the last A sequence number (SN) of an RLC PDU generates a status report.
  • one of the radio bearers or one RLC PDU corresponding to one logical channel or one of the plurality of RLC PDUs corresponding to one radio bearer or one logical channel in the MAC PDU The RLC PDU or a status report transmission request of the last one of the plurality of RLC PDUs corresponding to one radio bearer or one logical channel corresponding to one logical channel is not activated.
  • the processing device that is the status report of the receiving end determines that the status report transmission request in the header of the at least one RLC PDU is determined to be the MAC PDU transmission status report, not because of the
  • the MAC PDU includes multiple RLC PDUs, and the header of each RLC PDU includes different polling bit values, which affects the receiving end is not sure how to send a status report.
  • the trigger needs to send a report sending request, which is called trigger polling.
  • the RLC entity of the sending end is separately triggered and sent, and may also be triggered and sent by the RLC entity and the MAC entity of the sending end, as described below.
  • the RLC entity of the sending end independently triggers the need to send a report sending request according to the triggering condition, that is, triggering the polling, and the polling bit needs to be set to 1 or 0, and then the RLC entity of the sending end selects or notifies the MAC layer of the sending end to select one.
  • the RLC PDU and the polling bit in the header of the selected RLC PDU needs to be set to 1 or 0.
  • BYTE_WITHOUT_POLL predetermined threshold
  • the restart status report sends a request retransmission timer (ie, a Polling retransmission timer) t-PollRetransmit)) Timeout.
  • Polling trigger method 1 RLC entity operates independently, based on PDU_WITHOUT_POLL
  • the RLC entity of the sending end determines that RLC polling is triggered after the number of RLC PDUs that have been sent but have not yet been required to send a status report is equal to or greater than a threshold after the last transmission status report transmission request is sent.
  • the polling bit in the RLC header of the next RLC PDU is set to 1, and then the RLC PDU is sent to the MAC entity of the sending end.
  • the RLC entity at the transmitting end resets its own saved "PDU_WITHOUT_POLL” and "BYTE_WITHOUT_POLL” to 0, and restarts "t-PollRetransmit".
  • the MAC entity of the sender determines when the RLC PDU with the polling bit of 1 is transmitted on the air interface.
  • Polling trigger method 2 RLC entity independent operation, based on BYTE_WITHOUT_POLL
  • the RLC entity of the sending end determines that the RLC polling is triggered after the total number of BYTEs (BYTE_WITHOUT_POLL) of the RLC PDU that has been sent but has not yet been sent to the status report is equal to or greater than the threshold since the last transmission status report transmission request is sent.
  • the polling bit in the RLC header of the next RLC PDU is set to 1, and then the RLC PDU is sent to the MAC entity of the sending end.
  • the RLC entity at the transmitting end resets its own saved "PDU_WITHOUT_POLL” and "BYTE_WITHOUT_POLL” to 0, and restarts "t-PollRetransmit".
  • the MAC entity of the sender determines when the RLC PDU with the polling bit of 1 is transmitted on the air interface.
  • Polling trigger method three RLC entity independent operation, based on t-PollRetransmit
  • the RLC entity of the sending end determines that t-PollRetransmit is started when the last triggering needs to send a report sending request, and the t-PollRetransmit timeout triggers RLC polling.
  • the polling bit in the RLC header of the next RLC PDU is set to 1, and then the RLC PDU is sent to the MAC entity of the sending end.
  • the RLC entity at the transmitting end resets its own saved "PDU_WITHOUT_POLL” and "BYTE_WITHOUT_POLL” to 0, and restarts "t-PollRetransmit".
  • the MAC entity of the sender determines when the RLC PDU with the polling bit of 1 is transmitted on the air interface.
  • the RLC entity of the sending end triggers the polling independently, and the MAC entity of the sending end is invisible to the triggering polling process.
  • the advantage is that the inter-layer functions are clearly separated and the flow is simple.
  • the polling trigger may also be a joint triggering of the RLC entity and the MAC entity of the sending end, as described below.
  • Polling trigger method four RLC entity and MAC entity work together, based on PDU_WITHOUT_POLL
  • the RLC entity of the sending end determines that RLC polling is triggered after the number of RLC PDUs (PDU_WITHOUT_POLL) that have been sent but have not yet been sent to report status is equal to or greater than the threshold after the last transmission status report transmission request is sent.
  • the first notification message is sent to the MAC entity of the sending end, where the first notification message carries information that the RLC entity of the sending end has triggered RLC polling.
  • the MAC entity of the sending end sends a second notification message to the RLC entity of the sending end, when the MAC PDU is delivered to the PHY entity of the sending end.
  • the second notification message carries information requesting to set the polling bit corresponding to the last RLC PDU in the MAC PDU, and the MAC entity of the sending end sends the RLC SN corresponding to the last RLC PDU to the RLC entity of the sending end. .
  • the RLC entity of the sending end sets the polling bit of the RLC PDU corresponding to the RLC SN, and then The RLC PDU corresponding to the RLC SN is sent to the MAC entity of the sending end, and the MAC entity of the sending end processes the RLC PDU corresponding to the RLC SN into a corresponding MAC PDU, and then sends the RLC PDU to the sending end.
  • the PHY entity sends.
  • the RLC entity at the transmitting end sends a RLC PDU packet with a sequence number of 35-38 to the The MAC entity at the sender is ready to send.
  • the counter PDU_WITHOUT POLL saved by the RLC entity of the sending end exceeds the threshold, and the RLC entity of the sending end Trigger RLC polling.
  • the RLC entity of the sending end notifies the MAC entity of the sending end that the RLC entity of the sending end has triggered RLC polling information.
  • the MAC entity of the sending end When the MAC entity of the sending end prepares to send a MAC PDU, it requests to notify the sending of the information that the polling bit corresponding to the last RLC PDU in the MAC PDU is set to 1 and the sequence number of the last RLC PDU is 37. After the RLC entity of the transmitting end receives the notification, the polling bit of the RLC PDU packet with the serial number of 37 is set to 1, and the RLC PDU with the serial number of 37 is sent to The MAC entity of the sender. The MAC entity of the sending end processes the RLC PDU data packet with the sequence number 35-37 into a MAC PDU, wherein the polling bit corresponding to the RLC PDU data packet with the serial number 37 is 1.
  • the variable t-PollRetransmit maintained by the sender is restarted from time T2.
  • the value of PDU_WITHOUT POLL starts from 1.
  • the polling bit is carried in the RLC PDU packet with sequence number 37.
  • the RLC PDU packet with sequence number 38 belongs to the packet. Polling, to be counted in the next round of PDU_WITHOUT POLL.
  • the value of BYTE_WITHOUT POLL starts from X (X is the size of the RLC PDU packet with serial number 38), and the polling bit is carried in the RLC PDU packet with serial number 37, and the serial number is RLC 38.
  • the PDU packet belongs to the BYTE_WITHOUT POLL that is not polled and is counted in the next round.
  • Polling trigger method five RLC entity and MAC entity work together, based on BYTE_WITHOUT_POLL
  • the RLC entity of the sending end determines that the RLC polling is triggered after the RLC PDU data quantity (BYTE_WITHOUT_POLL) that has been sent but has not yet been sent to the status report is equal to or greater than the threshold after the last transmission status report transmission request is sent.
  • the third notification message is sent to the MAC entity of the sending end, where the third notification message carries the information that the RLC entity of the sending end has triggered the RLC polling.
  • the MAC entity of the sending end sends a fourth notification message to the RLC entity of the sending end, when the MAC PDU is delivered to the PHY entity of the sending end.
  • the fourth notification message carries information requesting to set the polling bit corresponding to the last RLC PDU in the MAC PDU, and the MAC entity of the sending end sends the RLC SN corresponding to the last RLC PDU to the RLC entity of the sending end. .
  • the RLC entity of the sending end sets the polling bit of the RLC PDU corresponding to the RLC SN, and then The RLC PDU corresponding to the RLC SN is sent to the MAC entity of the sending end, and the MAC entity of the sending end processes the RLC PDU corresponding to the RLC SN into a corresponding MAC PDU, and then sends the RLC PDU to the sending end.
  • the PHY entity sends.
  • Polling trigger method six RLC entity and MAC entity work together, based on t-PollRetransmit
  • the RLC entity of the sending end determines that t-PollRetransmit is started when the last triggering needs to send a report sending request, and RLC polling is triggered when the t-PollRetransmit times out.
  • the third notification message is sent to the MAC entity of the sending end, where the third notification message carries the information that the RLC entity of the sending end has triggered the RLC polling.
  • the MAC entity of the sending end sends a fourth notification message to the RLC entity of the sending end, when the MAC PDU is delivered to the PHY entity of the sending end.
  • the fourth notification message carries information requesting to set the polling bit corresponding to the last RLC PDU in the MAC PDU, and the MAC entity of the sending end sends the RLC SN corresponding to the last RLC PDU to the RLC entity of the sending end. .
  • the RLC entity of the sending end sets the polling bit of the RLC PDU corresponding to the RLC SN, and then The RLC PDU corresponding to the RLC SN is sent to the MAC entity of the sending end, and the MAC entity of the sending end processes the RLC PDU corresponding to the RLC SN into a corresponding MAC PDU, and then sends the RLC PDU to the sending end.
  • the PHY entity sends.
  • the polling bit of the last RLC PDU in the MAC PDU is always set, so that the variables PDU_WITHOUT_POLL and BYTE_WITHOUT_POLL maintained by the sender reflect the latest. status.
  • the MAC entity of the sending end when the RLC entity of the sending end triggers the RLC polling, the MAC entity of the sending end is notified, and after receiving the notification, the MAC entity of the sending end requests the sending when generating the MAC PDU.
  • the RLC entity at the end sets the polling bit of the last RLC PDU to 1 and informs the RLC entity of the SN of the last RLC PDU.
  • the polling bit of any one or more RLC PDUs in the MAC PDU may also be set to 1 to speed up the processing.
  • the MAC entity does not need to wait for the LCP to end, and determines which RLC PDU is the last RLC PDU in the current MAC PDU, and then determines to add polling. Setting the polling bit in multiple RLC PDUs can increase the reliability of polling. If one of the polling bits in the transmission process is wrong, it can be compensated by other polling bits.
  • the physical layer entity may The 0-n CBs are directly generated to the MAC entity. If the MAC entity can identify the MAC SDU according to the 0-n CBs, the MAC entity submits the MAC SDU to the corresponding RLC entity. If the RLC entity receives the polling bit, it is found to be 1. , you can start RLC retransmission. In this scenario, one way of processing is that in the MAC PDU, the RLC entity selects the first RLC PDU among the plurality of RLC PDUs from the same RLC entity, and sets its polling bit to 1.
  • the receiving end after receiving the MAC PDU with polling, the receiving end sends only one status report regardless of the number of polling bits in the MAC PDU. . And when the status report is sent, only the current RLC has received those RLC PDUs, and those RLC PDUs are not received, and the polling bits are not considered to be received from the RLC header of that RLC PDU.
  • the MAC entity of the sending end after the RLC entity of the sending end triggers the RLC polling, the MAC entity of the sending end is not notified.
  • the MAC entity of the sending end When the MAC entity of the sending end generates the MAC PDU, the SN of the last RLC PDU in the MAC PDU is notified to the RLC entity of the sending end regardless of whether the last RLC PDU needs to be segmented.
  • FIG. 10 is a process state diagram of another method for triggering an RLC Polling according to another embodiment of the present invention.
  • the RLC entity of the transmitting end sends the last RLC PDU SN to the MAC entity of the sending end, and sets the polling bit of the last RLC PDU to 1. And is also sent to the MAC entity of the sending end, as shown in FIG. 11, which is another process state diagram for triggering the RLC Polling method according to another embodiment of the present invention.
  • the RLC PDU packet of the number the RLC PDU packet with the serial number of 38 belongs to the RLC polling that is not triggered, and the data 1 is counted in the next round of the PDU_WITHOUT POLL.
  • the RLC PDU packet whose serial number is No. 38 belongs to the RLC polling that is not triggered, so the X needs to be counted in the next round of BYTE_WITHOUT POLL.
  • the BYTE_WITHOUT POLL may have another way: starting from X (X is the part of the RLC PDU packet with serial number 37 that has not been transmitted yet.
  • X is the part of the RLC PDU packet with serial number 37 that has not been transmitted yet.
  • the PDU packet belongs to the RLC polling packet. Therefore, the data size of the RLC PDU packet with the serial number 38 needs to be counted in the next round of BYTE_WITHOUT POLL.
  • the polling bit bit of all or part of the following multiple RLC PDUs is set to 1, until the MAC entity of the sending end receives the polling The information that the bit has been sent.
  • the RLC entity of the transmitting end stops setting the RLCpolling bit of the RLC PDU of the MAC entity that is subsequently sent to the sending end, as shown in FIG. 12, which is another embodiment of the present invention.
  • the MAC entity of the sending end may indicate that the RLC PDU whose sequence number SN is 38 has been sent to the RLC entity of the sending end, or may request that the serial number SN be Segmentation information for the RLC PDU No. 38.
  • FIG. 13 is a process state diagram of another method for triggering an RLC Polling according to another embodiment of the present invention. As shown in FIG. 13, after the MAC entity of the sending end sends the air interface, the RLC entity of the sending end indicates that the last RLC PDU SN in the MAC PDU is 37, and the RLC entity of the sending end receives the information.
  • the RLC PDU data packet with the serial number of 38 is found to have been sent to the MAC entity of the sending end, and the corresponding polling bit is 1, so that the RLC entity of the sending end is again referred to the transmitting end.
  • the MAC entity sends the RLC PDU packet with sequence number 38 and sets the polling bit to zero.
  • FIG. 14 is a process state diagram of another method for triggering an RLC Polling according to another embodiment of the present invention.
  • the RLC entity of the sending end determines to trigger RLC polling, it sends a notification message to the MAC, where the notification is sent.
  • the message may or may not carry an RLC PDU SN band.
  • the MAC entity of the sending end sets the polling bit of the RLC PDU corresponding to the RLC PDU SN to 1; if the notification message does not carry the RLC PDU SN, the sending end The MAC entity determines, according to the timing of receiving the notification message, which polling bit of the RLC PDU is set to 1, for example, after the MAC entity of the sending end receives the notification message, the next one from the transmitting end The polling bit of the RLC PDU received by the RLC entity is set to 1.
  • the MAC entity of the sending end may also set the polling bit of one or more RLC PDUs to be sent in the air interface.
  • FIG. 15 is a process state diagram of another method for triggering an RLC Polling according to another embodiment of the present invention.
  • the MAC entity of the sending end finds that multiple RLC PDUs are in the same logical channel. And sending the multiple RLC PDUs to the RLC entity of the sending end, and indicating that the multiple RLC PDUs are from the same MAC PDU.
  • FIG. 16 is a schematic diagram of a data structure of an RLC control PDU according to an embodiment of the present invention.
  • the RLC control PDU in this embodiment may be used to implement a polling function in the NR, and use an RLC Control PDU. Instructs the receiving end to send a status report.
  • D/C indicates whether the PDU is a data PDU or a control PDU
  • CPT indicates the type of the control PDU, and can be set to any CPT value different from the existing CPT
  • POLL_SN Indicates the SN of the RLC control PDU that triggers the status report.
  • the SN value may be the value of the POLL_SN that generates the status report based on its corresponding RLC PDU, or may be the SN value of other RLC PDUs in the current transmission window, in FIG.
  • the example is the case where the SN is 10 bits, but the specific case is not limited to the SN length.
  • each field is merely an example. In an implementation, each field may use a different length.
  • FIG. 17 is a schematic structural diagram of an RLC status PDU according to another embodiment of the present invention, where the RLC status PDU is used to implement status report feedback in the NR.
  • the value of the VR(R) indicates the sequence number of the RLC PDU and is the sequence number corresponding to the RLC PDU that the receiving end currently expects to receive
  • VR (MS) The value of the RLC PDU indicates the sequence number of the RLC PDU plus one for the sequence number corresponding to the highest RLC PDU currently received by the receiving end.
  • the RLC_SN_LENGTH indicates the number of bits occupied by the RLC SN field
  • the AMD PDU is an RLC PDU in an RLC AM mode
  • the AMD SDU is an RLC SDU in an RLC AM mode.
  • the parameters of the RLC status report format are as follows.
  • D/C indicates whether the PDU is a data PDU or a control PDU.
  • Control PDU TYPE, CPT indicates the type of the control PDU, which can be set to any CPT value different from the existing CPT.
  • the NACK_SN is the SN value of the AMD SDU or AMD SDU segment that the receiving end considers to be lost.
  • E1 indicates whether "NACK_SN_START+NACK_SN_END+E1+E2+E3" or "ACK_SN+E1" is followed by another "NACK_SN_START+NACK_SN_END+E1+E2+E3" combination.
  • a value of 0 corresponds to "No”
  • a value of 1 corresponds to "Yes”.
  • the NACK_SN_START is an SN indicating a first RLC PDU of a plurality of consecutive RLC PDUs that are not received by the receiving end
  • the NACK_SN_END is a last RLC PDU of the plurality of consecutive RLC PDUs that are not received by the receiving end.
  • E2 indicates whether "RANEstart” is followed by the combination of "NACK_SN_START+NACK_SN_END+E1+E2+E3".
  • a value of 0 corresponds to "No”, indicating that the first PDU is a complete SDU; a value of 1 corresponds to "Yes”, indicating that the first PDU is an RLC SDU segment.
  • the RANGEstart indicates that the RLC SDU segment (RLC SDU segement) is in a starting position in the RLC SDU corresponding to the NACK_SN_START.
  • E3 indicates whether "RANGEend” is followed by the combination of "NACK_SN_START+NACK_SN_END+E1+E2+E3".
  • a value of 0 corresponds to "No”, indicating that the last PDU is a complete RLC SDU; a value of 1 corresponds to "Yes”, indicating that the last PDU is an RLC SDU segment.
  • ACK_SN indicates that all packets have been received before the SN except that NACK_SN indicates a lost packet.
  • the RLC status report format is mainly applied to the case of a lost RLC PDU or a large number of segments.
  • the RRC configuration can be used to implement the conversion with the other status PDU formats described above.
  • the lengths of the NACK_SN_START and the NACK_SN_END are the same. In another embodiment of the present invention, the lengths of the NACK_SN_START and the NACK_SN_END may also be different.
  • the length of the NACK_SN_END is smaller than the length of the NACK_SN_START, for example, NACK_SN_END
  • the length is S bits
  • the length of NACK_SN_START is L bits
  • L> S
  • this format indicates that the upper bits of NACK_SN_END (total LS bits) are the same as the upper bits of NACK_SN_START, the lower bits of NACK_SN_END (total S bits) and the lower bits of NACK_SN_START The bits are different.
  • FIG. 17 is a schematic structural diagram of another RLC status PDU according to another embodiment of the present invention, where the RLC status PDU is used to implement status report feedback in the NR.
  • the status feedback report for the NR defines a format as shown in FIG.
  • VR(R) indicates the sequence number of the RLC PDU and is the sequence number corresponding to the RLC PDU that the receiving end currently desires to receive
  • VR The value of (MS) indicates the sequence number of the RLC PDU and is incremented by 1 for the sequence number corresponding to the highest RLC PDU currently received by the receiving end.
  • the RLC_SN_LENGTH indicates the number of bits occupied by the RLC SN field
  • the AMD PDU is an RLC PDU in an RLC AM mode
  • the AMD SDU is an RLC SDU in an RLC AM mode.
  • the parameters of the RLC status report format are as follows.
  • the D/C bit indicates whether the RLC PDU is an RLC data PDU or an RLC control PDU, and the D/C bit is 0, indicating that the corresponding RLC PDU is an RLC data PDU, and the D/C bit is 1, indicating that the corresponding RLC PDU is an RLC. Control PDU.
  • the type of control PDU indicates the type of the RLC control PDU. For example, a CPT value of 1 indicates that the RLC control PDU is an RLC status report, and a CPT value of 0 indicates that the RLC control PDU is another type of RLC control PDU. .
  • E1 indicates whether "NACK_SN_START+NACK_SN_END+E1+E2+E3" or "ACK_SN+E1" is followed by another "NACK_SN_START+NACK_SN_END+E1+E2+E3" combination.
  • the NACK_SN_START is an SN indicating a first RLC PDU of a plurality of consecutive RLC PDUs that are not received by the receiving end
  • the NACK_SN_END is a last RLC PDU of the plurality of consecutive RLC PDUs that are not received by the receiving end.
  • E2 indicates whether "RANEstart” is followed by the combination of "NACK_SN_START+NACK_SN_END+E1+E2+E3".
  • the E2 value is 0, it corresponds to "No", indicating that the first PDU is a complete SDU; when the E2 value is 1, it corresponds to "Yes", indicating that the first PDU is an RLC SDU segment.
  • the RANGEstart indicates that the RLC SDU segment (RLC SDU segement) is in a starting position in the RLC SDU corresponding to the NACK_SN_START.
  • the first byte in the RLC SDU segment is at the byte position in the RLC SDU corresponding to NACK_SN_START.
  • E3 indicates whether "RANGEend” is followed by the combination of "NACK_SN_START+NACK_SN_END+E1+E2+E3".
  • the E3 value is 0, it corresponds to "No", indicating that the last RLC PDU is a complete RLC SDU; when the E3 value is 1, it corresponds to "Yes", indicating that the last RLC PDU is an RLC SDU segment.
  • the RANGEend indicates that the RLC SDU segment is in the last position in the RLC SDU corresponding to the NACK_SN_END, that is, the byte position of the last byte in the RLC SDU segment in the RLC SDU corresponding to the NACK_SN_END.
  • ACK_SN indicates that all packets have been received before the SN except that NACK_SN indicates a lost packet. In another embodiment of the present invention, ACK_SN indicates that other packets have been received before the SN except that NACK_SN_START to the corresponding NACK_SN_END indicates consecutively lost packets.
  • the RLC status report format is mainly applied to the case of a lost RLC SDU or a large number of segments.
  • the RRC configuration can be used to implement the conversion with the other status PDU formats described above.
  • FIG. 18 is a schematic structural diagram of an RLC status PDU according to another embodiment of the present invention, where the RLC status PDU is used to implement status report feedback in the NR.
  • the status report is generated from the arrival, so the state needs to be generated.
  • the parameters of another RLC status report format are as follows.
  • D/C indicates whether the PDU is a data PDU or a control PDU.
  • CPT indicates the type of the control PDU, which can be set to any CPT value different from the existing CPT.
  • the NACK_SN is the SN value of the AMD PDU or AMD PDU segment that the receiving end considers to be lost.
  • E1 indicates whether "NACK_SN_START+E2+RANGEstart+NACK_SN_END+E3+RANGEend” or "ACK_SN+E1" is followed by another "NACK_SN_START+E2+RANGEstart+NACK_SN_END+E3+RANGEend” combination.
  • a value of 0 corresponds to "No”
  • a value of 1 corresponds to "Yes”.
  • the RANGEstart indicates that the RLC SDU segment (RLC SDU segement) is in a starting position in the RLC SDU corresponding to the NACK_SN_START.
  • the RANGEend indicates that the RLC SDU segment (RLC SDU segement) is the last position in the RLC SDU corresponding to the NACK_SN_START.
  • E2 indicates whether "RANGEstart” is followed by "NACK_SN_START".
  • a value of 0 corresponds to "No”, indicating that the first PDU is a complete SDU; a value of 1 corresponds to "Yes”, indicating that the first PDU is an RLC SDU segment.
  • E3 indicates whether "RANGEend” is followed by "NACK_SN_END”.
  • a value of 0 corresponds to "No”, indicating that the last PDU is a complete SDU; a value of 1 corresponds to "Yes”, indicating that the last PDU is an RLC SDU segment.
  • ACK_SN indicates that all packets have been received before the SN except that NACK_SN indicates a lost packet.
  • the status report format is mainly applied to the case of a lost RLC PDU or a large number of segments.
  • the RRC configuration can be used to implement the conversion with other status PDU formats.
  • This format indicates that the upper bits of the NACK_SN_END (total LS bits) are the same as the upper bits of the NACK_SN_START, and the lower bits of the NACK_SN_END (the total S bits) are different from the lower bits of the NACK_SN_START. .
  • FIG. 18 is a schematic structural diagram of another RLC status PDU according to another embodiment of the present invention, where the RLC status PDU is used to implement status report feedback in the NR.
  • the status report is generated from the arrival, so the state needs to be generated.
  • the parameters of another of the RLC status report formats are as follows.
  • the D/C bit indicates whether the RLC PDU is an RLC data PDU or an RLC control PDU, and the D/C bit is 0, indicating that the corresponding RLC PDU is an RLC data PDU, and the D/C bit is 1, indicating that the corresponding RLC PDU is an RLC. Control PDU.
  • CPT indicates the type of the RLC control PDU. For example, a CPT value of 1 indicates that the RLC control PDU is an RLC status report, and a CPT value of 0 indicates that the RLC control PDU is another type of RLC control PDU.
  • E1 indicates whether "NACK_SN_START+E2+RANGEstart+NACK_SN_END+E3+RANGEend” or "ACK_SN+E1" is followed by another "NACK_SN_START+E2+RANGEstart+NACK_SN_END+E3+RANGEend” combination.
  • the RANGEstart indicates that the RLC SDU segment (RLC SDU segement) is in a starting position in the RLC SDU corresponding to the NACK_SN_START.
  • the RANGEend indicates that the RLC SDU segment (RLC SDU segement) is the last position in the RLC SDU corresponding to the NACK_SN_START.
  • E1 may also indicate whether "NACK_SN_START+E2+RANGEstart+NACK_SN_END+E3+RANGEend” or "ACK_SN+E1" is followed by another "NACK_SN_START+E2+RANGEstart+NACK_SN_END+E3" +RANGEend” combination.
  • E1 value When the E1 value is 0, it corresponds to "No", and when the E1 value is 1, it corresponds to "Yes”.
  • the NACK_SN_START is an SN indicating a first RLC PDU of the plurality of consecutive RLC PDUs that are not received by the receiving end, and the NACK_SN_END is the last one of the plurality of consecutive RLC PDUs that are not received by the receiving end.
  • the RANGEstart indicates the starting position of the RLC SDU segment (RLC SDU segement) in the RLC SDU corresponding to the NACK_SN_START, that is, the byte position of the first byte in the RLC SDU segment in the RLC SDU corresponding to the NACK_SN_START.
  • the RANGEend indicates the last position in the RLC SDU corresponding to the RLC SDU segment (RLC SDU segement), that is, the byte position of the last byte in the RLC SDU segment in the RLC SDU corresponding to the NACK_SN_END.
  • E2 indicates whether "RANGEstart” is followed by "NACK_SN_START”. When the E2 value is 0, it corresponds to "No", indicating that the first PDU is a complete SDU; when the E2 value is 1, it corresponds to "Yes", indicating that the first PDU is an RLC SDU segment.
  • E3 indicates whether "RANGEend” is followed by "NACK_SN_END”. When the E3 value is 0, it corresponds to "No", indicating that the last PDU is a complete SDU; when the E3 value is 1, it corresponds to "Yes”, indicating that the last PDU is an RLC SDU segment.
  • ACK_SN indicates that all packets have been received before the SN except that NACK_SN indicates a lost packet. In another embodiment of the present invention, ACK_SN indicates that other packets have been received before the SN except that NACK_SN_START to the corresponding NACK_SN_END indicates consecutively lost packets.
  • the status report format is mainly applied to the case of a lost RLC SDU or a large number of segments.
  • the RRC configuration can be used to implement the conversion with other status PDU formats.
  • FIG. 19 is a schematic structural diagram of an RLC status PDU according to another embodiment of the present invention, where the RLC status PDU is used to implement status report feedback in the NR.
  • D/C indicates whether the PDU is a data PDU or a control PDU.
  • CPT indicates the type of the control PDU, which can be set to any CPT value different from the existing CPT.
  • the NACK_SN is the SN value of the AMD SDU or AMD SDU segment that the receiving end considers to be lost.
  • E1 indicates whether "NACK_SN+E1+E2+E3+RANGEstart+RANGEend” or "ACK_SN+E1" is followed by another "NACK_SN+E1+E2+E3+RANGEstart+RANGEend” combination.
  • a value of 0 corresponds to "No"
  • a value of 1 corresponds to "Yes”.
  • E2 indicates whether "RANGEstart+RANGEend” is followed immediately after "NACK_SN_START”. A value of 0 corresponds to "No”, indicating that the complete SDU is lost; a value of 1 corresponds to "Yes”, indicating that one segment of the SDU is lost.
  • E3 indicates whether "RANGEstart+RANGEend” is followed by "RANGEstart+RANGEend”.
  • a value of 0 corresponds to "No”, indicating that the combination is the last one in the current RLC SDU; a value of 1 corresponds to "Yes”, indicating that a "RANGEstart+RANGEend” is still followed.
  • ACK_SN indicates that all packets have been received before the SN except that NACK_SN indicates a lost packet.
  • FIG. 19 is a schematic structural diagram of another RLC status PDU according to another embodiment of the present invention, where the RLC status PDU is used to implement status report feedback in the NR.
  • the D/C bit indicates whether the RLC PDU is an RLC data PDU or an RLC control PDU, and the D/C bit is 0, indicating that the corresponding RLC PDU is an RLC data PDU, and the D/C bit is 1, indicating that the corresponding RLC PDU is an RLC. Control PDU.
  • CPT indicates the type of the RLC control PDU. For example, a CPT value of 1 indicates that the RLC control PDU is an RLC status report, and a CPT value of 0 indicates that the RLC control PDU is another type of RLC control PDU.
  • the NACK_SN is the SN value of the AMD SDU or AMD SDU segment that the receiving end considers to be lost.
  • E1 indicates whether “NACK_SN+E1+E2+E3+RANGEstart+RANGEend” or "ACK_SN+E1" is followed by another "NACK_SN+E1+E2+E3+RANGEstart+RANGEend” combination.
  • E1 value When the E1 value is 0, it corresponds to "No", and when the E1 value is 1, it corresponds to "Yes".
  • E2 indicates whether "RANGEstart+RANGEend” is followed immediately after "NACK_SN_START”. When the value of E2 is 0, it corresponds to "No", indicating that the complete SDU is lost; when the value of E2 is 1, it corresponds to "Yes", indicating that one segment of the SDU is lost.
  • E2 may also indicate whether "RANEstart+RANGEend" is followed by "NACK_SN".
  • NACK_SN When the value of E2 is 0, it corresponds to "No", indicating that the complete SDU is lost; when the value of E2 is 1, it corresponds to "Yes”, indicating that one segment of the SDU is lost.
  • the RANGEstart indicates the starting position of the RLC SDU segment in the RLC SDU corresponding to the NACK_SN, that is, the byte position of the first byte in the RLC SDU segment in the RLC SDU corresponding to the NACK_SN.
  • the RANGEend indicates the last position of the RLC SDU segment in the RLC SDU corresponding to the NACK_SN, that is, the byte position of the last byte in the RLC SDU segment in the RLC SDU corresponding to the NACK_SN.
  • E3 indicates whether "RANGEstart+RANGEend” is followed by "RANGEstart+RANGEend”. If the E3 value is 0, it corresponds to "No", indicating that the combination is the last one in the current RLC SDU; when the E3 value is 1, it corresponds to "Yes", indicating that it is still followed by a "RANGEstart+RANGEend”.
  • ACK_SN indicates that all packets have been received before the SN except that NACK_SN indicates a lost packet.
  • This status report is especially useful when the data packet is particularly large, such as the jumbo packet that NR agrees to support.
  • the conversion with the other status PDU formats described above can be implemented by the RRC configuration. According to the format of the above FIG. 19 or 19a, there are three combinations, as shown in Table 3.
  • the receiving end if the receiving end considers that the segments that are not received are relatively scattered, it is also possible to collectively feed back a relatively large segment to reduce the size of the RLC status report. For example, the three small segments of 20-22, 25-28, and 30-45 are not received.
  • the receiving end generates a status report, notifying the sender that the "20-45" segment has not been received. Please retransmit.
  • FIG. 20 is a schematic structural diagram of an RLC status PDU according to another embodiment of the present invention, where the RLC status PDU is used to implement status report feedback in the NR.
  • D/C indicates whether the PDU is a data PDU or a control PDU.
  • CPT indicates the type of the control PDU, which can be set to any CPT value different from the existing CPT.
  • the NACK_SN is the SN value of the AMD PDU or AMD PDU segment that the receiving end considers to be lost.
  • E1 indicates whether "NACK_SN_START+E3+RANGEend” or "ACK_SN+E1" is followed by another "NACK_SN_START+E2+RANGEstart+bitmap+E3+RANGEend” combination. A value of 0 corresponds to "No", and a value of 1 corresponds to "Yes”.
  • E2 indicates whether "RANGEstart” is followed by "NACK_SN_START".
  • a value of 0 corresponds to "No”, indicating that the first PDU is a complete SDU; a value of 1 corresponds to "Yes”, indicating that the first PDU is an RLC SDU segment.
  • Bitmap is used to indicate whether the RLC SDU or segment at the corresponding location is lost. If lost, the value of the bitmap is 0; otherwise, the value of the bitmap is 1. In the example in the figure, the length of the bitmap is 10 bits, but the application is not limited to the length of 10 bits.
  • E3 indicates whether or not "RANGEend” is followed immediately.
  • a value of 0 corresponds to "No”, indicating that the RLC PDU indicated by the last bit in the bitmap is a completely lost RLC SDU; a value of 1 corresponds to "Yes”, indicating that the last bit in the bitmap is 0.
  • the loss of the RLC PDU is segmentation.
  • ACK_SN indicates that all packets have been received before the SN except that NACK_SN indicates a lost packet.
  • This status report is especially useful when the package is particularly large, such as the jumbo packet that NR agrees to support.
  • FIG. 20 is a schematic structural diagram of another RLC status PDU according to another embodiment of the present invention, where the RLC status PDU is used to implement status report feedback in the NR.
  • the D/C bit indicates whether the RLC PDU is an RLC data PDU or an RLC control PDU, and the D/C bit is 0, indicating that the corresponding RLC PDU is an RLC data PDU, and the D/C bit is 1, indicating that the corresponding RLC PDU is an RLC. Control PDU.
  • CPT indicates the type of the RLC control PDU. For example, a CPT value of 1 indicates that the RLC control PDU is an RLC status report, and a CPT value of 0 indicates that the RLC control PDU is another type of RLC control PDU.
  • E1 indicates whether "NACK_SN_START+E3+RANGEend” or "ACK_SN+E1" is followed by another "NACK_SN_START+E2+RANGEstart+bitmap+E3+RANGEend” combination.
  • the E1 value is 0, it corresponds to "No", and when the E1 value is 1, it corresponds to "Yes”.
  • the NACK_SN_START is an SN indicating an RLC PDU indicated by the first bit in the bitmap.
  • E2 indicates whether "RANGEstart” is followed by "NACK_SN_START". When the E2 value is 0, it corresponds to "No", indicating that the first PDU is a complete SDU; when the E2 value is 1, it corresponds to "Yes", indicating that the first PDU is an RLC SDU segment.
  • the RANGEstart indicates that the RLC SDU segment is in a starting position in the RLC SDU corresponding to the NACK_SN_START, that is, the first byte in the RLC SDU segment is in the RLC SDU corresponding to the NACK_SN_START. Byte position.
  • Bitmap is used to indicate whether the RLC SDU or segment at the corresponding location is lost. If lost, the value of the bitmap is 0; otherwise, the value of the bitmap is 1. In the example in the figure, the length of the bitmap is 10 bits, but the application is not limited to the length of 10 bits.
  • E3 indicates whether or not "RANGEend” is followed immediately.
  • the E3 value When the E3 value is 0, it corresponds to "No", indicating that the RLC PDU indicated by the last bit in the bitmap is a completely lost RLC SDU; when the E3 value is 1, it corresponds to "Yes", indicating that the last bit in the bitmap is 0.
  • the indicated RLC PDU is lost is the segmentation of the RLC SDU.
  • the RANGEend indicates the last position of the RLC SDU segment in the corresponding RLC SDU, that is, the byte position of the last byte in the RLC SDU segment in the corresponding RLC SDU.
  • ACK_SN indicates that all packets have been received before the SN except that NACK_SN indicates a lost packet.
  • This status report is especially useful when the package is particularly large, such as the jumbo packet that NR agrees to support.
  • FIG. 21 is a schematic structural diagram of an RLC status PDU according to another embodiment of the present invention, where the RLC status PDU is used to implement status report feedback in the NR.
  • D/C indicates whether the PDU is a data PDU or a control PDU.
  • CPT indicates the type of the control PDU, which can be set to any CPT value different from the existing CPT.
  • the NACK_SN is the SN value of the AMD PDU or AMD PDU segment that the receiving end considers to be lost.
  • E1 indicates whether "NACK_SN_START+E2++RANGEstart+SN_RANGE+E3+RANGEend” or "ACK_SN+E1" is followed by another "NACK_SN_START+E2+RANGEstart+SN_RANGE+E3+RANGEend” combination.
  • a value of 0 corresponds to "No"
  • a value of 1 corresponds to "Yes”.
  • E2 indicates whether "RANGEstart” is followed by "NACK_SN_START".
  • a value of 0 corresponds to "No", indicating that the first PDU is a complete SDU; a value of 1 corresponds to "Yes", indicating that the first PDU is an RLC SDU segment.
  • SN_RANGE is used to indicate the number of consecutive lost RLC PDUs or segments after NACK_SN_START. The figure is represented by 10 bits, and in reality, it is not limited to this case.
  • E3 indicates whether or not "RANGEend” is followed immediately.
  • a value of 0 corresponds to "No”, indicating that the last RLC PDU indicated by SN_RANGE is a completely lost RLC SDU;
  • a value of 1 corresponds to "Yes”, indicating that the last RLC PDU indicated by SN_RANGE is missing an RLC SDU segment. .
  • ACK_SN indicates that all packets have been received before the SN except that NACK_SN indicates a lost packet.
  • This status report is flexible and can indicate different cases in which the number of consecutively lost packets is 0 to 1024.
  • FIG. 21 is a schematic structural diagram of another RLC status PDU according to another embodiment of the present invention.
  • the RLC status PDU is used to implement status report feedback in the NR.
  • the D/C bit indicates whether the RLC PDU is an RLC data PDU or an RLC control PDU, and the D/C bit is 0, indicating that the corresponding RLC PDU is an RLC data PDU, and the D/C bit is 1, indicating that the corresponding RLC PDU is an RLC. Control PDU.
  • CPT indicates the type of the RLC control PDU. For example, a CPT value of 1 indicates that the RLC control PDU is an RLC status report, and a CPT value of 0 indicates that the RLC control PDU is another type of RLC control PDU.
  • E1 indicates whether “NACK_SN_START+E2++RANGEstart+SN_RANGE+E3+RANGEend” or "ACK_SN+E1" is followed by another "NACK_SN_START+E2+RANGEstart+SN_RANGE+E3+RANGEend” combination.
  • E1 When E1 is 0, it corresponds to "No", and when E1 is 1, it corresponds to "Yes".
  • NACK_SN_START represents the SN of the first RLC PDU of the plurality of consecutive RLC PDUs that are not received by the receiving end.
  • E2 indicates whether "RANGEstart” is followed by "NACK_SN_START". When the E2 value is 0, it corresponds to "No", indicating that the first PDU is a complete SDU; when the E2 value is 1, it corresponds to "Yes", indicating that the first PDU is an RLC SDU segment.
  • the RANGEstart indicates a starting position of the RLC SDU segment in the RLC SDU corresponding to the NACK_SN_START, that is, the first byte in the RLC SDU segment is in the RLC SDU corresponding to the NACK_SN_START Byte position.
  • SN_RANGE is used to indicate the number of consecutive lost RLC PDUs or segments after NACK_SN_START.
  • the consecutive lost RLC PDU corresponding to the SN_RANGE includes the first lost RLC PDU corresponding to the NACK_SN_START, and includes the last lost RLC PDU. At this time, if there is only one missing RLC PDU, the SN_RANGE value is 1.
  • the continuously lost RLC PDU corresponding to the SN_RANGE may not include the first lost RLC PDU corresponding to the NACK_SN_START, and includes the last lost RLC PDU. At this time, if there is only one missing RLC PDU, the SN_RANGE value is 0.
  • the continuously lost RLC PDU corresponding to the SN_RANGE may include the first lost RLC PDU corresponding to the NACK_SN_START, and does not include the last lost RLC PDU. At this time, if there is only one missing RLC PDU, the SN_RANGE value is 0.
  • E3 indicates whether or not "RANGEend” is followed immediately. If the value of E3 is 0, it corresponds to "No", indicating that the last RLC PDU indicated by SN_RANGE is a completely lost RLC SDU; when the value of E3 is 1, it corresponds to "Yes", indicating that the last RLC PDU indicated by SN_RANGE is missing the RLC SDU. Segmentation.
  • the RANGEend indicates the last position of the RLC SDU segment in the corresponding RLC SDU, that is, the byte position of the last byte in the RLC SDU segment in the corresponding RLC SDU.
  • ACK_SN indicates that all packets have been received before the SN except that NACK_SN indicates a lost packet. In another embodiment of the invention, ACK_SN indicates that other packets have been received before the SN except for packets that are continuously lost starting from NACK_SN_START.
  • This status report is flexible and can indicate different cases in which the number of consecutively lost packets is 0 to 1024.
  • FIG. 21b is a schematic structural diagram of another RLC status PDU according to another embodiment of the present invention, where the RLC status PDU is used to implement status report feedback in the NR.
  • the D/C bit indicates whether the RLC PDU is an RLC data PDU or an RLC control PDU, and the D/C bit is 0, indicating that the corresponding RLC PDU is an RLC data PDU, and the D/C bit is 1, indicating that the corresponding RLC PDU is an RLC. Control PDU.
  • CPT indicates the type of the RLC control PDU. For example, a CPT value of 1 indicates that the RLC control PDU is an RLC status report, and a CPT value of 0 indicates that the RLC control PDU is another type of RLC control PDU.
  • E1 indicates whether "NACK_SN_START+RANGEstart+SN_RANGE+RANGEend” or "ACK_SN+E1" is followed by another "NACK_SN_START+RANGEstart+SN_RANGE+RANGEend” combination.
  • E1 value When the E1 value is 0, it corresponds to "No", and when the E1 value is 1, it corresponds to "Yes”.
  • NACK_SN_START is an SN indicating the first RLC PDU of a plurality of consecutive RLC PDUs that are not received by the receiving end.
  • RANGEstart indicates the starting position of the complete RLC SDU or RLC SDU segment corresponding to the first lost RLC PDU in the RLC SDU corresponding to the NACK_SN_START, that is, the complete RLC SDU or RLC SDU corresponding to the first lost RLC PDU.
  • the first byte in the segment is at the byte position in the RLC SDU corresponding to NACK_SN_START.
  • RANGEend indicates the last position of the complete RLC SDU or RLC SDU segment corresponding to the last lost RLC PDU in the corresponding RLC SDU, that is, the last one of the complete RLC SDU or RLC SDU segment corresponding to the last lost RLC PDU.
  • the continuously lost RLC PDU corresponding to the SN_RANGE includes the first lost RLC PDU corresponding to the NACK_SN_START, and includes the last lost RLC PDU. At this time, if there is only one missing RLC PDU, the SN_RANGE value is 1.
  • the continuously lost RLC PDU corresponding to the SN_RANGE may not include the first lost RLC PDU corresponding to the NACK_SN_START, and includes the last lost RLC PDU. At this time, if there is only one missing RLC PDU, the SN_RANGE value is 0.
  • the continuously lost RLC PDU corresponding to the SN_RANGE may include the first lost RLC PDU corresponding to the NACK_SN_START, and does not include the last lost RLC PDU. At this time, if there is only one missing RLC PDU, the SN_RANGE value is 0. ACK_SN indicates that before the SN, all packets except the one that has been continuously lost from NACK_SN_START have been received.
  • FIG. 22 is a schematic structural diagram of an RLC status PDU according to another embodiment of the present invention, where the RLC status PDU is used to implement status report feedback in the NR.
  • D/C indicates whether the PDU is a data PDU or a control PDU.
  • CPT indicates the type of the control PDU, which can be set to any CPT value different from the existing CPT.
  • the NACK_SN is the SN value of the AMD SDU or AMD SDU segment that the receiving end considers to be lost.
  • E1 indicates whether "NACK_SN_START+E2+RANGEstart+NACK_SN_END+E3+RANGEend” or "ACK_SN+E1" is followed by another "NACK_SN_START+E2+RANGEstart+NACK_SN_END+E3+RANGEend” combination.
  • a value of 0 corresponds to "No”
  • a value of 1 corresponds to "Yes”.
  • E2 indicates whether "RANGEstart” is followed by "NACK_SN_START".
  • a value of 0 corresponds to "No”, indicating that the first PDU is a complete SDU; a value of 1 corresponds to "Yes”, indicating that the first PDU is an RLC SDU segment.
  • E3 indicates whether "RANGEend” is followed by "NACK_SN_END”.
  • a value of 0 corresponds to "No”, indicating that the last PDU is a complete SDU; a value of 1 corresponds to "Yes”, indicating that the last PDU is an RLC SDU segment.
  • ACK_SN indicates that all packets have been received before the SN except that NACK_SN indicates a lost packet.
  • NACK_SN_START NACK_SN_END.
  • FIG. 22 is a schematic structural diagram of another RLC status PDU according to another embodiment of the present invention.
  • the RLC status PDU is used to implement status report feedback in the NR.
  • the D/C bit indicates whether the RLC PDU is an RLC data PDU or an RLC control PDU, and the D/C bit is 0, indicating that the corresponding RLC PDU is an RLC data PDU, and the D/C bit is 1, indicating that the corresponding RLC PDU is an RLC. Control PDU.
  • CPT indicates the type of the RLC control PDU. For example, a CPT value of 1 indicates that the RLC control PDU is an RLC status report, and a CPT value of 0 indicates that the RLC control PDU is another type of RLC control PDU.
  • E1 indicates whether "NACK_SN_START+E2+RANGEstart+NACK_SN_END+E3+RANGEend” or "ACK_SN+E1" is followed by another "NACK_SN_START+E2+RANGEstart+NACK_SN_END+E3+RANGEend” combination.
  • the NACK_SN_START is an SN indicating a first RLC PDU of the plurality of consecutive RLC PDUs that are not received by the receiving end
  • the NACK_SN_END is the last one of the plurality of consecutive RLC PDUs that are not received by the receiving end.
  • E2 indicates whether "RANGEstart” is followed by "NACK_SN_START".
  • the E2 value is 0, it corresponds to "No", indicating that the first PDU is a complete SDU; when the E2 value is 1, it corresponds to "Yes", indicating that the first PDU is an RLC SDU segment.
  • the RANGEstart indicates the starting position of the RLC SDU segment (RLC SDU segement) in the RLC SDU corresponding to the NACK_SN_START, that is, the byte position of the first byte in the RLC SDU segment in the RLC SDU corresponding to the NACK_SN_START.
  • E3 indicates whether "RANGEend” is followed by "NACK_SN_END". When the E3 value is 0, it corresponds to "No", indicating that the last PDU is a complete SDU; when the E3 value is 1, it corresponds to "Yes”, indicating that the last PDU is an RLC SDU segment.
  • the RANGEend indicates that the RLC SDU segment is in the last position in the RLC SDU corresponding to the NACK_SN_END, that is, the byte position of the last byte in the RLC SDU segment in the RLC SDU corresponding to the NACK_SN_END.
  • ACK_SN indicates that all packets have been received before the SN except that NACK_SN indicates a lost packet. In another embodiment of the present invention, ACK_SN indicates that before the SN, except for NACK_SN_START to the corresponding NACK_SN_END indicating consecutively lost packets, all other packets have been received.
  • NACK_SN_START NACK_SN_END.
  • the present invention provides a plurality of structures.
  • FIG. 23 it is a schematic structural diagram of a packet header of an RLC PDU according to an embodiment of the present invention.
  • the base station sends the RRC signaling to the base station and the terminal device, and instructs the base station and the terminal device to set the length of the segment offset (SO) field and the length of the length (L) field of the respective RLC entity and the MAC entity.
  • SO field represents an offset of the RLC SDU segment relative to the starting position in the RLC SDU corresponding to the NACK_SN_START
  • L field represents the length of the RLC PDU in the MAC PDU.
  • the base station sends RRC signaling to the base station and the terminal device, indicating a setting regarding the length of the L domain of the MAC entity and the SO domain of the RLC: the MAC understands this setting as the length of the L domain, and the RLC entity interprets this setting as the SO domain.
  • the length of the L domain of the MAC entity is equal to the length of the SO domain of the RLC entity.
  • the SO domain of the RLC packet header has the same length as the L domain of the MAC entity, and there is no F domain, and the F domain indicates the length of the L domain.
  • F2 is used to indicate the length of the L domain.
  • the MAC entity notifies the length of the L domain of the RLC entity after removing the sub-header of the MAC PDU, and notifies the length of the SO domain of the RLC entity.
  • the MAC entity notifies the length of the L domain of the RLC entity, after which the RLC entity obtains the length of the SO by the length notified by the MAC entity.
  • FIG. 24 is a schematic structural diagram of a packet header of another RLC PDU according to another embodiment of the present invention.
  • the RLC entity adds the same F-domain as the F-domain of the L-domain indicated by the MAC entity in the sub-header of the RLC PDU segment.
  • the SO domain of the RLC entity is set to the same length as the L domain of the MAC entity.
  • the RLC entity obtains the length of the SO domain by detecting the F field in the RLC subheader.
  • FIG. 25 is a schematic structural diagram of a packet header of another RLC PDU according to another embodiment of the present invention.
  • the RLC entity determines the length of the SO domain according to the length of the RLC SDU segment.
  • the specific method is as follows: First, after the LCP, the MAC entity informs the RLC entity of the grant obtained from a certain logical channel; after that, the RLC entity matches the size of the grant by segmenting the RLC SDU of the last RLC PDU; finally, the RLC entity The value of SO after segmentation is obtained, and the size of the SO domain is obtained by the value of SO.
  • the figure uses two different F-fields to indicate the length of the first and second SOs, but is not limited to such a configuration: it can be an F-domain to indicate the length of two SO-domains; it can also be multiple Fs. To indicate the length of multiple SO domains.
  • the RLC entity obtains the length of the SO domain by detecting the F field in the RLC subheader.
  • FIG. 26 is a schematic diagram of another process for configuring a token bucket state according to another embodiment of the present invention.
  • the state of the token bucket is used by the MAC layer to make scheduling decisions to determine how much data is transferred by that logical channel.
  • the number of tokens in the token bucket is represented by a parameter Bj, where the number of tokens indicates whether the data of one logical channel obtains a pre-configured transmission rate, for example, when Bj is a positive number, it indicates the current The data of the logical channel does not obtain the pre-configured transmission rate.
  • Bj is negative, the data obtained by the current logical channel obtains a transmission rate exceeding the pre-configured transmission rate.
  • the cumulative time granularity of Bj is specified by the protocol, which is the common divisor of all available Numerology/TTI lengths, such as the symbol length corresponding to the 60KHz subcarrier spacing.
  • the base station configures the number of Bj accumulations per unit time for the terminal device, and the terminal device performs Bj accumulation in units of the time granularity.
  • Bj/unit time is configured by the base station and is configured for each terminal device and configured by dedicated signaling.
  • the “unit time” is the common divisor of all available TTI lengths of the terminal equipment (the terminal equipment can use two TTI lengths: TTI1 and TTI2).
  • unit time may be the greatest common divisor of all available TTI lengths of the terminal device.
  • the terminal device in the figure can use two TTI lengths: TTI1 and TTI2, and the unit time can be the greatest common divisor of TTI1 and TTI2.
  • unit time may be the common divisor or the greatest common divisor of all available TTI lengths within the cell.
  • the cell has three TTI lengths: TTI1, TTI2, and TTI3.
  • the terminal device uses only two TTI lengths: TTI1, TTI2.
  • unit time refers to the common divisor or the greatest common divisor of TTI1, TTI2, and TTI3.
  • the “unit time” may be configured by the base station and sent to the terminal device, for example, the base station is configured through RRC signaling, and “unit time” may be configured to one or more logical channels of one terminal device.
  • each logical channel is configured with an independent "unit time.”
  • the "unit time” may be a time unit specified by the protocol, and all available TTI lengths in the cell are integer multiples of this "unit time". Specifically, the "unit time” may be the smallest symbol length of all available symbol lengths of the terminal device; or the minimum symbol length supported in the NR.
  • FIG. 27 is a schematic diagram of a process of changing a Bj state according to another embodiment of the present invention.
  • the terminal equipment receives two uplink resources in the same TTI: uplink grant A (UL grant A) and UL grant B, where the uplink resource and UL grant B indicated by UL grant A
  • the indicated uplink resources are not at the same time.
  • the terminal equipment prepares the two TBs from different points in time: TB A and TB B. From which point in time the terminal device prepares a specific TB, the Bj corresponding to that time point is used.
  • the cumulative value of Bj per time unit is 20.
  • Bj is subtracted in the process of generating TB B 100, so, after generating TB B, Bj becomes 0.
  • the LCH has data transmission in both TB A and TB B, so after both TBs are generated, Bj is reduced.
  • FIG. 28 is a schematic diagram of a process of changing a Bj state according to another embodiment of the present invention.
  • the terminal device does not consider the current LCH when preparing the TB B. If the terminal equipment is preparing TB B, the data of other LCHs is put in later, there is still space, the current LCH data can be put in; under other conditions, the current LCH data can also be put in, for example, other waiting
  • the transmitted LCH is a background type service and is not sensitive to delay. Under such conditions, the Bj maintained by the terminal device for the LCH is not reduced.
  • This ⁇ coefficient can be configured by the base station to the terminal device through dedicated RRC signaling, which is configured by per LCH.
  • ⁇ when ⁇ is equal to 0, it is equivalent to the case where Bj is not reduced as described above.
  • Each LCH uses a different coefficient. It can also be a set of logical channel-air interface format or TTI length (LCH-numerology/TTI).
  • FIG. 29 is a schematic diagram of coexistence of semi-persistent scheduling (SPS) resources and dynamic scheduling resources according to another embodiment of the present invention.
  • SPS semi-persistent scheduling
  • the base station allocates a semi-static scheduling resource SPS to the terminal device.
  • the SPS resource allocation may be an uplink resource or a downlink resource.
  • the terminal device may perform multiple services at the same time. If the base station considers that the terminal device needs to transmit more data at the moment when the SPS resource is located, the terminal device temporarily allocates dynamically scheduled resources.
  • SPS resources are always located on the Pcell and are not located on other Scells.
  • the terminal device ignores the dynamically scheduled uplink resources.
  • the terminal device has SPS uplink resources in two uplink subframes respectively, and in the same subframe where the SPS 1 resource is located, the base station allocates a dynamic scheduling resource to the terminal device.
  • the terminal device Abandon SPS 1, only use dynamically scheduled resources to transfer data in this subframe.
  • the terminal device may simultaneously transmit data using a plurality of numerology/TTI length resources, and different numerology/TTI lengths correspond to different service QoS.
  • the terminal device may abandons the SPS resource and uses dynamic scheduling. Resources will not meet the needs of the business with the highest QoS requirements. Therefore, you can make the following changes to the behavior of the terminal device:
  • the terminal device decides whether to adopt SPS resources or dynamically schedule resources.
  • An optimized method is: the terminal device judges according to the type of data in the current buffer. If the service data with the highest QoS requirement in the current buffer cannot be dynamically transmitted, and only the SPS resource transmission is used, the terminal device determines to use the SPS resource transmission, and does not use the dynamically scheduled resource.
  • Another optimization method is: the terminal device determines to use the SPS resource or the dynamic scheduling resource according to the remaining delay of the data packet with the highest QoS requirement in the data in the current buffer, for example, if the terminal device finds that the current QoS requirement is the highest. For the data packet, the remaining delay is still 20ms, and the next SPS resource (which can satisfy the QoS) is after 15ms. At this time, the terminal device decides to use the dynamic scheduling resource and does not use the SPS resource.
  • the base station configures a priority of different numerology/TTI lengths. If the terminal device finds that the SPS resource overlaps with the dynamic scheduling resource in time, the terminal device selects a resource of a higher priority numerology/TTI length. If the priorities of the two resources's numerology/TTI length are the same, the terminal device selects the dynamically scheduled resources.
  • the terminal device selects a resource with a shorter TTI length in the SPS resource or the dynamic scheduling resource according to the TTI length of the uplink resource, and abandons the resource with a longer TTI length. If the TTI lengths of the two resources are the same, the terminal device selects the dynamically scheduled resources for data transmission.
  • the behavior of the terminal device is clarified, and a resource is selected for data transmission.
  • the terminal device selects one of the SPS resource and the dynamic scheduling resource for data transmission.
  • each step of the above method may be completed by an integrated logic circuit of hardware in a processor or an instruction in a form of software.
  • the steps of the method disclosed in the embodiments of the present application may be directly implemented by the hardware processor, or may be performed by a combination of hardware and software modules in the processor.
  • the software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the storage medium is located in the memory, and the processor reads the information in the memory and combines the hardware to complete the steps of the above method. To avoid repetition, it will not be described in detail here.
  • sequence numbers of the above processes do not mean the order of execution, and the order of execution of each process should be determined by its function and internal logic, and should not be implemented in the embodiments of the present application.
  • the process 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 may be Integrate 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.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • This functionality if implemented as a software functional unit and sold or used as a standalone product, can be stored on a computer readable storage medium.
  • the technical solution of the present application which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including The instructions are used to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the method in accordance with various embodiments of the present invention.
  • 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)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本发明的多个方面公开一种状态报告的处理方法和装置，发送端生成MAC PDU，该MAC PDU包括一个或多个RLC PDU，其中一个或多个RLC PDU的包头中的状态报告发送请求置为激活；发送端将该MAC PDU发送给接收端，以便所述接收端解析出至少一个RLC PDU的包头中的状态报告发送请求置为激活时确定为所述MAC PDU发送状态报告。上述描述的数据传输的处理方法和装置，所述接收端只要解析出至少一个RLC PDU的包头中的状态报告发送请求置为激活时就确定为所述MAC PDU发送状态报告。

Description

一种数据传输的处理方法和装置
本申请要求于2017年5月5日提交中国专利局、申请号为201710314223.9、发明名称为“一种数据传输的处理方法和装置”和2017年8月11日提交中国专利局、申请号为201710687319.X、发明名称为“一种数据传输的处理方法和装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明实施例涉及通信技术，尤其涉及一种数据传输的处理方法、装置。
背景技术
目前通信存在各种制式，例如第二代(2G)、第三代(3G)、第四代(4G)通信系统和新无线接入网络，例如全球移动通信(Global System of Mobile communication，GSM)系统，码分多址(Code Division Multiple Access，CDMA)系统，时分多址(Time Division Multiple Access，TDMA)系统，宽带码分多址(Wideband Code Division Multiple Access，WCDMA)，频分多址(Frequency Division Multiple Addressing，FDMA)系统，正交频分多址(Orthogonal Frequency-Division Multiple Access，OFDMA)系统，单载波FDMA(SC-FDMA)系统，通用分组无线业务(General Packet Radio Service，GPRS)系统，长期演进(Long Term Evolution，LTE)系统，通用移动通信系统(Universal Mobile Telecommunications System，UMTS)以及其他此类通信系统。其中，新无线接入网络能够提供比LTE网络更高的传输速率，新无线接入网络也称为5G网络、下一代网络等。
随着接收端需求和技术的飞速发展，第五代移动通信(the 5th Generation mobile communication technology，5G)系统或者新无线接入技术(New radio，NR)即将到来，5G系统或NR系统能够提供比长期演进(Long Term Evolution，LTE)网络更快的传输速率，其最高理论传输速率可达每秒数十吉字节(Gigabyte，简称Gb)。
所述新通信系统为5G或下一代通信系统，包括下一代核心网(NG Core)和基站(gNB)，其中，所述gNB一般包括无线资源控制(Radio Resource Control，RRC)层、分组数据汇聚协议(Packet Data Convergence Protocol，PDCP)层、无线链路层控制(Radio Link Control，RLC)层、媒体介入控制(Media Access Control，MAC)层和物理层(Physical Layer，PHY)。
所述gNB也可以采用采用集中式单元(Centralized Unit，CU)和分布式单元(Distributed Unit，DU)架构，所述CU和DU通过有线或无线通信，所述DU与终端设备通过空口通信，所述终端设备在同一个或不同的DU下的不同小区进行移动。
如果所述gNB采用CU-DU架构，CU和DU功能的划分存在多种可能，其中一种功能划分方式可以是：CU包括RRC层和PDCP层，DU包括RLC层、MAC层 和PHY层。
CU设备一般负责集中式无线资源和连接管理控制，DU设备一般包含实现分布式用户面处理功能，主要处理物理层功能和实时性需求较高的层2(Layer 2)功能。
CU设备处理无线高层协议栈功能，例如RRC层，PDCP层等，甚至也能够支持部分核心网功能下沉至接入网，称作边缘计算网络，能够满足未来通信网络对于新兴业务例如视频，网购，虚拟/增强现实对于网络时延的更高要求。
CU涵盖无线接入网高层协议栈以及核心网的一部分功能，而DU涵盖了基带处理的物理层以及层2部分功能，CU可以集中式的布放，DU布放取决实际网络环境，核心城区，话务密度较高，站间距较小，机房资源受限的区域，例如高校，大型演出场馆等，DU也可以集中式布放，而话务较稀疏，站间距较大等区域，例如郊县，山区等区域，DU可以采取分布式的布放方式。
如图1所示，为现有技术中LTE系统的一种MAC PDU的结构示意图，所述LTE系统中，一个MAC协议数据单元(Protocol Data Unit，PDU)中，与一个无线承载(Radio Bearer，RB)或一个逻辑信道(Logical Channel，LCH)对应的只有一个RLC PDU，一个RLC PDU可以包括多个级联的RLC服务数据单元(Service Data Unit，SDU)，但是只在RLC PDU的包头(RLC header)中设置有状态报告发送请求比特(Polling bit)，例如Polling bit＝1表示激活，Polling bit＝0表示非激活，当所述发送端发送给MAC PDU给接收端时，所述接收端根据该RLC PDU的包头中的Polling bit值判断是否需要发送状态报告给发送端，例如Polling bit＝1表示激活时，所述接收端需要发送状态报告，例如Polling bit＝0表示非激活时，所述接收端不需要发送状态报告。
但对于下一代通信系统，如图2所示，为现有技术中下一代通信系统的一种MAC PDU的结构示意图，所述下一代通信系统可以是5G通信系统，NR中RLC层没有级联功能，一个MAC PDU中，与一个RB或一个LCH对应的有多个RLC PDU，例如LCH1对应三个RLC PDU：RLC PDU1、RLC PDU2和RLC PDU3，所述多个RLC SDU没有级联，每个RLC PDU都有一个RLC包头，每个包头中都有一个polling比特，这样对Polling bit产生了诸多影响，例如一个LCH对应的多个RLC PDU中，有的RLC PDU的Polling bit为1，有的RLC PDU的Polling bit为零，这样接收端收到该MAC PDU后对该LCH对应的有多个RLC PDU不知道如何发送状态报告。
发明内容
本发明的多个方面，提供一种数据传输的处理方法和装置，解决下一代通信系统中如何发送状态报告的问题。
本发明的第一方面提供一种状态报告的处理方法，包括：发送端生成MAC PDU，该MAC PDU包括一个或多个RLC PDU，其中一个或多个RLC PDU的包头中的状态报告发送请求置为激活；发送端将该MAC PDU发送给接收端，以便所述接收端解析出至少一个RLC PDU的包头中的状态报告发送请求置为激活时确定为所述MAC  PDU发送状态报告。
可选的，发送端的RLC层将其发送的所述一个或多个RLC PDU的包头中的状态报告发送请求置为激活，并将携带有所述状态报告发送请求的RLC PDU发送给所述发送端的MAC层。
可选的，所述发送端的RLC层确定需要发送状态报告发送请求，通知所述发送端的MAC层对下一次需要发送的MAC PDU中的所述一个或多个RLC PDU的包头中的状态报告发送请求置为激活。
可选的，所述发送端的RLC层确定需要发送状态报告发送请求，通知所述发送端的MAC层从下一次需要发送的MAC PDU中所述一个或多个RLC PDU选一个RLC PDU并将该选择的RLC PDU的序列号通知所述发送端的所述RLC层；所述发送端的所述RLC层将该序列号对应的RLC PDU的包头中的状态报告发送请求置为激活；所述发送端的所述RLC层将携带有所述状态报告发送请求的RLC PDU发送给所述发送端的MAC层。
可选的，RLC实体每发出一个RLC SDU，将计数器SDU_WITHOUT_POLL的值加1，直到SDU_WITHOUT_POLL等于所述门限K时，将最后生成的一个RLC PDU的RLC头中的polling比特置1，当发送完RLC SN为门限值对应的的RLC PDU后，polling等于0，SDU_WITHOUT_POLL等于0，当发送下一个RLC SDU，SDU_WITHOUT_POLL从1开始重新累计。
可选的，发送端的所述RLC层保存的已经发送RLC PDU数量的计数器，也可以是已经发送RLC SDU数量的计数器。
可选的，发送端的所述RLC层保存的已经发送RLC PDU数据量的计数器，也可以是已经发送RLC SDU数据量的计数器。
可选的，所述发送端的所述RLC层在将携带有所述状态报告发送请求的RLC PDU发送给所述发送端的所述MAC层时，将所述发送端的所述RLC层保存的已经发送RLC PDU数量的计数器和已经发送RLC PDU数据量的计数器置零，重启状态报告发送请求重传定时器。
可选的，所述发送端的所述RLC层在将携带有所述状态报告发送请求的RLC PDU发送给所述发送端的所述MAC层时，执行如下至少之一：将所述发送端的所述RLC层保存的已经发送RLC PDU数量的计数器、已经发送RLC PDU数据量的计数器置零和重启状态报告发送请求重传定时器。
可选的，所述发送端的所述RLC层在获知所述发送端的所述MAC层将携带状态报告发送请求置为激活的RLC PDU发送时，所述发送端的所述RLC层将其保存的已经发送RLC PDU数量的计数器和已经发送RLC PDU数据量的计数器置零，重启状态报告发送请求重传定时器。
可选的，所述发送端的所述RLC层在获知所述发送端的所述MAC层将携带状态报告发送请求置为激活的RLC PDU发送时，执行如下至少之一：所述发送端的所 述RLC层将其保存的已经发送RLC PDU数量的计数器、已经发送RLC PDU数据量的计数器置零和重启状态报告发送请求重传定时器。
可选的，所述发送端的所述MAC层在将携带状态报告发送请求置为激活的RLC PDU发送时，通知所述发送端的所述RLC层已经将携带状态报告发送请求置为激活的RLC PDU发送。
可选的，所述发送端的所述MAC层确定所述MAC PDU内一个无线承载或一个逻辑信道对应的任意一个RLC PDU或所述MAC PDU内一个无线承载或一个逻辑信道对应的多个RLC PDU中最后一个RLC PDU或所述MAC PDU内一个无线承载或一个逻辑信道对应的多个RLC PDU中最后一个没有被分段的RLC PDU的状态报告发送请求置为激活。
可选的，所述发送端的所述MAC层在将携带状态报告发送请求置为激活的RLC PDU发送时，通知所述发送端的所述RLC层一个RLC PDU的序列号SN，其中，该SN是状态报告发送请求置为激活的RLC PDU的SN，或者，该SN是一个状态报告发送请求置为激活的RLC PDU所属的MAC PDU内的最后一个RLC PDU的SN，或该SN是一个状态报告发送请求置为激活的RLC PDU所属的MAC PDU内的任意一个RLC PDU的SN。
可选的，所述发送端的所述MAC层在将携带状态报告发送请求置为激活的RLC PDU发送时，通知所述发送端的所述RLC层一个RLC PDU的序列号SN，和通知所述发送端的所述RLC层当前状态报告发送请求置为激活的。
本发明的第二方面提供一种状态报告的处理装置，包括：MAC实体，用于生成MAC PDU，该MAC PDU包括一个或多个RLC PDU，其中一个或多个RLC PDU的包头中的状态报告发送请求置为激活；所述MAC实体还用于将该MAC PDU发送给接收端，以便所述接收端解析出至少一个RLC PDU的包头中的状态报告发送请求置为激活时确定为所述MAC PDU发送状态报告。
可选的，所述装置还包括：RLC实体，用于将其发送的所述一个或多个RLC PDU的包头中的状态报告发送请求置为激活，并将携带有所述状态报告发送请求的RLC PDU发送给所述MAC实体。
可选的，所述装置还包括：RLC实体，用于确定需要发送状态报告发送请求，通知所述MAC实体对下一次需要发送的MAC PDU中的所述一个或多个RLC PDU的包头中的状态报告发送请求置为激活。
可选的，所述装置还包括：RLC实体，用于确定需要发送状态报告发送请求，通知所述MAC实体从下一次需要发送的MAC PDU中所述一个或多个RLC PDU选一个RLC PDU并将该选择的RLC PDU的序列号通知所述RLC实体；其中，所述RLC实体，还用于将该序列号对应的RLC PDU的包头中的状态报告发送请求置为激活，将携带有所述状态报告发送请求的RLC PDU发送给所述MAC实体。
可选的，所述RLC实体还用于在将携带有所述状态报告发送请求的RLC PDU 发送给所述MAC实体时，将所述RLC实体保存的已经发送RLC PDU数量的计数器和已经发送RLC PDU数据量的计数器置零，重启状态报告发送请求重传定时器。
可选的，所述RLC实体还用于在将携带有所述状态报告发送请求的RLC PDU发送给所述MAC实体时，执行如下至少之一：将所述RLC实体保存的已经发送RLC PDU数量的计数器、已经发送RLC PDU数据量的计数器置零和重启状态报告发送请求重传定时器。
可选的，所述RLC实体还用于在获知所述MAC实体将携带状态报告发送请求置为激活的RLC PDU发送时，将所述RLC实体保存的已经发送RLC PDU数量的计数器和已经发送RLC PDU数据量的计数器置零，重启状态报告发送请求重传定时器。
可选的，所述RLC实体还用于在获知所述MAC实体将携带状态报告发送请求置为激活的RLC PDU发送时，执行如下至少之一：将所述RLC实体保存的已经发送RLC PDU数量的计数器、已经发送RLC PDU数据量的计数器置零和重启状态报告发送请求重传定时器。
可选的，所述MAC实体还用于在将携带状态报告发送请求置为激活的RLC PDU发送时，通知所述RLC实体已经将携带状态报告发送请求置为激活的RLC PDU发送。
可选的，所述MAC实体还用于确定所述MAC PDU内一个无线承载或一个逻辑信道对应的任意一个RLC PDU或所述MAC PDU内一个无线承载或一个逻辑信道对应的多个RLC PDU中最后一个RLC PDU或所述MAC PDU内一个无线承载或一个逻辑信道对应的多个RLC PDU中最后一个没有被分段的RLC PDU的状态报告发送请求置为激活。
可选的，所述MAC实体还用于在将携带状态报告发送请求置为激活的RLC PDU发送时，通知所述RLC实体一个RLC PDU的序列号SN，其中，该SN是状态报告发送请求置为激活的RLC PDU的SN，或者，该SN是一个状态报告发送请求置为激活的RLC PDU所属的MAC PDU内的最后一个RLC PDU的SN，或该SN是一个状态报告发送请求置为激活的RLC PDU所属的MAC PDU内的任意一个RLC PDU的SN。
本发明的第三方面提供一种状态报告的处理方法，包括：接收端接收发送端发送的一个MAC PDU，该MAC PDU包括一个或多个RLC PDU，其中一个或多个RLC PDU的包头中的状态报告发送请求置为激活；当所述接收端确定该MAC PDU中至少一个RLC PDU的状态报告发送请求置为激活时，根据该状态报告发送请求置为激活状态生成状态报告；所述接收端向所述发送端发送状态报告。
可选的，所述根据该状态报告发送请求置为激活状态生成状态报告具体包括：根据该状态报告发送请求置为激活状态确定该MAC PDU中的最后一个RLC PDU的状态报告发送请求的状态为激活，根据最后一个RLC PDU的序列号(SN)生成状态报告。
可选的，所述MAC PDU内一个无线承载或一个逻辑信道对应的任意一个RLC PDU或所述MAC PDU内一个无线承载或一个逻辑信道对应的多个RLC PDU中最 后一个RLC PDU或所述MAC PDU内一个无线承载或一个逻辑信道对应的多个RLC PDU中最后一个没有被分段的RLC PDU的状态报告发送请求置为激活。
本发明的第四方面提供一种状态报告的处理装置，包括：接收器，用于接收发送端发送的一个MAC PDU，该MAC PDU包括一个或多个RLC PDU，其中一个或多个RLC PDU的包头中的状态报告发送请求置为激活；处理器，用于当确定该MAC PDU中至少一个RLC PDU的状态报告发送请求置为激活时，根据该状态报告发送请求置为激活状态生成状态报告；发送器，向所述发送端发送状态报告。
可选的，所述处理器用于根据该状态报告发送请求置为激活状态生成状态报告具体包括：所述处理器，用于根据该状态报告发送请求置为激活状态确定该MAC PDU中的最后一个RLC PDU的状态报告发送请求的状态为激活，根据最后一个RLC PDU的序列号(SN)生成状态报告。
可选的，所述MAC PDU内一个无线承载或一个逻辑信道对应的任意一个RLC PDU或所述MAC PDU内一个无线承载或一个逻辑信道对应的多个RLC PDU中最后一个RLC PDU或所述MAC PDU内一个无线承载或一个逻辑信道对应的多个RLC PDU中最后一个没有被分段的RLC PDU的状态报告发送请求置为激活。
上述实施例描述的数据传输的处理方法和装置，所述接收端只要解析出至少一个RLC PDU的包头中的状态报告发送请求置为激活时就确定为所述MAC PDU发送状态报告。
附图说明
图1为现有技术中LTE系统的一种MAC PDU的结构示意图；
图2为现有技术中下一代通信系统的一种MAC PDU的结构示意图；
图3为本发明一实施例的一种通信系统的示意图；
图4为本发明另一实施例的另一种通信系统的结构示意图；
图5为本发明一实施例的一种状态报告的处理方法流程示意图；
图5a为本发明另一实施例的一种发送RLC SDU的状态过程示意图；
图5b为本发明另一实施例的另一种发送RLC SDU的状态过程示意图；
图5c为本发明另一实施例的另一种发送RLC SDU的状态过程示意图；
图5d为本发明另一实施例的另一种发送RLC SDU的状态过程示意图；
图5e为本发明另一实施例的另一种发送RLC SDU的状态过程示意图；
图5f为本发明另一实施例的另一种发送RLC SDU的状态过程示意图；
图6为本发明另一实施例的一种状态报告的处理装置的结构示意图；
图7为本发明一实施例的另一种状态报告的处理方法流程示意图；
图8为本发明另一实施例的另一种状态报告的处理装置的结构示意图；
图9为本发明的另一实施例的一种触发RLC Polling方法的过程状态图；
图10为本发明的另一实施例的另一种触发RLC Polling方法的过程状态图；
图11为本发明的另一实施例的另一种触发RLC Polling方法的过程状态图；
图12为本发明的另一实施例的另一种触发RLC Polling方法的过程状态图；
图13为本发明的另一实施例的另一种触发RLC Polling方法的过程状态图；
图14为本发明的另一实施例的另一种触发RLC Polling方法的过程状态图；
图15为本发明的另一实施例的另一种触发RLC Polling方法的过程状态图；
图16为本发明一实施例的一种RLC control PDU的数据结构示意图；
图17为本发明另一实施例的一种RLC状态报告的结构示意图；
图17a为本发明另一实施例的另一种RLC状态报告格式的结构示意图；
图18为本发明另一实施例的另一种RLC状态报告的结构示意图；
图18a为本发明另一实施例的另一种RLC状态报告格式的结构示意图；
图19为本发明另一实施例的另一种RLC状态报告的结构示意图；
图19a为本发明另一实施例的另一种RLC状态报告格式的结构示意图；
图20为本发明另一实施例的另一种RLC状态报告的结构示意图；
图20a为本发明另一实施例的另一种RLC状态报告格式的结构示意图；
图21为本发明另一实施例的另一种RLC状态报告的结构示意图；
图21a为本发明另一实施例的另一种RLC状态报告格式的结构示意图；
图21b为本发明另一实施例的另一种RLC状态报告格式的结构示意图；
图22为本发明另一实施例的另一种RLC状态报告的结构示意图；
图22a为本发明另一实施例的另一种RLC状态报告格式的结构示意图；
图23为本发明实施例的一种RLC PDU的包头的结构示意图；
图24为本发明实施例的一种RLC PDU的包头的结构示意图；
图25为本发明另一实施例的另一种RLC PDU的包头的结构示意图；
图26为本发明另一实施例的另一种配置令牌桶状态的过程示意图；
图27为本发明另一实施例的一种Bj状态变化的过程示意图；
图28为本发明另一实施例的一种Bj状态变化的过程示意图；
图29为本发明另一实施例的一种半静态调度资源与动态调度资源的共存的示意图。
具体实施方式
为使本发明实施例的目的、技术方案和优点更加清楚，下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本发明一部分实施例，而不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本发明保护的范围。
本文所提及的“第一”、“第二”以及类似的词语并不表示任何顺序、数量或者重要性，而只是用来区分不同的组成部分。同样，“一个”或者“一”等类似词语也不表示数量限制，而是表示存在至少一个。“连接”或者“相连”等类似的词语并非限定于物理的或者机械的连接，而是可以包括电性的连接，不管是直接的还是间接的。
在本文提及的“模块”通常是指存储在存储器中的能够实现某些功能的程序或指令；在本文中提及的“单元”通常是指按照逻辑划分的功能性结构，该“单元”可以由纯硬件实现，或者，软硬件的结合实现。
在本文中提及的“多个”是指两个或两个以上。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。字符“/”一般表示前后关联对象是一种“或”的关系。
本文中描述的技术可用于新无线接入网络以及其他此类通信系统，其中，新无线接入网络能够提供比LTE网络更高的传输速率，新无线接入网络也称为5G网络、下一代网络等。
本文中结合接收端和/或基站来描述各种方面。
终端设备(Terminal Device)，可以是无线终端也可以是有线终端，无线终端可以是指向接收端提供语音和/或数据连通性的设备，具有无线连接功能的手持式设备、或连接到无线调制解调器的其他处理设备。无线终端可以经无线接入网(例如，RAN，Radio Access Network)与一个或多个核心网进行通信，无线终端可以是移动终端，如移动电话(或称为“蜂窝”电话)和具有移动终端的计算机，例如，可以是便携式、袖珍式、手持式、计算机内置的或者车载的移动装置，它们与无线接入网交换语言和/或数据。例如，个人通信业务(Personal Communication Service，PCS)电话、无绳电话、会话发起协议(SIP)话机、无线本地环路(Wireless Local Loop，WLL)站、个人数字助理(Personal Digital Assistant，PDA)等设备。无线终端也可以称为系统、订户单元(Subscriber Unit)、订户站(Subscriber Station)，移动站(Mobile Station)、移动台(Mobile)、远程站(Remote Station)、接入点(Access Point)、远程终端(Remote Terminal)、接入终端(Access Terminal)、用户终端(User Terminal)、用户设备(User Equipment)或用户代理(User Agent)。
基站(即，节点)可以是指接入网中在空中接口上通过一个或多个扇区与无 线终端通信的设备，例如新无线接入网络的接入网设备，所述新无线接入网络的接入网设备也称为基站(gNB)、NR Node(节点)或者NR BS(基站，Base Station)，在此不作限制，但为描述方便，本文中统一称为gNB。
如图3所示，为本发明一实施例的一种通信系统的示意图，所述通信系统包括接入网设备31和终端设备32，所述通信系统可以是新无线接入网络，例如所述新无线接入网络也称为5G网络、下一代网络等，所述接入网设备31可以是5G通信系统的gNB。
所述接入网设备31包括三层结构：层一为物理层(PHY层)，层二为媒体接入控制层(MAC层)、无线链路控制层(RLC层)和分组数据会聚协议层(PDCP层)，层三为无线资源控制层(RRC层)，其中PHY层是无线接入系统最底层，它以传输信道为接口，向上层提供服务。所述接入网设备31的所述PHY层、MAC层、RLC层、PDCP层和RRC层针对每个承载均设置有接收实体和发送实体，分别用于数据的接收和发送，但为描述的方便，下述描述时，均以各层发送或接收进行描述。
所述接入网设备31从终端设备32接收的数据依次经过所述接入网设备31的PHY层、MAC层、RLC层、PDCP层和RRC层进行处理。例如，所述接入网设备31的PHY层接收终端设备32发送的数据(Data)后，在所述接入网设备31内，所述PHY层将所接收的数据处理为PHY服务数据单元(Service Data Unit，SDU)，所述PHY层将所述PHY SDU发送给所述MAC层；所述MAC层接收所述PYH SDU，然后将所述PYH SDU处理为MAC SDU，所述MAC层将所述MAC SDU发送给所述RLC层；所述RLC层接收所述MAC SDU，然后将所述MAC SDU处理为RLC SDU，所述RLC层将所述RLC SDU发送给所述PDCP层；所述PDCP层接收所述RLC SDU，然后将所述RLC SDU处理为信令PDCP SDU和数据PDCP SDU，所述PDCP层将所述信令PDCP SDU发送给所述RRC层进行控制层的处理，所述PDCP层将所述数据PDCP SDU发送给核心网。
所述接入网设备31发送的数据依次经过PDCP层、RLC层、MAC层和PHY层，然后发送给终端设备32。例如，在所述接入网设备31内，所述PDCP层将数据处理为PDCP协议数据单元(Protocol Data Unit，PDU)，然后将所述PDCP PDU发送给所述RLC层；所述RLC层接收所述PDCP PDU，然后将所述PDCP PDU处理为RLC PDU，所述RLC层将所述RLC PDU发送给所述MAC层；所述MAC层接收所述RLC PDU，然后将所述RLC PDU处理为MAC PDU，所述MAC层将所述MAC PDU发送给所述PHY层；所述PHY层接收所述MAC PDU，然后将所述MAC PDU处理为PHY PDU，所述PHY层将所述PHY PDU发送给终端设备32。
所述终端设备32包括PHY层、MAC层、RLC层和PDCP层，所述终端设备32包括的每个层针对每个承载均设置有接收实体和发送实体，分别用于数据的接收和发送，但为描述的方便，下述描述时，均以各层发送或接收进行描述。。
所述终端设备32向所述接入网设备31发送的数据依次经过所述终端设备32的PDCP层、RLC层、MAC层和PHY层进行处理。例如，所述终端设备32的PDCP 层将数据处理为PDCP PDU，然后将所述PDCP PDU发送给所述RLC层；所述RLC层接收所述PDCP PDU，然后将所述PDCP PDU处理为RLC PDU，所述RLC层将所述RLC PDU发送给所述MAC层；所述MAC层接收所述RLC PDU，然后将所述RLC PDU处理为MAC PDU，所述MAC层将所述MAC PDU发送给所述PHY层；所述PHY层接收所述MAC PDU，然后将所述MAC PDU处理为PHY PDU，所述PHY层将所述PHY PDU发送给终端设备31内的处理器进行处理。
所述终端设备32从所述接入网设备31接收的数据依次经过所述终端设备32的PHY层、MAC层、RLC层和PDCP层进行处理。在所述终端设备32内，所述PHY层数据处理为PHY SDU，然后将所述PHY SDU发送给所述MAC层；所述MAC层接收所述PYH SDU，然后将所述PYH SDU处理为MAC SDU，所述MAC层将所述MAC SDU发送给所述RLC层；所述RLC层接收所述MAC SDU，然后将所述MAC SDU处理为RLC SDU，所述RLC层将所述RLC SDU发送给所述PDCP层；所述PDCP层接收所述RLC SDU，然后将所述RLC SDU处理为PDCP SDU，所述PDCP层将所述PDCP SDU发送给所述接入网设备31的高层进行处理。
图4为本发明另一实施例的另一种通信系统的结构示意图，所述通信系统为4G或下一代通信系统，包括接入网设备41、终端设备42和下一代核心网(NG Core)43。例如，所述接入网设备41为4G的gNB，所述接入网设备41包括集中式单元(CU)411和分布式单元(DU)412，所述CU411和DU412通过有线或无线通信，所述DU412与所述终端设备42通过空口通信。其中，RRC层和PDCP层功能位于所述CU411上，RLC层、MAC层和PHY层功能位于所述DU412上。
各层之间的数据通信可以参考图4实施例描述的内容，在此不再赘述。
如图5所示，为本发明一实施例的一种状态报告的处理方法流程示意图，通信系统包括接入网设备和终端设备，所述接入网设备与终端设备通过空口通信，所述接入网设备可以是5G通信系统中的gNB或下一代通信系统的基站，所述gNB可以采用图3或图4的gNB的架构，所述接入网设备与终端设备的其中一方为发送端，另一方为接收端，例如当所述接入网设备为发送端时，所述终端设备为接收端，反之亦然。
步骤51，发送端生成MAC PDU，该MAC PDU包括一个或多个RLC PDU，其中一个或多个RLC PDU的包头中的状态报告发送请求置为激活。
5G通信系统或或下一代通信系统中，所述发送端生成的一个MAC PDU中，与一个RB或一个LCH对应的有多个RLC PDU，例如LCH1对应三个RLC PDU：RLC PDU1、RLC PDU2和RLC PDU3，所述多个RLC SDU没有级联，每个RLC PDU都有一个RLC包头(RLC header)，每个RLC包头包括polling bit和RLC PDU的序列号(Sequence Number，SN)。所述polling bit＝1表示状态报告发送请求置为激活，要求接收端发送状态报告，所述polling bit＝0表示状态报告发送请求置为非激活，不要求所述接收端发送状态报告。
步骤52，所述发送端将该MAC PDU发送给接收端，以便所述接收端解析出至少一个RLC PDU的包头中的状态报告发送请求置为激活时确定为所述MAC PDU发 送状态报告。
在本发明的另一实施例中，所述发送端的RLC层将其发送的所述一个或多个RLC PDU的包头中的状态报告发送请求置为激活，并将携带有所述状态报告发送请求的RLC PDU发送给所述发送端的MAC层。
在本发明的另一实施例中，所述发送端的RLC层确定需要发送状态报告发送请求，通知所述发送端的MAC层对下一次需要发送的MAC PDU中的所述一个或多个RLC PDU的包头中的状态报告发送请求置为激活。例如，所述发送端的RLC层还通知所述发送端的MAC层下一次需要发送的MAC PDU中的所述一个或多个RLC PDU的序列号，指示所述发送端的MAC层对一个或多个RLC PDU的包头中的状态报告发送请求置为激活，由MAC层确定具体那一个RLC PDU置为1，例如，任意确定或最后一个RLC PDU。
例如，所述发送端的所述RLC层在获知所述发送端的所述MAC层将携带状态报告发送请求置为激活的RLC PDU发送时，例如，所述发送端的所述RLC层接收所述发送端的所述MAC层发送的有polling bit置为1的RLC PDU SN且该RLC PDU已经发送的通知信息，所述发送端的所述RLC层将其保存的已经发送RLC PDU数量的计数器(PDU_WITHOUT_POLL)和已经发送RLC PDU数据量的计数器(BYTE_WITHOUT_POLL)置零，重启状态报告发送请求重传定时器(t-PollRetransmit)。
例如，所述发送端的所述RLC层在获知所述发送端的所述MAC层将携带状态报告发送请求置为激活的RLC PDU发送时，例如，所述发送端的所述RLC层接收所述发送端的所述MAC层发送的有polling bit置为1的RLC PDU SN且该RLC PDU已经发送的通知信息，执行如下至少之一：所述发送端的所述RLC层将其保存的已经发送RLC PDU数量的计数器(PDU_WITHOUT_POLL)、已经发送RLC PDU数据量的计数器(BYTE_WITHOUT_POLL)置零和重启状态报告发送请求重传定时器(t-PollRetransmit)。
例如，所述发送端的所述MAC层在将携带状态报告发送请求置为激活的RLC PDU发送时，通知所述发送端的所述RLC层已经将携带状态报告发送请求置为激活的RLC PDU发送，例如所述发送端的所述MAC层通知所述发送端的所述RLC层有polling bit置为1的RLC PDU SN且该RLC PDU已经发送。
例如，所述发送端的所述MAC层在将携带状态报告发送请求置为激活的RLC PDU发送时，通知所述发送端的所述RLC层一个RLC PDU的序列号SN，其中，该SN是状态报告发送请求置为激活的RLC PDU的SN，或者，该SN是一个状态报告发送请求置为激活的RLC PDU所属的MAC PDU内的最后一个RLC PDU的SN，或该SN是一个状态报告发送请求置为激活的RLC PDU所属的MAC PDU内的任意一个RLC PDU的SN。
在本发明的另一实施例中，所述发送端的RLC层确定需要发送状态报告发送请求，通知所述发送端的MAC层从下一次需要发送的MAC PDU中所述一个或多个 RLC PDU选一个RLC PDU并将该选择的RLC PDU的序列号通知所述发送端的所述RLC层；所述发送端的所述RLC层将该序列号对应的RLC PDU的包头中的状态报告发送请求置为激活；所述发送端的所述RLC层将携带有所述状态报告发送请求的RLC PDU发送给所述发送端的MAC层。
在本发明的另一实施例中，发送端的所述RLC层保存的已经发送RLC PDU数量的计数器，也可以是已经发送RLC SDU数量的计数器。
在本发明的另一实施例中，发送端的所述RLC层保存的已经发送RLC PDU数据量的计数器，也可以是已经发送RLC SDU数据量的计数器。
在本发明的另一实施例中，RLC实体建立时，基站通过RRC消息给SDU_WITHOUT_POLL配置一个门限K，SDU_WITHOUT_POLL初始值为0，RLC实体每发出一个RLC SDU，发送端RLC计算SDU_WITHOUT_POLL时，就把计数器SDU_WITHOUT_POLL的值加1，直到SDU_WITHOUT_POLL等于所述门限K时(即SDU数量计数器等于K)，将最后一个RLC SDU所对应生成的一个RLC PDU的RLC头中的polling比特置1，发送完所述最后RLC SDU(即RLC SN为门限K对应的RLC PDU)后，polling等于0，SDU_WITHOUT_POLL等于0，当发送下一个RLC SDU，SDU_WITHOUT_POLL从1开始重新累计。其中，RLC实体发送RLC SDU给MAC实体主要包括：RLC实将RLC SDU处理后，形成一个或多个RLC PDU，再将RLC PDU发给MAC实体。所述RLC实体每发出一个RLC SDU，是指RLC实体开始处理这个RLC SDU，准备发送这个RLC SDU。
例如，RLC实体建立时，基站通过RRC消息给SDU_WITHOUT_POLL配置一个门限K，SDU_WITHOUT_POLL初始值为0，数据传输过程中，RLC实体每发出一个RLC SDU，就将SDU_WITHOUT_POLL加1，如果SDU_WITHOUT_POLL超出门限K，则RLC实体触发polling，将最后一个RLC SDU所对应生成的一个RLC PDU的RLC头中的polling比特置1，即通知接收端发送RLC状态报告。
如图5a所示，为本发明另一实施例的一种发送RLC SDU的状态过程示意图，SDU_WITHOUT_POLL的门限K配置为1000，当发送端RLC实体发现SDU_WITHOUT_POLL等于所述门限1000时(即SDU数量计数器等于1000)，则将RLC包头中的Polling比特置1，当发送完RLC SN为门限1000对应的的RLC PDU后，polling等于0，SDU_WITHOUT_POLL等于0，当发送下一个RLC SDU，SDU_WITHOUT_POLL从1开始重新累计。
在本发明的另一实施例中，RLC实体建立时，基站通过RRC消息给SDU_WITHOUT_POLL配置一个门限K，比如K＝1000，SDU_WITHOUT_POLL初始值为0。如果某个RLC SDU被分段，则对各个分段，只统一增加一次SDU_WITHOUT_POLL。例如，如图5b所示，RLC SN等于999的这一个RLC SDU被分成两个分段，这两个分段都使用同一个RLC SN，发送第一个分段时，SDU_WITHOUT_POLL从998增加到999，发送第二个分段时，RLC实体发现这是同一个RLC SDU的第二个分段，则不增加SDU_WITHOUT_POLL，取值仍然为999。
RLC SN等于999的RLC SDU发生分段，所对应的SDU_WITHOUT_POLL没有达到门限K＝1000，当发送端RLC实体发现SDU_WITHOUT_POLL等于所述门限1000时(即SDU数量计数器等于1000)，则将RLC包头中的Polling比特置1，当发送完RLC SN为门限1000对应的的RLC PDU后，polling等于0，SDU_WITHOUT_POLL等于0，当发送下一个RLC SDU，SDU_WITHOUT_POLL从1开始重新累计。
在本发明的另一实施例中，如果发生分段的RLC SDU所对应的SDU_WITHOUT_POLL达到门限，则Polling的处理有如下四种方式。
方式一：每一个RLC segment的polling比特都置为1
如图5c所示，为本发明另一实施例的另一种发送RLC SDU的状态过程示意图，RLC SN等于1000的这一个RLC SDU被分成三个分段，这三个分段都使用同一个RLC SN，所对应的SDU_WITHOUT_POLL达到门限K＝1000，则发送端RLC实体将每一个RLC segment的polling比特都置为1，当发送完RLC SN为门限1000对应的的RLC PDU后，polling等于0，SDU_WITHOUT_POLL等于0，当发送下一个RLC SDU，SDU_WITHOUT_POLL从1开始重新累计。接收端收到多个带有polling＝1的RLC分段，发现这些分段的RLC SN都相同，则判定这些分段属于同一个RLC SDU，则只发出一个RLC状态报告。
方式二：仅第一个RLC segment的polling比特置为1
如图5d所示，为本发明另一实施例的另一种发送RLC SDU的状态过程示意图，RLC SN等于1000的这一个RLC SDU被分成三个分段，这三个分段都使用同一个RLC SN，所对应的SDU_WITHOUT_POLL达到门限K＝1000，则发送端RLC实体仅将第一个RLC segment的polling比特置为1，当发送完RLC SN为门限1000对应的的RLC PDU后，polling等于0，SDU_WITHOUT_POLL等于0，当发送下一个RLC SDU，SDU_WITHOUT_POLL从1开始重新累计。接收端收到带有polling＝1的RLC分段，生成RLC状态报告并发送。
方式三：仅最后一个RLC segment的polling比特置为1
如图5e所示，为本发明另一实施例的另一种发送RLC SDU的状态过程示意图，RLC SN等于1000的这一个RLC SDU被分成三个分段，这三个分段都使用同一个RLC SN，所对应的SDU_WITHOUT_POLL达到门限K＝1000，则发送端RLC实体仅将最后一个RLC segment的polling比特置为1，当发送完RLC SN为门限1000对应的的RLC PDU后，polling等于0，SDU_WITHOUT_POLL等于0，当发送下一个RLC SDU，SDU_WITHOUT_POLL从1开始重新累计。接收端收到带有polling＝1的RLC分段，生成RLC状态报告并发送。
方式四：任选一个RLC segment的polling比特置为1
如图5f所示，为本发明另一实施例的另一种发送RLC SDU的状态过程示意图，RLC SN等于1000的这一个RLC SDU被分成三个分段，这三个分段都使用同一个RLC SN，所对应的SDU_WITHOUT_POLL达到门限K＝1000，则发送端RLC实体任选 一个RLC segment的polling比特置为1，当发送完RLC SN为门限1000对应的的RLC PDU后，polling等于0，SDU_WITHOUT_POLL等于0，当发送下一个RLC SDU，SDU_WITHOUT_POLL从1开始重新累计。接收端收到带有polling＝1的RLC分段，生成RLC状态报告并发送。
上述四种方式中，如果选择方式二，可以及时触发接收端发RLC状态报告，而且无需修改接收端的行为。
在本发明的另一实施例中，所述发送端的所述RLC层在将携带有所述状态报告发送请求的RLC PDU发送给所述发送端的所述MAC层时，将所述发送端的所述RLC层保存的已经发送RLC PDU数量的计数器和已经发送RLC PDU数据量的计数器置零，重启状态报告发送请求重传定时器。
在本发明的另一实施例中，所述发送端的所述RLC层在将携带有所述状态报告发送请求的RLC PDU发送给所述发送端的所述MAC层时，执行如下至少之一：将所述发送端的所述RLC层保存的已经发送RLC PDU数量的计数器、已经发送RLC PDU数据量的计数器置零和重启状态报告发送请求重传定时器。
在本发明的另一实施例中，所述发送端的所述MAC层确定所述MAC PDU内一个无线承载或一个逻辑信道对应的任意一个RLC PDU或所述MAC PDU内一个无线承载或一个逻辑信道对应的多个RLC PDU中最后一个RLC PDU或所述MAC PDU内一个无线承载或一个逻辑信道对应的多个RLC PDU中最后一个没有被分段的RLC PDU的状态报告发送请求置为激活。
上述实施例中，所述接收端只要解析出至少一个RLC PDU的包头中的状态报告发送请求置为激活时就确定为所述MAC PDU发送状态报告，不会因为所述MAC PDU包括多个RLC PDU，且每个RLC PDU的包头包括的polling bit值不相同时，而影响所述接收端不确定如何发送状态报告。
如图6所示，为本发明另一实施例的一种状态报告的处理装置的结构示意图，通信系统包括接入网设备和终端设备，所述接入网设备与终端设备通过空口通信，所述接入网设备可以是5G通信系统中的gNB或下一代通信系统的基站，所述gNB可以采用图3或图4的gNB的架构，所述接入网设备与终端设备的其中一方为发送端，另一方为接收端，例如当所述接入网设备为发送端时，所述终端设备为接收端，反之亦然。
本实施例中，所述发送端为所述状态报告的处理装置，所述状态报告的处理装置包括PYH实体61、MAC实体62、RLC实体63和PDCP实体64。
在本申请实施例中，所述PYH实体61、MAC实体62、RLC实体63和PDCP实体64的处理功能通过处理器来执行，所述处理器可以是可擦除可编辑逻辑器件(Erasable Programmable Logic Device，EPLD)、现场可编程门阵列(Field Programmable Gate Array，FPGA)、数字信号处理器(Digital Signal Processor，DSP)芯片、专用集成电路(Application Specific Integrated Circuit，ASIC)、或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。
所述PYH实体61、MAC实体62、RLC实体63和PDCP实体64的接收功能和发送功能分布通过接收器和发送器来执行。
所述状态报告的处理装置还包括存储器，用于存储代码或指令信息，还可以存储设备类型的信息。该存储器可以包括只读存储器(Read-Only Memory，ROM)和随机存取存储器(Random Access Memory，RAM)，用于向所述处理器提供指令和数据。所述存储器的一部分还可以包括非易失性随机存取存储器。
所述MAC实体62，用于生成MAC PDU，该MAC PDU包括一个或多个RLC PDU，其中一个或多个RLC PDU的包头中的状态报告发送请求置为激活。
5G通信系统或或下一代通信系统中，所述MAC实体62生成的一个MAC PDU中，与一个RB或一个LCH对应的有多个RLC PDU，例如LCH1对应三个RLC PDU：RLC PDU1、RLC PDU2和RLC PDU3，所述多个RLC SDU没有级联，每个RLC PDU都有一个RLC包头(RLC header)，每个RLC包头包括polling bit和RLC PDU的序列号(Sequence Number，SN)。所述polling bit＝1表示状态报告发送请求置为激活，要求接收端发送状态报告，所述polling bit＝0表示状态报告发送请求置为非激活，不要求所述接收端发送状态报告。
所述MAC实体62，还用于将该MAC PDU发送给接收端，以便所述接收端解析出至少一个RLC PDU的包头中的状态报告发送请求置为激活时确定为所述MAC PDU发送状态报告。
在本发明的另一实施例中，所述RLC实体63将其发送的所述一个或多个RLC PDU的包头中的状态报告发送请求置为激活，并将携带有所述状态报告发送请求的RLC PDU发送给所述MAC实体62。
在本发明的另一实施例中，所述RLC实体63确定需要发送状态报告发送请求，通知所述MAC实体62对下一次需要发送的MAC PDU中的所述一个或多个RLC PDU的包头中的状态报告发送请求置为激活。例如，所述RLC实体63还用于通知所述MAC实体62下一次需要发送的MAC PDU中的所述一个或多个RLC PDU的序列号，指示所述MAC实体62对一个或多个RLC PDU的包头中的状态报告发送请求置为激活，由所述发送端的所述MAC实体62确定具体那一个RLC PDU置为1，例如，任意确定或最后一个RLC PDU。
例如，所述RLC实体63在获知所述发送端的所述MAC实体62将携带状态报告发送请求置为激活的RLC PDU发送时，例如，所述RLC实体63接收所述发送端的所述MAC实体62发送的有polling bit置为1的RLC PDU SN且该RLC PDU已经发送的通知信息，所述RLC实体63将其保存的已经发送RLC PDU数量的计数器(PDU_WITHOUT_POLL)和已经发送RLC PDU数据量的计数器(BYTE_WITHOUT_POLL)置零，重启状态报告发送请求重传定时器(t-PollRetransmit)。
例如，所述RLC实体63在获知所述发送端的所述MAC实体62将携带状态报告发送请求置为激活的RLC PDU发送时，例如，所述RLC实体63接收所述发送端 的所述MAC实体62发送的有polling bit置为1的RLC PDU SN且该RLC PDU已经发送的通知信息，执行如下至少之一：所述RLC实体63将其保存的已经发送RLC PDU数量的计数器(PDU_WITHOUT_POLL)、已经发送RLC PDU数据量的计数器(BYTE_WITHOUT_POLL)置零和重启状态报告发送请求重传定时器(t-PollRetransmit)。
例如，所述发送端的所述MAC实体62在将携带状态报告发送请求置为激活的RLC PDU发送时，通知所述RLC实体63已经将携带状态报告发送请求置为激活的RLC PDU发送，例如所述发送端的所述MAC实体62通知所述RLC实体63有polling bit置为1的RLC PDU SN且该RLC PDU已经发送。
例如，所述发送端的所述MAC实体62在将携带状态报告发送请求置为激活的RLC PDU发送时，通知所述RLC实体63一个RLC PDU的序列号SN，其中，该SN是状态报告发送请求置为激活的RLC PDU的SN，或者，该SN是一个状态报告发送请求置为激活的RLC PDU所属的MAC PDU内的最后一个RLC PDU的SN，或该SN是一个状态报告发送请求置为激活的RLC PDU所属的MAC PDU内的任意一个RLC PDU的SN。
在本发明的另一实施例中，所述RLC实体63确定需要发送状态报告发送请求，通知所述发送端的所述MAC实体62从下一次需要发送的MAC PDU中所述一个或多个RLC PDU选一个RLC PDU并将该选择的RLC PDU的序列号通知所述RLC实体63；所述RLC实体63将该序列号对应的RLC PDU的包头中的状态报告发送请求置为激活；所述RLC实体63将携带有所述状态报告发送请求的RLC PDU发送给所述发送端的所述MAC实体62。
在本发明的另一实施例中，所述RLC实体63在将携带有所述状态报告发送请求的RLC PDU发送给所述发送端的所述MAC实体62时，将所述RLC实体63保存的已经发送RLC PDU数量的计数器和已经发送RLC PDU数据量的计数器置零，重启状态报告发送请求重传定时器。
在本发明的另一实施例中，所述RLC实体63在将携带有所述状态报告发送请求的RLC PDU发送给所述发送端的所述MAC实体62时，执行如下至少之一：将所述RLC实体63保存的已经发送RLC PDU数量的计数器、已经发送RLC PDU数据量的计数器置零和重启状态报告发送请求重传定时器。
在本发明的另一实施例中，所述发送端的所述MAC实体62确定所述MAC PDU内一个无线承载或一个逻辑信道对应的任意一个RLC PDU或所述MAC PDU内一个无线承载或一个逻辑信道对应的多个RLC PDU中最后一个RLC PDU或所述MAC PDU内一个无线承载或一个逻辑信道对应的多个RLC PDU中最后一个没有被分段的RLC PDU的状态报告发送请求置为激活。
上述实施例中，所述接收端只要解析出至少一个RLC PDU的包头中的状态报告发送请求置为激活时就确定为所述MAC PDU发送状态报告，不会因为所述MAC PDU包括多个RLC PDU，且每个RLC PDU的包头包括的polling bit值不相同时，而影 响所述接收端不确定如何发送状态报告。
如图7所示，为本发明一实施例的另一种状态报告的处理方法流程示意图，通信系统包括接入网设备和终端设备，所述接入网设备与终端设备通过空口通信，所述接入网设备可以是5G通信系统中的gNB或下一代通信系统的基站，所述gNB可以采用图3或图4的gNB的架构，所述接入网设备与终端设备的其中一方为发送端，另一方为接收端，例如当所述接入网设备为发送端时，所述终端设备为接收端，反之亦然。
步骤71，接收端接收发送端发送的一个MAC PDU，该MAC PDU包括一个或多个RLC PDU，其中一个或多个RLC PDU的包头中的状态报告发送请求置为激活。
步骤72，当所述接收端确定该MAC PDU中至少一个RLC PDU的状态报告发送请求置为激活时，根据该状态报告发送请求置为激活状态生成状态报告。
步骤73，所述接收端向所述发送端发送状态报告。
在本发明的另一实施例中，所述根据该状态报告发送请求置为激活状态生成状态报告具体包括：根据该状态报告发送请求置为激活状态确定该MAC PDU中的最后一个RLC PDU的状态报告发送请求的状态为激活，根据最后一个RLC PDU的序列号(SN)生成状态报告。
在本发明的另一实施例中，所述MAC PDU内一个无线承载或一个逻辑信道对应的任意一个RLC PDU或所述MAC PDU内一个无线承载或一个逻辑信道对应的多个RLC PDU中最后一个RLC PDU或所述MAC PDU内一个无线承载或一个逻辑信道对应的多个RLC PDU中最后一个没有被分段的RLC PDU的状态报告发送请求置为激活。
上述实施例中，所述接收端只要解析出至少一个RLC PDU的包头中的状态报告发送请求置为激活时就确定为所述MAC PDU发送状态报告，不会因为所述MAC PDU包括多个RLC PDU，且每个RLC PDU的包头包括的polling bit值不相同时，而影响所述接收端不确定如何发送状态报告。
如图8所示，为本发明另一实施例的另一种状态报告的处理装置的结构示意图，通信系统包括接入网设备和终端设备，所述接入网设备与终端设备通过空口通信，所述接入网设备可以是5G通信系统中的gNB或下一代通信系统的基站，所述gNB可以采用图3或图4的gNB的架构，所述接入网设备与终端设备的其中一方为发送端，另一方为接收端，例如当所述接入网设备为发送端时，所述终端设备为接收端，反之亦然。
本实施例中，所述接收端为所述状态报告的处理装置，所述数据传输装置包括接收器81、处理器82、发送器83和存储器84，其中，所述接收器81、处理器82、发送器83和存储器84相互之间通过总线通信。
在本申请实施例中，该处理器82可以是EPLD、FPGA、DSP芯片、ASIC、或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。
所述存储器84用于存储代码或指令信息，还可以存储设备类型的信息。该存 储器84可以包括ROM和RAM，用于向所述处理器82提供指令和数据。所述存储器84的一部分还可以包括非易失性随机存取存储器。
所述接收器81，用于接收发送端发送的一个MAC PDU，该MAC PDU包括一个或多个RLC PDU，其中一个或多个RLC PDU的包头中的状态报告发送请求置为激活；
所述处理器82，用于当确定该MAC PDU中至少一个RLC PDU的状态报告发送请求置为激活时，根据该状态报告发送请求置为激活状态生成状态报告；
所述发送器83，向所述发送端发送状态报告。
在本发明的另一实施例中，所述处理器82，用于根据该状态报告发送请求置为激活状态确定该MAC PDU中的最后一个RLC PDU的状态报告发送请求的状态为激活，根据最后一个RLC PDU的序列号(SN)生成状态报告。
在本发明的另一实施例中，所述MAC PDU内一个无线承载或一个逻辑信道对应的任意一个RLC PDU或所述MAC PDU内一个无线承载或一个逻辑信道对应的多个RLC PDU中最后一个RLC PDU或所述MAC PDU内一个无线承载或一个逻辑信道对应的多个RLC PDU中最后一个没有被分段的RLC PDU的状态报告发送请求置为激活。
上述实施例中，作为接收端的所述状态报告的处理装置只要解析出至少一个RLC PDU的包头中的状态报告发送请求置为激活时就确定为所述MAC PDU发送状态报告，不会因为所述MAC PDU包括多个RLC PDU，且每个RLC PDU的包头包括的polling bit值不相同时，而影响所述接收端不确定如何发送状态报告。
同一个一个MAC PDU中，与一个RB或一个LCH对应的有多个RLC PDU，当触发条件满足时，触发需要发送态报告发送请求，称为触发polling，本发明的实施例中，既可以由所述发送端的RLC实体单独触发和发送，也可以由所述发送端的RLC实体和MAC实体联合触发和发送，具体如下所述。
所述发送端的RLC实体独立根据触发条件触发需要发送态报告发送请求，即触发polling，需要将polling bit设置为1或0，然后所述发送端的RLC实体选择或通知所述发送端的MAC层选择一个RLC PDU并将该选择的RLC PDU的包头中的polling bit需要设置1或0。
所述发送端的RLC实体触发需要发送态报告发送请求(即触发polling)的条件包括如下至少之一：所述发送端发送的RLC PDU数量达到预先设定的门限(即PDU_WITHOUT_POLL＝预先设定的门限)、所述发送端发送的数据量(Byte量)数量达到预先设定的门限(即BYTE_WITHOUT_POLL＝预先设定的门限)、和重启状态报告发送请求重传定时器(即Polling重传定时器(t-PollRetransmit))超时。
Polling触发方法一：RLC实体独立操作，基于PDU_WITHOUT_POLL
所述发送端的RLC实体确定：自从上一次发送态报告发送请求发送后，已经发送过但还没有要求发送状态报告的RLC PDU数量等于或大于门限，就触发RLC  polling。所述发送端的RLC实体触发需要发送态报告发送请求后，将下一个RLC PDU的RLC包头中的polling bit置为1，然后将该RLC PDU发送给所述发送端的MAC实体。所述发送端的RLC实体将自己保存的“PDU_WITHOUT_POLL”和“BYTE_WITHOUT_POLL”重置为0，重启“t-PollRetransmit”。由所述发送端的MAC实体确定什么时候将这个polling比特为1的RLC PDU在空口传输。
Polling触发方法二：RLC实体独立操作，基于BYTE_WITHOUT_POLL
所述发送端的RLC实体确定：自从上一次发送态报告发送请求发送后，已经发送过但还没有要求发送状态报告的RLC PDU的BYTE总数量(BYTE_WITHOUT_POLL)等于或大于门限，就触发RLC polling。所述发送端的RLC实体触发需要发送态报告发送请求后，将下一个RLC PDU的RLC包头中的polling bit置为1，然后将该RLC PDU发送给所述发送端的MAC实体。所述发送端的RLC实体将自己保存的“PDU_WITHOUT_POLL”和“BYTE_WITHOUT_POLL”重置为0，重启“t-PollRetransmit”。由所述发送端的MAC实体确定什么时候将这个polling比特为1的RLC PDU在空口传输。
Polling触发方法三：RLC实体独立操作，基于t-PollRetransmit
所述发送端的RLC实体确定：上一次触发需要发送态报告发送请求时启动t-PollRetransmit，t-PollRetransmit超时，就触发RLC polling。所述发送端的RLC实体触发需要发送态报告发送请求后，将下一个RLC PDU的RLC包头中的polling bit置为1，然后将该RLC PDU发送给所述发送端的MAC实体。所述发送端的RLC实体将自己保存的“PDU_WITHOUT_POLL”和“BYTE_WITHOUT_POLL”重置为0，重启“t-PollRetransmit”。由所述发送端的MAC实体确定什么时候将这个polling比特为1的RLC PDU在空口传输。
采用上述三种方法，所述发送端的RLC实体独立触发polling，所述发送端的MAC实体对触发polling过程不可见，优点是层间功能分隔清晰，流程简单。
Polling触发的也可以是所述发送端的RLC实体和MAC实体联合触发，具体如下所述。
Polling触发方法四：RLC实体和MAC实体协同操作，基于PDU_WITHOUT_POLL
所述发送端的RLC实体确定：自从上一次发送态报告发送请求发送后，已经发送过但还没有要求发送状态报告的RLC PDU的数量(PDU_WITHOUT_POLL)等于或数量大于门限，就触发RLC polling。所述发送端的RLC实体触发RLC polling后，向所述发送端的MAC实体发送第一通知消息，所述第一通知消息携带所述发送端的所述RLC实体已经触发RLC polling的信息。所述发送端的MAC实体收到该通知消息后，等到向所述发送端的PHY实体递交MAC PDU时，所述发送端的MAC实体向所述发送端的所述RLC实体发送第二通知消息，所述第二通知消息携带请求将MAC PDU中的最后一个RLC PDU对应的polling比特置1的信息，所述发送端的MAC实体向所述发送端的所述RLC实体发送所述最后一个RLC PDU所对应的RLC SN。所述发送端的 所述RLC实体收到所述第二通知消息和所述最后一个RLC PDU所对应的RLC SN后，将所述RLC SN所对应的RLC PDU的polling比特置1，然后将所述RLC SN所对应的RLC PDU发送给所述发送端的所述MAC实体，所述发送端的所述MAC实体将所述RLC SN所对应的RLC PDU处理为对应的MAC PDU，然后发送给所述发送端的PHY实体进行发送。
例如，如图9所示，为本发明的另一实施例的一种触发RLC Polling方法的过程状态图，所述发送端的RLC实体将序列号为35-38号RLC PDU数据包发送给所述发送端的MAC实体准备发送。所述发送端的RLC实体将序列号为36号RLC PDU数据包发送给所述发送端的MAC实体后，所述发送端的所述RLC实体保存的计数器PDU_WITHOUT POLL超过门限，所述发送端的所述RLC实体触发RLC polling。所述发送端的所述RLC实体将所述发送端的所述RLC实体已经触发RLC polling信息通知所述发送端的所述MAC实体。所述发送端的所述MAC实体准备发送MAC PDU时，将请求将MAC PDU中的最后一个RLC PDU对应的polling比特置1的信息和最后一个RLC PDU的序列号是37号的信息通知所述发送端的所述RLC实体，所述发送端的所述RLC实体收到通知后，将所述序列号为37号RLC PDU数据包的polling比特置为1，并将该序列号为37的RLC PDU发给所述发送端的所述MAC实体。所述发送端的所述MAC实体将序列号为35-37号的RLC PDU数据包处理到一个MAC PDU中，其中，序列号为37号的RLC PDU数据包对应的polling比特是1。
发送端维护的变量t-PollRetransmit从T2时刻重启，PDU_WITHOUT POLL的值从1开始，polling bit携带在序列号为37号的RLC PDU数据包中，序列号为38号的RLC PDU数据包属于没有被polling的，要计入下一轮的PDU_WITHOUT POLL中。同理，BYTE_WITHOUT POLL的值从X开始(X是序列号为38号的RLC PDU数据包的大小)，polling bit携带在序列号为37号的RLC PDU数据包中，序列号为38号的RLC PDU数据包包属于没有被polling的，要计入下一轮的BYTE_WITHOUT POLL中。
Polling触发方法五：RLC实体和MAC实体协同操作，基于BYTE_WITHOUT_POLL
所述发送端的RLC实体确定：自从上一次发送态报告发送请求发送后，已经发送过但还没有要求发送状态报告的RLC PDU数据量(BYTE_WITHOUT_POLL)等于或数量大于门限，就触发RLC polling。所述发送端的RLC实体触发RLC polling后，向所述发送端的MAC实体发送第三通知消息，所述第三通知消息携带所述发送端的所述RLC实体已经触发RLC polling的信息。所述发送端的MAC实体收到该通知消息后，等到向所述发送端的PHY实体递交MAC PDU时，所述发送端的MAC实体向所述发送端的所述RLC实体发送第四通知消息，所述第四通知消息携带请求将MAC PDU中的最后一个RLC PDU对应的polling比特置1的信息，所述发送端的MAC实体向所述发送端的所述RLC实体发送所述最后一个RLC PDU所对应的RLC SN。所述发送端的所述RLC实体收到所述第二通知消息和所述最后一个RLC PDU所对应的RLC SN后，将所述RLC SN所对应的RLC PDU的polling比特置1，然后将所述RLC SN所对应的RLC PDU发送给所述发送端的所述MAC实体，所述发送端的所述MAC实体将所述 RLC SN所对应的RLC PDU处理为对应的MAC PDU，然后发送给所述发送端的PHY实体进行发送。
Polling触发方法六：RLC实体和MAC实体协同操作，基于t-PollRetransmit
所述发送端的RLC实体确定：上一次触发需要发送态报告发送请求时，启动t-PollRetransmit，当所述t-PollRetransmit超时时就触发RLC polling。所述发送端的RLC实体触发RLC polling后，向所述发送端的MAC实体发送第三通知消息，所述第三通知消息携带所述发送端的所述RLC实体已经触发RLC polling的信息。所述发送端的MAC实体收到该通知消息后，等到向所述发送端的PHY实体递交MAC PDU时，所述发送端的MAC实体向所述发送端的所述RLC实体发送第四通知消息，所述第四通知消息携带请求将MAC PDU中的最后一个RLC PDU对应的polling比特置1的信息，所述发送端的MAC实体向所述发送端的所述RLC实体发送所述最后一个RLC PDU所对应的RLC SN。所述发送端的所述RLC实体收到所述第二通知消息和所述最后一个RLC PDU所对应的RLC SN后，将所述RLC SN所对应的RLC PDU的polling比特置1，然后将所述RLC SN所对应的RLC PDU发送给所述发送端的所述MAC实体，所述发送端的所述MAC实体将所述RLC SN所对应的RLC PDU处理为对应的MAC PDU，然后发送给所述发送端的PHY实体进行发送。
通过所述发送端的MAC实体和RLC实体的协作，保证发送态报告发送请求时，MAC PDU中总是最后一个RLC PDU的polling比特置1，从而发送端维护的变量PDU_WITHOUT_POLL和BYTE_WITHOUT_POLL反映的是最新的状态。
上述Polling触发方法四、五和六中，所述发送端的RLC实体触发RLC polling时，通知所述发送端的MAC实体，所述发送端的MAC实体收到通知后，生成MAC PDU时，请求所述发送端的所述RLC实体将最后一个RLC PDU的polling比特置1并将该最后一个RLC PDU的SN通知RLC实体。
在本发明的另一实施例中，上述Polling触发方法四、五和六中，也可以将MAC PDU内的任意一个或多个RLC PDU的polling比特置1，可以加快处理速度。MAC实体不需要等LCP结束，确定哪一个RLC PDU是当前MAC PDU内的最后一个RLC PDU时，再确定加polling。将多个RLC PDU中的polling比特置1，可以增加polling的可靠性，如果传输过程中其中一个polling比特发生错误，可以通过其它的polling比特弥补。
在本发明的另一实施例中，上述Polling触发方法四、五和六中，如果引入CBG重传，某一部分CBG传输总是失败，而第0-n个CB成功收到，物理层实体可以将第0-n个CB直接发生给MAC实体，MAC实体如果能根据这0-n个CB识别出MAC SDU，就向相应的RLC实体递交，RLC实体收到后，如果发现有polling比特为1，就可以启动RLC重传。在这种场景下，一种处理方式是在MAC PDU中，RLC实体在来自同一个RLC实体的多个RLC PDU中，选择第一个RLC PDU，将其polling比特置1。
在本发明的另一实施例中，上述Polling触发方法四、五和六中，接收端收到带polling的MAC PDU后，无论该MAC PDU中带有几个polling比特，都只发一个状 态报告。并且发送状态报告时，只考虑目前RLC已经收到那些RLC PDU，没有收到那些RLC PDU，不考虑从那个RLC PDU的RLC头中收到polling比特。
在本发明的另一实施例中，所述发送端的RLC实体触发RLC polling后，不通知所述发送端的MAC实体。所述发送端的MAC实体生成MAC PDU时，不论最后一个RLC PDU是否需要分段，都将该MAC PDU中的最后一个RLC PDU的SN通知所述发送端的RLC实体。
如果所述MAC PDU中的最后一个RLC PDU需要分段，所述发送端的RLC实体将分段后的RLC PDU segment发给所述发送端的MAC实体，将该最后一个RLC PDU的polling比特置1，如图10所示，为本发明的另一实施例的另一种触发RLC Polling方法的过程状态图。
如果所述MAC PDU中的最后一个RLC PDU没有被分段，所述发送端的RLC实体将所述最后一个RLC PDU SN发给所述发送端的MAC实体，将该最后一个RLC PDU的polling比特置1，也发给所述发送端的MAC实体，如图11所示，为本发明的另一实施例的另一种触发RLC Polling方法的过程状态图。
当所述MAC PDU中的最后一个RLC PDU没有被分段，所述发送端的RLC实体从T2时刻开始，重启t-PollRetransmit，PDU_WITHOUT POLL的值从1开始，polling bit＝1携带在序列号为37号的RLC PDU数据包中，序列号为38号RLC PDU数据包属于没有被触发RLC polling的，将数据1计入下一轮的PDU_WITHOUT POLL中。同理，此时BYTE_WITHOUT POLL的值从X开始，其中，所述X是序列号为38号RLC PDU数据包的数据量大小值，因为polling bit＝1携带在序列号为37号的RLC PDU数据包中，序列号为38号RLC PDU数据包属于没有被触发RLC polling的，所以所述X需要要计入下一轮的BYTE_WITHOUT POLL中。
当序列号为37号的RLC PDU数据包被被分段时，BYTE_WITHOUT POLL还可以有另一种方式：从X开始(X是序列号为37号的RLC PDU数据包中还未被传输的部分的大小，加上序列号为38号的RLC PDU数据包的大小)，因为polling Bit携带在序列号为37号的RLC PDU数据包的第一个分段segment中，序列号为38号的RLC PDU数据包属于没有被RLC polling的，因此，序列号为38号的RLC PDU数据包的数据量大小需要计入下一轮的BYTE_WITHOUT POLL中。
在本发明的另一实施例中，所述发送端的RLC实体触发RLC polling后，对后面的多个RLC PDU的全部或部分的polling bit比特置1，直到收到所述发送端的MAC实体指示polling比特已经发送的信息，此时，所述发送端的RLC实体停止对后续发往所述发送端的MAC实体的RLC PDU的RLCpolling比特置1，如图12所示，为本发明的另一实施例的另一种触发RLC Polling方法的过程状态图。如图12，所述发送端的MAC实体收到序列号为38号的RLC PDU的polling bit＝1后，向所述发送端的所述RLC实体发送状态报告请求为激活已经发送信息。
在本发明的另一实施例中，所述发送端的MAC实体向所述发送端的RLC实体指示的也可以是序列号SN为38号的RLC PDU已经发送了，也可以是请求将序列号 SN为38号的RLC PDU进行分段的信息。
如果所述发送端的所述MAC实体向所述发送端的所述RLC实体指示了RLC PDU SN，所述发送端的所述RLC实体可以修改原来曾经发给所述发送端的所述MAC实体的RLC PDU，如图13所示，为本发明的另一实施例的另一种触发RLC Polling方法的过程状态图。如图13，所述发送端的所述MAC实体在空口发送后，向所述发送端的所述RLC实体指示MAC PDU中最后一个RLC PDU SN是37的信息，所述发送端的所述RLC实体收到后，发现序列号为38号的RLC PDU数据包已经发送给所述发送端的所述MAC实体，并且对应的polling比特是1，于是所述发送端的所述RLC实体再次向所述发送端的所述MAC实体发送序列号为38号的RLC PDU数据包，将polling比特置0。
如图14，为本发明的另一实施例的另一种触发RLC Polling方法的过程状态图，所述发送端的所述RLC实体确定触发RLC polling后，向所述MAC发送通知消息，所述通知消息可以携带或不携带一个RLC PDU SN带。如果所述通知消息携带RLC PDU SN，所述发送端的所述MAC实体将所述RLC PDU SN对应的RLC PDU的polling比特置1；如果所述通知消息没有携带RLC PDU SN，所述发送端的所述MAC实体根据收到通知消息的时机，确定将哪一个RLC PDU的polling比特置1，例如，所述发送端的所述MAC实体收到所述通知消息后，将下一个从所述发送端的所述RLC实体收到的RLC PDU的polling比特置1。所述发送端的所述MAC实体也可以将一个或多个RLC PDU的polling比特置1，在空口发送。
可选地，所述发送端的所述RLC实体将RLC polling已经触发信息通知所述发送端的所述MAC实体时，将PDU_WITHOUT_POLL和BYTE_WITHOUT_POLL置0，重新开始计数，重启T_PollRetransmit。在本发明的另一实施例中，所述发送端的所述MAC实体自行将序列号为X的RLC PDU头中的polling比特改成1时，将已经将RLC SN＝X的包的polling改成1信息向所述发送端的所述RLC实体发送，所述发送端的所述RLC实体收到该该已经将RLC SN＝X的包的polling改成1信息后，将PDU_WITHOUT_POLL和BYTE_WITHOUT_POLL置0，重新开始计数，重启T_PollRetransmit。
如图15，为本发明的另一实施例的另一种触发RLC Polling方法的过程状态图，所述发送端的所述MAC实体收到一个MAC PDU后，如果发现同一逻辑信道有多个RLC PDU，将所述多个RLC PDU发送给所述发送端的RLC实体，并指示所述多个RLC PDU来自同一个MAC PDU。
所述发送端的所述RLC实体收到多个RLC PDU后，只要有任何一个或多个RLC PDU的polling比特为1，就认为这批RLC PDU中RLC SN最高的那个RLC PDU触发了RLC polling，且polling比特为1，例如如图15，接收端确定：RLC PDU SN＝37的RLCPDU数据包触发了polling。所以，所述接收端的RLC实体在判定是否生成状态报告时，以RLC PDU SN＝37为准生成状态报告时，将RLC PDU SN＝37之前的数据包的接收情况都包含在内。
如图16所示，为本发明一实施例的一种RLC控制PDU(RLC control PDU)的数据结构示意图，本实施例的RLC control PDU可以用于实现NR中的polling功能，用RLC Control PDU来指示接收端发送状态报告。
如下图16所示，D/C表示该PDU是数据PDU(data PDU)还是控制PDU(control PDU)；CPT表示该control PDU的类型，可以设置为与现有CPT不同的任一CPT值；POLL_SN表示触发该状态报告的RLC control PDU的SN，这个SN值可以是以其对应的RLC PDU为准生成状态报告的POLL_SN的值，也可以是当前发送窗口中其他RLC PDU的SN值，图16中的例子为SN为10bit的情况，但具体情况下不仅限于该SN长度。
下面对于RLC状态报告的描述中，各个字段的长度仅仅是个举例，具体实施中，各个字段可以使用不同的长度。
如图17所示，为本发明另一实施例的一种RLC状态报告格式(RLC status PDU)的结构示意图，所述RLC status PDU用于实现NR中的状态报告反馈。
对于RLC PDU的序列号SN位于VR(R)<＝SN<＝VR(MS)之间，并且从VR(R)开始到低层指示的大小RLC_SN_LENGTH之间的AMD PDU，从前往后生成状态报告。因此，需要生成状态报告的范围是VR(R)<＝SN<＝min{VR(MS),VR(R)+RLC_SN_LENGTH}。据此，我们为NR的状态反馈报告定义如下格式，其中，所述VR(R)的值表示RLC PDU的序列号且为所述接收端当前期望接收的RLC PDU对应的序列号，VR(MS)的值表示RLC PDU的序列号且为所述接收端当前已收到的最高RLC PDU对应的序列号加1。其中，所述RLC_SN_LENGTH表示RLC SN这个字段所占的bit数，所述AMD PDU为RLC AM模式下的RLC PDU，AMD SDU为RLC AM模式下的RLC SDU。
如图17所示，所述RLC状态报告格式的参数如下描述。
D/C表示该PDU是data PDU还是control PDU。
控制PDU的类型(Control PDU TYPE，CPT)表示该control PDU的类型，可以设置为与现有CPT不同的任一CPT值。
NACK_SN为接收端认为丢失了的AMD SDU或者AMD SDU分段的SN值。
E1表示“NACK_SN_START+NACK_SN_END+E1+E2+E3”或“ACK_SN+E1”之后是否紧跟着另外一个“NACK_SN_START+NACK_SN_END+E1+E2+E3”组合。值为0时对应“否”，值为1时对应“是”。所述NACK_SN_START是表示接收端未收到的多个连续的RLC PDU中的第一个RLC PDU的SN，所述NACK_SN_END是表示接收端未收到的多个连续的RLC PDU中的最后一个RLC PDU的SN。
E2表示“NACK_SN_START+NACK_SN_END+E1+E2+E3”组合之后是否紧跟着“RANGEstart”。值为0时对应“否”，表明第一个PDU是完整的SDU；值为1时对应“是”，表示第一个PDU是RLC SDU分段。其中，所述RANGEstart表示RLC SDU分段(RLC SDU segement)在NACK_SN_START对应的RLC SDU中起始位置。
E3表示“NACK_SN_START+NACK_SN_END+E1+E2+E3”组合之后是否紧跟着“RANGEend”。值为0时对应“否”，表明最后一个PDU是完整的RLC SDU；值为1时对应“是”，表示最后一个PDU是RLC SDU分段。
ACK_SN表示在该SN之前，除了NACK_SN表示丢失的包之外，其他的包均已经收到。
可选的，如果“NACK_SN_START＝NACK_SN_END”。表示当前丢失的RLC PDU或分段只有一个。该RLC状态报告格式主要应用于丢失的RLC PDU或者分段数量较多的情况，可以通过RRC配置来实现与上述的其他status PDU格式的转换。
依照上述格式，一共有6种组合，结果显示对于这6种可能组合，上述RLC状态报告格式都能唯一的指示，如表1所示。
表1
Figure PCTCN2018085742-appb-000001
图17所示的例子中，NACK_SN_START和NACK_SN_END的长度相同，在 本发明的另一实施例中，所述NACK_SN_START和NACK_SN_END的长度也可以不同，例如，NACK_SN_END的长度小于NACK_SN_START的长度，比如：NACK_SN_END的长度为S比特，NACK_SN_START的长度为L比特，L>＝S，这种格式表示NACK_SN_END的高位比特(共L-S比特)与NACK_SN_START的高位比特相同，NACK_SN_END的低位比特(共S比特)与NACK_SN_START的低位比特不同。
如图17a所示，为本发明另一实施例的另一种RLC状态报告格式(RLC status PDU)的结构示意图，所述RLC status PDU用于实现NR中的状态报告反馈。
对于RLC PDU的序列号SN位于VR(R)<＝SN<＝VR(MS)之间，并且从VR(R)开始到低层指示的大小RLC_SN_LENGTH之间的AMD PDU，按照RLC SN的升序生成状态报告。因此，需要生成状态报告的范围是VR(R)<＝SN<＝min{VR(MS)，VR(R)+RLC_SN_LENGTH}。据此，为NR的状态反馈报告定义如图17a的格式，其中，所述VR(R)的值表示RLC PDU的序列号且为所述接收端当前期望接收的RLC PDU对应的序列号，VR(MS)的值表示RLC PDU的序列号且为所述接收端当前已收到的最高RLC PDU对应的序列号加1。其中，所述RLC_SN_LENGTH表示RLC SN这个字段所占的bit数，所述AMD PDU为RLC AM模式下的RLC PDU，AMD SDU为RLC AM模式下的RLC SDU。
如图17a所示，所述RLC状态报告格式的参数如下描述。
D/C比特表示该RLC PDU是RLC data PDU还是RLC control PDU，D/C比特为0，表示对应的RLC PDU为一个RLC data PDU,D/C比特为1，表示对应的RLC PDU为一个RLC control PDU。
控制PDU的类型(Control PDU TYPE，CPT)表示该RLC control PDU的类型，例如，CPT值为1表示RLC control PDU是一个RLC状态报告，CPT值为0表示RLC control PDU是其它类型的RLC control PDU。
E1表示“NACK_SN_START+NACK_SN_END+E1+E2+E3”或“ACK_SN+E1”之后是否紧跟着另外一个“NACK_SN_START+NACK_SN_END+E1+E2+E3”组合。E1值为0时对应“否”，E1值为1时对应“是”。所述NACK_SN_START是表示接收端未收到的多个连续的RLC PDU中的第一个RLC PDU的SN，所述NACK_SN_END是表示接收端未收到的多个连续的RLC PDU中的最后一个RLC PDU的SN。
E2表示“NACK_SN_START+NACK_SN_END+E1+E2+E3”组合之后是否紧跟着“RANGEstart”。E2值为0时对应“否”，表明第一个PDU是完整的SDU；E2值为1时对应“是”，表示第一个PDU是RLC SDU分段。其中，所述RANGEstart表示RLC SDU分段(RLC SDU segement)在NACK_SN_START对应的RLC SDU中起始位置。在本发明的另一实施例中，RLC SDU分段中的第一个字节在NACK_SN_START对应的RLC SDU中的字节位置。
E3表示“NACK_SN_START+NACK_SN_END+E1+E2+E3”组合之后是否紧跟着“RANGEend”。E3值为0时对应“否”，表明最后一个RLC PDU是完整的RLC SDU； E3值为1时对应“是”，表示最后一个RLC PDU是RLC SDU分段。在本发明的另一实施例中，所述RANGEend表示RLC SDU分段在NACK_SN_END对应的RLC SDU中最后位置，即RLC SDU分段中的最后一个字节在NACK_SN_END对应的RLC SDU中的字节位置。
ACK_SN表示在该SN之前，除了NACK_SN表示丢失的包之外，其他的包均已经收到。在本发明的另一实施例中，ACK_SN表示在该SN之前，除了NACK_SN_START到相对应NACK_SN_END表示连续丢失的包之外，其他的包均已经收到。
可选的，如果“NACK_SN_START＝NACK_SN_END”，表示当前丢失的RLC SDU或分段只有一个。该RLC状态报告格式主要应用于丢失的RLC SDU或者分段数量较多的情况，可以通过RRC配置来实现与上述的其他status PDU格式的转换。
依照上述格式，一共有6种组合，结果显示对于这6种可能组合，上述RLC状态报告格式都能唯一的指示，如表1a所示。
表1a
Figure PCTCN2018085742-appb-000002
如图18所示，为本发明另一实施例的一种RLC状态报告格式(RLC status PDU)的结构示意图，所述RLC status PDU用于实现NR中的状态报告反馈。
对于SN位于VR(R)<＝SN<＝VR(MS)之间，并且从VR(R)开始到低层指示的大小RLC_SN_LENGTH之间的AMD PDU，从前往后生成状态报告，因此，需要生成状态报告的范围是VR(R)<＝SN<＝min{VR(MS)，VR(R)+RLC_SN_LENGTH}。
如图18所示，另一所述RLC状态报告格式的参数如下描述。
D/C表示该PDU是data PDU还是control PDU。
CPT表示该control PDU的类型，可以设置为与现有CPT不同的任一CPT值。
NACK_SN为接收端认为丢失了的AMD PDU或者AMDPDU分段的SN值。
E1表示“NACK_SN_START+E2+RANGEstart+NACK_SN_END+E3+RANGEend”或“ACK_SN+E1”之后是否紧跟着另外一个“NACK_SN_START+E2+RANGEstart+NACK_SN_END+E3+RANGEend”组合。值为0时对应“否”，值为1时对应“是”。其中，所述RANGEstart表示RLC SDU分段(RLC SDU segement)在NACK_SN_START对应的RLC SDU中起始位置。所述RANGEend表示RLC SDU分段(RLC SDU segement)在NACK_SN_START对应的RLC SDU中最后位置。
E2表示“NACK_SN_START”之后是否紧跟着“RANGEstart”。值为0时对应“否”，表明第一个PDU是完整的SDU；值为1时对应“是”，表示第一个PDU是RLC SDU分段。
E3表示“NACK_SN_END”之后是否紧跟着“RANGEend”。值为0时对应“否”，表明最后一个PDU是完整的SDU；值为1时对应“是”，表示最后一个PDU是RLC SDU分段。
ACK_SN表示在该SN之前，除了NACK_SN表示丢失的包之外，其他的包均已经收到。
特别地，如果“NACK_SN_START＝NACK_SN_END”。表示当前丢失的RLC PDU或分段只有一个，该状态报告格式主要应用于丢失的RLC PDU或者分段数量较多的情况，可以通过RRC配置来实现与上述的其他status PDU格式的转换。
依照上述格式，一共有6种组合。结果显示对于这6种可能组合，上述RLC状态报告格式都能唯一的指示，如表2所示。
表2
Figure PCTCN2018085742-appb-000003
Figure PCTCN2018085742-appb-000004
图18所示的例子中，NACK_SN_START和NACK_SN_END的长度相同，在本发明的另一实施例中，所述NACK_SN_START和NACK_SN_END的长度不同，例如，NACK_SN_END的长度小于NACK_SN_START的长度，例如，NACK_SN_END的长度为S比特，NACK_SN_START的长度为L比特，L>＝S，这种格式表示NACK_SN_END的高位比特(共L-S比特)与NACK_SN_START的高位比特相同，NACK_SN_END的低位比特(共S比特)与NACK_SN_START的低位比特不同。
如图18a所示，为本发明另一实施例的另一种RLC状态报告格式(RLC status PDU)的结构示意图，所述RLC status PDU用于实现NR中的状态报告反馈。
对于SN位于VR(R)<＝SN<＝VR(MS)之间，并且从VR(R)开始到低层指示的大小RLC_SN_LENGTH之间的AMD PDU，从前往后生成状态报告，因此，需要生成状态报告的范围是VR(R)<＝SN<＝min{VR(MS)，VR(R)+RLC_SN_LENGTH}。
如图18a所示，另一所述RLC状态报告格式的参数如下描述。
D/C比特表示该RLC PDU是RLC data PDU还是RLC control PDU，D/C比特为0，表示对应的RLC PDU为一个RLC data PDU,D/C比特为1，表示对应的RLC PDU为一个RLC control PDU。
CPT表示该RLC control PDU的类型，例如，CPT值为1表示RLC control PDU是一个RLC状态报告，CPT值为0表示RLC control PDU是其它类型的RLC control PDU。
E1表示“NACK_SN_START+E2+RANGEstart+NACK_SN_END+ E3+RANGEend”或“ACK_SN+E1”之后是否紧跟着另外一个“NACK_SN_START+E2+RANGEstart+NACK_SN_END+E3+RANGEend”组合。E1值为0时对应“否”，E1值为1时对应“是”。其中，所述RANGEstart表示RLC SDU分段(RLC SDU segement)在NACK_SN_START对应的RLC SDU中起始位置。所述RANGEend表示RLC SDU分段(RLC SDU segement)在NACK_SN_START对应的RLC SDU中最后位置。
在本发明的另一实施例中，E1也可以表示“NACK_SN_START+E2+RANGEstart+NACK_SN_END+E3+RANGEend”或“ACK_SN+E1”之后是否紧跟着另外一个“NACK_SN_START+E2+RANGEstart+NACK_SN_END+E3+RANGEend”组合。E1值为0时对应“否”，E1值为1时对应“是”。其中，所述NACK_SN_START是表示接收端未收到的多个连续的RLC PDU中的第一个RLC PDU的SN，所述NACK_SN_END是表示接收端未收到的多个连续的RLC PDU中的最后一个RLC PDU的SN。所述RANGEstart表示RLC SDU分段(RLC SDU segement)在NACK_SN_START对应的RLC SDU中起始位置，即RLC SDU分段中的第一个字节在NACK_SN_START对应的RLC SDU中的字节位置。所述RANGEend表示RLC SDU分段(RLC SDU segement)在NACK_SN_END对应的RLC SDU中最后位置，即RLC SDU分段中的最后一个字节在NACK_SN_END对应的RLC SDU中的字节位置。
E2表示“NACK_SN_START”之后是否紧跟着“RANGEstart”。E2值为0时对应“否”，表明第一个PDU是完整的SDU；E2值为1时对应“是”，表示第一个PDU是RLC SDU分段。
E3表示“NACK_SN_END”之后是否紧跟着“RANGEend”。E3值为0时对应“否”，表明最后一个PDU是完整的SDU；E3值为1时对应“是”，表示最后一个PDU是RLC SDU分段。
ACK_SN表示在该SN之前，除了NACK_SN表示丢失的包之外，其他的包均已经收到。在本发明的另一实施例中，ACK_SN表示在该SN之前，除了NACK_SN_START到相对应NACK_SN_END表示连续丢失的包之外，其他的包均已经收到。
特别地，如果“NACK_SN_START＝NACK_SN_END”。表示当前丢失的RLC SDU或分段只有一个，该状态报告格式主要应用于丢失的RLC SDU或者分段数量较多的情况，可以通过RRC配置来实现与上述的其他status PDU格式的转换。
依照上述格式，一共有6种组合。结果显示对于这6种可能组合，上述RLC状态报告格式都能唯一的指示，如表2a所示。
表2a
Figure PCTCN2018085742-appb-000005
Figure PCTCN2018085742-appb-000006
如图19所示，为本发明另一实施例的一种RLC状态报告格式(RLC status PDU)的结构示意图，所述RLC status PDU用于实现NR中的状态报告反馈。
对于SN位于VR(R)<＝SN<＝VR(MS)之间，并且从VR(R)开始到低层指示的大小RLC_SN_LENGTH之间的AMD PDU，从前往后生成状态报告。因此，需要生成状态报告的范围是VR(R)<＝SN<＝min{VR(MS)，VR(R)+RLC_SN_LENGTH}。
D/C表示该PDU是data PDU还是control PDU。
CPT表示该control PDU的类型，可以设置为与现有CPT不同的任一CPT值。
NACK_SN为接收端认为丢失了的AMD SDU或者AMD SDU分段的SN值。
E1表示“NACK_SN+E1+E2+E3+RANGEstart+RANGEend”或“ACK_SN+E1”之后是否紧跟着另外一个“NACK_SN+E1+E2+E3+RANGEstart+RANGEend”组合。值为0时对应“否”，值为1时对应“是”。
E2表示“NACK_SN_START”之后是否紧跟着“RANGEstart+RANGEend”。值为0时对应“否”，表明是丢失的是完整的SDU；值为1时对应“是”，表示该SDU的一个分段丢失。
E3表示“RANGEstart+RANGEend”之后是否紧跟着“RANGEstart+RANGEend”。值为0时对应“否”，表明该组合是当前RLC SDU中最后一个；值为1时对应“是”，表示后面仍然跟随着一个“RANGEstart+RANGEend”。
ACK_SN表示在该SN之前，除了NACK_SN表示丢失的包之外，其他的包 均已经收到。
如图19a所示，为本发明另一实施例的另一种RLC状态报告格式(RLC status PDU)的结构示意图，所述RLC status PDU用于实现NR中的状态报告反馈。
对于SN位于VR(R)<＝SN<＝VR(MS)之间，并且从VR(R)开始到低层指示的大小RLC_SN_LENGTH之间的AMD PDU，从前往后生成状态报告。因此，需要生成状态报告的范围是VR(R)<＝SN<＝min{VR(MS)，VR(R)+RLC_SN_LENGTH}。
D/C比特表示该RLC PDU是RLC data PDU还是RLC control PDU，D/C比特为0，表示对应的RLC PDU为一个RLC data PDU,D/C比特为1，表示对应的RLC PDU为一个RLC control PDU。
CPT表示该RLC control PDU的类型，例如，CPT值为1表示RLC control PDU是一个RLC状态报告，CPT值为0表示RLC control PDU是其它类型的RLC control PDU。
NACK_SN为接收端认为丢失了的AMD SDU或者AMD SDU分段的SN值。
E1表示“NACK_SN+E1+E2+E3+RANGEstart+RANGEend”或“ACK_SN+E1”之后是否紧跟着另外一个“NACK_SN+E1+E2+E3+RANGEstart+RANGEend”组合。E1值为0时对应“否”，E1值为1时对应“是”。
E2表示“NACK_SN_START”之后是否紧跟着“RANGEstart+RANGEend”。E2值为0时对应“否”，表明是丢失的是完整的SDU；E2值为1时对应“是”，表示该SDU的一个分段丢失。
在本发明的另一实施例中，E2也可以表示“NACK_SN”之后是否紧跟着“RANGEstart+RANGEend”。E2值为0时对应“否”，表明是丢失的是完整的SDU；E2值为1时对应“是”，表示该SDU的一个分段丢失。其中，所述RANGEstart表示RLC SDU分段在NACK_SN对应的RLC SDU中起始位置，即RLC SDU分段中的第一个字节在NACK_SN对应的RLC SDU中的字节位置。所述RANGEend表示RLC SDU分段在NACK_SN对应的RLC SDU中最后位置，即RLC SDU分段中的最后一个字节在NACK_SN对应的RLC SDU中的字节位置。
E3表示“RANGEstart+RANGEend”之后是否紧跟着“RANGEstart+RANGEend”。E3值为0时对应“否”，表明该组合是当前RLC SDU中最后一个；E3值为1时对应“是”，表示后面仍然跟随着一个“RANGEstart+RANGEend”。
ACK_SN表示在该SN之前，除了NACK_SN表示丢失的包之外，其他的包均已经收到。
这种状态报告特别适用于数据包特别大的时候，比如NR中同意支持的巨大包(jumbo packet)。可以通过RRC配置来实现与上述的其他status PDU格式的转换，依照上述图19或19a的格式，一共有3种组合，如表3所示。
表3
Figure PCTCN2018085742-appb-000007
在本发明的另一实施例中，如果接收端认为没有收到的分段比较零散，也可以集中反馈一个比较大的分段，以减小RLC状态报告的尺寸。比如20-22，25-28，30-45这三个小分段没有收到，接收端生成一个状态报告，通知发送端“20-45”这一段都没有收到，请重传。
如图20所示，为本发明另一实施例的一种RLC状态报告格式(RLC status PDU)的结构示意图，所述RLC status PDU用于实现NR中的状态报告反馈。
对于SN位于VR(R)<＝SN<＝VR(MS)之间，并且从VR(R)开始到低层指示的大小RLC_SN_LENGTH之间的AMD PDU，从前往后生成状态报告。因此，需要生成状态报告的范围是VR(R)<＝SN<＝min{VR(MS)，VR(R)+RLC_SN_LENGTH}。
D/C表示该PDU是data PDU还是control PDU。
CPT表示该control PDU的类型，可以设置为与现有CPT不同的任一CPT值。
NACK_SN为接收端认为丢失了的AMD PDU或者AMDPDU分段的SN值。
E1表示“NACK_SN_START+E2+RANGEstart+bitmap+E3+RANGEend”或“ACK_SN+E1”之后是否紧跟着另外一个“NACK_SN_START+E2+RANGEstart+bitmap+E3+RANGEend”组合。值为0时对应“否”，值为1时对应“是”。
E2表示“NACK_SN_START”之后是否紧跟着“RANGEstart”。值为0时对应“否”，表明第一个PDU是完整的SDU；值为1时对应“是”，表示第一个PDU是RLC SDU分段。
Bitmap用来指示相应位置上的RLC SDU或分段是否丢失。如果丢失，bitmap的值为0；否则，bitmap的值为1。图中的例子中bitmap的长度为10bit，但是应用中不仅限于10bit的长度。
E3表示之后是否紧跟着“RANGEend”。值为0时对应“否”，表明bitmap中最后一个为0的位所指示的RLC PDU是完整丢失的RLC SDU；值为1时对应“是”，表示bitmap中最后一个为0的位所指示的RLC PDU丢失的是分段。
ACK_SN表示在该SN之前，除了NACK_SN表示丢失的包之外，其他的包均已经收到。
这种状态报告特别适用于包特别大的时候，比如NR中同意支持的jumbo packet。
如图20a所示，为本发明另一实施例的另一种RLC状态报告格式(RLC status PDU)的结构示意图，所述RLC status PDU用于实现NR中的状态报告反馈。
对于SN位于VR(R)<＝SN<＝VR(MS)之间，并且从VR(R)开始到低层指示的大小RLC_SN_LENGTH之间的AMD PDU，从前往后生成状态报告。因此，需要生成状态报告的范围是VR(R)<＝SN<＝min{VR(MS)，VR(R)+RLC_SN_LENGTH}。
D/C比特表示该RLC PDU是RLC data PDU还是RLC control PDU，D/C比特为0，表示对应的RLC PDU为一个RLC data PDU,D/C比特为1，表示对应的RLC PDU为一个RLC control PDU。
CPT表示该RLC control PDU的类型，例如，CPT值为1表示RLC control PDU是一个RLC状态报告，CPT值为0表示RLC control PDU是其它类型的RLC control PDU。
E1表示“NACK_SN_START+E2+RANGEstart+bitmap+E3+RANGEend”或“ACK_SN+E1”之后是否紧跟着另外一个“NACK_SN_START+E2+RANGEstart+bitmap+E3+RANGEend”组合。E1值为0时对应“否”，E1值为1时对应“是”。在本发明的另一实施例中，所述NACK_SN_START是表示bitmap中第一位所指示的RLC PDU的SN。
E2表示“NACK_SN_START”之后是否紧跟着“RANGEstart”。E2值为0时对应“否”，表明第一个PDU是完整的SDU；E2值为1时对应“是”，表示第一个PDU是RLC SDU分段。在本发明的另一实施例中，，所述RANGEstart表示RLC SDU分段在NACK_SN_START对应的RLC SDU中起始位置，即RLC SDU分段中的第一个字节在NACK_SN_START对应的RLC SDU中的字节位置。
Bitmap用来指示相应位置上的RLC SDU或分段是否丢失。如果丢失，bitmap的值为0；否则，bitmap的值为1。图中的例子中bitmap的长度为10bit，但是应用中不仅限于10bit的长度。
E3表示之后是否紧跟着“RANGEend”。E3值为0时对应“否”，表明bitmap中最后一个为0的位所指示的RLC PDU是完整丢失的RLC SDU；E3值为1时对应“是”，表示bitmap中最后一个为0的位所指示的RLC PDU丢失的是RLC SDU的分段。在本发明的另一实施例中，所述RANGEend表示该RLC SDU分段在对应的RLC SDU中最后位置，即RLC SDU分段中的最后一个字节在对应RLC SDU中的字节位置。
ACK_SN表示在该SN之前，除了NACK_SN表示丢失的包之外，其他的包均已经收到。
这种状态报告特别适用于包特别大的时候，比如NR中同意支持的jumbo packet。
如图21所示，为本发明另一实施例的一种RLC状态报告格式(RLC status  PDU)的结构示意图，所述RLC status PDU用于实现NR中的状态报告反馈。
对于SN位于VR(R)<＝SN<＝VR(MS)之间，并且从VR(R)开始到低层指示的大小RLC_SN_LENGTH之间的AMD PDU，从前往后生成状态报告。因此，需要生成状态报告的范围是VR(R)<＝SN<＝min{VR(MS)，VR(R)+RLC_SN_LENGTH}。
D/C表示该PDU是data PDU还是control PDU。
CPT表示该control PDU的类型，可以设置为与现有CPT不同的任一CPT值。
NACK_SN为接收端认为丢失了的AMD PDU或者AMDPDU分段的SN值。
E1表示“NACK_SN_START+E2+RANGEstart+SN_RANGE+E3+RANGEend”或“ACK_SN+E1”之后是否紧跟着另外一个“NACK_SN_START+E2+RANGEstart+SN_RANGE+E3+RANGEend”组合。值为0时对应“否”，值为1时对应“是”。
E2表示“NACK_SN_START”之后是否紧跟着“RANGEstart”。值为0时对应“否”，表明第一个PDU是完整的SDU；值为1时对应“是”，表示第一个PDU是RLC SDU分段。SN_RANGE用来表示在NACK_SN_START之后连续丢失的RLC PDU或者分段的个数。图中用10bit来表示，实际情况下不仅限于该情况。
E3表示之后是否紧跟着“RANGEend”。值为0时对应“否”，表明SN_RANGE所指示的最后一个RLC PDU是完整丢失的RLC SDU；值为1时对应“是”，表明SN_RANGE所指示的最后一个RLC PDU丢失的是RLC SDU分段。
ACK_SN表示在该SN之前，除了NACK_SN表示丢失的包之外，其他的包均已经收到。
这种状态报告比较灵活，可以指示连续丢失的包个数为0～1024的不同情况。
如图21a所示，为本发明另一实施例的另一种RLC状态报告格式(RLC status PDU)的结构示意图，所述RLC status PDU用于实现NR中的状态报告反馈。
对于SN位于VR(R)<＝SN<＝VR(MS)之间，并且从VR(R)开始到低层指示的大小RLC_SN_LENGTH之间的AMD PDU，从前往后生成状态报告。因此，需要生成状态报告的范围是VR(R)<＝SN<＝min{VR(MS)，VR(R)+RLC_SN_LENGTH}。
D/C比特表示该RLC PDU是RLC data PDU还是RLC control PDU，D/C比特为0，表示对应的RLC PDU为一个RLC data PDU,D/C比特为1，表示对应的RLC PDU为一个RLC control PDU。
CPT表示该RLC control PDU的类型，例如，CPT值为1表示RLC control PDU是一个RLC状态报告，CPT值为0表示RLC control PDU是其它类型的RLC control PDU。
E1表示“NACK_SN_START+E2+RANGEstart+SN_RANGE+E3+RANGEend”或“ACK_SN+E1”之后是否紧跟着另外一个“NACK_SN_START+E2+RANGEstart+SN_RANGE+E3+RANGEend”组合。E1值为0 时对应“否”，E1值为1时对应“是”。
在本发明的另一实施例中，NACK_SN_START表示接收端未收到的多个连续的RLC PDU中的第一个RLC PDU的SN。
E2表示“NACK_SN_START”之后是否紧跟着“RANGEstart”。E2值为0时对应“否”，表明第一个PDU是完整的SDU；E2值为1时对应“是”，表示第一个PDU是RLC SDU分段。在本发明的另一实施例中，所述RANGEstart表示RLC SDU分段在NACK_SN_START对应的RLC SDU中的起始位置，即RLC SDU分段中的第一个字节在NACK_SN_START对应的RLC SDU中的字节位置。SN_RANGE用来表示在NACK_SN_START之后连续丢失的RLC PDU或者分段的个数。图中用10bit来表示，实际情况下不仅限于该情况。在本发明的另一实施例中SN_RANGE对应的连续丢失的RLC PDU，包括NACK_SN_START对应的第一个丢失的RLC PDU，并且包括最后一个丢失的RLC PDU。此时，如果丢失的RLC PDU只有一个，SN_RANGE值为1。
可选地，SN_RANGE对应的连续丢失的RLC PDU，可以不包括NACK_SN_START对应的第一个丢失的RLC PDU，并且包括最后一个丢失的RLC PDU。此时，如果丢失的RLC PDU只有一个，SN_RANGE值为0。
可选地，SN_RANGE对应的连续丢失的RLC PDU，可以包括NACK_SN_START对应的第一个丢失的RLC PDU，并且不包括最后一个丢失的RLC PDU。此时，如果丢失的RLC PDU只有一个，SN_RANGE值为0。
E3表示之后是否紧跟着“RANGEend”。E3值为0时对应“否”，表明SN_RANGE所指示的最后一个RLC PDU是完整丢失的RLC SDU；E3值为1时对应“是”，表明SN_RANGE所指示的最后一个RLC PDU丢失的是RLC SDU分段。在本发明的另一实施例中，所述RANGEend表示该RLC SDU分段在对应RLC SDU中的最后位置，即RLC SDU分段中的最后一个字节在对应RLC SDU中的字节位置。
ACK_SN表示在该SN之前，除了NACK_SN表示丢失的包之外，其他的包均已经收到。在本发明的另一实施例中，ACK_SN表示在该SN之前，除了从NACK_SN_START开始连续丢失的包之外，其他的包均已经收到。
这种状态报告比较灵活，可以指示连续丢失的包个数为0～1024的不同情况。
如图21b所示，为本发明另一实施例的另一种RLC状态报告格式(RLC status PDU)的结构示意图，所述RLC status PDU用于实现NR中的状态报告反馈。
对于SN位于VR(R)<＝SN<＝VR(MS)之间，并且从VR(R)开始到低层指示的大小RLC_SN_LENGTH之间的AMD PDU，从前往后生成状态报告。因此，需要生成状态报告的范围是VR(R)<＝SN<＝min{VR(MS),VR(R)+RLC_SN_LENGTH}。
D/C比特表示该RLC PDU是RLC data PDU还是RLC control PDU，D/C比特为0，表示对应的RLC PDU为一个RLC data PDU,D/C比特为1，表示对应的RLC PDU为一个RLC control PDU。
CPT表示该RLC control PDU的类型，例如，CPT值为1表示RLC control PDU 是一个RLC状态报告，CPT值为0表示RLC control PDU是其它类型的RLC control PDU。
E1表示“NACK_SN_START+RANGEstart+SN_RANGE+RANGEend”或“ACK_SN+E1”之后是否紧跟着另外一个“NACK_SN_START+RANGEstart+SN_RANGE+RANGEend”组合。E1值为0时对应“否”，E1值为1时对应“是”。
NACK_SN_START是表示接收端未收到的多个连续的RLC PDU中的第一个RLC PDU的SN。
RANGEstart表示第一个丢失的RLC PDU所对应的完整RLC SDU或RLC SDU分段在NACK_SN_START对应的RLC SDU中的起始位置，即第一个丢失的RLC PDU所对应的完整RLC SDU或RLC SDU分段中的第一个字节在NACK_SN_START对应的RLC SDU中的字节位置。
RANGEend表示最后一个丢失的RLC PDU所对应的完整RLC SDU或RLC SDU分段在相应RLC SDU中的最后位置，即最后一个丢失的RLC PDU所对应的完整RLC SDU或RLC SDU分段中的最后一个字节在对应RLC SDU中的字节位置。如果丢失的最后一个RLC PDU是一个完整的RLC SDU，或者相应RLC SDU的最后一个分段，RANGEend＝该RLC SDU大小。可选地，如果丢失的最后一个RLC PDU是一个完整的RLC SDU，或者相应RLC SDU的最后一个分段，RANGEend＝0。可选地，如果丢失的最后一个RLC PDU是一个完整的RLC SDU，或者相应RLC SDU的最后一个分段，RANGEend＝‘1111111111’。
SN_RANGE用来表示在NACK_SN_START之后连续丢失的RLC PDU的个数。图中用10bit来表示，实际情况下不仅限于该情况。SN_RANGE对应的连续丢失的RLC PDU，包括NACK_SN_START对应的第一个丢失的RLC PDU，并且包括最后一个丢失的RLC PDU。此时，如果丢失的RLC PDU只有一个，SN_RANGE值为1。
可选地，SN_RANGE对应的连续丢失的RLC PDU，可以不包括NACK_SN_START对应的第一个丢失的RLC PDU，并且包括最后一个丢失的RLC PDU。此时，如果丢失的RLC PDU只有一个，SN_RANGE值为0。
可选地，SN_RANGE对应的连续丢失的RLC PDU，可以包括NACK_SN_START对应的第一个丢失的RLC PDU，并且不包括最后一个丢失的RLC PDU。此时，如果丢失的RLC PDU只有一个，SN_RANGE值为0。ACK_SN表示在该SN之前，除了从NACK_SN_START开始连续丢失的包之外，其他的包均已经收到。
如图22所示，为本发明另一实施例的一种RLC状态报告格式(RLC status PDU)的结构示意图，所述RLC status PDU用于实现NR中的状态报告反馈。
对于SN位于VR(R)<＝SN<＝VR(MS)之间，并且从VR(R)开始到低层指示的大小RLC_SN_LENGTH之间的AMD PDU，从前往后生成状态报告。因此，需要生成状态报告的范围是VR(R)<＝SN<＝min{VR(MS),VR(R)+RLC_SN_LENGTH}。
D/C表示该PDU是data PDU还是control PDU。
CPT表示该control PDU的类型，可以设置为与现有CPT不同的任一CPT值。
NACK_SN为接收端认为丢失了的AMD SDU或者AMD SDU分段的SN值。
E1表示“NACK_SN_START+E2+RANGEstart+NACK_SN_END+E3+RANGEend”或“ACK_SN+E1”之后是否紧跟着另外一个“NACK_SN_START+E2+RANGEstart+NACK_SN_END+E3+RANGEend”组合。值为0时对应“否”，值为1时对应“是”。
E2表示“NACK_SN_START”之后是否紧跟着“RANGEstart”。值为0时对应“否”，表明第一个PDU是完整的SDU；值为1时对应“是”，表示第一个PDU是RLC SDU分段。
E3表示“NACK_SN_END”之后是否紧跟着“RANGEend”。值为0时对应“否”，表明最后一个PDU是完整的SDU；值为1时对应“是”，表示最后一个PDU是RLC SDU分段。
ACK_SN表示在该SN之前，除了NACK_SN表示丢失的包之外，其他的包均已经收到。
特别地，如果“NACK_SN_START＝NACK_SN_END”。表示当前丢失的RLC PDU或分段只有一个。
因此，依照上述格式，一共有6种组合，结果显示对于这6种可能组合，上述RLC状态报告格式都能唯一的指示，如表4所示。
表4
Figure PCTCN2018085742-appb-000008
Figure PCTCN2018085742-appb-000009
如图22a所示，为本发明另一实施例的另一种RLC状态报告格式(RLC status PDU)的结构示意图，所述RLC status PDU用于实现NR中的状态报告反馈。
对于SN位于VR(R)<＝SN<＝VR(MS)之间，并且从VR(R)开始到低层指示的大小RLC_SN_LENGTH之间的AMD PDU，从前往后生成状态报告。因此，需要生成状态报告的范围是VR(R)<＝SN<＝min{VR(MS),VR(R)+RLC_SN_LENGTH}。
D/C比特表示该RLC PDU是RLC data PDU还是RLC control PDU，D/C比特为0，表示对应的RLC PDU为一个RLC data PDU,D/C比特为1，表示对应的RLC PDU为一个RLC control PDU。
CPT表示该RLC control PDU的类型，例如，CPT值为1表示RLC control PDU是一个RLC状态报告，CPT值为0表示RLC control PDU是其它类型的RLC control PDU。
E1表示“NACK_SN_START+E2+RANGEstart+NACK_SN_END+E3+RANGEend”或“ACK_SN+E1”之后是否紧跟着另外一个“NACK_SN_START+E2+RANGEstart+NACK_SN_END+E3+RANGEend”组合。E1值为0时对应“否”，E1值为1时对应“是”。其中，所述NACK_SN_START是表示接收端未收到的多个连续的RLC PDU中的第一个RLC PDU的SN，所述NACK_SN_END是表示接收端未收到的多个连续的RLC PDU中的最后一个RLC PDU的SN
E2表示“NACK_SN_START”之后是否紧跟着“RANGEstart”。E2值为0时对应“否”，表明第一个PDU是完整的SDU；E2值为1时对应“是”，表示第一个PDU是RLC SDU分段。其中，所述RANGEstart表示RLC SDU分段(RLC SDU segement)在NACK_SN_START对应的RLC SDU中起始位置，即RLC SDU分段中的第一个字节在NACK_SN_START对应的RLC SDU中的字节位置。
E3表示“NACK_SN_END”之后是否紧跟着“RANGEend”。E3值为0时对应“否”，表明最后一个PDU是完整的SDU；E3值为1时对应“是”，表示最后一个PDU是RLC SDU分段。其中，所述RANGEend表示RLC SDU分段在NACK_SN_END对应的RLC SDU中最后位置，即RLC SDU分段中的最后一个字节在NACK_SN_END对应的RLC SDU中的字节位置。
ACK_SN表示在该SN之前，除了NACK_SN表示丢失的包之外，其他的包均已经收到。在本发明的另一实施例中，ACK_SN表示在该SN之前，除了 NACK_SN_START到相对应NACK_SN_END表示连续丢失的包之外，其他的包均已经收到。
特别地，如果“NACK_SN_START＝NACK_SN_END”。表示当前丢失的RLC PDU或分段只有一个。
因此，依照上述格式，一共有6种组合，结果显示对于这6种可能组合，上述RLC状态报告格式都能唯一的指示，如表4a所示。
表4a
Figure PCTCN2018085742-appb-000010
对于RLC PDU的包头本发明提供多个结构，例如，如图23所示，为本发明实施例的一种RLC PDU的包头的结构示意图。
基站向给基站和终端设备发送RRC信令，指示所述基站和终端设备设置各自的RLC实体和MAC实体的分段偏移(segement offset，SO)域的长度和length(L)域的长度，所述SO域表示RLC SDU分段在NACK_SN_START对应的RLC SDU中相对起始位置的偏移，所述L域表示MAC PDU中RLC PDU的长度。
基站向给基站和终端设备发送RRC信令，指示一个关于MAC实体的L域和RLC的SO域的长度的设置：MAC把这个设置理解成L域的长度，RLC实体把这个设置理解为SO域的长度，所以MAC实体的L域的长度与RLC实体SO域的长度相等。
如图23，所述RLC包头的SO域与MAC实体的L域长度相同，没有F域，所述F域指示L域的长度。F2用于指示L域的长度。
在接收端，MAC实体去掉MAC PDU的子头之后通知RLC实体L域的长度，也就通知了RLC实体的SO域的长度。
在接收端，MAC实体通知RLC实体L域的长度，之后RLC实体通过MAC实体通知的长度得到SO的长度。
如图24所示，为本发明另一实施例的另一种RLC PDU的包头的结构示意图。
在发送端，需要分段的时候，RLC实体在RLC PDU分段的子头中加上与MAC实体指示L域的F域相同的F域。同时，为RLC实体的SO域设置成与MAC实体的L域一样的长度。
如图24中所示，MAC子头中的F域为F＝0，F2＝1，在分段的时候，RLC的子头中的F域的值设置成与MAC实体的一样：F＝0，F2＝1。
在接收端，RLC实体通过检测RLC子头中的F域来得到SO域的长度。
如图25所示，为本发明另一实施例的另一种RLC PDU的包头的结构示意图。
在发送端，需要分段的时候，RLC实体根据RLC SDU分段的长度自行决定SO域的长度。具体方法如下：首先，在LCP之后，MAC实体将某一个逻辑信道得到的grant告诉给RLC实体；之后，RLC实体通过给最后一个RLC PDU的RLC SDU分段来匹配grant的大小；最后，RLC实体得到分段之后SO的值，通过SO的值来得到SO域的大小。图中第一个SO＝32，只需要6bit的SO长度来指示；第二个SO＝1024，因此只需要11比特的SO长度来指示。图中用两种不同的F域来指示第一个和第二个SO的长度，但是不仅限于这样的配置：可以是一个F域，来指示两种SO域的长度；也可以是多个F，来指示多种SO域的长度。
在接收端，RLC实体通过检测RLC子头中的F域来得到SO域的长度。
如图26所示，为本发明另一实施例的另一种配置令牌桶状态的过程示意图。
所述令牌桶的状态用于MAC层作出调度决策，确定那个逻辑信道传输多少数据量。在所述令牌桶的状态维护中通过参数Bj表示令牌桶中令牌数量，所述令牌数量表示一个逻辑信道的数据是否获得预配置的传输速率，例如，Bj为正数时表示当前逻辑信道的数据未获得预配置的传输速率，Bj为负数时表示当前逻辑信道的数据获得的传输速率超过预配置的传输速率。
由协议规定Bj的累积时间粒度，该时间粒度是所有可用Numerology/TTI长度的公约数，比如：60KHz子载波间隔所对应的符号长度。
基站为终端设备配置单位时间内的Bj累积数，终端设备以该时间粒度为单位，进行Bj累计
“Bj/单位时间”由基站配置，是为每一个终端设备配的，通过专用信令配置。其中“单位时间”是该终端设备的所有可用的TTI长度(图中终端设备可以使用两种 TTI长度：TTI1和TTI2)的公约数。
可选地，“单位时间”可以是该终端设备的所有可用的TTI长度的最大公约数。比如，图中终端设备可以使用两种TTI长度：TTI1和TTI2，单位时间可以是TTI1和TTI2的最大公约数。
可选地，“单位时间”可以是该小区内所有可用的TTI长度的公约数或最大公约数。比如下图中，该小区有三种TTI长度：TTI1、TTI2、TTI3。但是该终端设备只使用了两种TTI长度：TTI1、TTI2。此时，“单位时间”指的是TTI1、TTI2、TTI3的公约数或最大公约数。
可选地，“单位时间”可以由基站配置并发送给终端设备，例如基站通过RRC信令配置，“单位时间”可以配置给一个终端设备的一个或多个逻辑信道。可选地，每个逻辑信道配置独立的“单位时间”。
可选地，“单位时间”可以是协议规定的一个时间单位，该小区内所有可用的TTI长度都是这个“单位时间”的整数倍。具体地，该“单位时间”可以是该终端设备的所有可用的符号长度中最小的符号长度；或NR中所支持的最小的符号长度。
如图27所示，为本发明另一实施例的一种Bj状态变化的过程示意图。
假设Bj在每个单位时间增加20，终端设备在同一个TTI收到两份上行资源：上行授权A(UL grant A)和UL grant B，其中UL grant A所表示的上行资源和UL grant B所表示的上行资源不在同一时间。终端设备从不同的时间点开始，准备这两个TB：TB A和TB B。终端设备从哪个时间点开始准备某个具体的TB，就使用该时间点对应的Bj。
图中，每个时间单位的Bj累积值为20。终端设备准备传输块(TB)A时，假定Bj＝120,在生成TB A的过程中，Bj减去60；准备TB B时，假定Bj＝80,在生成TB B的过程中，Bj减去100，所以，生成TB B后，Bj变为0。
该LCH在TB A和TB B内都有数据传输，所以两个TB生成后，Bj都减。
如图28所示，为本发明另一实施例的一种Bj状态变化的过程示意图。
如果基站配置了该LCH只能映射到TTI1上，不能映射到TTI2上。则终端设备在准备TB B时，不考虑当前LCH。如果终端设备在准备TB B时，其它LCH的数据都放入以后，还有剩余空间，可以把当前LCH的数据放入；在其它条件下，也可以把当前LCH的数据放入，比如其它待传的LCH都是背景类业务，对时延不敏感。这种条件下，终端设备对该LCH维护的Bj并不减。
可选地，终端设备在生成TB B时，当前LCH放入了100Byte的数据，在Bj计算时，可以乘上一个系数，如Bj＝Bj–100*ɑ。这个ɑ系数可以由基站通过专用RRC信令配置给终端设备,是per LCH配置的，可选的，当ɑ等于0时，相当于上面所述的Bj不减的情况。每个LCH使用不同的系数。也可以是每一组逻辑信道-空口格式或TTI长度(LCH-numerology/TTI)配一个系数。
如图29所示，为本发明另一实施例的一种半静态调度(Semi Persistent Scheduling，SPS)资源与动态调度资源的共存的示意图。
如果终端设备存在某种业务，数据量恒定，且定期有数据包需要传输，如VOIP业务。基站会为终端设备分配半静态调度资源SPS。SPS资源分配可以是上行资源，也可以是下行资源。在数据传输过程中，终端设备可能同时进行多种业务，如果基站认为在SPS资源所在的时刻，终端设备需要专输更多数据，就会临时为终端设备分配动态调度的资源。LTE中，SPS资源总是位于Pcell上，不会位于其它Scell上。如果终端设备发现在同一子帧内，在Pcell上既有SPS上行资源，又有动态调度的上行资源，终端设备会忽略动态调度的上行资源。如下图所示，终端设备分别在两个上行子帧有SPS上行资源，而在SPS 1这份资源所在的同一个子帧，基站又为终端设备分配了一份动态调度资源，此时，终端设备放弃SPS 1，在这个子帧仅使用动态调度的资源传输数据。
在NR中，终端设备可能同时使用多种numerology/TTI长度的资源发送数据，不同的numerology/TTI长度对应不同的业务QoS。此时，如果SPS资源所对应的numerology/TTI长度对应于较高的QoS，而动态调度资源所对应的numerology/TTI长度对应于较低的QoS，而终端设备仍然放弃SPS资源而使用动态调度的资源，会无法满足QoS要求最高的业务的需求。所以，可以对终端设备的行为做如下改动：
终端设备自行决定采用SPS资源还是动态调度资源。一种优化的方法是：终端设备根据当前buffer中的数据的类型判断。如果当前buffer中QoS要求最高的业务数据，不能使用动态调度的资源传输，只能使用SPS资源传输，则终端设备确定使用SPS资源传输，不使用动态调度的资源。另一种优化的方法是：终端设备根据当前buffer中的数据里QoS要求最高的数据包剩余的时延，确定使用SPS资源或动态调度资源，举个例子，如果终端设备发现当前QoS要求最高的数据包，剩余的时延还有20ms，而下一次SPS资源(可以满足该QoS)是在15ms以后，此时，终端设备就决定使用动态调度资源，不使用SPS资源。
基站配置不同numerology/TTI长度的优先级，如果终端设备发现SPS资源与动态调度资源在时间上有交叠，则终端设备选择优先级更高的numerology/TTI长度的资源。如果两份资源的numerology/TTI长度的优先级相同，则终端设备选择动态调度的资源。
终端设备根据上行资源的TTI长度，在SPS资源或动态调度资源中，选择TTI长度更短的资源,放弃TTI长度更长的资源。如果两份资源的TTI长度相同，则终端设备选择动态调度的资源进行数据传输。
当SPS资源和动态调度资源的numerology/TTI长度不同的条件下，明确了终端设备行为，选择一份资源进行数据传输。
根据业务数据QoS，SPS资源和动态调度资源的numerology/TTI长度，或者资源的优先级，终端设备在SPS资源和动态调度资源中选择一份进行数据传输。
在实现过程中，上述方法的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。结合本申请实施例所公开的方法的步骤可以直接体现为硬件 处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。为避免重复，这里不再详细描述。本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
应理解，在本申请的各个实施例中，上述各过程的序号大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本发明的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，该单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
该作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
该功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本发明各个实施例该方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(ROM，Read-Only  Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。
以上仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本发明揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本发明的保护范围之内。因此，本申请的保护范围应以该权利要求的保护范围为准。

Claims (24)

  1. 一种状态报告的处理方法，其特征在于，包括：
    发送端生成MAC PDU，该MAC PDU包括一个或多个RLC PDU，其中一个或多个RLC PDU的包头中的状态报告发送请求置为激活；
    发送端将该MAC PDU发送给接收端，以便所述接收端解析出至少一个RLC PDU的包头中的状态报告发送请求置为激活时确定为所述MAC PDU发送状态报告。
  2. 如权利要求1所述的方法，其中，所述方法还包括：
    发送端的RLC层将其发送的所述一个或多个RLC PDU的包头中的状态报告发送请求置为激活，并将携带有所述状态报告发送请求的RLC PDU发送给所述发送端的MAC层。
  3. 如权利要求1所述的方法，其中，所述方法还包括：
    所述发送端的RLC层确定需要发送状态报告发送请求，通知所述发送端的MAC层对下一次需要发送的MAC PDU中的所述一个或多个RLC PDU的包头中的状态报告发送请求置为激活。
  4. 如权利要求1所述的方法，其中，所述方法还包括：
    所述发送端的RLC层确定需要发送状态报告发送请求，通知所述发送端的MAC层从下一次需要发送的MAC PDU中所述一个或多个RLC PDU选一个RLC PDU并将该选择的RLC PDU的序列号通知所述发送端的所述RLC层；
    所述发送端的所述RLC层将该序列号对应的RLC PDU的包头中的状态报告发送请求置为激活；
    所述发送端的所述RLC层将携带有所述状态报告发送请求的RLC PDU发送给所述发送端的MAC层。
  5. 如权利要求2或4所述的方法，其中，所述方法还包括：
    所述发送端的所述RLC层在将携带有所述状态报告发送请求的RLC PDU发送给所述发送端的所述MAC层时，将所述发送端的所述RLC层保存的已经发送RLC PDU数量的计数器和已经发送RLC PDU数据量的计数器置零，重启状态报告发送请求重传定时器。
  6. 如权利要求3所述的方法，其中，所述方法还包括：
    所述发送端的所述RLC层在获知所述发送端的所述MAC层将携带状态报告发送请求置为激活的RLC PDU发送时，所述发送端的所述RLC层将其保存的已经发送RLC PDU数量的计数器和已经发送RLC PDU数据量的计数器置零，重启状态报告发送请求重传定时器。
  7. 如权利要求6的方法，其中，所述方法还包括：
    所述发送端的所述MAC层在将携带状态报告发送请求置为激活的RLC PDU发送时，通知所述发送端的所述RLC层已经将携带状态报告发送请求置为激活的RLC PDU发送。
  8. 如权利要求3或4的方法，其中，所述方法还包括：
    所述发送端的所述MAC层确定所述MAC PDU内一个无线承载或一个逻辑信道对应的任意一个RLC PDU或所述MAC PDU内一个无线承载或一个逻辑信道对应的多个RLC PDU中最后一个RLC PDU或所述MAC PDU内一个无线承载或一个逻辑信道对应的多个RLC PDU中最后一个没有被分段的RLC PDU的状态报告发送请求置为激活。
  9. 如权利要求7的方法，其中，所述方法还包括：
    所述发送端的所述MAC层在将携带状态报告发送请求置为激活的RLC PDU发送时，通知所述发送端的所述RLC层一个RLC PDU的序列号SN，其中，该SN是状态报告发送请求置为激活的RLC PDU的SN，或者，该SN是一个状态报告发送请求置为激活的RLC PDU所属的MAC PDU内的最后一个RLC PDU的SN，或该SN是一个状态报告发送请求置为激活的RLC PDU所属的MAC PDU内的任意一个RLC PDU的SN。
  10. 一种状态报告的处理装置，其特征在于，包括：
    MAC实体，用于生成MAC PDU，该MAC PDU包括一个或多个RLC PDU，其中一个或多个RLC PDU的包头中的状态报告发送请求置为激活；
    所述MAC实体还用于将该MAC PDU发送给接收端，以便所述接收端解析出至少一个RLC PDU的包头中的状态报告发送请求置为激活时确定为所述MAC PDU发送状态报告。
  11. 如权利要求10所述的装置，其中，所述装置还包括：
    RLC实体，用于将其发送的所述一个或多个RLC PDU的包头中的状态报告发送请求置为激活，并将携带有所述状态报告发送请求的RLC PDU发送给所述MAC实体。
  12. 如权利要求10所述的装置，其中，所述装置还包括：
    RLC实体，用于确定需要发送状态报告发送请求，通知所述MAC实体对下一次需要发送的MAC PDU中的所述一个或多个RLC PDU的包头中的状态报告发送请求置为激活。
  13. 如权利要求10所述的装置，其中，所述装置还包括：
    RLC实体，用于确定需要发送状态报告发送请求，通知所述MAC实体从下一次需要发送的MAC PDU中所述一个或多个RLC PDU选一个RLC PDU并将该选择的RLC PDU的序列号通知所述RLC实体；
    其中，所述RLC实体，还用于将该序列号对应的RLC PDU的包头中的状态报告发送请求置为激活，将携带有所述状态报告发送请求的RLC PDU发送给所述MAC实体。
  14. 如权利要求11或13所述的装置，其中，所述RLC实体还用于在将携带有所 述状态报告发送请求的RLC PDU发送给所述MAC实体时，将所述RLC实体保存的已经发送RLC PDU数量的计数器和已经发送RLC PDU数据量的计数器置零，重启状态报告发送请求重传定时器。
  15. 如权利要求12所述的装置，其中，所述RLC实体还用于在获知所述MAC实体将携带状态报告发送请求置为激活的RLC PDU发送时，将所述RLC实体保存的已经发送RLC PDU数量的计数器和已经发送RLC PDU数据量的计数器置零，重启状态报告发送请求重传定时器。
  16. 如权利要求15的装置，其中，所述MAC实体还用于在将携带状态报告发送请求置为激活的RLC PDU发送时，通知所述RLC实体已经将携带状态报告发送请求置为激活的RLC PDU发送。
  17. 如权利要求12或13的装置，其中，所述MAC实体还用于确定所述MAC PDU内一个无线承载或一个逻辑信道对应的任意一个RLC PDU或所述MAC PDU内一个无线承载或一个逻辑信道对应的多个RLC PDU中最后一个RLC PDU或所述MAC PDU内一个无线承载或一个逻辑信道对应的多个RLC PDU中最后一个没有被分段的RLC PDU的状态报告发送请求置为激活。
  18. 如权利要求16的装置，其中，所述MAC实体还用于在将携带状态报告发送请求置为激活的RLC PDU发送时，通知所述RLC实体一个RLC PDU的序列号SN，其中，该SN是状态报告发送请求置为激活的RLC PDU的SN，或者，该SN是一个状态报告发送请求置为激活的RLC PDU所属的MAC PDU内的最后一个RLC PDU的SN，或该SN是一个状态报告发送请求置为激活的RLC PDU所属的MAC PDU内的任意一个RLC PDU的SN。
  19. 一种状态报告的处理方法，其特征在于，包括：
    接收端接收发送端发送的一个MAC PDU，该MAC PDU包括一个或多个RLC PDU，其中一个或多个RLC PDU的包头中的状态报告发送请求置为激活；
    当所述接收端确定该MAC PDU中至少一个RLC PDU的状态报告发送请求置为激活时，根据该状态报告发送请求置为激活状态生成状态报告；
    所述接收端向所述发送端发送状态报告。
  20. 如权利要求19所述的方法，其中，所述根据该状态报告发送请求置为激活状态生成状态报告具体包括：
    根据该状态报告发送请求置为激活状态确定该MAC PDU中的最后一个RLC PDU的状态报告发送请求的状态为激活，根据最后一个RLC PDU的序列号(SN)生成状态报告。
  21. 如权利要求19或20所述的方法，其中，所述MAC PDU内一个无线承载或一个逻辑信道对应的任意一个RLC PDU或所述MAC PDU内一个无线承载或一个逻辑信道对应的多个RLC PDU中最后一个RLC PDU或所述MAC PDU内一个无线承载或一个逻辑信道对应的多个RLC PDU中最后一个没有被分段的RLC PDU的状态报告发送 请求置为激活。
  22. 一种状态报告的处理装置，其特征在于，包括：
    接收器，用于接收发送端发送的一个MAC PDU，该MAC PDU包括一个或多个RLC PDU，其中一个或多个RLC PDU的包头中的状态报告发送请求置为激活；
    处理器，用于当确定该MAC PDU中至少一个RLC PDU的状态报告发送请求置为激活时，根据该状态报告发送请求置为激活状态生成状态报告；
    发送器，向所述发送端发送状态报告。
  23. 如权利要求22所述的装置，其中，所述处理器用于根据该状态报告发送请求置为激活状态生成状态报告具体包括：
    所述处理器，用于根据该状态报告发送请求置为激活状态确定该MAC PDU中的最后一个RLC PDU的状态报告发送请求的状态为激活，根据最后一个RLC PDU的序列号(SN)生成状态报告。
  24. 如权利要求22或23所述的装置，其中，所述MAC PDU内一个无线承载或一个逻辑信道对应的任意一个RLC PDU或所述MAC PDU内一个无线承载或一个逻辑信道对应的多个RLC PDU中最后一个RLC PDU或所述MAC PDU内一个无线承载或一个逻辑信道对应的多个RLC PDU中最后一个没有被分段的RLC PDU的状态报告发送请求置为激活。
PCT/CN2018/085742 2017-05-05 2018-05-05 一种数据传输的处理方法和装置 WO2018202186A1 (zh)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN201710314223.9 2017-05-05
CN201710314223 2017-05-05
CN201710687319.XA CN108809510B (zh) 2017-05-05 2017-08-11 一种数据传输的处理方法和装置
CN201710687319.X 2017-08-11

Publications (1)

Publication Number Publication Date
WO2018202186A1 true WO2018202186A1 (zh) 2018-11-08

Family

ID=64015906

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/085742 WO2018202186A1 (zh) 2017-05-05 2018-05-05 一种数据传输的处理方法和装置

Country Status (1)

Country Link
WO (1) WO2018202186A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3914022A4 (en) * 2019-02-01 2022-04-13 Huawei Technologies Co., Ltd. METHOD AND APPARATUS FOR SENDING RADIO RESOURCE CONTROL (RRC) MESSAGE

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1852084A (zh) * 2005-10-10 2006-10-25 华为技术有限公司 一种数据包丢失的检测方法和检测装置
EP2073425A2 (en) * 2007-12-17 2009-06-24 Electronics And Telecommunications Research Institute Apparatus and method for optimizing status report time in mobile communication system
CN102740353A (zh) * 2011-04-02 2012-10-17 中兴通讯股份有限公司 上行状态报告上报方法、无线链路控制数据发送方法及装置
CN103338095A (zh) * 2008-01-08 2013-10-02 无线星球有限责任公司 无线通信网络中的方法和装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1852084A (zh) * 2005-10-10 2006-10-25 华为技术有限公司 一种数据包丢失的检测方法和检测装置
EP2073425A2 (en) * 2007-12-17 2009-06-24 Electronics And Telecommunications Research Institute Apparatus and method for optimizing status report time in mobile communication system
CN103338095A (zh) * 2008-01-08 2013-10-02 无线星球有限责任公司 无线通信网络中的方法和装置
CN102740353A (zh) * 2011-04-02 2012-10-17 中兴通讯股份有限公司 上行状态报告上报方法、无线链路控制数据发送方法及装置

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3914022A4 (en) * 2019-02-01 2022-04-13 Huawei Technologies Co., Ltd. METHOD AND APPARATUS FOR SENDING RADIO RESOURCE CONTROL (RRC) MESSAGE
US11997740B2 (en) 2019-02-01 2024-05-28 Huawei Technologies Co., Ltd. Radio resource control (RRC) message sending method and apparatus

Similar Documents

Publication Publication Date Title
WO2019192596A1 (zh) 传输数据的方法及其装置和系统
WO2019057154A1 (zh) 数据传输方法、终端设备和网络设备
JP2017201843A (ja) 論理チャネルを優先順位付けするための方法および装置
WO2018202037A1 (zh) 传输数据的方法、终端设备和网络设备
EP3737183B1 (en) Communication methods, apparatuses and computer-readable storage medium
US10869213B2 (en) Transmission status reporting apparatus and method and communication system
CN108337633B (zh) 数据分流配置方法、基站系统和用户终端
JP2011511566A (ja) トークンバケットの初期化、保持、および再構成のための方法および装置
US20190230682A1 (en) Data transmission method, apparatus, and system
WO2018059438A1 (zh) 消息传输方法、设备和系统
EP3737145A1 (en) Communication method, device and system
WO2023000827A1 (zh) 数据丢弃方法、装置、终端及存储介质
WO2020151700A1 (zh) 副链路缓存状态报告发送、接收方法和设备
WO2021218888A1 (zh) 通信方法和装置
CN110430599A (zh) 数据传输的方法和装置
TWI663858B (zh) L2層資料封包處理方法和使用該方法的電子裝置
WO2021022687A1 (zh) 通信方法、建立slrb的方法和通信装置
WO2020125573A1 (zh) 通信方法、装置、终端、网络设备及存储介质
WO2018228558A1 (zh) 一种传输数据的方法、网络设备和终端设备
WO2021081875A1 (zh) Rrc连接状态控制方法、装置及存储介质
WO2019029686A1 (zh) 数据传输方法、设备和通信系统
US20220015107A1 (en) Communications Method and Apparatus
CN108809510B (zh) 一种数据传输的处理方法和装置
CN111148225B (zh) 资源调度方法、装置及设备
WO2018171710A1 (zh) 信息的处理方法和设备

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18794484

Country of ref document: EP

Kind code of ref document: A1