WO2019063880A1 - Gestion d'unité de données de service - Google Patents

Gestion d'unité de données de service Download PDF

Info

Publication number
WO2019063880A1
WO2019063880A1 PCT/FI2018/050687 FI2018050687W WO2019063880A1 WO 2019063880 A1 WO2019063880 A1 WO 2019063880A1 FI 2018050687 W FI2018050687 W FI 2018050687W WO 2019063880 A1 WO2019063880 A1 WO 2019063880A1
Authority
WO
WIPO (PCT)
Prior art keywords
level protocol
protocol entity
data unit
entity
response
Prior art date
Application number
PCT/FI2018/050687
Other languages
English (en)
Inventor
Henri Koskinen
Original Assignee
Nokia Technologies Oy
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 Nokia Technologies Oy filed Critical Nokia Technologies Oy
Priority to EP18782095.6A priority Critical patent/EP3688909A1/fr
Publication of WO2019063880A1 publication Critical patent/WO2019063880A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/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
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/188—Time-out mechanisms

Definitions

  • Certain embodiments may relate to communication systems involving transmission of protocol data units (PDUs) and service data units (SDUs).
  • PDUs protocol data units
  • SDUs service data units
  • managing an SDU associated with a given sequence number may be used in a communication system to provide improved utilization of network resources.
  • one or more entities may include one or more layered protocol entities, such as one or more packet data convergence protocol (PDCP) entities, one or more radio link control (RLC) entities, one or more medium access control (MAC) entities, and one or more physical (PHY) entities.
  • PDCP packet data convergence protocol
  • RLC radio link control
  • MAC medium access control
  • PHY physical
  • a PDCP entity may be associated with a PDCP protocol layer
  • RLC entity may be associated with a RLC protocol layer
  • a MAC entity may be associated with a MAC protocol layer
  • PHY entity may be associated with a PHY protocol layer.
  • one or more protocol entities may be arranged according to one or more layers.
  • one or more PDCP entities may be higher-level protocol entities
  • one or more RLC entities may be lower-level protocol entities, with the one or more PDCP entities being at a higher level than the one or more RLC entities.
  • one or more MAC entities and/or one or more PHY entities may be lower-level protocol entities, with the one or more MAC entities and/or one or more PHY entities being at a lower level than one or more LC entities.
  • a first PDCP entity may send an indication not to wait for reception of an SDU to a second PDCP entity, despite the PDCP PDU already being transmitted at a first lower-level protocol entity. In such a case, the corresponding SDU may not be delivered to a higher layer despite being received, resulting in packet loss and wasted network resources.
  • a method may include transmitting, by a first higher- level protocol entity, a service data unit within a packet data unit to a first lower-level protocol entity.
  • the method may further include transmitting, by the first higher-level protocol entity to the first lower-level protocol entity, an indication for discarding the packet data unit.
  • the method may further include receiving, by the first higher-level protocol entity, a response to the indication from the first lower-level protocol entity.
  • the method may further include, based on the response or lack of response, transmitting, by the first higher-level protocol entity to a second higher- level protocol entity, an instruction not to wait for reception of the service data unit.
  • an apparatus may include means for transmitting a service data unit within a packet data unit to a first lower-level protocol entity.
  • the apparatus may further include means for transmitting an indication for discarding the packet data unit.
  • the apparatus may further include means for receiving a response to the indication from the first lower-level protocol entity.
  • the apparatus may further include, based on the response or lack of response, means for transmitting an instruction not to wait for reception of the service data unit.
  • an apparatus may include at least one processor and at least one memory including computer program code.
  • the at least one memory and the computer program code can be configured to, with the at least one processor, cause the apparatus to at least transmit a service data unit within a packet data unit to a first lower-level protocol entity.
  • the at least one memory and the computer program code can be further configured to, with the at least one processor, cause the apparatus to at least transmit an indication for discarding the packet data unit.
  • the at least one memory and the computer program code can be further configured to, with the at least one processor, cause the apparatus to at least receive a response to the indication from the first lower-level protocol entity.
  • the at least one memory and the computer program code can be further configured to, with the at least one processor, cause the apparatus to at least, based on the response or lack of response, transmit an instruction not to wait for reception of the service data unit.
  • a non-transitory computer readable medium can be encoded with instructions that may, when executed in hardware, perform a method.
  • the method may transmit a service data unit within a packet data unit to a first lower- level protocol entity.
  • the method may further transmit an indication for discarding the packet data unit.
  • the method may further receive a response to the indication from the first lower-level protocol entity.
  • the method may further, based on the response or lack of response, transmit an instruction not to wait for reception of the service data unit.
  • a computer program product may perform a method.
  • the method may transmit a service data unit within a packet data unit to a first lower-level protocol entity.
  • the method may further transmit an indication for discarding the packet data unit.
  • the method may further receive a response to the indication from the first lower-level protocol entity.
  • the method may further based on the response or lack of response, transmit an instruction not to wait for reception of the service data unit.
  • an apparatus may include circuitry configured to transmit a service data unit within a packet data unit to a first lower-level protocol entity.
  • the circuitry may further transmit an indication for discarding the packet data unit.
  • the circuitry may further receive a response to the indication from the first lower- level protocol entity.
  • the circuitry may further, based on the response or lack of response, transmit an instruction not to wait for reception of the service data unit.
  • a method may include receiving, by a first lower-level protocol entity, a service data unit from a first higher-level protocol entity.
  • the method may further include receiving, by the first lower-level protocol entity from the first higher-level protocol entity, an indication for discarding the service data unit.
  • the method may further include, in response to receiving the indication for discarding the service data unit, transmitting, by the first lower-level protocol entity, a response to the first higher-level protocol entity, wherein the response is used to determine whether to send an instruction to a second higher-level protocol entity not to wait for reception of the service data unit.
  • an apparatus may include means for receiving a service data unit from a first higher-level protocol entity.
  • the apparatus may further include means for receiving an indication for discarding the service data unit.
  • the apparatus may further include means for, in response to receiving the indication for discarding the service data unit, transmitting a response to the first higher-level protocol entity, wherein the response is used to determine whether to send an instruction to a second higher-level protocol entity not to wait for reception of the service data unit.
  • an apparatus may include at least one processor and at least one memory including computer program code.
  • the at least one memory and the computer program code can be configured to, with the at least one processor, cause the apparatus to at least receive a service data unit from a first higher- level protocol entity.
  • the at least one memory and the computer program code can be further configured to, with the at least one processor, cause the apparatus to at least receive an indication for discarding the service data unit.
  • the at least one memory and the computer program code can be further configured to, with the at least one processor, cause the apparatus to at least, in response to receiving the indication for discarding the service data unit, transmit a response to the first higher-level protocol entity, wherein the response is used to determine whether to send an instruction to a second higher-level protocol entity not to wait for reception of the service data unit.
  • a non-transitory computer readable medium can be encoded with instructions that may, when executed in hardware, perform a method.
  • the method may receive a service data unit from a first higher-level protocol entity.
  • the method may further receive an indication for discarding the service data unit.
  • the method may further, in response to receiving the indication for discarding the service data unit, transmit a response to the first higher- level protocol entity, wherein the response is used to determine whether to send an instruction to a second higher-level protocol entity not to wait for reception of the service data unit.
  • a computer program product may perform a method.
  • the method may receive a service data unit from a first higher-level protocol entity.
  • the method may further receive an indication for discarding the service data unit.
  • the method may further, in response to receiving the indication for discarding the service data unit, transmit a response to the first higher- level protocol entity, wherein the response is used to determine whether to send an instruction to a second higher-level protocol entity not to wait for reception of the service data unit.
  • an apparatus may include circuitry configured to receive a service data unit from a first higher-level protocol entity.
  • the circuitry may further receive an indication for discarding the service data unit.
  • the circuitry may further, in response to receiving the indication for discarding the service data unit, transmit a response to the first higher-level protocol entity, wherein the response is used to determine whether to send an instruction to a second higher-level protocol entity not to wait for reception of the service data unit.
  • Figure 1 illustrates a system according to certain embodiments.
  • Figure 2 illustrates an example of a signaling diagram according to certain embodiments.
  • Figure 3 illustrates another example of a signaling diagram according to certain embodiments.
  • Figure 4 illustrates an example of a method according to certain embodiments.
  • Figure 5 illustrates an example of another method according to certain embodiments.
  • Certain embodiments contained herein may provide significant technical advantages. For example, certain embodiments may improve the process related to transmission of indications not to wait for reception of PDCP SDUs. By doing so, certain embodiments may reduce the overall resources utilized by entities by avoiding unnecessary use of network resources. Such a reduction in the overall resources may allow the network to dedicate the saved resources to other areas, thus improving overall network performance and utilization.
  • Figure 1 illustrates a system according to certain embodiments.
  • a system may include multiple apparatuses, such as first apparatus 110 and/or second apparatus 120.
  • first apparatus 210 and/or second apparatus 220 may be one or more of user equipment, a mobile device, such as a mobile phone, smart phone, personal digital assistant (PDA), tablet, or portable media player, digital camera, pocket video camera, video game console, navigation unit, such as a global positioning system (GPS) device, desktop or laptop computer, single- location device, such as a sensor or smart meter, or any combination thereof.
  • GPS global positioning system
  • first apparatus 210 and/or second apparatus 220 may also be one or more of a base station, such as an evolved node B (eNB) or next generation node B (gNB), a next generation radio access network (NG RAN), a mobility management entity (MME), a serving gateway, a server, and/or any other access node or combination thereof.
  • a base station such as an evolved node B (eNB) or next generation node B (gNB), a next generation radio access network (NG RAN), a mobility management entity (MME), a serving gateway, a server, and/or any other access node or combination thereof.
  • eNB evolved node B
  • gNB next generation node B
  • NG RAN next generation radio access network
  • MME mobility management entity
  • serving gateway a server, and/or any other access node or combination thereof.
  • One or more of apparatuses 110 and 120 may include at least one processor, respectively indicated as 11 1 and 121. At least one memory may be provided in one or more of apparatuses 110 and 120, indicated at 112 and 122, respectively. Memory 1 12, 122 may be fixed and/or removable. Memory 112, 122 may include computer program instructions or computer code contained therein. Processors 11 1, 121 and memories 112, 122, or a subset thereof, may be configured to provide means corresponding to the various blocks of Figures 2-5. Although not shown, one or more of apparatuses 1 10 and 120 may also include positioning hardware, such as global positioning system (GPS) or micro electrical mechanical system (MEMS) hardware, which may be used to determine a location of the corresponding apparatus. Other sensors are also permitted and may be included to determine location, elevation, orientation, and so forth, such as barometers, altimeters, compasses, and the like.
  • GPS global positioning system
  • MEMS micro electrical mechanical system
  • transceivers 113 and 123 may be provided, and one or more transceivers may include at least one antenna, respectively illustrated as 1 14 and 124.
  • Apparatuses 110 and/or 120 may have many antennas, such as an array of antennas configured for multiple input multiple output (MIMO) communications, or multiple antennas for multiple radio access technologies. Other configurations of these apparatuses, for example, may be provided.
  • MIMO multiple input multiple output
  • Transceivers 113 and 123 may be a transmitter, a receiver, both a transmitter and a receiver, or a unit or device that may be configured both for transmission and reception.
  • Processors 11 1 and 121 may be embodied by any computational or data processing device, such as a central processing unit (CPU), application specific integrated circuit (ASIC), or comparable device.
  • the processors may be implemented as a single controller, or a plurality of controllers or processors.
  • the processors may be general purpose or special purpose processors.
  • Memory 1 12 and 122 may independently be any suitable storage device, such as a non-transitory computer-readable medium.
  • a hard disk drive (HDD), random access memory (RAM), flash memory, or other suitable memory may be used.
  • the memories may be combined on a single integrated circuit as the processor, or may be separate from the one or more processors.
  • the computer program instructions stored in the memory and which may be processed by the processors may be any suitable form of computer program code, for example, a compiled or interpreted computer program written in any suitable programming language.
  • the memory and the computer program instructions may be configured, with the processor for the particular apparatus, to cause an apparatus, such as user equipment, an eNB, or a gNB, to perform any of the processes described below (see, for example, Figures 2-5). Therefore, in certain embodiments, a non-transitory computer-readable medium may be encoded with computer instructions that, when executed in hardware, perform a process such as one of the processes described herein. Alternatively, certain embodiments may be performed entirely in hardware.
  • Figure 2 illustrates an example of one or more protocol entities in a cellular network, such as a LTE network, 5G, and/or New Radio network, transmitting and/or receiving one or more PDUs and/or SDUs.
  • a cellular network may include one or more protocol entities, such as PDCP entities 212 and 222, RLC entities 214 and 224, MAC entities 216 and 226, and physical-layer entities 218 and 228.
  • one or more of the protocol entities may be included in one or more apparatuses, with one or more of the protocol entities included in one or more of the same or different apparatuses.
  • PDCP entity 212 may be included in the same apparatus as RLC entity 214, MAC entity 216, and/or PHY entity 218, such as first apparatus 110, while PDCP entity 222 may be included in the same apparatus as RLC entity 224, MAC entity 226, and PHY entity 228, such as second apparatus 120.
  • PDCP entity 212, RLC entity 214, MAC entity 216, and/or PHY entity 218 may be included in different apparatuses.
  • IP Internet Protocol
  • IP entities 230 and 232 may be in communication with PDCP entities 212 and 232, respectively.
  • IP entities 230 and 232 may transmit one or more IP packets to one or more PDCP entities 212 and 222, which are received by one or more PDCP entities 212 and 222 as PDCP SDUs.
  • One or more PDCP entities 212 and 222 may perform at least one of the following functions: header compression of the PDCP SDU, integrity protection, ciphering based upon a PDCP COUNT value, setting a PDCP sequence number of a PDCP PDU based upon a PDCP COUNT value, and/or incrementing the PDCP COUNT value by one for the next PDCP SDU.
  • One or more PDCP entities 212 and 222 may also send a transmission to one or more lower- level protocol entities, for example, RLC entities 214 and 224, respectively. The transmission sent to the one or more lower-level protocol entities may be one or more PDCP PDUs/RLC SDUs.
  • a lower-level protocol entity such as RLC entities 214 and 224, may perform one or more of segmentation of the RLC SDUs and/or adding headers based upon the mode of operation of the RLC.
  • RLC entities 214 and 224 may operate in one or more of an acknowledged mode and an unacknowledged mode.
  • One or more RLC entities 214 and 224 may transmit one or more RLC PDUs/MAC SDUs to one or more lower-level protocol entities, for example, MAC entities 216 and 226.
  • a lower-level protocol entity such as one or more MAC entities 216 and 226, may perform one or more of padding and adding headers to form one or more MAC PDUs.
  • One or more MAC entities 216 and 226 may transmit one or more MAC PDUs to one or more lower-level protocol entities, such as one or more physical-layer entities 218 and 228.
  • FIG. 3 illustrates another example of a signal flow diagram according to certain embodiments.
  • IP entity 330 may transmit an IP packet to PDCP entity 312, which is received at PDCP entity 312 as a PDCP SDU.
  • step 303 higher-level PDCP entity 312 may transmit the PDCP SDU, associated with a sequence number, within a PDCP PDU to lower- level RLC entity 314.
  • step 305 PDCP entity 312 may transmit an indication for discarding the PDCP PDU to RLC entity 314.
  • RLC entity 314 may transmit a response to PDCP entity 312, in step 307. In some embodiments, the response may confirm the discarding of the PDCP PDU indicated in step 305.
  • step 309 PDCP entity 312 may transmit an instruction to PDCP entity 322 not to wait for reception of the SDU associated with the sequence number.
  • Figure 4 illustrates an example method of a first higher-level protocol entity receiving a response from a lower- level protocol entity, and instructing a second higher- level protocol entity not to wait for reception of a service data unit.
  • the first higher-level protocol entity may correspond to PDCP entity 212 and/or 312
  • the first lower-level protocol entity may correspond to RLC entity 214 and/or 314
  • the second higher-level protocol entity may correspond to PDCP entity 222 and/or 322.
  • the first higher-level protocol entity, the first lower-level protocol entity, and/or the second lower- level protocol entity may be in the same or different apparatuses, such as first apparatus 110 and/or second apparatus 120.
  • the first higher-level protocol entity and first lower-level protocol entity may be in a first apparatus, and/or the second higher-level protocol entity may be in a second apparatus.
  • the first higher-level protocol entity, the first lower-level protocol entity, and the second higher-level protocol entity may be in different apparatuses.
  • the first apparatus and/or the second apparatus may be user equipment, a base station, and/or an eNB.
  • the first higher-level protocol entity may receive an SDU.
  • the SDU may be received from an IP entity, such as IP entity 230 and/or 330.
  • the first higher- level protocol entity may begin a timer.
  • the timer may be a discard timer and/or may be associated with the received SDU.
  • the first higher-level protocol entity may associate a count value with the SDU.
  • the first higher- level protocol entity may perform at least one of the following: header compression of the SDU, integrity protection, ciphering based on the count value, setting a PDCP sequence number (SN) of a PDU carrying the SDU based on the count value, and/or incrementing the count value by one for a possible next SDU.
  • the higher-level protocol entity may transmit the PDU to the first lower-level protocol entity.
  • the first higher-level protocol entity may transmit an indication for discarding the PDU to the first lower-level protocol entity.
  • the first higher-level protocol entity may serve a duplication bearer.
  • the first higher-level protocol entity may send PDUs to two or more lower-level protocol entities, one of which may include the first lower-level protocol entity.
  • one or more of the two or more lower-level protocol entities may be included in the same and/or one or more different apparatuses as the first higher-level protocol entity.
  • one or more discard indications may be transmitted to one, at least one, or each lower-level protocol entity to which the first higher-level protocol entity has transmitted at least one PDU.
  • the first higher-level protocol entity in response to transmitting the indication for discarding the PDU in step 407, may receive a response from the first lower-level protocol entity. In some embodiments, the response may confirm the discarding of the PDU.
  • the first higher-level protocol entity determines whether to send to the second higher-level protocol entity an instruction not to wait for reception of the SDU associated with the count value.
  • the SDU may be associated with a sequence number.
  • the determination in step 411 may be based upon at least one of the following: the type of the first lower-level protocol entity, such as the mode of RLC, and/or the status of the PDU.
  • the determination may be based upon one or more responses received from the one or more lower-level protocol entities, including the first lower-level protocol entity.
  • the first higher-level protocol entity may determine, in some embodiments, not to send an instruction not to wait for reception of the SDU to the second higher-level protocol entity. For example, the first higher- level protocol entity may determine not to send an instruction not to wait for reception of the SDU to a second higher-level protocol entity based upon the delivery being unpreventable. Other reasons for determining not to send an instruction may include failing to receive a response from the first lower- level protocol entity, and/or that the discard timer is longer than a reordering timer operated by the second higher-level protocol entity.
  • the first higher-level protocol entity may determine to send an instruction not to wait for reception of the SDU to the second higher-level protocol entity based upon an inability of the PDU to be received by the first higher-level protocol entity.
  • the PDU may be unable to be received due to a lower-level protocol, such as an LC protocol, operating in an Unacknowledged Mode, and refraining from submitting a final segment of the PDU to a MAC protocol level for transmission.
  • the first higher-level protocol entity may transmit to the second higher-level protocol entity an instruction not to wait for reception of the SDU associated with a sequence number.
  • Figure 5 illustrates another example method of a first lower- level protocol entity transmitting a response to an indication from a first higher-level protocol entity for sending an instruction not to wait for reception of the SDU to a second higher-level protocol entity.
  • the first lower-level protocol entity may correspond to RLC entity 214 and/or 314, the first higher-level protocol entity may correspond to PDCP entity 212 and/or 312, and/or the second higher- level protocol entity may correspond to PDCP entity 222 and/or 322.
  • the first lower- level protocol entity, the first higher-level protocol entity, and/or the second higher-level protocol entity maybe in the same or different apparatuses, such as first apparatus 110 and/or second apparatus 120.
  • the first higher-level protocol entity and first lower-level protocol entity may be in a first apparatus, and/or the second higher-level protocol entity may be in a second apparatus.
  • the first higher-level protocol entity, the first lower-level protocol entity, and the second higher-level protocol entity may be in different apparatuses.
  • the first apparatus and/or the second apparatus may be user equipment, a base station, and/or an eNB.
  • the first lower- level protocol entity may receive an SDU from the first higher-level protocol entity.
  • the first lower-level protocol entity may receive an indication for discarding the RLC SDU from the first higher-level protocol entity.
  • the first lower-level protocol entity may transmit a response to the first higher-level protocol entity, as shown in step 505.
  • the response may be used to determine whether or not the first higher-level protocol entity should send an instruction not to wait for reception of the SDU to a second higher-level protocol entity based upon the delivery being unpreventable.
  • a method may include transmitting, by a first higher-level protocol entity, a service data unit within a packet data unit to a first lower- level protocol entity. The method may also include transmitting, by the first higher-level protocol entity to the first lower-level protocol entity, an indication for discarding the packet data unit. In addition, the method may include receiving, by the first higher-level protocol entity, a response to the indication from the first lower-level protocol entity. Further, based on the response or lack of response, the method may include transmitting, by the first higher-level protocol entity to a second higher-level protocol entity, an instruction not to wait for reception of the service data unit.
  • the first higher- level protocol entity and the first lower- level protocol entity may be in a first apparatus, and the second higher-level protocol entity may be in a second apparatus.
  • the first apparatus and/or the second apparatus may be user equipment, an evolved Node B, or a base station.
  • the first higher-level protocol entity may be in a first apparatus
  • the first lower-level protocol entity may be in a second apparatus
  • the second higher- level protocol entity may be in a third apparatus.
  • the first apparatus, the second apparatus, and/or the third apparatus may be user equipment, an evolved Node B, or a base station.
  • the first lower-level protocol entity may be a radio link control (LC) protocol.
  • LC radio link control
  • the first higher-level protocol entity may be a packet data convergence protocol (PDCP) protocol.
  • PDCP packet data convergence protocol
  • the second higher-level protocol entity may be a packet data convergence protocol (PDCP) protocol.
  • PDCP packet data convergence protocol
  • the response may include an indication indicating whether the second higher-level protocol entity may receive the packet data unit.
  • the indication not to wait for the service data unit includes a sequence number.
  • sequence number is a count value.
  • a method may include receiving, by a first lower-level protocol entity, a service data unit from a first higher-level protocol entity.
  • the method may further include receiving, by the first lower-level protocol entity from the first higher-level protocol entity, an indication for discarding the service data unit.
  • the method may further include, in response to receiving the indication for discarding the service data unit, transmitting, by the first lower-level protocol entity, a response to the first higher-level protocol entity, wherein the response is used to determine whether to send an instruction to a second higher-level protocol entity not to wait for reception of the service data unit.
  • the first higher- level protocol entity and the first lower- level protocol entity are may be in a first apparatus, and the second higher-level protocol entity may be in a second apparatus.
  • the first apparatus and/or the second apparatus may be user equipment, an evolved Node B, or a base station.
  • the first higher-level protocol entity may be in a first apparatus
  • the first lower-level protocol entity may be in a second apparatus
  • the second higher- level protocol entity may be in a third apparatus.
  • the first apparatus, the second apparatus, and/or the third apparatus may be user equipment, an evolved Node B, or a base station.
  • the first lower-level protocol entity may include a radio link control (LC) protocol.
  • LC radio link control
  • the first higher-level protocol entity may include a packet data convergence protocol (PDCP) protocol.
  • PDCP packet data convergence protocol
  • the second higher-level protocol entity may include a packet data convergence protocol (PDCP) protocol.
  • PDCP packet data convergence protocol
  • the response may include an indication indicating whether the second higher-level protocol entity may receive the service data unit.
  • the indication for discarding the service data unit includes a sequence number.
  • sequence number is a count value.
  • an apparatus can include at least one processor and at least one memory and computer program code.
  • the at least one memory and the computer program code can be configured to, with the at least one processor, cause the apparatus at least to perform a method according to the first embodiment and the second embodiment, and any of its variants.
  • an apparatus can include means for performing the method according to the first embodiment and the second embodiment, and any of its variants.
  • a computer program product may encode instructions for performing a process including a method according to the first embodiment and the second embodiment, and any of its variants.
  • a non-transitory computer-readable medium may encode instructions that, when executed in hardware, perform a process including a method according to the first embodiment and the second embodiment, and any of its variants.
  • a computer program code may include instructions for performing a method according to the first embodiment and the second embodiment, and any of its variants.

Landscapes

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

Abstract

Selon certains modes de réalisation, l'invention peut concerner des systèmes de communication, et, par exemple, selon certains modes de réalisation, l'invention peut concerner le rejet basé sur un temporisateur d'unité de données de service (SDU) de protocole de convergence de données par paquets (PDCP). Selon un premier mode de réalisation, un procédé peut consister à transmettre, par une première entité de protocole de niveau supérieur, une unité de données de service dans une unité de données par paquets à une première entité de protocole de niveau inférieur. Le procédé peut également consister à transmettre, par la première entité de protocole de niveau supérieur à la première entité de protocole de niveau inférieur, une indication pour rejeter l'unité de données par paquets. De plus, le procédé peut consister à recevoir, par la première entité de protocole de niveau supérieur, une réponse à l'indication provenant de la première entité de protocole de niveau inférieur. En outre, sur la base de la réponse ou du manque de réponse, le procédé peut consister à transmettre, par la première entité de protocole de niveau supérieur à une seconde entité de protocole de niveau supérieur, une instruction de ne pas attendre la réception de la SDU.
PCT/FI2018/050687 2017-09-28 2018-09-24 Gestion d'unité de données de service WO2019063880A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP18782095.6A EP3688909A1 (fr) 2017-09-28 2018-09-24 Gestion d'unité de données de service

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201762564752P 2017-09-28 2017-09-28
US62/564,752 2017-09-28

Publications (1)

Publication Number Publication Date
WO2019063880A1 true WO2019063880A1 (fr) 2019-04-04

Family

ID=63722417

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/FI2018/050687 WO2019063880A1 (fr) 2017-09-28 2018-09-24 Gestion d'unité de données de service

Country Status (2)

Country Link
EP (1) EP3688909A1 (fr)
WO (1) WO2019063880A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023115473A1 (fr) * 2021-12-23 2023-06-29 Lenovo (Beijing) Limited 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

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2830352A1 (fr) * 2013-07-24 2015-01-28 Panasonic Intellectual Property Corporation of America Mécanisme d'abandon efficace dans un déploiement à petites cellules

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2830352A1 (fr) * 2013-07-24 2015-01-28 Panasonic Intellectual Property Corporation of America Mécanisme d'abandon efficace dans un déploiement à petites cellules

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "PDCP and RLC behaviour for PDCP data duplication", vol. RAN WG2, no. Berlin, Germany; 20170821 - 20170825, 20 August 2017 (2017-08-20), XP051318212, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings_3GPP_SYNC/RAN2/Docs/> [retrieved on 20170820] *
NOKIA NETWORKS: "Further discussion on PDCP discard with split bearers", vol. RAN WG2, no. Beijing, China; 20150824 - 20150828, 23 August 2015 (2015-08-23), XP051003900, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings_3GPP_SYNC/RAN2/Docs/> [retrieved on 20150823] *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023115473A1 (fr) * 2021-12-23 2023-06-29 Lenovo (Beijing) Limited 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

Also Published As

Publication number Publication date
EP3688909A1 (fr) 2020-08-05

Similar Documents

Publication Publication Date Title
KR101597072B1 (ko) 패킷 데이터 컨버전스 프로토콜 데이터 유닛의 처리
EP3353930B1 (fr) Amélioration d&#39;un rapport d&#39;état pdcp
CN110249659B (zh) 服务质量流重新定位
CN109983740B (zh) 数据传输方法
US10334471B2 (en) Lossless bearer reconfiguration from use of longer to shorter sequence number
CN108282292B (zh) 用于处理数据的方法、发送端和接收端
US20080225891A1 (en) Flexible pdu sizes for unacknowledged mode radio link control
CN111294153A (zh) 传输数据的方法和设备
CN110463239B (zh) 数据传输的方法、终端设备和网络设备
US20130250849A1 (en) Method and Apparatus for Efficient Content Delivery in Radio Access Networks
US8073012B2 (en) Method and related apparatus for handling packet discard in a wireless communications system
WO2019063880A1 (fr) Gestion d&#39;unité de données de service
CN106341368A (zh) 一种实现数据处理的方法及装置
US20100080247A1 (en) Reassembly of service data units in communications system
JP2023062123A (ja) 無線通信装置、無線通信方法、及び無線通信システム
CN108200605B (zh) 一种基站的数据传输方法和装置
US20090109951A1 (en) Method and Apparatus for Counting Transmission Times of a PDU
US11395177B2 (en) Sequence numbering on demand for segmentation
WO2018127842A1 (fr) Changement de numéro de séquence de protocole de convergence de données de paquets sans perte
CN111357223B (zh) 一种通信的方法、装置和计算机可读存储介质
CN111835657A (zh) 传输数据的方法和装置
WO2017114551A1 (fr) Formats de pdu ayant des sdu de taille fixe pour des réseaux sans fil
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&#39;une perte de paquet
CN113573357A (zh) 下行数据接收方法、系统、存储介质及终端
WO2022063636A1 (fr) Capacité de données supplémentaire offerte par utilisation de cellules secondaires candidates pour communication sans fil

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2018782095

Country of ref document: EP

Effective date: 20200428