WO2019018989A1 - 处理无线链路失败的方法和终端设备 - Google Patents

处理无线链路失败的方法和终端设备 Download PDF

Info

Publication number
WO2019018989A1
WO2019018989A1 PCT/CN2017/094160 CN2017094160W WO2019018989A1 WO 2019018989 A1 WO2019018989 A1 WO 2019018989A1 CN 2017094160 W CN2017094160 W CN 2017094160W WO 2019018989 A1 WO2019018989 A1 WO 2019018989A1
Authority
WO
WIPO (PCT)
Prior art keywords
carrier
terminal device
network device
secondary carrier
rlf
Prior art date
Application number
PCT/CN2017/094160
Other languages
English (en)
French (fr)
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 EP17919441.0A priority Critical patent/EP3661316B1/en
Priority to PCT/CN2017/094160 priority patent/WO2019018989A1/zh
Priority to CN201780090258.7A priority patent/CN110612775B/zh
Priority to US16/621,674 priority patent/US11102057B2/en
Priority to TW107125484A priority patent/TW201909666A/zh
Publication of WO2019018989A1 publication Critical patent/WO2019018989A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
    • H04L41/0668—Management of faults, events, alarms or notifications using network fault recovery by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0453—Resources in frequency domain, e.g. a carrier in FDMA
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • 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
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0003—Two-dimensional division
    • H04L5/0005—Time-frequency
    • H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT
    • H04L5/001—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT the frequencies being arranged in component carriers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/06—Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals

Definitions

  • the present application relates to the field of communications, and in particular, to a method and a terminal device for handling a failure of a wireless link.
  • LTE long term evolution
  • RLC radio link control
  • AM acknowledge mode
  • AMdata protocol data protocol data unit in the acknowledge mode
  • ARQ automatic repeat request
  • the RLF event is triggered by the UE reaching the maximum number of retransmissions of the AMD PDUs occurring in the RLC entities of the primary cell group (MCG) and the secondary cell group (SCG).
  • the packet data convergence protocol layer transmits the generated duplicate data (ie, the PDCP PDU and the copied PDCP PDU) to the two.
  • the generated duplicate data ie, the PDCP PDU and the copied PDCP PDU
  • the two RLC entities are mapped to different physical layer carriers, such as a primary carrier (PCELL) and a secondary carrier (SCELL), and the above-mentioned duplicate data is transmitted through the primary carrier and the secondary carrier.
  • PCELL primary carrier
  • SCELL secondary carrier
  • Radio Resource Control RRC
  • a connection re-establishment may occur, and for the NR CA scenario, For an RLF event to be generated by an RLC entity mapped to a secondary carrier or a primary carrier, it is necessary to rethink how to handle the RLF event.
  • the present application provides a method and a terminal device for processing an RLF, which can improve transmission efficiency.
  • a first aspect provides a method for processing an RLF, where the method includes: the terminal device sends the same packet data convergence protocol PDCP layer data to the network device by using the primary carrier and the secondary carrier; and the RLC entity corresponding to the secondary carrier in the secondary carrier If the number of transmissions of the AMD PDU reaches the maximum number of transmissions, it is determined that the secondary carrier generates an RLF event, and sends the RLF event to the network device.
  • the first RRC reconfiguration information is used by the terminal device to perform RRC connection reconfiguration with the network device.
  • the terminal device may transmit the same data to the network device by using the primary carrier and the secondary carrier, and when the RLF event occurs on the primary carrier or the RLC entity corresponding to the secondary carrier, according to different carrier types, Determine different processing modes, perform RRC connection reconfiguration or RRC reestablishment with the network device, increase data transmission flexibility, and improve transmission efficiency.
  • the method further includes: receiving, by the terminal device, first carrier configuration information that is sent by the network device according to the first RRC reconfiguration information, the first carrier configuration information And the terminal device is configured to send the same PDCP layer data to the network device by using the first carrier instead of the secondary carrier that generates the RLF event.
  • the method further includes: the terminal device sending the first RLF type indication information to the network device, where the first RLF type indication information is used
  • the carrier indicating that the RLF event occurs is the secondary carrier.
  • the method further includes: the terminal device suspending transmission mapping to the secondary carrier when the secondary carrier generates the RLF event Data for all RLC entities.
  • the method further includes: the terminal device suspending transmission mapping to the secondary carrier when the secondary carrier generates the RLF event The data in the at least one RLC entity, the number of transmissions of the AMD PDU in each of the at least one RLC entity reaches the maximum number of retransmissions.
  • the method further includes: the terminal device maintaining the operation of the medium access control MAC entity if the RCF event occurs on the secondary carrier .
  • the method further includes: the terminal device, by using the primary carrier and the network device, when the secondary carrier generates the RLF event
  • the radio bearer signaling SRB carried by the secondary carrier is transmitted and transmitted.
  • the method further includes: the terminal device has a maximum number of transmission times of the AMD PDU in the RLC entity corresponding to the primary carrier. In the case, determining that the primary carrier generates an RLF event, and sending an RRC reestablishment request message to the network device, where the RRC reestablishment request message is used to request the network The network device performs RRC reconstruction.
  • the primary carrier is a primary carrier in the MCG
  • the secondary carrier is a secondary carrier in the MCG
  • the primary carrier is an SCG.
  • the primary carrier in the medium carrier, the secondary carrier being the secondary carrier in the SCG.
  • the primary carrier is a primary carrier in the SCG
  • the secondary carrier is a secondary carrier in the SCG
  • the method further includes: If the number of transmissions of the AMD PDU reaches the maximum number of transmissions in the RLC entity corresponding to the primary carrier in the SCG, the terminal device determines that the primary carrier in the SCG generates an RLF event, and sends a second RRC reconfiguration to the network device.
  • the second RRC reconfiguration information is used by the terminal device to perform RRC connection reconfiguration with the network device.
  • the method further includes: receiving, by the terminal device, the second carrier configuration information that is sent by the network device according to the second RRC reconfiguration information, The second carrier configuration information is used to indicate the second carrier; the terminal device sends the same PDCP layer data to the network device by using the second carrier instead of the primary carrier in the SCG in which the RLF event occurs.
  • the method further includes: the terminal device sending, by the terminal device, second RLF type indication information, where the second RLF type indication information is used
  • the carrier indicating that the RLF event occurs is the primary carrier in the SCG.
  • the terminal device may transmit the same data to the network device by using the primary carrier and the secondary carrier, and when the RLF event occurs on the primary carrier or the RLC entity corresponding to the secondary carrier, according to different carrier types, Determine different processing modes, perform RRC connection reconfiguration or RRC reestablishment with the network device, increase data transmission flexibility, and improve transmission efficiency.
  • 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 storage unit for storing instructions for executing instructions stored in the memory, and a processor, and when the processor executes the instructions stored by the memory The execution causes the processor to perform the method of the first aspect or any possible implementation of the first aspect.
  • a computer readable medium for storing a computer program comprising instructions for performing the method of the first aspect or any of the possible implementations of the first aspect.
  • a computer program product comprising instructions for performing processing in any of the above-described first aspect or any of the possible implementations of the first aspect when the computer runs the finger of the computer program product The method of RLF.
  • the computer program product can be run on the terminal device of the above third aspect.
  • FIG. 1 is a schematic flowchart of a method of processing an RLF according to an embodiment of the present application.
  • FIG. 2 is a schematic diagram of copying and transmitting PDCP layer data according to an embodiment of the present application.
  • FIG. 3 is a schematic block diagram of a terminal device according to an embodiment of the present application.
  • FIG. 4 is another schematic block diagram of a terminal device according to an embodiment of the present application.
  • LTE long term evolution
  • FDD frequency division duplex
  • TDD Time division duplex
  • 4.5 4.5th generation, 4.5G generation network
  • 5th generation, 5G fifth generation
  • NR new radio
  • the terminal device in the embodiment of the present application may also be referred to as a terminal, a user equipment (UE), a mobile station (MS), a mobile terminal (MT), and the like.
  • the terminal device can be a mobile phone, a tablet, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, and an industrial control (industrial control).
  • Wireless terminal wireless terminal in self driving, wireless terminal in remote medical surgery, wireless terminal in smart grid, wireless in transport safety A terminal, a wireless terminal in a smart city, a wireless terminal in a smart home, and the like.
  • the network device involved in the embodiment of the present application is deployed in a radio access network for A device in which a terminal device provides a wireless communication function.
  • the network device may be a base station, and the base station may include various forms of macro base stations, micro base stations, relay stations, access points, and the like.
  • the names of devices with base station functionality may vary.
  • an Evolved NodeB eNB or eNodeB
  • 3G 3rd Generation
  • Base stations and terminal equipment can be deployed on land, indoors or outdoors, hand-held or on-board; they can also be deployed on the water; they can also be deployed on airborne aircraft, balloons and satellites.
  • the application scenarios of the base station and the terminal device are not limited in the embodiment of the present application.
  • FIG. 1 shows a schematic flow diagram of a method 100 of processing an RLF, which may be performed by a terminal device, in accordance with an embodiment of the present application.
  • the method 100 includes: S110.
  • a terminal device sends the same PDCP layer data to a network device by using a primary carrier and a secondary carrier.
  • the embodiment of the present application may be used for the replication transmission in the CA scenario, and the primary carrier and the secondary carrier that the terminal device transmits the same PDCP layer data may respectively refer to one or multiple carriers, that is, the primary carrier may be one carrier, or The carrier group includes multiple carriers, and the secondary carrier may also be one carrier or a carrier group including multiple carriers.
  • the same PDCP layer data transmitted in S110 refers to repeatedly transmitting PDCP layer data packets.
  • FIG. 2 shows a schematic diagram of copying and transmitting PDCP layer data according to an embodiment of the present application.
  • one PDCP entity is bound to two RLC entities.
  • the terminal device performs duplication of the first PDCP PDU to be sent to obtain a second PDCP PDU.
  • the terminal device delivers the first PDCP PDU to one of the two RLC entities, RLC 1, and delivers the second PDCP PDU to another RLC entity RLC2 of the two RLC entities.
  • the two RLC entities respectively process the received PDCP PDU, and send the first PDCP PDU and the second PDCP PDU to the network device by using two different carriers, for example, as shown in FIG. 2, by using carrier 1 and Carrier 2 is separately transmitted, wherein the carrier 1 can be a primary carrier, and the carrier 2 can be a secondary carrier.
  • the process of processing the received PDCP PDU by the two RLC entities is the same as the processing of the PDCP PDU by a single RLC entity when the repeated transmission is not performed in the prior art, and need not be described here.
  • the terminal device may further transmit the PDCP layer data by using more than two carriers, and the terminal device may also send the same data packet to the network device by using M carriers, where M is a positive integer greater than or equal to 3.
  • the terminal device can transmit the PDCP PDU to be sent. Copying, obtaining M data packets including the PDCP PDU to be transmitted, respectively transmitting the M identical data packets to the network device through the M carriers, thereby further improving the reliability of data transmission.
  • the method in which the terminal device processes the RLF in the case where the same data packet is transmitted to the network device through the M carriers is similar to the manner in which the terminal device processes the RLF in the case where the same data packet is transmitted to the network device through the two carriers.
  • the primary carrier may be any one of the M carriers
  • the secondary carrier may be any one of the M carriers.
  • the terminal device is configured to perform the retransmission function.
  • the RLC entity may be configured by the network device through RRC signaling.
  • the network device may configure that the terminal device may use five RLC entities for repeated transmission, and two of the five RLC entities are in an active state, and the terminal device may use the two RLC entities for repeated transmission.
  • the terminal device copies the first PDCP PDU to be transmitted to obtain the second PDCP PDU.
  • the terminal device sends the first PDCP PDU and the second PDCP PDU to two RLC entities, and each RLC entity processes the received PDCP PDU and sends the received PDCP PDU to the MAC entity.
  • the MAC entity processes the data packets sent by the two RLC layers separately, and then sends the two RLC layer data packets to the network device through two different carriers.
  • the process of processing the RLC layer data packet by the MAC layer entity is the same as the manner in which the MAC entity processes the RLC layer data packet when the repeated transmission is not performed, and need not be described here.
  • the duplicate transmission in the repeated transmission data packet or the data packet repetition transmission function in the embodiment of the present application refers to copying one data packet to obtain two or more identical data.
  • the packet transmits the two or more identical data packets using different carriers respectively.
  • the repeated transmission referred to in the embodiment of the present application does not refer to packet retransmission in a mechanism such as an automatic retransmission request.
  • the foregoing carrier may refer to a link with a different network device.
  • the primary carrier may be a primary carrier in the MCG
  • the secondary carrier may be a secondary carrier in the MCG.
  • the primary carrier may be a primary carrier in the SCG
  • the secondary carrier may be a secondary carrier in the SCG. The embodiment is not limited to this.
  • the method 100 further includes: S120, the terminal device determines that the secondary carrier generates an RLF event and sends the first to the network device if the number of transmissions of the AMD PDU reaches the maximum number of transmissions in the RLC entity corresponding to the secondary carrier.
  • RRC reconfiguration information the first RRC reconfiguration information is used by the terminal device to perform RRC connection reconfiguration with the network device.
  • the primary carrier may be a primary carrier in the MCG, or may also be a primary carrier in the SCG.
  • the secondary carrier may be a secondary carrier in the MCG, or may also be in the SCG. Secondary carrier. Therefore, the determining, by the terminal device, that the secondary carrier generates the RLF event further includes determining that the secondary carrier in the MCG generates an RLF event, or generating an RLF event for the secondary carrier in the SCG.
  • the first RRC reconfiguration information sent by the terminal device to the network device may be used by the terminal device to perform RRC connection reconfiguration with the network device, where the RRC connection reconfiguration process may be
  • the RRC connection reconfiguration process is the same as that of the RRC connection reconfiguration process when the RLF event occurs on the carrier in the SCG in the prior art, and is not described here.
  • the RRC connection reconfiguration of the terminal device and the network device may include: the terminal device sends the first RRC reconfiguration information to the network device, and the network device stops transmitting the replication data according to the first RRC reconfiguration information.
  • the data on the secondary carrier through which the RLF event occurs is stopped, the mapping relationship between the RLC entity and the secondary carrier is released, and another new carrier is configured for the RLC entity, for example, the first carrier is configured for the RLC entity, and Sending first carrier configuration information to the terminal device, where the first carrier configuration information is used to indicate the first carrier.
  • the terminal device receives the first carrier configuration information that is sent by the network device according to the first RRC reconfiguration information, where the first carrier configuration information is used to indicate the first carrier, and the terminal device replaces the first carrier with the secondary carrier that generates the RLF time. And transmitting PDCP layer data to the network device by using the first carrier, and restarting transmission of the duplicate data.
  • the terminal device may further send the first RLF type indication information to the network device when the secondary carrier generates the RLF event, where the first RLF type indication information is used to indicate that the carrier where the RLF event occurs is the secondary carrier.
  • the secondary carrier when the RLF event occurs on the secondary carrier, only the data transmission of the RLC entity mapped to the secondary carrier may be suspended, that is, the secondary carrier is suspended, without affecting the data transmission of the primary carrier.
  • the secondary carrier when the secondary carrier generates the RLF event, the secondary carrier may be a secondary carrier in the MCG, or may also be a secondary carrier in the SCG, and may suspend transmission of data transmissions mapped to all RLC entities on the secondary carrier;
  • the data transmission mapped to the partial RLC entity on the secondary carrier may be suspended, that is, the data transmission mapped to the at least one RLC entity on the secondary carrier is suspended, and the AMD PDU exists in each RLC entity in the at least one RLC entity. The number of transmissions reached the maximum number of retransmissions.
  • the data transmission mapped to the RLC entity on the primary carrier may be suspended, and the data transmission mapped to the RLC entity on the corresponding secondary carrier may be suspended, that is, the primary carrier is suspended at the same time.
  • Secondary carrier when the RLF event occurs on the primary carrier, the data transmission mapped to the RLC entity on the primary carrier may be suspended, and the data transmission mapped to the RLC entity on the corresponding secondary carrier may be suspended, that is, the primary carrier is suspended at the same time.
  • the operation of the MAC entity may be continued, so that the data transmission on the primary carrier is not affected.
  • the secondary carrier may be a secondary carrier in the MCG, or may also be a secondary carrier in the SCG, and may maintain MAC entity operations without resetting the MAC entity.
  • the MAC entity when the RLF event occurs on the primary carrier, the MAC entity needs to be reset, where the primary carrier may be a primary carrier in the MCG, or may also be a primary carrier in the SCG.
  • the terminal device may carry a Radio Bearer (SRB) through a secondary carrier.
  • SRB Radio Bearer
  • the terminal device may transmit the secondary carrier by using the primary carrier.
  • the embodiment of the present application is not limited to the SRB carried.
  • the secondary carrier where the RLF event occurs does not carry the SRB, the normal transmission of the SRB is not affected.
  • the method 100 further includes: when the number of transmissions of the AMD PDU in the RLC entity of the primary carrier reaches the maximum number of transmissions, determining that the primary carrier generates an RLF event, where the primary carrier may It is the primary carrier in the MCG, or it can also be the primary carrier in the SCG.
  • the RRC reestablishment request message may be sent to the network device, where the RRC reconfiguration request message is used to request RRC reestablishment with the network device.
  • the network device determines that the carrier that generates the RLF event is the primary carrier, and determines that the RRC reestablishment is performed with the terminal device according to the RRC reconfiguration request message, and may return RRC reestablishment information to the terminal device for performing RRC with the terminal device; or
  • the network may also refuse to perform RRC reestablishment with the terminal according to the RRC reestablishment request message.
  • the RRC reestablishment may be an RRC connection release or an RRC connetction re-establishment.
  • the primary carrier may be a primary carrier in the MCG.
  • the process of performing the RRC re-establishment of the RLF event on the primary carrier of the network device and the network device may be the same as the process of performing the RRC re-establishment of the RLF event of the carrier of the MCG in the prior art, and details are not described herein again.
  • the primary carrier when the RLF event occurs on the primary carrier, the primary carrier may be The terminal device may send the second RRC reconfiguration information to the network device, where the second RRC reconfiguration information is used by the terminal device to perform RRC connection reconfiguration with the network device.
  • the process of the RRC reconfiguration is the same as that in the prior art.
  • the process of the RLF event in the SCG in the SCG needs to be performed in the RRC reconfiguration process, and details are not described herein.
  • the terminal device may receive second carrier configuration information that is sent by the network device according to the second RRC reconfiguration information, where the second carrier configuration information is used. For indicating the second carrier, the terminal device may continue to transmit the same PDCP layer data as the network device by replacing the second carrier with the primary carrier in the SCG in which the RLF event occurs.
  • the terminal device may further send the second RLF type indication information to the network device, where the second RLF type indication information is used to indicate that the carrier where the RLF event occurs is the primary carrier in the SCG.
  • the terminal device may transmit the same data to the network device by using the primary carrier and the secondary carrier, and when the RLF event occurs on the primary carrier or the RLC entity corresponding to the secondary carrier, according to different carrier types.
  • Determine different processing modes perform RRC connection reconfiguration or RRC reestablishment with the network device, increase data transmission flexibility, and improve transmission efficiency.
  • the size of the sequence numbers of the foregoing processes does not mean the order of execution sequence, and the order of execution of each process should be determined by its function and internal logic, and should not be applied to the embodiment of the present application.
  • the implementation process constitutes any limitation.
  • a method for processing an RLF according to an embodiment of the present application is described in detail above with reference to FIG. 1 to FIG. 2, and a terminal device and a network device according to an embodiment of the present application will be described below with reference to FIG. 3 to FIG.
  • the terminal device 200 includes: a sending unit 210 and a determining unit 220, and optionally, a receiving unit 230.
  • the sending unit 210 is configured to: send the same PDCP layer data to the network device by using the primary carrier and the secondary carrier; the determining unit 220 is configured to: the terminal device has the maximum number of transmissions of the AMD PDU in the RLC entity corresponding to the secondary carrier. In the case of the number of transmissions, it is determined that the secondary carrier generates an RLF event, and the first RRC reconfiguration information is sent to the network device by the sending unit, where the first RRC reconfiguration information is used by the terminal device to perform an RRC connection with the network device. Reconfiguration.
  • the terminal device in the embodiment of the present application may transmit the same data to the network device by using the primary carrier and the secondary carrier, and when the RLF event occurs on the primary carrier or the RLC entity corresponding to the secondary carrier, Different processing modes are determined according to different carrier types, and RRC connection reconfiguration or RRC reestablishment is performed with the network device to increase data transmission flexibility and improve transmission efficiency.
  • the receiving unit 230 is configured to: receive the first carrier configuration information that is sent by the network device according to the first RRC reconfiguration information, where the first carrier configuration information is used to indicate the first carrier; And: transmitting the same PDCP layer data to the network device by using the first carrier instead of the secondary carrier that generates the RLF event.
  • the sending unit 210 is configured to send the first RLF type indication information to the network device, where the first RLF type indication information is used to indicate that the carrier where the RLF event occurs is the secondary carrier.
  • the determining unit 220 is specifically configured to: when the RCF event occurs on the secondary carrier, suspend transmission of data mapped to all RLC entities of the secondary carrier.
  • the determining unit 220 is specifically configured to: when the RCF event occurs on the secondary carrier, suspend transmission of data in the at least one RLC entity mapped to the secondary carrier, where each RLC entity in the at least one RLC entity The number of transmissions of AMD PDUs reached the maximum number of retransmissions.
  • the determining unit 220 is specifically configured to: maintain the operation of the medium access control MAC entity if the RCF event occurs on the secondary carrier.
  • the sending unit 210 is configured to: when the RCF event occurs on the secondary carrier, copy and transmit the radio bearer signaling SRB carried by the secondary carrier by using the primary carrier and the network device.
  • the determining unit 220 is configured to: when the number of transmissions of the AMD PDU reaches the maximum number of transmissions in the RLC entity corresponding to the primary carrier, determine that the primary carrier generates an RLF event, and send, by using the sending unit 210, The network device sends an RRC reestablishment request message, where the RRC reestablishment request message is used to request RRC reestablishment with the network device.
  • the primary carrier is a primary carrier in the MCG, and the secondary carrier is a secondary carrier in the MCG; or the primary carrier is a primary carrier in the SCG, and the secondary carrier is a secondary carrier in the SCG.
  • the primary carrier is the primary carrier in the SCG
  • the secondary carrier is the secondary carrier in the SCG
  • the determining unit 220 is specifically configured to: the AMD PDU exists in the RLC entity corresponding to the primary carrier in the SCG.
  • the second RRC reconfiguration information is sent to the network device by using the sending unit 210, where the second RRC reconfiguration information is used for the terminal.
  • the device performs RRC with the network device. Connection reconfiguration.
  • the receiving unit 230 is configured to: receive second carrier configuration information that is sent by the network device according to the second RRC reconfiguration information, where the second carrier configuration information is used to indicate the second carrier; And transmitting the same PDCP layer data to the network device by using the second carrier instead of the primary carrier in the SCG in which the RLF event occurs.
  • the sending unit 210 is specifically configured to: send the second RLF type indication information to the network device, where the second RLF type indication information is used to indicate that the carrier where the RLF event occurs is the primary carrier in the SCG.
  • terminal device 300 may correspond to the method 100 in the embodiment of the present application, and the foregoing and other operations and/or functions of the respective units in the terminal device 300 are respectively implemented to implement FIG. 1 to FIG. 2 .
  • the corresponding processes of the terminal devices in the respective methods are not described herein for the sake of brevity.
  • the terminal device in the embodiment of the present application may transmit the same data to the network device by using the primary carrier and the secondary carrier, and determine different processing according to different carrier types when the RLC event occurs on the primary carrier or the RLC entity corresponding to the secondary carrier.
  • the data transmission flexibility is increased, and the transmission efficiency is improved.
  • FIG. 4 is a schematic block diagram of a terminal device 300 according to an embodiment of the present application.
  • the terminal device 300 includes: a processor 310 and a transceiver 320.
  • the processor 310 is connected to the transceiver 320, and is optional.
  • the terminal device 300 further includes a memory 330, and the memory 330 is connected to the processor 310.
  • the processor 310, the memory 330, and the transceiver 320 communicate with each other through an internal connection path to transfer control and/or data signals.
  • the memory 330 can be used to store instructions, and the processor 310 is configured to execute the memory 330.
  • the instruction is used to control the transceiver 320 to send information or a signal, and the transceiver 320 is configured to: send the same PDCP layer data to the network device by using the primary carrier and the secondary carrier; the processor 310 is configured to: the terminal device corresponds to the secondary carrier If the number of transmissions of the AMD PDU reaches the maximum number of transmissions in the RLC entity, the RLF event is determined to be generated by the secondary carrier, and the first RRC reconfiguration information is sent to the network device by the transceiver 320, where the first RRC reconfiguration is performed. The information is used by the terminal device to perform RRC connection reconfiguration with the network device.
  • the terminal device in the embodiment of the present application may transmit the same data to the network device by using the primary carrier and the secondary carrier, and determine different processing according to different carrier types when the RLC event occurs on the primary carrier or the RLC entity corresponding to the secondary carrier.
  • RRC connection with network equipment Configuration or RRC re-establishment increases data transmission flexibility and improves transmission efficiency.
  • the transceiver 320 is configured to: receive first carrier configuration information that is sent by the network device according to the first RRC reconfiguration information, where the first carrier configuration information is used to indicate the first carrier;
  • the first carrier transmits the same PDCP layer data to the network device instead of the secondary carrier in which the RLF event occurs.
  • the transceiver 320 is configured to send the first RLF type indication information to the network device, where the first RLF type indication information is used to indicate that the carrier where the RLF event occurs is the secondary carrier.
  • the processor 310 is configured to suspend transmission of data of all RLC entities mapped to the secondary carrier if the RCF event occurs on the secondary carrier.
  • the processor 310 is configured to: suspend transmission of data in the at least one RLC entity mapped to the secondary carrier, where the secondary carrier generates the RLF event, in the at least one RLC entity.
  • the number of transmissions of AMD PDUs in each RLC entity reaches the maximum number of retransmissions.
  • the processor 310 is configured to: maintain the operation of the medium access control MAC entity if the RCF event occurs on the secondary carrier.
  • the transceiver 320 is configured to: when the secondary carrier generates the RLF event, copy and transmit the radio bearer signaling SRB carried by the secondary carrier by using the primary carrier and the network device.
  • the processor 310 is configured to: when the number of transmissions of the AMD PDU reaches the maximum number of transmissions in the RLC entity corresponding to the primary carrier, determine that the primary carrier generates an RLF event, and pass the The transceiver 320 sends an RRC reestablishment request message to the network device, where the RRC reestablishment request message is used to request RRC reestablishment with the network device.
  • the primary carrier is a primary carrier in the MCG
  • the secondary carrier is a secondary carrier in the MCG
  • the primary carrier is a primary carrier in the SCG, where the secondary carrier is in the SCG.
  • Secondary carrier is a primary carrier in the MCG
  • the primary carrier is a primary carrier in the SCG
  • the secondary carrier is a secondary carrier in the SCG
  • the processor 310 is configured to: in the RLC entity corresponding to the primary carrier in the SCG. If the number of transmissions of the AMD PDU reaches the maximum number of transmissions, it is determined that the RLF event occurs on the primary carrier in the SCG, and the second RRC reconfiguration information is sent to the network device by the transceiver 320, where the second RRC reconfiguration information is generated. For the terminal device and the network device Perform RRC connection reconfiguration.
  • the transceiver 320 is configured to: receive second carrier configuration information that is sent by the network device according to the second RRC reconfiguration information, where the second carrier configuration information is used to indicate the second carrier;
  • the second carrier transmits the same PDCP layer data to the network device instead of the primary carrier in the SCG in which the RLF event occurs.
  • the transceiver 320 is configured to send the second RLF type indication information to the network device, where the second RLF type indication information is used to indicate that the carrier where the RLF event occurs is the master in the SCG. Carrier.
  • terminal device 300 may correspond to the terminal device 200 in the embodiment of the present application, and may correspond to the corresponding body in the method 100 according to the embodiment of the present application, and each of the terminal devices 300
  • the foregoing and other operations and/or functions of the unit are respectively implemented in order to implement the corresponding processes of the terminal devices in the respective methods in FIG. 1.
  • no further details are provided herein.
  • the terminal device in the embodiment of the present application may transmit the same data to the network device by using the primary carrier and the secondary carrier, and determine different processing according to different carrier types when the RLC event occurs on the primary carrier or the RLC entity corresponding to the secondary carrier.
  • the data transmission flexibility is increased, and the transmission efficiency is improved.
  • the processor may be an integrated circuit chip with signal processing capabilities.
  • each step of the foregoing method embodiments may be completed by an integrated logic circuit of hardware in a processor or an instruction in a form of software.
  • the processor may be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a Field Programmable Gate Array (FPGA), or the like. Programming logic devices, discrete gates or transistor logic devices, discrete hardware components.
  • the methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the steps of the method disclosed in the embodiments of the present application may be directly implemented by the hardware decoding processor, or may be performed by a combination of hardware and software modules in the decoding 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, and the processor reads the information in the memory and combines the hardware to complete the steps of the above method.
  • the memory in the embodiment of the present application may be a volatile memory or a non-volatile memory.
  • the memory may include both volatile and non-volatile memory.
  • the non-volatile memory may be a read-only memory (ROM), a programmable read only memory (PROM), an erasable programmable read only memory (Erasable PROM, EPROM), or an electric Erase programmable read only memory (EEPROM) or flash memory.
  • the volatile memory can be a Random Access Memory (RAM) that acts as an external cache.
  • RAM Random Access Memory
  • many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (Synchronous DRAM).
  • SDRAM Double Data Rate SDRAM
  • DDR SDRAM Double Data Rate SDRAM
  • ESDRAM Enhanced Synchronous Dynamic Random Access Memory
  • SLDRAM Synchronous Connection Dynamic Random Access Memory
  • DR RAM direct memory bus random access memory
  • 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 Can be integrated 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 unit described as a separate component may or may not be physically separated, and the component displayed as a unit may or may not be a physical unit, that is, may be located in one place. Or it can be distributed to multiple network elements. 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.
  • the functions may be stored in a computer readable storage medium if implemented in the form of a software functional unit and sold or used as a standalone product.
  • 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 the methods described in 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. .

Landscapes

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

Abstract

本申请实施例涉及处理无线链路失败的方法和终端设备。该方法包括：终端设备通过主载波和辅载波向网络设备发送相同的分组数据汇聚协议PDCP层数据；该终端设备在该辅载波对应的RLC实体中存在AMD PDU的传输次数达到最大传输次数的情况下，确定该辅载波发生RLF事件，并向该网络设备发送第一RRC重配置信息，该第一RRC重配置信息用于该终端设备与该网络设备进行RRC连接重配置。本申请实施例的处理RLF的方法和终端设备，在载波对应的RLC实体发生RLF事件时，根据载波类型的不同，确定不同的处理方式，与网络设备进行RRC连接重配置或者RRC重建，增加数据传输灵活性，并提高传输效率。

Description

处理无线链路失败的方法和终端设备 技术领域
本申请涉及通信领域，尤其涉及处理无线链路失败的方法和终端设备。
背景技术
在长期演进(long term evolution，LTE)***中，在无线链路控制(radio link control，RLC)实体处于确认模式(acknowledged mode，AM)时，当存在确认模式下的协议数据单元(AMdata protocol data unit，AMD PDU)的传输次数达到最大自动重传请求(automatic repeat request，ARQ)重传次数时，触发无线链路失败(radio link failure，RLF)事件，RLC实体上报网络设备。
在LTE中，UE对主小区组(master cell group，MCG)和次小区组(secondary cell group，SCG)的RLC实体中所发生的AMD PDU达到最大重传次数都触发RLF事件。
在NR中，针对载波聚合(carrier aggregation，CA)场景下的复制数据传输，分组数据汇聚协议(packet data convergence protocol)层将生成的复制数据(即PDCP PDU和复制的PDCP PDU)分别传输到两个不同的RLC实体，两个RLC实体映射到不同的物理层载波，比如主载波(PCELL)和辅载波(SCELL)，通过该主载波和辅载波传输上述复制数据。现有LTE在处理RLF时，如果是MCG，则会发生无线资源控制(Radio Resource Control，RRC)连接释放(connection release)或者RRC连接重建立(connection re-establishment)，而对于NR中CA场景，对于映射到辅载波或者主载波的RLC实体发生RLF事件，需要重新考虑如何处理RLF事件。
发明内容
本申请提供了一种处理RLF的方法和终端设备，能够提高传输效率。
第一方面，提供了一种处理RLF的方法，该方法包括：终端设备通过主载波和辅载波向网络设备发送相同的分组数据汇聚协议PDCP层数据；该终端设备在该辅载波对应的RLC实体中存在AMD PDU的传输次数达到最大传输次数的情况下，确定该辅载波发生RLF事件，并向该网络设备发送 第一RRC重配置信息，该第一RRC重配置信息用于该终端设备与该网络设备进行RRC连接重配置。
因此，本申请实施例的处理RLF的方法，终端设备可以通过主载波和辅载波与网络设备传输相同的数据，在主载波或者辅载波对应的RLC实体发生RLF事件时，根据载波类型的不同，确定不同的处理方式，与网络设备进行RRC连接重配置或者RRC重建，增加数据传输灵活性，并提高传输效率。
结合第一方面，在第一方面的一种实现方式中，该方法还包括：该终端设备接收该网络设备根据该第一RRC重配置信息发送的第一载波配置信息，该第一载波配置信息用于指示第一载波；该终端设备通过该第一载波代替发生该RLF事件的该辅载波向该网络设备发送该相同的PDCP层数据。
结合第一方面及其上述实现方式，在第一方面的另一种实现方式中，该方法还包括：该终端设备向该网络设备发送第一RLF类型指示信息，该第一RLF类型指示信息用于指示发生该RLF事件的载波为该辅载波。
结合第一方面及其上述实现方式，在第一方面的另一种实现方式中，该方法还包括：该终端设备在该辅载波发生该RLF事件的情况下，暂停传输映射到该辅载波的所有RLC实体的数据。
结合第一方面及其上述实现方式，在第一方面的另一种实现方式中，该方法还包括：该终端设备在该辅载波发生该RLF事件的情况下，暂停传输映射到该辅载波的至少一个RLC实体中的数据，该至少一个RLC实体中每个RLC实体中存在AMD PDU的传输次数达到最大重传次数。
结合第一方面及其上述实现方式，在第一方面的另一种实现方式中，该方法还包括：该终端设备在该辅载波发生该RLF事件的情况下，维持介质访问控制MAC实体的操作。
结合第一方面及其上述实现方式，在第一方面的另一种实现方式中，该方法还包括：该终端设备在该辅载波发生该RLF事件的情况下，通过该主载波与该网络设备复制传输该辅载波承载的无线承载信令SRB。
结合第一方面及其上述实现方式，在第一方面的另一种实现方式中，该方法还包括：该终端设备在该主载波对应的RLC实体中存在AMD PDU的传输次数达到最大传输次数的情况下，确定该主载波发生RLF事件，并向该网络设备发送RRC重建请求消息，该RRC重建请求消息用于请求与该网 络设备进行RRC重建。
结合第一方面及其上述实现方式，在第一方面的另一种实现方式中，该主载波为MCG中的主载波，该辅载波为该MCG中的辅载波；或，该主载波为SCG中的主载波，该辅载波为该SCG中的辅载波。
结合第一方面及其上述实现方式，在第一方面的另一种实现方式中，该主载波为该SCG中的主载波，该辅载波为该SCG中的辅载波，该方法还包括：该终端设备在该SCG中的主载波对应的RLC实体中存在AMD PDU的传输次数达到最大传输次数的情况下，确定该SCG中的主载波发生RLF事件，并向该网络设备发送第二RRC重配置信息，该第二RRC重配置信息用于该终端设备与该网络设备进行RRC连接重配置。
结合第一方面及其上述实现方式，在第一方面的另一种实现方式中，该方法还包括：该终端设备接收该网络设备根据该第二RRC重配置信息发送的第二载波配置信息，该第二载波配置信息用于指示第二载波；该终端设备通过该第二载波代替发生该RLF事件的该SCG中的主载波向该网络设备发送该相同的PDCP层数据。
结合第一方面及其上述实现方式，在第一方面的另一种实现方式中，该方法还包括：该终端设备向该网络设备发送第二RLF类型指示信息，该第二RLF类型指示信息用于指示发生该RLF事件的载波为该SCG中的主载波。
因此，本申请实施例的处理RLF的方法，终端设备可以通过主载波和辅载波与网络设备传输相同的数据，在主载波或者辅载波对应的RLC实体发生RLF事件时，根据载波类型的不同，确定不同的处理方式，与网络设备进行RRC连接重配置或者RRC重建，增加数据传输灵活性，并提高传输效率。
第二方面，提供了一种终端设备，用于执行上述第一方面或第一方面的任意可能的实现方式中的方法。具体地，该终端设备包括用于执行上述第一方面或第一方面的任意可能的实现方式中的方法的单元。
第三方面，提供了一种终端设备，包括：存储单元和处理器，该存储单元用于存储指令，该处理器用于执行该存储器存储的指令，并且当该处理器执行该存储器存储的指令时，该执行使得该处理器执行第一方面或第一方面的任意可能的实现方式中的方法。
第四方面，提供了一种计算机可读介质，用于存储计算机程序，该计算机程序包括用于执行第一方面或第一方面的任意可能的实现方式中的方法的指令。
第五方面，提供了一种包括指令的计算机程序产品，当计算机运行所述计算机程序产品的所述指时，所述计算机执行上述第一方面或第一方面的任意可能的实现方式中的处理RLF的方法。具体地，该计算机程序产品可以运行于上述第三方面的终端设备上。
附图说明
图1是根据本申请实施例的处理RLF的方法的示意性流程图。
图2是根据本申请实施例的复制传输PDCP层数据的示意图。
图3是根据本申请实施例的终端设备的示意性框图。
图4是根据本申请实施例的终端设备的另一示意性框图。
具体实施方式
下面将结合附图，对本申请实施例中的技术方案进行描述。
应理解，本申请实施例的技术方案可以应用于各种通信***，例如：长期演进(long term evolution，LTE)***、LTE频分双工(frequency division duplex，FDD)***、LTE时分双工(time division duplex，TDD)、第4.5(4.5th generation，4.5G)代网络、第五代(5th generation，5G)网络、新空口(new radio，NR)等。
本申请实施例中的终端设备也可以称为终端(Terminal)、用户设备(user equipment，UE)、移动台(mobile station，MS)、移动终端(mobile terminal，MT)等。终端设备可以是手机(mobile phone)、平板电脑(Pad)、带无线收发功能的电脑、虚拟现实(Virtual Reality，VR)终端设备、增强现实(Augmented Reality，AR)终端设备、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程手术(remote medical surgery)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端等等。
本申请实施例所涉及到的网络设备是一种部署在无线接入网中用以为 终端设备提供无线通信功能的装置。所述网络设备可以为基站，所述基站可以包括各种形式的宏基站，微基站，中继站，接入点等。在采用不同的无线接入技术的***中，具有基站功能的设备的名称可能会有所不同。例如在LTE网络中，称为演进的节点B(Evolved NodeB，eNB或eNodeB)，在第三代(3rd Generation，3G)网络中，称为节点B(Node B)等等。
基站和终端设备可以部署在陆地上，包括室内或室外、手持或车载；也可以部署在水面上；还可以部署在空中的飞机、气球和卫星上。本申请的实施例对基站和终端设备的应用场景不做限定。
图1示出了根据本申请实施例的处理RLF的方法100的示意性流程图，该方法100可以由终端设备执行。
如图1所示，该方法100包括：S110，终端设备通过主载波和辅载波向网络设备发送相同的PDCP层数据。
应理解，本申请实施例可以用于CA场景下的复制传输，终端设备传输相同的PDCP层数据的主载波和辅载波可以分别指一个或多个载波，即该主载波可以为一个载波，或者包括多个载波的载波组，辅载波也可以为一个载波，或者包括多个载波的载波组。
在本申请实施例中，S110中传输的相同的PDCP层数据是指重复传输PDCP层数据包。具体地，图2示出了根据本申请实施例的复制传输PDCP层数据的示意图。如图2所示，一个PDCP实体与两个RLC实体绑定。该终端设备将待发送的第一PDCP PDU进行复制(duplication)，得到第二PDCP PDU。终端设备将该第一PDCP PDU下发到该两个RLC实体中的一个RLC实体RLC 1，将该第二PDCP PDU下发到该两个RLC实体中的另一个RLC实体RLC2。该两个RLC实体分别对收到的PDCP PDU进行处理，并通过两个不同的载波将该第一PDCP PDU和该第二PDCP PDU发送至网络设备，例如如图2所示，通过载波1和载波2分别发送，其中，该载波1可以为主载波，载波2可以为辅载波。该两个RLC实体对接收到的PDCP PDU进行处理的过程与现有技术中不进行重复传输时单个RLC实体处理PDCP PDU的方式相同，在此就不必赘述。
可选地，终端设备还可以通过多于两个载波传输该PDCP层数据，该终端设备还可以通过M个载波向该网络设备发送相同的数据包，其中M为大于或等于3的正整数。在此情况下，该终端设备可以将待发送的PDCP PDU 复制，得到包括该待发送的PDCP PDU在内的M个数据包，分别通过该M个载波将该M个相同的数据包发送至网络设备，从而进一步提高数据传输的可靠性。该终端设备在通过M个载波向该网络设备发送相同的数据包的情况下处理RLF的方法与该终端设备在通过两个载波向网络设备发送相同的数据包的情况下处理RLF的方式类似。换句话说，该主载波可以该M个载波中的任意一个主载波，该辅载波可以为该M个载波中的任意一个辅载波。
应理解，终端设备用于进行重复传输功能RLC实体可以由网络设备通过RRC信令进行配置。例如，该网络设备可以配置该终端设备可以使用五个RLC实体进行重复传输，且五个RLC实体中的两个RLC实体处于激活状态，则该终端设备可以使用该两个RLC实体进行重复传输。
在重复传输PDCP PDU层数据包的情况下，该终端设备会将待发送的第一PDCP PDU复制，得到第二PDCP PDU。终端设备将该第一PDCP PDU和该第二PDCP PDU分别发送至两个RLC实体，每个RLC实体会对接收到的PDCP PDU进行处理，并发送至MAC实体。MAC实体会分别对两个RLC层发送的数据包进行处理，再通过两个不同的载波将两个RLC层数据包发送至该网络设备。MAC层实体对RLC层数据包进行处理的过程与中不进行重复传输时MAC实体处理RLC层数据包的方式相同在此就不必赘述。
可以理解的是，本申请实施例中所称的重复传输数据包或者数据包重复传输功能中的重复传输(duplicated transmission)是指将一个数据包复制后得到两个或者两个以上的相同的数据包，分别采用不同载波传输这两个或两个以上的相同的数据包。本申请实施例中所称的重复传输并不是指自动重传请求等机制中的数据包重传(retransmission)。
可选的，在另外一些实施例中，比如双连接场景下，上述载波可以是指与不同网络设备之间的连接(link)。例如，该主载波可以为MCG中的主载波，该辅载波可以为MCG中的辅载波；或者，该主载波可以为SCG中的主载波，该辅载波可以为SCG中的辅载波，本申请实施例并不限于此。
该方法100还包括：S120，该终端设备在该辅载波对应的RLC实体中存在AMD PDU的传输次数达到最大传输次数的情况下，确定该辅载波发生RLF事件，并向该网络设备发送第一RRC重配置信息，该第一RRC重配置信息用于该终端设备与该网络设备进行RRC连接重配置。
应理解，对于双连接场景，该主载波可以为MCG中的主载波，或者还可以为SCG中的主载波，对应的，该辅载波可以为MCG中的辅载波，或者还可以为SCG中的辅载波。因此，终端设备确定辅载波发生RLF事件还包括具体确定该MCG中的辅载波发生RLF事件，或者为SCG中的辅载波发生RLF事件。
应理解，终端设备在辅载波发生RLF事件时，向网络设备发送的第一RRC重配置信息可以用于终端设备与网络设备进行RRC连接重配置，其中，该RRC连接重配置的过程可以与现有技术相同，具体地，可以与现有技术中SCG中的载波发生RLF事件时进行的RRC连接重配置过程相同，在此不再赘述。
可选地，作为一个实施例，终端设备与网络设备进行RRC连接重配置可以包括：终端设备向网络设备发送第一RRC重配置信息，网络设备根据该第一RRC重配置信息，停止传输复制数据，即停止传输通过发生RLF事件的辅载波上的数据，释放RLC实体与该辅载之间的映射关系，重新为该RLC实体配置另一个新的载波，例如为RLC实体配置第一载波，并向终端设备发送第一载波配置信息，该第一载波配置信息用于指示该第一载波。则终端设备接收网络设备根据该第一RRC重配置信息发送的第一载波配置信息，该第一载波配置信息用于指示第一载波，终端设备将该第一载波代替发生该RLF时间的辅载波，通过该第一载波向网络设备发送PDCP层数据，重新开始复制数据的传输。
本申请实施例中，终端设备还可以在辅载波发生RLF事件时向网络设备发送第一RLF类型指示信息，该第一RLF类型指示信息用于指示发生RLF事件的载波为辅载波。
在本申请实施例中，当辅载波发生RLF事件时，可以仅暂停映射到该辅载波的RLC实体的数据传输，即挂起该辅载波，而不影响主载波的数据传输。具体地，在辅载波发生RLF事件时，该辅载波可以为MCG中的辅载波，或者还可以为SCG中的辅载波，可以暂停传输映射到该辅载波上的全部RLC实体的数据传输；还可以暂停传输映射到该辅载波上的部分RLC实体的数据传输，即暂停传输映射到该辅载波上的至少一个RLC实体的数据传输，该至少一个RLC实体中每个RLC实体中都存在AMD PDU的传输次数达到最大重传次数。
可选地，当主载波发生RLF事件时，可以暂停映射到该主载波上的RLC实体的数据传输，还可以暂停映射到对应的辅载波上的RLC实体的数据传输，即同时挂起主载波和辅载波。
在本申请实施例中，当辅载波发生RLF事件时，可以继续维持MAC实体的操作，从而不影响主载波上的数据传输。具体地，在辅载波发生RLF事件时，该辅载波可以为MCG中的辅载波，或者还可以为SCG中的辅载波，可以维持MAC实体操作，而无需重置MAC实体。
可选地，当主载波发生RLF事件时，需要重置MAC实体，其中，该主载波可以为MCG中的主载波，或者还可以为SCG中的主载波。
在本申请实施例中，终端设备可以通过辅载波承载无线承载信令(Signaling Radio Bearer，SRB)，当用于承载SRB的辅载波发生RLF事件时，终端设备可以通过主载波复制传输该辅载波承载的SRB，本申请实施例并不限于此。
可选地，若该发生RLF事件的辅载波不承载SRB，则不影响SRB的正常传输。
在本申请实施例中，该方法100还包括：终端设备在主载波的RLC实体中存在AMD PDU的传输次数达到最大传输次数的情况下，确定该主载波发生RLF事件，其中，该主载波可以为MCG中的主载波，或者还可以为SCG中的主载波。
可选地，作为一个实施例，在该主载波发生RLF事件时，可以向网络设备发送RRC重建请求消息，该RRC重建请求消息用于请求与网络设备进行RRC重建。网络设备确定该发生RLF事件的载波为主载波，根据该RRC重建请求消息，确定与终端设备进行RRC重建，则可以向该终端设备返回RRC重建信息，用于与终端设备进行RRC；或者，该网络也可以根据该RRC重建请求消息，拒绝与终端进行RRC重建。其中，该RRC重建可以为RRC connection release或RRC connetction re-establishment。可选地，该主载波可以为MCG中的主载波。
应理解，终端设备与网络设备在主载波发生RLF事件进行RRC重建的过程可以与现有技术中MCG的载波发生RLF事件进行RRC重建的过程相同，在此不再赘述。
可选地，作为一个实施例，在该主载波发生RLF事件时，该主载波可 以为SCG中的主载波，则终端设备可以向网络设备发送第二RRC重配置信息，该第二RRC重配置信息用于终端设备与网络设备进行RRC连接重配置。具体地，该RRC重配置的过程与现有技术相同，例如与现有技术中SCG中的载波发生RLF事件需要进行RRC重配置的过程相同，在此不再赘述。
可选地，作为一个实施例，在终端设备与网络设备进行RRC连接重配置过程中，终端设备可以接收网络设备根据第二RRC重配置信息发送的第二载波配置信息，该第二载波配置信息用于指示第二载波，终端设备可以将该第二载波代替发生RLF事件的SCG中的主载波，继续与网络设备传输相同的PDCP层数据。
可选地，终端设备还可以向网络设备发送第二RLF类型指示信息，该第二RLF类型指示信息用于指示发生RLF事件的载波为SCG中的主载波。
因此，本申请实施例中的处理RLF的方法，终端设备可以通过主载波和辅载波与网络设备传输相同的数据，在主载波或者辅载波对应的RLC实体发生RLF事件时，根据载波类型的不同，确定不同的处理方式，与网络设备进行RRC连接重配置或者RRC重建，增加数据传输灵活性，并提高传输效率。
应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
上文中结合图1至图2，详细描述了根据本申请实施例的处理RLF的方法，下面将结合图3至图4，描述根据本申请实施例的终端设备和网络设备。
如图3所示，根据本申请实施例的终端设备200包括：发送单元210和确定单元220，可选的，还可以包括接收单元230。
该发送单元210用于：通过主载波和辅载波向网络设备发送相同的PDCP层数据；该确定单元220用于：该终端设备在该辅载波对应的RLC实体中存在AMD PDU的传输次数达到最大传输次数的情况下，确定该辅载波发生RLF事件，并通过该发送单元向该网络设备发送第一RRC重配置信息，该第一RRC重配置信息用于该终端设备与该网络设备进行RRC连接重配置。
因此，本申请实施例的终端设备，可以通过主载波和辅载波与网络设备传输相同的数据，在主载波或者辅载波对应的RLC实体发生RLF事件时， 根据载波类型的不同，确定不同的处理方式，与网络设备进行RRC连接重配置或者RRC重建，增加数据传输灵活性，并提高传输效率。
可选的，该接收单元230用于：接收该网络设备根据该第一RRC重配置信息发送的第一载波配置信息，该第一载波配置信息用于指示第一载波；该发送单元210具体用于：通过该第一载波代替发生该RLF事件的该辅载波向该网络设备发送该相同的PDCP层数据。
可选的，该发送单元210具体用于：向该网络设备发送第一RLF类型指示信息，该第一RLF类型指示信息用于指示发生该RLF事件的载波为该辅载波。
可选的，该确定单元220具体用于：在该辅载波发生该RLF事件的情况下，暂停传输映射到该辅载波的所有RLC实体的数据。
可选的，该确定单元220具体用于：在该辅载波发生该RLF事件的情况下，暂停传输映射到该辅载波的至少一个RLC实体中的数据，该至少一个RLC实体中每个RLC实体中存在AMD PDU的传输次数达到最大重传次数。
可选的，该确定单元220具体用于：在该辅载波发生该RLF事件的情况下，维持介质访问控制MAC实体的操作。
可选的，该发送单元210具体用于：在该辅载波发生该RLF事件的情况下，通过该主载波与该网络设备复制传输该辅载波承载的无线承载信令SRB。
可选的，该确定单元220具体用于：在该主载波对应的RLC实体中存在AMD PDU的传输次数达到最大传输次数的情况下，确定该主载波发生RLF事件，并通过该发送单元210向该网络设备发送RRC重建请求消息，该RRC重建请求消息用于请求与该网络设备进行RRC重建。
可选的，该主载波为MCG中的主载波，该辅载波为该MCG中的辅载波；或，该主载波为SCG中的主载波，该辅载波为该SCG中的辅载波。
可选的，该主载波为该SCG中的主载波，该辅载波为该SCG中的辅载波，该确定单元220具体用于：在该SCG中的主载波对应的RLC实体中存在AMD PDU的传输次数达到最大传输次数的情况下，确定该SCG中的主载波发生RLF事件，并通过该发送单元210向该网络设备发送第二RRC重配置信息，该第二RRC重配置信息用于该终端设备与该网络设备进行RRC 连接重配置。
可选的，该接收单元230用于：接收该网络设备根据该第二RRC重配置信息发送的第二载波配置信息，该第二载波配置信息用于指示第二载波；该发送单元210具体用于：通过该第二载波代替发生该RLF事件的该SCG中的主载波向该网络设备发送该相同的PDCP层数据。
可选的，该发送单元210具体用于：向该网络设备发送第二RLF类型指示信息，该第二RLF类型指示信息用于指示发生该RLF事件的载波为该SCG中的主载波。
应理解，根据本申请实施例的终端设备300可对应于执行本申请实施例中的方法100，并且终端设备300中的各个单元的上述和其它操作和/或功能分别为了实现图1至图2中的各个方法中终端设备的相应流程，为了简洁，在此不再赘述。
因此，本申请实施例的终端设备，可以通过主载波和辅载波与网络设备传输相同的数据，在主载波或者辅载波对应的RLC实体发生RLF事件时，根据载波类型的不同，确定不同的处理方式，与网络设备进行RRC连接重配置或者RRC重建，增加数据传输灵活性，并提高传输效率。
图4示出了根据本申请实施例的终端设备300的示意性框图，如图4所示，该终端设备300包括：处理器310和收发器320，处理器310和收发器320相连，可选地，该终端设备300还包括存储器330，存储器330与处理器310相连。其中，处理器310、存储器330和收发器320之间通过内部连接通路互相通信，传递控制和/或数据信号，该存储器330可以用于存储指令，该处理器310用于执行该存储器330存储的指令，以控制收发器320发送信息或信号，该收发器320用于：通过主载波和辅载波向网络设备发送相同的PDCP层数据；该处理器310用于：该终端设备在该辅载波对应的RLC实体中存在AMD PDU的传输次数达到最大传输次数的情况下，确定该辅载波发生RLF事件，并通过该收发器320向该网络设备发送第一RRC重配置信息，该第一RRC重配置信息用于该终端设备与该网络设备进行RRC连接重配置。
因此，本申请实施例的终端设备，可以通过主载波和辅载波与网络设备传输相同的数据，在主载波或者辅载波对应的RLC实体发生RLF事件时，根据载波类型的不同，确定不同的处理方式，与网络设备进行RRC连接重 配置或者RRC重建，增加数据传输灵活性，并提高传输效率。
可选的，作为一个实施例，该收发器320用于：接收该网络设备根据该第一RRC重配置信息发送的第一载波配置信息，该第一载波配置信息用于指示第一载波；通过该第一载波代替发生该RLF事件的该辅载波向该网络设备发送该相同的PDCP层数据。
可选的，作为一个实施例，该收发器320用于：向该网络设备发送第一RLF类型指示信息，该第一RLF类型指示信息用于指示发生该RLF事件的载波为该辅载波。
可选的，作为一个实施例，该处理器310用于：在该辅载波发生该RLF事件的情况下，暂停传输映射到该辅载波的所有RLC实体的数据。
可选的，作为一个实施例，该处理器310用于：在该辅载波发生该RLF事件的情况下，暂停传输映射到该辅载波的至少一个RLC实体中的数据，该至少一个RLC实体中每个RLC实体中存在AMD PDU的传输次数达到最大重传次数。
可选的，作为一个实施例，该处理器310用于：在该辅载波发生该RLF事件的情况下，维持介质访问控制MAC实体的操作。
可选的，作为一个实施例，该收发器320用于：在该辅载波发生该RLF事件的情况下，通过该主载波与该网络设备复制传输该辅载波承载的无线承载信令SRB。
可选的，作为一个实施例，该处理器310用于：在该主载波对应的RLC实体中存在AMD PDU的传输次数达到最大传输次数的情况下，确定该主载波发生RLF事件，并通过该收发器320向该网络设备发送RRC重建请求消息，该RRC重建请求消息用于请求与该网络设备进行RRC重建。
可选的，作为一个实施例，该主载波为MCG中的主载波，该辅载波为该MCG中的辅载波；或，该主载波为SCG中的主载波，该辅载波为该SCG中的辅载波。
可选的，作为一个实施例，该主载波为该SCG中的主载波，该辅载波为该SCG中的辅载波，该处理器310用于：在该SCG中的主载波对应的RLC实体中存在AMD PDU的传输次数达到最大传输次数的情况下，确定该SCG中的主载波发生RLF事件，并通过该收发器320向该网络设备发送第二RRC重配置信息，该第二RRC重配置信息用于该终端设备与该网络设备 进行RRC连接重配置。
可选的，作为一个实施例，该收发器320用于：接收该网络设备根据该第二RRC重配置信息发送的第二载波配置信息，该第二载波配置信息用于指示第二载波；通过该第二载波代替发生该RLF事件的该SCG中的主载波向该网络设备发送该相同的PDCP层数据。
可选的，作为一个实施例，该收发器320用于：向该网络设备发送第二RLF类型指示信息，该第二RLF类型指示信息用于指示发生该RLF事件的载波为该SCG中的主载波。
应理解，根据本申请实施例的终端设备300可对应于本申请实施例中的终端设备200，并可以对应于执行根据本申请实施例的方法100中的相应主体，并且终端设备300中的各个单元的上述和其它操作和/或功能分别为了实现图1中的各个方法中终端设备的相应流程，为了简洁，在此不再赘述。
因此，本申请实施例的终端设备，可以通过主载波和辅载波与网络设备传输相同的数据，在主载波或者辅载波对应的RLC实体发生RLF事件时，根据载波类型的不同，确定不同的处理方式，与网络设备进行RRC连接重配置或者RRC重建，增加数据传输灵活性，并提高传输效率。
应注意，本申请上述方法实施例可以应用于处理器中，或者由处理器实现。处理器可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现成可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。
可以理解，本申请实施例中的存储器可以是易失性存储器或非易失性存 储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(RandomAccess Memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(Synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，DR RAM)。应注意，本文描述的***和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的***、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的***、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个***，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方， 或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (24)

  1. 一种处理无线链路失败RLF的方法，其特征在于，包括：
    终端设备通过主载波和辅载波向网络设备发送相同的分组数据汇聚协议PDCP层数据；
    所述终端设备在所述辅载波对应的无线链路控制RLC实体中存在确认模式下的协议数据单元AMD PDU的传输次数达到最大传输次数的情况下，确定所述辅载波发生RLF事件，并向所述网络设备发送第一无线资源控制RRC重配置信息，所述第一RRC重配置信息用于所述终端设备与所述网络设备进行RRC连接重配置。
  2. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    所述终端设备接收所述网络设备根据所述第一RRC重配置信息发送的第一载波配置信息，所述第一载波配置信息用于指示第一载波；
    所述终端设备通过所述第一载波代替发生所述RLF事件的所述辅载波向所述网络设备发送所述相同的PDCP层数据。
  3. 根据权利要求1或2所述的方法，其特征在于，所述方法还包括：
    所述终端设备向所述网络设备发送第一RLF类型指示信息，所述第一RLF类型指示信息用于指示发生所述RLF事件的载波为所述辅载波。
  4. 根据权利要求1至3中任一项所述的方法，其特征在于，所述方法还包括：
    所述终端设备在所述辅载波发生所述RLF事件的情况下，暂停传输映射到所述辅载波的所有RLC实体的数据。
  5. 根据权利要求1至3中任一项所述的方法，其特征在于，所述方法还包括：
    所述终端设备在所述辅载波发生所述RLF事件的情况下，暂停传输映射到所述辅载波的至少一个RLC实体中的数据，所述至少一个RLC实体中每个RLC实体中存在AMD PDU的传输次数达到最大重传次数。
  6. 根据权利要求1至5中任一项所述的方法，其特征在于，所述方法还包括：
    所述终端设备在所述辅载波发生所述RLF事件的情况下，维持介质访问控制MAC实体的操作。
  7. 根据权利要求1至6中任一项所述的方法，其特征在于，所述方法 还包括：
    所述终端设备在所述辅载波发生所述RLF事件的情况下，通过所述主载波与所述网络设备复制传输所述辅载波承载的无线承载信令SRB。
  8. 根据权利要求1至7中任一项所述的方法，其特征在于，所述方法还包括：
    所述终端设备在所述主载波对应的RLC实体中存在AMD PDU的传输次数达到最大传输次数的情况下，确定所述主载波发生RLF事件，并向所述网络设备发送RRC重建请求消息，所述RRC重建请求消息用于请求与所述网络设备进行RRC重建。
  9. 根据权利要求1至7中任一项所述的方法，其特征在于，所述主载波为主小区组MCG中的主载波，所述辅载波为所述MCG中的辅载波；或
    所述主载波为次小区组SCG中的主载波，所述辅载波为所述SCG中的辅载波。
  10. 根据权利要求9所述的方法，其特征在于，所述主载波为所述SCG中的主载波，所述辅载波为所述SCG中的辅载波，所述方法还包括：
    所述终端设备在所述SCG中的主载波对应的RLC实体中存在AMDPDU的传输次数达到最大传输次数的情况下，确定所述SCG中的主载波发生RLF事件，并向所述网络设备发送第二RRC重配置信息，所述第二RRC重配置信息用于所述终端设备与所述网络设备进行RRC连接重配置。
  11. 根据权利要求10所述的方法，其特征在于，所述方法还包括：
    所述终端设备接收所述网络设备根据所述第二RRC重配置信息发送的第二载波配置信息，所述第二载波配置信息用于指示第二载波；
    所述终端设备通过所述第二载波代替发生所述RLF事件的所述SCG中的主载波向所述网络设备发送所述相同的PDCP层数据。
  12. 根据权利要求10或11所述的方法，其特征在于，所述方法还包括：
    所述终端设备向所述网络设备发送第二RLF类型指示信息，所述第二RLF类型指示信息用于指示发生所述RLF事件的载波为所述SCG中的主载波。
  13. 一种终端设备，其特征在于，包括：
    发送单元，用于通过主载波和辅载波向网络设备发送相同的分组数据汇聚协议PDCP层数据；
    确定单元，用于所述终端设备在所述辅载波对应的无线链路控制RLC实体中存在确认模式下的协议数据单元AMD PDU的传输次数达到最大传输次数的情况下，确定所述辅载波发生RLF事件，并通过所述发送单元向所述网络设备发送第一无线资源控制RRC重配置信息，所述第一RRC重配置信息用于所述终端设备与所述网络设备进行RRC连接重配置。
  14. 根据权利要求13所述的终端设备，其特征在于，所述终端设备还包括：
    接收单元，用于接收所述网络设备根据所述第一RRC重配置信息发送的第一载波配置信息，所述第一载波配置信息用于指示第一载波；
    所述发送单元具体用于：
    通过所述第一载波代替发生所述RLF事件的所述辅载波向所述网络设备发送所述相同的PDCP层数据。
  15. 根据权利要求13或14所述的终端设备，其特征在于，所述发送单元具体用于：
    向所述网络设备发送第一RLF类型指示信息，所述第一RLF类型指示信息用于指示发生所述RLF事件的载波为所述辅载波。
  16. 根据权利要求13至15中任一项所述的终端设备，其特征在于，所述确定单元具体用于：
    在所述辅载波发生所述RLF事件的情况下，暂停传输映射到所述辅载波的所有RLC实体的数据。
  17. 根据权利要求13至15中任一项所述的终端设备，其特征在于，所述确定单元具体用于：
    在所述辅载波发生所述RLF事件的情况下，暂停传输映射到所述辅载波的至少一个RLC实体中的数据，所述至少一个RLC实体中每个RLC实体中存在AMD PDU的传输次数达到最大重传次数。
  18. 根据权利要求13至17中任一项所述的终端设备，其特征在于，所述确定单元具体用于：
    在所述辅载波发生所述RLF事件的情况下，维持介质访问控制MAC实体的操作。
  19. 根据权利要求13至18中任一项所述的终端设备，其特征在于，所述发送单元具体用于：
    在所述辅载波发生所述RLF事件的情况下，通过所述主载波与所述网络设备复制传输所述辅载波承载的无线承载信令SRB。
  20. 根据权利要求13至19中任一项所述的终端设备，其特征在于，所述确定单元具体用于：
    在所述主载波对应的RLC实体中存在AMD PDU的传输次数达到最大传输次数的情况下，确定所述主载波发生RLF事件，并通过所述发送单元向所述网络设备发送RRC重建请求消息，所述RRC重建请求消息用于请求与所述网络设备进行RRC重建。
  21. 根据权利要求13至19中任一项所述的终端设备，其特征在于，所述主载波为主小区组MCG中的主载波，所述辅载波为所述MCG中的辅载波；或
    所述主载波为次小区组SCG中的主载波，所述辅载波为所述SCG中的辅载波。
  22. 根据权利要求21所述的终端设备，其特征在于，所述主载波为所述SCG中的主载波，所述辅载波为所述SCG中的辅载波，所述确定单元具体用于：
    在所述SCG中的主载波对应的RLC实体中存在AMD PDU的传输次数达到最大传输次数的情况下，确定所述SCG中的主载波发生RLF事件，并通过所述发送单元向所述网络设备发送第二RRC重配置信息，所述第二RRC重配置信息用于所述终端设备与所述网络设备进行RRC连接重配置。
  23. 根据权利要求22所述的终端设备，其特征在于，所述终端设备还包括：
    接收单元，用于接收所述网络设备根据所述第二RRC重配置信息发送的第二载波配置信息，所述第二载波配置信息用于指示第二载波；
    所述发送单元具体用于：
    通过所述第二载波代替发生所述RLF事件的所述SCG中的主载波向所述网络设备发送所述相同的PDCP层数据。
  24. 根据权利要求22或23所述的终端设备，其特征在于，所述发送单元具体用于：
    向所述网络设备发送第二RLF类型指示信息，所述第二RLF类型指示信息用于指示发生所述RLF事件的载波为所述SCG中的主载波。
PCT/CN2017/094160 2017-07-24 2017-07-24 处理无线链路失败的方法和终端设备 WO2019018989A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
EP17919441.0A EP3661316B1 (en) 2017-07-24 2017-07-24 Method for processing radio link failure, and terminal device
PCT/CN2017/094160 WO2019018989A1 (zh) 2017-07-24 2017-07-24 处理无线链路失败的方法和终端设备
CN201780090258.7A CN110612775B (zh) 2017-07-24 2017-07-24 处理无线链路失败的方法和终端设备
US16/621,674 US11102057B2 (en) 2017-07-24 2017-07-24 Terminal device and method for processing radio link failure to improve transmission efficiency
TW107125484A TW201909666A (zh) 2017-07-24 2018-07-24 處理無線鏈路失敗的方法和終端設備

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2017/094160 WO2019018989A1 (zh) 2017-07-24 2017-07-24 处理无线链路失败的方法和终端设备

Publications (1)

Publication Number Publication Date
WO2019018989A1 true WO2019018989A1 (zh) 2019-01-31

Family

ID=65039361

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/094160 WO2019018989A1 (zh) 2017-07-24 2017-07-24 处理无线链路失败的方法和终端设备

Country Status (5)

Country Link
US (1) US11102057B2 (zh)
EP (1) EP3661316B1 (zh)
CN (1) CN110612775B (zh)
TW (1) TW201909666A (zh)
WO (1) WO2019018989A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115336316A (zh) * 2020-01-31 2022-11-11 三星电子株式会社 用于在无线通信***中控制侧链路辅助载波的装置和方法
WO2023004714A1 (zh) * 2021-07-29 2023-02-02 Oppo广东移动通信有限公司 无线通信方法及设备

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3611954B1 (en) * 2017-07-27 2021-12-22 Shenzhen Heytap Technology Corp., Ltd. Data transmission method implemented in a termin al device having a first rlc entity and a second rlc entity and terminal device
EP3635900B1 (en) * 2017-08-16 2022-01-12 Samsung Electronics Co., Ltd. Method and apparatus for transmitting and receiving duplicate packets in next-generation mobile communication system
WO2019138087A1 (en) * 2018-01-11 2019-07-18 Telefonaktiebolaget Lm Ericsson (Publ) Radio link maintenance involving muliple uplink carriers
KR102598001B1 (ko) * 2018-06-18 2023-11-06 삼성전자 주식회사 이동 통신 시스템에서 효율적인 패킷 중복 전송을 위한 방법 및 장치
US11032189B2 (en) * 2018-09-28 2021-06-08 Lg Electronics Inc. Method for transmitting packet when radio link failure is detected in wireless communication system and apparatus therefor
CN116601989A (zh) * 2020-12-10 2023-08-15 华为技术有限公司 数据传输处理方法及相关装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103906152A (zh) * 2012-12-24 2014-07-02 北京三星通信技术研究有限公司 支持ue快速恢复的方法
US20160037579A1 (en) * 2013-04-05 2016-02-04 Pantech Co., Ltd. Method and apparatus for wireless link control in wireless communication system supporting dual connectivity
CN105393582A (zh) * 2013-07-17 2016-03-09 Lg电子株式会社 报告无线电链路控制重传失败的方法及其设备
WO2016061390A1 (en) * 2014-10-15 2016-04-21 Qualcomm Incorporated Early radio link failure (rlf) declaration

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2012138079A2 (ko) * 2011-04-03 2012-10-11 엘지전자 주식회사 신호 전송 여부 결정 방법
US20130010641A1 (en) * 2011-07-05 2013-01-10 Esmael Dinan Carrier Activation Employing RRC messages
US10368334B2 (en) * 2017-03-17 2019-07-30 Ofinno Technologies, Llc Radio access network paging area configuration
US10536878B2 (en) * 2017-03-24 2020-01-14 Mediatek Inc. User equipment and methods for PDCP duplication in 5G RAN
US10405231B2 (en) * 2017-04-24 2019-09-03 Motorola Mobility Llc Switching between packet duplication operating modes
US10757615B2 (en) * 2017-09-13 2020-08-25 Comcast Cable Communications, Llc Radio link failure information for PDCP duplication

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103906152A (zh) * 2012-12-24 2014-07-02 北京三星通信技术研究有限公司 支持ue快速恢复的方法
US20160037579A1 (en) * 2013-04-05 2016-02-04 Pantech Co., Ltd. Method and apparatus for wireless link control in wireless communication system supporting dual connectivity
CN105393582A (zh) * 2013-07-17 2016-03-09 Lg电子株式会社 报告无线电链路控制重传失败的方法及其设备
WO2016061390A1 (en) * 2014-10-15 2016-04-21 Qualcomm Incorporated Early radio link failure (rlf) declaration

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3661316A4 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115336316A (zh) * 2020-01-31 2022-11-11 三星电子株式会社 用于在无线通信***中控制侧链路辅助载波的装置和方法
WO2023004714A1 (zh) * 2021-07-29 2023-02-02 Oppo广东移动通信有限公司 无线通信方法及设备

Also Published As

Publication number Publication date
EP3661316B1 (en) 2021-09-08
CN110612775B (zh) 2024-03-15
EP3661316A4 (en) 2020-08-05
CN110612775A (zh) 2019-12-24
US11102057B2 (en) 2021-08-24
TW201909666A (zh) 2019-03-01
US20200127886A1 (en) 2020-04-23
EP3661316A1 (en) 2020-06-03

Similar Documents

Publication Publication Date Title
WO2019018989A1 (zh) 处理无线链路失败的方法和终端设备
TWI776866B (zh) 新無線電接取技術中的複製與無線電連結控制操作技術
CN104935414B (zh) 一种在双连接***中传输信息的方法和装置
WO2018202187A1 (zh) 一种切换的方法、终端设备及网络设备
US11082905B2 (en) Method for processing radio link failure, and terminal device and network device
US20190253895A1 (en) Control signaling processing method, device, and system
US11218256B2 (en) Data transmission method, terminal device and network device
WO2018127220A1 (zh) 一种数据转发方法及装置
WO2019095114A1 (zh) 处理无线链路失败的方法、终端设备和网络设备
WO2019014916A1 (zh) 处理数据的方法和设备
WO2021047374A1 (zh) 通信方法和装置
WO2019024120A1 (zh) 资源调度的方法、终端设备和网络设备
WO2022061661A1 (zh) 无线通信的方法、终端设备和网络设备
WO2019127292A1 (zh) 数据复制传输功能的控制方法和设备
WO2020155124A1 (zh) 复制数据的传输方法、终端设备及接入网设备
WO2019036930A1 (zh) 用于数据传输的方法、发送端设备和接收端设备
WO2021169732A1 (zh) 一种切换方法及通信装置
WO2019153209A1 (zh) 处理无线链路失败rlf的方法和终端设备
JP2021509779A (ja) データを再送信する方法及び機器
KR20200004384A (ko) 데이터 손상 여부를 결정하기 위한 방법 및 장치
WO2019153208A1 (zh) 处理无线链路失败rlf的方法和终端设备
AU2018312020A1 (en) Counting method and communications apparatus
WO2023123212A1 (zh) 通信方法及通信装置
WO2022204999A1 (zh) 存活时间的处理方法和终端设备
WO2023155763A1 (zh) 通信方法及通信装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17919441

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2017919441

Country of ref document: EP

Effective date: 20200224