WO2020224781A1 - Attribution de données dans une communication cellulaire - Google Patents

Attribution de données dans une communication cellulaire Download PDF

Info

Publication number
WO2020224781A1
WO2020224781A1 PCT/EP2019/061886 EP2019061886W WO2020224781A1 WO 2020224781 A1 WO2020224781 A1 WO 2020224781A1 EP 2019061886 W EP2019061886 W EP 2019061886W WO 2020224781 A1 WO2020224781 A1 WO 2020224781A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
protocol
transport block
packet
data units
Prior art date
Application number
PCT/EP2019/061886
Other languages
English (en)
Inventor
Kalle Petteri Kela
Daniela Laselva
Jani Matti Johannes Moilanen
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 PCT/EP2019/061886 priority Critical patent/WO2020224781A1/fr
Publication of WO2020224781A1 publication Critical patent/WO2020224781A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/321—Interlayer communication protocols or service data unit [SDU] definitions; Interfaces between layers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
    • H04W28/065—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information using assembly or disassembly of packets
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/40—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection
    • 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

Definitions

  • the present application generally relates to the field of wireless communications.
  • the present application relates to allocation of data into packets and transmission resources.
  • PDU packet data units
  • OSI Open Systems Interconnection
  • a receiver decapsulates received packets and forwards payload data of the decapsulated packet to upper layers.
  • An example embodiment of an apparatus may be configured to receive, at a first protocol layer, a plurality of protocol data units for transmission, wherein the plurality of protocol data units comprises data from at least a first and a second data packet of a second protocol layer; in response to determining that the plurality of protocol data units comprises data from the first and the second data packets of the second protocol layer: fill at least one first transport block with protocol data units including data from the first data packet and restrict filling the at least one first transport block with protocol data units including data from the second data packet; and fill at least one second transport block with protocol data units including data from the second data packet.
  • An example embodiment of an apparatus may be configured to: determine to restrict filling at least one first transport block with a plurality of protocol data units at a first protocol layer when the plurality of protocol data units comprises data from a first and a second data packet of a second protocol layer; and transmit an indication to restrict filling the at least one first transport block with the plurality of protocol data units.
  • An example embodiment of a method comprises receiving, at a first protocol layer, a plurality of protocol data units for transmission, wherein the plurality of protocol data units comprises data from at least a first and a second data packet of a second protocol layer; in response to determining that the plurality of protocol data units comprises data from the first and the second data packets of the second protocol layer: filling at least one first transport block with protocol data units including data from the first data packet and restrict filling the at least one first transport block with protocol data units including data from the second data packet; and filling at least one second transport block with protocol data units including data from the second data packet.
  • An example embodiment of a method comprises determining to restrict filling at least one first transport block with a plurality of protocol data units at a first protocol layer when the plurality of protocol data units comprises data from a first and a second data packet of a second protocol layer; and transmitting an indication to restrict filling the at least one first transport block with the plurality of protocol data units.
  • An example embodiment of an apparatus comprises means for performing at least the following: receiving, at a first protocol layer, a plurality of protocol data units for transmission, wherein the plurality of protocol data units comprises data from at least a first and a second data packet of a second protocol layer, in response to determining that the plurality of protocol data units comprises data from the first and the second data packets of the second protocol layer: filling at least one first transport block with protocol data units including data from the first data packet and restrict filling the at least one first transport block with protocol data units including data from the second data packet; and filling at least one second transport block with protocol data units including data from the second data packet.
  • An example embodiment of an apparatus comprises means for performing at least the following: determining to restrict filling at least one first transport block with a plurality of protocol data units at a first protocol layer when the plurality of protocol data units comprises data from a first and a second data packet of a second protocol layer; and transmitting an indication to restrict filling the at least one first transport block with the plurality of protocol data units.
  • An example embodiment of a computer program comprises instructions for causing an apparatus to perform at least the following: receiving, at a first protocol layer, a plurality of protocol data units for transmission, wherein the plurality of protocol data units comprises data from at least a first and a second data packet of a second protocol layer, in response to determining that the plurality of protocol data units comprises data from the first and the second data packets of the second protocol layer: filling at least one first transport block with protocol data units including data from the first data packet and restrict filling the at least one first transport block with protocol data units including data from the second data packet; and filling at least one second transport block with protocol data units including data from the second data packet .
  • An example embodiment of a computer program comprises instructions for causing an apparatus to perform at least the following: determining to restrict filling at least one first transport block with a plurality of protocol data units at a first protocol layer when the plurality of protocol data units comprises data from a first and a second data packet of a second protocol layer; and transmitting an indication to restrict filling the at least one first transport block with the plurality of protocol data units.
  • FIG. 1 illustrates an example embodiment of a network comprising network nodes and user nodes
  • FIG. 2 illustrates an example embodiment of an apparatus, for example a network node or a user node;
  • FIG. 3 illustrates an example embodiment of a data flow through protocol layers with segmentation and concatenation.
  • FIG. 4 illustrates an example embodiment of a data flow through protocol layers with a concatenation restriction .
  • FIG. 5 illustrates an example embodiment of a data flow through protocol layers when filling data packets with other data.
  • FIG. 6 illustrates a flow chart of an example of packets or segment allocation, according to an example embodiment.
  • FIG. 7 illustrates an example embodiment of a method for filling protocol data units in transport blocks .
  • FIG. 8 illustrates an example embodiment of a method for providing instructions for restricting filling of protocol data units to transport blocks.
  • FIG. 9 illustrates an example of simulation results for example embodiments compared to a reference system.
  • a first protocol layer may receive multiple protocol data units (PDU) for transmission.
  • the first protocol layer may determine whether the received PDUs include data from multiple data packets of an upper protocol layer. This may be the case for example if multiple upper layer packets have been concatenated in a single PDU. On the other hand, multiple PDUs may not contain multiple upper layer data packets, for example if one upper layer data packet has been segmented over multiple PDUs.
  • the first protocol layer may restrict allocation of the received PDUs such that PDUs including data from different data packets of the upper layer will be allocated to different transmissions.
  • a single transport block may not be filled with PDUs including data from multiple data packets of the upper layer protocol. This decreases the amount of consecutive packet errors on the upper layer.
  • the restriction may be applied if an allowed delay time associated with a data packet of the upper layer will not be exceeded because of delaying the data packet to the different transmission.
  • one or more first transport blocks may be filled with PDUs comprising data from a first data packet of an upper layer protocol. Applying said restriction may cause PDUs comprising data from a second data packet of the upper layer to be allocated to one or more second transport blocks.
  • the second transport block may be therefore filled with data from the second data packet.
  • the second transport block (s) may be subsequent to the first transport block (s) in processing order.
  • the one or more second transport blocks filled with PDUs comprising data from the second data packet may be transmitted after the transport block (s) has been transmitted.
  • an indication to restrict filling a single transport block with PDUs including data from multiple data packets of an upper layer protocol may be sent to a user node or a distributed unit of a base station.
  • Such indication may include information on the type of restriction and one or more conditions for applying the restriction.
  • the indication may include an identification of a user equipment, a data radio bearer, logical channel, or data packet type, for which the restriction is to be applied.
  • the indication may include identification of the protocol layer at which the restriction is to be applied and/or an identification of the upper protocol layer. This example embodiment enables to control data allocation such that the number of consecutive packet errors on a particular layer can be decreased.
  • FIG. 1 illustrates an example embodiment of a network 100.
  • the network may comprise one or more core network elements such as for example Access and Mobility Management Function (AMF) and/or User Plane Function (UPF) 130, one or more base stations, represented in the example of FIG. 1 by gNBs 120, and/or user nodes or user equipment (UE) 110.
  • a user node 110 may communicate with one or more of the base stations via wireless radio channel (s) .
  • the base stations may be configured to communicate with the core the network elements over a communication interface, such as for example control plane or user plane interface NG-C/U.
  • Base stations may be also called radio access network (RAN) nodes.
  • RAN radio access network
  • AMF/UPF, gNB, gNB-CU, and gNB-DU may be generally referred to as network nodes. Although depicted as a single device, a network node may not be a stand-alone device, but for example a distributed computing system coupled to a remote radio head.
  • Network 100 may be configured for example in accordance with the 5 th Generation digital cellular communication network, as defined by the 3 rd Generation Partnership Project (3GPP) . In one example, network 100 may operate according to 3GPP 5G-NR (5G New Radio) .
  • a base station for example a gNB 120
  • the central unit may be a logical node and may include functions such as for example transfer of user data, mobility control, radio access network sharing, positioning, session management, or the like, except for functions that may be allocated to the distributed unit(s) .
  • the central unit may be connected to the one or more distributed units over a communication interface, for example an FI interface.
  • the one or more distributed units may be logical nodes that may be configured to provide a subset of base station functions, depending on how the functions are split between the central unit and the distributed unit(s) .
  • the distributed unit(s) may be controlled by the central unit through the communication interface.
  • a central unit may control data allocation in one or more of the distributed units.
  • a base station may be connected to other radio access network nodes by another communication interface, for example, gNB 120 may communicate with one or more other gNBs 120 through an Xn interface.
  • FIG. 2 illustrates an example of an apparatus 200.
  • Apparatus 200 may represent a network node or a user node 110.
  • Apparatus 200 may comprise, for example, a base station.
  • the base station may include, for example, a fifth-generation base station, gNB 120, providing an air interface for user nodes 110 to connect to a wireless network via wireless transmissions.
  • apparatus 200 may comprise a central unit of a base station such as for example a central unit of a 5 th generation base station gNB-CU 122, or a distributed unit of a base station such as for example a distributed unit of a 5 th generation base station gNB- DU 124.
  • Apparatus 200 may comprise a user device, for example user node 110.
  • User node 110 may be for example a mobile phone, a tablet computer, a laptop, an internet of things (IoT) device, or the like.
  • IoT devices include, but are not limited to, consumer electronics, wearables, and smart home appliances.
  • apparatus 200 may comprise a vehicle such as for example a car, which may for example enable one or more automated functions, for example automated driving, based on the communication capabilities described herein.
  • Apparatus 200 may comprise one or more processors 202, and one or more memories 204 that comprise computer program code configured, when executed by the at least one processor 202, to cause performance of the apparatus 200.
  • Apparatus 200 may also include a transceiver 206, as well as other elements, such as an input/output module (not shown in FIG. 2), and/or a communication interface (not shown in FIG. 2), for example one or more antennas.
  • the apparatus may include separate transmitter ( s ) or receiver (s) configured to enable unidirectional communication.
  • apparatus 200 is depicted to include only one processor 202, the apparatus 200 may include more than one processor.
  • the memory 204 is capable of storing instructions, such as an operating system and/or various applications.
  • the processor 202 is capable of executing the stored instructions.
  • the processor 202 may be embodied as a multi-core processor, a single core processor, or a combination of one or more multi-core processors and one or more single core processors.
  • the processor 202 may be embodied as one or more of various processing devices, such as a coprocessor, a microprocessor, a controller, a digital signal processor (DSP) , a processing circuitry with or without an accompanying DSP, or various other processing devices including integrated circuits such as, for example, an application specific integrated circuit (ASIC) , a field programmable gate array (FPGA) , a microcontroller unit (MCU) , a hardware accelerator, a special-purpose computer chip, or the like.
  • the processor 202 may be configured to execute hard coded functionality.
  • the processor 202 is embodied as an executor of software instructions, wherein the instructions may specifically configure the processor 202 to perform the algorithms and/or operations described herein when the instructions are executed.
  • the memory 204 may be embodied as one or more volatile memory devices, one or more non-volatile memory devices, and/or a combination of one or more volatile memory devices and non-volatile memory devices.
  • the memory 204 may be embodied as semiconductor memories (such as mask ROM, PROM (programmable ROM) , EPROM (erasable PROM) , flash ROM, RAM (random access memory) , etc . ) .
  • FIG. 3 illustrates an example embodiment a data flow through protocol layers with examples of concatenation and segmentation.
  • the example of FIG. 3 illustrates five protocol layers, namely the Internet Protocol (IP) layer, Service Data Adaptation Protocol (SDAP) , Packet Data Convergence Protocol (PDCP) , Radio Link Control (RLC) layer, and Medium Access Control (MAC) layer, but any other number and type of layers may be used.
  • IP Internet Protocol
  • SDAP Service Data Adaptation Protocol
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control
  • MAC Medium Access Control
  • the SDAP layer may receive a plurality of IP packets 302, or IP protocol data units (PDU) .
  • the IP packets may be included in payload portions of SDAP packets 304, which may include an SDAP header (H) specific to the SDAP layer and the IP data packets as SDAP service data units (SDU) .
  • SDAP header H
  • SDU Secure Data Unit
  • the PDCP layer may encapsulate SDAP packets in PDCP packets 306, RLC layer may encapsulate PDCP packets 306 in RLC packets 308, and MAC layer may encapsulate RLC packets 308 in MAC packets 310.
  • One purpose of the RLC layer may be to segment data packets receiver from the PDCP layer and resegment data packets received from the MAC layer.
  • One purpose of the MAC layer may be to multiplex or demultiplex MAC SDUs belonging to one or more logical channels into/from transport blocks (TB) delivered to/from the physical layer on one or more transport channels. In this example, concatenating MAC packets that include data from multiple upper layer data packets is not restricted.
  • MAC packets 310A, 310B, and 310C may be allocated into a transport block k, even if MAC packets 310A, 310B, and 310C contain data from multiple RLC packets 308, 308A. In some circumstances, this may cause consecutive packet errors at the RLC layer, for example if majority of transport block k is lost in transmission.
  • a gNB- CU 122 may include SDAP and PDCP layers
  • a gNB-DU 124 may include the lower layers.
  • a transport block may refer to a physical layer transmission block, which may have its own modulation and/or coding scheme (MCS) .
  • a first transmission may comprise one or more first transport blocks.
  • a second transmission may comprise one or more second transport blocks.
  • a transmission may also refer to any other set of transmission resources, for example physical layer transmission resources, and therefore it is not limited to transport blocks.
  • different transport blocks may be mapped to different physical layer resource blocks (PRB) , which may for example comprise a number of subcarriers in one or more Orthogonal Frequency Division Multiplexing (OFDM) symbols.
  • PRB physical layer resource blocks
  • OFDM Orthogonal Frequency Division Multiplexing
  • use of MIMO Multiple Input Multiple Output
  • data allocated to different transmissions, for example transport blocks may benefit from time, frequency, and/or antenna diversity provided by different locations of the transmission resources in the time-frequency- antenna space .
  • Data packets may be segmented in various protocol layers of a protocol stack, for example the user plane protocol stack of 5G. This may apply to both uplink and downlink traffic.
  • data packets may be segmented in the RLC layer, furthermore, data packets may be concatenated and multiplexed in the MAC layer.
  • PDCP packet 306A may be segmented into two portions, which may be allocated to two RLC packets 308A and 308B.
  • a single transport block k may concatenate data from multiple MAC packets 310A, 310B, 310C.
  • one physical layer transmission can include data from separate data packets.
  • concatenation may not be applied at RLC layer to allow RLC PDU pre-creation in the transmitter side as the knowledge of available grant may not be required - only segmentation may be performed in real time.
  • High reliability for packet transmission is a desired property in many communication networks.
  • appearance of industrial applications is setting even more demanding targets for reliability.
  • applications designed for Ultra-Reliable Low- Latency Communication (URLLC) of 5G NR applications may require even higher reliability for packet transmissions, for example 1-0.1 L 5 reliability, that is, 5-nine reliability within 1ms latency budget.
  • new service types may be defined in 3GPP for Industrial IoT scenarios, which may require 7 or 9- nine reliability and/or sub millisecond latency.
  • a communication system used in an industrial setting may have a target of not having packet errors that result in exceeding a survival time of the system, which could adversely affect reliability of the industrial application.
  • a survival time may comprise a time, for example a duration or a period, which an application may survive without receiving the expected packet (s), or, as the time that an application consuming a communication service may continue without an anticipated message.
  • anticipation may imply timeliness and correctness.
  • the communication service continuity may imply one or more of the following conditions: 1) the message should arrive in time (timeliness), 2) only uncorrupted messages may be accepted by a receive, and 3) received messages need to be processed and sent out from 3GPP 5G system to the target automation function.
  • a timer may be started.
  • the communication service for that application may declared "unavailable" to indicate service discontinuity.
  • the expiration time may be referred to as the survival time.
  • the survival time may be understood as an allowed delay time.
  • Segmentation or concatenation as illustrated in FIG. 3 may provide an efficient solution for transmitting and receiving mobile broadband data. Segmentation and concatenation of packets may improve radio resource usage and allow protocols to function according to instantaneous quality of the channel and to correct errors.
  • concatenation may comprise allocation portions of data to the same packet, block, or other data container. Therefore, concatenation may include allocating data into adjacent portions of a data packet or allocating data into non-adjacent portions of a data packet.
  • the URLLC payload may be rather small, for example in the order of 50-100 bytes at most, segmentation may be applied in at least two situations.
  • segmentation may be applied by URLLC UEs located at the cell edge, for example to ensure that a transmission can be sent reliably, for example with a sufficiently low block error rate (e.g. from 0.1% to 1%) .
  • segmenting a next URLLC packet may be used to obtain a segment size such that an allocation of particular size is completely filled, for example such that an entire transport block is filled. For example, as shown in FIG. 3 the PDCP packet 306A is segmented such that MAC packet 310C including the first segment 308A of PDCP packet 306A substantially fills the space of the transport block not filled by MAC packets 310A and 310B.
  • a transport block k may include payload data from data packets n, n+1 and n+2.
  • transmission of transport block k fails, then it may cause failure of three consecutive data packets. It is therefore an object of the present example embodiments to improve reliability, for example by reducing consecutive packet errors. This may be achieved for example by designing a system that allocates segments belonging to distinct data packets to separate physical layer transmissions or resources, for example to different transport blocks. Restrictions may be applied upon certain conditions.
  • Example embodiments may prevent that protocol data units (PDU) belonging to subsequent data packets are sent together in the same physical transmission, for example the same transport block. This may be done to increase reliability of consecutive packets and to ensure meeting a survival time target.
  • the method may be applied to downlink and/or uplink directions and can be realized by introducing restriction ( s ) or condition (s) in at least one layer of the radio protocol stack, for example the RLC or MAC layers.
  • restriction ( s ) or condition (s) in at least one layer of the radio protocol stack, for example the RLC or MAC layers.
  • LCH logical channel
  • specific concatenation restriction ( s ) may be applied at the MAC layer.
  • FIG. 4 illustrates an example of a data flow through protocol layers with an example of concatenation restriction.
  • chopping or dividing packets into smaller segments is allowed in a way that distinct data packets, for example IP PDUs n, n+1, and n+2, are transmitted in separate physical layer transmissions, for example in transport blocks (TB) k, k+1, k+2, and k+3.
  • IP PDU n+2 (402) may be received at the PDCP layer and encapsulated into PDCP PDU 406.
  • IP PDU 402 may be carried in the PDCP PDU as the PDCP SDU.
  • PDCP PDU 406 may be received at the RLC layer and segmented into two RLC PDUs 408A and 408B.
  • RLC PDUs 408A and 408B may be received at the MAC layer and encapsulated into two MAC PDUs 410A and 410B, respectively.
  • at least one restriction for concatenating MAC PDUs including data from multiple upper layer PDUs in transport blocks 412 may be in place at the MAC layer.
  • the MAC layer may determine to allocate MAC PDUs 410A and 410B to transport block k+2 and a subsequent transport block k+3.
  • Concatenation may be restricted based on at least one condition.
  • concatenation may be restricted if the PDUs to be allocated include data from multiple upper layer PDUs.
  • An upper layer PDU may refer to a PDU of any layer above the layer on which the restriction ( s ) apply.
  • a condition at MAC layer may restrict concatenation of MAC PDUs, if data from multiple RLC packets is included in the MAC packets to be allocated.
  • a condition at MAC layer may restrict concatenation of MAC PDUs, if data from multiple PDCP packets is included in the MAC packets to be allocated. This allows flexibility in the system to control at which layer the number of consecutive layers is to be reduced. Conditions may apply for one or more layers at the same time.
  • condition (s) may be associated with one or more logical channels.
  • At least one restriction may be implemented at MAC/RLC layers as follows.
  • RLC may pre-create RLC PDUs, which in one example embodiment may have a fixed size.
  • MAC layer may be configured to enforce the concatenation restriction when filling an allocation having a certain transport block size (TBS) based on TBS.
  • TBS transport block size
  • L1/L2 control overhead may comprise L1/L2 headers and the cyclic redundancy check (s) (CRC) .
  • a UE 110 or a distributed unit of a base station may receive an indication, for example a message, to apply at least one concatenation restriction, for example to restrict filling PDUs into same transport block.
  • an indication for example a message
  • Such indication may comprise include one or more of the following conditions:
  • a received message may include at least one of the conditions described above.
  • the message may further indicate a type of restriction, such as for example a concatenation restriction, a concatenation restriction with an allowed delay time, a concatenation restriction and leg switch restriction, a concatenation restriction and transmission leg switch restriction with an allowed delay time, or any other type of restriction.
  • the UE 110 or the distributed unit may restrict concatenation of packets at one or more protocol layers. For example, the UE 110 or the distributed unit may restrict allocation of MAC layer packets in the same transport block, if the MAC layer packets include data from multiple RLC packets or PDCP packets.
  • the UE 110 or distributed unit may be preconfigured with information on the layers at which the restriction is to be applied and/or preconfigured with information on the one or more conditions for applying the restriction.
  • the UE 110 or distributed unit may apply the restriction on layer (s) indicated in the received message.
  • the restriction may be applied to the one or more indicated logical channels (LCH) .
  • the UE 110 or the distributed unit may determine whether the plurality of PDUs includes data from multiple data packets of an upper layer protocol, for example a previous layer in the protocol stack. Additionally, the plurality of PDUs may include data from further data packets.
  • UE 110 or the distributed unit may determine whether there is data from at least two data packets, such as for example the first data packet and the second data packet. In one example embodiment, determining whether the plurality of PDUs includes data from multiple data packets of an upper layer protocol may be based on an indication received from the upper layer protocol. For example, if restrictions are applied at the MAC layer for RLC PDUs received from the RLC layer, the RLC layer may indicate whether two RLC PDUs are associated with different upper layer data packets, for example different PDCP PDUs.
  • the UE 110 or the distributed unit may determine that no restrictions apply and may allocate multiple PDUs in a single transmission, for example one or more transport blocks.
  • the UE 110 or the distributed unit may determine to apply the indicated restriction ( s ) as described above.
  • data packets encapsulated by the RAN protocol stack may comprise Ethernet frames. This may be the case for example in industrial systems.
  • the data packets may comprise IP datagrams, which may be used for example in cellular systems.
  • a survival time of a packet may be used as a condition for applying the at least one concatenation restriction.
  • the UE 110 or the distributed unit may determine that at least one packet included in the plurality of PDU is associated with a survival time.
  • the survival time may comprise a delay time that is allowed for a particular packet or a group of packets.
  • the UE 110 or the distributed unit may be configured to ensure that survival time is not exceeded because of applying a restriction, for example not allocating PDUs including multiple upper layer packets to same transmission.
  • the UE 110 or the distributed unit may monitor one or more timers associated with packets in its buffer and if a timer is about to be expired, the UE 110 or the distributed unit may temporarily stop applying the concatenation restriction and may allocate a plurality of PDUs in the same transmission even if the PDUs include data from multiple data packets. This ensures that latency requirements are met even if the UE 110 or the distributed unit is instructed to improve transmission reliability by applying concatenation restrictions.
  • UE 110 may be configured to send a buffer status report to a network node, for example to a scheduling entity such as a MAC scheduler of the network 100.
  • the buffer status report may indicate an amount of data that is waiting for transmission in the transmit buffer of UE 110.
  • the scheduler may then allocate uplink resources for the UE 110 to transmit the data.
  • the allocated uplink resources may be referred to as an uplink grant.
  • the network node may not know sizes of UE's individual packets or segments of those, for example URLCC packets or segments of URLCC packets. Therefore, the resource allocation may not be optimized, for example to accommodate in one uplink grant only the last segment (s) of packet n.
  • One solution for the UE may comprise inserting padding bits at the end of the last segment (s) of one URLLC packet in order to substantially fill the complete resource allocation, without mixing distinct URLLC packets in the same uplink grant.
  • the network node may learn to estimate sizes of the individual packets by machine learning or artificial intelligence approaches, which may be effective for example for industrial IoT use cases due to deterministic nature of the traffic.
  • the network node may assign multiple uplink grants per buffer status report (BSR) and thereby minimize usage of segmentation or padding.
  • BSR buffer status report
  • a buffer status report may be extended to indicate packet sizes, in contrast to indicating buffer status per logical channel (LCH) only.
  • the buffer status report may include an indication, for example a first signaling field, of a number of packets or segments in the buffer.
  • the buffer status report may include one or more second signaling fields for indicating size for one or more of the packets or segments, for example for each packet or segment .
  • UE 110 may be configured to send the extended buffer report in response to receiving an indication to restrict concatenation of PDUs at one or more layers. Including the information on packet and/or segment sizes in the buffer status report may result in slightly higher control overhead, but the increase in the overhead may be reduced by including this additional information only if a UE 110 is instructed to apply concatenation restriction ( s ) . Since the additional information is included for UEs 110 that indicate in their BSR the presence of multiple packets for the targeted LCH in the buffer, the additional information is included only for a small subset of all packets received by the base stations. Moreover, since the additional information may be included in response to instructing a UE 110 to apply concatenation restriction ( s ) , the base station may control whether this additional data is included or not. Therefore, more flexibility in resource allocation is achieved .
  • a switch of radio link may be performed such that segments of a data packet are transmitted using the same radio link.
  • UE 110, a base station, or a distributed unit of the base station may be configured to transmit desired segments, in one example all segments of a data packet, over a single radio link This reduces the probability of consecutive packet errors due to leg switching, in particular when applied in combination with the concatenation restriction ( s ) .
  • a leg switch may be performed after transport blocks k and k+1, but not after transport k+2, because part of PDCP packet 406 will be transmitted in transport block k+3.
  • a UE 110 or a base station may determine whether a packet contains desired segments, for example all segments, of an upper layer packet, and if the desired segments are not included, it may determine not to switch radio link.
  • a UE configured with carrier aggregation or dual connectivity may have at least two radio connections to different cells referred to as a primary or master cell and a secondary cell. The UE may have multiple secondary cells in case it has more than two radio connections. Such radio connection may be called a transmission leg, transmission link, or a radio link.
  • FIG. 5 illustrates an example embodiment of the subject matter described herein illustrating a data flow through protocol layers.
  • part of the transmission for example a particular transport block or any other set of transmission resources, may be used for sending other data.
  • the other data may for example include data belonging to a logical channel for which the concatenation restriction does not apply. For example, if size of the last segment (s) of a URLLC packet is smaller than the available allocation, then left over radio resources can be utilized by the UE 110 to send other traffic than the URLLC data mapped to the restricted logical channel (LCH) . This enables to avoid using padding bits or an unnecessarily robust modulation and/or coding scheme, which improves transmission efficiency .
  • LCH restricted logical channel
  • URLLC protocol data units 506 and eMBB (enhanced Mobile Broadband) protocol data units 507 may be allocated to RLC packets 508.
  • a first URLLC packet 506A may be allocated to a first RLC packet 508A.
  • a second URLLC packet 506B may be allocated to a second RLC packet 508B. This may be done in response to determining that allocating URLLC the second URLLC packet 506B to the second RLC packet 508B does not cause expiration of an allowed delay time, for example a survival time associated with the second URLLC packet 506B.
  • a device for example UE 110 or a gNB-DU 124, performing the allocation may have knowledge of the packet or transport block sizes at necessary layers to determine whether a particular allocation causes expiration of the allowed delay time. If URLLC packet 506A does not fill the available capacity in the first RLC packet 508A, an eMBB packet 507A, or a portion thereof, may be allocated to the first RLC packet 508A. Furthermore, if the first URLLC packet 506A and the eMBB 507A do not fill the available capacity of a first MAC packet 510A, an eMBB packet 507B, or a portion thereof as illustrated in FIG. 5, may be allocated to the first MAC packet 510A.
  • the second URLLC packet 506B may be allocated to a second MAC packet 510B along with other eMBB data, for example a portion of eMBB packet 507B.
  • This example embodiment enables improving transmission efficiency by restricting concatenation of URLLC packets to increase transmission reliability for URLLC packets, while not increasing overall transmission overhead.
  • URLLC and eMBB are used as example data types, it is appreciated that this example embodiment could be applied for any types of protocol data units having different requirements with respect to consecutive packet errors. It is also appreciated that example embodiments could be applied to any other layers of a protocol stack, for example at MAC/PHY layers.
  • packet sizes may be known by the scheduling entity of network 100 and therefore in some cases allocations may be optimized according to segment size(s) . However, this may not be the case if the protocol stack is split between central and distributed units of a base station, for example a gNB .
  • a central unit of a base station may be configured to send an indication of at least one concatenation restriction to a distributed unit of the base station, for example a gNB-DU 124.
  • the distributed unit may be configured to send the indication to one or more UEs 110.
  • the indication may for example include instructions to restrict filling PDUs including data from different upper layer data packets into same transport block.
  • the indication may include one or more of the following conditions:
  • the indication may be included in a message transmitted to the distributed unit of the base station, or a UE .
  • the message may further indicate a type of restriction, such as for example a concatenation restriction, a concatenation restriction with an allowed delay time, a concatenation restriction and leg switch restriction, a concatenation restriction and transmission leg switch restriction with an allowed delay time, or any other type of restriction.
  • the indication of the at least one restriction may be sent at the PDCP layer.
  • the indication may be included in a header of a PDCP packet 406.
  • the indication is sent by a central unit via the FI interface.
  • a distributed unit may receive the indication, for example over the FI interface, and apply one or more restrictions based on the received indication, as described throughout the specification .
  • the present example embodiments may comprise slightly delaying transmission of an initial part of a data packet or an entire data packet on purpose, for example for packets that are considered as ultra-reliable low-latency communication (URLLC) data. This will improve the likelihood of maintaining desired strict reliability and latency targets.
  • URLLC ultra-reliable low-latency communication
  • the application packet delay will be anyhow determined by the transmission time of the last packet, so advantageously such example embodiments do not lead to any additional delays.
  • FIG. 6 illustrates an example of a flow chart for determining how to allocate packets, for example URLLC packets.
  • the method may be performed for example in a user node 110, or a network node such as a distributed unit of a base station, for example gNB-DU 124.
  • the method may be initiated or re-initiated at 601.
  • the method may comprise determining whether there is room in next transmission allocation for more data and whether unsent URLLC data exists.
  • the next transmission may comprise for example a next transmission time interval (TTI), a subframe, a mini slot such as for example a mini-slot of two OFDM symbols, a transport block, or the like.
  • TTI next transmission time interval
  • subframe a subframe
  • mini slot such as for example a mini-slot of two OFDM symbols
  • transport block or the like.
  • the method may proceed to operation 608, where the procedure may be ended.
  • the method may proceed to operation 603.
  • the method may comprise taking into consideration a next URLLC packet or segment that is available for transmission. The method may then proceed to operation 604.
  • the method may comprise determining whether an unsent earlier URLLC packet exists in transmission protocol buffer (s) for the next transmission . In response to determining that no unsent earlier URLLC packet exists in transmission protocol buffer (s) for the next transmission, the method may proceed to operation 605.
  • the method may proceed to operation 606.
  • the method may comprise forwarding the packet or segment to at least one lower layer for transmission.
  • the method may then proceed to operation 608, where the method may be ended for the packet or the segment.
  • the method may be then re-initiated for another packet or segment at 601.
  • the method may comprise determining whether an allowed delay time has expired or would be expired if packet transmission is delayed to the next transmission, for example whether a packet delay timer has exceeded or would exceed the survival threshold.
  • the method may proceed to operation 605.
  • the method may proceed to operation 607.
  • packet transmission may be delayed by one or more transmissions, for example by n TTIs.
  • the amount of delay for example the number of TTIs, may be determined to be such that the allowed packet delay time is not exceeded.
  • the procedure may then proceed back to operation 602, which causes allocation of the same packet or segment to be determined again based on one or more of the operations 602 to 607.
  • a benefit of the present example embodiments is that packets may be transmitted in time, but separately in order to avoid multiple simultaneous errors. Moreover, when packets are delayed, parameters or information such as for example channel measurement ( s ) , link adaptation offset (s), and/or MCS selection could be updated for an upcoming TTI when next transmission takes place. Thus, e.g. a single over estimation of signal-to-interference-plus-noise ratio (SINR) would not cause failure of multiple packets. This is beneficial because retransmissions may not be possible due to HARQ (Hybrid Automatic Repeat Request) round-trip times. Thus, a delay of few TTIs is acceptable, since multiple transmission failures or retransmission can be avoided. It beneficial to avoid retransmissions, because they cause more delays due to increased network load and interference, which may be undesirable in a URLLC communication environment.
  • SINR signal-to-interference-plus-noise ratio
  • FIG. 7 illustrates an example of a method 700 suitable for data allocation.
  • the method may comprise receiving, at a first protocol layer, a plurality of protocol data units for transmission, wherein the plurality of protocol data units comprises data from at least a first and a second data packet of a second protocol layer.
  • the method may comprise determining that the plurality of protocol data units comprises data from the first and the second data packets of the second protocol layer.
  • the method may comprise, for example in response to the determination at 702, filling at least one first transport block with protocol data units including data from the first data packet and restricting filling the at least one first transport block with protocol data units including data from the second data packet.
  • the method may comprise, for example in response to the determination at 702, filling at least one second transport block with protocol data units including data from the second data packet.
  • An apparatus for example a user node or user device, such as for example a mobile terminal, may be configured to perform one or more operations of method 700.
  • a computer program may comprise instructions for causing an apparatus to perform one or more operations of method 700.
  • an apparatus may comprise means for performing one or more operations of method 700.
  • FIG. 8 illustrates an example of a method 800 suitable for providing instructions for data allocation.
  • the method may comprise determining to restrict filling at least one first transport block with a plurality of protocol data units at a first protocol layer when the plurality of protocol data units comprises data from a first and a second data packet of a second protocol layer.
  • the method may comprise transmitting an indication to restrict filling the at least one first transport block with the plurality of protocol data units .
  • An apparatus for example a network node may be configured to perform one or more of operations of method 800.
  • a computer program may comprise instructions for causing an apparatus to perform one or more operations of method 800.
  • an apparatus may comprise means for performing one or more operations of method 800.
  • a method may comprise receiving, at a first protocol layer, a plurality of packet data units for transmission, wherein the plurality of packet data units comprises at least one data packet of a second protocol layer, and wherein the at least one data packet of the second protocol layer is associated with an allowed delay time; in response to determining that the plurality of packet data units comprises data from multiple data packets of the second protocol layer: allocating the plurality of packet data units to a first transmission if allocating at least one of the plurality of packet data units to a second transmission would cause expiration of the allowed delay time; and allocate the at least one of the plurality of packet data units to the second transmission if allocating the at least one of the plurality of packet data units to the second transmission does not cause expiration of the allowed delay time.
  • a method may comprise determining to restrict allocation of a plurality of packet data units at a first protocol layer into a first transmission, when the plurality of packet data units comprises data from multiple data packets of a second protocol layer; and transmitting an indication to restrict allocation of a plurality of packet data units at a first protocol layer into a first transmission .
  • an apparatus or a computer program may be configured to perform, cause to perform, or comprise means for performing any variations of the methods, as described in the appended claims and throughout the description.
  • FIG. 9 illustrates an example of transmission reliability, in accordance with a reference system and some example embodiments.
  • the example embodiments can improve reliability of URLLC packet transmissions, both in terms of single errors (white bars) and of two consecutive errors (diagonal hash) .
  • the number of packet errors can be reduced and close to 1-0.1 L 5 reliability can be achieved without HARQ retransmissions. It can be observed that combining concatenation restriction with conditions on leg switching further improves the reliability.
  • Avoiding retransmissions is beneficial, because they would cause delays due to round-trip time caused by sending an acknowledgement and retransmission. Moreover, there may be also more time to perform link adaptation (such as for example channel estimation and MCS selection) between packets. This may occur for example when two packets become available for transmission with short inter-arrival time. Then, instead of immediate transmission, second packet may be delayed a bit in a way that it is transmitted after transmission of all segments of the first packet, but still within the packet survival time.
  • link adaptation such as for example channel estimation and MCS selection
  • circuitry' may refer to one or more or all of the following: (a) hardware-only circuit implementations
  • circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and/or firmware.
  • circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.

Landscapes

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

Abstract

L'invention concerne des appareils, des procédés et des programmes informatiques d'attribution de données dans un réseau de communication cellulaire. Une ou plusieurs restrictions concernant l'attribution d'unités de données de protocole (408A, 408B) d'un protocole de couche supérieure (RLC) à un bloc de transport (TB) unique au niveau d'une couche inférieure (MAC) peuvent être appliquées.
PCT/EP2019/061886 2019-05-09 2019-05-09 Attribution de données dans une communication cellulaire WO2020224781A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/EP2019/061886 WO2020224781A1 (fr) 2019-05-09 2019-05-09 Attribution de données dans une communication cellulaire

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2019/061886 WO2020224781A1 (fr) 2019-05-09 2019-05-09 Attribution de données dans une communication cellulaire

Publications (1)

Publication Number Publication Date
WO2020224781A1 true WO2020224781A1 (fr) 2020-11-12

Family

ID=66530028

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2019/061886 WO2020224781A1 (fr) 2019-05-09 2019-05-09 Attribution de données dans une communication cellulaire

Country Status (1)

Country Link
WO (1) WO2020224781A1 (fr)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018086693A1 (fr) * 2016-11-10 2018-05-17 Huawei Technologies Co., Ltd. Dispositif d'émission, dispositif de réception et procédés associés

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018086693A1 (fr) * 2016-11-10 2018-05-17 Huawei Technologies Co., Ltd. Dispositif d'émission, dispositif de réception et procédés associés

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; NR and NG-RAN Overall Description; Stage 2 (Release 15)", 3GPP STANDARD; TECHNICAL SPECIFICATION; 3GPP TS 38.300, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. V15.5.0, 9 April 2019 (2019-04-09), pages 1 - 97, XP051723349 *

Similar Documents

Publication Publication Date Title
US11012999B2 (en) Method and apparatus for indicating time domain resource allocation of data transmission in a wireless communication system
JP6976337B2 (ja) 無線通信システムにおける端末のアップリンク制御チャネル送信方法及び前記方法を利用する通信装置
US8817636B2 (en) Method, system, and equipment for information processing
JP6959331B2 (ja) データ送信ノード、データ受信ノード、データ受信ノードにデータを送信するための方法、および、データ送信ノードからデータを受信するための方法
US9155070B2 (en) Method and apparatus for transmitting uplink data burst in wireless connection system
US11296841B2 (en) Communications method and apparatus
JP2020530240A (ja) 通信方法および通信機器
US10536892B2 (en) Method and device for data transmission
CN110199541B (zh) 用于在无线通信系统中处理数据的方法和装置
JP2010524389A (ja) 通信システムにおける方法および装置
US20220322326A1 (en) Communications devices and methods
US11101935B2 (en) Apparatus and method for transmitting packet data units
US20220377781A1 (en) Method, apparatus, computer program product and computer program
US20230232373A1 (en) Method and device in nodes used for wireless communication
CN115380484A (zh) 无线通信系统中发送和接收下行链路信道的基于盲解码的方法和设备
CN109963340B (zh) 用于降低信令开销和数据延迟的方法、设备及计算机可读介质
JP7012292B2 (ja) チャネル符号化に用いるユーザー装置、基地局における方法及び装置
US20230022663A1 (en) Method and device in nodes used for wireless communication
CN111757519B (zh) 通信方法和通信装置
US20230198681A1 (en) Method and device in nodes used for wireless communication
WO2020224781A1 (fr) Attribution de données dans une communication cellulaire
JP2020065289A (ja) 短レイテンシ高速再送信トリガ
EP4152668A1 (fr) Procédé et dispositif utilisés dans un noeud pour des communications sans fil
US20230224114A1 (en) Method and device in nodes used for wireless communication
CN114390682A (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: 19723757

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

Country of ref document: EP

Kind code of ref document: A1