WO2019153209A1 - Procédé de traitement d'échec de liaison radio (rlf) et dispositif terminal - Google Patents

Procédé de traitement d'échec de liaison radio (rlf) et dispositif terminal Download PDF

Info

Publication number
WO2019153209A1
WO2019153209A1 PCT/CN2018/075874 CN2018075874W WO2019153209A1 WO 2019153209 A1 WO2019153209 A1 WO 2019153209A1 CN 2018075874 W CN2018075874 W CN 2018075874W WO 2019153209 A1 WO2019153209 A1 WO 2019153209A1
Authority
WO
WIPO (PCT)
Prior art keywords
radio bearer
rlc entity
terminal device
radio
data transmission
Prior art date
Application number
PCT/CN2018/075874
Other languages
English (en)
Chinese (zh)
Inventor
石聪
Original Assignee
Oppo广东移动通信有限公司
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 Oppo广东移动通信有限公司 filed Critical Oppo广东移动通信有限公司
Priority to PCT/CN2018/075874 priority Critical patent/WO2019153209A1/fr
Priority to CN201880036995.3A priority patent/CN110710143B/zh
Publication of WO2019153209A1 publication Critical patent/WO2019153209A1/fr

Links

Images

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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path

Definitions

  • the embodiments of the present application relate to the field of communications, and, more particularly, to a method and a terminal device for processing a radio link failure RLF.
  • a Packet Data Convergence Protocol (PDCP) entity corresponding to a radio bearer can support a duplicate data transmission function, that is, a PDCP Protocol Data Unit (PDU) is copied into two. This improves the reliability of data transmission.
  • PDCP Packet Data Convergence Protocol
  • PDU Packet Data Unit
  • RLF radio link failure
  • the embodiment of the present application provides a method and a terminal device for processing a radio link failure RLF, which is beneficial to improving reliability of data transmission.
  • a method for processing a radio link failure RLF comprising: the replica data transmission function of the first radio bearer is in a deactivated state, and the data of the first radio bearer is in the first radio bearer If the corresponding first radio link control RLC entity reaches the maximum number of retransmissions, or the replica data transmission function of the first radio bearer is in a deactivated state and the data of the second radio bearer is corresponding to the second radio bearer In the case that the maximum number of retransmissions is reached on the third RLC entity, the terminal device switches the RLC entity for transmitting data from the first RLC entity to the second RLC entity corresponding to the first radio bearer, the first The carrier mapped by the RLC entity at least partially overlaps with the carrier mapped by the third RLC entity.
  • the method further includes: the terminal device sending, to the network device, indication information, where the indication information is used to indicate that the first radio bearer has a radio link failure RLF.
  • the second radio bearer has a duplicate data transmission function, or the second radio bearer does not have a duplicate data transmission function.
  • the first radio bearer and the second radio bearer correspond to the same cell group or correspond to different cell groups.
  • the cell group includes a primary cell group MCG and/or a secondary cell group SCG.
  • the working mode of the first RLC entity is the acknowledge mode AM; or if the third RLC entity reaches the maximum number of retransmissions, the third The working mode of the RLC entity is the acknowledge mode AM, and the working mode of the RLC entity corresponding to the first radio bearer is the acknowledge mode AM or the non-acknowledge mode UM.
  • the first RLC entity is a primary link of the first radio bearer
  • the second RLC entity is a secondary link of the first radio bearer
  • a terminal device for performing the method of any of the above first aspect or any of the possible implementations of the first aspect.
  • the terminal device comprises means for performing the method of any of the above-described first aspect or any of the possible implementations of the first aspect.
  • a terminal device comprising: a memory, a processor, an input interface, and an output interface.
  • the memory, the processor, the input interface, and the output interface are connected by a bus system.
  • the memory is for storing instructions for executing the memory stored instructions for performing the method of any of the first aspect or the first aspect of the first aspect.
  • a computer storage medium for storing computer software instructions for performing the method of any of the above first aspect or any of the possible implementations of the first aspect, comprising program.
  • a computer program product comprising instructions, when executed on a computer, causes the computer to perform the method of any of the first aspect or the optional implementation of the first aspect.
  • FIG. 1 is a schematic diagram of an application scenario of an embodiment of the present application.
  • Figure 2 shows a protocol architecture diagram in a carrier aggregation scenario.
  • FIG. 3 is a schematic block diagram of a method for processing a radio link failure RLF according to an embodiment of the present application.
  • FIG. 4 shows a schematic block diagram of a terminal device of an embodiment of the present application.
  • FIG. 5 is another schematic block diagram of a terminal device according to an embodiment of the present application.
  • GSM Global System of Mobile communication
  • CDMA Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • FDD Frequency Division Duplex
  • TDD Time Division Duplex
  • UMTS Universal Mobile Telecommunication System
  • WiMAX Worldwide Interoperability for Microwave Access
  • the technical solutions of the embodiments of the present application can be applied to various communication systems based on non-orthogonal multiple access technologies, such as a sparse code multiple access (SCMA) system, and a low-density signature (Low). Density Signature (LDS) system, etc., of course, the SCMA system and the LDS system may also be referred to as other names in the communication field; further, the technical solution of the embodiment of the present application can be applied to multi-carrier using non-orthogonal multiple access technology.
  • SCMA sparse code multiple access
  • LDS Density Signature
  • Orthogonal Frequency Division Multiplexing OFDM
  • Filter Bank Multi-Carrier FBMC
  • General Frequency Division Multiplexing Generalized Frequency Division Multiplexing (OFDM)) Frequency Division Multiplexing (GFDM)
  • Filtered Orthogonal Frequency Division Multiplexing Filtered-OFDM, F-OFDM
  • the terminal device in the embodiment of the present application may refer to a user equipment (User Equipment, UE), an access terminal, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, and a wireless device.
  • Communication device user agent or user device.
  • the access terminal may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), with wireless communication.
  • SIP Session Initiation Protocol
  • WLL Wireless Local Loop
  • PDA Personal Digital Assistant
  • the network device in the embodiment of the present application may be a device for communicating with a terminal device, where the network device may be a Base Transceiver Station (BTS) in GSM or CDMA, or may be a base station (NodeB, NB) in a WCDMA system. And may be an evolved base station (eNB or eNodeB) in the LTE system, or may be a wireless controller in a cloud radio access network (CRAN) scenario, or the network device may be The embodiments of the present application are not limited to the relay station, the access point, the in-vehicle device, the wearable device, and the network device in the future 5G network or the network device in the future evolved PLMN network.
  • BTS Base Transceiver Station
  • NodeB NodeB
  • NB base station
  • CRAN cloud radio access network
  • the embodiments of the present application are not limited to the relay station, the access point, the in-vehicle device, the wearable device, and the network device in the future 5G network or
  • FIG. 1 is a schematic diagram of an application scenario of an embodiment of the present application.
  • the communication system in FIG. 1 may include a terminal device 10 and a network device 20.
  • the network device 20 is configured to provide communication services for the terminal device 10 and access the core network.
  • the terminal device 10 accesses the network by searching for synchronization signals, broadcast signals, and the like transmitted by the network device 20, thereby performing communication with the network.
  • the arrows shown in FIG. 1 may represent uplink/downlink transmissions by a cellular link between the terminal device 10 and the network device 20.
  • the PDCP entity can support the data replication function, that is, the PDCP replication data function is used, so that the copied data is separately transmitted to two Radio Link Control (RLC) entities (corresponding to two different Logical channel), and finally ensure that the copied PDCP PDU can be transmitted on different physical layer aggregate carriers to achieve frequency diversity gain to improve data transmission reliability.
  • RLC Radio Link Control
  • the PDCP entity corresponding to a radio bearer has a split bearer replication function, and the data process of the PDCP Service Data Unit (SDU) is copied and encapsulated into PDCP PDU1 and PDCP PDU2, PDCP PDU1 and PDCP PDU2.
  • SDU Service Data Unit
  • PDCP PDU1 and PDCP PDU2 are respectively mapped to different Radio Link Control (RLC) entities, that is, PDCP PDU1 is transmitted to RLC entity 1, and PDCP PDU2 is transmitted to RLC entity 2, and different RLC entities correspond to different logics.
  • RLC Radio Link Control
  • the replicated data is transmitted on different carriers, for example, the RLC entity 1
  • the transmitted duplicate data is transmitted on the physical carrier 1
  • the replicated data transmitted in the RLC entity 2 is transmitted on the physical carrier 2.
  • the radio link failure RLF occurs, and how the terminal device should respond to the RLF has not been involved in the current discussion.
  • FIG. 3 is a schematic block diagram of a method 100 of processing a radio link failure RLF in an embodiment of the present application. As shown in FIG. 3, the method 100 includes:
  • the data transmission function of the first radio bearer is in a deactivated state, and the data of the first radio bearer reaches a maximum number of retransmissions on the first radio link control RLC entity corresponding to the first radio bearer. In case, or
  • the terminal device An RLC entity for transmitting data is switched from the first RLC entity to a second RLC entity corresponding to the first radio bearer, where the carrier mapped by the first RLC entity and the carrier mapped by the third RLC entity are at least Partial overlap.
  • radio bearers correspond to different PDCP entities
  • a PDCP entity having a duplicate data transmission function may be configured to correspond to two RLC entities
  • a replica data transmission function of the PDCP entity may also be a replica data transmission function of the radio bearer.
  • the terminal device determines that the first radio bearer has an RLF. That is to say, when the terminal device may be performing non-replicated data transmission by using an RLC entity corresponding to the first radio bearer, the first radio bearer generates an RLF.
  • the first radio bearer may be triggered by the maximum number of retransmissions on the first RLC entity corresponding to the first radio bearer that is undergoing non-replicated data transmission, or may be the third corresponding to the second radio bearer.
  • the RLC entity is triggered by the maximum number of retransmissions, where the carrier mapped by the third RLC entity at least partially overlaps with the carrier mapped by the first RLC entity.
  • the carrier mapped by the third RLC entity and the carrier mapped by the first RLC entity may be a subset of each other.
  • the terminal device may stop using the RLC entity corresponding to the first radio bearer to perform data transmission, and use the RLC entity that does not generate the RLF corresponding to the first radio bearer to perform data. Transmission.
  • the link corresponding to the first RLC entity corresponding to the first radio bearer is RLF, and the terminal device may correspond to the first radio bearer.
  • the RLC entity for transmitting data switches from the first RLC entity to the second RLC entity corresponding to the first radio bearer.
  • the method for processing the radio link RLF in the embodiment of the present application is advantageous for improving the reliability of data transmission.
  • the maximum number of retransmissions of data transmitted on an RLC entity means that the working mode of the RLC entity may be an acknowledged mode (AM).
  • the retransmission counter corresponding to a certain RLC SDU reaches the configured threshold.
  • the foregoing second radio bearer may or may not have a duplicate data transmission function.
  • the carrier mapped by the first RLC entity and the carrier mapped by the third RLC entity corresponding to the second radio bearer at least partially overlap, for example, may correspond to at least one same secondary cell.
  • the first radio bearer and the second radio bearer may also be the same or different cell groups, for example, a primary cell group (MCG) and/or a secondary cell group (SCG).
  • the first radio bearer occurs when the RLF is reached by the third RLC entity corresponding to the second radio bearer, and the working mode of the third RLC entity is the AM mode, then the first radio
  • the working mode of carrying the corresponding RLC entity may be an AM mode or an Unacknowledged Mode (UM).
  • the link corresponding to the first RLC entity is a primary link
  • the link corresponding to the second RLC entity is a secondary link, that is, when the replication data transmission function of the first radio bearer is in a deactivated state.
  • the default use of the network device configuration is that the first RLC entity performs data transmission, and the default unused RLC entity configured by the network device is the second RLC entity.
  • the data is forwarded to the RLC entity corresponding to the primary link, and the data is forwarded to the RLC entity corresponding to the secondary link.
  • the secondary link automatically becomes the primary link;
  • the data is delivered to the RLC entity corresponding to the secondary link, and the data is delivered to the RLC entity corresponding to the primary link.
  • the method further includes: the terminal device sends the indication information to the network device, where the indication information is used to indicate that the radio link failure RLF occurs on the first radio bearer. That is to say, the terminal device can report the RLF to the network device, and the terminal device can report to the network device that the link is triggered by the RLF.
  • the size of the sequence numbers of the above processes does not mean the order of execution, and the order of execution of each process should be determined by its function and internal logic, and should not be implemented in the present application.
  • the implementation of the examples constitutes any limitation.
  • a method for processing a radio link failure RLF according to an embodiment of the present application is described in detail above.
  • An apparatus for processing a radio link failure RLF according to an embodiment of the present application will be described below with reference to FIG. 4 and FIG. The technical features are applicable to the following device embodiments.
  • FIG. 4 shows a schematic block diagram of a terminal device 200 of an embodiment of the present application.
  • the terminal device 200 includes:
  • the processing unit 210 is configured to: the replica data transmission function of the first radio bearer is in a deactivated state, and the data of the first radio bearer reaches a maximum retransmission on the first radio link control RLC entity corresponding to the first radio bearer. In the case of the number of times, or
  • the RLC entity switches from the first RLC entity to a second RLC entity corresponding to the first radio bearer, and the carrier mapped by the first RLC entity at least partially overlaps with the carrier mapped by the third RLC entity.
  • the terminal device in the embodiment of the present application is advantageous for improving the reliability of data transmission.
  • the terminal device further includes: a sending unit, configured to send the indication information to the network device, where the indication information is used to indicate that the radio link failure RLF occurs on the first radio bearer.
  • the second radio bearer has a duplicate data transmission function, or the second radio bearer does not have a duplicate data transmission function.
  • the first radio bearer and the second radio bearer correspond to the same cell group or correspond to different cell groups.
  • the cell group includes a primary cell group MCG and/or a secondary cell group SCG.
  • the working mode of the first RLC entity is the acknowledge mode AM; or if the third RLC entity reaches the maximum number of retransmissions, The working mode of the third RLC entity is the acknowledge mode AM, and the working mode of the RLC entity corresponding to the first radio bearer is the acknowledge mode AM or the non-acknowledgement mode UM.
  • the first RLC entity is a primary link of the first radio bearer
  • the second RLC entity is a secondary link of the first radio bearer
  • terminal device 200 may correspond to the terminal device in the method embodiment of the present application, and the foregoing and other operations and/or functions of the respective units in the terminal device 200 respectively implement the terminal in the method of FIG.
  • the corresponding process of the device is not described here for brevity.
  • the embodiment of the present application further provides a terminal device 300, which may be the terminal device 200 in FIG. 4, which can be used to execute the content of the terminal device corresponding to the method 100 of FIG.
  • the terminal device 300 includes an input interface 310, an output interface 320, a processor 330, and a memory 340.
  • the input interface 310, the output interface 320, the processor 330, and the memory 340 can be connected by a bus system.
  • the memory 340 is for storing programs, instructions or codes.
  • the processor 330 is configured to execute a program, an instruction or a code in the memory 340 to control the input interface 310 to receive a signal, control the output interface 320 to transmit a signal, and complete the operations in the foregoing method embodiments.
  • the terminal device in the embodiment of the present application is advantageous for improving the reliability of data transmission.
  • the processor 330 may be a central processing unit (CPU), and the processor 330 may also be another general-purpose processor, a digital signal processor (DSP). , Application Specific Integrated Circuit (ASIC), Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, etc.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the memory 340 can include read only memory and random access memory and provides instructions and data to the processor 330. A portion of the memory 340 may also include a non-volatile random access memory. For example, the memory 340 can also store information of the device type.
  • each content of the above method may be completed by an integrated logic circuit of hardware in the processor 330 or an instruction in a form of software.
  • the content of the method disclosed in the embodiments of the present application may be directly implemented as a hardware processor, or may be performed by a combination of hardware and software modules in the processor.
  • the software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the storage medium is located in the memory 340, and the processor 330 reads the information in the memory 340 and completes the contents of the above method in combination with its hardware. To avoid repetition, it will not be described in detail here.
  • the processing unit of the terminal device 200 may be implemented by the processor 330 of FIG. 5, and the transmitting unit of the terminal device 200 may be implemented by the output interface 320 of FIG.
  • the disclosed systems, devices, and methods may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or may be Integrate into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • This functionality if implemented as a software functional unit and sold or used as a standalone product, can be stored on a computer readable storage medium.
  • the technical solution of the present application which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including The instructions are used to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of various embodiments of the present application.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like, which can store program codes. .

Landscapes

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

Abstract

La présente invention concerne, selon un mode de réalisation, un procédé de traitement d'échec de liaison radio (RLF), ainsi qu'un dispositif terminal. Le procédé comprend les étapes suivantes : si une fonction de réplication et de transmission de données d'une première porteuse radio est dans un état inactif et si une retransmission de données de la première porteuse radio sur une première entité de commande de liaison radio (RLC) correspondant à la première porteuse radio atteint un décompte de retransmission maximal, ou si la fonction de réplication et de transmission de données de la première porteuse radio est dans l'état inactif et si la retransmission de données d'une seconde porteuse radio sur une troisième entité RLC correspondant à la seconde porteuse radio atteint un décompte de retransmission maximal, un dispositif terminal commute une entité RLC pour une transmission de données de la première entité RLC à une deuxième entité RLC correspondant à la première porteuse radio, une porteuse mappée par la première entité RLC chevauchant au moins partiellement une porteuse mappée par la troisième entité RLC. Le procédé et le dispositif terminal des modes de réalisation de la présente invention permettent d'améliorer la fiabilité d'une transmission de données.
PCT/CN2018/075874 2018-02-08 2018-02-08 Procédé de traitement d'échec de liaison radio (rlf) et dispositif terminal WO2019153209A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2018/075874 WO2019153209A1 (fr) 2018-02-08 2018-02-08 Procédé de traitement d'échec de liaison radio (rlf) et dispositif terminal
CN201880036995.3A CN110710143B (zh) 2018-02-08 2018-02-08 处理无线链路失败rlf的方法和终端设备

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2018/075874 WO2019153209A1 (fr) 2018-02-08 2018-02-08 Procédé de traitement d'échec de liaison radio (rlf) et dispositif terminal

Publications (1)

Publication Number Publication Date
WO2019153209A1 true WO2019153209A1 (fr) 2019-08-15

Family

ID=67548684

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/075874 WO2019153209A1 (fr) 2018-02-08 2018-02-08 Procédé de traitement d'échec de liaison radio (rlf) et dispositif terminal

Country Status (2)

Country Link
CN (1) CN110710143B (fr)
WO (1) WO2019153209A1 (fr)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113347694B (zh) * 2021-06-30 2022-12-06 锐迪科微电子科技（上海）有限公司 无线承载释放方法、装置、设备和介质
CN113507726B (zh) * 2021-07-14 2024-05-14 Oppo广东移动通信有限公司 分离承载模式下的数据传输方法、装置以及终端设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103201977A (zh) * 2010-11-08 2013-07-10 高通股份有限公司 用于使用多链路pdcp 子层进行多点hsdpa 通信的系统和方法
WO2016061390A1 (fr) * 2014-10-15 2016-04-21 Qualcomm Incorporated Déclaration précoce de défaillance de liaison radio (rlf)
CN105960772A (zh) * 2014-01-31 2016-09-21 高通股份有限公司 用于在双连接场景下管理辅助eNB(SeNB)无线链路失败(S-RLF)的过程
CN107438976A (zh) * 2017-03-28 2017-12-05 北京小米移动软件有限公司 数据传输方法及装置、数据接收方法及装置、电子设备

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2806593B1 (fr) * 2012-01-17 2019-03-06 LG Electronics Inc. Procédé et appareil pour la transmission d'informations de commande de liaison montante dans un système de communication sans fil
CN103581942B (zh) * 2012-07-31 2017-08-11 电信科学技术研究院 一种无线链路失败的处理方法、装置及系统
CN106993313A (zh) * 2016-01-21 2017-07-28 中兴通讯股份有限公司 一种实现承载切换的方法及终端和基站
US10750410B2 (en) * 2016-09-30 2020-08-18 Huawei Technologies Co., Ltd. Ultra reliable low latency connection support in radio access networks
CN107567041B (zh) * 2017-08-08 2019-12-10 电信科学技术研究院 一种处理无线链路故障的方法和设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103201977A (zh) * 2010-11-08 2013-07-10 高通股份有限公司 用于使用多链路pdcp 子层进行多点hsdpa 通信的系统和方法
CN105960772A (zh) * 2014-01-31 2016-09-21 高通股份有限公司 用于在双连接场景下管理辅助eNB(SeNB)无线链路失败(S-RLF)的过程
WO2016061390A1 (fr) * 2014-10-15 2016-04-21 Qualcomm Incorporated Déclaration précoce de défaillance de liaison radio (rlf)
CN107438976A (zh) * 2017-03-28 2017-12-05 北京小米移动软件有限公司 数据传输方法及装置、数据接收方法及装置、电子设备

Also Published As

Publication number Publication date
CN110710143B (zh) 2021-01-12
CN110710143A (zh) 2020-01-17

Similar Documents

Publication Publication Date Title
EP3672302B1 (fr) Procédé de transmission de données et dispositif terminal
WO2018170855A1 (fr) Procédé de transmission de données, dispositif terminal et dispositif de réseau
WO2018227555A1 (fr) Procédé de transmission de données, dispositif terminal et dispositif de réseau
EP3672128B1 (fr) Procédé de transmission de données, dispositif terminal et dispositif de réseau
TWI751346B (zh) 用於傳輸數據的方法、終端設備和網絡設備
TWI791033B (zh) 無線通訊的方法、終端設備和網路設備
US11778689B2 (en) Method and device for processing data
WO2019095114A1 (fr) Procédé de gestion d'un échec de liaison radio, dispositif terminal, et dispositif de réseau
WO2019127289A1 (fr) Procédé de transmission de données et équipement terminal
WO2019153209A1 (fr) Procédé de traitement d'échec de liaison radio (rlf) et dispositif terminal
US11310103B2 (en) Method for handling radio link failure (RLF) and terminal device
WO2019028824A1 (fr) Procédé de transmission de données, dispositif terminal, et dispositif de réseau
WO2022120541A1 (fr) Procédé et appareil de transmission de données
WO2020124540A1 (fr) Procédé de réordonnancement de paquets de données, dispositif électronique et support d'informations

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18905881

Country of ref document: EP

Kind code of ref document: A1