[go: up one dir, main page]

WO2025233001A1 - Rapport d'état de contrôle de liaison radio et retransmission - Google Patents

Rapport d'état de contrôle de liaison radio et retransmission

Info

Publication number
WO2025233001A1
WO2025233001A1 PCT/EP2025/053492 EP2025053492W WO2025233001A1 WO 2025233001 A1 WO2025233001 A1 WO 2025233001A1 EP 2025053492 W EP2025053492 W EP 2025053492W WO 2025233001 A1 WO2025233001 A1 WO 2025233001A1
Authority
WO
WIPO (PCT)
Prior art keywords
pdu
status reporting
rlc
configuration information
receiving device
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/EP2025/053492
Other languages
English (en)
Inventor
Henri Markus Koskinen
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.)
Nokia Technologies Oy
Original Assignee
Nokia Technologies Oy
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nokia Technologies Oy filed Critical Nokia Technologies Oy
Publication of WO2025233001A1 publication Critical patent/WO2025233001A1/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/1854—Scheduling and prioritising arrangements
    • 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/1864—ARQ related signaling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/1607—Details of the supervisory signal
    • H04L1/1642—Formats specially adapted for sequence numbers

Definitions

  • Embodiments of the present disclosure relate to the field of telecommunication and in particular to devices, methods, apparatuses and computer readable storage media for enabling a retransmission and a status reporting by a radio link control (RLC) entity.
  • RLC radio link control
  • a communication network can be seen as a facility that enables communications between two or more communication devices or provides communication devices access to a data network.
  • a mobile or wireless communication network is one example of a communication network.
  • Such communication networks operate by standards promulgated by 3GPP (Third Generation Partnership Project) or ETSI (European Telecommunications Standards Institute). Such standards include the 5G (5th Generation) standard or other standards promulgated by 3GPP.
  • the present embodiments provide reliable data transmission schemes.
  • the present embodiments provide methods to minimize retransmissions.
  • the present embodiments prevent transmitting unintentional or premature NACKs.
  • a receiving device comprising at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the receiving device at least to perform: obtaining configuration information, receiving, from a transmitting device, at least one data protocol data unit, PDU, including at least a portion of a service data unit, SDU, determining whether the at least one data PDU is placed in a reception buffer, triggering a status reporting based on the configuration information and the determination that the at least one data PDU is placed in the reception buffer, generating a control PDU for the status reporting in consideration of whether a prohibit timer has expired or not, the prohibit timer being used to prohibit transmission of the control PDU; and transmitting the control PDU to the transmitting device.
  • the receiving device may be further configured to perform: determining whether the at least one data PDU does not fulfill conditions for discarding the at least one data PDU, before triggering the status reporting.
  • a method comprising steps of obtaining configuration information; receiving, from a transmitting device, at least one data protocol data unit, PDU, including at least a portion of a service data unit, SDU; determining whether the at least one data PDU is placed in a reception buffer; triggering a status reporting based on the configuration information and the determination that the at least one data PDU is placed in the reception buffer; generating a control PDU for the status reporting in consideration of whether a prohibit timer has expired or not, the prohibit timer being used to prohibit transmission of the control PDU; and transmitting the control PDU to the transmitting device.
  • the method may further comprise step of: determining whether the at least one data PDU does not fulfill conditions for discarding the at least one data PDU, before triggering the status reporting.
  • a computer program comprising instructions which, when executed by a receiving device, cause the user device to perform at least the following: obtaining configuration information; receiving, from a transmitting device, at least one data protocol data unit, PDU, including at least a portion of a service data unit, SDU; determining whether the at least one data PDU is placed in a reception buffer; triggering a status reporting based on the configuration information and the determination that the at least one data PDU is placed in the reception buffer; generating a control PDU for the status reporting in consideration of whether a prohibit timer has expired or not, the prohibit timer being used to prohibit transmission of the control PDU; and transmitting the control PDU to the transmitting device.
  • non-transitory computer readable medium comprising instructions which, when executed by a receiving device, cause the receiving device to perform at least the following: obtaining configuration information; receiving, from a transmitting device, at least one data protocol data unit, PDU, including at least a portion of a service data unit, SDU; determining whether the at least one data PDU is placed in a reception buffer; triggering a status reporting based on the configuration information and the determination that the at least one data PDU is placed in the reception buffer; generating a control PDU for the status reporting in consideration of whether a prohibit timer has expired or not, the prohibit timer being used to prohibit transmission of the control PDU; and transmitting the control PDU to the transmitting device.
  • the configuration information may include at least one of: a first indication indicating that an expiry of a reassembly timer does not trigger the status reporting; a second indication indicating that the placing of the at least one data PDU in the reception buffer is to trigger the status reporting; a third indication indicating that the status reporting is to be triggered when the at least one data PDU has not been acknowledged and is within a RLC receiving window; a fourth indication indicating that the status reporting is to be triggered when the at least one data PDU is received after the prohibit timer expires; or a fifth indication indicating that the reassembly timer is set to 0, wherein the reassembly timer is used to detect a loss of data PDU.
  • the control PDU may be generated whenever the prohibit timer is not running.
  • the receiving device may be a user device and the transmission device may be a base station.
  • the configuration information may be obtained from the transmission device via a radio resource control, RRC, message.
  • the receiving device may be a base station and the transmission device may be a user device, and the configuration information may be constructed by the base station.
  • Each of the one or more data PDUs may include a sequence number, SN, field indicative of a sequence number of a corresponding SDU.
  • the control PDU may comprise a status PDU.
  • the configuration information may be related to a Radio Link Control Acknowledged Mode, RLC AM.
  • a receiving device comprising at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the receiving device at least to perform: obtaining configuration information including a threshold value to be used for triggering a status reporting; receiving, from a transmitting device, at least one data protocol data unit, PDU, including at least a portion of a service data unit, SDU; determining that the threshold value is reached; triggering a status reporting based on the configuration information and the determination; generating a control PDU for the status reporting, the control PDU indicating successfully received SDUs; and transmitting the control PDU to the transmitting device.
  • a method performed by a receiving device comprising steps of: obtaining configuration information including a threshold value to be used for triggering a status reporting; receiving, from a transmitting device, at least one data protocol data unit, PDU, including at least a portion of a service data unit, SDU; determining that the threshold value is reached; triggering a status reporting based on the configuration information and the determination; generating a control PDU for the status reporting, the control PDU indicating successfully received SDUs; and transmitting the control PDU to the transmitting device.
  • a computer program comprising instructions which, when executed by a receiving device, cause the receiving device to perform: obtaining configuration information including a threshold value to be used for triggering a status reporting; receiving, from a transmitting device, at least one data protocol data unit, PDU, including at least a portion of a service data unit, SDU; determining that the threshold value is reached; triggering a status reporting based on the configuration information and the determination; generating a control PDU for the status reporting, the control PDU indicating successfully received SDUs; and transmitting the control PDU to the transmitting device.
  • a non-transitory computer readable medium comprising instructions which, when executed by a receiving device, cause the receiving device to perform: obtaining configuration information including a threshold value to be used for triggering a status reporting; receiving, from a transmitting device, at least one data protocol data unit, PDU, including at least a portion of a service data unit, SDU; determining that the threshold value is reached; triggering a status reporting based on the configuration information and the determination; generating a control PDU for the status reporting, the control PDU indicating successfully received SDUs; and transmitting the control PDU to the transmitting device.
  • the configuration information may further include at least one of: a first indication indicating that an expiry of a reassembly timer does not trigger the status reporting; a second indication indicating that the placing of the at least one data PDU in the reception buffer is to trigger the status reporting; a third indication indicating that the status reporting is to be triggered when the at least one data PDU has not been acknowledged and is within a RLC receiving window; a fourth indication indicating that the status reporting is to be triggered when the at least one data PDU is received after a prohibit timer expires, the prohibit timer being used to prohibit transmission of the control PDU; or a fifth indication indicating that the reassembly timer is set to 0, the reassembly timer being used to detect a loss of data PDU.
  • the receiving device may be further configured to: set a counter to count a number of successfully received SDUs up to the threshold value; and reset the counter when the control PDU is transmitted.
  • the receiving device may be a user device and the transmission device may be a base station.
  • the configuration information may be obtained from the transmission device via a radio resource control, RRC, message.
  • the receiving device may be a base station and the transmission device may be a user device.
  • the configuration information may be constructed by the base station.
  • Each of the one or more data PDUs may include a sequence number, SN, field indicative of a sequence number of a corresponding SDU.
  • the control PDU may comprise a status PDU.
  • the configuration information may be related to a Radio Link Control Acknowledged Mode, RLC AM.
  • a transmitting device comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the transmitting device at least to perform: obtaining configuration information; transmitting, to a receiving device, at least one data protocol data unit, PDU, including at least a portion of a service data unit, SDU; receiving a control PDU related to the at least one data PDU, the control PDU including a first SN indicating a first SDU and the first SDU is not positively acknowledged, determining whether to retransmit or not the SDU indicated by the first SN based on the configuration information and the control PDU.
  • a method performed by a transmitting device comprising: obtaining configuration information; transmitting, to a receiving device, at least one data protocol data unit, PDU, including at least a portion of a service data unit, SDU; receiving a control PDU related to the at least one data PDU, the control PDU including a first SN indicating a first SDU and the first SDU is not positively acknowledged; and determining whether to retransmit or not the SDU indicated by the first SN based on the configuration information and the control PDU.
  • a computer program comprising instructions which, when executed by a transmitting device, cause the transmitting device to perform: obtaining configuration information; transmitting, to a receiving device, at least one data protocol data unit, PDU, including at least a portion of a service data unit, SDU; receiving a control PDU related to the at least one data PDU, the control PDU including a first SN indicating a first SDU and the first SDU is not positively acknowledged; and determining whether to retransmit or not the SDU indicated by the first SN based on the configuration information and the control PDU.
  • a non-transitory computer readable medium comprising instructions which, when executed by a transmitting device, cause the transmitting device to perform: obtaining configuration information; transmitting, to a receiving device, at least one data protocol data unit, PDU, including at least a portion of a service data unit, SDU; receiving a control PDU related to the at least one data PDU, the control PDU including a first SN indicating a first SDU and the first SDU is not positively acknowledged; and determining whether to retransmit or not the SDU indicated by the first SN based on the configuration information and the control PDU.
  • the configuration information may include at least one of: a sixth indication indicating that a not positively acknowledged SDU in a middle of SDUs positively acknowledged in a control PDU is not to be considered for retransmission based on the control PDU; a seventh indication indicating that a negative acknowledgment sequence number, NACK_SN, field does not trigger a retransmission; or an eighth indication indicating that a NACK_SN field does not indicate a negative acknowledgement.
  • the control PDU may indicate a positive acknowledgment, ACK, for a second SN and an ACK for a third SN, the first SN being greater than the second SN and less than the third SN.
  • the control PDU may explicitly indicate the ACK for the second SN and the ACK for the third SN.
  • the control PDU may implicitly indicate the ACK for the second SN and the ACK for the third SN.
  • the transmitting device may be a user device and the receiving device may be a base station.
  • the configuration information may be obtained from the receiving device via a radio resource control, RRC, message.
  • the transmitting device may be a base station and the receiving device may be a user device.
  • the configuration information may be constructed by the base station.
  • Each of the one or more data PDUs may include a sequence number, SN, field indicative of a sequence number of a corresponding SDU.
  • the control PDU may comprise a status PDU.
  • the configuration information may be related to a Radio Link Control Acknowledged Mode, RLC AM.
  • FIG. 1 illustrates an example of a wireless communication network
  • FIG. 2 illustrates embodiments to generate configuration information.
  • FIG. 3 illustrates a method for a status reporting scheme at the receiving device, according to embodiments of the disclosure.
  • FIG. 4 illustrates a method for a status reporting scheme at the receiving device, according to the other embodiment of the disclosure.
  • Fig. 5 illustrates a method for an RLC retransmission scheme at the transmitting device, according to embodiments of the disclosure.
  • FIG. 6 illustrates an example of an apparatus.
  • FIG. 7 illustrates an example of an apparatus.
  • references in the present disclosure to "one embodiment,” “an embodiment,” “an example embodiment,” and the like indicate that the embodiment described may include a particular feature, structure, element or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, element or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, element or characteristic in connection with other embodiments whether or not explicitly described.
  • step "in response to A” does not indicate that the step is performed immediately after "A" occurs and one or more intervening steps may be included.
  • circuitry may refer to one or more or all of the following:
  • circuit(s) and or processor(s) such as a microprocessor(s) or a portion of a microprocessor(s), that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation.
  • software e.g., firmware
  • circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and/or firmware.
  • circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit fora mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.
  • the term "communication network” refers to a network following any suitable communication standards, such as New Radio (NR), Long Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed Packet Access (HSPA), Narrow Band Internet of Things (NB-loT) and so on.
  • NR New Radio
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • WCDMA Wideband Code Division Multiple Access
  • HSPA High-Speed Packet Access
  • NB-loT Narrow Band Internet of Things
  • the communications between a terminal device and a network device in the communication network may be performed according to any suitable generation communication protocols, including, but not limited to, the first generation (1G), the second generation (2G), 2.5G, 2.75G, the third generation (3G), the fourth generation (4G), 4.5G, the fifth generation (5G), the sixth generation (6G) communication protocols, and/or any other protocols either currently known or to be developed in the future.
  • suitable generation communication protocols including, but not limited to, the first generation (1G), the second generation (2G), 2.5G, 2.75G, the third generation (3G), the fourth generation (4G), 4.5G, the fifth generation (5G), the sixth generation (6G) communication protocols, and/or any other protocols either currently known or to be developed in the future.
  • Embodiments of the present disclosure may be applied in various communication systems. Given the rapid development in communications, there will of course also be future type communication technologies and systems with which the present disclosure may be embodied. It should not be seen as limiting the scope of the present disclosure to only the aforementioned system.
  • the term "network entity” refers to a node in a communication network via which a user device accesses the network and receives services therefrom.
  • the network entity may refer to a network device, a base station (BS) or an access point (AP), for example, a node B (NodeB or NB), an evolved NodeB (eNodeB or eNB), an NR NB (also referred to as a gNB), a radio access network (RAN) node, a new generation RAN (NG-RAN) node, a Remote Radio Unit (RRU), a radio header (RH), a remote radio head (RRH), a relay, an Integrated Access and Backhaul (IAB) node, a low power node such as a femto, a pico, a non-terrestrial network (NTN) or non-ground network device such as a satellite network device, a low earth orbit (LEO) satellite and a geosynchronous earth orbit (GE)
  • radio access network (RAN) split architecture includes a Centralized Unit (CU) and a Distributed Unit (DU) at an IAB donor node.
  • An IAB node includes a Mobile Terminal (IAB-MT) part that behaves like a UE toward the parent node, and a DU part of an IAB node behaves like a base station toward the next-hop IAB node.
  • IAB-MT Mobile Terminal
  • a terminal device refers to any end device that may be capable of wireless communication.
  • a terminal device may also be referred to as a communication device, user equipment (UE), a Subscriber Station (SS), a Portable Subscriber Station, a Mobile Station (MS), a terminal device or an Access Terminal (AT).
  • UE user equipment
  • SS Subscriber Station
  • MS Mobile Station
  • AT Access Terminal
  • the user device may include, but not limited to, a mobile phone, a cellular phone, a smart phone, voice over IP (VoIP) phones, wireless local loop phones, a tablet, a wearable terminal device, a personal digital assistant (PDA), portable computers, desktop computer, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback appliances, vehicle-mounted wireless terminal devices, wireless endpoints, mobile stations, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), USB dongles, smart devices, wireless customer-premises equipment (CPE), an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and/or other wireless devices operating in an industrial and/or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and/or industrial wireless networks, and the like.
  • VoIP voice over
  • the user device may also correspond to a Mobile Termination (MT) part of an IAB node (e.g., a relay node).
  • MT Mobile Termination
  • IAB node e.g., a relay node
  • the terms “user device”, “communication device”, “terminal”, “terminal device”, “user equipment” and “UE” may be used interchangeably.
  • the term “resource,” “transmission resource,” “resource block,” “physical resource block” (PRB), “uplink resource,” “downlink resource” or “sidelink resource” may refer to any resource for performing a communication, for example, a communication between a user device and a network entity, such as a resource in time domain, a resource in frequency domain, a resource in space domain, a resource in code domain, or any other resource enabling a communication, and the like.
  • a resource in both frequency domain and time domain will be used as an example of a transmission resource for describing some example embodiments of the present disclosure. It is noted that example embodiments of the present disclosure are equally applicable to other resources in other domains.
  • FIG. 1 depicts an example of a simplified wireless communication network showing some physical and logical network entities.
  • the connections shown in FIG. 1 may be physical connections or logical connections. It is apparent to a person skilled in the art that the wireless communication network may also comprise other physical and logical entities than those shown in FIG. 1.
  • the example wireless communication network shown in FIG. 1 includes an access network, such as a radio access network (RAN), and a core network 110.
  • an access network such as a radio access network (RAN)
  • RAN radio access network
  • core network 110 a core network 110.
  • FIG. 1 shows user equipment (UE) 100, 102 configured to be in a wireless connection on one or more communication channels in a radio cell with an access node (AN) 104 of an access network.
  • the AN 104 may be an evolved NodeB (abbreviated as eNB or eNodeB), or a next generation evolved NodeB (abbreviated as ng-eNB), or a next generation NodeB (abbreviated as gNB or gNodeB), providing the radio cell.
  • eNB evolved NodeB
  • ng-eNB next generation evolved NodeB
  • gNB next generation NodeB
  • the wireless connection (e.g., radio link) from a UE to the access node 104 may be called uplink (UL) or reverse link, and the wireless connection (e.g., radio link) from the access node to the UE may be called downlink (DL) or forward link.
  • UE 100 may also communicate directly with UE 102, and vice versa, via a wireless connection generally referred to as a sidelink (SL).
  • SL sidelink
  • the access node 104 or its functionalities may be implemented by using any node, host, server or access point etc. entity suitable for providing such functionalities.
  • the access network may comprise more than one access node, in which case the access nodes may also be configured to communicate with one another over links, wired or wireless. These links between access nodes may be used for sending and receiving control plane signaling and also for routing data from one access node to another access node.
  • the access node may comprise a computing device configured to control the radio resources of the access node.
  • the access node may also be referred to as a network entity, a base station, a base transceiver station (BTS), an access point, a cell site, a radio access node or any other type of node capable of being in a wireless connection with a UE (e.g., UEs 100, 102).
  • the access node may include or be coupled to transceivers. From the transceivers of the access node, a connection may be provided to an antenna unit that establishes bi-directional radio links to UEs 100, 102.
  • the antenna unit may comprise an antenna or antenna element, or a plurality of antennas or antenna elements.
  • the access node 104 may further be connected to a core network (CN) 110.
  • the core network 110 may comprise an evolved packet core (EPC) network and/or a 5th generation core network (5GC).
  • the EPC may comprise network entities, such as a serving gateway (S-GW for routing and forwarding data packets), a packet data network gateway (P- GW) for providing connectivity of UEs to external packet data networks, and a mobility management entity (MME).
  • the 5GC may comprise network functions, such as a user plane function (UPF), an access and mobility management function (AMF), and a location management function (LMF).
  • UPF user plane function
  • AMF access and mobility management function
  • LMF location management function
  • the core network 110 may also be able to communicate with one or more external networks 113, such as a public switched telephone network or the Internet, or utilize services provided by them.
  • external networks 113 such as a public switched telephone network or the Internet
  • the UPF of the core network 110 may be configured to communicate with an external data network via an N6 interface.
  • the P-GW of the core network 110 may be configured to communicate with an external data network.
  • the illustrated UE 100, 102 is one type of an apparatus to which resources on the air interface may be allocated and assigned.
  • the UE 100, 102 may also be called a wireless communication device, a subscriber unit, a mobile station, a remote terminal, an access terminal, a user terminal, a terminal device, or a user device just to mention but a few names.
  • the UE may be a computing device operating with or without a subscriber identification module (SIM), including, but not limited to, the following types of computing devices: a mobile phone, a smartphone, a personal digital assistant (PDA), a handset, a computing device comprising a wireless modem (e.g., an alarm or measurement device, etc.), a laptop computer, a desktop computer, a tablet, a game console, a notebook, a multimedia device, a reduced capability (RedCap) device, a wearable device (e.g., a watch, earphones or eyeglasses) with radio parts, a sensor comprising a wireless modem, or any computing device comprising a wireless modem integrated in a vehicle.
  • SIM subscriber identification module
  • a UE may also be a nearly exclusive uplink-only device, of which an example may be a camera or video camera loading images or video clips to a network.
  • a UE may also be a device having capability to operate in an Internet of Things (loT) network, which is a scenario in which objects may be provided with the ability to transfer data over a network without requiring human-to-human or human-to-computer interaction.
  • the UE may also utilize cloud. In some applications, the computation may be carried out in the cloud or in another UE.
  • the wireless communication network may also be able to support the usage of cloud services, for example at least part of core network operations may be carried out as a cloud service (this is depicted in FIG. 1 by "cloud" 114).
  • the wireless communication network may also comprise a central control entity, or the like, providing facilities for wireless communication networks of different operators to cooperate for example in spectrum sharing.
  • 5G enables using multiple input - multiple output (MIMO) antennas in the access node 104 and/or the UE 100, 102, many more base stations or access nodes than an LTE network (a so-called small cell concept), including macro sites operating in co-operation with smaller stations and employing a variety of radio technologies depending on service needs, use cases and/or spectrum available.
  • 5G wireless communication networks may support a wide range of use cases and related applications including video streaming, augmented reality, different ways of data sharing and various forms of machine type applications, such as (massive) machine-type communications (mMTC), including vehicular safety, different sensors and real-time control.
  • MIMO multiple input - multiple output
  • access nodes and/or UEs may have multiple radio interfaces, namely below 6GHz, cmWave and mmWave, and also being integrable with existing legacy radio access technologies, such as the LTE. Integration with the LTE may be implemented, for example, as a system, where macro coverage may be provided by the LTE, and 5G radio interface access may come from small cells by aggregation to the LTE.
  • a 5G wireless communication network may support both inter- RAT operability (such as LTE-5G) and inter-RI operability (inter-radio interface operability, such as below 6GHz - cmWave - mmWave).
  • One of the concepts considered to be used in 5G wireless communication networks may be network slicing, in which multiple independent and dedicated virtual sub-networks (network instances) may be created within the substantially same infrastructure to run services that have different requirements on latency, reliability, throughput and mobility.
  • an access node may comprise: a radio unit (RU) comprising a radio transceiver (TRX), i.e., a transmitter (Tx) and a receiver (Rx); one or more distributed units (DUs) 105 that may be used for the so-called Layer 1 (LI) processing and real-time Layer 2 (L2) processing; and a central unit (CU) 108 (also known as a centralized unit) that may be used for non-real-time L2 and Layer 3 (L3) processing.
  • the CU 108 may be connected to the one or more DUs 105 for example via an Fl interface.
  • Such an embodiment of the access node may enable the centralization of CUs relative to the cell sites and DUs, whereas DUs may be more distributed and may even remain at cell sites.
  • the CU and DU together may also be referred to as baseband or a baseband unit (BBU).
  • BBU baseband unit
  • the CU and DU may also be comprised in a radio access point (RAP).
  • RAP radio access point
  • the CU 108 may be a logical node hosting radio resource control (RRC), service data adaptation protocol (SDAP) and/or packet data convergence protocol (PDCP), of the NR protocol stack for an access node.
  • the DU 105 may be a logical node hosting radio link control (RLC), medium access control (MAC) and/or physical (PHY) layers of the NR protocol stack for the access node.
  • RLC radio link control
  • MAC medium access control
  • PHY physical layers of the NR protocol stack for the access node.
  • the operations of the DU may be at least partly controlled by the CU. It should also be understood that the distribution of functions between DU 105 and CU 108 may vary depending on implementation.
  • the CU may comprise a control plane (CU-CP), which may be a logical node hosting the RRC and the control plane part of the PDCP protocol of the NR protocol stack for the access node.
  • CU-CP control plane
  • the CU may further comprise a user plane (CU-UP), which may be a logical node hosting the user plane part of the PDCP protocol and the SDAP protocol of the CU for the access node.
  • CU-CP control plane
  • CU-UP user plane
  • Cloud computing systems may also be used to provide the CU 108 and/or DU 105.
  • a CU provided by a cloud computing system may be referred to as a virtualized CU (vCU).
  • vCU virtualized CU
  • vDU virtualized DU
  • the DU may be implemented on so-called bare metal solutions, for example application-specific integrated circuit (ASIC) or customer-specific standard product (CSSP) system-on-a-chip (SoC).
  • ASIC application-specific integrated circuit
  • CSSP customer-specific standard product
  • Edge cloud may be brought into the access network (e.g., RAN) by utilizing network function virtualization (NFV) and software defined networking (SDN).
  • NFV network function virtualization
  • SDN software defined networking
  • Using edge cloud may mean access node operations to be carried out, at least partly, in a computing system operationally coupled to a remote radio head (RRH) or a radio unit (RU) of an access node. It is also possible that access node operations may be performed on a distributed computing system or a cloud computing system located at the access node.
  • Application of cloud RAN architecture enables RAN real-time functions being carried out at the access network (e.g., in a DU 105) and non-real-time functions being carried out in a centralized manner (e.g., in a CU 108).
  • 5G (or new radio, NR) wireless communication networks may support multiple hierarchies, where multi-access edge computing (MEC) servers may be placed between the core network 110 and the access node 104. It should be appreciated that MEC may be applied in LTE wireless communication networks as well.
  • MEC multi-access edge computing
  • a 5G wireless communication network may also comprise a non- terrestrial communication network, such as a satellite communication network, to enhance or complement the coverage of the 5G radio access network.
  • a non- terrestrial communication network such as a satellite communication network
  • satellite communication may support the transfer of data between the 5G radio access network and the core network, enabling more extensive network coverage.
  • Possible use cases may be providing service continuity for machine-to-machine (M2M) or Internet of Things (loT) devices or for passengers on board of vehicles, or ensuring service availability for critical communications, and future railway/maritime/aeronautical communications.
  • M2M machine-to-machine
  • LoT Internet of Things
  • Satellite communication may utilize geostationary earth orbit (GEO) satellite systems, but also low earth orbit (LEO) satellite systems, in particular mega-constellations (systems in which hundreds of (nano)satellites are deployed).
  • GEO geostationary earth orbit
  • LEO low earth orbit
  • a given satellite 106 in the mega-constellation may cover several satellite-enabled network entities that create on-ground cells.
  • the on- ground cells may be created through an on-ground relay access node or by an access node 104 located on-ground or in a satellite.
  • the access node 104 depicted in FIG. 1 is just an example of a part of an access network (e.g., a radio access network) and in practice, the access network may comprise a plurality of access nodes, the UEs 100, 102 may have access to a plurality of radio cells, and the access network may also comprise other apparatuses, such as physical layer relay access nodes or other entities. At least one of the access nodes may be a Home eNodeB or a Home gNodeB.
  • a Home gNodeB or a Home eNodeB is a type of access node that may be used to provide indoor coverage inside a home, office, or other indoor environment.
  • Radio cells may be macro cells (or umbrella cells) which may be large cells having a diameter of up to tens of kilometers, or smaller cells such as micro-, femto- or picocells.
  • the access node(s) of FIG. 1 may provide any kind of these cells.
  • a cellular radio network may be implemented as a multilayer access networks including several kinds of radio cells. In multilayer access networks, one access node may provide one kind of a radio cell or radio cells, and thus a plurality of access nodes may be needed to provide such a multilayer access network.
  • An access network which may be able to use “plug-and-play” access nodes, may include, in addition to Home eNodeBs or Home gNodeBs, a Home Node B gateway, or HNB-GW (not shown in FIG. 1).
  • An HNB-GW which may be installed within an operator's access network, may aggregate traffic from a large number of Home eNodeBs or Home gNodeBs back to a core network of the operator.
  • Radio Resource Control is generally in control of the Radio Link Control (RLC) configuration.
  • RLC Radio Link Control
  • a RLC layer is the sub-layer of the 5G Protocol stack.
  • Packet Data Convergence Protocol (PDCP) layer is present at its top and the Medium Access Control (MAC) layer is present below it.
  • PDCP Packet Data Convergence Protocol
  • MAC Medium Access Control
  • the PDCP layer is connected to the RLC layer via RLC channels, and the RLC layer is connected to the MAC layer via logical channels.
  • RLC sub layer Functions of the RLC sub layer are performed by RLC entities.
  • RLC entity configured at the gNB there is a peer RLC entity configured at the user device (UE) and vice versa.
  • UE user device
  • NR sidelink communication in New Radio (NR) sidelink communication, in NR sidelink discovery, for an RLC entity configured at the transmitting UE, there is a peer RLC entity configured at each receiving UE.
  • NR New Radio
  • An RLC entity may receive/deliver RLC SDUs from/to an upper layer and sends/receives RLC Protocol Data Units (PDUs) to/from its peer RLC entity via lower layers.
  • PDUs RLC Protocol Data Units
  • An RLC PDU can either be an RLC data PDU (shortly, data PDU) or an RLC control PDU (shortly, control PDU). If an RLC entity receives RLC SDUs from upper layer, it receives them through a single RLC channel between RLC and upper layer, and after forming RLC data PDUs from the received RLC SDUs, the RLC entity submits the RLC data PDUs to lower layer through a single logical channel.
  • an RLC entity receives RLC data PDUs from lower layer, it receives them through a single logical channel, and after forming RLC SDUs from the received RLC data PDUs, the RLC entity delivers the RLC SDUs to upper layer through a single RLC channel between RLC and upper layer. If an RLC entity submits/receives RLC control PDUs to/from lower layer, it submits/receives them through the same logical channel it submits/receives the RLC data PDUs through.
  • An RLC entity can be configured to perform data transfer in one of the following three modes: 1) Transparent Mode (TM), 2) Unacknowledged Mode (UM) or 3) Acknowledged Mode (AM). Consequently, an RLC entity is categorized as a TM RLC entity, an UM RLC entity or an AM RLC entity depending on the mode of data transfer that the RLC entity is configured to provide.
  • TM Transparent Mode
  • UM Unacknowledged Mode
  • AM Acknowledged Mode
  • a TM RLC entity is configured either as a transmitting TM RLC entity or a receiving TM RLC entity.
  • the transmitting TM RLC entity receives RLC SDUs from upper layer and sends RLC PDUs to its peer receiving TM RLC entity via lower layers.
  • the receiving TM RLC entity delivers RLC SDUs to upper layer and receives RLC PDUs from its peer transmitting TM RLC entity via lower layers.
  • An UM RLC entity is configured either as a transmitting UM RLC entity or a receiving UM RLC entity.
  • the transmitting UM RLC entity receives RLC SDUs from upper layer and sends RLC PDUs to its peer receiving UM RLC entity via lower layers.
  • the receiving UM RLC entity delivers RLC SDUs to upper layer and receives RLC PDUs from its peer transmitting UM RLC entity via lower layers.
  • An AM RLC entity may comprise a transmitting side (e.g., transmitting device) and/or a receiving side (e.g., receiving device).
  • the transmitting side of an AM RLC entity receives RLC SDUs from upper layer and sends RLC PDUs to its peer AM RLC entity via lower layers.
  • the receiving side of an AM RLC entity delivers RLC SDUs to upper layer and receives RLC PDUs from its peer AM RLC entity via lower layers.
  • the RLC SDUs of variable sizes which are byte aligned (e.g., multiple of 8 bits) are supported for all RLC entity types (i.e. TM, UM and AM RLC entity).
  • Each RLC SDU can be used to construct an RLC PDU without waiting for notification from the lower layer (i.e., by MAC) of a transmission opportunity.
  • an RLC SDU may be segmented and transported using two or more RLC PDUs based on the notification(s) from the lower layer.
  • RLC PDUs are submitted to lower layer only when a transmission opportunity has been notified by lower layer (i.e. by MAC).
  • the transmitting side of an AM RLC entity may generate Acknowledged Mode Data (AMD) PDU(s) for each RLC SDU.
  • the AMD PDU may be referred to a RLC data PDU or a data PDU.
  • the transmitting AM RLC entity shall segment the RLC SDUs, if needed, so that the corresponding AMD PDUs, with RLC headers updated as needed, fit within the total size of RLC PDU(s) indicated by lower layer.
  • the transmitting side of an AM RLC entity supports retransmission of RLC SDUs or RLC SDU segments (e.g., Automatic Repeat request: ARQ):
  • the AM RLC entity can segment the RLC SDU or re-segment the RLC SDU segments into RLC SDU segments;
  • the number of re-segmentation is not limited.
  • an AM RLC entity When the transmitting side of an AM RLC entity forms AMD PDUs from RLC SDUs or RLC SDU segments, it may include relevant RLC headers in the AMD PDU.
  • the AMD PDU comprises a Data field and an AMD PDU header.
  • the AMD PDU header is byte aligned.
  • the AM RLC entity is configured by RRC to use either a 12 bit sequence number (SN ), or a 18 bit SN for the AMD PDU.
  • the length of the AMD PDU header is two and three bytes, respectively.
  • the length of the SN field is 12 bits or 18 bits (configurable) for AMD PDU.
  • the SN field may indicate the sequence number of the corresponding RLC SDU.
  • RLC AM the sequence number is incremented by one for every RLC SDU.
  • RLC UM the sequence number is incremented by one for every segmented RLC SDU.
  • the AMD PDU header may further contain at least one of a data/control (D/C), a Polling (P), a Segment Indication (SI), and/or reserved (R) fields.
  • D/C data/control
  • P Polling
  • SI Segment Indication
  • R reserved
  • An AMD PDU header contains the Segmentation Offset (SO) field only when the Data field consists of an RLC SDU segment which is not the first segment, in which case a 16 bit SO is present.
  • the SI field may have a length of 2 bits.
  • the SI field indicates whether an RLC PDU contains a complete RLC SDU or the first, middle, last segment of an RLC SDU.
  • the D/C field may have a 1 bit length.
  • the D/C field indicates whether the RLC PDU is an RLC data PDU or RLC control PDU.
  • the P field may have a 1 bit length.
  • the P field indicates whether or not the transmitting side of an AM RLC entity requests a STATUS report from its peer AM RLC entity.
  • the R field may have 1 bit length.
  • the R field is a reserved field and the transmitting entity shall set the R field to "0". The receiving entity may ignore this field.
  • the STATUS PDU may comprise a STATUS PDU payload and an RLC control PDU header.
  • RLC control PDU header may comprise a D/C and a Control PDU Type (CPT) field.
  • the CPT field may have a 3 bits length and indicate the type of the RLC control PDU. For example, in case the CPT filed is set as "000", it indicates the status PDU is included in the STATUS PDU payload.
  • the STATUS PDU payload starts from the first bit following the RLC control PDU header, and it may comprise one Acknowledgment SN (ACK_SN) and one Extension bit 1 (El) field, zero or more sets of a Negative Acknowledgement SN (NACK_SN), an El, an Extension bit 2 (E2) and an Extension bit 3 (E3), and possibly a pair of a Sequence Offset start (SOstart) and a Sequence Offset end (SOend) or a NACK range field for each NACK_SN.
  • ACK_SN Acknowledgment SN
  • El Extension bit 1
  • E3 Extension bit 3
  • the ACK_SN field may have a length of 12 bits or 18 bits (configurable).
  • the ACK_SN field may indicate the SN of the next not received RLC SDU which is not reported as missing in the STATUS PDU.
  • the El field may indicate whether or not a set of NACK_SN, El, E2 and E3 follows.
  • the E2 field may indicates whether or not a set of SOstart and SOend follows.
  • the E3 field may indicate whether or not information about a continous sequence of RLC SDUs that have not been received follows.
  • the NACK_SN field may have a length of 12 bits or 18 bits (configurable).
  • the NACK_SN field indicates the SN of the RLC SDU (or RLC SDU segment) that has been detected as lost at the receiving side of the AM RLC entity.
  • the NACK range field may have a length of 8 bits.
  • the NACK range field indicates the number of consecutively lost RLC SDUs starting from and including NACK_SN.
  • the STATUS PDU provides ACK/NACK feedback from an RLC entity receiving data to the one transmitting it.
  • the Status PDU includes the ACK_SN field, which indicates the lowest SN of an RLC SDU that is not yet received but not NACKed either (because lower-layer transmission may still be underway). Additionally, the Status PDU may contain the NACK_SN fields indicating SNs not exceeding the ACK_SN, of SDUs or segments thereof that are NACKed. The SDUs with SN below the ACK_SN and not indicated as NACKed are implicitly ACKed.
  • This variable may progress past SNs of missing SDUs based on the t-Reassembly timer.
  • the t-reassembly timer is started when an SDU with SN greater than that of a nonreceived SDU is received, and only once the timer expires, RX_Highest_Status is updated past the SN of the non-received SDU. Expiry of the timer also triggers status reporting, i.e. generating and sending a Status PDU upon the next allowed opportunity.
  • the RLC NACKs may not be fast enough trigger for RLC retransmissions.
  • the retransmissions could be "blind” such that a given RLC SDU is retransmitted when a certain time period has elapsed since its initial transmission unless it has been positively acknowledged (ACKed).
  • ACKs for non-consecutive SNs of RLC SDUs can only be indicated if the SNs between them are negatively acknowledged (NACKed).
  • received NACKs always trigger retransmission. For instance, even if a blind retransmission of the same SDU has just taken place.
  • t-Reassembly timer Besides, sending NACKs (and in their presence also ACKs) is governed and delayed by the t-Reassembly timer. While the duration of t-Reassembly timer can be configured as 0 to expedite the ACKs, that also leads to immediate NACKing of missing SDUs.
  • the embodiments propose the methods, apparatus and/or computer programs for optimized status reporting and retransmitting the SDUs.
  • FIG. 2 illustrates embodiments to generate configuration information.
  • FIG. 2 depicts one user device 100 and one network device 104, two or more user devices and/or two or more network devices may be deployed.
  • the network device 104 may be referred to as a base station, gNB, or gNB-DU.
  • the user device 100 may be a receiving device and the network device 104 may be a transmitting device for a downlink data transmission. Meanwhile the user device 100 may be a transmitting device and the network device 104 may be a receiving device for an uplink data transmission.
  • the network device 104 obtains an indication of QoS requirements for a data flow (S210).
  • the indication of QoS requirements may be received by a gNB-DU from a gNB-CU in e.g. an F1AP UE CONTEXT SETUP REQUEST message, or by a gNB from an AMF in e.g. an NGAP INITIAL CONTEXT SETUP REQUEST message or an NGAP PDU SESSION RESOURCE SETUP REQUEST message.
  • the network device 104 generates configuration information indicating new configurable properties for RLC entities.
  • the configuration information may be generated based on the indication of the QoS requirements (S220).
  • the network device 104 transmits the configuration information to the user device 100.
  • the configuration information may be transmitted to the user device as an unicast manner via a RRC message, a group cast or a broadcast manner (S230).
  • the configurable properties for the RLC entities may be at least one of:
  • - NACK_SN field in a received Status PDU may not trigger retransmission (this means the status PDU is used only to convey ACKs while allowing using the existing PDU formats including the status PDU, minimizing specification impact);
  • - Status reporting may be periodical in terms of time (this may mean that a status PDU is generated and sent whenever the current timer t-StatusProhibit is not running).
  • a further necessary condition may be that new data (i.e. not yet ACKed data within the RLC receiving window) has been received since the previously sent Status PDU; if t-StatusProhibit expires before new data arrives, the new data triggers status reporting;
  • Status reporting may be event triggered in terms of threshold value of a new counter (this may mean in case of new SDUs are successfully received, status reporting may be triggered whenever the new counter reaches a threshold value).
  • the counter may be SDU_WITHOUT_ACKS and the counter may be reset whenever the status PDU is sent.
  • the counter may be incremented for every new received (completely) SDU;
  • - t-reassembly timer may be configured to '0' to prevent missing SDUs from delaying the positive acknowledgement.
  • the configurable properties for the RLC entities may be indicated by indicators.
  • the configuration information may include at least one of:
  • a first indication indicating that an expiry of a reassembly timer (e.g., T- Reassembly timer) does not trigger the status reporting
  • a second indication indicating that the placing of the at least one data PDU in the reception buffer is to trigger the status reporting
  • NACK_SN negative acknowledgment sequence number
  • the above configurable properties may be indicated jointly as a RRC-configured parameter 'ACKOnlyOperation'.
  • FIG. 3 illustrates a method for a status reporting scheme at the receiving device, according to embodiments of the disclosure.
  • the receiving device obtains configuration information (S310).
  • the configuration information may be received from the transmitting device (S305). If the receiving device is the network device 100, the network device may generate or construct the configuration information.
  • the configuration information may be referred to that of FIG. 2.
  • the receiving device receives, from a transmitting device, at least one data protocol data unit (PDU) including at least a portion of a service data unit (SDU) (S320).
  • PDU data protocol data unit
  • SDU service data unit
  • the receiving device determines whether the at least one data PDU (or, at least one SDU) is placed in a reception buffer (S330). Only a data PDU (or, a SDU included in the data PDU) may be placed in the reception buffer when it is successfully received by the receiving device.
  • the receiving device triggers a status reporting based on the configuration information and the determination that the at least one data PDU is placed in the reception buffer (S340).
  • the receiving device generates a control PDU for the status reporting in consideration of whether a prohibit timer has expired or not (S350).
  • the prohibit timer may be used to prohibit transmission of the control PDU.
  • the prohibit timer may be referred to as a t-StatusProhibit timer.
  • the receiving device transmits the generated control PDU to the transmitting device (S360).
  • the receiving device may further be configured to perform determining whether the at least one data PDU does not fulfill conditions for discarding the at least one data PDU, before triggering the status reporting.
  • the configuration information may include at least one of a first indication indicating that an expiry of a reassembly timer (e.g., T-Reassembly timer) does not trigger the status reporting, a second indication indicating that the placing of the at least one data PDU in the reception buffer is to trigger the status reporting, a third indication indicating that the status reporting is to be triggered when the at least one data PDU has not been acknowledged and is within a RLC receiving window, a fourth indication indicating that the status reporting is to be triggered when the at least one data PDU is received after the prohibit timer expires or a fifth indication indicating that the reassembly timer is set to 0, wherein the reassembly timer is used to detect a loss of data PDU.
  • the at least one of the indications may be informed by a parameter, ACKOnlyOperation.
  • control PDU may be generated whenever the prohibit timer is not running.
  • the receiving device may be a user device and the transmission device may be a base station, and the configuration information is obtained from the transmission device via a radio resource control (RRC) message.
  • RRC radio resource control
  • the receiving device may be a base station and the transmission device is a user device, and the configuration information may be constructed by the base station.
  • each of the one or more data PDUs may include a sequence number (SN) field indicative of a sequence number of a corresponding SDU.
  • SN sequence number
  • control PDU may comprise a status PDU.
  • the configuration information may be related to a Radio Link Control Acknowledged Mode (RLC AM).
  • RLC AM Radio Link Control Acknowledged Mode
  • FIG. 4 illustrates a method for a status reporting scheme at the receiving device, according to the other embodiment of the disclosure.
  • the receiving device obtains configuration information including a threshold value to be used for triggering a status reporting (S410).
  • the configuration information may be received from the transmitting device (S405). If the receiving device is the network device 100, the network device may generate or construct the configuration information.
  • the configuration information may be referred to that of FIG. 2.
  • the receiving device receives, from a transmitting device, at least one data protocol data unit (PDU) including at least a portion of a service data unit (SDU) (S420).
  • PDU data protocol data unit
  • SDU service data unit
  • the receiving device determines whether the threshold value is reached or not.
  • the receiving device may determine that the threshold value is reached by using a counter.
  • the counter value may be set to '0' and incremented by 1 per each of new reception of the SDU (or data PDU) (S430).
  • the receiving device triggers a status reporting based on the configuration information and the determination of S430 (S440).
  • the receiving device generates a control PDU for the status reporting.
  • the control PDU may indicate successfully received SDUs (S450).
  • the receiving device transmits the generated control PDU to the transmitting device (S460).
  • the configuration information may include at least one of a first indication indicating that an expiry of a reassembly timer (e.g., T-Reassembly timer) does not trigger the status reporting, a second indication indicating that the placing of the at least one data PDU in the reception buffer is to trigger the status reporting, a third indication indicating that the status reporting is to be triggered when the at least one data PDU has not been acknowledged and is within a RLC receiving window, a fourth indication indicating that the status reporting is to be triggered when the at least one data PDU is received after the prohibit timer expires or a fifth indication indicating that the reassembly timer is set to 0, wherein the reassembly timer is used to detect a loss of data PDU.
  • the at least one of the indications may be informed by a parameter, ACKOnlyOperation.
  • the receiving device may be further configured to set a counter to count a number of successfully received SDUs up to the threshold value and reset the counter when the control PDU is transmitted.
  • control PDU may be generated whenever the prohibit timer is not running.
  • the receiving device may be a user device and the transmission device may be a base station, and the configuration information is obtained from the transmission device via a radio resource control (RRC) message.
  • RRC radio resource control
  • the receiving device may be a base station and the transmission device is a user device, and the configuration information may be constructed by the base station.
  • each of the one or more data PDUs may include a sequence number (SN) field indicative of a sequence number of a corresponding SDU.
  • SN sequence number
  • control PDU may comprise a status PDU.
  • configuration information may be related to a
  • Radio Link Control Acknowledged Mode (RLC AM).
  • Fig. 5 illustrates a method for an RLC retransmission scheme at the transmitting device, according to embodiments of the disclosure.
  • the transmitting device obtains configuration information (S510).
  • the configuration information may be received from the receiving device (S505).
  • the transmitting device is the network device 100, the network device may generate or construct the configuration information.
  • the configuration information may be referred to that of FIG. 2.
  • the transmitting device transmits, to a receiving device, at least one data protocol data unit (PDU) including at least a portion of a service data unit (SDU) (S520).
  • PDU data protocol data unit
  • SDU service data unit
  • the data PDU of S520 may contain a header field indicating the SN of a SDU and data payload containing the SDU indicated by the SN.
  • the transmitting device receives a control PDU related to the at least one data PDU.
  • the control PDU may include a first SN indicating a first SDU and the first SDU is not positively acknowledged (S530).
  • the control PDU of S530 may indicate that the first SDU is not positively acknowledged.
  • the control PDU of S530 may identify a first SDU, and the control PDU may indicate the first SDU is not positively acknowledged.
  • the transmitting device determines whether to trigger retransmission of the SDU that has been indicated by the first SN, based on the configuration information and the control PDU (S540).
  • the transmitting device decided to retransmit the SDU indicated by the control PDU, then it retransmits the SDU.
  • the retransmitted SDU may be transmitted in a data PDU (S550).
  • the configuration information includes at least one of a sixth indication indicating that a not positively acknowledged SDU in a middle of SDUs positively acknowledged in a control PDU is not to be considered for retransmission based on the control PDU, a seventh indication indicating that a negative acknowledgment sequence number, NACK_SN, field does not trigger a retransmission, or an eighth indication indicating that a NACK_SN field does not indicate a negative acknowledgement.
  • the control PDU may indicate a positive acknowledgment (ACK) for a second SN and an ACK for a third SN.
  • the first SN may be greater than the second SN and less than the third SN.
  • the control PDU may indicate ACK for the second and the third SNs and not indicate ACK for the first SN.
  • the first SN may be greater than the second SN and less than the third SN.
  • control PDU may explicitly indicate the ACK for the second SN and the ACK for the third SN.
  • control PDU may include at least one SN field indicating at least one SDU corresponding to the at least one SN field.
  • control PDU may implicitly indicate the ACK for the second SN and the ACK for the third SN.
  • control PDU may leave the second SN and the third SN without explicit indications, and the control PDU may be defined such that if an SN is not explicitly indicated, it means an implicitly indicated ACK.
  • the transmitting device may be a user device and the receiving device may be a base station.
  • the configuration information may be obtained from the receiving device via the RRC message.
  • the transmitting device may be a base station and the receiving device may be a user device.
  • the configuration information may be constructed by the base station.
  • each of the one or more data PDUs includes a sequence number (SN) field indicative of a sequence number of a corresponding SDU.
  • SN sequence number
  • control PDU may comprise a status PDU.
  • the configuration information may be related to a Radio Link Control Acknowledged Mode (RLC AM).
  • RLC AM Radio Link Control Acknowledged Mode
  • FIG. 6 illustrates an example of an apparatus 600 comprising means for performing one or more of the example embodiments described above.
  • the apparatus 600 may be, or comprise, or be comprised in, the user device 100.
  • the apparatus 600 may comprise a circuitry or a chipset applicable for realizing one or more of the example embodiments described above.
  • the apparatus 600 may comprise at least one processor 610.
  • the at least one processor 610 interprets instructions (e.g., computer program instructions) and processes data.
  • the at least one processor 610 may comprise one or more programmable processors.
  • the at least one processor 610 may comprise programmable hardware with embedded firmware and may, alternatively or additionally, comprise one or more application-specific integrated circuits (ASICs).
  • ASICs application-specific integrated circuits
  • the at least one processor 610 is coupled to at least one memory 620.
  • the at least one processor is configured to read and write data to and from the at least one memory 620.
  • the at least one memory 620 may comprise one or more memory units.
  • the memory units may be volatile or non-volatile. It is to be noted that there may be one or more units of nonvolatile memory and one or more units of volatile memory or, alternatively, one or more units of non-volatile memory, or, alternatively, one or more units of volatile memory.
  • Volatile memory may be for example random-access memory (RAM), dynamic random-access memory (DRAM) or synchronous dynamic random-access memory (SDRAM).
  • Non-volatile memory may be for example read-only memory (ROM), programmable read-only memory (PROM), electronically erasable programmable read-only memory (EEPROM), flash memory, optical storage or magnetic storage.
  • ROM read-only memory
  • PROM programmable read-only memory
  • EEPROM electronically erasable programmable read-only memory
  • flash memory optical storage or magnetic storage.
  • memories may be referred to as non- transitory computer readable media.
  • non-transitory is a limitation of the medium itself (i.e., tangible, not a signal) as opposed to a limitation on data storage persistency (e.g., RAM vs. ROM).
  • the at least one memory 620 stores computer readable instructions that are executed by the at least one processor 610 to perform one or more of the example embodiments described above.
  • non-volatile memory stores the computer readable instructions
  • the at least one processor 610 executes the instructions using volatile memory for temporary storage of data and/or instructions.
  • the computer readable instructions may refer to computer program code.
  • the computer programs or the computer readable instructions may have been prestored to the at least one memory 620 or, alternatively or additionally, they may be received, by the apparatus, via an electromagnetic carrier signal and/or may be copied from a physical entity such as a computer program product.
  • Execution of the computer readable instructions by the at least one processor 610 causes the apparatus 600 to perform one or more of the example embodiments described above (e.g., FIGs. 1 to 5). That is, the at least one processor and the at least one memory storing the instructions may provide the means for providing or causing the performance of any of the methods, steps and/or blocks of FIGs. I to 5.
  • a "memory” or “computer-readable media” or “computer-readable medium” may be any non-transitory media or medium or means that can contain, store, communicate, propagate or transport the instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer.
  • the non-transitory computer readable medium may comprise program instructions which, when executed by an apparatus, cause the apparatus to perform the methods or the steps of FIGs. 2 to 5.
  • the apparatus 600 may further comprise, or be connected to, an input unit 630.
  • the input unit 630 may comprise one or more interfaces for receiving input.
  • the one or more interfaces may comprise for example one or more temperature, motion and/or orientation sensors, one or more cameras, one or more accelerometers, one or more microphones, one or more buttons and/or one or more touch detection units.
  • the input unit 630 may comprise an interface to which external devices may connect to.
  • the apparatus 600 may also comprise an output unit 640.
  • the output unit may comprise or be connected to one or more displays capable of rendering visual content, such as a light emitting diode (LED) display, a liquid crystal display (LCD) and/or a liquid crystal on silicon (LCoS) display.
  • the output unit 640 may further comprise one or more audio outputs.
  • the one or more audio outputs may be for example loudspeakers.
  • the apparatus 600 further comprises a connectivity unit 650.
  • the connectivity unit 650 enables wireless connectivity to one or more external devices.
  • the connectivity unit 650 comprises at least one transmitter and at least one receiver that may be integrated to the apparatus 600 or that the apparatus 600 may be connected to.
  • the at least one transmitter comprises at least one transmission antenna, and the at least one receiver comprises at least one receiving antenna.
  • the connectivity unit 650 may comprise an integrated circuit or a set of integrated circuits that provide the wireless communication capability for the apparatus 600.
  • the wireless connectivity may be a hardwired application-specific integrated circuit (ASIC).
  • ASIC application-specific integrated circuit
  • the connectivity unit 650 may also provide means for performing at least some of the blocks or functions of one or more example embodiments described above.
  • the connectivity unit 650 may comprise one or more components, such as: power amplifier, digital front end (DFE), analog-to-digital converter (ADC), digital-to-analog converter (DAC), frequency converter, (de)modulator, and/or encoder/decoder circuitries, controlled by the corresponding controlling units.
  • DFE digital front end
  • ADC analog-to-digital converter
  • DAC digital-to-analog converter
  • frequency converter frequency converter
  • demodulator demodulator
  • encoder/decoder circuitries controlled by the corresponding controlling units.
  • the apparatus 600 may further comprise various components not illustrated in FIG. 6.
  • the various components may be hardware components and/or software components.
  • FIG. 7 illustrates an example of an apparatus 700 comprising means for performing one or more of the example embodiments described above.
  • the apparatus 700 may be an apparatus such as, or comprising, or comprised in, the network node 104 or the network entity, and support the embodiments and examples described above.
  • the network node 104 may also be referred to, for example, as a network element, a next generation radio access network (NG-RAN) node, a NodeB, an eNB, a gNB, a base transceiver station (BTS), a base station, an NR base station, a 5G base station, an access node, an access point (AP), a cell site, a relay node, a repeater, an integrated access and backhaul (IAB) node, an IAB donor node, a distributed unit (DU), a central unit (CU), a baseband unit (BBU), a radio unit (RU), a radio head, a remote radio head (RRH), or a transmission and reception point (TRP).
  • NG-RAN next generation radio access network
  • NodeB an eNB
  • a gNB base transceiver station
  • BTS base transceiver station
  • a base station an NR base station
  • 5G base station 5G base station
  • the apparatus 700 may comprise, for example, a circuitry or a chipset applicable for realizing one or more of the example embodiments described above.
  • the apparatus 700 may be an electronic device comprising one or more electronic circuitries.
  • the apparatus 700 may comprise a communication control circuitry 710 such as at least one processor, and at least one memory 720 storing instructions 722 which, when executed by the at least one processor, cause the apparatus 700 to carry out one or more of the example embodiments described above.
  • Such instructions 722 may, for example, include computer program code (software).
  • the at least one processor and the at least one memory storing the instructions may provide the means for providing or causing the performance of any of the methods and/or blocks described above.
  • the processor is coupled to the memory 720.
  • the processor is configured to read and write data to and from the memory 720.
  • the memory 720 may comprise one or more memory units.
  • the memory units may be volatile or non-volatile. It is to be noted that there may be one or more units of non-volatile memory and one or more units of volatile memory or, alternatively, one or more units of non-volatile memory, or, alternatively, one or more units of volatile memory.
  • Volatile memory may be for example random-access memory (RAM), dynamic random-access memory (DRAM) or synchronous dynamic random-access memory (SDRAM).
  • Non-volatile memory may be for example read-only memory (ROM), programmable read-only memory (PROM), electronically erasable programmable read-only memory (EEPROM), flash memory, optical storage or magnetic storage.
  • ROM read-only memory
  • PROM programmable read-only memory
  • EEPROM electronically erasable programmable read-only memory
  • flash memory optical storage or magnetic storage.
  • memories may be referred to as non-transitory computer readable media.
  • non-transitory is a limitation of the medium itself (i.e., tangible, not a signal) as opposed to a limitation on data storage persistency (e.g., RAM vs. ROM).
  • the memory 720 stores computer readable instructions that are executed by the processor.
  • non-volatile memory stores the computer readable instructions, and the processor executes the instructions using volatile memory for temporary storage of data and/or instructions.
  • the computer readable instructions may have been pre-stored to the memory 720 or, alternatively or additionally, they may be received, by the apparatus, via an electromagnetic carrier signal and/or may be copied from a physical entity such as a computer program product. Execution of the computer readable instructions causes the apparatus 700 to perform one or more of the functionalities described in FIGs 1 to 5.
  • the memory 720 may be implemented using any suitable data storage technology, such as semiconductor-based memory devices, flash memory, magnetic memory devices and systems, optical memory devices and systems, fixed memory and/or removable memory.
  • the memory may comprise a configuration database for storing configuration data, such as the configurable properties explained in Fig. 2.
  • a non-transitory computer readable medium may be provided.
  • the non-transitory computer readable medium may comprise program instructions which, when executed by an apparatus, cause the apparatus to perform at least the steps or methods explained by FIGs. 1 to 5.
  • the apparatus 700 may further comprise or be connected to a communication interface 730, such as a radio unit, comprising hardware and/or software for realizing communication connectivity with one or more wireless communication devices according to one or more communication protocols.
  • the communication interface 730 comprises at least one transmitter (Tx) and at least one receiver (Rx) that may be integrated to the apparatus 700 or that the apparatus 700 may be connected to.
  • the communication interface 730 may provide means for performing some of the blocks for one or more example embodiments described above.
  • the communication interface 730 may comprise one or more components, such as: power amplifier, digital front end (DFE), analog-to-digital converter (ADC), digital-to-analog converter (DAC), frequency converter, (de)modulator, and/or encoder/decoder circuitries, controlled by the corresponding controlling units.
  • DFE digital front end
  • ADC analog-to-digital converter
  • DAC digital-to-analog converter
  • frequency converter frequency converter
  • demodulator demodulator
  • encoder/decoder circuitries controlled by the corresponding controlling units.
  • the communication interface 730 provides the apparatus with radio communication capabilities to communicate in the wireless communication network.
  • the communication interface may, for example, provide a radio interface to one or more wireless communication devices.
  • the apparatus 700 may further comprise or be connected to another interface towards a core network such as the network coordinator apparatus or AMF, and/or to the access nodes of the wireless communication network.
  • the apparatus 700 may further comprise a scheduler 740 that is configured to allocate radio resources.
  • the scheduler 740 may be configured along with the communication control circuitry 710 or it may be separately configured.
  • the apparatus 700 may further comprise various components not illustrated in FIG. 7.
  • the various components may be hardware components and/or software components.
  • the apparatus 700 may perform or be applied with the embodiments described above. More specifically, the apparatus 700 may be the network device 104, and the network device 104 may be configured to perform the methods explained by using FIGs 1 to 5.
  • the techniques and methods described herein may be implemented by various means. For example, these techniques may be implemented in hardware (one or more devices), firmware (one or more devices), software (one or more modules), or combinations thereof.
  • the apparatus(es) of example embodiments may be implemented within one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), graphics processing units (GPUs), processors, controllers, micro-controllers, microprocessors, other electronic units designed to perform the functions described herein, or a combination thereof.
  • ASICs application-specific integrated circuits
  • DSPs digital signal processors
  • DSPDs digital signal processing devices
  • PLDs programmable logic devices
  • FPGAs field programmable gate arrays
  • GPUs graphics processing units
  • processors controllers, micro-controllers, microprocessors, other electronic units designed to perform the functions described herein, or a combination
  • the implementation can be carried out through modules of at least one chipset (for example procedures, functions, and so on) that perform the functions described herein.
  • the software codes may be stored in a memory unit and executed by processors.
  • the memory unit may be implemented within the processor or externally to the processor. In the latter case, it can be communicatively coupled to the processor via various means, as is known in the art.
  • the components of the systems described herein may be rearranged and/or complemented by additional components in order to facilitate the achievements of the various aspects, etc., described with regard thereto, and they are not limited to the precise configurations set forth in the given figures, as will be appreciated by one skilled in the art.

Landscapes

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

Abstract

La présente divulgation se rapporte au domaine de la télécommunication. Par exemple, la présente divulgation concerne un dispositif de réception comprenant au moins un processeur ; et au moins une mémoire stockant des instructions qui, lorsqu'elles sont exécutées par le ou les processeurs, amènent le dispositif de réception au moins à effectuer les actions suivantes consistant à : obtenir des informations de configuration comprenant une valeur de seuil à utiliser pour déclencher un rapport d'état ; recevoir, en provenance d'un dispositif de transmission, au moins une unité de données de protocole de données, PDU, comprenant au moins une partie d'une unité de données de service, SDU ; déterminer que la valeur de seuil est atteinte ; déclencher un rapport d'état sur la base des informations de configuration et de la détermination ; générer une PDU de commande pour le rapport d'état, la PDU de commande indiquant des SDU reçues avec succès ; et transmettre la PDU de commande au dispositif de transmission.
PCT/EP2025/053492 2024-05-08 2025-02-11 Rapport d'état de contrôle de liaison radio et retransmission Pending WO2025233001A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
FI20245579 2024-05-08
FI20245579 2024-05-08

Publications (1)

Publication Number Publication Date
WO2025233001A1 true WO2025233001A1 (fr) 2025-11-13

Family

ID=94637650

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2025/053492 Pending WO2025233001A1 (fr) 2024-05-08 2025-02-11 Rapport d'état de contrôle de liaison radio et retransmission

Country Status (1)

Country Link
WO (1) WO2025233001A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170012745A1 (en) * 2014-02-26 2017-01-12 Mediatek Inc. Method and apparatus for triggering acknowledgement status report in wireless communications system
US10813027B2 (en) * 2015-09-25 2020-10-20 Jrd Communication Inc. Systems and methods for reporting data reception status

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170012745A1 (en) * 2014-02-26 2017-01-12 Mediatek Inc. Method and apparatus for triggering acknowledgement status report in wireless communications system
US10813027B2 (en) * 2015-09-25 2020-10-20 Jrd Communication Inc. Systems and methods for reporting data reception status

Similar Documents

Publication Publication Date Title
US12192290B2 (en) Data transmission method and communications device
EP3295735B1 (fr) Procédé et appareil de transmission d'informations de commande
US20230379920A1 (en) Mutliplexing and transmitting cancelled uplink control information
EP4014371A1 (fr) Fiabilité améliorée de multi-connectivité
US20240381161A1 (en) Radio access retransmission control
EP3618332A1 (fr) Procédé de transmission de copie et dispositif associé
WO2017076454A1 (fr) Initiation d'une mesure, d'un rapport et/ou d'une utilisation d'un retard de chemin secondaire pour attribuer des paquets ou supports parmi un chemin primaire et un chemin secondaire dans un réseau sans fil
CN114514776B (zh) 基于同时连接的切换
EP4305784B1 (fr) Procédé de commande de retransmissions
US20220330026A1 (en) Counter measures for attacking messages
EP4240083A1 (fr) Procédé et appareil utilisés dans un noeud de communication pour une communication sans fil
CN111937476A (zh) 针对用于无线网络的持续传输的反馈指示
US20250338237A1 (en) Multiple time alignment timers
WO2025233001A1 (fr) Rapport d'état de contrôle de liaison radio et retransmission
WO2025233000A1 (fr) Rapport d'état rlc et retransmission
WO2025232999A1 (fr) Rapport d'état rlc et retransmission
CN116633497A (zh) 适配混合自动重传请求
US12471078B2 (en) Enhanced downlink semi persistent scheduling operation for multi-transmission reception point
WO2021032266A1 (fr) Procédé de détermination d'un livre de codes de rétroaction d'accusé de réception de demande de répétition automatique hybride
CN121056926A (zh) 数据传输方法、通信装置及通信设备
WO2025201924A1 (fr) Rapport de performance dans une connectivité double et architecture divisée
CN120937319A (zh) 用于ai模型传递的终端设备、网络设备、和方法
WO2021008672A1 (fr) Appareil, procédé et programme informatique pour la transmission fiable de commande