[go: up one dir, main page]

WO2025205080A1 - Dispositif de communication, procédé de commande et programme pour empêcher une transmission inutile dans une rlc-am - Google Patents

Dispositif de communication, procédé de commande et programme pour empêcher une transmission inutile dans une rlc-am

Info

Publication number
WO2025205080A1
WO2025205080A1 PCT/JP2025/009896 JP2025009896W WO2025205080A1 WO 2025205080 A1 WO2025205080 A1 WO 2025205080A1 JP 2025009896 W JP2025009896 W JP 2025009896W WO 2025205080 A1 WO2025205080 A1 WO 2025205080A1
Authority
WO
WIPO (PCT)
Prior art keywords
rlc
pdu
pdcp
discarded
sequence number
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/JP2025/009896
Other languages
English (en)
Japanese (ja)
Inventor
洋樹 武田
ヤンウェイ 李
淑考 高久
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.)
KDDI Corp
Original Assignee
KDDI Corp
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 KDDI Corp filed Critical KDDI Corp
Publication of WO2025205080A1 publication Critical patent/WO2025205080A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/04—Error control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/02—Data link layer protocols

Definitions

  • the present invention relates to data transmission technology using RLC-AM in cellular communication systems.
  • the 3rd Generation Partnership Project (3GPP (registered trademark)) cellular communication standard introduces a mechanism called Radio Link Control (RLC)-Acknowledge Mode (AM) to improve the reliability of user data communications.
  • RLC Radio Link Control
  • AM Acknowledge Mode
  • This mode retransmits user data if an acknowledgment (ACK) indicating that the user data has been received by the other device is not received.
  • ACK acknowledgment
  • Some user data has a set delay tolerance (tolerable delay time, packet delay budget) for the delay it takes to reach the remote device.
  • delay tolerance tolerable delay time, packet delay budget
  • user data that requires real-time performance is naturally expected to have a short tolerable delay time.
  • the tolerable delay time will be exceeded when the user data is transmitted or retransmitted.
  • User data that exceeds the tolerable delay time is no longer data that needs to be transmitted.
  • the RLC-AM entity cannot stop processes such as retransmission, which can result in waste, such as the transmission of unnecessary data.
  • the present invention provides technology that prevents the transmission of data that exceeds the allowable delay time in RLC-AM.
  • a communication device is a communication device that complies with the cellular communication standard of the Third Generation Partnership Project (3GPP), and includes: a PDCP processing means that performs PDCP layer processing, including the generation of a Packet Data Convergence Protocol (PDCP) Protocol Data Unit (PDU) containing user data; and a radio link control (RLC) PDU that acquires a PDCP PDU from the PDCP processing means, generates a Radio Link Control (RLC) PDU containing one or more PDCP PDUs, and transmits the PDCP PDU in an RLC-Acknowledgement Mode (RLC-AM) format.
  • 3GPP Third Generation Partnership Project
  • the PDCP processing means manages the allowable delay time, which is the allowable delay until the transmitted PDCP PDU is successfully received by the other communication device, and discards PDCP PDUs that exceed the allowable delay time, and the RLC processing means obtains information identifying the discarded PDCP PDU from the PDCP processing means, identifies the sequence number of the RLC PDU that includes the discarded PDCP PDU, discards the RLC PDU that includes the discarded PDCP PDU, and notifies the other communication device of the sequence number of the RLC PDU to be discarded.
  • a communication device is a communication device that complies with the cellular communication standard of the Third Generation Partnership Project (3GPP), and receives an RLC Protocol Data Unit (PDU) from a communication partner device in Radio Link Control (RLC)-Acknowledge Mode (AM), and outputs one or more RLC Service Data Units (SDUs) included in the RLC PDU.
  • 3GPP Third Generation Partnership Project
  • RLC Radio Link Control
  • AM Radio Link Control
  • SDUs RLC Service Data Units
  • the RLC processing means includes an LC processing means, and a PDCP processing means that acquires the RLC SDU as a Packet Data Convergence Protocol (PDCP) PDU and performs reception processing of the PDCP PDU, and the RLC processing means receives notification of the sequence number of the RLC PDU to be discarded from the other device, and does not request retransmission of the RLC PDU even if the RLC PDU with the notified sequence number is not received.
  • PDCP Packet Data Convergence Protocol
  • This invention makes it possible to prevent the transmission of data that exceeds the allowable delay time in RLC-AM.
  • FIG. 1 is a diagram illustrating an example of the configuration of a wireless communication system.
  • FIG. 2 is a diagram illustrating an example of the hardware configuration of a base station device and a terminal device.
  • FIG. 2 is a diagram illustrating an example of the functional configuration of a base station device and a terminal device.
  • FIG. 1 is a diagram illustrating a process executed in a wireless communication system.
  • FIG. 1 shows an example of the configuration of a wireless communication system according to this embodiment.
  • This wireless communication system is compliant with cellular communication standards such as Long Term Evolution (LTE) or 5th Generation (5G) of the Third Generation Partnership Project (3GPP (registered trademark)), or their successor standards.
  • This wireless communication system includes a base station device 101 and a terminal device 111.
  • the terminal device 111 is a communication device that establishes a connection with the base station device 101, transmits user data on an uplink (a link from the terminal device 111 to the base station device 101), and receives user data on a downlink (a link from the base station device 101 to the terminal device 111).
  • the base station device 101 is a communication device that transmits downlink user data to the connected terminal device 111 and receives uplink user data.
  • the ROM 202 is a read-only memory that stores information such as programs and various parameters related to the processes executed by the base station device 101 and the terminal device 111.
  • the RAM 203 functions as a workspace when the processor 201 executes the programs and is a random access memory that stores temporary information.
  • the storage device 204 is configured, for example, by a removable external storage device.
  • the communication circuit 205 is configured, for example, by a circuit for wireless communication of LTE, 5G, or a successor standard. While FIG. 2 illustrates one communication circuit 205, the base station device 101 and the terminal device 111 may have multiple communication circuits.
  • the base station device 101 and the terminal device 111 may have wireless communication circuits for LTE, 5G, and a successor standard, respectively, and a common antenna for these circuits.
  • the base station device 101 and the terminal device 111 may also have separate antennas suitable for each standard.
  • the base station device 101 may also have a wired communication circuit used when communicating with other base station devices or nodes in the core network.
  • the terminal device 111 may also have a communication circuit compliant with a wireless communication standard other than a cellular communication standard, such as a wireless local area network (LAN) or Bluetooth (registered trademark).
  • the base station device 101 and the terminal device 111 may have separate communication circuits 205 for each of the multiple available frequency bands, or may have a common communication circuit 205 for at least some of the frequency bands.
  • Figure 3 shows an example of the functional configuration of the base station device 101 and terminal device 111 according to this embodiment.
  • Both the base station device 101 and the terminal device 111 are configured to include a PDCP processing unit 301, an RLC processing unit 302, a MAC processing unit 303, and a PHY processing unit 304.
  • Figure 3 only shows functions particularly related to this embodiment, and does not illustrate various other functions that the base station device and the terminal device may have.
  • the terminal device naturally has other functions that terminal devices compliant with 5G and subsequent standards generally have.
  • the functional blocks in Figure 3 are shown schematically, and the respective functional blocks may be realized as an integrated unit or may be further subdivided.
  • each function in Figure 3 may be realized, for example, by the processor 201 executing a program stored in the ROM 202 or the storage device 204, or by a processor residing within the communication circuit 205 executing predetermined software. Since the details of the processing performed by each functional unit have been described above, only the general functions of the base station device 101 and terminal device 111 will be outlined here.
  • the PDCP processing unit 301 performs processing of the Packet Data Convergence Protocol (PDCP) layer.
  • PDCP Packet Data Convergence Protocol
  • IP Internet Protocol
  • SDU PDCP Service Data Unit
  • the PDCP processing unit 301 then adds a PDCP layer header (PDCP header) to the PDCP SDU to generate a PDCP Protocol Data Unit (PDU).
  • PDCP header PDCP layer header
  • PDU PDCP Protocol Data Unit
  • the PDCP processing unit 301 outputs the PDCP PDU to the RLC processing unit 302.
  • the RLC processing unit 302 performs processing of the Radio Link Control (RLC) layer.
  • the RLC processing unit 302 treats the PDCP PDU input from the PDCP processing unit 301 as an RLC SDU, adds an RLC layer header (RLC header) to the RLC SDU to generate an RLC PDU, and outputs the RLC PDU to the MAC processing unit 303.
  • the RLC processing unit 302 can concatenate multiple RLC SDUs to generate a single RLC PDU. At this time, a single RLC SDU may be divided and included in multiple RLC PDUs.
  • the MAC processing unit 303 performs processing on the Medium Access Control (MAC) layer.
  • the MAC processing unit 303 takes the RLC PDU generated by the RLC processing unit 302 as a MAC SDU, adds a MAC layer header (MAC header) and padding to the MAC SDU to generate a MAC PDU, and outputs the MAC PDU to the PHY processing unit 304.
  • the PHY processing unit 304 uses the MAC PDU as a transport block to generate a subframe to be transmitted, and transmits it as a wireless signal to the remote device.
  • each processing unit of the transmitting communication device performs the reverse procedure. That is, the PHY processing unit 304 receives a radio signal (subframe) containing a transport block from the other device and outputs the transport block to the MAC processing unit 303.
  • the MAC processing unit 303 treats the transport block as a MAC PDU, removes the MAC header and padding from it, extracts a MAC SDU, and outputs the MAC SDU to the RLC processing unit 302.
  • the RLC processing unit 302 treats the MAC SDU as an RLC PDU, removes the RLC header, and extracts the RLC SDU. Note that an RLC PDU may contain multiple RLC SDUs.
  • the RLC processing unit 302 divides or concatenates the payload portion contained in the RLC PDU to recreate each RLC SDU.
  • the RLC processing unit 302 then outputs the reconstructed RLC SDU to the PDCP processing unit 301.
  • the PDCP processing unit 301 removes the PDCP header from the RLC SDU and extracts the IP packets. In this way, the user data (IP packets) from the transmitting communication device (terminal device 111 for the uplink, or base station device 101 for the downlink) reaches the receiving communication device (base station device 101 for the uplink, or terminal device 111 for the downlink).
  • the PDCP processing unit 301 in the transmitting communication device manages the allowable delay time, which is the allowable delay until user data (IP packets) are successfully received by the other communication device.
  • the PDCP processing unit 301 discards the PDCP PDU if the elapsed time from the generation of the user data (input to the PDCP processing unit 301) exceeds the allowable delay time.
  • the allowable delay time in this case can be notified to the terminal device, which is the transmitting communication device, by the base station device, which is the receiving communication device.
  • the base station device can determine the allowable delay time based on information indicating the quality required for the wireless line, such as 5QI (5G QoS Identifier), received from the core network device, and notify the terminal device of this as the discardTimer, which is part of the PDCP parameters.
  • 5QI 5G QoS Identifier
  • the RLC processing unit 302 can also use an acknowledgement and retransmission mechanism known as RLC-Acknowledge Mode (AM).
  • RLC-AM the RLC processing unit 302 assigns a sequence number to the RLC PDU to be transmitted and transmits it.
  • the RLC processing unit 302 receives an acknowledgement (status information) indicating the sequence number of the RLC PDU that was not successfully received by the RLC processing unit 302 of the other communication device, and retransmits the RLC PDU that was not successfully received. From the other device, for example, a STATUS PDU is received that indicates the reception status of the RLC PDU.
  • the STATUS PDU contains, for example, information indicating the sequence number of the RLC PDU that was not successfully received and the sequence number next to the sequence number of the RLC PDU that was successfully received (i.e., the sequence number of the next RLC PDU that should be received). For example, if RLC PDUs with sequence numbers 1 to 3 have been transmitted, and the RLC PDU with sequence number 2 has not been successfully received, but the RLC PDUs with sequence numbers 1 and 3 have been successfully received, the STATUS PDU may contain the sequence number "2" of the RLC PDU that was not successfully received, and the sequence number "4" of the next RLC PDU to be received. In response to receiving the STATUS PDU, the RLC processing unit 302 may retransmit the RLC PDU with sequence number "2" and transmit the RLC PDU with sequence number "4".
  • the transmitting communication device When communication control is performed using RLC-AM, if the receiving communication device does not successfully receive an RLC PDU, the transmitting communication device will repeatedly transmit that RLC PDU. At this time, for example, if the PDCP processing unit 301 determines that the time since the generation of the user data to be transmitted using that RLC PDU has exceeded the allowable delay time, it discards the PDCP PDU related to that user data. At this point, it may no longer be necessary to retransmit the RLC PDU containing that PDCP PDU at the RLC layer, but the RLC processing unit 302 cannot recognize that retransmission is no longer necessary.
  • the RLC processing unit 302 for user data with a short allowable delay time, it is possible that the time since the generation of that user data will exceed the allowable delay time while the RLC processing unit 302 is preparing to transmit the RLC PDU containing that user data. In such a case, the RLC processing unit 302 will perform an unnecessary transmission. Furthermore, the RLC processing unit 302 in the receiving communication device is unable to recognize that the RLC PDU no longer needs to be transmitted because the allowable delay time for user data has elapsed, and continues to send retransmission requests.
  • this embodiment provides technology for suppressing unnecessary transmission of RLC PDUs.
  • the PDCP processing unit 301 when the PDCP processing unit 301 discards user data (a PDCP PDU or PDCP SDU containing the user data), it notifies the RLC processing unit 302 of information identifying the discarded user data.
  • the PDCP processing unit 301 may, for example, notify the RLC processing unit 302 of information identifying the PDCP PDU or PDCP SDU. Based on the notified information, the RLC processing unit 302 identifies the sequence number of the RLC PDU containing the discarded user data.
  • the RLC processing unit 302 of the transmitting device then discards the RLC PDU with that sequence number and further notifies the RLC processing unit 302 of the receiving communication device (hereinafter referred to as the "receiving device") of the sequence number of the discarded RLC PDU.
  • the receiving device receives information about the sequence number of a discarded RLC PDU.
  • the receiving device can avoid sending a retransmission request for that RLC PDU to the transmitting device even if the RLC PDU with that sequence number is not received.
  • the transmitting device may notify the receiving device of the sequence number of the discarded RLC PDU each time an RLC PDU is discarded, or may, for example, periodically notify the receiving device of (a list of) the sequence numbers of the discarded RLC PDUs at a predetermined interval.
  • information that can identify the predetermined interval may be notified from base station device 101 when the transmitting device is terminal device 111. Note that even when the transmitting device is base station device 101, information that can identify the predetermined interval may be notified from terminal device 111 to base station device 101.
  • the transmitting device may activate a prohibit timer to prevent further notification of the sequence number of the discarded RLC PDU for a predetermined period of time. In other words, it may prevent the sequence number of the discarded RLC PDU from being notified frequently, and after the sequence number has been notified once, it may prevent similar notification for a certain period of time.
  • the transmitting device may transmit only information regarding the sequence numbers of the discarded RLC PDUs to the receiving device, or may include information regarding the sequence numbers of the discarded RLC PDUs in an RLC PDU (Acknowledge Mode Data (AMD) PDU) containing user data to be transmitted to the receiving device and transmit this to the receiving device.
  • APD Acknowledge Mode Data
  • the transmitting device may also generate a STATUS PDU containing information regarding the sequence numbers of the discarded RLC PDUs and transmit this STATUS PDU to the receiving device.
  • This STATUS PDU may be newly defined to notify the discarded RLC PDUs.
  • the information notified by the transmitting device is not limited to (a list of) the sequence numbers of the discarded RLC PDUs, but may also be information consisting of the minimum sequence number of the discarded RLC PDUs and the number of discarded RLC PDUs.
  • the transmitting device may advance the sequence numbers of other RLC PDUs to be transmitted after that RLC PDU, and may not notify the transmitting device of the sequence number of the discarded RLC PDU. For example, if a first RLC PDU with sequence number "n" is discarded before being transmitted to the receiving device, the transmitting device may reassign the sequence number of the second RLC PDU, which was scheduled to be transmitted with sequence number "n+1," to "n,” and may not notify the receiving device of the sequence number of the first RLC PDU. Because the first RLC PDU has never been transmitted, the receiving device is unaware of the existence of the first RLC PDU, and will not request a retransmission of the first RLC PDU.
  • a transmitting device may retransmit the notification of the sequence number of the discarded RLC PDU to the receiving device without transmitting the RLC PDU. This is because it is assumed that the notification of the sequence number of the discarded RLC PDU has not yet arrived at the receiving device due to the receipt of the retransmission request. Note that to perform this processing, the transmitting device may distinguish between transmitted RLC PDUs and discarded RLC PDUs.
  • the transmitting device manages transmission using a window of a predetermined size to identify RLC PDUs with sequence numbers within a predetermined range as those to be transmitted, but this management alone is not sufficient to distinguish between discarded RLC PDUs and RLC PDUs that may be retransmitted. For this reason, when a transmitting device receives a request to retransmit a discarded RLC PDU, it may manage information that enables it to identify that the RLC PDU is not to be retransmitted. Based on this information, for example, the transmitting device can determine whether or not to retransmit the RLC PDU that is the subject of the retransmission request.
  • the transmitting device can determine not to retransmit a discarded RLC PDU even if a retransmission request is received, and can determine to retransmit an RLC PDU that is not discarded if a retransmission request is received. Furthermore, for example, if an RLC PDU with the smallest sequence number within the range of sequence numbers specified by the above-mentioned window is discarded, the transmitting device can shift the window to a range that does not include the discarded sequence number, thereby changing the range of transmission targets.
  • the transmitting device may discard the RLC PDU containing the first PDCP PDU and generate an RLC PDU containing only the second PDCP PDU. The transmitting device may then transmit this RLC PDU to the receiving device.
  • the sequence number of this RLC PDU may be the same as that of the discarded RLC PDU, or a different sequence number may be assigned to this RLC PDU.
  • the RLC PDU containing the discarded first PDCP PDU and the undeleted second PDCP PDU may not be discarded, and conventional processing, including retransmission of the RLC PDU, may continue.

Landscapes

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

Abstract

L'invention concerne un dispositif de communication qui génère une PDU RLC comprenant au moins une PDU PDCP et transmet la PDU RLC à un dispositif homologue de communication par RLC-AM. Le dispositif de communication gère un temps de retard admissible qui est une valeur admissible d'un retard jusqu'à ce que la PDU PDCP transmise soit reçue avec succès par le dispositif homologue dans la couche PDCP, rejette la PDU PDCP dont le temps de retard admissible est expiré, acquiert des informations identifiant la PDU PDCP rejetée dans la couche RLC, identifie un numéro de séquence de la PDU RLC comprenant la PDU PDCP rejetée, rejette la PDU RLC comprenant la PDU PDCP rejetée, et notifie le dispositif homologue du numéro de séquence de la PDU RLC rejetée.
PCT/JP2025/009896 2024-03-29 2025-03-14 Dispositif de communication, procédé de commande et programme pour empêcher une transmission inutile dans une rlc-am Pending WO2025205080A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2024056620A JP2025153907A (ja) 2024-03-29 2024-03-29 Ｒｌｃ－ａｍにおける不要な送信を防ぐための端末装置、基地局装置、及び制御方法
JP2024-056620 2024-03-29

Publications (1)

Publication Number Publication Date
WO2025205080A1 true WO2025205080A1 (fr) 2025-10-02

Family

ID=97218087

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2025/009896 Pending WO2025205080A1 (fr) 2024-03-29 2025-03-14 Dispositif de communication, procédé de commande et programme pour empêcher une transmission inutile dans une rlc-am

Country Status (2)

Country Link
JP (1) JP2025153907A (fr)
WO (1) WO2025205080A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015008962A1 (fr) * 2013-07-17 2015-01-22 Lg Electronics Inc. Procédé de rapport de défaillance de retransmission de commande de liaison radio et dispositif associé
WO2019167228A1 (fr) * 2018-03-01 2019-09-06 三菱電機株式会社 Système de communication mobile, dispositif côté réception et dispositif côté émission

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015008962A1 (fr) * 2013-07-17 2015-01-22 Lg Electronics Inc. Procédé de rapport de défaillance de retransmission de commande de liaison radio et dispositif associé
WO2019167228A1 (fr) * 2018-03-01 2019-09-06 三菱電機株式会社 Système de communication mobile, dispositif côté réception et dispositif côté émission

Also Published As

Publication number Publication date
JP2025153907A (ja) 2025-10-10

Similar Documents

Publication Publication Date Title
US8369865B2 (en) Data transmission method and data re-transmission method
EP3616347B1 (fr) Indication de l'état de données retransmises
JP6907444B2 (ja) データ伝送方法、通信デバイス、端末、および基地局
US8588784B2 (en) Mobile communication system, wireless base station and hand over reconnection method for use therewith including an accumulation portion for holding data
JP4865910B2 (ja) シーケンス番号の更新
KR101509766B1 (ko) 이동통신시스템에서의 ｒｌｃ ｐｄｕ 전송 방법, 자원할당 방법 및 ｒｌｃ 엔티티
JP4806030B2 (ja) 移動通信システムで信号を転送する方法
KR20090122962A (ko) 재송요구 송신방법 및 수신측 장치
WO2018202133A1 (fr) Procédé et dispositif de traitement de données
JPWO2019244284A1 (ja) 送信装置及びバッファ制御方法
JP2025528125A (ja) データ処理方法及び機器
RU2392752C2 (ru) Способ передачи данных и способ повторной передачи данных
US9246638B2 (en) Method and apparatus for polling transmission status in a wireless communications system
WO2025205080A1 (fr) Dispositif de communication, procédé de commande et programme pour empêcher une transmission inutile dans une rlc-am
KR100912785B1 (ko) 상태 보고를 보고하는 방법 및 수신기
TW202406397A (zh) 增強無線電鏈路控制的方法及其使用者設備
JP2011055435A (ja) 再送制御装置及び再送制御方法
CN120614642A (zh) 通信方法及装置、计算机可读存储介质
WO2025123267A1 (fr) Procédés de transmission de données, dispositifs terminaux et dispositifs réseau

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

Country of ref document: EP

Kind code of ref document: A1