WO2023115477A1 - Procédés et appareils de prise en charge d'une opération de rejet de paquet dans une couche rlc en raison d'une perte de paquet - Google Patents

Procédés et appareils de prise en charge d'une opération de rejet de paquet dans une couche rlc en raison d'une perte de paquet Download PDF

Info

Publication number
WO2023115477A1
WO2023115477A1 PCT/CN2021/140954 CN2021140954W WO2023115477A1 WO 2023115477 A1 WO2023115477 A1 WO 2023115477A1 CN 2021140954 W CN2021140954 W CN 2021140954W WO 2023115477 A1 WO2023115477 A1 WO 2023115477A1
Authority
WO
WIPO (PCT)
Prior art keywords
packet
value
rlc
entity
response
Prior art date
Application number
PCT/CN2021/140954
Other languages
English (en)
Inventor
Congchi ZHANG
Mingzeng Dai
Lianhai WU
Jing HAN
Original Assignee
Lenovo (Beijing) Limited
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Lenovo (Beijing) Limited filed Critical Lenovo (Beijing) Limited
Priority to PCT/CN2021/140954 priority Critical patent/WO2023115477A1/fr
Publication of WO2023115477A1 publication Critical patent/WO2023115477A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/32—Flow control; Congestion control by discarding or delaying data units, e.g. packets or frames
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1835—Buffer management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1848—Time-out mechanisms
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/187—Details of sliding window management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/1874—Buffer management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/1896—ARQ related signaling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/34—Flow control; Congestion control ensuring sequence integrity, e.g. using sequence numbers

Definitions

  • Embodiments of the present application generally relate to wireless communication technology, in particular to methods and apparatuses for supporting a packet discarding operation in radio link control (RLC) layer due to a packet loss.
  • RLC radio link control
  • Extended reality including augmented reality (AR) and virtual reality (VR) , as well as cloud gaming (CG)
  • AR augmented reality
  • VR virtual reality
  • CG cloud gaming
  • XR services require high bit rate with bounded latency.
  • the applications require a certain minimum granularity of application data to be available on the client side before the next level of processing can start. This minimum granularity of application data is referred to an application data unit (ADU) .
  • ADU application data unit
  • the high bit rates may lead to that a large ADU will be transmitted in several IP packets. When these IP packets arrive to RAN, RAN will treat all the packets as if they are uncorrelated from each other.
  • the ADU represents a group of pictures (GOP) for video service. Groups of pictures (GOPs) are grouped together in ways that enhance the visual result of a video sequence.
  • GOPs may include various types of pictures, such as, intra-coded pictures (I-frame) , predictive coded pictures (P-frame) , or B-predictive coded pictures (B-frame) .
  • Encoders use groups of pictures and other tools to render smoothly streaming video. Frame rates and other metrics may also apply.
  • frames in the same ADU or GOP may be correlated to each other. For instance, if the I-frame is lost, the user will not be able to decode the subsequent P-frames and B-frames. In the meanwhile, due to the nature of wireless communication, a packet loss may happen in the UL or DL transmission.
  • an important packet e.g., I-frame in one ADU or GOP
  • RLC entity e.g., P-frame, B-frame in the same ADU or GOP
  • the RLC receiving entity includes a processor and a transceiver coupled to the processor; and the processor is configured: to detect a packet loss or to receive, via the transceiver from an RLC transmitting entity, parameter information regarding a discarding operation of the RLC receiving entity, wherein the packet loss or the discarding operation is associated with a packet; and to perform the discarding operation to discard a further packet related to the packet in a receiving buffer, in response to detecting the packet loss or in response to receiving the parameter information.
  • RLC radio link control
  • Some embodiments of the present application provide a method, which may be performed by an RLC receiving entity.
  • the method includes: detecting a packet loss or receiving, from an RLC transmitting entity, parameter information regarding a discarding operation of the RLC receiving entity, wherein the packet loss or the discarding operation is associated with a packet; and determining to perform the discarding operation to discard a further packet related to the packet in a receiving buffer, in response to detecting the packet loss or in response to receiving the parameter information.
  • Some embodiments of the present application also provide an apparatus for wireless communications.
  • the apparatus includes: a non-transitory computer-readable medium having stored thereon computer-executable instructions; a receiving circuitry; a transmitting circuitry; and a processor coupled to the non-transitory computer-readable medium, the receiving circuitry and the transmitting circuitry, wherein the computer-executable instructions cause the processor to implement any of the above-mentioned method performed by an RLC receiving entity.
  • the RLC transmitting entity includes a processor and a transceiver coupled to the processor; and the processor is configured: to detect a packet loss or to receive, via the transceiver from an RLC receiving entity, parameter information regarding a discarding operation of the RLC transmitting entity, wherein the packet loss or the discarding operation is associated with a packet; and to stop transmitting a further packet related to the packet in a transmitting buffer and to perform the discarding operation to discard the further packet, in response to detecting the packet loss or in response to receiving the parameter information.
  • Some embodiments of the present application provide a method, which may be performed by an RLC transmitting entity.
  • the method includes: detecting a packet loss or receiving, from an RLC receiving entity, parameter information regarding a discarding operation of the RLC transmitting entity, wherein the packet loss or the discarding operation is associated with a packet; and stopping transmitting a further packet related to the packet in a transmitting buffer and performing the discarding operation to discard the further packet, in response to detecting the packet loss or in response to receiving the parameter information.
  • the apparatus includes: a non-transitory computer-readable medium having stored thereon computer-executable instructions, a receiving circuitry; a transmitting circuitry; and a processor coupled to the non-transitory computer-readable medium, the receiving circuitry and the transmitting circuitry, wherein the computer-executable instructions cause the processor to implement the abovementioned method performed by an RLC transmitting entity.
  • FIG. 1 illustrates a schematic diagram of a wireless communication system according to some embodiments of the present application.
  • FIG. 2 illustrates an exemplary block diagram of an apparatus according to some embodiments of the present application.
  • FIG. 3 illustrates an exemplary flow chart for a packet discarding operation according to some embodiments of the present application.
  • FIG. 4 illustrates a further exemplary flow chart for a packet discarding operation according to some embodiments of the present application.
  • FIG. 5 illustrates an exemplary flow chart of a packet discarding operation in an RLC UM or AM receiving entity according to some embodiments of the present application.
  • FIG. 6 illustrates an exemplary flow chart of a packet discarding operation in an RLC AM transmitting entity according to some embodiments of the present application.
  • FIG. 1 illustrates a schematic diagram of a wireless communication system according to some embodiments of the present application.
  • the wireless communication system 100 includes at least one base station (BS) 101 and at least one user equipment (UE) 102.
  • the wireless communication system 100 includes one BS 101 and two UE 102 (e.g., UE 102a and UE 102b) for illustrative purpose.
  • UE 102a and UE 102b e.g., UE 102a and UE 102b
  • the wireless communication system 100 may include more or less BSs and UEs in some other embodiments of the present application.
  • the wireless communication system 100 is compatible with any type of network that is capable of sending and receiving wireless communication signals.
  • the wireless communication system 100 is compatible with a wireless communication network, a cellular telephone network, a time division multiple access (TDMA) -based network, a code division multiple access (CDMA) -based network, an orthogonal frequency division multiple access (OFDMA) -based network, an LTE network, a 3GPP-based network, a 3GPP 5G network, a satellite communications network, a high altitude platform network, and/or other communications networks.
  • TDMA time division multiple access
  • CDMA code division multiple access
  • OFDMA orthogonal frequency division multiple access
  • BS 101 may communicate with a core network (CN) node (not shown) , e.g., a mobility management entity (MME) or a serving gateway (S-GW) , a mobility management function (AMF) or a user plane function (UPF) etc. via an interface.
  • a BS also be referred to as an access point, an access terminal, a base, a macro cell, a node-B, an enhanced node B (eNB) , a gNB, a home node-B, a relay node, or a device, or described using other terminology used in the art.
  • a BS may also refer to as a RAN node or network apparatus.
  • Each BS may serve a number of UE (s) within a serving area, for example, a cell or a cell sector via a wireless communication link.
  • Neighbor BSs may communicate with each other as necessary, e.g., during a handover procedure for a UE.
  • UE 102 e.g., UE 102a and UE 102b
  • any type terminal device which may include computing devices, such as desktop computers, laptop computers, personal digital assistants (PDAs) , tablet computers, smart televisions (e.g., televisions connected to the Internet) , set-top boxes, game consoles, security systems (including security cameras) , vehicle on-board computers, network devices (e.g., routers, switches, and modems) , or the like.
  • computing devices such as desktop computers, laptop computers, personal digital assistants (PDAs) , tablet computers, smart televisions (e.g., televisions connected to the Internet) , set-top boxes, game consoles, security systems (including security cameras) , vehicle on-board computers, network devices (e.g., routers, switches, and modems) , or the like.
  • PDAs personal digital assistants
  • smart televisions e.g., televisions connected to the Internet
  • set-top boxes e.g., game consoles
  • UE 102 may include a portable wireless communication device, a smart phone, a cellular telephone, a flip phone, a device having a subscriber identity module, a personal computer, a selective call receiver, or any other device that is capable of sending and receiving communication signals on a wireless network.
  • UE 102 may include wearable devices, such as smart watches, fitness bands, optical head-mounted displays, or the like.
  • UE 102 may be referred to as a subscriber unit, a mobile, a mobile station, a user, a terminal, a mobile terminal, a wireless terminal, a fixed terminal, a subscriber station, a user terminal, or a device, or described using other terminology used in the art.
  • UE 102 may communicate directly with BSs 101 via uplink (UL) communication signals.
  • UL uplink
  • data transfer procedures include an unacknowledged mode (UM) data transfer procedure and an acknowledged mode (AM) data transfer procedure.
  • UM unacknowledged mode
  • AM acknowledged mode
  • a transmitting side of an UM RLC entity when submitting an unacknowledged mode data (UMD) packet data unit (PDU) to lower layer, a transmitting side of an UM RLC entity shall: set the SN of the UMD PDU to TX_Next, if the UMD PDU contains a segment of an RLC service data unit (SDU) ; and increment TX_Next by one, if the UMD PDU contains a segment that maps to the last byte of an RLC SDU.
  • UMD unacknowledged mode data
  • SDU RLC service data unit
  • a transmitting side of an UM RLC entity may also be named as “an RLC UM Tx entity” , “an UM RLC Tx entity” , “an RLC UM transmitting entity” , “an UM RLC transmitting entity” , “a transmitting RLC UM entity” , “a transmitting UM RLC entity” , or the like.
  • a receiving side of an UM RLC entity In an UM data transfer procedure, during reception operations, a receiving side of an UM RLC entity shall maintain a reassembly window according to state variable RX_Next_Highest.
  • the receiving side of an UM RLC entity When receiving an UMD PDU from a lower layer, the receiving side of an UM RLC entity shall: either deliver the UMD PDU to upper layer after removing the RLC header, discard the received UMD PDU, or place it in the reception buffer; and update state variables, reassemble and deliver RLC SDUs to upper layer and start or stop timer t-Reassembly as needed, if the received UMD PDU was placed in the reception buffer.
  • timer t-Reassembly expires, the receiving side of an UM RLC entity shall: update state variables, discard RLC SDU segments and start timer t-Reassembly as needed.
  • a receiving side of an UM RLC entity may also be named as “an RLC UM Rx entity” , “an UM RLC Rx entity” , “an RLC UM receiving entity” , “an UM RLC receiving entity” , “a receiving RLC UM entity” , “a receiving UM RLC entity” , or the like.
  • a transmitting side of an AM RLC entity shall prioritize transmission of RLC control PDUs over acknowledged mode data (AMD) PDUs.
  • the transmitting side of an AM RLC entity shall prioritize transmission of AMD PDUs containing previously transmitted RLC SDUs or RLC SDU segments over transmission of AMD PDUs containing not previously transmitted RLC SDUs or RLC SDU segments.
  • the transmitting side of an AM RLC entity shall maintain a transmitting window according to the state variable TX_Next_Ack.
  • the transmitting side of an AM RLC entity shall not submit to lower layer any AMD PDU whose SN falls outside of the transmitting window.
  • the AM RLC entity For each RLC SDU received from the upper layer, the AM RLC entity shall: associate a SN with the RLC SDU equal to TX_Next and construct an AMD PDU by setting the SN of the AMD PDU to TX_Next; and increment TX_Next by one.
  • the transmitting side of an AM RLC entity When submitting an AMD PDU that contains a segment of an RLC SDU, to a lower layer, the transmitting side of an AM RLC entity shall: set the SN of the AMD PDU to the SN of the corresponding RLC SDU.
  • the transmitting side of an AM RLC entity can receive a positive acknowledgement (confirmation of successful reception by its peer AM RLC entity) for an RLC SDU by the following: STATUS PDU from its peer AM RLC entity.
  • a transmitting side of an AM RLC entity may also be named as “an RLC AM Tx entity” , “an AM RLC Tx entity” , “an RLC AM transmitting entity” , “an AM RLC transmitting entity” , “a transmitting RLC AM entity” , “a transmitting AM RLC entity” , or the like.
  • a receiving side of an AM RLC entity In an AM data transfer procedure, during reception operations, a receiving side of an AM RLC entity shall maintain a receiving window according to the state variable RX_Next.
  • the receiving side of an AM RLC entity When receiving an AMD PDU from a lower layer, the receiving side of an AM RLC entity shall: either discard the received AMD PDU or place it in the reception buffer; and update state variables, reassemble and deliver RLC SDUs to upper layer and start or stop timer t-Reassembly as needed, if the received AMD PDU was placed in the reception buffer.
  • timer t-Reassembly expires, the receiving side of an AM RLC entity shall update state variables and start timer t-Reassembly as needed.
  • a receiving side of an AM RLC entity may also be named as “an RLC AM Rx entity” , “an AM RLC Rx entity” , “an RLC AM receiving entity” , “an AM RLC receiving entity” , “a receiving RLC AM entity” , “a receiving AM RLC entity” , or the like.
  • an RLC AM receiving entity or an RLC UM receiving entity may detect a packet loss and decide to discard some other packets which have already been received in the receiving buffer of the RLC AM receiving entity or the RLC UM receiving entity.
  • an RLC AM transmitting entity or an RLC UM transmitting entity may be informed by a peer RLC AM or UM receiving entity about the packet discarding decision and stop the relevant packet transmission.
  • the RLC AM transmitting entity may detect a packet loss according to the received RLC status report and decide to stop transmitting and discard some packets without causing an RLC failure.
  • a GOP may be deemed as one kind of an ADU, and packets belonging to the same ADU are correlated to each other.
  • parameters related to an ADU e.g., an index value of an ADU, “ADUIndexToDiscard” , and etc.
  • an index value of an ADU may be changed or modified to an index value of a GOP.
  • “ADUIndexToDiscard” may be changed or modified to “GOPIndexToDiscard” .
  • “NumberInUnitToDiscard” associated with an ADU may be changed or modified to “NumberInUnitToDiscard” associated with a GOP.
  • “ImportanceToDiscard” associated with an ADU may be changed or modified to “ImportanceToDiscard” associated with a GOP. The embodiments with any of such kind of parameter modifications may also solve the above-mentioned issue.
  • FIG. 2 illustrates an exemplary block diagram of an apparatus according to some embodiments of the present application.
  • the apparatus 200 may include at least one processor 204 and at least one transceiver 202 coupled to the processor 204.
  • the at least one transceiver 202 may be a wired transceiver or a wireless transceiver.
  • the apparatus 200 may be an RLC receiving entity or an RLC transmitting entity.
  • the transceiver 202 may be divided into two devices, such as a receiving circuitry and a transmitting circuitry.
  • the apparatus 200 may further include an input device, a memory, and/or other components.
  • the apparatus 200 may be an RLC receiving entity (e.g., RLC UM/AM Rx entity 510 or RLC AM Rx entity 610 as shown and illustrated in FIG. 5 or FIG. 6) .
  • the processor 204 of the RLC receiving entity may be configured: to detect a packet loss or to receive, via the transceiver 202 from an RLC transmitting entity (e.g., RLC UM/AM Tx entity 520 or RLC AM Tx entity 620 as shown and illustrated in FIG. 5 or FIG.
  • parameter information regarding a discarding operation of the RLC receiving entity wherein the packet loss or the discarding operation is associated with a packet; and to perform the discarding operation to discard a further packet related to the packet in a receiving buffer, in response to detecting the packet loss or in response to receiving the parameter information.
  • the processor 204 of the RLC receiving entity may be configured to detect the packet loss.
  • the processor 204 of the RLC receiving entity may be configured to receive the parameter information regarding the discarding operation of the RLC receiving entity. Specific examples are described in embodiments of FIGS. 5 and 6 as follows.
  • the packet may be named as “the 1st packet” , and the further packet is named as “the 2nd packet” , for simplicity.
  • the 1st packet or the 2nd packet may be at least one of:
  • the 1st packet and the 2nd packet belong to one application data unit (ADU) .
  • ADU application data unit
  • the 1st packet and the 2nd packet have the same ADU index value.
  • the 1st packet and the 2nd packet belong to one group of picture (GOP) .
  • the 1st packet and the 2nd packet have the same GOP index value.
  • the parameter information may be carried via at least one of: physical uplink control channel (PUCCH) signalling, a medium access control (MAC) control element (CE) , or an RLC control PDU.
  • the parameter information received by the RLC receiving entity may include at least one of:
  • the 1st index value may be “ADUIndexToDiscard” in embodiments in FIGS. 5 and 6.
  • an index number (which is marked as “the 1st index number” for simplicity) of the 1st packet in a group of packets belonging to the 1st ADU.
  • the 1st index number may be “NumberInUnitToDiscard” in embodiments in FIGS. 5 and 6.
  • An importance level (which is marked as “the 1st importance level” for simplicity) of the 1st packet.
  • the 1st importance level may be “ImportanceToDiscard” in embodiments in FIGS. 5 and 6.
  • the 1st importance level is configured by a network node.
  • a sequence number (SN) value (which is marked as “the 1st SN value” for simplicity) of the 1st packet.
  • the 1st SN value may be “SNToDiscard” in embodiments in FIGS. 5 and 6.
  • An offset value (which is marked as “the 1st offset value” for simplicity) related to the 1st SN value of the 1st packet.
  • the 1st offset value may be “Offset” in embodiments in FIGS. 5 and 6.
  • the processor 204 of the RLC receiving entity may be configured to check whether “an index value (which is marked as “the 2nd index value” for simplicity) of an ADU (which is marked as “the 2nd ADU” for simplicity) to which the 2nd packet belongs” is equal to “the 1st index value of the 1st ADU” (e.g., ADUIndexToDiscard) .
  • the processor 204 of the RLC receiving entity may be configured to discard the 2nd packet in the receiving buffer.
  • the processor 204 of the RLC receiving entity may be configured:
  • the processor 204 of the RLC receiving entity may be configured:
  • the 2nd index value of the 2nd ADU to which the 2nd packet belongs is equal to “the 1st index value of the 1st ADU” (e.g., ADUIndexToDiscard) ;
  • the processor 204 of the RLC receiving entity may be configured:
  • the processor 204 of the RLC receiving entity in response to receiving the parameter information from the RLC transmitting entity and in response to the parameter information including the 1st SN value of the 1st packet (e.g., SNToDiscard) , during performing the discarding operation of the RLC receiving entity, the processor 204 of the RLC receiving entity may be configured:
  • the processor 204 of the RLC receiving entity may be configured:
  • the processor 204 of the RLC receiving entity may be configured:
  • the processor 204 of the RLC receiving entity in response to detecting the packet loss associated with the 1st packet, during performing the discarding operation of the RLC receiving entity, the processor 204 of the RLC receiving entity may be configured:
  • the processor 204 of the RLC receiving entity in response to detecting the packet loss associated with the 1st packet, during performing the discarding operation of the RLC receiving entity, the processor 204 of the RLC receiving entity may be configured:
  • the processor 204 of the RLC receiving entity may be configured: to generate further parameter information regarding a discarding operation of the RLC transmitting entity; and to transmit the further parameter information via the transceiver 202 to the RLC transmitting entity.
  • the further discarding operation is associated with the 1st packet.
  • the further parameter information may be carried via at least one of PUCCH signalling, a MAC CE, or an RLC control PDU.
  • the further parameter information may include at least one of:
  • the processor 204 of the RLC receiving entity may be configured to perform at least one of:
  • the processor 204 of the RLC receiving entity may be configured to receive, via the transceiver 202 from a network node, configuration information regarding whether the discarding operation of the RLC receiving entity is supported for a radio bearer.
  • the processor 204 of the RLC receiving entity may be configured to receive, via the transceiver 202 from a network node, configuration information regarding a reception failure number threshold for the RLC receiving entity (e.g., NumberOfReceptionFailure in embodiments in FIGS. 5 and 6) .
  • the discarding operation of the RLC receiving entity may be performed upon meeting the reception failure number threshold for the RLC receiving entity.
  • the processor 204 of the RLC receiving entity may be configured:
  • the processor 204 of the RLC receiving entity may be configured:
  • the processor 204 of the RLC receiving entity may be configured to:
  • the processor 204 of the RLC receiving entity may be configured to:
  • the processor 204 of the RLC receiving entity may be configured:
  • the apparatus 200 may be an RLC transmitting entity (e.g., RLC UM/AM Tx entity 520 or RLC AM Tx entity 620 as shown and illustrated in FIG. 5 or FIG. 6) .
  • the processor 204 of the RLC transmitting entity may be configured: to detect a packet loss or to receive, via the transceiver 202 from an RLC receiving entity (e.g., RLC UM/AM Rx entity 510 or RLC AM Rx entity 610 as shown and illustrated in FIG. 5 or FIG.
  • parameter information regarding a discarding operation of the RLC transmitting entity wherein the packet loss or the discarding operation is associated with a packet; and to stop transmitting a further packet related to the packet in a transmitting buffer and to perform the discarding operation to discard the further packet, in response to detecting the packet loss or in response to receiving the parameter information.
  • the parameter information may be carried via at least one of PUCCH signalling, a MAC CE, or an RLC control PDU.
  • the processor 204 of the RLC transmitting entity may be configured to detect the packet loss.
  • the processor 204 of the RLC transmitting entity may be configured to receive the parameter information regarding the discarding operation of the RLC transmitting entity. Specific examples are described in embodiments of FIGS. 5 and 6 as follows.
  • each of the 1st packet and the 2nd packet is at least one of: (1) an RLC UMD PDU; (2) an RLC AMD PDU; (3) an RLC UMD SDU; (4) an RLC AMD SDU; (5) an RLC UMD segment; or (6) an RLC AMD segment.
  • the 1st packet and the 2nd packet belong to one ADU or one GOP.
  • the 1st packet and the 2nd packet have the same ADU index value or the same GOP index value.
  • the processor 204 of the RLC transmitting entity may be configured to receive, via the transceiver 202 from the network node, at least one of:
  • the discarding operation of the RLC transmitting entity is performed after the RLC transmitting entity performing a certain number of an RLC retransmission attempt operation for the 1st packet. In an embodiment, the discarding operation of the RLC transmitting entity is performed in response to the certain number of an RLC retransmission attempt operation for the 1st packet exceeding a maximum RLC retransmission number of the RLC transmitting entity.
  • the processor 204 of the RLC transmitting entity in response to detecting the packet loss associated with the 1st packet, during performing the discarding operation of the RLC transmitting entity, the processor 204 of the RLC transmitting entity may be configured:
  • the processor 204 of the RLC transmitting entity in response to detecting the packet loss associated with the 1st packet, during performing the discarding operation of the RLC transmitting entity, the processor 204 of the RLC transmitting entity may be configured:
  • the processor 204 of the RLC transmitting entity in response to detecting the packet loss associated with the 1st packet, during performing the discarding operation of the RLC transmitting entity, the processor 204 of the RLC transmitting entity may be configured:
  • the processor 204 of the RLC transmitting entity in response to detecting the packet loss associated with the 1st packet, during performing the discarding operation of the RLC transmitting entity, the processor 204 of the RLC transmitting entity may be configured:
  • the processor 204 of the RLC transmitting entity may be configured to transmit, via the transceiver 202 to an RLC receiving entity, further parameter information regarding a discarding operation of the RLC receiving entity.
  • the discarding operation of the RLC receiving entity is associated with the 1st packet.
  • the further parameter information may be carried via at least one of PUCCH signalling, a MAC CE, or an RLC control PDU.
  • the further parameter information may include at least one of:
  • an acknowledgement state variable e.g., TX_Next_Ack in embodiments in FIG. 6
  • the parameter information received by the RLC transmitting entity includes at least one of:
  • An importance level (which is marked as “the 1st importance level” for simplicity) of the 1st packet, e.g., “ImportanceToDiscard” in embodiments in FIGS. 5 and 6.
  • the importance level is configured by a network node.
  • a SN value (which is marked as “the 1st SN value” for simplicity) of the 1st packet, e.g., “SNToDiscard” in embodiments in FIGS. 5 and 6.
  • An offset value (which is marked as “the 1st offset value” for simplicity) related to the 1st SN value of the 1st packet, e.g., “Offset” in embodiments in FIGS. 5 and 6.
  • the processor 204 of the RLC transmitting entity in response to receiving the parameter information from the RLC receiving entity and in response to the parameter information including the 1st index value of the 1st ADU (e.g., ADUIndexToDiscard) , during performing the discarding operation of the RLC transmitting entity, the processor 204 of the RLC transmitting entity is configured:
  • the processor 204 of the RLC transmitting entity in response to receiving the parameter information from the RLC receiving entity and in response to the parameter information including the 1st index value of the 1st ADU (e.g., ADUIndexToDiscard) and the 1st index number of the 1st packet (e.g., NumberInUnitToDiscard) , during performing the discarding operation of the RLC transmitting entity, the processor 204 of the RLC transmitting entity is configured:
  • the 2nd index value of the 2nd ADU to which the 2nd packet belongs is equal to “the 1st index value of the 1st ADU” (e.g., ADUIndexToDiscard) ;
  • the processor 204 of the RLC transmitting entity in response to receiving the parameter information from the RLC receiving entity and in response to the parameter information including the 1st index value of the 1st ADU (e.g., ADUIndexToDiscard) and the 1st importance level of the 1st packet (e.g., ImportanceToDiscard) , during performing the discarding operation of the RLC transmitting entity, the processor 204 of the RLC transmitting entity is configured:
  • the 2nd index value of the 2nd ADU to which the 2nd packet belongs is equal to “the 1st index value of the 1st ADU” (e.g., ADUIndexToDiscard) ;
  • the processor 204 of the RLC transmitting entity in response to receiving the parameter information from the RLC receiving entity and in response to the parameter information including the 1st SN value of the 1st packet (e.g., SNToDiscard) and the 1st offset value related to the 1st SN value (e.g., Offset) , during performing the discarding operation of the RLC transmitting entity, the processor 204 of the RLC transmitting entity is configured:
  • the processor 204 of the RLC transmitting entity in response to receiving the parameter information from the RLC receiving entity and in response to the parameter information including the 1st SN value of the 1st packet (e.g., SNToDiscard) , during performing the discarding operation of the RLC transmitting entity, the processor 204 of the RLC transmitting entity is configured:
  • the apparatus 200 may include at least one non-transitory computer-readable medium.
  • the non-transitory computer-readable medium may have stored thereon computer-executable instructions to cause a processor to implement the method with respect to an RLC receiving entity or an RLC transmitting entity as described above.
  • the computer-executable instructions when executed, cause the processor 204 interacting with the transceiver 202, so as to perform operations of the methods, e.g., as described in view of FIGS. 3-6.
  • FIG. 3 illustrates an exemplary flow chart for a packet discarding operation according to some embodiments of the present application.
  • the method 300 may be performed by an RLC receiving entity (e.g., RLC UM/AM Rx entity 510 or RLC AM Rx entity 610 as shown and illustrated in FIG. 5 or FIG. 6) .
  • RLC receiving entity e.g., RLC UM/AM Rx entity 510 or RLC AM Rx entity 610 as shown and illustrated in FIG. 5 or FIG. 6
  • RLC receiving entity e.g., RLC UM/AM Rx entity 510 or RLC AM Rx entity 610 as shown and illustrated in FIG. 5 or FIG. 6
  • RLC receiving entity e.g., RLC UM/AM Rx entity 510 or RLC AM Rx entity 610 as shown and illustrated in FIG. 5 or FIG. 6
  • RLC receiving entity e.g., RLC UM/AM Rx entity 510 or RLC AM Rx entity 610 as shown and illustrated in FIG. 5
  • an RLC receiving entity e.g., RLC UM/AM Rx entity 510 as shown and illustrated in FIG. 5 detects a packet loss (which is marked as “the 1st packet” for simplicity) or receives, from an RLC transmitting entity (e.g., RLC UM/AM Tx entity 520 as shown and illustrated in FIG. 5) , parameter information regarding a discarding operation of the RLC receiving entity.
  • the packet loss or the discarding operation is associated with the 1st packet.
  • the RLC receiving entity determines to perform the discarding operation to discard a further packet (which is marked as “the 2nd packet” for simplicity) related to the 1st packet in a receiving buffer, in response to detecting the packet loss or in response to receiving the parameter information from the RLC transmitting entity.
  • the RLC receiving entity may detect the packet loss.
  • the RLC receiving entity may receive the parameter information regarding the discarding operation of the RLC receiving entity. Specific examples are described in embodiments of FIGS. 5 and 6 as follows.
  • each of the 1st packet and the 2nd packet is at least one of: (1) an RLC UMD PDU; (2) an RLC AMD PDU; (3) an RLC UMD SDU; (4) an RLC AMD SDU; (5) an RLC UMD segment; or (6) an RLC AMD segment.
  • the 1st packet and the 2nd packet belong to one ADU, e.g., the 1st packet and the 2nd packet have the same ADU index value.
  • the 1st packet and the 2nd packet belong to one GOP, e.g., the 1st packet and the 2nd packet have the same GOP index value.
  • the parameter information may be carried via at least one of PUCCH signalling, a MAC CE, or an RLC control PDU.
  • the parameter information received by the RLC receiving entity may include at least one of following parameters.
  • An importance level (which is marked as “the 1st importance level” for simplicity) of the 1st packet, e.g., “ImportanceToDiscard” in embodiments in FIGS. 5 and 6.
  • the 1st importance level is configured by a network node.
  • a sequence number (SN) value (which is marked as “the 1st SN value” for simplicity) of the 1st packet, e.g., “SNToDiscard” in embodiments in FIGS. 5 and 6.
  • An offset value (which is marked as “the 1st offset value” for simplicity) related to the 1st SN value of the 1st packet, e.g., “Offset” in embodiments in FIGS. 5 and 6.
  • the RLC receiving entity in response to receiving the parameter information from the RLC transmitting entity and in response to the parameter information including the 1st index value (e.g., ADUIndexToDiscard) of the 1st ADU to which the 1st packet belongs, during performing the discarding operation, the RLC receiving entity further checks whether “an index value (which is marked as “the 2nd index value” for simplicity) of an ADU (which is marked as “the 2nd ADU” for simplicity) to which the 2nd packet belongs” is equal to “the 1st index value of the 1st ADU” (e.g., ADUIndexToDiscard) . In response to the 2nd index value of the 2nd ADU being equal to the 1st index value of the 1st ADU, the RLC receiving entity may discard the 2nd packet in the receiving buffer.
  • an index value which is marked as “the 2nd index value” for simplicity
  • the RLC receiving entity may discard the 2nd packet in the receiving buffer.
  • the RLC receiving entity in response to receiving the parameter information from the RLC transmitting entity and in response to the parameter information including the 1st index value of the 1st ADU (e.g., ADUIndexToDiscard) and the 1st index number of the 1st packet (e.g., NumberInUnitToDiscard) , during performing the discarding operation, the RLC receiving entity may:
  • the RLC receiving entity in response to receiving the parameter information from the RLC transmitting entity and in response to the parameter information including the 1st index value of the 1st ADU (e.g., ADUIndexToDiscard) and the 1st importance level of the 1st packet (e.g., ImportanceToDiscard) , during performing the discarding operation of the RLC receiving entity, the RLC receiving entity may:
  • the RLC receiving entity in response to receiving the parameter information from the RLC transmitting entity and in response to the parameter information including the 1st SN value of the 1st packet (e.g., SNToDiscard) and the 1st offset value related to the 1st SN value (e.g., Offset) , during performing the discarding operation of the RLC receiving entity, the RLC receiving entity may:
  • the RLC receiving entity in response to receiving the parameter information from the RLC transmitting entity and in response to the parameter information including the 1st SN value of the 1st packet (e.g., SNToDiscard) , during performing the discarding operation of the RLC receiving entity, the RLC receiving entity may:
  • the RLC receiving entity in response to detecting the packet loss associated with the 1st packet, during performing the discarding operation of the RLC receiving entity, the RLC receiving entity may:
  • the RLC receiving entity in response to detecting the packet loss associated with the 1st packet, during performing the discarding operation of the RLC receiving entity, the RLC receiving entity may:
  • the RLC receiving entity in response to detecting the packet loss associated with the 1st packet, during performing the discarding operation of the RLC receiving entity, the RLC receiving entity may:
  • the RLC receiving entity in response to detecting the packet loss associated with the 1st packet, during performing the discarding operation of the RLC receiving entity, the RLC receiving entity may:
  • the RLC receiving entity may generate further parameter information regarding a discarding operation of the RLC transmitting entity, and transmit the further parameter information to the RLC transmitting entity.
  • the further discarding operation is associated with the 1st packet.
  • the further parameter information may be carried via at least one of PUCCH signalling, a MAC CE, or an RLC control PDU.
  • the further parameter information may include at least one of:
  • the RLC receiving entity in response to discarding the 2nd packet in the receiving buffer, the RLC receiving entity may perform at least one of:
  • the RLC receiving entity may receive, from a network node, configuration information regarding whether the discarding operation of the RLC receiving entity is supported for a radio bearer.
  • the RLC receiving entity may receive, from a network node, configuration information regarding a reception failure number threshold for the RLC receiving entity (e.g., NumberOfReceptionFailure in embodiments in FIGS. 5 and 6) .
  • the discarding operation of the RLC receiving entity may be performed upon meeting the reception failure number threshold for the RLC receiving entity.
  • the RLC receiving entity may:
  • the RLC receiving entity may:
  • the RLC receiving entity may:
  • the RLC receiving entity may:
  • the RLC receiving entity may:
  • the method 300 illustrated in FIG. 3 may include other operation (s) not shown, for example, any operation (s) described with respect to FIGS. 2 and 4-6.
  • FIG. 4 illustrates a further exemplary flow chart for a packet discarding operation according to some embodiments of the present application.
  • the embodiments of FIG. 4 may be performed by an RLC transmitting entity (e.g., RLC UM/AM Tx entity 520 or RLC AM Tx entity 620 as shown and illustrated in FIG. 5 or FIG. 6) .
  • RLC transmitting entity e.g., RLC UM/AM Tx entity 520 or RLC AM Tx entity 620 as shown and illustrated in FIG. 5 or FIG. 6
  • RLC transmitting entity e.g., RLC UM/AM Tx entity 520 or RLC AM Tx entity 620 as shown and illustrated in FIG. 5 or FIG. 6
  • RLC transmitting entity e.g., RLC UM/AM Tx entity 520 or RLC AM Tx entity 620 as shown and illustrated in FIG. 5 or FIG. 6
  • RLC transmitting entity e.g., RLC UM/AM Tx entity 520 or RLC AM Tx
  • an RLC transmitting entity e.g., RLC UM/AM Tx entity 520 as shown and illustrated in FIG. 5 detects a packet loss (which is marked as “the 1st packet” for simplicity) or receives, from an RLC receiving entity (e.g., RLC UM/AM Rx entity 510 as shown and illustrated in FIG. 5) , parameter information regarding a discarding operation of the RLC transmitting entity.
  • the packet loss or the discarding operation is associated with the 1st packet.
  • operation 402 as shown in FIG.
  • the RLC transmitting entity stops transmitting a further packet (which is marked as “the 2nd packet” for simplicity) related to the 1st packet in a transmitting buffer and performs the discarding operation to discard the further packet, in response to detecting the packet loss or in response to receiving the parameter information.
  • a further packet which is marked as “the 2nd packet” for simplicity
  • the RLC transmitting entity may detect the packet loss.
  • the RLC transmitting entity may receive the parameter information regarding the discarding operation of the RLC transmitting entity. Specific examples are described in embodiments of FIGS. 5 and 6 as follows.
  • each of the 1st packet and the 2nd packet is at least one of: (1) an RLC UMD PDU; (2) an RLC AMD PDU; (3) an RLC UMD SDU; (4) an RLC AMD SDU; (5) an RLC UMD segment; or (6) an RLC AMD segment.
  • the 1st packet and the 2nd packet belong to one ADU, e.g., the 1st packet and the 2nd packet have the same ADU index value.
  • the 1st packet and the 2nd packet belong to one GOP, e.g., the 1st packet and the 2nd packet have the same GOP index value.
  • the parameter information may be carried via at least one of PUCCH signalling, a MAC CE, or an RLC control PDU.
  • the RLC transmitting entity may receive, from the network node, at least one of:
  • the RLC retransmission failure number is different from a maximum RLC retransmission number of the RLC transmitting entity.
  • the discarding operation of the RLC transmitting entity is performed after the RLC transmitting entity performing a certain number of an RLC retransmission attempt operation for the 1st packet. In an embodiment, the discarding operation of the RLC transmitting entity is performed in response to the certain number of an RLC retransmission attempt operation for the 1st packet exceeding a maximum RLC retransmission number of the RLC transmitting entity.
  • the RLC transmitting entity in response to detecting the packet loss associated with the 1st packet, during performing the discarding operation of the RLC transmitting entity, the RLC transmitting entity may:
  • the RLC transmitting entity in response to detecting the packet loss associated with the 1st packet, during performing the discarding operation of the RLC transmitting entity, the RLC transmitting entity may:
  • the RLC transmitting entity in response to detecting the packet loss associated with the 1st packet, during performing the discarding operation of the RLC transmitting entity, the RLC transmitting entity may:
  • the RLC transmitting entity in response to detecting the packet loss associated with the 1st packet, during performing the discarding operation of the RLC transmitting entity, the RLC transmitting entity may:
  • the RLC transmitting entity may transmit, to an RLC receiving entity, further parameter information regarding a discarding operation of the RLC receiving entity.
  • the discarding operation of the RLC receiving entity is associated with the 1st packet.
  • the further parameter information may be carried via at least one of PUCCH signalling, a MAC CE, or an RLC control PDU.
  • the further parameter information may include at least one of:
  • TX_Next_Ack e.g., TX_Next_Ack
  • the parameter information received by the RLC transmitting entity includes at least one of:
  • An importance level (which is marked as “the 1st importance level” for simplicity) of the 1st packet, e.g., “ImportanceToDiscard” in embodiments in FIGS. 5 and 6.
  • the importance level is configured by a network node.
  • a SN value (which is marked as “the 1st SN value” for simplicity) of the 1st packet, e.g., “SNToDiscard” in embodiments in FIGS. 5 and 6.
  • An offset value (which is marked as “the 1st offset value” for simplicity) related to the 1st SN value of the 1st packet, e.g., “Offset” in embodiments in FIGS. 5 and 6.
  • the RLC transmitting entity in response to receiving the parameter information from the RLC receiving entity and in response to the parameter information including the 1st index value of the 1st ADU (e.g., ADUIndexToDiscard) , during performing the discarding operation of the RLC transmitting entity, the RLC transmitting entity may:
  • the RLC transmitting entity in response to receiving the parameter information from the RLC receiving entity and in response to the parameter information including the 1st index value of the 1st ADU (e.g., ADUIndexToDiscard) and the 1st index number of the 1st packet (e.g., NumberInUnitToDiscard) , during performing the discarding operation of the RLC transmitting entity, the RLC transmitting entity may:
  • the RLC transmitting entity in response to receiving the parameter information from the RLC receiving entity and in response to the parameter information including the 1st index value of the 1st ADU (e.g., ADUIndexToDiscard) and the 1st importance level of the 1st packet (e.g., ImportanceToDiscard) , during performing the discarding operation of the RLC transmitting entity, the RLC transmitting entity may:
  • the RLC transmitting entity in response to receiving the parameter information from the RLC receiving entity and in response to the parameter information including the 1st SN value of the 1st packet (e.g., SNToDiscard) and the 1st offset value related to the 1st SN value (e.g., Offset) , during performing the discarding operation of the RLC transmitting entity, the RLC transmitting entity may:
  • the RLC transmitting entity in response to receiving the parameter information from the RLC receiving entity and in response to the parameter information including the 1st SN value of the 1st packet (e.g., SNToDiscard) , during performing the discarding operation of the RLC transmitting entity, the RLC transmitting entity may:
  • the method illustrated in FIG. 4 may include other operation (s) not shown, for example, any operation (s) described with respect to FIGS. 2, 3, 5, and 6.
  • FIGS. 5 and 6 show some specific embodiments of the methods as shown and illustrated in FIGS. 2-4.
  • the embodiments of FIGS. 5 and 6 assume that the packets are related to one XR service and correlated with each other.
  • each packet i.e., an RLC PDU
  • ADU or GOP index i.e., the number of frames in the same ADU or GOP
  • An importance level i.e., the number of frames in the same ADU or GOP
  • One ADU or GOP has multiple frames correlated to each other. Packets belonging to the same ADU or GOP are correlated to each other, e.g., for instance, if the I-frame packet is lost, the user will not be able to decode the subsequent P-frames and B-frames.
  • Packets belonging to the same ADU or GOP are of different importance levels, e.g., the I-frame packets are of a higher importance level than P-frames and B-frames.
  • a packet can be an UMD PDU, an AMD PDU, a segment of a PDU, an UMD SDU, an AMD SDU, or a segment of a SDU.
  • FIG. 5 illustrates an exemplary flow chart of a packet discarding operation in an RLC UM or AM receiving entity according to some embodiments of the present application.
  • RLC UM/AM Rx entity 510 makes a packet discarding decision.
  • RLC UM/AM Rx entity 510 transmits “parameter information regarding a discarding operation of RLC UM/AM Tx entity 520” to RLC UM/AM Tx entity 520.
  • RLC UM/AM Rx entity 510 may transmit “parameter information regarding the packet loss and a discarding operation of RLC UM/AM Rx entity 510” to RLC UM/AM Tx entity 520 (e.g., which may be an RLC UM transmitting entity) .
  • the parameter information can be transmitted via PUCCH signalling, a MAC CE or an RLC control PDU (e.g., RLC status report or new RLC control PDU) .
  • the parameter information may include “ADUIndexToDiscard” value, and optionally “NumberInUnitToDiscard” value or “ImportanceToDiscard” value.
  • RLC UM/AM Tx entity 520 upon receiving the parameter information from RLC UM/AM Rx entity 510, RLC UM/AM Tx entity 520 will discard packet (s) (e.g., UM PDU (s) ) in the transmitting buffer which is correlated to the discarded packet (s) indicated by RLC UM/AM Rx entity 510.
  • packet (s) e.g., UM PDU (s)
  • RLC UM/AM Tx entity 520 may perform one of:
  • RLC UM/AM Rx entity 510 there may be different operations of RLC UM/AM Rx entity 510 in an RLC UM data transfer procedure or an RLC AM data transfer procedure, which are described as below.
  • RLC UM Rx entity 510 may detect a packet loss or perform a packet discarding operation. For example, RLC UM Rx entity 510 detects a packet loss in case that segments associated with one SN are discarded before all received due to an expiry of timer t-Reassembly. For an RLC UM data transfer procedure, RLC UM Tx entity 520 does not know any packet loss of RLC UM Rx entity 510, and thus a packet discarding operation of RLC UM Rx entity 510 can be only triggered by RLC UM Tx entity 520.
  • RLC UM Rx entity 510 when RLC UM Rx entity 510 detects UMD PDU loss for an RLC UM data radio bearer, RLC UM Rx entity 510 may discard one or multiple received UMD PDUs that are dependent on the lost UMD PDU (e.g., belong to the same ADU or GOP) .
  • whether a packet discarding operation according to ADU or GOP is allowed to a given data radio bearer is configured by a network node. It might also imply whether the RLC PDU header will include information about ADU or GOP, a number in unit, or importance level information. For example, once RLC UM Rx entity 510 makes a packet discarding decision, RLC UM Rx entity 510 also notifies RLC UM Tx entity 520 about the packet discarding decision, e.g., by indicating the ADUIndexToDiscard.
  • RLC UM Rx entity 510 if the lost packet is associated with a certain ADU or GOP indicated by an ADU or GOP index and is the number “N” packet in the ADU or GOP indicated by the number in the unit, RLC UM Rx entity 510 will discard other packet (s) belonging to the same ADU or GOP and with the number of unit greater than “N” .
  • the information about the lost packet may be indicated by an upper layer of RLC UM Rx entity 510.
  • RLC UM Rx entity 510 when an UMD PDU is received from a lower layer, RLC UM Rx entity 510 shall check whether the associated ADU index equals to ADUIndexToDiscard and whether the associated number in the unit is greater than NumberInUnitToDiscard. If so, RLC UM Rx entity 510 shall discard the received UMD PDU.
  • One specific embodiment may be as follows:
  • RLC UM Rx entity 510 shall:
  • RLC UM Rx entity 510 when RLC UM Rx entity 510 discards UMD PDUs with packet (s) outside a reassemble window, RLC UM Rx entity 510 discards other UMD PDU (s) in the RLC receiving buffer with an ADU index which is equal to an ADU index associated with the lost UMD PDU and (optionally) the associated number in the unit which is greater than the number in unit associated with the lost UMD PDU.
  • RLC UM Rx entity 510 may update or set values of ADUIndexToDiscard and NumberInUnitToDiscard.
  • the value of ADUIndexToDiscard may be updated or set to the largest ADU index associated with the discarded UMD PDU (s)
  • the value of NumberInUnitToDiscard may be updated or set to the largest number in unit value associated with the discarded UMD PDU (s) .
  • RLC UM Rx entity 510 may transmit information including ADUIndexToDiscard and/or NumberInUnitToDiscard to RLC UM Tx entity 520.
  • RLC UM Rx entity 510 upon discarding the relevant UMD PDU (s) , updates or sets an UM receiving state variable (e.g., RX_Next_Reassembly) to a SN value of the first packet that has not been reassembled.
  • RX_Next_Reassembly an UM receiving state variable
  • the RLC UM receiving entity shall:
  • NumberInUnitToDiscard the largest number in unit value associated with the discarded segments (e.g., UMD PDUs)
  • RLC UM Rx entity 510 if the lost packet is associated with a certain ADU or GOP indicated by an ADU or GOP index and is of importance level “M” , RLC UM Rx entity 510 will discard other packet (s) belonging to the same ADU or GOP and of a lower importance level than the lost packet importance level “M” .
  • the information about the lost packet may be indicated by an upper layer of RLC UM Rx entity 510.
  • RLC UM Rx entity 510 when an UMD PDU is received from a lower layer, RLC UM Rx entity 510 shall check whether the associated ADU index equals to ADUIndexToDiscard and whether the associated importance level is less than ImportanceToDiscard. If so, RLC UM Rx entity 510 shall discard the received UMD PDU. For example, the value of ImportanceToDiscard is configured by a network node via radio resource control (RRC) signalling.
  • RRC radio resource control
  • RLC UM Rx entity 510 when RLC UM Rx entity 510 discards UMD PDUs with packet (s) outside a reassemble window, RLC UM Rx entity 510 discards the other UMD PDUs in the RLC receiving buffer with “an ADU index equals to the ADU index associated with the lost UMD PDU” and “the associated importance level less than ImportanceToDiscard” . Then, RLC UM Rx entity 510 may update or set the value of ADUIndexToDiscard. In an embodiment, the value of ADUIndexToDiscard may be updated or set to the largest ADU index associated with the discarded UMD PDU (s) .
  • RLC UM Rx entity 510 may transmit information including ADUIndexToDiscard to RLC UM Tx entity 520.
  • an UM receiving state variable e.g., RX_Next_Reassembly
  • RX_Next_Reassembly may be updated or set to a SN value of the first packet that has not been reassembled.
  • RLC AM Rx entity 510 may the RLC AM receiving entity may discard one or multiple received AMD PDU (s) that are dependent on the lost AMD PDU and belonging to the same ADU or GOP without causing an RLC failure.
  • RLC AM Rx entity 510 and RLC AM Tx entity 520 know the packet loss, and thus a packet discarding operation of RLC AM Rx entity 510 can be only triggered by any side and inform the peer side.
  • an AMD PDU discard operation is triggered by RLC AM Rx entity 510. Whether the AMD PDU discard operation according to the lost AMD PDU is allowed to a given data radio bearer is configured by a network node. It might also imply whether the RLC PDU header will include information about correlation with other AMD PDU (s) (e.g., an offset value means that it depends on an offset number of AMD PDUs before it, an ADU or a GOP, a number in unit, or importance level information) .
  • an offset value means that it depends on an offset number of AMD PDUs before it, an ADU or a GOP, a number in unit, or importance level information
  • RLC AM Rx entity 510 receives an indication from the peer RLC AM transmitting entity, i.e., RLC AM Tx entity 520, about an AMD PDU discarding operation triggered by RLC AM Tx entity 520.
  • the indication may imply at least one of:
  • ADUIndexToDiscard value and optionally NumberInUnitToDiscard value or ImportanceToDiscard value decided by RLC AM Tx entity 520.
  • RLC AM Rx entity 510 once RLC AM Rx entity 510 performs the AMD PDU discarding operation, RLC AM Rx entity 510 also notifies information about the AMD PDU discarding operation, e.g., by indicating ADUIndexToDiscard, to RLC AM Tx entity 520.
  • the RLC AM packet contains an offset value, which means that the current RLC AM packet has dependency on the offset number of an RLC AM packet before it, and any loss of the previous offset number of RLC AM packet will make the current RLC AM packet useless.
  • SN1 SN1
  • RLC AM Rx entity 510 will discard this RLC packet.
  • RLC AM Rx entity 510 will update or set SNToDiscard to the largest SN value associated with the discarded RLC AM packets. Then, RLC AM Rx entity 510 may transmit information including SNToDiscard to RLC AM Tx entity 520.
  • a receiving state variable (e.g., RX_Next) is updated to the SN value of the first RLC SDU with “SN > current RX_Next” and for which not all bytes have been received.
  • a receiving state variable status trigger value (e.g., RX_Next_Status_Trigger) may be updated to “RX_Next + 1” .
  • the RLC AM receiving entity will discard the other packets belonging to the same ADU or GOP and (optionally) with the number of unit greater than “N” .
  • RLC AM Rx entity 510 when an AMD PDU is received from a lower layer, RLC AM Rx entity 510 shall check whether the associated ADU index equals to ADUIndexToDiscard and whether the associated number in the unit is greater than NumberInUnitToDiscard. If so, RLC AM Rx entity 510 shall discard the received AMD PDU.
  • One specific embodiment may be as follows:
  • RLC AM Rx entity 510 when RLC AM Rx entity 510 detects an AMD PDU reception failure, when timer t-Reassembly expires, RLC AM Rx entity 510 discards the other AMD PDUs in the RLC reception buffer with “an ADU index equals to an ADU index associated with the lost AMD PDU” and “the associated number in the unit is greater than the number in unit associated with the lost AMD PDU” . Then, RLC AM Rx entity 510 updates or sets the value of ADUIndexToDiscard and/or NumberInUnitToDiscard.
  • RLC UM Rx entity 510 may transmit information including ADUIndexToDiscard and/or NumberInUnitToDiscard to RLC UM Tx entity 520.
  • a receiving state variable (e.g., RX_Next) is updated to the SN value of the first RLC SDU with “SN > current RX_Next” and for which not all bytes have been received.
  • a receiving state variable status trigger value (e.g., RX_Next_Status_Trigger) may be updated to “RX_Next +1” .
  • RLC AM Rx entity 510 will discard the other packets belonging to the same ADU or GOP and of a lower importance level than importance level value “M” of the lost packet.
  • the receiving AM RLC entity when an AMD PDU is received from a lower layer, the receiving AM RLC entity shall check whether the associated ADU index equals to ADUIndexToDiscard and whether the associated importance level is below ImportanceToDiscard. If so, RLC AM Rx entity 510 shall discard the received AMD PDU.
  • ImportanceToDiscard may be configured by a network node.
  • RLC AM Rx entity 510 when RLC AM Rx entity 510 detects an AMD PDU reception failure upon timer t-Reassembly expiry, RLC AM Rx entity 510 discards relevant AMD PDU (s) in the RLC reception buffer with “ADU index equals to ADU index associated with the lost AMD PDU” and “the associated number in the unit is greater than the number in unit associated with the lost AMD PDU” . Then, RLC AM Rx entity 510 update or set the value of ADUIndexToDiscard. For instance, the value of ADUIndexToDiscard is updated to the largest ADU index associated with the discarded AMD PDU (s) .
  • RLC AM Rx entity 510 may transmit information including ADUIndexToDiscard to RLC AM Tx entity 520.
  • a receiving state variable e.g., RX_Next
  • RX_Next_Status_Trigger e.g., RX_Next + 1”
  • NumberOfReceptionFailure is configured to RLC AM Rx entity 510 by a network node.
  • NumberOfReceptionFailure e.g., “timer t-Reassembly expires a number of times greater than NumberOfReceptionFailure” and “the same missing RLC AMD PDU has not been received yet”
  • RLC AM Rx entity 510 will discard the relevant RLC AMD PDUs, e.g., based on conditions related to “SNToDiscard and/or Offset” or “ADUIndexToDiscard and/or NumberInUnitToDiscard” or “ADUIndexToDiscard and/or ImportanceToDiscard” described in any of the abovementioned embodiments.
  • RLC AM Rx entity 510 may also indicate the packet loss and a packet discarding decision to RLC AM Tx entity 520.
  • RLC AM Rx entity 510 can transmit such indication information via a PUCCH signalling, a MAC CE, or an RLC control PDU (e.g., an RLC status report or a new RLC control PDU) .
  • the information may imply or include:
  • ADUIndexToDiscard value and optionally NumberInUnitToDiscard or ImportanceToDiscard value decided by RLC AM Tx entity 520.
  • RLC AM Rx entity 510 upon receiving indication information about a packet discard operation from RLC AM Tx entity 520, RLC AM Rx entity 510 will discard those RLC AM packets in the reception buffer which is correlated to the discarded RLC AM packet (s) indicated by RLC AM Tx entity 520. For example:
  • RLC AM Rx entity 510 may discard those associated with “the ADU index which is the same as ADUIndexToDiscard” .
  • RLC AM Rx entity 510 may discard those associated with “the ADU index which is the same as ADUIndexToDiscard” and with “a number in unit which is greater than NumberInUnitToDiscard, if applicable” .
  • RLC AM Rx entity 510 may discard those associated with “the ADU index which is same as ADUIndexToDiscard” and with “an importance level which is lower than ImportanceToDiscard” , if applicable.
  • RX_Next is updated to the SN of the first RLC SDU with SN > current RX_Next and for which not all bytes have been received.
  • RX_Next_Status_Trigger is updated to “RX_Next + 1” .
  • SNToDiscard, ADUIndexToDiscard, NumberInUnitToDiscard, ImportanceToDiscard are set to the values indicated by RLC AM Tx entity 520.
  • FIG. 6 illustrates an exemplary flow chart of a packet discarding operation in an RLC AM transmitting entity according to some embodiments of the present application.
  • RLC AM Tx entity 620 of an AM data radio bearer may decide to discard relevant RLC AMD PDU (s) in its transmitting buffer (which may also be named as a transmission buffer) .
  • RLC AM Tx entity 620 makes a packet discarding decision.
  • RLC AM Tx entity 620 transmits “parameter information regarding a discarding operation of RLC AM Rx entity 610” to RLC Rx entity 610.
  • RLC AM Rx entity 610 discard relevant packets.
  • the number of RLC retransmission failure which triggers packet discard at the RLC AM transmitting entity is configured by the network and is a different value than the maximum number of RLC AM retransmission.
  • the RLC transmitting entity will discard the relevant RLC AMD PDU (s) if the number of RLC retransmission attempts exceeds the maximum number of RLC retransmission.
  • RLC AM Tx entity 620 may perform one of:
  • RLC AMD PDU discard is triggered by RLC AM Tx entity 620 itself:
  • SNToDiscard is set to the SN value associated with the RLC packet in the transmission buffer which triggers the RLC packet discarding operation.
  • ADUIndexToDiscard is set to the ADU index value associated with the RLC AMD PDU in the transmission buffer which triggers the RLC AMD PDU (s) discarding operation.
  • NumberInUnitToDiscard is set to the number in unit value associated with the RLC AMD PDU in the transmission buffer which triggers the RLC AMD PDU (s) discarding operation.
  • ImportanceToDiscard is either set to the importance level value associated with the RLC AMD PDU in the transmission buffer which triggers the RLC AMD PDU (s) discarding operation, or set to an ImportanceToDiscard value configured by a network node in advance.
  • RLC AM Tx entity 620 may also indicate the packet discard to RLC AM Rx entity 610.
  • indication information can be sent via PDCCH signalling, a MAC CE, or a new RLC control PDU.
  • the indication information may imply or include:
  • ADUIndexToDiscard value and optionally NumberInUnitToDiscard or ImportanceToDiscard value decided by RLC AM Tx entity 620.
  • the RLC AMD PDU discard is triggered by receiving the RLC AMD PDU discard decision from RLC AM Rx entity 610, SNToDiscard, ADUIndexToDiscard, NumberInUnitToDiscard, ImportanceToDiscard are set to the values as indicated by RLC AM Rx entity 610.
  • controllers, flowcharts, and modules may also be implemented on a general purpose or special purpose computer, a programmed microprocessor or microcontroller and peripheral integrated circuit elements, an integrated circuit, a hardware electronic or logic circuit such as a discrete element circuit, a programmable logic device, or the like.
  • any device that has a finite state machine capable of implementing the flowcharts shown in the figures may be used to implement the processing functions of the present disclosure.
  • the terms “includes, “ “including, “ or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that includes a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus.
  • An element proceeded by “a, “ “an, “ or the like does not, without more constraints, preclude the existence of additional identical elements in the process, method, article, or apparatus that includes the element.
  • the term “another” is defined as at least a second or more.
  • the term “having” and the like, as used herein, are defined as "including.

Landscapes

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

Abstract

Des modes de réalisation de la présente demande concernent des procédés et des appareils de prise en charge d'une opération de rejet de paquet dans une couche de commande de liaison radioélectrique (RLC) en raison d'une perte de paquet. Selon un mode de réalisation de la présente demande, une entité de réception RLC inclut un processeur et un émetteur-récepteur couplé au processeur. Le processeur est configuré : pour détecter une perte de paquet ou pour recevoir, via l'émetteur-récepteur en provenance d'une entité de transmission RLC, des informations de paramètre concernant une opération de rejet de l'entité de réception RLC, la perte de paquet ou l'opération de rejet étant associée à un paquet; et pour réaliser l'opération de rejet pour rejeter un autre paquet associé au paquet dans la mémoire tampon de réception, en réponse à la détection de la perte de paquet ou en réponse à la réception des informations de paramètre.
PCT/CN2021/140954 2021-12-23 2021-12-23 Procédés et appareils de prise en charge d'une opération de rejet de paquet dans une couche rlc en raison d'une perte de paquet WO2023115477A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/140954 WO2023115477A1 (fr) 2021-12-23 2021-12-23 Procédés et appareils de prise en charge d'une opération de rejet de paquet dans une couche rlc en raison d'une perte de paquet

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/140954 WO2023115477A1 (fr) 2021-12-23 2021-12-23 Procédés et appareils de prise en charge d'une opération de rejet de paquet dans une couche rlc en raison d'une perte de paquet

Publications (1)

Publication Number Publication Date
WO2023115477A1 true WO2023115477A1 (fr) 2023-06-29

Family

ID=86901148

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/140954 WO2023115477A1 (fr) 2021-12-23 2021-12-23 Procédés et appareils de prise en charge d'une opération de rejet de paquet dans une couche rlc en raison d'une perte de paquet

Country Status (1)

Country Link
WO (1) WO2023115477A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200052833A1 (en) * 2017-04-28 2020-02-13 Guamgdong Oppo Mobile Telecommunications Corp., Ltd. Method and apparatus for wireless communication
CN112770312A (zh) * 2021-01-04 2021-05-07 腾讯科技（深圳）有限公司 数据传输方法、装置、计算机可读介质及电子设备
CN112804710A (zh) * 2021-01-04 2021-05-14 腾讯科技（深圳）有限公司 数据传输方法、装置、计算机可读介质及电子设备
CN112804711A (zh) * 2021-01-04 2021-05-14 腾讯科技（深圳）有限公司 数据传输方法、装置、计算机可读介质及电子设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200052833A1 (en) * 2017-04-28 2020-02-13 Guamgdong Oppo Mobile Telecommunications Corp., Ltd. Method and apparatus for wireless communication
CN112770312A (zh) * 2021-01-04 2021-05-07 腾讯科技（深圳）有限公司 数据传输方法、装置、计算机可读介质及电子设备
CN112804710A (zh) * 2021-01-04 2021-05-14 腾讯科技（深圳）有限公司 数据传输方法、装置、计算机可读介质及电子设备
CN112804711A (zh) * 2021-01-04 2021-05-14 腾讯科技（深圳）有限公司 数据传输方法、装置、计算机可读介质及电子设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
INTEL CORPORATION: "Report of [Post109e#11][MOB] Resolving open issues for DAPS (Intel)", 3GPP DRAFT; R2-2003371, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Online Meeting ;20200420 - 20200430, 10 April 2020 (2020-04-10), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051871332 *

Similar Documents

Publication Publication Date Title
EP3011705B1 (fr) Mécanisme d'interrogation et de notification
US20160219458A1 (en) Methods and apparatus for radio link control switching
KR101577451B1 (ko) Ｒｌｃ 무한 재전송 오류를 검출하고 처리하는 방법
US20170134992A1 (en) Interruptions In Wireless Communications
JP6262991B2 (ja) ユーザ装置及び方法
JP2020509663A (ja) データ伝送方法、通信デバイス、端末、および基地局
EP3186912B1 (fr) Procédé et appareil de gestion d'une perte de paquet dans un réseau de communication mobile
US10979950B2 (en) Method and device for improving communication quality in mobile communication network
US20150382395A1 (en) Method For Recovering From PDCP HFN De-Synchronization For VoLTE Call And Data Failure In RLC Layer
WO2024082572A1 (fr) Procédés et appareils pour un temporisateur de rejet
WO2023206133A1 (fr) Procédés et appareils d'améliorations d'opération de rejet de données
WO2023087145A1 (fr) Procédés et appareils de gestion de réordonnancement de pdcp
WO2023184479A1 (fr) Procédé et appareil de prise en charge de mobilité
WO2023115477A1 (fr) Procédés et appareils de prise en charge d'une opération de rejet de paquet dans une couche rlc en raison d'une perte de paquet
WO2023115473A9 (fr) Procédés et appareils pour prendre en charge une opération de rejet de paquets dans une couche pdcp en raison d'une perte de paquet
US20230362721A1 (en) Method and apparatus for multicast and broadcast services
CN114270742B (zh) 处理数据包的方法和通信装置
WO2023108413A1 (fr) Procédé et appareil de rapport d'état de tampon
US9313136B1 (en) Managing data retransmission to a wireless device
WO2024087585A9 (fr) Procédé et appareil de transmission de données utilisant des temporisateurs de rejet d'ensemble d'unités de données de protocole
WO2024073967A1 (fr) Procédés et appareils pour un mécanisme d'activation de gestion de congestion
EP4052504B1 (fr) Traitement d'erreur pour segmentation rrc
WO2023216258A1 (fr) Procédés et appareils pour une opération de gestion de réception de sdu pdcp
US20240080928A1 (en) Method and apparatus for data transmission
GB2626626A (en) Methods for controlling a packet data convergence protocol communication network

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE