[go: up one dir, main page]

WO2025170520A1 - Retransmissions de commande de liaison radio flexibles pour mode acquitté de commande de liaison radio pour des services critiques vis-à-vis du temps - Google Patents

Retransmissions de commande de liaison radio flexibles pour mode acquitté de commande de liaison radio pour des services critiques vis-à-vis du temps

Info

Publication number
WO2025170520A1
WO2025170520A1 PCT/SE2025/050086 SE2025050086W WO2025170520A1 WO 2025170520 A1 WO2025170520 A1 WO 2025170520A1 SE 2025050086 W SE2025050086 W SE 2025050086W WO 2025170520 A1 WO2025170520 A1 WO 2025170520A1
Authority
WO
WIPO (PCT)
Prior art keywords
rlc
pdu
rlc pdu
radio node
retransmitted
Prior art date
Legal status (The legal status 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 status listed.)
Pending
Application number
PCT/SE2025/050086
Other languages
English (en)
Inventor
Richard TANO
Jose Luis Pradas
Du Ho Kang
Fabian DE LAVAL
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Telefonaktiebolaget LM Ericsson AB
Original Assignee
Telefonaktiebolaget LM Ericsson AB
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 AB filed Critical Telefonaktiebolaget LM Ericsson AB
Publication of WO2025170520A1 publication Critical patent/WO2025170520A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

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/1829—Arrangements specially adapted for the receiver end
    • H04L1/1832—Details of sliding window management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1825—Adaptation of specific ARQ protocol parameters according to transmission conditions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/187—Details of sliding window management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/188—Time-out mechanisms
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/1896—ARQ related signaling

Definitions

  • the present disclosure relates, in general, to wireless communications and, more particularly, systems and methods for flexible Radio Link Control (RLC) retransmissions for Radio Link Control-Acknowledged Mode (RLC-AM) for time critical services.
  • RLC Radio Link Control
  • RLC-AM Radio Link Control-Acknowledged Mode
  • the transmitter entity When RLC AM Mode is configured, the transmitter entity will perform retransmissions when data is not successfully received by the receiver.
  • the receiver will typically inform the transmitter about the successfully received (positive acknowledgement - ACK) or unsuccessfully received (negative acknowledgement - NACK) RLC SDUs or RLC SDU segments. In NR, this information is carried in the RLC STATUS PDU.
  • Certain embodiments may provide one or more of the following technical advantage(s). For example, certain embodiments may provide a technical advantage of enabling configuration of RLC AM Mode while not having to retransmit PLC PDUs if, for example, the PDB for the associated RLC SDU has been exceeded.
  • FIGURE 3 illustrates XR traffic characteristics compared to Voice Over IP (VoIP) and Web-browsing
  • FIGURE 4 illustrates one example format of an AMD PDU
  • FIGURE 17 illustrates another example method by a receiving radio node for RLC transmissions, according to certain embodiments
  • the SMTC configuration comprising parameters such as SMTC periodicity, SMTC occasion length in time or duration, SMTC time offset with regard to reference time (e.g., serving cell’s SFN) etc. Therefore, SMTC occasion may also occur with certain periodicity (e.g., 5 ms, 10 ms, 20 ms, 40 ms, 80 ms, and 160 ms).
  • uplink (UL) physical signals are reference signals such as Sounding Reference Signals (SRS), Demodulation Reference Signals (DMRS), etc.
  • SRS Sounding Reference Signals
  • DMRS Demodulation Reference Signals
  • the term physical channel refers to any channel carrying higher layer information e.g. data, control etc.
  • Examples of physical channels are Physical Broadcast Channel (PBCH), Physical Downlink Control Channel (PDCCH), Physical Downlink Shared Channel (PDSCH), Physical Uplink Shared Channel (PUSCH), Physical Uplink Control Channel (PUCCH), Physical Uplink Shared Channel (PUSCH), Short PUSCH (sPUCCH), Short PDSCH (sPDSCH), Short PUCCH (sPUCCH), Short PUSCH (sPUSCH), MTC PDCCH (MPDCCH), Narrowband PBCH (NPBCH), Narrowband PDCCH (NPDCCH), Narrowband PDSCH (NPDSCH), Narrowband PUSCH (NPUSCH), Enhanced PDCCH (E-PDCCH), etc.
  • time resource used herein may correspond to any type of physical resource or radio resource expressed in terms of length of time.
  • time resources are: symbol, time slot, subframe, radio frame, TTI, interleaving time, slot, sub-slot, mini-slot, system frame number (SFN) cycle, hyper-SFN (H-SFN) cycle etc.
  • a new control PDU is introduced, which may be referred to as an RLC Advance Window.
  • This new Control PDU is used to inform the RLC receiver or the transmitter entity that no more retransmissions are needed for one or more RLC PDUs. This may also result in the transmitting and receiving RLC windows being updated. For example, in a particular embodiment, the lower end of the RLC window may be moved forward.
  • the new Control PDU is identified by a new CPT value, introduced for this purpose.
  • the Control PDU may include one or more of the following: the RLC PDU(s) SN that do not need be retransmitted, lowest RLC PDU SN waiting for retransmission, lowest end of the RLC window, and/or SN range.
  • the RLC entity will ignore these RLC PDU SN or considered them as if they had been positively received. If the indicated RLC PDU SNs do belong to RLC SDUs not completely received, the receiving RLC entity will discard the already received RLC SDUs segments belonging to those incomplete RLC SDUs.
  • the RLC Control PDU sets 1-bit such as, for example, the El-bit, to indicate that additional RLC SDU SNs are indicated.
  • the RLC transmitting entity will not retransmit those RLC PDUs SN that were pending of retransmission up to the indicated RLC PDU SN (included or up to the one before it) and will consider those RLC PDUs SN as if they were positively received by the receiver. If there were incomplete RLC SDUs (include or up to the one before the indicated SN), the receiving RLC entity will discard the already received RLC SDUs segments belonging to those incomplete RLC SDUs and will also consider those RLC SDUs (included or up to the one before the indicated RLC PDU SN) as if they were positively received. Those complete RLC SDUs waiting to be passed to higher layers, will then be passed to higher layer up (included or up to the one before the indicated RLC PDU SN).
  • one RLC SDU can be equivalent to 1 or more RLC PDUs. In case the RLC SDU is segmented, then there will be more than one RLC PDU. However, if any RLC PDU associated to RLC SDU has not started to be transmitted, then there is no need to send any indication to the receiver. Also note that one RLC SDU has one SN and all RLC PDUs associated to the RLC SDU share the same SN.
  • FIGURE 5 illustrates the case in which a new Control PDU 100 indicates the RLC SN 102 associated to the lowest end of the window, when the SN length is 12-bits, according to certain embodiments.
  • FIGURE 6 illustrates an example Control PDU 200 in which 18 -bit SN length is configured and the new Control PDU indicates multiple RLC SN 202a, 202b, 202c, 202d, 202e, and 202f and a SN range 204, according to certain embodiments.
  • the RLC control PDU header can consist of one or more RLC SN 202c and one El 206a and one E3 206b, and possibly a SN range field 204 for each RLC SN.
  • FIGURE 7 illustrates an exemplary new Control PDU 300 combining STATUS PDU and RLC SDU skipping information, according to certain embodiments.
  • a new field such as, for example, E4 302, is introduced to indicate that a set of RLC SN, El, E2, E3, and E4 follows.
  • E4 is set, one RLC SN, one or more of El, E2, E3, E4 would follow, in a particular embodiment.
  • Those present fields one or more of El, E2, E3, E4 would be redefined.
  • the following fields would indicate one or more RLC
  • FIGURE 8 illustrates another alternative new Control PDU 400 that uses the “R”-bit after the ACK_SN to indicate whether a RLC SN + E-fields follow, according to certain embodiments.
  • El is set to 0 and the new field such as, for example, E4 802, is set to 1, then one RLC SN, and one or more of the E-fields follow, as explained above.
  • FIGURE 9 illustrates an example Control AMD PDU 500 that uses 18 bit SN 502 without
  • the two reserved bits can be used to indicate RLC_SN 504 is followed after SN 502 of the data. Then 18 bits of RLC_SN 504 are followed before data 506. The RLC_SN 504 will be used for the same purpose as one in the new control PDU. If the reserved bits are not flagged, i.e. 00, there are no RNC_SN followed so the legacy AMD PDU 500 is transmitted.
  • FIGURE 10 shows the modified format of AMD PDU 600 with 12 bits SN with now SO.
  • RLC_SN indication bit (RN) 602 is added after SN 604 and that indicates if RLC_SN 606 is followed or not. Once that bit is flagged, RLC SN 606 is added. Otherwise, there is no RLC SN bits added before data 608.
  • the RLC entity when the PDCP entity indicates to lower layers (e.g., RLC) to discard a certain PDCP PDU (e.g., an RLC SDU), the RLC entity discards the associated RLC SDU if the complete or a segment of the RLC SDU was not already transmitted.
  • RLC lower layers
  • the transmitting RLC entity performs one or more of the following: a. The transmitting RLC entity discards the RLC SDUs associated to the said PDCP PDUs, and the transmitting RLC entity will stop any ongoing transmissions for the RLC SDUs or any of their segments. b. The transmitting RLC entity builds the new RLC Control PDU providing an indication of the RLC SDUs which the transmitter is discarding. c. The transmitting RLC entity considers those RLC SDUs as if the RLC SDUs had been positively acknowledged. d.
  • the transmitting RLC entity may update the TX_Next_Ack taking into account the said RLC SDUs which were considered as positively acknowledged. e. The transmitting RLC entity does not send an indication to the upper layers of successful delivery for the said RLC SDUs. f. The transmitting RLC entity does not perform any further retransmissions of those RLC SDUs.
  • the receiving RLC entity performs one or more of: a. If the indication provided the RLC PDU(s) SN that do not need be retransmitted, i. the receiving RLC entity considers the RLC SDUs indicated in the message as if these RLC PDUs has been placed in the reception buffer, which results in that the receiving RLC entity will update the receiver window variables accordingly. b. If the indication provided the lowest RLC PDU SN waiting for retransmission or lowest end of the RLC window, i. the receiving RLC entity considers the RLC SDUs up to the indicated SN as if these RLC PDUs has been placed in the reception buffer, which results in that the receiving RLC entity will update the receiver window variables accordingly.
  • the receiving RLC entity If the indication provided a SN range, i. the receiving RLC entity considers the RLC SDUs within the range as if these RLC PDUs has been placed in the reception buffer, which results in that the receiving RLC entity will update the receiver window variables accordingly. d. The receiving RLC entity discards the RLC SDU segments, if any, of the affected RLC SDUs SN.
  • a network can introduce new RLC parameters to configure the triggering of the new RLC control PDU instead of relying on PDCP discarding operation. For example, a network configures a threshold of RLC AM retransmission attempt (R thr) which can be smaller than the maximum RLC AM retransmission which is used for RLC failure to reestablish RRC connection. Once the number of RLC AM retransmission reaches R thr, the transmitting/receiving RLC entity follows the procedures of 2) and 3) above.
  • a network instead of or in addition to R thr, a network configures the maximum delay of RLC transmission (L thr), which can be measured from the first initial RLC transmission timing to the reception of its ACK. Once the L thr is reached for a RLC SDU, the transmitting/receiving RLC entity follows the procedures of 2) and 3) above.
  • the RLC entity may follow the procedures of 2) and 3) above.
  • a network is configured to use PDU Set Importance (PSI) levels to differentiate between high and low importance packets in a flow, and if PSI levels are identified, the transmitting RLC entity triggers a RLC control PDU after X retransmission attempts associated with PSI level Y.
  • the network may, in a particular embodiment, configure how many re-transmission attempts is possible for each PSI level.
  • FIGURE 11 shows an example of a communication system 700 in accordance with some embodiments.
  • the communication system 700 includes a telecommunication network 702 that includes an access network 704, such as a radio access network (RAN), and a core network 706, which includes one or more core network nodes 708.
  • the access network 704 includes one or more access network nodes, such as network nodes 710a and 710b (one or more of which may be generally referred to as network nodes 710), or any other similar 3rd Generation Partnership Project (3 GPP) access node or non-3GPP access point.
  • 3 GPP 3rd Generation Partnership Project
  • the network nodes 710 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 712a, 712b, 712c, and 712d (one or more of which may be generally referred to as UEs 712) to the core network 706 over one or more wireless connections.
  • UE user equipment
  • Example wireless communications over a wireless connection include transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors.
  • the communication system 700 may include any number of wired or wireless networks, network nodes, UEs, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.
  • the communication system 700 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.
  • the UEs 712 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and/or operable to communicate wirelessly with the network nodes 710 and other communication devices.
  • the network nodes 710 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 712 and/or with other network nodes or equipment in the telecommunication network 702 to enable and/or provide network access, such as wireless network access, and/or to perform other functions, such as administration in the telecommunication network 702.
  • UMTS Telecommunications System
  • LTE Long Term Evolution
  • 5G Fifth Generation
  • WiFi wireless local area network
  • WiMax Worldwide Interoperability for Microwave Access
  • WiMax Bluetooth
  • Z-Wave Z-Wave
  • NFC Near Field Communication
  • LiFi LiFi
  • LPWAN low-power wide-area network
  • the telecommunication network 702 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 702 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 702. For example, the telecommunications network 702 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and/or Massive Machine Type Communication (mMTC)/Massive loT services to yet further UEs.
  • URLLC Ultra Reliable Low Latency Communication
  • eMBB Enhanced Mobile Broadband
  • mMTC Massive Machine Type Communication
  • the hub 714 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data.
  • the hub 714 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 714 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 714 then provides to the UE either directly, after performing local processing, and/or after adding additional local content.
  • the hub 714 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy loT devices.
  • the hub 714 may be a dedicated hub - that is, a hub whose primary function is to route communications to/from the UEs from/to the network node 710b.
  • the hub 714 may be a nondedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 710b, but which is additionally capable of operating as a communication start and/or end point for certain data channels.
  • FIGURE 12 shows a UE 800, which may be an embodiment of the UE 112 of FIGURE 11, in accordance with some embodiments.
  • a UE refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other UEs.
  • the input/output interface 806 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and/or output devices.
  • Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof.
  • An input device may allow a user to capture information into the UE 800.
  • the memory 810 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth.
  • the memory 810 includes one or more application programs 814, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 816.
  • the memory 810 may store, for use by the UE 800, any of a variety of various operating systems or combinations of operating systems.
  • the memory 810 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and/or ISIM, other memory, or any combination thereof.
  • RAID redundant array of independent disks
  • HD-DVD high-density digital versatile disc
  • HDDS holographic digital data storage
  • DIMM external mini-dual in-line memory module
  • SDRAM synchronous dynamic random access memory
  • SDRAM synchronous dynamic random access memory
  • the UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’
  • eUICC embedded UICC
  • iUICC integrated UICC
  • SIM card removable UICC commonly known as ‘SIM card.’
  • the memory 810 may allow the UE 800 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data.
  • An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 810, which may be or comprise a device-readable storage medium.
  • the processing circuitry 802 may be configured to communicate with an access network or other network using the communication interface 812.
  • the communication interface 812 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 822.
  • the communication interface 812 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network).
  • Each transceiver may include a transmitter 818 and/or a receiver 820 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth).
  • the transmitter 818 and receiver 820 may be coupled to one or more antennas (e.g., antenna 822) and may share circuit components, software or firmware, or alternatively be implemented separately.
  • communication functions of the communication interface 812 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof.
  • GPS global positioning system
  • Communications may be implemented in according to one or more communication protocols and/or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol/intemet protocol (TCP/IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.
  • CDMA Code Division Multiplexing Access
  • WCDMA Wideband Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • GSM Global System for Mobile communications
  • LTE Long Term Evolution
  • NR New Radio
  • UMTS Worldwide Interoperability for Microwave Access
  • WiMax Ethernet
  • TCP/IP transmission control protocol/intemet protocol
  • SONET synchronous optical networking
  • ATM Asynchronous Transfer Mode
  • QUIC Hypertext Transfer Protocol
  • HTTP Hypertext Transfer Protocol
  • a UE may provide an output of data captured by its sensors, through its communication interface 812, via a wireless connection to a network node.
  • Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE.
  • the output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected, an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e g., a live video feed of a patient).
  • a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection.
  • the states of the actuator, the motor, or the switch may change.
  • the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.
  • a UE when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare.
  • loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door/window sensor, a flood/moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or itemtracking
  • AR Augmented
  • a UE may represent a machine or other device that performs monitoring and/or measurements and transmits the results of such monitoring and/or measurements to another UE and/or a network node.
  • the UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device.
  • the UE may implement the 3 GPP NB-IoT standard.
  • a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.
  • any number of UEs may be used together with respect to a single use case.
  • a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone.
  • the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’ s speed.
  • the first and/or the second UE can also include more than one of the functionalities described above.
  • a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.
  • FIGURE 13 shows a network node 900, which may be an embodiment of the network node 110 of FIGURE 5, in accordance with some embodiments.
  • network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a UE and/or with other network nodes or equipment, in a telecommunication network.
  • network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)).
  • APs access points
  • BSs base stations
  • Node Bs evolved Node Bs
  • gNBs NR NodeBs
  • Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations.
  • a base station may be a relay node or a relay donor node controlling a relay.
  • a network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio.
  • RRUs remote radio units
  • RRHs Remote Radio Heads
  • Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio.
  • Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).
  • DAS distributed antenna system
  • network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi -cell/multi cast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and/or Minimization of Drive Tests (MDTs).
  • MSR multi-standard radio
  • RNCs radio network controllers
  • BSCs base station controllers
  • BTSs base transceiver stations
  • OFDM Operation and Maintenance
  • OSS Operations Support System
  • SON Self-Organizing Network
  • positioning nodes e.g., Evolved Serving Mobile Location Centers (E-SMLCs)
  • the network node 900 includes a processing circuitry 902, a memory 904, a communication interface 906, and a power source 908.
  • the network node 900 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components.
  • the network node 900 comprises multiple separate components (e.g., BTS and BSC components)
  • one or more of the separate components may be shared among several network nodes.
  • a single RNC may control multiple NodeBs.
  • each unique NodeB and RNC pair may in some instances be considered a single separate network node.
  • the network node 900 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 904 for different RATs) and some components may be reused (e.g., a same antenna 910 may be shared by different RATs).
  • the network node 900 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 900, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 900.
  • RFID Radio Frequency Identification
  • the processing circuitry 902 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node 900 components, such as the memory 904, to provide network node 900 functionality.
  • the processing circuitry 902 includes a system on a chip (SOC). In some embodiments, the processing circuitry 902 includes one or more of radio frequency (RF) transceiver circuitry 912 and baseband processing circuitry 914. In some embodiments, the radio frequency (RF) transceiver circuitry 912 and the baseband processing circuitry 914 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 912 and baseband processing circuitry 914 may be on the same chip or set of chips, boards, or units.
  • SOC system on a chip
  • the processing circuitry 902 includes one or more of radio frequency (RF) transceiver circuitry 912 and baseband processing circuitry 914.
  • the radio frequency (RF) transceiver circuitry 912 and the baseband processing circuitry 914 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of
  • the memory 904 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device-readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by the processing circuitry 902.
  • volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-
  • the memory 904 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and/or other instructions capable of being executed by the processing circuitry 902 and utilized by the network node 900.
  • the memory 904 may be used to store any calculations made by the processing circuitry 902 and/or any data received via the communication interface 906.
  • the processing circuitry 902 and memory 904 is integrated.
  • the communication interface 906 is used in wired or wireless communication of signaling and/or data between a network node, access network, and/or UE. As illustrated, the communication interface 906 comprises port(s)/terminal(s) 916 to send and receive data, for example to and from a network over a wired connection.
  • the communication interface 906 also includes radio frontend circuitry 918 that may be coupled to, or in certain embodiments a part of, the antenna 910. Radio front-end circuitry 918 comprises filters 920 and amplifiers 922.
  • the radio front-end circuitry 918 may be connected to an antenna 910 and processing circuitry 902.
  • the radio frontend circuitry may be configured to condition signals communicated between antenna 910 and processing circuitry 902.
  • the radio front-end circuitry 918 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection.
  • the radio front-end circuitry 918 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 920 and/or amplifiers 922.
  • the radio signal may then be transmitted via the antenna 910.
  • the antenna 910 may collect radio signals which are then converted into digital data by the radio front-end circuitry 918.
  • the digital data may be passed to the processing circuitry 902.
  • the communication interface may comprise different components and/or different combinations of components.
  • the network node 900 does not include separate radio front-end circuitry 918, instead, the processing circuitry 902 includes radio front-end circuitry and is connected to the antenna 910. Similarly, in some embodiments, all or some of the RF transceiver circuitry 912 is part of the communication interface 906. In still other embodiments, the communication interface 906 includes one or more ports or terminals 916, the radio front-end circuitry 918, and the RF transceiver circuitry 912, as part of a radio unit (not shown), and the communication interface 906 communicates with the baseband processing circuitry 914, which is part of a digital unit (not shown).
  • the antenna 910 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals.
  • the antenna 910 may be coupled to the radio front-end circuitry 918 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly.
  • the antenna 910 is separate from the network node 900 and connectable to the network node 900 through an interface or port.
  • the power source 908 provides power to the various components of network node 900 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component).
  • the power source 908 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 900 with power for performing the functionality described herein.
  • the network node 900 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 908.
  • the power source 908 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.
  • Embodiments of the network node 900 may include additional components beyond those shown in FIGURE 13 for providing certain aspects of the network node’ s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein.
  • the network node 900 may include user interface equipment to allow input of information into the network node 900 and to allow output of information from the network node 900. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 900.
  • FIGURE 14 is a block diagram illustrating a virtualization environment 1000 in which functions implemented by some embodiments may be virtualized.
  • virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources.
  • virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components.
  • Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 1000 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host.
  • VMs virtual machines
  • the virtual node does not require radio connectivity (e.g., a core network node or host)
  • the node may be entirely virtualized.
  • Applications 1002 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.
  • Hardware 1004 includes processing circuitry, memory that stores software and/or instructions executable by hardware processing circuitry, and/or other hardware devices as described herein, such as a network interface, input/output interface, and so forth.
  • Software may be executed by the processing circuitry to instantiate one or more virtualization layers 1006 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 1008a and 1008b (one or more of which may be generally referred to as VMs 1008), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein.
  • the virtualization layer 1006 may present a virtual operating platform that appears like networking hardware to the VMs 1008.
  • the VMs 1008 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 1006.
  • NFV network function virtualization
  • NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.
  • a VM 1008 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine.
  • Each of the VMs 1008, and that part of hardware 1004 that executes that VM be it hardware dedicated to that VM and/or hardware shared by that VM with others of the VMs, forms separate virtual network elements.
  • a virtual network function is responsible for handling specific network functions that run in one or more VMs 1008 on top of the hardware 1004 and corresponds to the application 1002.
  • Hardware 1004 may be implemented in a standalone network node with generic or specific components. Hardware 1004 may implement some functions via virtualization. Alternatively, hardware 1004 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 1010, which, among others, oversees lifecycle management of applications 1002.
  • hardware 1004 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station.
  • some signaling can be provided with the use of a control system 1012 which may alternatively be used for communication between hardware nodes and radio units.
  • FIGURE 15 illustrates an example method 1100 by a transmitting radio node for RLC transmissions, according to certain embodiments.
  • the method includes at least one of a determining step at 1102 and a taking step at 1104.
  • the transmitting radio node may determine at least one RLC PDU not to be retransmitted by the transmitting radio node.
  • the transmitting radio node may take at least one action to prevent a retransmission of the at least one RLC PDU while the transmitting radio node is in RLC AM.
  • FIGURE 16 illustrates an example method 1200 by a receiving radio node for RLC transmissions, according to certain embodiments.
  • the method includes at least one of a determining step at 1202 and a taking step at 1204
  • the receiving radio node may determine at least one RLC PDU not to be retransmitted by a transmitting radio node to the receiving radio node.
  • the receiving radio node may take at least one action associated with the at least on RLC PDU not to be retransmitted to the receiving radio node.
  • FIGURE 17 illustrates another example method 1300 by a receiving radio node for Radio Link Control (RLC) transmissions, according to certain embodiments.
  • the method includes at least one of a determining step at 1302 and a taking step at 1304.
  • the receiving radio node may determine at least one RLC PDU for which retransmission by a transmitting radio node is not needed.
  • the receiving radio node may take at least one action to prevent the retransmission of the at least one RLC PDU by the transmitting radio node.
  • FIGURE 18 illustrates another example method 1400 by a transmitting radio node for Radio Link Control (RLC) transmissions, according to certain embodiments.
  • the method includes at least one of a determining step at 1402 and a taking step at 1404.
  • the transmitting radio node may determine at least one RLC PDU not to be retransmitted to a receiving radio node.
  • the transmitting radio node may take at least one action to prevent a retransmission of the at least one RLC PDU to a receiving radio node.
  • FIGURE 19 illustrates a method 1500 performed by a receiving radio node 710, 712 for Radio Link Control, RLC, transmissions, according to certain embodiments.
  • the method begins at step 1502 when the receiving radio node 710, 712 receives, from a transmitting node 710, 712, information indicating that at least one RLC PDU is not to be retransmitted by the transmitting radio node.
  • the receiving radio node 710, 712 takes at least one action associated with the at least one RLC PDU not to be retransmitted to the receiving radio node 710, 712, and the at least one action includes updating at least one parameter associated with an RLC receiving window.
  • At least one of the transmitting radio node 710, 712 and the receiving radio node 710, 712 are in RLC AM.
  • taking the at least one action includes transmitting an acknowledgment message to the transmitting node 710, 712.
  • updating the at least one parameter associated with the RLC receiving window includes advancing a lower end of the RLC receiving window forward.
  • taking the at least one action comprises at least one of: discarding the at least one RLC PDU not to be retransmitted; discarding all RLC PDUs that are associated with at least one RLC SDU associated with the at least one RLC PDU not to be retransmitted; considering the at least one RLC PDU as being positively received by the receiving radio node; and transmitting at least one feedback message based on the information.
  • the method includes determining at least one additional packet that has a dependency or association with the at least one RLC PDU and taking the at least one action with regard to the at least one additional packet.
  • the method includes receiving, from a transmitting radio node 710, 712, at least one control or data PDU that indicates and/or is used for determining that the at least one RLC PDU is not to be retransmitted to the receiving radio node 710, 712 and/or that at least one RLC SN associated with the RLC PDU is to be discarded.
  • the at least one control or data PDU indicates at least one of: at least one SN associated with the at least one RLC PDU, at least one lowest SN associated with the at least one RLC PDU, at least one E-field associated with the at least one RLC PDU, a range of SNs associated with the at least one RLC PDU, a range of SNs associated with at least one other RLC PDU, a lower end of the RLC receiving window used for determining RLC PDUs, and at least one bit indicating that at least one SN is included for determining the at least one RLC PDU.
  • the at least one control or data PDU is included in a status PDU.
  • the at least one control or data PDU is at least one control PDU and includes a CPT value
  • the method includes determining, based on the CPT value, that the at least one RLC PDU is not to be retransmitted to the receiving radio node 710, 712 and/or that the at least one RLC SN associated with the RLC PDU is to be discarded.
  • the at least one control or data PDU is a data PDU and comprises at least one bit that indicates or is for determining the at least one RLC PDU that is not to be retransmitted to the receiving radio node 710, 712.
  • the data PDU comprises an Acknowledge Mode Data PDU.
  • the information includes a maximum retransmission threshold and wherein at least one of: the at least one RLC PDU is determined not to be retransmitted when the maximum retransmission threshold is reached and/or exceeded, and the at least one action is taken when the maximum retransmission threshold is reached and/or exceeded.
  • the maximum retransmission threshold is less than a configured maximum RLC AM retransmission used for RLC failure to reestablish RRC connection.
  • the information includes a maximum delay threshold. Additionally, the at least one RLC PDU is determined not to be retransmitted when the maximum delay threshold is reached and/or exceeded, and/or the at least one action is taken when the maximum delay threshold is reached and/or exceeded.
  • the maximum retransmission threshold and/or the maximum delay threshold is associated with a PDU Set Importance level indicating a level of importance of a set of packets of which the at least one RLC PDU is associated.
  • the transmitting radio node 710, 712 determines at least one additional packet has a dependency or association with the at least one RLC PDU and takes the at least one action with regard to the at least one additional packet.
  • the message transmitted to the receiving radio node 710, 712 that indicates that the at least one RLC PDU is not to be retransmitted is control or data PDU.
  • the at least one control or data PDU indicates at least one of: at least one SN associated with the at least one RLC PDU, at least one lowest SN associated with the at least one RLC PDU, at least one E-field associated with the at least one RLC PDU, a range of SNs associated with the at least one RLC PDU, a range of SNs associated with at least one other RLC PDU, a SN associated with a low end of a RLC transmitting window used for determining the at least one RLC PDU, and at least one bit indicating that at least one SN is included for determining the at least one RLC PDU.
  • the at least one control or data PDU is at least one control PDU and comprises a CPT value indicating that the at least one RLC PDU is not to be retransmitted and/or that the at least one RLC SDU associated with the RLC PDU is to be discarded.
  • the at least one control or data PDU is a data PDU and includes at least one bit that indicates or is for determining the at least one RLC PDU that is not to be retransmitted and/or that at least one RLC SDU associated with the RLC PDU is to be discarded.
  • the data PDU comprises an Acknowledge Mode Data PDU.
  • the transmitting radio node 710, 712 receives, from a network node, information for determining that the at least one RLC PDU is not to be retransmitted and/or for determining to take the at least one action.
  • the information includes a maximum retransmission threshold and the at least one RLC PDU is determined not to be retransmitted when the maximum retransmission threshold is reached and/or exceeded and/or the at least one action is taken when the maximum retransmission threshold is reached and/or exceeded.
  • the maximum retransmission threshold is less than a configured maximum RLC AM retransmission used for RLC failure to reestablish RRC connection.
  • the information comprises a maximum delay threshold
  • the at least one RLC PDU is determined not to be retransmitted when the maximum delay threshold is reached and/or exceeded and/or the at least one action is taken when the maximum delay threshold (is reached and/or exceeded.
  • the maximum retransmission threshold and/or the maximum delay threshold is associated with a PDU Set Importance level indicating a level of importance of a set of packets of which the at least one RLC PDU is associated.
  • computing devices described herein may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • processing circuitry may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components.
  • a communication interface may be configured to include any of the components described herein, and/or the functionality of the components may be partitioned between the processing circuitry and the communication interface.
  • non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.
  • processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium.
  • some or all of the functionalities may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner.
  • the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device but are enjoyed by the computing device as a whole, and/or by end users and a wireless network generally.
  • Example Embodiment Al A method performed by a user equipment for flexible Radio Link Control (RLC) transmissions, the method comprising: any of the user equipment steps, features, or functions described above, either alone or in combination with other steps, features, or functions described above.
  • RLC Radio Link Control
  • Example Embodiment A2 The method of the previous embodiment, further comprising one or more additional user equipment steps, features or functions described above.
  • Example Embodiment A3 The method of any of the previous embodiments, further comprising: providing user data; and forwarding the user data to a host computer via the transmission to the network node.
  • Example Embodiment BL A method performed by a network node flexible Radio Link Control (RLC) transmissions, the method comprising: any of the network node steps, features, or functions described above, either alone or in combination with other steps, features, or functions described above.
  • RLC Radio Link Control
  • Example Embodiment B2 The method of the previous embodiment, further comprising one or more additional network node steps, features or functions described above.
  • Example Embodiment B3 The method of any of the previous embodiments, further comprising: obtaining user data; and forwarding the user data to a host or a user equipment.
  • Example Embodiment Cl A method performed by a transmitting radio node for RLC transmissions, the method comprising at least one of: determining at least one RLC PDU not to be retransmitted by the transmitting radio node; and taking at least one action to prevent a retransmission of the at least one RLC PDU to a receiving radio node.
  • Example Embodiment C2 The method of Example Embodiment Cl, wherein at least one of the transmitting radio node and the receiving radio node are in RLC AM.
  • Example Embodiment C3 The method of any one of Example Embodiments Cl to C2, wherein taking the at least one action to prevent the retransmission of the at least one RLC PDU comprises at least one of: determining not to retransmit the at least one RLC PDU based on the information; removing the at least one RLC PDU from a queueing buffer; considering the at least one RLC PDU as being positively received by at least one receiving radio node; and discarding the at least one RLC PDU; stopping at least one ongoing transmission of the at least one RLC PDU; determining not to send an indication to an upper layer of successful delivery of the at least one RLC PDU; and updating at least one parameter associated with a RLC transmitting window.
  • Example Embodiment C4 The method of Example Embodiment C3, wherein updating the at least one parameter associated with the RLC transmitting window comprises advancing a lower end of the RLC transmitting window forward.
  • Example Embodiment C5 The method of any one of Example Embodiments Cl to C4, comprising: determining at least one additional packet has a dependency or association with the at least one RLC PDU; and take the at least one action with regard to the at least one additional packet.
  • Example Embodiment C6 The method of any one of Example Embodiments Cl to C5, wherein taking the at least one action comprises transmitting, to the receiving radio node, at least one control PDU that indicates that the at least one RLC PDU is not to be retransmitted and/or that at least one RLC SDU associated with the RLC PDU is to be discarded.
  • Example Embodiment C7 The method of Example Embodiment C6, wherein the at least one control PDU comprises a Control PDU Type (CPT) value indicating that the at least one RLC PDU is not to be retransmitted and/or that the at least one RLC SDU associated with the RLC PDU is to be discarded.
  • CPT Control PDU Type
  • Example Embodiment C8 The method of any one of Example Embodiments C6 to C7, wherein the at least one control PDU indicates at least one of: at least one SN associated with the at least one RLC PDU, at least one lowest SN associated with the at least one RLC PDU, at least one E-field associated with the at least one RLC PDU, a range of SNs associated with the at least one RLC PDU, a SN associated with a low end of a RLC transmitting window used for determining the at least one RLC PDU, and at least one bit indicating that at least one SN is included for determining the at least one RLC PDU.
  • Example Embodiment C9 The method of any one of Example Embodiments C6 to C8, wherein the at least one control PDU is included in a status PDU.
  • Example Embodiment CIO The method of any one of Example Embodiments Cl to C5, wherein taking the at least one action comprises transmitting, to the receiving radio node, at least one data PDU that indicates and/or is used for determining that the at least one RLC PDU is not to be retransmitted and/or that at least one RLC SDU associated with the RLC PDU is to be discarded.
  • Example Embodiment Cl l The method of Example Embodiment CIO, wherein the data PDU comprises at least one bit indicating or for determining the at least one RLC PDU that is not to be retransmitted and/or that at least one RLC SDU associated with the RLC PDU is to be discarded.
  • Example Embodiment Cl 6 The method of any one of Example Embodiments C14 to C15, wherein the information comprises a maximum retransmission threshold (e.g., R_thresh) and wherein at least one of: the at least one RLC PDU is determined not to be retransmitted when the maximum retransmission threshold (e g., R_thresh)is reached and/or exceeded, and the at least one action is taken when the maximum retransmission threshold (e.g., R_thresh) is reached and/or exceeded.
  • a maximum retransmission threshold e.g., R_thresh
  • Example Embodiment C23 The method of Example Embodiments C22, further comprising: obtaining user data; and forwarding the user data to a host or a user equipment.
  • Example Embodiment C27 A computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments Cl to C23.
  • Example Embodiment C28 A computer program product comprising computer program, the computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments Cl to C23.
  • Example Embodiment C29 A non-transitory computer readable medium storing instructions which when executed by a computer perform any of the methods of Example Embodiments Cl to C3.
  • Example Embodiment DI A method performed by a receiving radio node for RLC transmissions, the method comprising at least one of determining at least one RLC PDU not to be retransmitted by a transmitting radio node to the receiving radio node; and taking at least one action associated with the at least on RLC PDU not to be retransmitted to the receiving radio node.
  • Example Embodiment D2 The method of Example Embodiment Cl, wherein at least one of the transmitting radio node and the receiving radio node are in RLC AM.
  • Example Embodiment D3 The method of any one of Example Embodiments DI to D2, wherein taking the at least one action comprises at least one of: discarding the at least one RLC PDU not to be retransmitted; discarding all RLC PDUs that are associated with the at least one RLC SDU associated with the at least one RLC PDU not to be retransmitted; considering the at least one RLC PDU as being positively received by the receiving radio node; transmitting at least one feedback message based on the information; and updating at least one parameter associated with a RLC receiving window.
  • Example Embodiment D4 The method of Example Embodiment D3, wherein updating the at least one parameter associated with the RLC receiving window comprises advancing a lower end of a RLC receiving window forward.
  • Example Embodiment D5 The method of any one of Example Embodiments DI to D4, comprising: determining at least one additional packet that has a dependency or association with the at least one RLC PDU; and taking the at least one action with regard to the at least one additional packet.
  • Example Embodiment D6 The method of any one of Example Embodiments DI to D5, comprising receiving, from a transmitting radio node, at least one control PDU that indicates and/or is used for determining: that the at least one RLC PDU is not to be retransmitted to the receiving radio node, and/or that at least one RLC SN associated with the RLC PDU is to be discarded.
  • Example Embodiment D7 The method of Example Embodiment D6, wherein the at least one control PDU comprises a Control PDU Type (CPT) value and the method comprises: determining, based on the CPT value, that the at least one RLC PDU is not to be retransmitted to the receiving radio node and/or that the at least one RLC SN associated with the RLC PDU is to be discarded.
  • CPT Control PDU Type
  • Example Embodiment D8 The method of any one of Example Embodiments D6 to D7, wherein the at least one control PDU indicates at least one of: at least one SN associated with the at least one RLC PDU, at least one lowest SN associated with the at least one RLC PDU, at least one E-field associated with the eat least one RLC PDU, a range of SNs associated with the at least one RLC PDU, a range of SNs associated with at least one other RLC PDU, a low end of a RLC window used for determining RLC PDUs, and at least one bit indicating that at least one SN is included for determining the at least one RLC PDU.
  • Example Embodiment D9 The method of any one of Example Embodiments D6 to D8, wherein the at least one control PDU is included in a status PDU.
  • Example Embodiment Dll The method of Example Embodiment DIO, wherein the data PDU comprises at least one bit indicating or for determining the at least one RLC PDU that is not to be retransmitted to the receiving radio node.
  • Example Embodiment D 12 The method of any one of Example Embodiments D 10 to D 11, wherein the data PDU comprises an AMD PDU.
  • Example Embodiment D 13 The method of any one of Example Embodiments DIO to D 12, wherein the at least one data PDU indicates at least one of: at least one SN associated with the at least one RLC PDU, at least one lowest SN associated with the at least one RLC PDU, at least one E-field associated with the eat least one RLC PDU, a range of SNs associated with the at least one RLC PDU, a range of SNs associated with at least one other RLC PDU, a low end of a RLC window used for determining the at least one RLC PDU, and at least one bit indicating that at least one SN is included for determining the at least one RLC PDU.
  • Example Embodiment D 14 The method of any one of Example Embodiments D 1 to D 13, comprising obtaining information for determining the at least one RLC PDU not to be retransmitted and/or for determining to take the at least one action.
  • Example Embodiment D 16 The method of any one of Example Embodiments D 14 to D 15, wherein the information comprises a maximum retransmission threshold (e.g., R_thresh) and wherein at least one of: the at least one RLC PDU is determined not to be retransmitted when the maximum retransmission threshold (e g., R_thresh) is reached and/or exceeded, and the at least one action is taken when the maximum retransmission threshold (e.g., R_thresh) is reached and/or exceeded.
  • a maximum retransmission threshold e.g., R_thresh
  • Example Embodiment DI 7 The method of Example Embodiment D16, wherein the maximum retransmission threshold (e.g., R_thresh) is less than a configured maximum RLC AM retransmission used for RLC failure to reestablish Radio Resource Control (RRC) connection.
  • R_thresh the maximum retransmission threshold
  • RRC Radio Resource Control
  • Example Embodiment DI 9 The method of any one of Example Embodiments D16 to DI 8, wherein the maximum retransmission threshold (e.g., R_thresh) and/or the maximum delay threshold (e.g., L_thr) is associated with a PDU Set Importance (PSI) level indicating a level of importance of a set of packets of which the at least one RLC PDU is associated.
  • the maximum retransmission threshold e.g., R_thresh
  • the maximum delay threshold e.g., L_thr
  • PSI PDU Set Importance
  • Example Embodiment D20 The method of Example Embodiments DI to D19, wherein the receiving radio node comprises a UE.
  • Example Embodiment D21 The method of Example Embodiment D20, further comprising: providing user data; and forwarding the user data to a host via the transmission to the network node.
  • Example Embodiment D22 The method of Example Embodiments DI to DI 9, wherein the transmitting radio node comprises a network node.
  • Example Embodiment D23 The method of Example Embodiment D22, further comprising: obtaining user data; and forwarding the user data to a host or a user equipment.
  • Example Embodiment D24 A receiving radio node comprising processing circuitry configured to perform any of the methods of Example Embodiments DI to D23.
  • Example Embodiment D25 A receiving radio node configured to and/or adapted to perform any of the methods of Example Embodiments DI to D23.
  • Example Embodiment D26 A receiving radio node comprising processing circuitry configured to perform any of the methods of Example Embodiments DI to D23.
  • Example Embodiment D27 A computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments DI to D23.
  • Example Embodiment D28 A computer program product comprising computer program, the computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments DI to D23.
  • Example Embodiment D29 A non-transitory computer readable medium storing instructions which when executed by a computer perform any of the methods of Example Embodiments D 1 to D23.
  • Example Embodiment El A method performed by a receiving radio node for RLC transmissions, the method comprising at least one of: determining at least one RLC PDU for which retransmission by a transmitting radio node is not needed; and taking at least one action to prevent the retransmission of the at least one RLC PDU by the transmitting radio node.
  • Example Embodiment E2 The method of Example Embodiment El, wherein at least one of the receiving radio node and the transmitting radio node are in RLC AM.
  • Example Embodiment E3 The method of any one of Example Embodiments El to E2, wherein taking the at least one action to prevent the retransmission of the at least one RLC PDU comprises at least one of: removing the at least one RLC PDU from a buffer; considering the at least one RLC PDU as being positively received by the receiving radio node; and discarding the at least one RLC PDU; determining not to send an indication to an upper layer of successful reception of the at least one RLC PDU; and updating at least one parameter associated with a RLC receiving window.
  • Example Embodiment E4 The method of Example Embodiment E3, wherein updating the at least one parameter associated with the RLC receiving window comprises advancing a lower end of the RLC receiving window forward.
  • Example Embodiment E7 The method of Example Embodiment E6, wherein the at least one control PDU comprises a Control PDU Type (CPT) value indicating that the at least one RLC PDU is not to be retransmitted and/or that the at least one RLC SN associated with the RLC PDU is to be discarded.
  • CPT Control PDU Type
  • Example Embodiment E8 The method of any one of Example Embodiments E6 to E7, wherein the at least one control PDU indicates at least one of: at least one SN associated with the at least one RLC PDU, at least one lowest SN associated with the at least one RLC PDU, at least one E-field associated with the at least one RLC PDU, a range of SNs associated with the at least one RLC PDU, a range of SNs associated with at least one other RLC PDU, a low end of a RLC receiving window used for determining the at least one RLC PDU, and at least one bit indicating that at least one SN is included for determining the at least one RLC PDU.
  • Example Embodiment E9 The method of any one of Example Embodiments E6 to E8, wherein the at least one control PDU is included in a status PDU.
  • Example Embodiment E10 The method of any one of Example Embodiments El to E9, comprising obtaining information for determining the at least one RLC PDU not to be retransmitted and/or for determining to take the at least one action.
  • Example Embodiment El l The method of Example Embodiment E10, wherein obtaining the information comprises receiving the information from a network node via RRC signaling.
  • Example Embodiment E12 The method of any one of Example Embodiments E10 to El 1, wherein the information comprises a maximum retransmission threshold (e.g., R_thresh) and wherein at least one of: the at least one RLC PDU is determined not to be retransmitted when the maximum retransmission threshold (e g., R_thresh) is reached and/or exceeded, and the at least one action is taken when the maximum retransmission threshold (e.g., R_thresh) is reached and/or exceeded.
  • a maximum retransmission threshold e.g., R_thresh
  • Example Embodiment E13 The method of Example Embodiment E12, wherein the maximum retransmission threshold (e.g., R_thresh) is less than a configured maximum RLC AM retransmission used for RLC failure to reestablish Radio Resource Control (RRC) connection.
  • R_thresh the maximum retransmission threshold
  • RRC Radio Resource Control
  • Example Embodiment E14 The method of any one of Example Embodiments E10 to E13, wherein the information comprises a maximum delay threshold (e.g., L_thr), and wherein at least one of: the at least one RLC PDU is determined not to be retransmitted when the maximum delay threshold (e.g., L thr) is reached and/or exceeded, and the at least one action is taken when the maximum delay threshold (e.g., L_thr) is reached and/or exceeded.
  • a maximum delay threshold e.g., L_thr
  • Example Embodiment El 5 The method of any one of Example Embodiments E12 to E14, wherein the maximum retransmission threshold e.g., R_thresh) and/or the maximum delay threshold (e.g., L_thr) is associated with a PDU Set Importance (PSI) level indicating a level of importance of a set of packets of which the at least one RLC PDU is associated.
  • PDU Set Importance (PSI) level indicating a level of importance of a set of packets of which the at least one RLC PDU is associated.
  • Example Embodiment E16 The method ofExample Embodiments El to E15, wherein the receiving radio node comprises a UE.
  • Example Embodiment E17 The method ofExample Embodiment E16 further comprising: providing user data; and forwarding the user data to a host via the transmission to the network node.
  • Example Embodiment El 8 The method ofExample Embodiments El to El 5, wherein the receiving radio node comprises a network node.
  • Example Embodiment El 9 The method ofExample Embodiment El 8, further comprising: obtaining user data; and forwarding the user data to a host or a user equipment.
  • Example Embodiment E20 A receiving radio node comprising processing circuitry configured to perform any of the methods ofExample Embodiments El to E19.
  • Example Embodiment E21 A receiving radio node configured to and/or adapted to perform any of the methods ofExample Embodiments El to E19.
  • Example Embodiment E22 A receiving radio node comprising processing circuitry configured to perform any of the methods ofExample Embodiments El to E19.
  • Example Embodiment E23 A computer program comprising instructions which when executed on a computer perform any of the methods ofExample Embodiments El to E19.
  • Example Embodiment E24 A computer program product comprising computer program, the computer program comprising instructions which when executed on a computer perform any of the methods ofExample Embodiments El to E19.
  • Example Embodiment E25 A non-transitory computer readable medium storing instructions which when executed by a computer perform any of the methods of Example Embodiments El to E19.
  • Example Embodiment F2 The method of Example Embodiment Fl, wherein at least one of the transmitting radio node and the receiving radio node are in RLC AM.
  • Example Embodiment F3 The method of any one of Example Embodiments Fl to F2, wherein taking the at least one action comprises at least one of: determining not to retransmit the at least one RLC PDU based on the information; removing the at least one RLC PDU from a buffer; considering the at least one RLC PDU as being positively received by the receiving radio node; discarding the at least one RLC PDU; stopping at least one ongoing transmission of the at least one RLC PDU; determining not to send an indication to an upper layer of successful transmission of the at least one RLC PDU; and updating at least one parameter associated with a RLC transmitting window.
  • Example Embodiment F4 The method of Example Embodiment F3, wherein updating the at least one parameter associated with the RLC transmitting window comprises advancing a lower end of a RLC transmitting window forward.
  • Example Embodiment F7 The method of Example Embodiment F6, wherein the at least one control PDU comprises a Control PDU Type (CPT) value indicating that the at least one RLC PDU is not to be retransmitted to the receiving radio node and/or the at least one RLC SN associated with the RLC PDU is to be discarded.
  • CPT Control PDU Type
  • Example Embodiment F8 The method of any one of Example Embodiments F5 to F6, wherein the at least one control PDU indicates at least one of: at least one sequence number associated with the at least one RLC PDU, at least one lowest SN associated with the at least one RLC PDU, at least one E-field associated with the eat least one RLC PDU, a range of SNs associated with the at least one RLC PDU, a range of SNs associated with at least one other RLC PDU, a low end of a RLC window used for determining RLC PDUs, and at least one bit indicating that at least one SN is included for determining the at least one RLC PDU.
  • Example Embodiment F9 The method of any one of Example Embodiments F6 to F8, wherein the at least one control PDU is included in a status PDU.
  • Example Embodiment F 11 The method of Example Embodiment F10, wherein obtaining the information comprises receiving the information from a network node via RRC signaling.
  • Example Embodiment Fl 2 The method of any one of Example Embodiments F10 to Fl 1, wherein the information comprises a maximum retransmission threshold (e.g., R_thresh)and wherein at least one of: the at least one RLC PDU is determined not to be retransmitted when the maximum retransmission threshold (e g., R_thresh) is reached and/or exceeded, and the at least one action is taken when the maximum retransmission threshold (e.g., R_thresh) is reached and/or exceeded.
  • a maximum retransmission threshold e.g., R_thresh
  • Example Embodiment F13 The method of Example Embodiment F12, wherein the maximum retransmission threshold (e.g., R_thresh) is less than a configured maximum RLC AM retransmission used for RLC failure to reestablish Radio Resource Control (RRC) connection.
  • R_thresh the maximum retransmission threshold
  • RRC Radio Resource Control
  • Example Embodiment Fl 4 The method of any one of Example Embodiments F10 to F13, wherein the information comprises a maximum delay threshold (e.g., L_thr), and wherein at least one of: the at least one RLC PDU is determined not to be retransmitted when the maximum delay threshold (e.g., L thr) is reached and/or exceeded, and the at least one action is taken when the maximum delay threshold (e.g., L_thr) is reached and/or exceeded.
  • a maximum delay threshold e.g., L_thr
  • Example Embodiment F 15 The method of any one of Example Embodiments F12 to F14, wherein the maximum retransmission threshold (e.g., R_thresh) and/or the maximum delay threshold (e.g., L_thr) is associated with a PDU Set Importance (PSI) level indicating a level of importance of a set of packets of which the at least one RLC PDU is associated.
  • the maximum retransmission threshold e.g., R_thresh
  • the maximum delay threshold e.g., L_thr
  • PSI PDU Set Importance
  • Example Embodiment Fl 6 The method of Example Embodiments Fl to F15, wherein the transmitting radio node comprises a UE.
  • Example Embodiment F 17 The method ofExample EmbodimentF16, further comprising: providing user data; and forwarding the user data to a host via the transmission to the network node.
  • Example Embodiment Fl 8 The method of Example Embodiments Fl to F15, wherein the transmitting radio node comprises a network node.
  • Example Embodiment F 19 The method of Example Embodiment F 18, further comprising: obtaining user data; and forwarding the user data to a host or a user equipment.
  • Example Embodiment F20 A receiving radio node comprising processing circuitry configured to perform any of the methods of Example Embodiments Fl to Fl 9.
  • Example Embodiment F21 A receiving radio node configured to and/or adapted to perform any of the methods of Example Embodiments Fl to F19.
  • Example Embodiment F22 A receiving radio node comprising processing circuitry configured to perform any of the methods of Example Embodiments Fl to Fl 9.
  • Example Embodiment F23 A computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments Fl to F19.
  • Example Embodiment F24 A computer program product comprising computer program, the computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments Fl to F19.
  • Example Embodiment F25 A non-transitory computer readable medium storing instructions which when executed by a computer perform any of the methods of Example Embodiments Fl to Fl 9.
  • Example Embodiment GE A user equipment for RLC transmissions, the UE comprising: processing circuitry configured to perform any of the steps of any of the Group A, C, D, E, and F Example Embodiments, and power supply circuitry configured to supply power to the processing circuitry.
  • Example Embodiment G2 A network node for RLC transmissions, the network node comprising: processing circuitry configured to perform any of the steps of any of the Group B, C, D, E, and F Example Embodiments; power supply circuitry configured to supply power to the processing circuitry.
  • Example Embodiment G3 A user equipment (UE) for Radio Link Control (RLC) transmissions, the UE comprising: an antenna configured to send and receive wireless signals; radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; the processing circuitry being configured to perform any of the steps of any of the Group A, C, D, E, and F Example Embodiments; an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and a battery connected to the processing circuitry and configured to supply power to the UE.
  • UE Radio Link Control
  • Example Embodiment G4 A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform any of the steps of any of the Group A, C, D, E, and F Example Embodiments to receive the user data from the host.
  • OTT over-the-top
  • Example Embodiment G5 The host of the previous Example Embodiment, wherein the cellular network further includes a network node configured to communicate with the UE to transmit the user data to the UE from the host.
  • Example Embodiment G6 The host of the previous 2 Example Embodiments, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.
  • Example Embodiment G7 A method implemented by a host operating in a communication system that further includes a network node and a user equipment (UE), the method comprising: providing user data for the UE; and initiating a transmission carrying the user data to the UE via a cellular network comprising the network node, wherein the UE performs any of the operations of any of the Group A embodiments to receive the user data from the host.
  • UE user equipment
  • Example Embodiment G9 The method of the previous Example Embodiment, further comprising: at the host, transmitting input data to the client application executing on the UE, the input data being provided by executing the host application, wherein the user data is provided by the client application in response to the input data from the host application.
  • Example Embodiment GIO A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform any of the steps of any of the Group A, C, D, E, and F Example Embodiments to transmit the user data to the host.
  • OTT over-the-top
  • Example Embodiment G11 The host of the previous Example Embodiment, wherein the cellular network further includes a network node configured to communicate with the UE to transmit the user data from the UE to the host.
  • Example Embodiment G12 The host of the previous 2 Example Embodiments, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.
  • Example Embodiment G13 A method implemented by a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: at the host, receiving user data transmitted to the host via the network node by the UE, wherein the UE performs any of the steps of any of the Group A, C, D, E, and F Example Embodiments to transmit the user data to the host.
  • UE user equipment
  • Example Embodiment G14 The method of the previous Example Embodiment, further comprising: at the host, executing a host application associated with a client application executing on the UE to receive the user data from the UE.
  • Example Embodiment G15 The method of the previous Example Embodiment, further comprising: at the host, transmitting input data to the client application executing on the UE, the input data being provided by executing the host application, wherein the user data is provided by the client application in response to the input data from the host application.
  • Example Embodiment G16 A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a network node in a cellular network for transmission to a user equipment (UE), the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B, C, D, E, and F Example Embodiments to transmit the user data from the host to the UE.
  • OTT over-the-top
  • Example Embodiment G17 The host of the previous Example Embodiment, wherein: the processing circuitry of the host is configured to execute a host application that provides the user data; and the UE comprises processing circuitry configured to execute a client application associated with the host application to receive the transmission of user data from the host.
  • Example Embodiment G18 A method implemented in a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: providing user data for the UE; and initiating a transmission carrying the user data to the UE via a cellular network comprising the network node, wherein the network node performs any of the operations of any of the Group B, C, D, E, and F Example Embodiments to transmit the user data from the host to the UE.
  • UE user equipment
  • Example Embodiment G19 The method of the previous Example Embodiment, further comprising, at the network node, transmitting the user data provided by the host for the UE.
  • Example Embodiment G20 The method of any of the previous 2 Example Embodiments, wherein the user data is provided at the host by executing a host application that interacts with a client application executing on the UE, the client application being associated with the host application.
  • Example Embodiment G21 A communication system configured to provide an over-the- top service, the communication system comprising: a host comprising: processing circuitry configured to provide user data for a user equipment GTE), the user data being associated with the over-the-top service; and a network interface configured to initiate transmission of the user data toward a cellular network node for transmission to the UE, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B, C, D, E, and F Example Embodiments to transmit the user data from the host to the UE.
  • a host comprising: processing circuitry configured to provide user data for a user equipment GTE), the user data being associated with the over-the-top service; and a network interface configured to initiate transmission of the user data toward a cellular network node for transmission to the UE, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the
  • Example Embodiment G22 The communication system of the previous Example Embodiment, further comprising: the network node; and/or the user equipment.
  • Example Embodiment G23 A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to initiate receipt of user data; and a network interface configured to receive the user data from a network node in a cellular network, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B, C, D, E, and F Example Embodiments to receive the user data from a user equipment (UE) for the host.
  • OTT over-the-top
  • Example Embodiment G24 The host of the previous 2 Example Embodiments, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.
  • Example Embodiment G25 The host of the any of the previous 2 Example Embodiments, wherein the initiating receipt of the user data comprises requesting the user data.
  • Example Embodiment G26 A method implemented by a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: at the host, initiating receipt of user data from the UE, the user data originating from a transmission which the network node has received from the UE, wherein the network node performs any of the steps of any of the Group B, C, D, E, and F Example Embodiments to receive the user data from the UE for the host.
  • UE user equipment
  • Example Embodiment G27 The method of the previous Example Embodiment, further comprising at the network node, transmitting the received user data to the host.

Landscapes

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

Abstract

Selon l'invention, un procédé (1500) effectué par un nœud radio de réception (710, 712) pour des transmissions RLC consiste à recevoir (1502), en provenance d'un nœud de transmission (710, 712), des informations indiquant qu'au moins une PDU RLC ne doit pas être retransmise par le nœud radio émetteur. Le nœud radio récepteur prend au moins une action (1504) associée à l'au moins une PDU RLC qui ne doit pas être retransmise au nœud radio de réception. Par exemple, la prise de l'au moins une action comprend la mise à jour d'au moins un paramètre associé à une fenêtre de réception RLC.
PCT/SE2025/050086 2024-02-05 2025-02-04 Retransmissions de commande de liaison radio flexibles pour mode acquitté de commande de liaison radio pour des services critiques vis-à-vis du temps Pending WO2025170520A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202463549621P 2024-02-05 2024-02-05
US63/549,621 2024-02-05

Publications (1)

Publication Number Publication Date
WO2025170520A1 true WO2025170520A1 (fr) 2025-08-14

Family

ID=94688014

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2025/050086 Pending WO2025170520A1 (fr) 2024-02-05 2025-02-04 Retransmissions de commande de liaison radio flexibles pour mode acquitté de commande de liaison radio pour des services critiques vis-à-vis du temps

Country Status (1)

Country Link
WO (1) WO2025170520A1 (fr)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210266115A1 (en) * 2017-03-24 2021-08-26 Telefonaktiebolaget Lm Ericsson (Publ) Systems and Methods for Removal of Duplicated Packets for Transmission

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210266115A1 (en) * 2017-03-24 2021-08-26 Telefonaktiebolaget Lm Ericsson (Publ) Systems and Methods for Removal of Duplicated Packets for Transmission

Non-Patent Citations (6)

* Cited by examiner, † Cited by third party
Title
GEUMSAN JO ET AL: "Discussion on the discard for XR", vol. RAN WG2, no. Chicago, US; 20231113 - 20231117, 3 November 2023 (2023-11-03), XP052535695, Retrieved from the Internet <URL:https://www.3gpp.org/ftp/TSG_RAN/WG2_RL2/TSGR2_124/Docs/R2-2313293.zip R2-2313293_Discussion on the discard for XR_r3.DOCX> [retrieved on 20231103] *
JOACHIM LOEHR ET AL: "PSI based discarding operation for XR", vol. RAN WG2, no. Xiamen, CN; 20231009 - 20231013, 28 September 2023 (2023-09-28), XP052529136, Retrieved from the Internet <URL:https://www.3gpp.org/ftp/TSG_RAN/WG2_RL2/TSGR2_123bis/Docs/R2-2310141.zip R2-2310141.docx> [retrieved on 20230928] *
JUHA KORHONEN ET AL: "Report of [AT124][019] PDCP discard (CATT)", vol. RAN WG2, no. Chicago, US; 20231113 - 20231117, 17 November 2023 (2023-11-17), XP052548959, Retrieved from the Internet <URL:https://www.3gpp.org/ftp/TSG_RAN/WG2_RL2/TSGR2_124/Docs/R2-2313923.zip R2-2313923 [AT124][019][XR] PDCP discard.docx> [retrieved on 20231117] *
LI CHEN ET AL: "Discussion on discard operation for XR", vol. RAN WG2, no. Xiamen, CN; 20231009 - 20231013, 29 September 2023 (2023-09-29), XP052528730, Retrieved from the Internet <URL:https://www.3gpp.org/ftp/TSG_RAN/WG2_RL2/TSGR2_123bis/Docs/R2-2309729.zip R2-2309729_Discussion on discard operation for XR.doc> [retrieved on 20230929] *
LI CHEN ET AL: "Enhancement on Transmit/Receipt Operation for PDCP and RLC", vol. RAN WG2, no. Chicago, US; 20231113 - 20231117, 3 November 2023 (2023-11-03), XP052534327, Retrieved from the Internet <URL:https://www.3gpp.org/ftp/TSG_RAN/WG2_RL2/TSGR2_124/Docs/R2-2311909.zip R2-2311909_Enhancement on Transmit and Receipt Operation for PDCP and RLC.doc> [retrieved on 20231103] *
SUDEEP PALAT ET AL: "Support of discard at lower layers", vol. RAN WG2, no. Xiamen, CN; 20231009 - 20231013, 29 September 2023 (2023-09-29), XP052529146, Retrieved from the Internet <URL:https://www.3gpp.org/ftp/TSG_RAN/WG2_RL2/TSGR2_123bis/Docs/R2-2310151.zip R2-2310151_XR_Discard-Lower-Layers.docx> [retrieved on 20230929] *

Similar Documents

Publication Publication Date Title
WO2022264090A1 (fr) Journalisation et notification d&#39;informations spécifiques à un équipement utilisateur aérien
EP4512132A1 (fr) Procédés de gestion de pdu pdcp dans une architecture gnb divisée
EP4360353A1 (fr) Signalisation inter-noeuds pour la configuration d&#39;un rapport de transfert intercellulaire réussi
US20250184285A1 (en) User Plane Traffic Characteristics in a Communication Network
WO2024123231A1 (fr) Détection de réussite et de défaillance d&#39;exécution de mobilité déclenchée par l1/l2 (ltm) par un équipement utilisateur
WO2024232804A1 (fr) Indication de ltm candidat après exécution
WO2025170520A1 (fr) Retransmissions de commande de liaison radio flexibles pour mode acquitté de commande de liaison radio pour des services critiques vis-à-vis du temps
WO2023211357A1 (fr) Sélection de porteuse pour des informations de commande de liaison descendante uniques planifiant de multiples cellules
WO2024035290A1 (fr) Exécution de mobilité intercellulaire l1/l2
EP4490871A1 (fr) États de tci unifiés pour pdsch à multiples trp
CN119654918A (zh) 具有候选du参与的l1/l2小区间移动性执行
WO2024172748A1 (fr) Génération de pdu mac pour de multiples occasions de transmission d&#39;autorisations configurées
EP4666774A1 (fr) Génération de pdu mac pour de multiples occasions de transmission d&#39;autorisations configurées
US20250024319A1 (en) Systems and methods for user equipment assisted buffer size in multi- connectivity
EP4573835A1 (fr) Signalisation d&#39;informations de réalité étendue
WO2025162661A1 (fr) Dispositif radio et procédé dans un réseau de communication sans fil
WO2025162660A1 (fr) Dispositif radio et procédé dans un réseau de communication sans fil
EP4613016A1 (fr) Accès aléatoire pendant cg-sdt
WO2023068988A1 (fr) Gestion de support pour désactivation du scg
WO2024035287A1 (fr) Évitement de situations de concurrence entre mobilité l1/l2 et l3
WO2024019646A1 (fr) Envoi d&#39;une unité de données à un nœud de réseau d&#39;accès radio, et transmission d&#39;une unité de données à un équipement utilisateur
EP4649721A1 (fr) Protection contre des fausses stations de base dans une mobilité déclenchée par l1/l2 (ltm) par un équipement utilisateur
EP4612975A1 (fr) Commutation de cellule de mobilité déclenchée par couche 1/couche 2
WO2025238204A1 (fr) Rapport d&#39;intervalle de numéro de séquence de paquets pour protocole de convergence de données par paquets
WO2025068420A1 (fr) Commutation de trajet sans perte impliquant des relais de liaison latérale

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

Country of ref document: EP

Kind code of ref document: A1