WO2019057012A1 - 数据传输失败的处理方法及装置 - Google Patents

数据传输失败的处理方法及装置 Download PDF

Info

Publication number
WO2019057012A1
WO2019057012A1 PCT/CN2018/106035 CN2018106035W WO2019057012A1 WO 2019057012 A1 WO2019057012 A1 WO 2019057012A1 CN 2018106035 W CN2018106035 W CN 2018106035W WO 2019057012 A1 WO2019057012 A1 WO 2019057012A1
Authority
WO
WIPO (PCT)
Prior art keywords
target
scell
rlc entity
bearer
target event
Prior art date
Application number
PCT/CN2018/106035
Other languages
English (en)
French (fr)
Inventor
吴昱民
Original Assignee
维沃移动通信有限公司
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 维沃移动通信有限公司 filed Critical 维沃移动通信有限公司
Priority to US16/650,658 priority Critical patent/US11290939B2/en
Priority to EP18858284.5A priority patent/EP3691403A1/en
Publication of WO2019057012A1 publication Critical patent/WO2019057012A1/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/0659—Management of faults, events, alarms or notifications using network fault recovery by isolating or reconfiguring faulty entities
    • H04L41/0661—Management of faults, events, alarms or notifications using network fault recovery by isolating or reconfiguring faulty entities by reconfiguring faulty entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H04W36/30—Reselection being triggered by specific parameters by measured or perceived connection quality data
    • H04W36/305—Handover due to radio link failure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/08—Arrangements for detecting or preventing errors in the information received by repeating transmission, e.g. Verdan system
    • 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
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0016—Hand-off preparation specially adapted for end-to-end data sessions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access
    • 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
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H04W76/34—Selective release of ongoing 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
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0069—Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink

Definitions

  • the present application relates to the field of communications technologies, and in particular, to a processing method and apparatus for data transmission failure.
  • the 5G (5th-Generation, 5th generation) mobile communication system adopts a DC (Dual Connectivity) architecture, wherein the DC architecture includes two cell groups: MCG (Master Cell Group) and SCG (Secondary).
  • the cell group corresponds to the MN (Master Node) on the network side
  • the SCG corresponds to the SN (Signaling Node) on the network side.
  • the network side may configure a plurality of SRBs (Signaling Radio Bearers) for the terminal device, including: SRB1 and SRB2 configured on the MCG, and SRB3 configured on the SCG.
  • the 5G mobile communication system includes two bearers supporting the data replication function of the Packet Data Convergence Protocol (PDCP): Duplicate bearer replication bearer and Split bearer split bearer, wherein, as shown in FIG. 1, Duplicate bearer corresponds to A PDCP entity, a RLC (Radio Link Control) entity, and a MAC (Medium Access Control) entity in a cell group in the terminal device; as shown in FIG. 2, Split The bearer corresponds to one PDCP entity in the terminal device, two RLC entities (two RLC entities in different cell groups), and two MAC entities (two MAC entities in different cell groups).
  • the Duplicate bearer data from different RLC entities is transmitted through different cells, and the cell may be a SCell (Secondary Cell) or a PCell (Primary Cell).
  • the data to be sent of the RLC entity is sent only through the SCell, if at least one of the following occurs: the RLC entity reaches the maximum number of retransmissions, The SCell physical layer out of synchronization and the random access procedure of the SCell failing to send the data of the RLC entity are called SCell failure.
  • SCell failure The SCell physical layer out of synchronization and the random access procedure of the SCell failing to send the data of the RLC entity.
  • the purpose of the embodiments of the present application is to provide a processing method and apparatus for data transmission failure to ensure the working performance of the terminal device and the network device.
  • a method for processing data transmission failure is proposed, the method being performed by a terminal device, the method comprising:
  • a target radio link control RLC entity reaches a maximum number of retransmissions, a target secondary cell SCell physical layer out of synchronization, and a target SCell random access procedure If the target RLC entity is the RLC entity in the terminal device corresponding to the replication bearer, the data to be sent of the target RLC entity is sent by the SCell, and the target SCell is at least the data to be sent of the target RLC entity.
  • the target RLC entity reaches a maximum number of retransmissions
  • a target secondary cell SCell physical layer out of synchronization a target SCell random access procedure
  • a processing apparatus for data transmission failure comprising:
  • a first determining unit configured to determine that a target event occurs, where the target event includes at least one of: a target radio link control RLC entity reaches a maximum number of retransmissions, a target secondary cell SCell physical layer out of synchronization, and The random access procedure of the target SCell fails.
  • the target RLC entity is an RLC entity in the terminal device corresponding to the replication bearer.
  • the data to be sent of the target RLC entity is sent only through the SCell, and the target SCell is used to send the target RLC. At least one SCell of the entity to be sent data;
  • the processing unit includes at least one of the following subunits: a first processing subunit, a second processing subunit, and a third processing subunit, wherein the first processing subunit is configured to reset the target RLC entity, The second processing subunit is configured to process the target SCell, and the third processing subunit is configured to process the replication bearer.
  • an electronic device comprising:
  • a memory storing computer executable instructions that, when executed, cause the processor to perform the following operations:
  • a target radio link control RLC entity reaches a maximum number of retransmissions, a target secondary cell SCell physical layer out of synchronization, and a target SCell random access procedure If the target RLC entity is the RLC entity in the terminal device corresponding to the replication bearer, the data to be sent of the target RLC entity is sent by the SCell, and the target SCell is at least the data to be sent of the target RLC entity.
  • the target RLC entity reaches a maximum number of retransmissions
  • a target secondary cell SCell physical layer out of synchronization a target SCell random access procedure
  • a computer readable storage medium storing one or more programs that, when executed by an electronic device comprising a plurality of applications, cause The electronic device performs the following operations:
  • a target radio link control RLC entity reaches a maximum number of retransmissions, a target secondary cell SCell physical layer out of synchronization, and a target SCell random access procedure If the target RLC entity is the RLC entity in the terminal device corresponding to the replication bearer, the data to be sent of the target RLC entity is sent by the SCell, and the target SCell is at least the data to be sent of the target RLC entity.
  • the target RLC entity reaches a maximum number of retransmissions
  • a target secondary cell SCell physical layer out of synchronization a target SCell random access procedure
  • the embodiment of the present application can clarify that, when a target event occurs, that is, an SCell failure occurs, the terminal device uses the RLC entity that generates the target event, the SCell in which the target event occurs, and the replication bearer. The processing is done to ensure the performance of the terminal equipment and to avoid interference with other terminal equipment.
  • the terminal device may also generate information related to the target event to the network device, so that the network device can perform subsequent processing on the target event, thereby ensuring the working performance of the network device.
  • FIG. 1 is a schematic diagram of a replication bearer in a communication system of the present application.
  • FIG. 2 is a schematic diagram of a split bearer in a communication system of the present application.
  • FIG. 3 is a flowchart of a method for processing data transmission failure according to an embodiment of the present application.
  • FIG. 4 is a diagram showing an example of a processing method for data transmission failure according to an embodiment of the present application.
  • FIG. 5 is a flowchart of a method for processing data transmission failure according to another embodiment of the present application.
  • FIG. 6 is a flow diagram of a process for processing a data transmission failure according to an embodiment of the present application.
  • FIG. 7 is a flow diagram of a process for processing a data transmission failure according to another embodiment of the present application.
  • FIG. 8 is a flow diagram of a process for processing a data transmission failure according to another embodiment of the present application.
  • FIG. 9 is a schematic structural diagram of a processing apparatus for data transmission failure according to an embodiment of the present application.
  • FIG. 10 is a schematic structural diagram of an electronic 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 Wireless GPRS (General Packet Radio Service)
  • LTE Long Term Evolution
  • FDD Frequency Division Duplex
  • TDD Time Division Duplex
  • LTE Time Division Duplex Time Division Duplex
  • UMTS Universal Mobile Telecommunication System
  • WiMAX Worldwide Interoperability for Microwave Access
  • the terminal device may include, but is not limited to, a mobile station (Mobile Station, MS), a mobile terminal (Mobile Terminal), a mobile phone (Mobile Telephone), a user equipment (User Equipment, UE), and a mobile phone (handset).
  • a portable device, a vehicle, etc. the terminal device can communicate with one or more core networks via a Radio Access Network (RAN), for example, the terminal device can be a mobile phone (or Known as "cellular" telephones, computers with wireless communication capabilities, etc., the terminal devices can also be portable, pocket-sized, handheld, computer-integrated or in-vehicle mobile devices.
  • RAN Radio Access Network
  • the network device involved in the embodiment of the present application is a device deployed in a radio access network to provide a wireless communication function for a terminal device.
  • 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
  • FIG. 3 is a flowchart of a method for processing data transmission failure according to an embodiment of the present application. As shown in FIG. 3, the method is performed by a terminal device, and the method may include the following steps:
  • determining that a target event occurs wherein the target event includes at least one of the following events: the target RLC entity reaches the maximum number of retransmissions, the target SCell physical layer is out of synchronization, and the target SCell random access procedure fails.
  • the target RLC entity is an RLC entity in the terminal device corresponding to the replication bearer, and the data to be sent of the target RLC entity is sent only by the SCell, and the target SCell is at least one SCell for transmitting the data of the target RLC entity to be sent.
  • the receiving end feeds back to the sending end whether the data is received by the RLC STATU PDU. If the receiving end does not receive the data packet, the transmitting end performs data packet retransmission, and the network side The maximum number of retransmissions of the RLC layer packet is configured.
  • the Duplicate Bear includes: a primary cell group replication bearer and a secondary cell group replication bearer, where the primary cell group replication bearer is a Duplicate Bear established between the terminal device and the network device in the primary cell group, and the secondary cell group replication bearer A Duplicate Bearer established for a network device in a terminal device and a secondary cell group.
  • the target RLC entity may be any one or more RLC entities in the terminal device corresponding to the replication bearer, and the data to be sent of the target RLC entity may be sent only through the SCell in the primary cell group, or may only be supplemented by the SCell in the primary cell group.
  • the SCell is sent in the cell group SCG, where the primary cell group includes: a PCell and at least one SCell, and the secondary cell group includes: a PCell and at least one SCell.
  • the target event can again become a SCell failure.
  • the target RLC entity reaches the maximum number of retransmissions, it is determined that the target event occurs.
  • the target SCell physical layer is out of step, it is determined that the target event occurs.
  • the target SCell when the random access procedure of the target SCell fails, it is determined that the target event occurs.
  • the target RLC entity reaches the maximum number of retransmissions and the random access procedure of the target SCell fails, it is determined that the target event occurs.
  • the target RLC entity reaches the maximum number of retransmissions and the target SCell physical layer is out of step, it is determined that the target event occurs.
  • the target SCell physical layer is out of step, it is determined that the target event occurs.
  • the target RLC entity reaches the maximum number of retransmissions and the target SCell physical layer is out of synchronization, and the random access procedure of the target SCell fails, it is determined that the target event occurs.
  • At least one of the following processing operations is performed: resetting the target RLC entity, processing the target SCell, and processing the duplicate bearer.
  • the processing the target SCell may include at least one processing operation described below:
  • the downlink signal reception of the target SCell is stopped.
  • the processing the replication bearer may include at least one processing operation as follows:
  • the replication bearer is suspended, wherein when the replication bearer is suspended, the replication bearer does not send and receive data;
  • the default sending path of the replication bearer is determined to be the sending path corresponding to the target RLC entity.
  • the following steps may be further included:
  • the RLC entity 1 in the primary cell group replication bearer is the target RLC entity.
  • the replication bearer corresponding to the target RLC entity is the primary cell group replication bearer
  • the PDCP entity corresponding to the primary cell group replication bearer is the PDCP entity 1, the primary group.
  • the MAC entity corresponding to the replication bearer is MAC entity 1
  • the target SCell is the SCell in the primary cell group.
  • the RLC entity 1 is reset when a target event occurs.
  • the RLC entity 1 in the primary cell group replication bearer reaches the maximum number of retransmissions, and the RLC entity 1 is reset.
  • the target SCell when a target event occurs, all RLC entities in the terminal device corresponding to the target SCell are reset, the target SCell is deactivated, the uplink signal transmission of the target SCell is stopped, and the downlink signal reception of the target SCell is stopped.
  • the data replication function of the PDCP entity 1 is deactivated, and the default transmission path of the primary cell group replication bearer is changed to the transmission path corresponding to the RLC entity 2, and the primary cell group replication bearer is suspended and reconstructed.
  • a target event when a target event occurs, it is determined that at least one of the following events occurs in the RLC entity 2: the maximum number of retransmissions of the RLC entity, the SCell physical layer out of synchronization for transmitting the data of the RLC entity, and the use of The random access procedure of the SCell that sends the data of the RLC entity to be sent fails, and then suspends the primary cell group replication bearer.
  • a target event when a target event occurs, it is determined that at least one of the following events occurs in the RLC entity 2: the maximum number of retransmissions of the RLC entity, the SCell physical layer out of synchronization for transmitting the data of the RLC entity, and the use of The random access procedure of the SCell for transmitting the data of the RLC entity fails to re-establish the PDCP entity 1.
  • a target event when a target event occurs, it is determined that at least one of the following events occurs in the RLC entity 2: the maximum number of retransmissions of the RLC entity, the SCell physical layer out of synchronization for transmitting the data of the RLC entity, and the use of The random access procedure of the SCell that sends the data of the RLC entity to be transmitted fails, and then the MAC entity 1 is reset.
  • this embodiment can clarify the processing performed by the terminal device on the target RLC entity, the target SCell, and the replication bearer when the target event occurs (ie, the SCell fails), thereby ensuring the working performance of the terminal device ( For example, to save power) and to avoid interference with other terminal devices.
  • FIG. 5 is a flowchart of a method for processing data transmission failure according to an embodiment of the present application. As shown in FIG. 5, the method is performed by a terminal device. To ensure the performance of the network device, the method may include the following steps:
  • the protocol or the configuration information may be used to stipulate whether the related information of the target event is sent to the network device when the target event occurs.
  • the foregoing S502 may include:
  • the protocol is stored in the terminal device before the terminal device leaves the factory.
  • the foregoing S502 may include:
  • the network device may include: the primary node MN corresponding to the primary cell group MCG, and/or the secondary node corresponding to the secondary cell group SCG SN.
  • the terminal device receives configuration information sent by the primary node corresponding to the primary cell group, and determines, according to the configuration information sent by the primary node, whether to send related information of the target event to the primary node when the target event occurs.
  • the terminal device receives configuration information sent by the primary node corresponding to the primary cell group, and determines, according to the configuration information sent by the primary node, whether to send information about the target event to the secondary node corresponding to the secondary cell group when the target event occurs.
  • the terminal device receives configuration information sent by the secondary node corresponding to the secondary cell group, and determines, according to the configuration information sent by the secondary node, whether to send related information of the target event to the secondary node when the target event occurs.
  • the terminal device receives configuration information sent by the secondary node corresponding to the secondary cell group, and determines, according to the configuration information sent by the secondary node, whether to send information about the target event to the primary node corresponding to the primary cell group when the target event occurs.
  • the related information of the target event includes any combination of one or more of the following:
  • the identifier of the cell group to which the target SCell belongs
  • the identifier of the logical channel group to which the logical channel corresponding to the target RLC entity belongs
  • one serving cell may include multiple cell groups, and one cell group may include multiple cells;
  • the measurement result of the serving cell of the cell group to which the target SCell belongs is the measurement result of the serving cell of the cell group to which the target SCell belongs.
  • the measurement result of the cell corresponding to the target RLC entity may include: a reference signal received power RSRP and/or a reference signal received quality RSRQ of the cell corresponding to the target RLC entity.
  • the measurement result of the beam of the cell corresponding to the target RLC entity may include: RSRP and/or RSRQ of the beam of the cell corresponding to the target RLC entity.
  • the measurement result of the serving cell may include: RSRP and/or RSRQ of the serving cell.
  • the measurement result of the beam of the serving cell may include: RSRP and/or RSRQ of the beam of the serving cell.
  • the measurement result of the cell serving the frequency point may include: RSRP and/or RSRQ of the cell serving the frequency point.
  • the measurement result of the beam of the cell serving the frequency point may include: RSRP and/or RSRQ of the beam of the cell serving the frequency point.
  • the measurement result of the serving cell of the cell group to which the target SCell belongs may include: RSRP and/or RSRQ of the serving cell of the cell group to which the target SCell belongs.
  • the measurement result of the beam of the serving cell of the cell group to which the target SCell belongs may include: RSRP and/or RSRQ of the beam of the serving cell of the cell group to which the target SCell belongs.
  • the measurement result of the cell of the service frequency point to which the target SCell belongs may include: RSRP and/or RSRQ of the cell of the service frequency to which the target SCell belongs.
  • the measurement result of the beam of the cell of the service frequency point to which the target SCell belongs may include: RSRP and/or RSRQ of the beam of the cell of the service frequency point to which the target SCell belongs.
  • the measurement result of the cell of the non-serving frequency point may include: RSRP and/or RSRQ of the cell of the non-serving frequency point.
  • the measurement result of the beam of the cell of the non-serving frequency point may include: RSRP and/or RSRQ of the beam of the cell of the non-serving frequency point.
  • determining that a target event occurs wherein the target event includes at least one of the following: a target RLC entity reaches a maximum number of retransmissions, a target SCell physical layer is out of synchronization, and a random access procedure of the target SCell fails.
  • the target RLC entity is an RLC entity in the terminal device corresponding to the replication bearer, and the data to be sent of the target RLC entity is sent only by the SCell, and the target SCell is at least one SCell for transmitting the data of the target RLC entity to be sent.
  • At least one of the following processing operations is performed: resetting the target RLC entity, processing the target SCell, and processing the duplicate bearer.
  • S504 and S506 in the embodiment of the present application is similar to the content of S302 and S304 in the embodiment shown in FIG. 3, and details are not described herein again. For details, refer to the contents of S302 and S304 in the embodiment shown in FIG.
  • this embodiment can clarify the processing performed by the terminal device on the target RLC entity, the target SCell, and the replication bearer when the target event occurs (ie, the SCell fails), thereby ensuring the working performance of the terminal device and avoiding Causes interference to other terminal devices.
  • the configuration information or protocol sent by the network device may be used to specify whether the terminal device sends the information about the target event to the network device when the target event occurs, so that the terminal device may also be related to the target event when the target event occurs. The information is generated to the network device, so that the network device can perform subsequent processing on the target event, thereby ensuring the working performance of the network device.
  • the execution sequence of the step “determining whether to send relevant information of the target event to the network device when the target event occurs” may be performed in addition to the execution order in the embodiment shown in FIG. 5 Execution after the step of the event may also be performed after the step of performing at least one of the following processing operations: resetting the target RLC entity, processing the target SCell, and processing the duplicate bearer This embodiment of the present application does not limit this.
  • the interaction process between the terminal device and the primary node corresponding to the primary cell group (which may also be referred to as a primary base station) includes the following steps:
  • the terminal device may determine, according to the protocol, whether to send the related information of the target event to the primary node when the target event occurs; or, by receiving the configuration information sent by the primary node in the primary cell group, Whether the information about the target event is sent to the primary node when the target event occurs.
  • the primary node sends configuration information through the RRC Connection Reconfiguration process.
  • At least one of the following processing operations is performed: resetting the target RLC entity, processing the target SCell, and processing the duplicate bearer.
  • the terminal device may send the information about the target event to the primary node corresponding to the primary cell group by using the signaling radio bearer SRB1 or SRB2.
  • the terminal device may send the information related to the target event to the primary node corresponding to the primary cell group by using the signaling radio bearer SRB1.
  • the terminal device may send the information about the target event to the primary node corresponding to the primary cell group by signaling the radio bearer SRB2.
  • the interaction process between the terminal device, the primary node corresponding to the primary cell group, and the secondary node corresponding to the secondary cell group includes the following steps:
  • the terminal device may determine, according to the protocol, whether to send the related information of the target event to the secondary node when the target event occurs; or, by receiving the configuration information sent by the primary node in the primary cell group, Whether the information about the target event is sent to the secondary node when the target event occurs.
  • the primary node sends configuration information through the RRC Connection Reconfiguration process; or, by receiving configuration information sent by the secondary node in the secondary cell group, Whether the information about the target event is sent to the secondary node when the target event occurs.
  • the secondary node sends configuration information through the RRC Connection Reconfiguration process.
  • At least one of the following processing operations is performed: resetting the target RLC entity, processing the target SCell, and processing the duplicate bearer.
  • the terminal device when determining that a target event occurs, may directly send information about the target event to the secondary node corresponding to the secondary cell group by using the signaling radio bearer SRB3.
  • the interaction process of the terminal device, the primary node corresponding to the primary cell group, and the secondary node corresponding to the secondary cell group includes the following Step, wherein the terminal device performs S802 to S808, and the master node executes S810;
  • the terminal device may determine, according to the protocol, whether to send the related information of the target event to the secondary node when the target event occurs; or, by receiving the configuration information sent by the primary node in the primary cell group, Whether the information about the target event is sent to the secondary node when the target event occurs.
  • the primary node sends configuration information through the RRC Connection Reconfiguration process; or, by receiving configuration information sent by the secondary node in the secondary cell group, Whether the information about the target event is sent to the secondary node when the target event occurs.
  • the secondary node sends configuration information through the RRC Connection Reconfiguration process.
  • At least one of the following processing operations is performed: resetting the target RLC entity, processing the target SCell, and processing the duplicate bearer.
  • the terminal device when determining that a target event occurs, may send information about the target event to the primary node corresponding to the primary cell group by using the signaling radio bearer SRB1 or SRB2, and then the primary node may obtain information about the target event. Forward to the secondary node.
  • the processing procedure of the target RLC entity, the target SCell, and the replica bearer in the embodiment shown in FIG. 6 to FIG. 8 is similar to the processing procedure in the embodiment shown in FIG. 3, and the embodiments shown in FIG. 6 to FIG.
  • the content of the related information of the target event is similar to the content of the related information of the target event in the embodiment shown in FIG. 5 , and details are not described herein again. For details, refer to the corresponding content in the embodiment shown in FIG. 3 and FIG. 5 .
  • FIG. 9 is a schematic structural diagram of a processing device for data transmission failure according to an embodiment of the present invention.
  • the processing device 900 for data transmission failure may include: a first determining unit 910 and a processing unit 920, where
  • the first determining unit 910 is configured to determine that a target event occurs, where the target event includes at least one of the following events: the target radio link control RLC entity reaches a maximum number of retransmissions, and the target secondary cell SCell physical layer is out of synchronization
  • the random access procedure with the target SCell fails.
  • the target RLC entity is the RLC entity in the terminal device corresponding to the replication bearer.
  • the data to be sent of the target RLC entity is sent only through the SCell, and the target SCell is used to send the target. At least one SCell of the data to be transmitted of the RLC entity;
  • the processing unit 920 includes at least one of the following subunits: a first processing subunit, a second processing subunit, and a third processing subunit, where the first processing subunit is configured to reset the target RLC entity
  • the second processing subunit is configured to process the target SCell
  • the third processing subunit is configured to process the replication bearer.
  • this embodiment can clarify the processing performed by the terminal device on the target RLC entity, the target SCell, and the replication bearer when the target event occurs (ie, the SCell fails), thereby ensuring the working performance of the terminal device and avoiding the pair.
  • Other terminal equipment causes interference.
  • the processing device 900 that fails the data transmission may further include:
  • a second determining unit configured to determine whether to send related information of the target event to the network device when the target event occurs.
  • the second processing sub-unit is specifically configured to perform at least one processing operation described below:
  • the downlink signal reception of the target SCell is stopped.
  • the third processing sub-unit is specifically configured to perform at least one processing operation described below:
  • the third processing subunit is further configured to:
  • Determining, by default, the default sending path of the replication bearer is a sending path corresponding to the target RLC entity.
  • the third processing subunit is further configured to:
  • the RLC entity Before performing the operation of suspending the replication bearer, determining that all the RLC entities corresponding to the replication bearer generate at least one of the following events: the RLC entity reaches the maximum number of retransmissions, and is used to send the RLC entity.
  • the SCell physical layer out of synchronization of the data to be transmitted and the random access procedure of the SCell for transmitting the data to be transmitted by the RLC entity fail.
  • the third processing subunit is further configured to:
  • the RLC entity Before performing the operation of reestablishing the PDCP entity corresponding to the replication bearer, determining that all the RLC entities corresponding to the replication bearer have at least one of the following events: the RLC entity reaches the maximum number of retransmissions, and is used to send the RLC.
  • the SCell physical layer out of synchronization of the entity to be transmitted data and the random access procedure of the SCell for transmitting the data to be transmitted by the RLC entity fail.
  • the third processing subunit is further configured to:
  • the SCell physical layer out of synchronization for transmitting the data of the RLC entity and the random access procedure of the SCell for transmitting the data to be transmitted by the RLC entity fail.
  • the second determining unit includes:
  • a first determining subunit configured to determine, according to a protocol preconfigured in the terminal device, whether to send related information of the target event to the network device when the target event occurs.
  • the second determining unit includes:
  • a second determining subunit configured to receive configuration information sent by the network device, where the configuration information is used to indicate whether the related information of the target event is sent to the network device when the target event occurs;
  • the network device includes: a primary node MN corresponding to the primary cell group MCG, and/or a secondary node SN corresponding to the secondary cell group SCG.
  • the target SCell is an SCell in the MCG
  • the device also includes:
  • the first sending unit is configured to send the related information of the target event to the MN corresponding to the MCG by signaling the radio bearer SRB1 or SRB2 when the target event occurs.
  • the target SCell is an SCell in the SCG
  • the device also includes:
  • a second sending unit configured to send, by using the signaling radio bearer SRB3, information related to the target event to the SN corresponding to the SCG, when the target event occurs.
  • the target SCell is an SCell in the SCG
  • the device also includes:
  • a third sending unit configured to send, by using a signaling radio bearer SRB1 or SRB2, information related to the target event to the MN corresponding to the MCG, where the MN is configured to use the target event
  • the related information is forwarded to the SN corresponding to the SCG.
  • the related information of the target event includes any combination of one or more of the following:
  • the identifier of the cell group to which the target SCell belongs
  • FIG. 10 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
  • the electronic device 1000 shown in FIG. 10 includes at least one processor 1001, a memory 1002, at least one network interface 1004, and a user interface 1003.
  • the various components in electronic device 1000 are coupled together by a bus system 1005.
  • the bus system 1005 is used to implement connection communication between these components.
  • the bus system 1005 includes a power bus, a control bus, and a status signal bus in addition to the data bus.
  • various buses are labeled as bus system 1005 in FIG.
  • the user interface 1003 may include a display, a keyboard, or a pointing device (eg, a mouse, a trackball, a touchpad, or a touch screen, etc.).
  • a pointing device eg, a mouse, a trackball, a touchpad, or a touch screen, etc.
  • the memory 1002 in the embodiment of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory can be a read-only memory (ROM), a programmable read only memory (Programmable ROM (PROM), an erasable programmable read only memory (ErasablePROM, EPROM), and an electrically erasable Program an read only memory (Electrically EPROM, EEPROM) or flash memory.
  • the volatile memory can be a Random Access Memory (RAM) that acts as an external cache.
  • RAM static random access memory
  • DRAM dynamic random access memory
  • SDRAM synchronous dynamic random access memory
  • DDRSDRAM Double Data Rate Synchronous Dynamic Random Access Memory
  • ESDRAM Enhanced Synchronous Dynamic Random Access Memory
  • SDRAM Synchronous Connection Dynamic Random Access Memory
  • DRAM Direct Memory Bus Random Memory
  • Memory 1002 of the systems and methods described in this application embodiment is intended to comprise, without being limited to, these and any other suitable types of memory.
  • the memory 1002 stores elements, executable modules or data structures, or a subset thereof, or their extended set: an operating system 10021 and an application 10022.
  • the operating system 10021 includes various system programs, such as a framework layer, a core library layer, a driver layer, and the like, for implementing various basic services and processing hardware-based tasks.
  • the application 10022 includes various applications, such as a media player (Media Player), a browser (Browser), etc., for implementing various application services.
  • a program implementing the method of the embodiment of the present application may be included in the application 10022.
  • the terminal device 1000 further includes: a computer program stored on the memory 1002 and executable on the processor 1001.
  • a computer program stored on the memory 1002 and executable on the processor 1001.
  • a target radio link control RLC entity reaches a maximum number of retransmissions, a target secondary cell SCell physical layer out of synchronization, and a target SCell random access procedure If the target RLC entity is the RLC entity in the terminal device corresponding to the replication bearer, the data to be sent of the target RLC entity is sent by the SCell, and the target SCell is at least the data to be sent of the target RLC entity.
  • the target RLC entity reaches a maximum number of retransmissions
  • a target secondary cell SCell physical layer out of synchronization a target SCell random access procedure
  • the method disclosed in the foregoing embodiment of the present application may be applied to the processor 1001 or implemented by the processor 1001.
  • the processor 1001 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the foregoing method may be completed by an integrated logic circuit of hardware in the processor 1001 or an instruction in a form of software.
  • the processor 1001 may be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, and a discrete gate. Or transistor logic devices, discrete hardware components.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA Field Programmable Gate Array
  • 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 modules can be located in a conventional computer readable storage medium of the art, such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the computer readable storage medium is located in the memory 1002, and the processor 1001 reads the information in the memory 1002 and performs the steps of the above method in combination with its hardware.
  • the computer readable storage medium stores a computer program, and when the computer program is executed by the processor 1001, each step of the embodiment of the processing method that fails the data transmission described above is implemented.
  • the embodiments described in the embodiments of the present application can be implemented by hardware, software, firmware, middleware, microcode, or a combination thereof.
  • the processing unit can be implemented in one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDevices, DSPDs), Programmable Logic Devices (Programmable Logic Devices, PLDs). ), Field-Programmable Gate Array (FPGA), general purpose processor, controller, microcontroller, microprocessor, other electronic units for performing the functions described herein, or a combination thereof.
  • ASICs Application Specific Integrated Circuits
  • DSPs Digital Signal Processors
  • DSPDevices Digital Signal Processing Devices
  • PLDs Programmable Logic Devices
  • FPGA Field-Programmable Gate Array
  • general purpose processor controller, microcontroller, microprocessor, other electronic units for performing the functions described herein, or a combination thereof.
  • the technology described in the embodiments of the present application can be implemented by a module (for example, a process, a function, and the like) that performs the functions described in the embodiments of the present application.
  • the software code can be stored in memory and executed by the processor.
  • the memory can be implemented in the processor or external to the processor.
  • the method further includes:
  • the processing the target SCell includes at least one processing operation as follows:
  • the downlink signal reception of the target SCell is stopped.
  • the processing the copy bearer includes at least one processing operation as follows:
  • the method before the step of changing the default sending path of the replication bearer to a sending path corresponding to another RLC entity, the method further includes:
  • Determining, by default, the default sending path of the replication bearer is a sending path corresponding to the target RLC entity.
  • the method before the step of suspending the replication bearer, the method further includes:
  • the RLC entity reaches the maximum number of retransmissions, the SCell physical layer out of synchronization for transmitting the RLC entity, and the RLC entity used to send the RLC entity
  • the random access procedure of the SCell of the data to be transmitted fails.
  • the method before the step of reestablishing the PDCP entity corresponding to the replication bearer, the method further includes:
  • the RLC entity reaches the maximum number of retransmissions, the SCell physical layer out of synchronization for transmitting the RLC entity, and the RLC entity used to send the RLC entity
  • the random access procedure of the SCell of the data to be transmitted fails.
  • the method before the step of resetting the media access control MAC entity corresponding to the replication bearer, the method further includes:
  • the RLC entity reaches the maximum number of retransmissions, the SCell physical layer out of synchronization for transmitting the RLC entity, and the RLC entity used to send the RLC entity
  • the random access procedure of the SCell of the data to be transmitted fails.
  • the determining whether to send the related information of the target event to the network device when the target event occurs includes:
  • the determining whether to send the related information of the target event to the network device when the target event occurs includes:
  • the network device includes: a primary node MN corresponding to the primary cell group MCG, and/or a secondary node SN corresponding to the secondary cell group SCG.
  • the target SCell is an SCell in the MCG
  • the method further includes:
  • the information about the target event is sent to the MN corresponding to the MCG by signaling the radio bearer SRB1 or SRB2.
  • the target SCell is an SCell in the SCG
  • the method further includes:
  • the information related to the target event is sent to the SN corresponding to the SCG by using the signaling radio bearer SRB3.
  • the target SCell is an SCell in the SCG
  • the method further includes:
  • the information related to the target event is sent to the MN corresponding to the MCG by using the signaling radio bearer SRB1 or SRB2, where the MN is configured to forward related information of the target event to the SCG.
  • the signaling radio bearer SRB1 or SRB2 where the MN is configured to forward related information of the target event to the SCG.
  • the information about the target event includes any combination of one or more of the following:
  • the identifier of the cell group to which the target SCell belongs
  • the terminal device 1000 can implement various processes implemented by the terminal device in the foregoing embodiment. To avoid repetition, details are not described herein again.
  • the embodiment of the present application further provides a computer readable storage medium storing one or more programs, the one or more programs including instructions, when the portable electronic device is included in a plurality of applications When executed, the portable electronic device can be configured to perform the method of the embodiment shown in FIG. 1 and specifically for performing the following operations:
  • a target radio link control RLC entity reaches a maximum number of retransmissions, a target secondary cell SCell physical layer out of synchronization, and a target SCell random access procedure If the target RLC entity is the RLC entity in the terminal device corresponding to the replication bearer, the data to be sent of the target RLC entity is sent by the SCell, and the target SCell is at least the data to be sent of the target RLC entity.
  • the target RLC entity reaches a maximum number of retransmissions
  • a target secondary cell SCell physical layer out of synchronization a target SCell random access procedure
  • the system, device, module or unit illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product having a certain function.
  • a typical implementation device is a computer.
  • the computer can be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or A combination of any of these devices.
  • Computer readable media includes both permanent and non-persistent, removable and non-removable media.
  • Information storage can be implemented by any method or technology.
  • the information can be computer readable instructions, data structures, modules of programs, or other data.
  • Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read only memory. (ROM), electrically erasable programmable read only memory (EEPROM), flash memory or other memory technology, compact disk read only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, Magnetic tape cartridges, magnetic tape storage or other magnetic storage devices or any other non-transportable media can be used to store information that can be accessed by a computing device.
  • computer readable media does not include temporary storage of computer readable media, such as modulated data signals and carrier waves.

Landscapes

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

Abstract

本申请实施例公开了一种数据传输失败的处理方法及装置，该方法包括：确定发生目标事件，该目标事件包括下述事件中的至少一种：RLC实体达到最大重传次数、目标SCell物理层失步和目标SCell的随机接入过程失败，该目标RLC实体为复制承载对应的终端设备中的RLC实体，该目标RLC实体的待发送数据只通过SCell发送，该目标SCell为用于发送目标RLC实体的待发送数据的至少一个SCell；执行下述至少一种处理操作：重置目标RLC实体、对目标SCell进行处理以及对复制承载进行处理。本技术方案可以明确在发生目标事件时，终端设备所做出的具体处理，从而确保终端设备的工作性能以及避免对其他终端设备造成干扰。

Description

数据传输失败的处理方法及装置 技术领域
本申请涉及通信技术领域，尤其涉及一种数据传输失败的处理方法及装置。
背景技术
5G(5th-Generation，第五代)移动通信系统采用DC(Dual Connectivity，双连接)架构，其中，该DC架构中包括两个小区组：MCG(Master Cell Group，主小区组)和SCG(Secondary Cell Group，辅小区组)，该MCG对应于网络侧的MN(Master Node，主节点)，该SCG对应于网络侧的SN(Signaling Node，辅节点)。网络侧可以为终端设备配置多个SRB(Signaling Radio Bearer，信令无线承载)，包括：配置在MCG上的SRB1和SRB2，以及配置在SCG上的SRB3。
目前，5G移动通信系统中包括两种支持PDCP(Packet Data Convergence Protocol，包数据汇聚协议)数据复制功能的承载：Duplicate bearer复制承载和Split bearer分离承载，其中，如图1所述，Duplicate bearer对应终端设备中的在一个小区组中的一个PDCP实体、2个RLC(Radio Link Control，无线链路控制)实体和一个MAC(Medium Access Control，媒体接入控制)实体；如图2所示，Split bearer对应终端设备中的一个PDCP实体、2个RLC实体(2个RLC实体在不同的小区组)和2个MAC实体(2个MAC实体在不同的小区组)。对于Duplicate bearer，来自不同RLC实体的数据通过不同的小区进行发送，该小区可以为SCell(Secondary Cell，辅小区)或PCell(Primary Cell，主小区)。
当Duplicate bearer对应的终端设备中的某个RLC实体被配置为：该RLC实体的待发送数据只通过SCell发送时，如果发生以下情况中的至少一种：该RLC实体达到最大重传次数、用于发送该RLC实体的待发送数据的SCell物 理层失步和该SCell的随机接入过程失败，则称为SCell失败。然而，目前相关技术中并未讨论如果发生SCell失败，终端设备将进行何种操作，因此需要提出一种数据传输失败的处理方法，来阐述SCell失败情况下终端设备的操作，以确保终端设备和网络设备的工作性能。
发明内容
本申请实施例的目的是提供一种数据传输失败的处理方法及装置，以确保终端设备和网络设备的工作性能。
为解决上述技术问题，本申请实施例是这样实现的：
第一方面，提出了一种数据传输失败的处理方法，所述方法由终端设备执行，所述方法包括：
确定发生目标事件，其中，所述目标事件包括下述事件中的至少一种：目标无线链路控制RLC实体达到最大重传次数、目标辅小区SCell物理层失步和目标SCell的随机接入过程失败，目标RLC实体为复制承载对应的终端设备中的RLC实体，所述目标RLC实体的待发送数据只通过SCell发送，所述目标SCell为用于发送所述目标RLC实体的待发送数据的至少一个SCell；
执行下述至少一种处理操作：重置所述目标RLC实体、对所述目标SCell进行处理以及对所述复制承载进行处理。
第二方面，提出了一种数据传输失败的处理装置，所述装置包括：
第一确定单元，用于确定发生目标事件，其中，所述目标事件包括下述事件中的至少一种：目标无线链路控制RLC实体达到最大重传次数、目标辅小区SCell物理层失步和目标SCell的随机接入过程失败，目标RLC实体为复制承载对应的终端设备中的RLC实体，所述目标RLC实体的待发送数据只通过SCell发送，所述目标SCell为用于发送所述目标RLC实体的待发送数据的至少一个SCell；
处理单元，包括下述子单元中的至少一个：第一处理子单元、第二处理子 单元和第三处理子单元，其中，所述第一处理子单元用于重置所述目标RLC实体，所述第二处理子单元用于对所述目标SCell进行处理，第三处理子单元用于对所述复制承载进行处理。
第三方面，提出了一种电子设备，该电子设备包括：
处理器；以及
存储计算机可执行指令的存储器，所述可执行指令在被执行时使所述处理器执行以下操作：
确定发生目标事件，其中，所述目标事件包括下述事件中的至少一种：目标无线链路控制RLC实体达到最大重传次数、目标辅小区SCell物理层失步和目标SCell的随机接入过程失败，目标RLC实体为复制承载对应的终端设备中的RLC实体，所述目标RLC实体的待发送数据只通过SCell发送，所述目标SCell为用于发送所述目标RLC实体的待发送数据的至少一个SCell；
执行下述至少一种处理操作：重置所述目标RLC实体、对所述目标SCell进行处理以及对所述复制承载进行处理。
第四方面，提出了一种计算机可读存储介质，所述计算机可读存储介质存储一个或多个程序，所述一个或多个程序当被包括多个应用程序的电子设备执行时，使得所述电子设备执行以下操作：
确定发生目标事件，其中，所述目标事件包括下述事件中的至少一种：目标无线链路控制RLC实体达到最大重传次数、目标辅小区SCell物理层失步和目标SCell的随机接入过程失败，目标RLC实体为复制承载对应的终端设备中的RLC实体，所述目标RLC实体的待发送数据只通过SCell发送，所述目标SCell为用于发送所述目标RLC实体的待发送数据的至少一个SCell；
执行下述至少一种处理操作：重置所述目标RLC实体、对所述目标SCell进行处理以及对所述复制承载进行处理。
由以上本申请实施例提供的技术方案可见，本申请实施例可以明确在发生目标事件(即发生SCell失败)时，终端设备对发生目标事件的RLC实体、发 生目标事件的SCell和复制承载中所做出的处理，从而确保终端设备的工作性能以及避免对其他终端设备造成干扰。此外，在发生目标事件时，终端设备还可以将与该目标事件相关的信息发生给网络设备，以便网络设备可以对该目标事件进行后续的处理，从而保证网络设备的工作性能。
附图说明
为了更清楚地说明本申请实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请中记载的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图。
图1是本申请的通信系统中的复制承载的示意图。
图2是本申请的通信系统中的分离承载的示意图。
图3是本申请一实施例的数据传输失败的处理方法的流程图。
图4是本申请一实施例的数据传输失败的处理方法的实例图。
图5是本申请另一实施例的数据传输失败的处理方法的流程图。
图6是本申请一实施例的数据传输失败的处理方法的流程交互图。
图7是本申请另一实施例的数据传输失败的处理方法的流程交互图。
图8是本申请另一实施例的数据传输失败的处理方法的流程交互图。
图9是本申请一实施例的数据传输失败的处理装置的结构示意图。
图10是本申请的一个实施例电子设备的结构示意图。
具体实施方式
为了使本技术领域的人员更好地理解本申请中的技术方案，下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获 得的所有其他实施例，都应当属于本申请保护的范围。
应理解，本申请的技术方案可以应用于各种通信系统，例如：GSM(Global System of Mobile communication,全球移动通讯系统)，CDMA(Code Division Multiple Access，码分多址)系统，WCDMA(Wideband Code Division Multiple Access Wireless，宽带码分多址)，GPRS(General Packet Radio Service，通用分组无线业务)，LTE(Long Term Evolution，长期演进)、FDD(Frequency Division Duplex，LTE频分双工)系统、TDD(Time Division Duplex，LTE时分双工)、UMTS(Universal Mobile Telecommunication System，通用移动通信系统)或WiMAX(Worldwide Interoperability for Microwave Access，全球互联微波接入)通信系统、5G系统，或者说NR(New Radio，新无线)系统。
在本申请实施例中，终端设备可以包括但不限于移动台(Mobile Station，MS)、移动终端(Mobile Terminal)、移动电话(Mobile Telephone)、用户设备(User Equipment，UE)、手机(handset)及便携设备(portable equipment)、车辆(vehicle)等，该终端设备可以经无线接入网(Radio Access Network，RAN)与一个或多个核心网进行通信，例如，终端设备可以是移动电话(或称为“蜂窝”电话)、具有无线通信功能的计算机等，终端设备还可以是便携式、袖珍式、手持式、计算机内置的或者车载的移动装置。
本申请实施例所涉及到的网络设备是一种部署在无线接入网中用以为终端设备提供无线通信功能的装置。所述网络设备可以为基站，所述基站可以包括各种形式的宏基站，微基站，中继站，接入点等。在采用不同的无线接入技术的系统中，具有基站功能的设备的名称可能会有所不同。例如在LTE网络中，称为演进的节点B(Evolved NodeB，eNB或eNodeB)，在第三代(3rd Generation，3G)网络中，称为节点B(Node B)等等。
图3是本申请一实施例的数据传输失败的处理方法的流程图，如图3所示，该方法由终端设备执行，该方法可以包括以下步骤：
在S302中，确定发生目标事件，其中，该目标事件包括下述事件中的至 少一种：目标RLC实体达到最大重传次数、目标SCell物理层失步和目标SCell的随机接入过程失败，该目标RLC实体为复制承载对应的终端设备中的RLC实体，该目标RLC实体的待发送数据只通过SCell发送，该目标SCell为用于发送目标RLC实体的待发送数据的至少一个SCell。
为了便于理解，首先对本申请实施例中涉及到的一些概念进行介绍。
在RLC AM(Acknowledged Mode，确认模式)下，接收端会向发送端反馈数据是否接收到的RLC STATU PDU，如果接收端反馈没有接收到数据包，发送端会进行数据包重传，而网络侧会配置RLC层数据包的最大重传次数。
复制承载(Duplicate Bear)包括：主小区组复制承载和辅小区组复制承载，其中，主小区组复制承载为终端设备与主小区组中的网络设备之间建立的Duplicate Bear，辅小区组复制承载为终端设备与辅小区组中的网络设备建立的Duplicate Bearer。
本申请实施例中，目标RLC实体可以为复制承载对应的终端设备中的任意一个或多个RLC实体，目标RLC实体的待发送数据可以只通过主小区组中的SCell发送，也可以只通过辅小区组SCG中的SCell发送，其中，主小区组中包括：PCell和至少一个SCell，辅小区组中包括：PCell和至少一个SCell。目标事件又可以成为SCell失败。
作为一个例子，当目标RLC实体达到最大重传次数时，确定发生目标事件。
作为一个例子，当目标SCell物理层失步时，确定发生目标事件。
作为一个例子，当目标SCell的随机接入过程失败，确定发生目标事件。
作为一个例子，当目标RLC实体达到最大重传次数、且目标SCell的随机接入过程失败时，确定发生目标事件。
作为一个例子，当目标RLC实体达到最大重传次数、且目标SCell物理层失步时，确定发生目标事件。
作为一个例子，当目标SCell的随机接入过程失败、且目标SCell物理层 失步时，确定发生目标事件。
作为一个例子，当目标RLC实体达到最大重传次数、且目标SCell物理层失步、且目标SCell的随机接入过程失败时，确定发生目标事件。
在S304中，执行下述至少一种处理操作：重置目标RLC实体、对目标SCell进行处理以及对复制承载进行处理。
在一个实施方式中，上述对目标SCell进行处理，可以包括下述至少一种处理操作：
重置目标SCell所对应的所有RLC实体；
去激活目标SCell；
停止目标SCell的上行信号发送；以及
停止目标SCell的下行信号接收。
在一个实施方式中，上述对复制承载进行处理，可以包括下述至少一种处理操作：
去激活复制承载中PDCP实体的数据复制功能；
将复制承载的默认发送路径更改为其他RLC实体对应的发送路径；
将复制承载挂起，其中，复制承载挂起时，该复制承载不发送收和接收数据；
重建复制承载对应的PDCP实体；以及，
重置复制承载对应的媒体接入控制MAC实体。
在本实施方式中，在上述将复制承载的默认发送路径更改为其他RLC实体对应的发送路径的步骤之前，还可以包括以下步骤：
确定复制承载的默认发送路径为目标RLC实体对应的发送路径。
在本实施方式中，在上述将复制承载挂起的步骤之前，还可以包括以下步骤：
确定复制承载对应的所有RLC实体均发生下述事件中的至少一种：RLC实体达到最大重传次数、用于发送RLC实体的待发送数据的SCell物理层失步 和用于发送RLC实体的待发送数据的SCell的随机接入过程失败。
在本实施方式中，在上述重建复制承载对应的PDCP实体的步骤之前，还可以包括以下步骤：
确定复制承载对应的所有RLC实体均发生下述事件中的至少一种：RLC实体达到最大重传次数、用于发送RLC实体的待发送数据的SCell物理层失步和用于发送RLC实体的待发送数据的SCell的随机接入过程失败。
在本实施方式中，在上述重置复制承载对应的媒体接入控制MAC实体的步骤之前，还可以包括以下步骤：
确定复制承载对应的所有RLC实体均发生下述事件中的至少一种：RLC实体达到最大重传次数、用于发送RLC实体的待发送数据的SCell物理层失步和用于发送RLC实体的待发送数据的SCell的随机接入过程失败。
为了便于理解，结合图4所示的实例图，对上述S304中的处理操作进行介绍。
例如，主小区组复制承载中的RLC实体1为目标RLC实体，此时，目标RLC实体对应的复制承载为主小区组复制承载，主小区组复制承载对应的PDCP实体为PDCP实体1，主小组复制承载对应的MAC实体为MAC实体1，目标SCell为主小区组中的SCell。
作为一个例子，在发生目标事件时，重置RLC实体1。例如，主小区组复制承载中的RLC实体1达到最大重传次数，重置RLC实体1。
作为一个例子，在发生目标事件时，重置目标SCell所对应的终端设备中的所有RLC实体，去激活目标SCell，停止目标SCell的上行信号发送及停止目标SCell的下行信号接收。
作为一个例子，在发生目标事件时，去激活PDCP实体1的数据复制功能，将主小区组复制承载的默认发送路径更改为RLC实体2对应的发送路径，将主小区组复制承载挂起，重建PDCP实体1，以及重置MAC实体1。
作为一个例子，在发生目标事件时，先确定RLC实体2发生下述事件中 的至少一种：RLC实体达到最大重传次数、用于发送RLC实体的待发送数据的SCell物理层失步和用于发送RLC实体的待发送数据的SCell的随机接入过程失败，再将主小区组复制承载挂起。
作为一个例子，在发生目标事件时，先确定RLC实体2发生下述事件中的至少一种：RLC实体达到最大重传次数、用于发送RLC实体的待发送数据的SCell物理层失步和用于发送RLC实体的待发送数据的SCell的随机接入过程失败，再重建PDCP实体1。
作为一个例子，在发生目标事件时，先确定RLC实体2发生下述事件中的至少一种：RLC实体达到最大重传次数、用于发送RLC实体的待发送数据的SCell物理层失步和用于发送RLC实体的待发送数据的SCell的随机接入过程失败，再重置MAC实体1。
由上述实施例可见，该实施例可以明确在发生目标事件(即发生SCell失败)时，终端设备对目标RLC实体、目标SCell和复制承载中所做出的处理，从而确保终端设备的工作性能(例如节省电量)以及避免对其他终端设备造成干扰。
图5是本申请一实施例的数据传输失败的处理方法的流程图，如图5所示，该方法由终端设备执行，为了保证网络设备的工作性能，该方法可以包括以下步骤：
在S502中，确定在发生目标事件时是否向网络设备发送该目标事件的相关信息。
本申请实施例中，可以通过协议或配置信息，来约定在发生目标事件时是否向网络设备发送该目标事件的相关信息。
可选地，在一个实施方式中，上述S502可以包括：
根据预先配置在终端设备内的协议，确定在发生所述目标事件时是否向网络设备发送所述目标事件的相关信息。例如，在终端设备出厂前，将协议存储在该终端设备中。
可选地，在另一个实施方式中，上述S502可以包括：
接收网络设备发送的配置信息，其中，该配置信息用于指示在发生目标事件时是否向网络设备发送目标事件的相关信息；
根据配置信息，确定在发生目标事件时是否向网络设备发送目标事件的相关信息，其中，该网络设备可以包括：主小区组MCG对应的主节点MN、和/或辅小区组SCG对应的辅节点SN。
作为一个例子，终端设备接收主小区组对应的主节点发送的配置信息，根据主节点发送的配置信息，确定在发生目标事件时是否向该主节点发送目标事件的相关信息。
作为一个例子，终端设备接收主小区组对应的主节点发送的配置信息，根据主节点发送的配置信息，确定在发生目标事件时是否向辅小区组对应的辅节点发送目标事件的相关信息。
作为一个例子，终端设备接收辅小区组对应的辅节点发送的配置信息，根据辅节点发送的配置信息，确定在发生目标事件时是否向该辅节点发送目标事件的相关信息。
作为一个例子，终端设备接收辅小区组对应的辅节点发送的配置信息，根据辅节点发送的配置信息，确定在发生目标事件时是否向主小区组对应的主节点发送目标事件的相关信息。
本申请实施例中，目标事件的相关信息，包括以下一项或多项的任意组合：
目标SCell的标识；
目标SCell所属小区组的标识；
目标RLC实体对应的复制承载的标识；
目标RLC实体的标识；
目标RLC实体对应的逻辑信道的标识；
目标RLC实体对应的逻辑信道所属逻辑信道组的标识；
目标RLC实体对应的小区的测量结果；
目标RLC实体对应的小区的波束的测量结果；
服务小区的测量结果；
服务小区的波束的测量结果，其中，一个服务频点对应多个服务小区和多个非服务小区，一个服务小区可以包括多个小区组，一个小区组可以包括多个小区；
服务频点的小区的测量结果；
服务频点的小区的波束的测量结果；
目标SCell所属小区组的服务小区的测量结果；
目标SCell所属小区组的服务小区的波束的测量结果；
目标SCell所属服务频点的小区的测量结果；
目标SCell所属服务频点的小区的波束的测量结果；
非服务频点的小区的测量结果；以及，
非服务频点的小区的波束的测量结果。
作为一个例子，目标RLC实体对应的小区的测量结果，可以包括：目标RLC实体对应的小区的参考信号接收功率RSRP和/或参考信号接收质量RSRQ。
作为一个例子，目标RLC实体对应的小区的波束的测量结果，可以包括：目标RLC实体对应的小区的波束的RSRP和/或RSRQ。
作为一个例子，服务小区的测量结果，可以包括：服务小区的RSRP和/或RSRQ。
作为一个例子，服务小区的波束的测量结果，可以包括：服务小区的波束的RSRP和/或RSRQ。
作为一个例子，服务频点的小区的测量结果，可以包括：服务频点的小区的RSRP和/或RSRQ。
作为一个例子，服务频点的小区的波束的测量结果，可以包括：服务频点的小区的波束的RSRP和/或RSRQ。
作为一个例子，目标SCell所属小区组的服务小区的测量结果，可以包括： 目标SCell所属小区组的服务小区的RSRP和/或RSRQ。
作为一个例子，目标SCell所属小区组的服务小区的波束的测量结果，可以包括：目标SCell所属小区组的服务小区的波束的RSRP和/或RSRQ。
作为一个例子，目标SCell所属服务频点的小区的测量结果，可以包括：目标SCell所属服务频点的小区的RSRP和/或RSRQ。
作为一个例子，目标SCell所属服务频点的小区的波束的测量结果，可以包括：目标SCell所属服务频点的小区的波束的RSRP和/或RSRQ。
作为一个例子，非服务频点的小区的测量结果，可以包括：非服务频点的小区的RSRP和/或RSRQ。
作为一个例子，非服务频点的小区的波束的测量结果，可以包括：非服务频点的小区的波束的RSRP和/或RSRQ。
在S504中，确定发生目标事件，其中，该目标事件包括下述事件中的至少一种：目标RLC实体达到最大重传次数、目标SCell物理层失步和目标SCell的随机接入过程失败，该目标RLC实体为复制承载对应的终端设备中的RLC实体，该目标RLC实体的待发送数据只通过SCell发送，该目标SCell为用于发送目标RLC实体的待发送数据的至少一个SCell。
在S506中，执行下述至少一种处理操作：重置目标RLC实体、对目标SCell进行处理以及对复制承载进行处理。
本申请实施例中S504、S506的内容，与图3所示实施例中S302、S304的内容类似，在此不再赘述，详情请见图3所示实施例中S302、S304的内容。
由上述实施例可见，该实施例可以明确在发生目标事件(即发生SCell失败)时，终端设备对目标RLC实体、目标SCell和复制承载所做出的处理，从而确保终端设备的工作性能以及避免对其他终端设备造成干扰。此外，还可以通过网络设备发送的配置信息或协议约定终端设备在发生目标事件时是否向网络设备发送该目标事件的相关信息，以便在发生目标事件时，终端设备还可以将与该目标事件相关的信息发生给网络设备，使得网络设备可以对该目标事 件进行后续的处理，从而保证网络设备的工作性能。
需要说明的是，步骤“确定在发生目标事件时是否向网络设备发送该目标事件的相关信息”的执行顺序，除了图5所示实施例中的执行顺序之外，还可以在“确定发生目标事件”的步骤之后进行执行，也可以在“执行下述至少一种处理操作：重置所述目标RLC实体、对所述目标SCell进行处理以及对所述复制承载进行处理”的步骤之后进行执行，本申请实施例对此不作限定。
在本申请提供的另一个实施例中，当目标SCell为主小区组中的SCell时，如图6所示，终端设备与主小区组对应的主节点(也可称为主基站)的交互过程包括以下步骤：
在S602中，确定在发生目标事件时是否向网络设备发送该目标事件的相关信息。
本申请实施例中，终端设备可以根据协议，确定在发生目标事件时是否向主节点发送该目标事件的相关信息；或者，也可以通过接收主小区组中的主节点发送的配置信息，确定在发生目标事件时是否向该主节点发送该目标事件的相关信息，具体的，主节点通过RRC Connection Reconfiguration过程发送配置信息。
在S604中，确定发生目标事件。
在S606中，执行下述至少一种处理操作：重置目标RLC实体、对目标SCell进行处理以及对复制承载进行处理。
在S608中，向主节点发送目标事件的相关信息。
本申请实施例中，在确定发生目标事件时，终端设备可以通过信令无线承载SRB1或SRB2，向主小区组对应的主节点发送目标事件的相关信息。
作为一个例子，在确定发生目标事件时，终端设备可以通过信令无线承载SRB1，向主小区组对应的主节点发送目标事件的相关信息。
作为一个例子，在确定发生目标事件时，终端设备可以通过信令无线承载SRB2，向主小区组对应的主节点发送目标事件的相关信息。
在本申请提供的另一个实施例中，当目标SCell为辅小区组中的SCell时，如图7所示，终端设备、主小区组对应的主节点及辅小区组对应的辅节点的交互过程包括以下步骤：
在S702中，确定在发生目标事件时是否向网络设备发送该目标事件的相关信息。
本申请实施例中，终端设备可以根据协议，确定在发生目标事件时是否向辅节点发送该目标事件的相关信息；或者，也可以通过接收主小区组中的主节点发送的配置信息，确定在发生目标事件时是否向辅节点发送该目标事件的相关信息，具体的，主节点通过RRC Connection Reconfiguration过程发送配置信息；或者，也可以通过接收辅小区组中的辅节点发送的配置信息，确定在发生目标事件时是否向该辅节点发送该目标事件的相关信息，具体的，辅节点通过RRC Connection Reconfiguration过程发送配置信息。
在S704中，确定发生目标事件。
在S706中，执行下述至少一种处理操作：重置目标RLC实体、对目标SCell进行处理以及对复制承载进行处理。
在S708中，向辅节点发送目标事件的相关信息。
本申请实施例中，在确定发生目标事件时，终端设备可以通过信令无线承载SRB3直接向辅小区组对应的辅节点发送目标事件的相关信息。
在本申请提供的另一个实施例中，当目标SCell为SCG中的SCell时，如图8所示，终端设备、主小区组对应的主节点及辅小区组对应的辅节点的交互过程包括以下步骤，其中，终端设备执行S802～S808，主节点执行S810；
在S802中，确定在发生目标事件时是否向网络设备发送该目标事件的相关信息。
本申请实施例中，终端设备可以根据协议，确定在发生目标事件时是否向辅节点发送该目标事件的相关信息；或者，也可以通过接收主小区组中的主节点发送的配置信息，确定在发生目标事件时是否向辅节点发送该目标事件的相 关信息，具体的，主节点通过RRC Connection Reconfiguration过程发送配置信息；或者，也可以通过接收辅小区组中的辅节点发送的配置信息，确定在发生目标事件时是否向该辅节点发送该目标事件的相关信息，具体的，辅节点通过RRC Connection Reconfiguration过程发送配置信息。
在S804中，确定发生目标事件。
在S806中，执行下述至少一种处理操作：重置目标RLC实体、对目标SCell进行处理以及对复制承载进行处理。
在S808中，向主节点发送目标事件的相关信息。
在S810中，将目标事件的相关信息转发给辅节点。
本申请实施例中，在确定发生目标事件时，终端设备可以通过信令无线承载SRB1或SRB2向主小区组对应的主节点发送目标事件的相关信息，再由该主节点将目标事件的相关信息转发给辅节点。
需要说明的是，图6～图8所示实施例中对目标RLC实体、目标SCell及复制承载的处理过程与图3所示实施例中的处理过程类似，图6～图8所示实施例中目标事件的相关信息的内容与图5所示实施例中的目标事件的相关信息的内容类似，在此不再赘述，详情请见图3和图5所示实施例中的对应内容。
上述对本申请特定实施例进行了描述。其它实施例在所附权利要求书的范围内。在一些情况下，在权利要求书中记载的动作或步骤可以按照不同于实施例中的顺序来执行并且仍然可以实现期望的结果。另外，在附图中描绘的过程不一定要求示出的特定顺序或者连续顺序才能实现期望的结果。在某些实施方式中，多任务处理和并行处理也是可以的或者可能是有利的。
图9是本申请一实施例的数据传输失败的处理装置的结构示意图，如图9所示，数据传输失败的处理装置900，该装置可以包括：第一确定单元910和处理单元920，其中，
第一确定单元910，用于确定发生目标事件，其中，所述目标事件包括下述事件中的至少一种：目标无线链路控制RLC实体达到最大重传次数、目标 辅小区SCell物理层失步和目标SCell的随机接入过程失败，目标RLC实体为复制承载对应的终端设备中的RLC实体，所述目标RLC实体的待发送数据只通过SCell发送，所述目标SCell为用于发送所述目标RLC实体的待发送数据的至少一个SCell；
处理单元920，包括下述子单元中的至少一个：第一处理子单元、第二处理子单元和第三处理子单元，其中，所述第一处理子单元用于重置所述目标RLC实体，所述第二处理子单元用于对所述目标SCell进行处理，第三处理子单元用于对所述复制承载进行处理。
由上述实施例可见，该实施例可以明确在发生目标事件(即SCell失败)时，终端设备对目标RLC实体、目标SCell和复制承载所做出的处理，从而确保终端设备的工作性能以及避免对其他终端设备造成干扰。
可选地，作为一个实施例，数据传输失败的处理装置900，还可以包括：
第二确定单元，用于确定在发生所述目标事件时是否向网络设备发送所述目标事件的相关信息。
可选地，作为一个实施例，所述第二处理子单元，具体用于执行下述至少一种处理操作：
重置所述目标SCell所对应的所有RLC实体；
去激活所述目标SCell；
停止所述目标SCell的上行信号发送；以及，
停止所述目标SCell的下行信号接收。
可选地，作为一个实施例，所述第三处理子单元，具体用于执行下述至少一种处理操作：
去激活所述复制承载对应的包数据汇聚协议PDCP实体的数据复制功能；
将所述复制承载的默认发送路径更改为其他RLC实体对应的发送路径；
将所述复制承载挂起，其中，复制承载挂起时，所述复制承载不发送收和接收数据；
重建所述复制承载对应的PDCP实体；以及，
重置所述复制承载对应的媒体接入控制MAC实体。
可选地，作为一个实施例，所述第三处理子单元还用于：
确定所述复制承载的默认发送路径为所述目标RLC实体对应的发送路径。
可选地，作为一个实施例，所述第三处理子单元还用于：
在执行所述将所述复制承载挂起的操作之前，确定所述复制承载对应的所有RLC实体均发生下述事件中的至少一种：RLC实体达到最大重传次数、用于发送RLC实体的待发送数据的SCell物理层失步和用于发送RLC实体的待发送数据的SCell的随机接入过程失败。
可选地，作为一个实施例，所述第三处理子单元还用于：
在执行所述重建所述复制承载对应的PDCP实体的操作之前，确定所述复制承载对应的所有RLC实体均发生下述事件中的至少一种：RLC实体达到最大重传次数、用于发送RLC实体的待发送数据的SCell物理层失步和用于发送RLC实体的待发送数据的SCell的随机接入过程失败。
可选地，作为一个实施例，所述第三处理子单元还用于：
在执行所述重置所述复制承载对应的媒体接入控制MAC实体的操作之前，确定所述复制承载对应的所有RLC实体均发生下述事件中的至少一种：RLC实体达到最大重传次数、用于发送RLC实体的待发送数据的SCell物理层失步和用于发送RLC实体的待发送数据的SCell的随机接入过程失败。
可选地，作为一个实施例，所述第二确定单元包括：
第一确定子单元，用于根据预先配置在所述终端设备内的协议，确定在发生所述目标事件时是否向网络设备发送所述目标事件的相关信息。
可选地，作为一个实施例，所述第二确定单元包括：
第二确定子单元，用于接收网络设备发送的配置信息，其中，所述配置信息用于指示在发生所述目标事件时是否向所述网络设备发送所述目标事件的相关信息；
根据所述配置信息，确定在发生所述目标事件时是否向所述网络设备发送所述目标事件的相关信息。
可选地，作为一个实施例，所述网络设备包括：主小区组MCG对应的主节点MN、和/或辅小区组SCG对应的辅节点SN。
可选地，作为一个实施例，所述目标SCell为MCG中的SCell；
所述装置还包括：
第一发送单元，用于在发生所述目标事件时，通过信令无线承载SRB1或SRB2，向所述MCG对应的MN发送所述目标事件的相关信息。
可选地，作为一个实施例，所述目标SCell为SCG中的SCell；
所述装置还包括：
第二发送单元，用于在发生所述目标事件时，通过信令无线承载SRB3向所述SCG对应的SN发送所述目标事件的相关信息。
可选地，作为一个实施例，所述目标SCell为SCG中的SCell；
所述装置还包括：
第三发送单元，用于在发生所述目标事件时，通过信令无线承载SRB1或SRB2向MCG对应的MN发送所述目标事件的相关信息，其中，所述MN用于将所述目标事件的相关信息转发给所述SCG对应的SN。
可选地，作为一个实施例，所述目标事件的相关信息，包括以下一项或多项的任意组合：
目标SCell的标识；
所述目标SCell所属小区组的标识；
所述目标RLC实体对应的复制承载的标识；
所述目标RLC实体的标识；
所述目标RLC实体对应的逻辑信道的标识；
所述目标RLC实体对应的逻辑信道所属逻辑信道组的标识；
所述目标RLC实体对应的小区的测量结果；
所述目标RLC实体对应的小区的波束的测量结果；
服务小区的测量结果；
服务小区的波束的测量结果；
服务频点的小区的测量结果；
服务频点的小区的波束的测量结果；
所述目标SCell所属小区组的服务小区的测量结果；
所述目标SCell所属小区组的服务小区的波束的测量结果；
所述目标SCell所属服务频点的小区的测量结果；
所述目标SCell所属服务频点的小区的波束的测量结果；
非服务频点的小区的测量结果；以及，
非服务频点的小区的波束的测量结果。
图10是本申请的一个实施例电子设备的结构示意图。图10所示的电子设备1000包括：至少一个处理器1001、存储器1002、至少一个网络接口1004和用户接口1003。电子设备1000中的各个组件通过总线系统1005耦合在一起。可理解，总线系统1005用于实现这些组件之间的连接通信。总线系统1005除包括数据总线之外，还包括电源总线、控制总线和状态信号总线。但是为了清楚说明起见，在图10中将各种总线都标为总线系统1005。
其中，用户接口1003可以包括显示器、键盘或者点击设备(例如，鼠标，轨迹球(trackball)、触感板或者触摸屏等。
可以理解，本申请实施例中的存储器1002可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(Read-OnlyMemory，ROM)、可编程只读存储器(ProgrammableROM，PROM)、可擦除可编程只读存储器(ErasablePROM，EPROM)、电可擦除可编程只读存储器(ElectricallyEPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(RandomAccessMemory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如 静态随机存取存储器(StaticRAM，SRAM)、动态随机存取存储器(DynamicRAM，DRAM)、同步动态随机存取存储器(SynchronousDRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(DoubleDataRate SDRAM，DDRSDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(SynchlinkDRAM，SLDRAM)和直接内存总线随机存取存储器(DirectRambusRAM，DRRAM)。本申请实施例描述的系统和方法的存储器1002旨在包括但不限于这些和任意其它适合类型的存储器。
在一些实施方式中，存储器1002存储了如下的元素，可执行模块或者数据结构，或者他们的子集，或者他们的扩展集：操作系统10021和应用程序10022。
其中，操作系统10021，包含各种系统程序，例如框架层、核心库层、驱动层等，用于实现各种基础业务以及处理基于硬件的任务。应用程序10022，包含各种应用程序，例如媒体播放器(MediaPlayer)、浏览器(Browser)等，用于实现各种应用业务。实现本申请实施例方法的程序可以包含在应用程序10022中。
在本申请实施例中，终端设备1000还包括：存储在存储器1002上并可在处理器1001上运行的计算机程序，计算机程序被处理器1001执行时实现如下步骤：
确定发生目标事件，其中，所述目标事件包括下述事件中的至少一种：目标无线链路控制RLC实体达到最大重传次数、目标辅小区SCell物理层失步和目标SCell的随机接入过程失败，目标RLC实体为复制承载对应的终端设备中的RLC实体，所述目标RLC实体的待发送数据只通过SCell发送，所述目标SCell为用于发送所述目标RLC实体的待发送数据的至少一个SCell；
执行下述至少一种处理操作：重置所述目标RLC实体、对所述目标SCell进行处理以及对所述复制承载进行处理。
上述本申请实施例揭示的方法可以应用于处理器1001中，或者由处理器 1001实现。处理器1001可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法的各步骤可以通过处理器1001中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器1001可以是通用处理器、数字信号处理器(DigitalSignalProcessor，DSP)、专用集成电路(ApplicationSpecific IntegratedCircuit，ASIC)、现成可编程门阵列(FieldProgrammableGateArray，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的计算机可读存储介质中。该计算机可读存储介质位于存储器1002，处理器1001读取存储器1002中的信息，结合其硬件完成上述方法的步骤。具体地，该计算机可读存储介质上存储有计算机程序，计算机程序被处理器1001执行时实现如上述数据传输失败的处理方法实施例的各步骤。
可以理解的是，本申请实施例描述的这些实施例可以用硬件、软件、固件、中间件、微码或其组合来实现。对于硬件实现，处理单元可以实现在一个或多个专用集成电路(ApplicationSpecificIntegratedCircuits，ASIC)、数字信号处理器(DigitalSignalProcessing，DSP)、数字信号处理设备(DSPDevice，DSPD)、可编程逻辑设备(ProgrammableLogicDevice，PLD)、现场可编程门阵列(Field-ProgrammableGateArray，FPGA)、通用处理器、控制器、微控制器、微处理器、用于执行本申请所述功能的其它电子单元或其组合中。
对于软件实现，可通过执行本申请实施例所述功能的模块(例如过程、函数等)来实现本申请实施例所述的技术。软件代码可存储在存储器中并通过处理器执行。存储器可以在处理器中或在处理器外部实现。
此外，计算机程序被处理器1001执行时还可实现如下步骤：
可选地，所述方法还包括：
确定在发生所述目标事件时是否向网络设备发送所述目标事件的相关信息。
可选地，所述对所述目标SCell进行处理，包括下述至少一种处理操作：
重置所述目标SCell所对应的所有RLC实体；
去激活所述目标SCell；
停止所述目标SCell的上行信号发送；以及，
停止所述目标SCell的下行信号接收。
可选地，所述对所述复制承载进行处理，包括下述至少一种处理操作：
去激活所述复制承载对应的包数据汇聚协议PDCP实体的数据复制功能；
将所述复制承载的默认发送路径更改为其他RLC实体对应的发送路径；
将所述复制承载挂起，其中，复制承载挂起时，所述复制承载不发送收和接收数据；
重建所述复制承载对应的PDCP实体；以及，
重置所述复制承载对应的媒体接入控制MAC实体。
可选地，在所述将所述复制承载的默认发送路径更改为其他RLC实体对应的发送路径的步骤之前，还包括：
确定所述复制承载的默认发送路径为所述目标RLC实体对应的发送路径。
可选地，在所述将所述复制承载挂起的步骤之前，还包括：
确定所述复制承载对应的所有RLC实体均发生下述事件中的至少一种：RLC实体达到最大重传次数、用于发送RLC实体的待发送数据的SCell物理层失步和用于发送RLC实体的待发送数据的SCell的随机接入过程失败。
可选地，在所述重建所述复制承载对应的PDCP实体的步骤之前，还包括：
确定所述复制承载对应的所有RLC实体均发生下述事件中的至少一种：RLC实体达到最大重传次数、用于发送RLC实体的待发送数据的SCell物理层失步和用于发送RLC实体的待发送数据的SCell的随机接入过程失败。
可选地，在所述重置所述复制承载对应的媒体接入控制MAC实体的步骤之前，还包括：
确定所述复制承载对应的所有RLC实体均发生下述事件中的至少一种：RLC实体达到最大重传次数、用于发送RLC实体的待发送数据的SCell物理层失步和用于发送RLC实体的待发送数据的SCell的随机接入过程失败。
可选地，所述确定在发生所述目标事件时是否向网络设备发送所述目标事件的相关信息，包括：
根据预先配置在所述终端设备内的协议，确定在发生所述目标事件时是否向网络设备发送所述目标事件的相关信息。
可选地，所述确定在发生所述目标事件时是否向网络设备发送所述目标事件的相关信息，包括：
接收网络设备发送的配置信息，其中，所述配置信息用于指示在发生所述目标事件时是否向所述网络设备发送所述目标事件的相关信息；
根据所述配置信息，确定在发生所述目标事件时是否向所述网络设备发送所述目标事件的相关信息。
可选地，所述网络设备包括：主小区组MCG对应的主节点MN、和/或辅小区组SCG对应的辅节点SN。
可选地，所述目标SCell为MCG中的SCell；
所述方法还包括：
在发生所述目标事件时，通过信令无线承载SRB1或SRB2，向所述MCG对应的MN发送所述目标事件的相关信息。
可选地，所述目标SCell为SCG中的SCell；
所述方法还包括：
在发生所述目标事件时，通过信令无线承载SRB3向所述SCG对应的SN发送所述目标事件的相关信息。
可选地，所述目标SCell为SCG中的SCell；
所述方法还包括：
在发生所述目标事件时，通过信令无线承载SRB1或SRB2向MCG对应的MN发送所述目标事件的相关信息，其中，所述MN用于将所述目标事件的相关信息转发给所述SCG对应的SN。
可选地，所述目标事件的相关信息，包括以下一项或多项的任意组合：
目标SCell的标识；
所述目标SCell所属小区组的标识；
所述目标RLC实体对应的复制承载的标识；
所述目标RLC实体的标识；
所述目标RLC实体对应的逻辑信道的标识；
所述目标RLC实体对应的逻辑信道所属逻辑信道组的标识；
所述目标RLC实体对应的小区的测量结果；
所述目标RLC实体对应的小区的波束的测量结果；
服务小区的测量结果；
服务小区的波束的测量结果；
服务频点的小区的测量结果；
服务频点的小区的波束的测量结果；
所述目标SCell所属小区组的服务小区的测量结果；
所述目标SCell所属小区组的服务小区的波束的测量结果；
所述目标SCell所属服务频点的小区的测量结果；
所述目标SCell所属服务频点的小区的波束的测量结果；
非服务频点的小区的测量结果；以及，
非服务频点的小区的波束的测量结果。
终端设备1000能够实现前述实施例中终端设备实现的各个过程，为避免重复，这里不再赘述。
本申请实施例还提出了一种计算机可读存储介质，该计算机可读存储介质 存储一个或多个程序，该一个或多个程序包括指令，该指令当被包括多个应用程序的便携式电子设备执行时，能够使该便携式电子设备执行图1所示实施例的方法，并具体用于执行以下操作：
确定发生目标事件，其中，所述目标事件包括下述事件中的至少一种：目标无线链路控制RLC实体达到最大重传次数、目标辅小区SCell物理层失步和目标SCell的随机接入过程失败，目标RLC实体为复制承载对应的终端设备中的RLC实体，所述目标RLC实体的待发送数据只通过SCell发送，所述目标SCell为用于发送所述目标RLC实体的待发送数据的至少一个SCell；
执行下述至少一种处理操作：重置所述目标RLC实体、对所述目标SCell进行处理以及对所述复制承载进行处理。
总之，以上所述仅为本申请的较佳实施例而已，并非用于限定本申请的保护范围。凡在本申请的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本申请的保护范围之内。
上述实施例阐明的系统、装置、模块或单元，具体可以由计算机芯片或实体实现，或者由具有某种功能的产品来实现。一种典型的实现设备为计算机。具体的，计算机例如可以为个人计算机、膝上型计算机、蜂窝电话、相机电话、智能电话、个人数字助理、媒体播放器、导航设备、电子邮件设备、游戏控制台、平板计算机、可穿戴设备或者这些设备中的任何设备的组合。
计算机可读介质包括永久性和非永久性、可移动和非可移动媒体可以由任何方法或技术来实现信息存储。信息可以是计算机可读指令、数据结构、程序的模块或其他数据。计算机的存储介质的例子包括，但不限于相变内存(PRAM)、静态随机存取存储器(SRAM)、动态随机存取存储器(DRAM)、其他类型的随机存取存储器(RAM)、只读存储器(ROM)、电可擦除可编程只读存储器(EEPROM)、快闪记忆体或其他内存技术、只读光盘只读存储器(CD-ROM)、数字多功能光盘(DVD)或其他光学存储、磁盒式磁带，磁带磁磁盘存储或其他磁性存储设备或任何其他非传输介质，可用于存储可以被计算设备访问的信息。按照本文中 的界定，计算机可读介质不包括暂存电脑可读媒体(transitory media)，如调制的数据信号和载波。
还需要说明的是，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、商品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、商品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括所述要素的过程、方法、商品或者设备中还存在另外的相同要素。
本说明书中的各个实施例均采用递进的方式描述，各个实施例之间相同相似的部分互相参见即可，每个实施例重点说明的都是与其他实施例的不同之处。尤其，对于系统实施例而言，由于其基本相似于方法实施例，所以描述的比较简单，相关之处参见方法实施例的部分说明即可。

Claims (32)

  1. 一种数据传输失败的处理方法，其特征在于，所述方法由终端设备执行，所述方法包括：
    确定发生目标事件，其中，所述目标事件包括下述事件中的至少一种：目标无线链路控制RLC实体达到最大重传次数、目标辅小区SCell物理层失步和目标SCell的随机接入过程失败，目标RLC实体为复制承载对应的终端设备中的RLC实体，所述目标RLC实体的待发送数据只通过SCell发送，所述目标SCell为用于发送所述目标RLC实体的待发送数据的至少一个SCell；
    执行下述至少一种处理操作：重置所述目标RLC实体、对所述目标SCell进行处理以及对所述复制承载进行处理。
  2. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    确定在发生所述目标事件时是否向网络设备发送所述目标事件的相关信息。
  3. 根据权利要求1或2所述的方法，其特征在于，所述对所述目标SCell进行处理，包括下述至少一种处理操作：
    重置所述目标SCell所对应的所有RLC实体；
    去激活所述目标SCell；
    停止所述目标SCell的上行信号发送；以及，
    停止所述目标SCell的下行信号接收。
  4. 根据权利要求1～3任一项所述的方法，其特征在于，所述对所述复制承载进行处理，包括下述至少一种处理操作：
    去激活所述复制承载对应的包数据汇聚协议PDCP实体的数据复制功能；
    将所述复制承载的默认发送路径更改为其他RLC实体对应的发送路径；
    将所述复制承载挂起，其中，复制承载挂起时，所述复制承载不发送收和接收数据；
    重建所述复制承载对应的PDCP实体；以及，
    重置所述复制承载对应的媒体接入控制MAC实体。
  5. 根据权利要求4所述的方法，其特征在于，在所述将所述复制承载的默认发送路径更改为其他RLC实体对应的发送路径的步骤之前，还包括：
    确定所述复制承载的默认发送路径为所述目标RLC实体对应的发送路径。
  6. 根据权利要求4所述的方法，其特征在于，在所述将所述复制承载挂起的步骤之前，还包括：
    确定所述复制承载对应的所有RLC实体均发生下述事件中的至少一种：RLC实体达到最大重传次数、用于发送RLC实体的待发送数据的SCell物理层失步和用于发送RLC实体的待发送数据的SCell的随机接入过程失败。
  7. 根据权利要求4所述的方法，其特征在于，在所述重建所述复制承载对应的PDCP实体的步骤之前，还包括：
    确定所述复制承载对应的所有RLC实体均发生下述事件中的至少一种：RLC实体达到最大重传次数、用于发送RLC实体的待发送数据的SCell物理层失步和用于发送RLC实体的待发送数据的SCell的随机接入过程失败。
  8. 根据权利要求4所述的方法，其特征在于，在所述重置所述复制承载对应的媒体接入控制MAC实体的步骤之前，还包括：
    确定所述复制承载对应的所有RLC实体均发生下述事件中的至少一种：RLC实体达到最大重传次数、用于发送RLC实体的待发送数据的SCell物理层失步和用于发送RLC实体的待发送数据的SCell的随机接入过程失败。
  9. 根据权利要求2所述的方法，其特征在于，所述确定在发生所述目标事件时是否向网络设备发送所述目标事件的相关信息，包括：
    根据预先配置在所述终端设备内的协议，确定在发生所述目标事件时是否向网络设备发送所述目标事件的相关信息。
  10. 根据权利要求2所述的方法，其特征在于，所述确定在发生所述目标事件时是否向网络设备发送所述目标事件的相关信息，包括：
    接收网络设备发送的配置信息，其中，所述配置信息用于指示在发生所述 目标事件时是否向所述网络设备发送所述目标事件的相关信息；
    根据所述配置信息，确定在发生所述目标事件时是否向所述网络设备发送所述目标事件的相关信息。
  11. 根据权利要求10所述的方法，其特征在于，所述网络设备包括：主小区组MCG对应的主节点MN、和/或辅小区组SCG对应的辅节点SN。
  12. 根据权利要求2所述的方法，其特征在于，所述目标SCell为MCG中的SCell；
    所述方法还包括：
    在发生所述目标事件时，通过信令无线承载SRB1或SRB2，向所述MCG对应的MN发送所述目标事件的相关信息。
  13. 根据权利要求2所述的方法，其特征在于，所述目标SCell为SCG中的SCell；
    所述方法还包括：
    在发生所述目标事件时，通过信令无线承载SRB3向所述SCG对应的SN发送所述目标事件的相关信息。
  14. 根据权利要求2所述的方法，其特征在于，所述目标SCell为SCG中的SCell；
    所述方法还包括：
    在发生所述目标事件时，通过信令无线承载SRB1或SRB2向MCG对应的MN发送所述目标事件的相关信息，其中，所述MN用于将所述目标事件的相关信息转发给所述SCG对应的SN。
  15. 根据权利要求2所述的方法，其特征在于，所述目标事件的相关信息，包括以下一项或多项的任意组合：
    目标SCell的标识；
    所述目标SCell所属小区组的标识；
    所述目标RLC实体对应的复制承载的标识；
    所述目标RLC实体的标识；
    所述目标RLC实体对应的逻辑信道的标识；
    所述目标RLC实体对应的逻辑信道所属逻辑信道组的标识；
    所述目标RLC实体对应的小区的测量结果；
    所述目标RLC实体对应的小区的波束的测量结果；
    服务小区的测量结果；
    服务小区的波束的测量结果；
    服务频点的小区的测量结果；
    服务频点的小区的波束的测量结果；
    所述目标SCell所属小区组的服务小区的测量结果；
    所述目标SCell所属小区组的服务小区的波束的测量结果；
    所述目标SCell所属服务频点的小区的测量结果；
    所述目标SCell所属服务频点的小区的波束的测量结果；
    非服务频点的小区的测量结果；以及，
    非服务频点的小区的波束的测量结果。
  16. 一种数据传输失败的处理装置，其特征在于，所述装置包括：
    第一确定单元，用于确定发生目标事件，其中，所述目标事件包括下述事件中的至少一种：目标无线链路控制RLC实体达到最大重传次数、目标辅小区SCell物理层失步和目标SCell的随机接入过程失败，目标RLC实体为复制承载对应的终端设备中的RLC实体，所述目标RLC实体的待发送数据只通过SCell发送，所述目标SCell为用于发送所述目标RLC实体的待发送数据的至少一个SCell；
    处理单元，包括下述子单元中的至少一个：第一处理子单元、第二处理子单元和第三处理子单元，其中，所述第一处理子单元用于重置所述目标RLC实体，所述第二处理子单元用于对所述目标SCell进行处理，第三处理子单元用于对所述复制承载进行处理。
  17. 根据权利要求16所述的装置，其特征在于，所述装置还包括：
    第二确定单元，用于确定在发生所述目标事件时是否向网络设备发送所述目标事件的相关信息。
  18. 根据权利要求15或16所述的装置，其特征在于，所述第二处理子单元，具体用于执行下述至少一种处理操作：
    重置所述目标SCell所对应的所有RLC实体；
    去激活所述目标SCell；
    停止所述目标SCell的上行信号发送；以及，
    停止所述目标SCell的下行信号接收。
  19. 根据权利要求16～18任一项所述的装置，其特征在于，所述第三处理子单元，具体用于执行下述至少一种处理操作：
    去激活所述复制承载对应的包数据汇聚协议PDCP实体的数据复制功能；
    将所述复制承载的默认发送路径更改为其他RLC实体对应的发送路径；
    将所述复制承载挂起，其中，复制承载挂起时，所述复制承载不发送收和接收数据；
    重建所述复制承载对应的PDCP实体；以及，
    重置所述复制承载对应的媒体接入控制MAC实体。
  20. 根据权利要求19所述的装置，其特征在于，所述第三处理子单元还用于：
    确定所述复制承载的默认发送路径为所述目标RLC实体对应的发送路径。
  21. 根据权利要求19所述的装置，其特征在于，所述第三处理子单元还用于：
    在执行所述将所述复制承载挂起的操作之前，确定所述复制承载对应的所有RLC实体均发生下述事件中的至少一种：RLC实体达到最大重传次数、用于发送RLC实体的待发送数据的SCell物理层失步和用于发送RLC实体的待发送数据的SCell的随机接入过程失败。
  22. 根据权利要求19所述的装置，其特征在于，所述第三处理子单元还用于：
    在执行所述重建所述复制承载对应的PDCP实体的操作之前，确定所述复制承载对应的所有RLC实体均发生下述事件中的至少一种：RLC实体达到最大重传次数、用于发送RLC实体的待发送数据的SCell物理层失步和用于发送RLC实体的待发送数据的SCell的随机接入过程失败。
  23. 根据权利要求19所述的装置，其特征在于，所述第三处理子单元还用于：
    在执行所述重置所述复制承载对应的媒体接入控制MAC实体的操作之前，确定所述复制承载对应的所有RLC实体均发生下述事件中的至少一种：RLC实体达到最大重传次数、用于发送RLC实体的待发送数据的SCell物理层失步和用于发送RLC实体的待发送数据的SCell的随机接入过程失败。
  24. 根据权利要求17所述的装置，其特征在于，所述第二确定单元包括：
    第一确定子单元，用于根据预先配置在所述终端设备内的协议，确定在发生所述目标事件时是否向网络设备发送所述目标事件的相关信息。
  25. 根据权利要求17所述的装置，其特征在于，所述第二确定单元包括：
    第二确定子单元，用于接收网络设备发送的配置信息，其中，所述配置信息用于指示在发生所述目标事件时是否向所述网络设备发送所述目标事件的相关信息；
    根据所述配置信息，确定在发生所述目标事件时是否向所述网络设备发送所述目标事件的相关信息。
  26. 根据权利要求25所述的装置，其特征在于，所述网络设备包括：主小区组MCG对应的主节点MN、和/或辅小区组SCG对应的辅节点SN。
  27. 根据权利要求17所述的装置，其特征在于，所述目标SCell为MCG中的SCell；
    所述装置还包括：
    第一发送单元，用于在发生所述目标事件时，通过信令无线承载SRB1或SRB2，向所述MCG对应的MN发送所述目标事件的相关信息。
  28. 根据权利要求17所述的装置，其特征在于，所述目标SCell为SCG中的SCell；
    所述装置还包括：
    第二发送单元，用于在发生所述目标事件时，通过信令无线承载SRB3向所述SCG对应的SN发送所述目标事件的相关信息。
  29. 根据权利要求17所述的装置，其特征在于，所述目标SCell为SCG中的SCell；
    所述装置还包括：
    第三发送单元，用于在发生所述目标事件时，通过信令无线承载SRB1或SRB2向MCG对应的MN发送所述目标事件的相关信息，其中，所述MN用于将所述目标事件的相关信息转发给所述SCG对应的SN。
  30. 根据权利要求17所述的装置，其特征在于，所述目标事件的相关信息，包括以下一项或多项的任意组合：
    目标SCell的标识；
    所述目标SCell所属小区组的标识；
    所述目标RLC实体对应的复制承载的标识；
    所述目标RLC实体的标识；
    所述目标RLC实体对应的逻辑信道的标识；
    所述目标RLC实体对应的逻辑信道所属逻辑信道组的标识；
    所述目标RLC实体对应的小区的测量结果；
    所述目标RLC实体对应的小区的波束的测量结果；
    服务小区的测量结果；
    服务小区的波束的测量结果；
    服务频点的小区的测量结果；
    服务频点的小区的波束的测量结果；
    所述目标SCell所属小区组的服务小区的测量结果；
    所述目标SCell所属小区组的服务小区的波束的测量结果；
    所述目标SCell所属服务频点的小区的测量结果；
    所述目标SCell所属服务频点的小区的波束的测量结果；
    非服务频点的小区的测量结果；以及，
    非服务频点的小区的波束的测量结果。
  31. 一种电子设备，其特征在于，该电子设备包括：
    处理器；以及
    存储计算机可执行指令的存储器，所述可执行指令在被执行时使所述处理器执行如权利要求1～15任一所述方法的步骤。
  32. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质存储一个或多个程序，所述一个或多个程序当被包括多个应用程序的电子设备执行时，使得所述电子设备执行如权利要求1～15任一所述方法的步骤。
PCT/CN2018/106035 2017-09-25 2018-09-17 数据传输失败的处理方法及装置 WO2019057012A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US16/650,658 US11290939B2 (en) 2017-09-25 2018-09-17 Method and apparatus for processing data transmission failure
EP18858284.5A EP3691403A1 (en) 2017-09-25 2018-09-17 Method and apparatus for processing data transmission failure

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710877187.7A CN109560946B (zh) 2017-09-25 2017-09-25 数据传输失败的处理方法及装置
CN201710877187.7 2017-09-25

Publications (1)

Publication Number Publication Date
WO2019057012A1 true WO2019057012A1 (zh) 2019-03-28

Family

ID=65810586

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/106035 WO2019057012A1 (zh) 2017-09-25 2018-09-17 数据传输失败的处理方法及装置

Country Status (4)

Country Link
US (1) US11290939B2 (zh)
EP (1) EP3691403A1 (zh)
CN (1) CN109560946B (zh)
WO (1) WO2019057012A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113455042A (zh) * 2019-07-29 2021-09-28 Oppo广东移动通信有限公司 无线通信的方法、终端设备和网络设备
WO2021243725A1 (en) * 2020-06-06 2021-12-09 Qualcomm Incorporated Avoiding random access issues in non-standalone new radio cells

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018197091A1 (en) * 2017-04-27 2018-11-01 Sony Corporation Mobile communications network, infrastructure equipment, communications device and methods
US10757615B2 (en) * 2017-09-13 2020-08-25 Comcast Cable Communications, Llc Radio link failure information for PDCP duplication
CN110475285B (zh) * 2018-05-10 2021-03-16 维沃移动通信有限公司 一种操作方法及终端
CN111465119B (zh) * 2019-03-28 2023-02-24 维沃移动通信有限公司 数据发送方法、信息配置方法、终端及网络设备
US12004247B2 (en) * 2019-06-25 2024-06-04 Apple Inc. User equipment assistance information for voice over cellular

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102378403A (zh) * 2010-08-16 2012-03-14 宏达国际电子股份有限公司 处理无线资源控制连线重设的方法
WO2014179982A1 (en) * 2013-05-10 2014-11-13 Broadcom Corporation Configurable protocol stack for dual connectivity
CN104247491A (zh) * 2013-02-01 2014-12-24 华为技术有限公司 无线链路控制方法及装置、无线网络控制器、用户设备
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
US20160065700A1 (en) * 2014-08-29 2016-03-03 Lg Electronics Inc. Pdcp operation in a wireless communication system supporting dual connectivity

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102223658B (zh) * 2010-04-19 2016-06-29 中兴通讯股份有限公司 一种处理无线链路失败的方法和中继节点
CN102347827A (zh) * 2010-07-28 2012-02-08 中兴通讯股份有限公司 一种实现rlc层重传的方法及系统
EP3603322B1 (en) * 2017-03-24 2023-08-16 Nokia Technologies Oy Handling of pdcp duplication and data recovery in new radio access technology
US10757615B2 (en) * 2017-09-13 2020-08-25 Comcast Cable Communications, Llc Radio link failure information for PDCP duplication

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102378403A (zh) * 2010-08-16 2012-03-14 宏达国际电子股份有限公司 处理无线资源控制连线重设的方法
CN104247491A (zh) * 2013-02-01 2014-12-24 华为技术有限公司 无线链路控制方法及装置、无线网络控制器、用户设备
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
WO2014179982A1 (en) * 2013-05-10 2014-11-13 Broadcom Corporation Configurable protocol stack for dual connectivity
US20160065700A1 (en) * 2014-08-29 2016-03-03 Lg Electronics Inc. Pdcp operation in a wireless communication system supporting dual connectivity

Non-Patent Citations (1)

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

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113455042A (zh) * 2019-07-29 2021-09-28 Oppo广东移动通信有限公司 无线通信的方法、终端设备和网络设备
CN113455042B (zh) * 2019-07-29 2023-10-31 Oppo广东移动通信有限公司 无线通信的方法、终端设备和网络设备
WO2021243725A1 (en) * 2020-06-06 2021-12-09 Qualcomm Incorporated Avoiding random access issues in non-standalone new radio cells

Also Published As

Publication number Publication date
CN109560946A (zh) 2019-04-02
EP3691403A4 (en) 2020-08-05
US11290939B2 (en) 2022-03-29
CN109560946B (zh) 2021-02-09
EP3691403A1 (en) 2020-08-05
US20200322864A1 (en) 2020-10-08

Similar Documents

Publication Publication Date Title
WO2019057012A1 (zh) 数据传输失败的处理方法及装置
WO2019137304A1 (zh) 数据的处理方法、用户侧设备及网络侧设备
KR102455839B1 (ko) 접속 실패의 회복 방법 및 기기
WO2022237740A1 (zh) 一种小区切换及其控制方法及装置
US20200214065A1 (en) User equipment category signaling in an lte-5g configuration
US11490292B2 (en) Transferring a data connection to a radio access network
US20220330126A1 (en) Information transmission method and apparatus
WO2021139546A1 (zh) 信息传输方法及装置
CN114009139A (zh) 会话上下文的处理
WO2019061110A1 (zh) 一种接入链路的管理方法、设备、存储介质及系统
WO2021083054A1 (zh) 消息传输方法及装置
WO2023024864A1 (zh) 会话重建的方法、装置和系统
TWI753992B (zh) 資訊傳輸方法、設備及電腦可讀介質
WO2021185118A1 (zh) 通信方法及终端设备
EP3614714B1 (en) Method for acquiring context configuration information, terminal device and access network device
CN112217618B (zh) 信息传输方法及装置
US11876868B2 (en) Deriving an operating system identity
US11902835B2 (en) Method and device for configuring data flow
EP4135462A1 (en) Data transmission method and apparatus
WO2024017244A1 (zh) 信息发送方法、信息接收方法、装置及相关设备
WO2024065419A1 (en) Methods and apparatuses of a cho procedure with candidate scgs
WO2023231878A1 (zh) 信息处理方法、装置、网络侧设备及终端
US20210029755A1 (en) Method of configuring service data adaptation protocol entity and device
CN112804753A (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: 18858284

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

Country of ref document: EP

Effective date: 20200428