WO2020067960A1 - Transmission d'unités de données de protocole - Google Patents

Transmission d'unités de données de protocole Download PDF

Info

Publication number
WO2020067960A1
WO2020067960A1 PCT/SE2019/050876 SE2019050876W WO2020067960A1 WO 2020067960 A1 WO2020067960 A1 WO 2020067960A1 SE 2019050876 W SE2019050876 W SE 2019050876W WO 2020067960 A1 WO2020067960 A1 WO 2020067960A1
Authority
WO
WIPO (PCT)
Prior art keywords
transmission
pdcp
duplicates
pdcp pdu
entity
Prior art date
Application number
PCT/SE2019/050876
Other languages
English (en)
Inventor
Torsten DUDDA
Jose Luis Pradas
Henrik Enbuske
Nianshan SHI
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
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 Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Publication of WO2020067960A1 publication Critical patent/WO2020067960A1/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/189—Transmission or retransmission of more than one copy of a message
    • 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/08—Arrangements for detecting or preventing errors in the information received by repeating transmission, e.g. Verdan system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/02—Data link layer protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L2001/0092—Error control systems characterised by the topology of the transmission link
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L2001/0092—Error control systems characterised by the topology of the transmission link
    • H04L2001/0096—Channel splitting in point-to-point links

Definitions

  • Embodiments presented herein relate to a method, a PDCP transmission entity, a computer program, and a computer program product for transmission of PDUs.
  • communications networks there may be a challenge to obtain good performance and capacity for a given communications protocol, its parameters and the physical environment in which the communications network is deployed.
  • a dual connectivity (DC) or multi-connectivity protocol architecture of a split bearer is specified for the air interface (denoted New Radio, or NR) of the fifth generation mobile networks.
  • the DC protocol architecture builds on the protocol architecture used for the air interface of the fourth generation mobile networks for the DC split bearer.
  • the terminal device (often denoted User Equipment, or UE) is operatively connected to two distinct network nodes in the radio network.
  • the terminal device maintains a packet data convergence protocol (PDCP) entity for the split bearer connected to multiple radio link control (RLC) and medium access control (MAC) entities, as well as physical layer entities (PHY). These are each associated to a cell group; the master cell group and secondary cell group
  • Transmission via the master cell group goes to the Master gNB (eNB in Long Term Evolution (LTE) terminology), MgNB; transmission via the secondary cell group goes to the Secondary gNB(eNB), SgNB.
  • MgNB and SgNB maintain their own RLC and MAC entities associated to this single split bearer.
  • a further node or function denoted packet processing function (PPF), which may be separate, or collocated with MgNB or SgNB, also denoted MN or SN, terminates the PDCP protocol on the network side.
  • PPF packet processing function
  • the centralized unit terminating PDCP may also be called centralized unit (CU) while the remaining nodes
  • DUs distributed units
  • PDUs protocol data units
  • PDCP may be routed (or“split”) via either lower layer or duplicated via both as further described below.
  • RLC entity associated with master cell group or RLC entity associated with secondary cell group may also be denoted as transmission paths.
  • CA carrier aggregation
  • the terminal device is operatively connected to one network node in the radio network via at least two (e.g. multiple) carriers. That is, at least two physical layers (PHY) are maintained.
  • the protocol stack consists of one MAC, one RLC, and one PDCP entity.
  • data units to be transmitted may be routed via both carriers.
  • An exception is packet duplication, where the protocol stack entails two RLC logical channels, to which the PDCP entity routes duplicates, and where transmission of each RLC entity is done one a separate carrier by the MAC level.
  • routing packets via the different RLC entities associated with the same MAC entity (cell group) may be denoted as different transmission paths.
  • Duplication at PDCP therefore generally consists of sending the same PDCP PDUs twice; once on the original RLC entity and a second time on the additional RLC entity.
  • packet duplication is therefore used to increase reliability and reduces latency and is especially beneficial for ultra-reliable low latency (URLLC) services.
  • URLLC ultra-reliable low latency
  • duplication can be activated and de-activated per DRB by means of a MAC control element (CE).
  • CE MAC control element
  • An object of embodiments herein is to provide efficient utilization of multiple available transmission paths for PDCP PDU transmission.
  • a method for transmission of PDUs is performed by a PDCP transmission entity.
  • the PDCP transmission entity has P>2 available transmission paths configured for PDCP PDU transmission.
  • the method comprises transmitting, in a first transmission, duplicates of a PDCP PDU, wherein the first transmission is conditionally limited to only on a proper subset consisting of M ⁇ P of all the available transmission paths.
  • the first transmission is initiated for P duplicates of the PDCP PDU but the first transmission is conditionally limited to transmitting only the first M ⁇ P duplicates of the PDCP PDU, such that the last P-M duplicates of the PDCP PDU are discarded from the first transmission.
  • a PDCP transmission entity for transmission of PDUs.
  • the PDCP transmission entity has P>2 available transmission paths configured for PDCP PDU transmission.
  • the PDCP transmission entity comprises processing circuitry.
  • the processing circuitry is configured to cause the PDCP transmission entity to transmit, in a first transmission, duplicates of a PDCP PDU, wherein the first transmission is conditionally limited to only on a proper subset consisting of M ⁇ P of all the available transmission paths.
  • the transmission is initiated for P duplicates of the PDCP PDU but the first transmission is conditionally limited to transmitting only the first M ⁇ P duplicates of the PDCP PDU, such that the last P-M duplicates of the PDCP PDU are discarded from the first transmission.
  • a PDCP transmission entity for transmission of PDUs.
  • the PDCP transmission entity has P>2 available transmission paths configured for PDCP PDU transmission.
  • the PDCP transmission entity comprises a transmit module configured to transmit, in a first transmission, duplicates of a PDCP PDU, wherein the first transmission is conditionally limited to only on a proper subset consisting of M ⁇ P of all the available transmission paths.
  • a computer program for transmission of PDUs the computer program comprising computer program code which, when run on a PDCP transmission entity having P>2 available transmission paths configured for PDCP PDU transmission, causes the PDCP transmission entity to perform a method according to the first aspect.
  • the first transmission is initiated for P duplicates of the PDCP PDU but the first transmission is conditionally limited to transmitting only the first M ⁇ P duplicates of the PDCP PDU, such that the last P-M duplicates of the PDCP PDU are discarded from the first transmission.
  • a computer program product comprising a computer program according to the fourth aspect and a computer readable storage medium on which the computer program is stored.
  • the computer readable storage medium could be a non-transitory computer readable storage medium.
  • this provides similar reliability as if duplicating over more than two transmission paths, but does not result in the resource expense of using all transmission paths for duplication in an architecture utilizing more than two transmission paths.
  • Fig. l is a schematic diagram illustrating a communications network according to embodiments.
  • Fig. 2 is a flowchart of methods according to embodiments
  • Fig. 3 schematically illustrates a protocol architecture according to an embodiment
  • Fig. 4 is a schematic diagram showing functional units of a PDCP transmission entity according to an embodiment
  • Fig. 5 is a schematic diagram showing functional modules of a PDCP transmission entity according to an embodiment.
  • Fig. 6 shows one example of a computer program product comprising computer readable storage medium according to an embodiment.
  • Fig. l is a schematic diagram illustrating a communications network loo where embodiments presented herein can be applied.
  • the communications network too could be a third generation (3G) telecommunications network, a fourth generation (4G) telecommunications network, or a fifth (5G) telecommunications network and support any 3GPP telecommunications standard, where applicable.
  • the communications network 100 comprises two network nodes 150a, 150b configured to, via respective transmission and reception points 140a, 140b, provide network access to at least one terminal device 160 in a radio access network 110, thus enabling the terminal device 160 to communicate over transmission paths 170a, 170b, 170c.
  • transmission paths 170a, 170b, 170c there might be a plurality of transmission paths 170a, 170b, 170c.
  • the terminal device 160 might have a connection over a plurality of transmission paths to a single one of the network nodes 150a, 150b by means of carrier aggregation, or have a connection over a plurality of transmission paths to two or more of the network nodes 150a, 150b by means of dual connectivity.
  • Examples of network nodes 150a, 150b are radio access network nodes, radio base stations, base transceiver stations, Node Bs, evolved Node Bs (eNBs), g Node Bs (gNBs), access points, and access nodes, and backhaul nodes.
  • Examples of terminal devices 160 are wireless devices, mobile stations, mobile phones, handsets, wireless local loop phones, user equipment (UE), smartphones, laptop computers, tablet computers, network equipped sensors, network equipped vehicles, and so-called Internet of Things devices.
  • the radio access network 110 is operatively connected to a core network 120.
  • the core network 120 is in turn operatively connected to a service network 130, such as the Internet.
  • the terminal device 160 is thereby enabled to, via the network nodes 150a, 150b, access services of, and exchange data with, the service network 130.
  • the terminal device 160 and the network nodes 170a, 170b are configured for communication of PDCP PDUs over the transmission paths 170a, 170b, 170c.
  • Transmission of the PDCP PDUs is managed by PDCP transmission entities 200.
  • the PDCP transmission entity 200 might thus be part of, or hosted by, the terminal device 160 and/or a network node 150a, 150b.
  • the PDCP transmission entity 200 might be part of, or hosted by a CU or PPF.
  • the CU or PPF might be located in the radio access network 110 or the core network 120.
  • reception of the PDCP PDUs might be managed by PDCP PDU reception entities (not shown).
  • the PDCP PDU reception entities might be located as the PDCP transmission entities 200.
  • the PDCP transmission entity 200 keeps transmitting PDCP PDUs until it gets discarding instruction from the node or device hosting the PDCP transmission entity 200. This could potentially lead to further resource inefficiencies by redundant duplicates of one and the same PDCP PDU being transmitted.
  • the embodiments disclosed herein therefore relate to mechanisms for efficient transmission of PDUs.
  • a PDCP transmission entity 200 a method performed by the PDCP transmission entity 200, a computer program product comprising code, for example in the form of a computer program, that when run on a PDCP transmission entity 200, causes the PDCP transmission entity 200 to perform the method.
  • the methods are advantageously provided as computer programs 620.
  • Some of the embodiments relates to mechanisms for PDCP duplication in which more than two (such as multiple) transmission paths 170a, 170b, 170c (e.g. carriers, or bearers, or logic RLC channels, when using CA and/or DC) are available but where the PDCP transmitter entity 200 limits the maximum combined count of
  • Fig. 2 is a flowchart illustrating embodiments of methods for transmission of PDUs.
  • the methods are performed by the PDCP transmission entity 200.
  • the number of available configured transmission paths 170a, 170b, 170c is denoted P.
  • the PDCP transmission entity 200 has P>2 available transmission paths 170a, 170b, 170c configured for PDCP PDU transmission.
  • the maximum duplicate count of the PDCP PDU (including the original) is denoted M.
  • the PDCP transmission entity 200 transmits only a proper subset of PDCP PDU duplicates over the air.
  • the PDCP transmitting entity 200 transmits M ⁇ P duplicates of the same PDCP PDU towards lower layers (such as RLC, MAC, PHY).
  • the PDCP, transmission entity 200 transmits, in a first transmission, duplicates of a PDCP PDU.
  • the first transmission is conditionally limited to only on a proper subset consisting of M ⁇ P of all the available transmission paths 170a, 170b, 170c.
  • the first transmission is initiated for P duplicates of the PDCP PDU but the first transmission is conditionally limited to transmitting only the first M ⁇ P duplicates of the PDCP PDU, such that the last P-M duplicates of the PDCP PDU are discarded from the first transmission.
  • the PDCP transmission entity 200 refrains from transmitting more duplicates of the PDCP PDU when transmission of M duplicates of the PDCP PDU have been initiated (e.g. as an initiation of a PDCP PDU transmission in a hybrid automatic repeat request (HARQ) process or processes). That is, in an embodiment, transmission of M duplicates of the PDCP PDU is initiated in at least one HARQ process.
  • HARQ hybrid automatic repeat request
  • each PDCP PDU can be identified by a sequence number and hence all duplicates of one and the same PDCP PDU will have the same sequence number.
  • the transmission paths 170a, 170b, 170c could be carriers, or bearers, or logic channels, in a dual connectivity and/or carrier aggregation architecture.
  • the transmission paths 170a, 170b, 170c could be carriers, or bearers, or logic channels, in a dual connectivity and/or carrier aggregation architecture.
  • at least two of all the available transmission paths 170a, 170b, 170c are configured for dual connectivity of the PDCP transmission entity, and/or at least two of all the available transmission paths 170a, 170b, 170c are configured for carrier aggregation for the PDCP transmission entity.
  • each respective transmission path could have its own RLC entity towards which the duplicates of the PDCP PDU are transmitted.
  • the PDCP transmitting entity 200 might discard further duplicate transmissions of the same PDCP PDU. That is, according to an embodiment the first transmission is conditionally limited to M duplicates of the PDCP PDU upon the PDCP transmission entity obtaining an indication that one duplication of the PDCP PDU has been successfully transmitted.
  • the discarding may be indicated from the PDCP transmission entity 200 to lower layers, e.g. to an RLC entity where remaining duplicates of the PDCP PDU might be present.
  • the discarding is indicated via a midhaul channel, such as via interface Xn.
  • the discarding is indicated via the midhaul channel (see Fig. 3), e.g. the Xn interface, in case of the PDCP
  • transmitter entity 200 being hosted by a network node.
  • the PDCP transmitter entity 200 indicates for which transmission path the duplicates of the PDCP PDU are to be discarded from the first transmission.
  • the node hosting the PDCP transmitter entity 200 might indicate for which transmission path specifically the duplicate shall be discarded, e.g. by indicating a logical channel identifier.
  • Lower layers e.g. PHY, HARQ, MAC, RLC may indicate to the PDCP transmission entity 200 the start of such a transmission.
  • the PDCP transmission entity 200 thereupon may refrain from submitting further duplicates of the PDCP PDU and may discard further transmission processes of those duplicates.
  • the last P-M duplicates of the PDCP PDU are discarded at RLC level.
  • the network node hosting those lower layers might indicate to the PDCP transmission entity 200 when a PDCP PDU duplicate has been transmitted or for which transmission has been initiated.
  • this network node might, according to an embodiment, indicate to the PDCP transmission entity 200 the number of duplicates (i.e., how many duplicates) that have been transmitted.
  • This signaling may be implemented on an Xn interface over a midhaul channel. That is, according to an embodiment, the indication of how many duplicates that have been transmitted is indicated via a midhaul channel, such as via the Xn interface.
  • the value of M is dependent on how many duplicates of the PDCP PDU are successfully transmitted.
  • the PDCP transmission entity 200 might then increase or decrease (or keep unchanged) the value of M. There could be different conditions for increasing or decreasing (or keeping unchanged) the value of M.
  • the value of M is increased when the number of successfully
  • the transmitted duplicates of the PDCP PDU is below a first threshold value.
  • the value of M is decreased when the number of successfully
  • the transmitted duplicates of the PDCP PDU is above a second threshold value.
  • the second threshold value is equal to or greater than the first threshold value.
  • the PDCP transmission entity 200 is configured to only send M duplicates as default.
  • the first transmission is conditionally limited by being initiated for only the M duplicates of the PDCP PDU.
  • the PDCP transmission entity 200 then only uses more than M (but at most P) transmission paths 170a, 170b, 170c under certain conditions.
  • the PDCP transmission entity 200 is configured to perform (optional) step S104:
  • the PDCP transmission entity 200 transmits, in a second transmission, further duplicates of the PDCP PDU on available transmission paths 170a, 170b, 170c outside the proper subset M ⁇ P of all the available transmission paths 170a, 170b, 170c.
  • One condition is an indication from a scheduling entity. That is, the scheduling entity determines that it is useful for a certain time and/or for certain PDUs to activate more than M transmissions.
  • the indication may be realized by a MAC control element (CE) or PDCP control signaling, stating the value of M which should be used from now on until the next indication stating another value of M is received.
  • CE MAC control element
  • PDCP control signaling stating the value of M which should be used from now on until the next indication stating another value of M is received.
  • One condition is that a lower layer indicates insufficient robustness or reliability level for their respective transmission path. This may be estimated or measured by e.g.
  • RLC RTT RLC RTT
  • HARQ block error probability HARQ block error probability
  • throughput Increasing M may then be done depending on these metrics exceeding certain threshold levels.
  • a network node hosting lower layers indicates unsuccessfully transmitted PDUs.
  • the indication might be a received HARQ NACK or RLC status report that indicates NACK for a transmitted duplicate or other indication that some of sent duplicates were not successfully transmitted.
  • the further duplicates of the PDCP PDU are transmitted upon the PDCP transmission entity obtaining: a request from a scheduling entity to transmit further duplicates of the PDCP PDU, or an indication of insufficient robustness for at least one of the transmission paths 170a, 170b, 170c used for the first transmission, or an indication of unsuccessful transmission of at least one of the duplicates of the PDCP PDU transmitted in the first transmission. Further, a respective one of the duplicates of the PDCP PDU in the second
  • transmission might be transmitted on a respective available transmission path outside the proper subset M ⁇ P of all the available transmission paths 170a, 170b, 170c.
  • the PDCP transmission entity 200 always utilizes an indicated transmission path for the transmission of a duplicate of the PDCP PDU, i.e. not stopping/discarding transmission on this transmission path.
  • This transmission path could be a so-called primary path.
  • the primary path may be (pre-) configured by the network.
  • the primary path (or an order of priority for the transmission paths 170a, 170b, 170c) may be chosen e.g. according to estimated/measured RLC RTT, HARQ block error probability or throughput.
  • one particular of all the available transmission paths 170a, 170b, 170c is a primary transmission path and always is included in the subset M ⁇ P of all the available transmission paths 170a, 170b, 170c.
  • the value of M may be configured for the PDCP transmitting entity 200 by means of RRC signaling, or a MAC CE, or PDCP control signaling.
  • the value of M is configured by RRC signalling, or MAC signalling, or PDCP control signalling.
  • the PDCP transmission entity 200 is informed by the node or device hosting the PDCP transmission entity 200 of a window from the latest received PDCP PDU at the corresponding PDCP reception entity, so that the PDCP transmission entity 200 may discard any old PDCP PDUs outside the window.
  • the node or device hosting the PDCP transmission entity 200 may alternatively indicate a timer value, so any PDCP PDUs at the RLC entity are automatically discarded upon expiration of the timer value.
  • Such indication may be sent by the node hosting the PDCP transmission entity 200 in the GTP-U header extension (where GTP is short for GPRS Tunneling Protocol, where GPRS is short for General Packet Radio Service, and where GTP-U is used for carrying user data within the GPRS core network and between the radio access network and the core network), together with the downlink data.
  • GTP-U header extension where GTP is short for GPRS Tunneling Protocol, where GPRS is short for General Packet Radio Service, and where GTP-U is used for carrying user data within the GPRS core network and between the radio access network and the core network
  • Fig. 3 shows a protocol architecture 300 when using combined DC and CA for multiple transmission paths 170a, 170b, 170c (denoted Carrier 1, Carrier 2, Carrier 3 in Fig. 3).
  • the protocol architecture 300 a configuration for PDCP duplication is assumed.
  • the PDCP transmission entity 200 of a radio bearer, or carrier is associated with three RLC entities, such as bearers or carriers or logical channels. Those RLC entities are associated with transmission restrictions and/or are associated with different carriers.
  • the network node 150a (denoted DU2/SeNB/SgNB in Fig. 3) utilizes CA for communication with the terminal device 160 (denoted UE in Fig.
  • the network node 150a in combination with the network node 150b utilize DC for communication with the terminal device 160.
  • the terminal device 160 utilizes a combination of CA and DC for its communication of PDCP PDUs.
  • the terminal device 160 has one PDCP transmitter entity 200 whilst the network nodes 150a, 150b share one central PDCP transmitter entity 200 hosted by a CU/PPF 310.
  • each of the network nodes 150a, 150b and the terminal device 160 run at least one instance of an RLC entity 320, a MAC entity 330 and a PHY entity 340.
  • P>2 transmission paths 170a, 170b, 170c e.g. carriers, bearers, logical channels
  • P>2 transmission paths 170a, 170b, 170c e.g. carriers, bearers, logical channels
  • duplicates of the PDCP PDU are transmitted over a subset M ⁇ P of the transmission paths 170a, 170b, 170c.
  • the transmission of the duplicates of the PDCP PDU is conditionally limited by transmission being initiated for P duplicates, but where the transmission is limited to transmission only of the first M ⁇ P duplicates. Transmission of the remaining possible duplicate transmissions is discarded. This is an alternative when the PDCP transmission entity 200 obtains an indication that one duplicate has been successfully transmitted, or alternatively, that M duplicates just have been
  • the transmission of the duplicates of the PDCP PDU is conditionally limited by transmission being initiated for M duplicates only, but where the transmission is extended to transmission of more than M (up to P) duplicates when the PDCP transmission entity 200 obtains an indication of unsuccessful/late transmission.
  • Fig. 4 schematically illustrates, in terms of a number of functional units, the components of a PDCP transmission entity 200 according to an embodiment.
  • Processing circuitry 210 is provided using any combination of one or more of a suitable central processing unit (CPU), multiprocessor, microcontroller, digital signal processor (DSP), etc., capable of executing software instructions stored in a computer program product 610 (as in Fig. 6), e.g. in the form of a storage medium 230.
  • the processing circuitry 210 may further be provided as at least one application specific integrated circuit (ASIC), or field programmable gate array (FPGA).
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • processing circuitry 210 is configured to cause the PDCP
  • the storage medium 230 may store the set of operations
  • the processing circuitry 210 may be configured to retrieve the set of operations from the storage medium 230 to cause the PDCP transmission entity 200 to perform the set of operations.
  • the set of operations maybe provided as a set of executable instructions.
  • the processing circuitry 210 is thereby arranged to execute methods as herein disclosed.
  • the storage medium 230 may also comprise persistent storage, which, for example, can be any single one or combination of magnetic memory, optical memory, solid state memory or even remotely mounted memory.
  • the PDCP transmission entity 200 may further comprise a communications interface 220 at least configured for communications with other entities, functions, nodes, and devices. As such the communications interface 220 may comprise one or more transmitters and receivers, comprising analogue and digital components.
  • the processing circuitry 210 controls the general operation of the PDCP transmission entity 200 e.g. by sending data and control signals to the communications interface 220 and the storage medium 230, by receiving data and reports from the communications interface 220, and by retrieving data and instructions from the storage medium 230.
  • Other components, as well as the related functionality, of the PDCP transmission entity 200 are omitted in order not to obscure the concepts presented herein.
  • Fig. 5 schematically illustrates, in terms of a number of functional modules, the components of a PDCP transmission entity 200 according to an embodiment.
  • the PDCP transmission entity 200 of Fig. 5 comprises a transmit module 210a configured to perform step S102.
  • the PDCP transmission entity 200 of Fig. 5 may further comprise a number of optional functional modules, such as a transmit module 210b configured to perform step S104.
  • each functional module 2ioa-2iob may in one embodiment be implemented only in hardware and in another
  • modules correspond to parts of a computer program, they do not need to be separate modules therein, but the way in which they are implemented in software is dependent on the programming language used.
  • one or more or all functional modules 2ioa-2iob maybe implemented by the processing circuitry 210, possibly in cooperation with the communications interface 220 and/or the storage medium 230.
  • the processing circuitry 210 may thus be configured to from the storage medium 230 fetch instructions as provided by a functional module 2ioa-2iob and to execute these instructions, thereby performing any steps as disclosed herein.
  • the PDCP transmission entity 200 may be provided as a standalone device or as a part of at least one further device. Examples of devices which might host the PDCP transmission entity 200 have been given above.
  • the PDCP transmission entity 200 may be provided in a node of the radio access network or in a node of the core network or in the terminal device.
  • functionality of the PDCP transmission entity 200 may be distributed between at least two devices, or nodes. These at least two nodes, or devices, may either be part of the same network part (such as the radio access network or the core network) or may be spread between at least two such network parts.
  • instructions that are required to be performed in real time may be performed in a device, or node, operatively closer to the cell than instructions that are not required to be performed in real time.
  • a first portion of the instructions performed by the PDCP transmission entity 200 may be executed in a first device, and a second portion of the of the instructions performed by the PDCP transmission entity 200 may be executed in a second device; the herein disclosed embodiments are not limited to any particular number of devices on which the instructions performed by the PDCP transmission entity 200 may be executed.
  • the methods according to the herein disclosed embodiments are suitable to be performed by a PDCP transmission entity 200 residing in a cloud computational environment. Therefore, although a single processing circuitry 210 is illustrated in Fig. 4 the processing circuitry 210 may be distributed among a plurality of devices, or nodes. The same applies to the functional modules 2ioa-2iob of Fig. 5 and the computer program 620 of Fig. 6 (see below).
  • Fig. 6 shows one example of a computer program product 610 comprising computer readable storage medium 630.
  • a computer program 620 can be stored, which computer program 620 can cause the processing circuitry 210 and thereto operatively coupled entities and devices, such as the communications interface 220 and the storage medium 230, to execute methods according to embodiments described herein.
  • the computer program 620 and/or computer program product 610 may thus provide means for performing any steps as herein disclosed.
  • the computer program product 610 is illustrated as an optical disc, such as a CD (compact disc) or a DVD (digital versatile disc) or a Blu-Ray disc.
  • the computer program product 610 could also be embodied as a memory, such as a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), or an electrically erasable
  • EEPROM programmable read-only memory
  • EEPROM programmable read-only memory
  • USB Universal Serial Bus
  • Flash memory such as a compact Flash memory.
  • the computer program 620 is here schematically shown as a track on the depicted optical disk, the computer program 620 can be stored in any way which is suitable for the computer program product 610.

Landscapes

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

Abstract

L'invention concerne des mécanismes de transmission d'unités de données de protocole (PDU). Un procédé est mis en œuvre par une entité de transmission de protocole de convergence de données par paquets (PDCP). L'entité de transmission PDCP comporte P>2 voies de transmission disponibles configurées pour une transmission de PDU de PDCP. Le procédé consiste à transmettre, dans une première transmission, des copies d'une PDU de PDCP. La première transmission est limitée de manière conditionnelle uniquement à un sous-ensemble approprié constitué de M<P de toutes les voies de transmission disponibles. La première transmission est lancée pour P copies de la PDU de PDCP sauf lorsque la première transmission est limitée de manière conditionnelle pour ne transmettre que les premières M<P copies de la PDU de PDCP, de telle sorte que les dernières P-M copies de la PDU de PDCP sont supprimées de la première transmission. La première transmission est lancée pour P copies de la PDU de PDCP, mais la première transmission est limitée de manière conditionnelle pour ne transmettre que les premières M<P copies de la PDU de PDCP, de telle sorte que les dernières P-M copies de la PDU de PDCP sont supprimées de la première transmission.
PCT/SE2019/050876 2018-09-27 2019-09-17 Transmission d'unités de données de protocole WO2020067960A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201862737201P 2018-09-27 2018-09-27
US62/737,201 2018-09-27

Publications (1)

Publication Number Publication Date
WO2020067960A1 true WO2020067960A1 (fr) 2020-04-02

Family

ID=68063007

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2019/050876 WO2020067960A1 (fr) 2018-09-27 2019-09-17 Transmission d'unités de données de protocole

Country Status (1)

Country Link
WO (1) WO2020067960A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023193568A1 (fr) * 2022-04-04 2023-10-12 Telefonaktiebolaget Lm Ericsson (Publ) Procédé et appareil de gestion d'une duplication pdcp

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018028391A1 (fr) * 2016-08-11 2018-02-15 华为技术有限公司 Procédé et appareil destinés à réaliser un traitement de retransmission
WO2018121347A1 (fr) * 2016-12-30 2018-07-05 夏普株式会社 Procédé de rapport de capacité de transmission à connexions multiples, procédé de configuration de modes de transmission à connexions multiples, procédé de prévention d'une retransmission de données, ue et station de base
WO2018143600A1 (fr) * 2017-02-02 2018-08-09 Lg Electronics Inc. Procédé et dispositif de transmission d'unité de données
WO2018167358A1 (fr) * 2017-03-13 2018-09-20 Nokia Technologies Oy Duplication et opération rlc dans une nouvelle technologie d'accès radio
US20180270718A1 (en) * 2016-11-04 2018-09-20 Telefonaktiebolaget Lm Ericsson (Publ) Enabling Efficient Handling of Redundant Packet Copies in a Wireless Communication System

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018028391A1 (fr) * 2016-08-11 2018-02-15 华为技术有限公司 Procédé et appareil destinés à réaliser un traitement de retransmission
EP3468083A1 (fr) * 2016-08-11 2019-04-10 Huawei Technologies Co., Ltd. Procédé et appareil destinés à réaliser un traitement de retransmission
US20180270718A1 (en) * 2016-11-04 2018-09-20 Telefonaktiebolaget Lm Ericsson (Publ) Enabling Efficient Handling of Redundant Packet Copies in a Wireless Communication System
WO2018121347A1 (fr) * 2016-12-30 2018-07-05 夏普株式会社 Procédé de rapport de capacité de transmission à connexions multiples, procédé de configuration de modes de transmission à connexions multiples, procédé de prévention d'une retransmission de données, ue et station de base
EP3565367A1 (fr) * 2016-12-30 2019-11-06 Sharp Kabushiki Kaisha Procédé de rapport de capacité de transmission à connexions multiples, procédé de configuration de modes de transmission à connexions multiples, procédé de prévention d'une retransmission de données, ue et station de base
WO2018143600A1 (fr) * 2017-02-02 2018-08-09 Lg Electronics Inc. Procédé et dispositif de transmission d'unité de données
WO2018167358A1 (fr) * 2017-03-13 2018-09-20 Nokia Technologies Oy Duplication et opération rlc dans une nouvelle technologie d'accès radio

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023193568A1 (fr) * 2022-04-04 2023-10-12 Telefonaktiebolaget Lm Ericsson (Publ) Procédé et appareil de gestion d'une duplication pdcp

Similar Documents

Publication Publication Date Title
CN109075919B (zh) 拆分承载双/多连接重传分集
US9622132B2 (en) Switching between cellular and license-exempt (shared) bands
US9848435B2 (en) Systems and methods to enhance radio link performance in a multi-carrier environment
CN112534897A (zh) 通信系统、通信终端及基站
US20180262302A1 (en) Wireless device, a network node and methods therein for harq feedback prioritization
KR102566795B1 (ko) 데이터 송신을 위한 방법, 디바이스, 및 시스템
CN110741722A (zh) 用于多连接通信中的分组复制的控制机制
CN110214432B (zh) 通信网络中载波的激活或去活的方法和节点
US10142253B2 (en) Method for efficient reliable transmission
US10812224B2 (en) NR user plane signaling controlled triggering of PDCP duplication
TW201933923A (zh) 附加上行鏈路故障處理
WO2017220855A1 (fr) Procédé et appareil pour réaliser une duplication de paquets dans un scénario à connectivité multiple
EP3484081B1 (fr) Procédé et dispositif de retransmission de données
CN112423330B (zh) 一种通信方法及装置
JP6397059B2 (ja) ユーザ装置及び基地局
JP6685295B2 (ja) 基地局
US20210226733A1 (en) Communication apparatus, wireless communication system, and wireless communication method
WO2020067960A1 (fr) Transmission d&#39;unités de données de protocole
US20230199749A1 (en) Configured grant enhancements in unlicensed band
US20240188111A1 (en) Duplicate Transmission of Protocol Data Units
EP2827676A1 (fr) Dispositif sans fil, noeud de réseau radio, procédés associés, programme informatique et support de stockage lisible par ordinateur
TW202428053A (zh) 通信方法及裝置
WO2017128699A1 (fr) Procédé et appareil de traitement de données
CN118283715A (zh) 一种通信方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19773961

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19773961

Country of ref document: EP

Kind code of ref document: A1