Data transmission processing method and related device

Abstract

The embodiment of the present application provides a data transmission processing method, including: determining the occurrence of a target event, wherein the target event includes at least one of the following: a primary cell group connection failure event, a secondary cell group connection failure event, and a secondary cell group deactivation event; controlling the target entity not to perform data transmission based on the first cell group corresponding to the target event, or suspending the target entity. The target entity is a target packet data convergence protocol PDCP entity or a first radio link control layer protocol RLC entity in the first cell group. By adopting the embodiment of the present application, data transmission failure can be avoided.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a data transmission processing method and related devices. Background Art

[0002] In the dual connection structure, the terminal device can establish a physical path with two access network devices and realize data transmission. The two access network devices can be divided into a master node (MN) and a secondary node (SN). The one or more cells provided by the MN for the terminal device can be called a master cell group (MCG), and the one or more cells provided by the SN for the terminal device can be called a secondary cell group (SCG). The terminal device can communicate through the MCG and / or SCG.

[0003] In the existing mechanism, when the terminal device detects that the link between the terminal device and the SCG fails to connect, it will suspend the transmission link of the SCG to avoid the failure of communication based on the SCG. After the terminal device suspends the transmission link of the SCG, the packet data convergence protocol (PDCP) entity and the radio link control (RLC) entity in the SCG still work normally. For uplink data, the PDCP entity will process the data to be sent normally and submit the PDCP protocol data unit (PDU) to the RLC entity of the SCG. The RLC entity of the SCG will also process the data normally and wait for the media access control protocol (MAC) layer to schedule the transmission.

[0004] However, because the SCG transmission link is suspended, the RLC layer data of the SCG that has been processed cannot be sent in time, resulting in data transmission failure. When the terminal device detects that the link between the MCG and the terminal device fails to connect, the MCG transmission link will be suspended, and the RLC layer data of the MCG that has been processed will have a technical problem of transmission failure. And in the existing mechanism, the processing method of the SCG deactivation event has not been defined. If the method for handling the connection failure event of the link between the terminal device and the SCG is referred to, the SCG transmission link will be suspended, and the RLC layer data of the SCG that has been processed will have a technical problem of transmission failure. Summary of the invention

[0005] The embodiments of the present application disclose a data transmission processing method and related devices, which can avoid data transmission failure.

[0006] In the first aspect, an embodiment of the present application discloses a data transmission processing method, including: determining the occurrence of a target event, wherein the target event includes at least one of the following: a primary cell group connection failure event, a secondary cell group connection failure event, and a secondary cell group deactivation event; controlling the target entity not to perform data transmission based on the first cell group corresponding to the target event, or suspending the target entity. The target entity is a PDCP entity or an RLC entity in the first cell group. That is, after the terminal device determines that the target event has occurred, the target entity in the first cell group is controlled not to use the transmission resources of the first cell group corresponding to the target event for data transmission, or the target entity is suspended so that the target entity does not use the transmission resources of the first cell group corresponding to the target event for data transmission, thereby avoiding the use of the first cell group to communicate with the access network device corresponding to the first cell group, and avoiding the occurrence of data transmission failure.

[0007] In a possible example, the target entity is a target PDCP entity, and the method further includes: the terminal device controls the target PDCP entity to send data to a second RLC entity in a second cell group, and the second cell group and the first cell group correspond to different access network devices. That is, when the target PDCP entity does not transmit data based on the first cell group, sending data based on the second RLC entity in the second cell group can avoid data transmission interruption in the target PDCP entity, thereby improving data transmission efficiency.

[0008] In a possible example, the second RLC entity includes an RLC entity associated with the target PDCP entity copied by the access network device in the second cell group, and the terminal device controls the target PDCP entity to send data to the second RLC entity in the second cell group, including: in response to the second RLC entity being in an activated state, the terminal device controls the target PDCP entity to send data to the second RLC entity. It can be understood that when the second RLC entity is an RLC entity associated with the target PDCP entity copied by the access network device in the second cell group, and is in an activated state, the data of the target PDCP entity can be transmitted based on the second RLC entity, thereby avoiding data transmission interruption in the target PDCP entity and improving data transmission efficiency. When the second RLC entity is in an inactive state, the terminal device first configures the second RLC entity to be in an activated state, and then controls the target PDCP entity to send data to the second RLC entity.

[0009] The second RLC entity includes an RLC entity associated with the separated bearer in the second cell group by the access network device as the target PDCP entity. If the uplink data threshold is not considered, the terminal device can directly control the target PDCP entity to send data to the second RLC entity. If the uplink data threshold is considered, in a possible example, the terminal device controls the target PDCP entity to send data to the second RLC entity in the second cell group, including: in response to the second RLC entity being the main RLC entity, the terminal device controls the target PDCP entity to send data to the second RLC entity. It can be understood that when the second RLC entity is an RLC entity associated with the separated bearer in the second cell group by the access network device as the target PDCP entity, and is the main RLC entity, the data of the target PDCP entity can be transmitted based on the second RLC entity, thereby avoiding data transmission interruption in the target PDCP entity and improving data transmission efficiency. When the second RLC entity is not the main RLC entity, the terminal device first modifies the second RLC entity as the main RLC entity, and then controls the target PDCP entity to send data to the second RLC entity.

[0010] In a possible example, the target entity is a first RLC entity, and the method further includes: the terminal device discards the RLC SDU that has been partially sent in the first RLC entity. It can be understood that before the target event occurs, if the segment of the RLC SDU has been sent, the RLC SDU is also discarded, and after the target event is restored, the terminal device can reprocess the RLC SDU to avoid data loss.

[0011] In a possible example, the target entity is a first RLC entity, and the method further includes: the terminal device suspends the target PDCP entity. That is, when it is determined that the target event occurs, the first RLC entity and the target PDCP entity are suspended, which can prevent the target PDCP entity from sending uplink data to the first RLC entity, and prevent the first RLC entity from sending uplink data, further avoiding the occurrence of data transmission failure.

[0012] In a possible example, before the terminal device controls the target entity not to perform data transmission based on the first cell group, or suspends the target entity, the method further includes: the terminal device sends first indication information to the target entity, the first indication information is used to indicate the occurrence of the target event, or to indicate that the target entity does not perform data transmission based on the first cell group. In this way, the target entity can be directly controlled by the terminal device according to the first indication information, thereby improving the processing efficiency of the target entity.

[0013] In a possible example, the method further includes: the terminal device suspends the transmission link of the first cell group. That is, when it is determined that the target event occurs, the transmission link of the first cell group is suspended, which can prevent the target entity from sending uplink data to the first cell group and prevent the first cell group from receiving the uplink data, further avoiding the occurrence of data transmission failure.

[0014] In a possible example, the method further includes: the terminal device sends second indication information to the access network device, the second indication information is used to indicate the occurrence of the target event, the type of the target event, or the measurement result of the terminal device. In this way, the access network device can determine the occurrence of the target event and related information of the target event in the terminal device through the second indication information, which facilitates the access network device to process the target event and improves processing efficiency.

[0015] In the second aspect, an embodiment of the present application discloses a data transmission processing method, including: a terminal device receives a third indication information from an access network device; the terminal device determines the target event recovery based on the third indication information, wherein the target event includes at least one of the following: a primary cell group connection failure event, a secondary cell group connection failure event, and a secondary cell group deactivation event; the terminal device controls the target entity to perform data transmission based on the first cell group corresponding to the target event, or restores the target entity. The target entity is the target PDCP entity or the first RLC entity in the first cell group. That is to say, after the terminal device receives the third indication information, it can determine that the target event is restored, so that the target entity can be directly controlled to use the transmission resources of the first cell group corresponding to the target event for data transmission, or the target entity can be restored to enable the target entity to use the transmission resources of the first cell group corresponding to the target event for data transmission, thereby avoiding data loss.

[0016] In a possible example, the target entity is a target PDCP entity, and the method further includes: the terminal device reestablishes the first RLC entity. In this way, it can be ensured that the RLC state of the terminal device is consistent with that of the serving cell of the new SCG, which can increase the probability of successful data transmission.

[0017] In a possible example, the method further includes: the terminal device discards the data stored in the first RLC entity. In this way, the data received by the first RLC entity can be reprocessed to avoid repeated transmission.

[0018] In a possible example, the target entity is a target PDCP entity, and the method further includes: the terminal device reestablishes the target PDCP entity. In this way, the target PDCP entity can be reconnected with the first RLC entity in the first cell group, which can ensure that the RLC state of the terminal device is consistent with that of the service cell of the new SCG, and the probability of successful data transmission can be increased.

[0019] In a possible example, the method further includes: the terminal device retransmits the unsent data of the PDCP entity, thereby avoiding data loss.

[0020] In a possible example, the method further includes: the terminal device controls the target PDCP entity to send data to the second RLC entity in the second cell group, and the second cell group and the first cell group correspond to different access network devices. It can be understood that by transmitting data for the target PDCP entity by the first RLC entity and the second RLC entity at the same time, the data transmission efficiency can be improved.

[0021] In a possible example, the first RLC entity includes an RLC entity associated with a bearer that is copied by an access network device as a target PDCP entity in a first cell group, and the terminal device controls the target entity to perform data transmission based on the first cell group, including: in response to the first RLC entity being in an activated state, the terminal device controls the target PDCP entity to send data to the first RLC entity. That is, when the first RLC entity is an RLC entity associated with a bearer that is copied by an access network device as a target PDCP entity in a first cell group, and the first RLC entity is in an activated state, the terminal device can control the target PDCP entity to send data to the first RLC entity. When the first RLC entity is in an inactive state, the terminal device first configures the first RLC entity to be in an activated state, and then controls the target PDCP entity to send data to the first RLC entity.

[0022] The first RLC entity includes an RLC entity associated with the target PDCP entity separated from the access network device in the first cell group. If the uplink data threshold is not considered, the terminal device can directly control the target PDCP entity to send data to the first RLC entity. If the uplink data threshold is considered, in a possible example, the terminal device controls the target entity to transmit data based on the first cell group, including: in response to the first RLC entity being the main RLC entity, the terminal device controls the target PDCP entity to send data to the first RLC entity. That is, when the first RLC entity is the RLC entity separated from the target PDCP entity in the first cell group, and the first RLC entity is an RLC entity, the terminal device can control the target PDCP entity to send data to the main RLC entity (i.e., the first RLC entity). When the first RLC entity is not the main RLC entity, the terminal device first modifies the first RLC entity as the main RLC entity, and then controls the target PDCP entity to send data to the first RLC entity.

[0023] In a possible example, the target entity is a first RLC entity, and the method further includes: the terminal device reprocesses the RLC SDU stored in the first RLC entity. It can be understood that after the terminal device reconstructs the first RLC entity, reprocessing the data RLC SDU stored in the first RLC entity can avoid data loss.

[0024] In a possible example, before the terminal device controls the target entity to perform data transmission based on the first cell group corresponding to the target event, or restores the target entity, the method further includes: the terminal device sends fourth indication information to the target entity, and the fourth indication information is used to indicate the target event recovery, or to indicate the target entity to perform data transmission based on the first cell group. In this way, the target entity can be directly controlled by the terminal device according to the fourth indication information, thereby improving the processing efficiency of the target entity.

[0025] In a possible example, the method further includes: the terminal device recovering the transmission link of the first cell group. In this way, by recovering the transmission link of the first cell group, the situation where data transmission failure occurs when the target entity sends uplink data to the first cell group can be further avoided.

[0026] In a third aspect, an embodiment of the present application provides a data transmission processing device, comprising a processing unit and / or a communication unit corresponding to the method of any of the above aspects.

[0027] In a fourth aspect, an embodiment of the present application provides a data transmission processing device, including a processor, a memory and a communication interface, wherein the processor is used to store computer program code stored in the memory for executing any of the methods described above.

[0028] In a fifth aspect, the present application provides a chip, including a processor, for calling and executing instructions stored in the memory from a memory, so that a terminal device equipped with the chip executes any of the above methods.

[0029] In the sixth aspect, the present application provides another chip, which can be a chip in a terminal device or an access network device. The chip includes: an input interface, an output interface and a processing circuit. The input interface, the output interface and the circuit are connected through an internal connection path, and the processing circuit is used to execute any of the above methods.

[0030] In the seventh aspect, the present application provides another chip, including: an input interface, an output interface, a processor, and optionally, a memory. The input interface, the output interface, the processor and the memory are connected through an internal connection path. The processor is used to execute the code in the memory. When the code is executed, the processor is used to execute the method in any of the above aspects.

[0031] In an eighth aspect, the present application provides a chip system, which includes at least one processor, a memory and an interface circuit, wherein the memory, a transceiver and at least one processor are interconnected through lines, and instructions are stored in at least one memory; when the above instructions are executed by the processor, the method of any of the above aspects is implemented.

[0032] In a ninth aspect, the present application provides a computer-readable storage medium, in which instructions are stored, and when the computer-readable storage medium is run on a computer, the computer executes any of the methods described above.

[0033] In a tenth aspect, the present application provides a computer program product, which is used to store a computer program. When the computer program runs on a computer, it enables the computer to execute any of the methods described above.

[0034] In the eleventh aspect, an embodiment of the present application provides a communication system, comprising a terminal device and an access network device in any of the above aspects. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] Figure 1 It is a schematic diagram of the architecture of a communication system provided in an embodiment of the present application;

[0036] Figure 2 is a schematic diagram of a user plane protocol stack provided in an embodiment of the present application;

[0037] Figure 3 It is a schematic diagram of a framework in which a MN and a SN support multiple bearers, provided in an embodiment of the present application;

[0038] Figure 4 It is a flowchart of a method for processing an SCG connection failure event in the prior art provided by an embodiment of the present application;

[0039] Figure 5 It is a flowchart of a method for processing an MCG connection failure event in the prior art provided by an embodiment of the present application;

[0040] Figure 6 It is a flow chart of a method for SCG deactivation event or activation event in the prior art provided by an embodiment of the present application;

[0041] Figure 7 It is a flowchart of a first data transmission processing method provided in an embodiment of the present application;

[0042] Figure 8 It is a schematic diagram of the architecture of MCG and SCG provided in an embodiment of the present application;

[0043] Fig. 9 It is a schematic diagram of another structure of MCG and SCG provided in an embodiment of the present application;

[0044] Fig.10 It is a flowchart of a second data transmission processing method provided in an embodiment of the present application;

[0045] Fig.11It is a flowchart of a third data transmission processing method provided in an embodiment of the present application;

[0046] Fig.12 It is a flowchart of a fourth data transmission processing method provided in an embodiment of the present application;

[0047] Fig.13 It is a structural schematic diagram of a data transmission processing device provided in an embodiment of the present application;

[0048] Fig.14 It is a structural diagram of another data transmission processing device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0049] The embodiments of the present application are described below in conjunction with the drawings in the embodiments of the present application.

[0050] The embodiments of the present application can be applied to a communication system using multiple radio access technologies (RATs) dual connectivity (MR-DC) and / or carrier aggregation (CA). In addition, the embodiments of the present application can also be applied to other communication systems that can send the same data packet through multiple transmission paths, without limitation.

[0051] Please refer to Figure 1 , Figure 1 (a) and Figure 1 (b) in FIG. 1 is a network architecture diagram of a communication system using MR-DC. Figure 1 As shown, the communication system of MR-DC may include a core network, a master node (MN), a secondary node (SN) and a terminal device. In the embodiment of the present application, MN may also be referred to as a master station, an anchor, a primary network device, a primary access network device, etc., and SN may also be referred to as a secondary station, a secondary network device, a secondary access network device, etc. The embodiment of the present application does not limit the names of MN and SN.

[0052] It should be understood that MN is a radio access network (RAN) device that provides the user plane and control plane protocol stack termination points of the wireless communication air interface for the terminal device. SN is also a RAN device that provides the user plane and control plane termination points of the wireless communication air interface for the terminal device. It should be noted that MN and SN can be RAN devices that support different wireless communication technologies, or they can be RAN devices that support the same wireless communication technology. Wireless communication technology may include, but is not limited to, global system for mobile communications (GSM), general packet radio service (GPRS), universal mobile telecommunications system (UMTS), code division multiple access (CDMA), wideband code division multiple access (WCDMA), time-division code division multiple access (TD-SCDMA), evolved universal terrsetrial radio access (E-UTRA), next generation wireless communication (NR), wireless local area network (WLAN) or future 5G (the fifth generation) wireless communication system.

[0053] In a communication system using MR-DC, the MN can communicate with the core network on the control plane and the data plane. The SN can communicate with the core network on the control plane through the MN. The SN can also Figure 1 As shown in (a) of FIG. 1 , the MN communicates with the core network on the data plane, or the SN can also communicate with the core network on the data plane as shown in FIG. Figure 1 As shown in (b) in the figure, when data plane communication is realized with the core network, there is no need to go through the MN.

[0054] It should be understood that the RAN device in the embodiments of the present application may also be referred to as an access network device, an access network device, etc., and may be referred to as an access network device hereinafter. For example, the access network device may be an access network device in a fifth generation mobile communication system (5th-generation, 5G), for example, a next generation base station (generation nodeB, gNB), or an access network device in a long term evolution (LongTerm Evolution, LTE) system, for example, an evolved node B (evolved nodeB, eNB), or a radio network controller (radio network controller, RNC), a node B (node ​​B, NB), a base station controller (base station controller, BSC), a base transceiver station (base transceiver station, BTS), a home base station (for example, home evolved node B, or home node B, HNB), a baseband unit (basebandunit, BBU), a transmitting and receiving point (transmitting and receiving point, TRP), a transmitting point (transmittingpoint, TP), a mobile switching center, a wireless fidelity (wireless fidelity, Wifi) access point (access point, AP), a wireless controller in a cloud radio access network (cloud radio access network, CRAN) scenario, a relay station, an access point, an access network device in a future mobile communication system, or a future evolved public mobile land network (public land Access network equipment in mobilenetwork (PLMN), etc.

[0055] It should be understood that the terminal device of the embodiment of the present application is a device with wireless transceiver function, which can be called terminal, user equipment (UE), mobile station (MS), mobile terminal (MT), access equipment, vehicle-mounted equipment, industrial control equipment, UE unit, UE station, mobile station, remote station, remote equipment, mobile device, UE terminal, wireless communication equipment, UE agent or UE device, etc. The terminal device can be fixed or mobile. It should be noted that the terminal device can support at least one wireless communication technology, such as LTE, NR, WCDMA, etc. For example, the terminal device may be a mobile phone, a tablet computer (pad), a desktop computer, a laptop computer, a PDA, a mobile internet device (MID), a wearable device, an all-in-one machine, a vehicle-mounted terminal, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal in industrial control, a wireless terminal in self driving, a wireless terminal in remote medical surgery, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a wearable device, a terminal device in a future mobile communication network, or a terminal device in a future evolved PLMN, etc.

[0056] In the embodiment of the present application, the communication system using the dual connection architecture includes but is not limited to the following four types, among which:

[0057] 1. EN-DC (E-UTRA NR DC).

[0058] EN-DC (E-UTRA NR DC) can also be called Option 3 series, that is, the core network is the evolved packet core (EPC), MN is the access network device in long term evolution (LTE), and SN is the access network device in NR. Take the access network device in LTE as eNB (ie MN) and the access network device in NR as gNB (ie SN) as an example. There is an X2 interface between eNB and gNB, at least a control plane connection, and there may also be a user plane connection; there is an S1 interface between eNB and EPC, at least a control plane connection, and there may also be a user plane connection; there is an S1-U interface between gNB and EPC, that is, there may only be a user plane connection.

[0059] 2. EN-DC (E-UTRA NR DC).

[0060] NE-DC is also called Option 4 series, that is, the core network is the 5G core network (5G core, 5GC), MN is the access network equipment in LTE, and SN is the access network equipment in NR. Take the access network equipment in LTE as eNB (ie MN) and the access network equipment in NR as gNB (ie SN) as an example. There is an Xn interface between eNB and gNB, at least a control plane connection, and there may also be a user plane connection; there is an NG interface between the eNB base station and 5GC, at least a control plane connection, and there may also be a user plane connection; there is an NG-U interface between gNB and 5GC, that is, there can only be a user plane connection.

[0061] 3. NG EN-DC (Next Generation E-UTRA NRDC).

[0062] NG EN-DC is also called Option 7 series, that is, the core network is 5GC, MN is the access network equipment in LTE, and SN is the access network equipment in NR. Take the access network equipment in LTE as eNB (ie SN) and the access network equipment in NR as gNB (ie MN) as an example. There is an Xn interface between gNB and eNB, at least a control plane connection, and there can also be a user plane connection; there is an NG interface between gNB and 5GC, at least a control plane connection, and there can also be a user plane connection; there is an NG-U interface between eNB and 5GC, that is, there can only be a user plane connection.

[0063] It should be understood that the above-mentioned EN-DC, NE-DC and NG EN-DC are all dual connections between access network equipment in LTE and access network equipment in NR, which can be referred to as dual connections between LTE and NR.

[0064] 4. NR-NR DC.

[0065] NR-NR DC can be understood as a dual connection between NR and NR, with the core network being 5GC, and both MN and SN being access network devices in NR (e.g., gNB). Taking the access network device in NR as gNB as an example, the interface between the primary gNB and the secondary gNB is an Xn interface, which has at least a control plane connection and may also have a user plane connection; there is an NG interface between the primary gNB and 5GC, which has at least a control plane connection and may also have a user plane connection; there is an NG-U interface between the secondary gNB and 5GC, which means that there can only be a user plane connection.

[0066] It should be understood that in a communication system using MR-DC or NR-NR DC, a terminal device can simultaneously access at least one access network device. When the terminal device accesses one access network device, the access network device is the MN of the terminal device. When the terminal device accesses two or more access network devices, one of the two or more access network devices is the MN of the terminal device, and the other one or more access network devices are the SN of the terminal device.

[0067] The air interface resources in the embodiment of the present application may include one or more cells provided by an access network device (such as MN or SN) to provide services for a terminal device. Among them, the one or more cells provided by MN for the terminal device may be referred to as a master cell group (MCG), and the one or more cells provided by SN for the terminal device may be referred to as a secondary cell group (SCG). Exemplarily, the access network device in LTE is eNB, and the access network device in NR is gNB. The MCGs in the above EN-DC, NE-DC, NG EN-DC and NR-NR DC are eNB, eNB, gNB, and master gNB, respectively, and the SCGs are gNB, gNB, eNB, and auxiliary gNB, respectively.

[0068] The NR wireless protocol stack is divided into two planes: user plane (UP) and control plane (CP). The control plane protocol stack is the protocol cluster used for the system's control signaling transmission, and the user plane protocol stack is the protocol cluster used for user data transmission. Compared with the LTE protocol stack, the NR user plane protocol stack has an additional service data adaptation protocol (SDAP) layer. The UE is used as the terminal device and the gNB is used as the access network device for example. Figure 2As shown in the figure, the user plane protocols are, from top to bottom: SDAP layer, packet data convergence protocol (PDCP) layer, radio link control (RLC) layer, media access control protocol (MAC) layer, and physical layer protocol (PHY) layer.

[0069] The SDAP layer is configured through radio resource control (RRC) signaling. The SDAP layer is responsible for mapping the quality of service (QoS) flow to the corresponding data radio bearer (DRB). One or more QoS flows can be mapped to the same DRB, and one QoS flow can only be mapped to one DRB.

[0070] The PDCP layer is responsible for compressing and decompressing the Internet Protocol (IP) header, transmitting user data and maintaining the sequence number (SN) of the radio bearer (used to indicate the order in which the data packet is sent), and processing the RRC messages on the control plane and the IP packets on the user plane. On the user plane, after the PDCP sublayer receives the IP data packet from the upper layer, it can perform header compression and encryption on the IP data packet and then submit it to the RLC sublayer. The PDCP sublayer can also provide the upper layer with in-order submission and duplicate packet detection functions based on the SN of the PDCP data packet. The basic process of the PDCP entity as the transmitter includes the following six steps, among which:

[0071] Step 1: Cache the received PDCP service data unit (SDU) in the PDCP transmission buffer, set a dedicated timeout timer (discardTimer) for the PDCP SDU, and assign a sequence number to each data packet in the order of arrival at the PDCP layer.

[0072] The PDCP SDU includes control plane data from the RRC layer or user plane data from the SDAP layer. The timeout timer is used to detect whether the PDCP SDU is successfully sent. When the preset duration of the timeout timer expires, or a status report (Status Report) indicating successful reception of the PDCP SDU is received, it can be determined that the PDCP SDU has been sent, and the PDCP entity needs to discard the PDCP SDU and the corresponding PDCP PDU.

[0073] Step 2: The PDCP entity performs header compression on the user plane data.

[0074] Step 2 is optional. The PDCP entity will only perform header compression on the user plane data, but will not perform header compression on the control plane data.

[0075] Step 3: The PDCP entity performs integrity protection on the control plane data or user plane data based on the integrity protection algorithm.

[0076] The PDCP entity performs integrity protection on the control plane data or user plane data and can generate a verification code called MAC-I for the receiving end to perform integrity verification. The control plane data is always integrity protected, and the integrity protection function of the user plane data is optional.

[0077] Step 4: The PDCP entity encrypts the control plane data or the user plane data.

[0078] Step 4 is optional. The PDCP entity encrypts the control plane data or the user plane data to ensure the security of data transmission between the sender and the receiver.

[0079] Step 5: Add the PDCP header and generate the PDCP PDU.

[0080] Step 6: Send PDCP PDU to the RLC layer.

[0081] When the terminal device changes from the connected state to the third state (i.e., inactive state), the PDCP entity will be suspended. For the PDCP entity as the transmitter, all saved PDCP PDUs will be discarded, and the transmitter variable (TX_NEXT) will be set to the initial value, i.e., 0. However, the PDCP entity as the transmitter will not discard the saved SDUs (hereinafter referred to as suspended PDCP SDUs), so that after the terminal device enters the connected state, these data packets can be given a chance to be transmitted, thereby avoiding data packet loss during the state transition process.

[0082] For the PDCP entity as the receiving end, the running reordering timer (t_Reordering) will be stopped and reset. The reordering timer is used to detect whether the PDCP PDU is successfully received. If the PDCP PDU is not received within the time specified by the reordering timer, the receiving end considers that the PDCP PDU has been lost. While the reordering timer is running, the PDCP entity as the receiving end waits for the arrival of out-of-order PDCP PDUs. When the reordering timer times out, it will no longer wait for the out-of-order PDCP PDUs, but will deliver the received PDCP PDUs to the upper layer in ascending order of SN numbers (i.e., the control plane data is delivered to the RRC layer, and the user plane data is delivered to the SDAP layer).

[0083] It can be understood that when the terminal device performs a suspension operation on the PDCP entity, the PDCP entity no longer transmits data. The PDCP entity as the sender will discard all saved PDCP PDUs, save the suspended PDCP SDU, and set the sender variables to initial values. After the terminal device enters the connected state, the PDCP SDU can be reprocessed to generate a PDCP PDU, and the data can be transmitted upward in a new order, which can avoid the loss of data packets during the state transition process. The PDCP entity as the receiving end will stop the running reordering timer and reset it, so that after the terminal device enters the connected state, it can be delivered to the upper layer in sequence according to the previous order. In summary, after the terminal device enters the connected state, the PDCP entity will transmit the untransmitted data, thereby improving the efficiency of data transmission.

[0084] The access network device can configure whether the PDCP layer of the radio bearer (RB) of the terminal device should copy the data of the PDCP entity and send the copied data through two or more different paths (such as two different RLC entities). Different RLC entities correspond to different logical channels. RLC can communicate with the PDCP layer through the service access point (SAP) and can also communicate with the MAC layer through logical channels. Each logical channel of each terminal device has an RLC entity.

[0085] The PDCP data replication function can be indicated by MAC layer control signaling (CE) to start (i.e., activate) or stop (i.e., deactivate). When configuring the PDCP data replication function of the RB, the access network device can configure whether the PDCP data replication function is started immediately after the configuration is completed. When the RLC entity is in the activated state, the PDCP entity can send data to the RLC entity.

[0086] The access network equipment can configure multiple signaling radio bearers (SRBs) for the terminal equipment, for example, SRB1 and SRB2 configured on the MCG, and SRB3 configured on the SCG. The split bearer in which PDCP terminates at the MN can also be called the MN terminated split bearer, which can be referred to as the MN bearer for short; the split bearer in which PDCP terminates at the SN can also be called the SN terminated split bearer, which can be referred to as the SN bearer for short. The bearer types of the PDCP data replication function can include two types: split bearer (also called split bearer) and duplicate bearer (duplicatebearer). Among them, the split bearer can be understood as a radio bearer that can be associated with two or more transmission paths, that is, the data on a split bearer can be transmitted through one or more transmission paths in the transmission path associated with the split bearer.

[0087] It should be noted that the maximum number of transmission paths that can be associated with a split bearer is related to the number of SNs to which the terminal device is connected. That is to say, in a multi-connection scenario, each of the two or more transmission paths associated with the same split bearer is associated with the air interface resources of different access network devices. For example, if the terminal device is connected to an MN and an SN, when a split bearer is associated with a first transmission path and a second transmission path, the first transmission path can be associated with the air interface resources of the MN, and the second transmission path can be associated with the air interface resources of the SN. For example, Figure 3 As shown, the terminal device can be connected to one MN and one SN, so the number of transmission paths associated with a split bearer is 2. For example, PDCP#3 can transmit data through RLC#3 or RLC#6. PDCP can separate the data to be transmitted into multiple sub-data, transmit part of the sub-data through the MN RLC in the MCG, and transmit the remaining sub-data through the SN RLC in the SCG.

[0088] For uplink split bearer, one PDCP entity is associated with at least two RLC entities of MCG and SCG. Whether the terminal device delivers the PDCP data to the RLC entity associated with MCG or the RLC entity associated with SCG depends on the uplink data threshold configured by the access network device. When the amount of data to be sent by the terminal device is greater than or equal to the uplink data threshold, the terminal device can decide to deliver the PDCP data to the RLC entity associated with MCG or the RLC entity associated with SCG. When the amount of data to be sent by the terminal device is less than the uplink data threshold, the terminal device can only deliver the PDCP data to the primary RLC entity. Among them, the primary RLC entity can be the RLC entity associated with MCG or the RLC entity associated with SCG, which is indicated by the access network device. If the sub-data packets of the same service are transmitted through the primary RLC entity and the secondary RLC entity respectively, the data transmission throughput is improved.

[0089] A duplicate bearer can be understood as duplicate data (for example, RRC messages, etc.) that can be transmitted on two or more transmission paths associated with a split bearer, thereby helping to improve the reliability of data transmission between access network equipment and terminal equipment.

[0090] In the NR user plane protocol stack, the RLC layer communicates with the PDCP layer (or RRC layer) through the RLC channel, and communicates with the MAC layer through the logical channel. RLC configuration is a logical channel-level configuration, and one RLC entity corresponds to only one logical channel of one terminal device. The data received by the RLC entity from the PDCP layer or sent to the PDCP layer is called RLC SDU (or PDCP PDU). The data received by the RLC entity from the MAC layer or sent to the MAC layer is called RLC PDU (or MAC SDU).

[0091] The RLC layer includes the transmission mode (transparent mode, TM), the acknowledged mode (acknowledged mode, AM) and the unacknowledged mode (unacknowledged mode, UM). It is mainly responsible for the segmentation / reassembly (segmentation / reassembly), reassembly of RLC SDU and discarding of reassembled RLC SDU in the acknowledged mode (acknowledged mode, AM) and unacknowledged mode (unacknowledged mode, UM); in the AM mode, it performs error correction, duplicate packet detection (duplicate detection), re-segmentation of RLC SDU segments and protocol error detection through automatic repeat-request (ARQ). In addition, the RLC layer can also be used to implement the transmission of the upper layer PDU and the reconstruction of the RLC layer.

[0092] When the terminal device performs the suspension operation of the RLC entity, the RLC entity no longer transmits data. The RLC entity as the transmitter will discard all saved RLC PDUs, save the suspended RLC SDUs, and set the transmitter variables to initial values. After the terminal device enters the connected state, the RLC SDU can be reprocessed to generate RLC PDUs, and the data can be transmitted upward in a new order, which can avoid the loss of data packets during the state transition process. The RLC entity as the receiving end will stop the running reordering timer and reset it, so that after the terminal device enters the connected state, it can be delivered to the upper layer in sequence according to the previous order. In summary, after the terminal device enters the connected state, the RLC entity can transmit the untransmitted data, thereby improving the efficiency of data transmission.

[0093] The MAC layer is mainly responsible for mapping, multiplexing and demultiplexing between logical channels and transport channels, reporting scheduling information, error correction through hybrid automatic repeat request (HARQ), priority management between users through dynamic scheduling, and logical channel priority management.

[0094] like Figure 3 As shown, after the user's QoS flow passes through the SDAP layer, the SDAP layer maps the QoS flow with the DRB to determine the bearer corresponding to the QoS flow, which can be one of the MCG bearer, SCG bearer or split bearer. Then it is sent to the MN or SN through the PDCP entity, RLC entity and MAC entity corresponding to the bearer.

[0095] When describing the embodiments of the present application, some concepts used in the following description are first explained.

[0096] (1) An MCG connection failure event and an SCG connection failure event occur.

[0097] In order to maintain the reliability of the communication link between the terminal device and the access network device, the terminal device will detect the signal quality of each communication link. In multi-connection mode, the terminal device will detect whether a connection failure event occurs in the link with each access network device. For example, the terminal device will detect whether a connection failure occurs in the link with the MCG, and whether a connection failure occurs in the link between the terminal device and the SCG. In an embodiment of the present application, the detection by the terminal device of a connection failure in the link between the MCG and the terminal device may be referred to as determining the occurrence of an MCG connection failure event, and the detection by the terminal device of a connection failure in the link between the SCG and the terminal device may be referred to as determining the occurrence of an SCG connection failure event, but the embodiment of the present application is not limited thereto. Determining the occurrence of an MCG connection failure event may also be referred to as detecting the occurrence of an MCG connection failure event. Determining the occurrence of an SCG connection failure event may also be referred to as detecting the occurrence of an SCG connection failure event.

[0098] The MCG connection failure event in the embodiment of the present application may include a connection failure of a link between a terminal device and a primary cell (Pcell) in the MCG or a special cell (SpCell) in the MCG, or a connection failure of links between the terminal device and all cells in the MCG. The SCG connection failure event in the embodiment of the present application may include a connection failure of a link between a terminal device and a secondary cell (Scell) in the SCG or a SpCell in the SCG, or a connection failure of links between the terminal device and all cells in the SCG.

[0099] Generally, an MCG connection failure event or an SCG connection failure event includes at least one of the following: radio link failure (RLF), hand over failure (HOF), integrity check failure, RRC reconfiguration failure, etc., which is not limited to the embodiments of the present application.

[0100] RLF includes the following four situations:

[0101] 1. The terminal device detects that the number of consecutive out-of-sync indications (out-of-sync) is higher than a threshold, or does not receive a synchronization indication (in-sync) within a preset time.

[0102] Among them, the out-of-sync indication can be the information reported by the terminal device when the channel quality of the physical downlink control channel (physical downlink control channel, PDCCH) or the physical downlink shared channel (physical downlink shared channel, PDSCH) is lower than a certain threshold within a time window. The synchronization indication can be the information reported by the terminal device when the channel instruction of PDCCH or PDSCH is higher than a certain threshold within a time window. It can be understood that the out-of-sync indication can be understood as poor channel quality, and the synchronization indication can be understood as good channel quality. When the terminal device detects that the number of consecutive out-of-sync indications is higher than a threshold, or no synchronization indication is received within a preset time period, it may indicate a wireless link failure.

[0103] 2. The terminal device detects that a random access problem occurs.

[0104] When a random access problem occurs, for example, when the number of random access failures is higher than a threshold, it can be considered that RLF occurs in the current communication link.

[0105] 3. The terminal device detects that the RLC retransmission has reached the maximum number of transmissions.

[0106] This application does not limit the maximum number of transmissions of RLC retransmissions. When an RLC SDU fails to be transmitted successfully after multiple transmissions, it can be considered that the current communication link has RLF.

[0107] 4. For unlicensed spectrum, continuous listen-before-talk (LBT) failures are detected.

[0108] For example, if a terminal device fails to seize a channel for multiple consecutive times, it can be considered that RLF occurs in the current communication link.

[0109] The reasons for HOF include but are not limited to the following: insufficient transmission resources, no network path (IPPATH) configured, wrong configuration of neighbor nodes in IPPATH, etc. After receiving the handover instruction, if the terminal device cannot successfully access the target cell within a given time, it can be considered HOF.

[0110] Integrity check failure means that the terminal device fails to perform integrity check on the SRB or DRB data packet configured by the access network device. When there is an integrity check failure, it is considered that the content of the data packet may have been tampered with by an attacker, so the current link is unreliable and the access network device needs to be notified.

[0111] RRC reconfiguration failure means that when the access network device sends an RRC reconfiguration message for configuring or reconfiguring MCG and / or SCG, the terminal device cannot perform configuration operations according to the configuration information in the RRC reconfiguration message. The RRC reconfiguration message includes but is not limited to the following: at least one configuration information does not match the terminal device capability, at least one configuration information indicates that the terminal identity information does not match the terminal device, etc.

[0112] Please refer to Figure 4 , Figure 4 FIG. 1 is a flow chart of a method for handling an SCG connection failure event in the prior art. Figure 4 As shown, the method includes the following steps S401 to S406, wherein:

[0113] S401: The terminal device detects an SCG connection failure event.

[0114] S402: The terminal device suspends the transmission link of the SCG.

[0115] Among them, the transmission link of SCG suspended by the terminal device includes all SRBs and DRBs carried by SCG. In the embodiment of the present application, the transmission link of SCG can be suspended by resetting the MAC entity of SCG. It can be understood that when the terminal device detects that an SCG connection failure event occurs, the transmission link of SCG is suspended, which can directly avoid using SCG to communicate with SN.

[0116] S403: The terminal device reports SCG failure information to the master node (MN).

[0117] Among them, the SCG failure information can be an RRC message, which may include the failure type of the SCG connection failure event, such as RLF, HOF, integrity check failure, RRC connection reconfiguration failure, etc., or continuous out-of-sync indications detected in RLF, or no synchronization indications received for a long time, or random access problems, or RLC retransmissions reaching the maximum number of transmissions, or continuous LBT failures, etc., which are not limited here.

[0118] Optionally, the SCG failure information may also carry a measurement result to facilitate the MN to make a decision. The measurement result may be a measurement result of at least one frequency point associated with the SCG, for example, a measurement result of a neighboring cell of the serving cell of the SCG at a given frequency point.

[0119] S404: The master node performs SCG failure recovery.

[0120] Among them, the MN can restore the communication link between the UE and the SCG by releasing the transmission link of the SCG, or triggering the switching process to change the primary cell of the SCG, etc. It can be understood that when the terminal device does not detect the MCG connection failure event, it can be determined that the air interface link of the MCG has no connection failure problem, so that the SCG failure recovery is performed through the MN corresponding to the MCG, which can improve the success rate of failure recovery.

[0121] S405: The master node sends SCG recovery information to the terminal device.

[0122] The SCG recovery information is used to indicate the recovery of the SCG connection failure event, or to indicate the terminal device to perform SCell change, etc., which is not limited here. The SCG recovery information can be an RRC message, such as an RRC reconfiguration message.

[0123] S406: The terminal device resumes the transmission link of the SCG.

[0124] Among them, the terminal device restores the transmission link of SCG, including restoring all SRBs and DRBs carried by SCG.

[0125] Optionally, after step S406, the method further includes: if the terminal device changes the SCG key, rebuilding the PDCP entity.

[0126] Optionally, after step S406, the method further includes: the terminal device reconstructing the RLC entity of the SCG.

[0127] Among them, the terminal device rebuilds the RLC entity of the SCG and discards all RLC data, including RLC SDU, RLC SDU segments and RLC PDU, so that the RLC state of the terminal device is consistent with that of the service cell of the new SCG.

[0128] After the terminal device suspends the transmission link of the SCG, the PDCP entity and RLC entity in the SCG still operate normally. For uplink data, the PDCP entity will process the data to be sent normally and deliver the PDCP PDU to the RLC entity of the SCG. The RLC entity of the SCG will also process the data normally and wait for the MAC layer to schedule and send it. However, due to the suspension of SCG transmission, the processed RLC layer data of the SCG cannot be sent in time, resulting in data transmission failure. In addition, when the RLC entity of the SCG is rebuilt, the terminal device will discard all RLC data, resulting in the loss of data that the RLC layer has started or has completed processing during the SCG failure recovery process.

[0129] The handling method of MCG connection failure events can also refer to the handling method of SCG connection failure events. In order to avoid the 90-130ms data interruption delay caused by the cell reselection and access process caused by triggering RRC reconstruction, and to avoid the signaling overhead caused by the access network equipment reconfiguring the MCG and SCG of the terminal device due to RRC reconstruction, the NR protocol introduces the MCG failure recovery mechanism. For details, please refer to Figure 5 , Figure 5 FIG. 1 is a flow chart of a method for handling an MCG connection failure event in the prior art. Figure 5 As shown, the method includes the following steps S501 to S507, wherein:

[0130] S501: The terminal device detects an MCG connection failure event.

[0131] S502: The terminal device suspends the transmission link of the MCG.

[0132] Among them, the transmission link of MCG suspended by the terminal device includes all SRBs and DRBs carried by MCG. In the embodiment of the present application, the transmission link of MCG can be suspended by resetting the MAC entity of MCG. It can be understood that when the terminal device detects the occurrence of MCG connection failure event, it suspends the transmission link of MCG, which can directly avoid using MCG to communicate with MN.

[0133] S503: The terminal device sends MCG failure information (MCG failure information) to the secondary node (SN).

[0134] Among them, the MCG failure information can be reported through the signaling radio bearer configured by the MN, and the signaling radio bearer can be a dedicated signaling bearer for transmitting RRC messages between the terminal device and the SN, such as SRB3, etc. The MCG failure information can be an RRC message, which can include the type of MCG connection failure event, such as RLF, HOF, integrity check failure, RRC connection reconfiguration failure, etc., or the detection of continuous out-of-sync indications in the RLF, or the failure to receive synchronization indications for a long time, or the occurrence of random access problems, or the RLC retransmission reaches the maximum number of transmissions, or continuous LBT failures, etc., which are not limited here. Optionally, the MCG failure information can also carry measurement results to facilitate the MN to make a decision. The measurement result can be the measurement result of at least one frequency point associated with the MCG, such as the measurement result of the neighboring cell of the MCG's service cell at a given frequency point. Optionally, it can also carry the measurement result of at least one frequency point associated with the SCG, such as the measurement result of the neighboring cell of the SCG's service cell at a given frequency point.

[0135] S504: The secondary node sends MCG failure information to the primary node (MN).

[0136] It can be understood that SN forwards the MCG failure information to MN.

[0137] S505: The master node performs MCG failure recovery.

[0138] Among them, the MN can restore the communication link between the terminal device and the MCG by releasing the transmission link of the MCG, or triggering the switching process to change the main cell of the MCG, etc.

[0139] S506: The master node sends MCG recovery information to the terminal device.

[0140] The MCG recovery information is used to indicate the recovery of the MCG connection failure event, or to indicate the terminal device to change the PCell, etc., which is not limited here. The MCG recovery information can be an RRC message, such as an RRC reconfiguration message.

[0141] S507: The terminal device resumes the transmission link of the MCG.

[0142] Among them, the terminal device restores the transmission link of MCG including restoring all SRBs and DRBs carried by MCG.

[0143] Optionally, after step S507, the method further includes: if the terminal device changes the key of the MCG, rebuilding the PDCP entity.

[0144] Optionally, after step S507, the method further includes: the terminal device reestablishing the RLC entity of the MCG.

[0145] Among them, the terminal device rebuilds the RLC entity of the MCG and discards all RLC data, including RLC SDU, RLC SDU segments and RLC PDU, so that the RLC state of the terminal device is consistent with that of the service cell of the new MCG.

[0146] It can be understood that after the terminal device suspends the transmission link of the MCG, the PDCP entity and RLC entity in the MCG still work normally. For uplink data, the PDCP entity will process the data to be sent normally and deliver the PDCP PDU to the RLC entity of the MCG. The RLC entity of the MCG will also process the data normally and wait for the MAC layer to schedule and send it. However, due to the suspension of MCG transmission, the processed RLC layer data of the MCG cannot be sent in time, resulting in data transmission failure. In addition, when the RLC entity of the MCG is rebuilt, the terminal device will discard all RLC data, resulting in the loss of data that the RLC layer has started or has completed processing during the MCG failure recovery process.

[0147] (2) MCG connection failure event recovery and SCG connection failure event recovery.

[0148] After MN performs SCG failure recovery on SCG, MN may send information indicating recovery of the SCG connection failure event (for example, the SCG recovery information described in step S405) to the terminal device. After MN performs MCG failure recovery on MCG, MN may send information indicating recovery of the MCG connection failure event (for example, the MCG recovery information described in step S506) to the terminal device. In an embodiment of the present application, when the terminal device receives information indicating recovery of the SCG connection failure event, it may be determined that the SCG connection failure event has been recovered, and when the terminal device receives information indicating recovery of the MCG connection failure event, it may be determined that the MCG connection failure event has been recovered.

[0149] (3) SCG deactivation event occurs and SCG deactivation event recovery occurs.

[0150] Under a dual (or multiple) connection architecture, the access network device controls the SCG to perform deactivation operations according to the network conditions or the needs of the terminal device. For example, when the data rate requirement of the terminal device changes (for example, the rate requirement changes from high to low), or considering the power consumption of the terminal device communicating with the access network device, the access network device allows the SCG to be deactivated. In other words, when the terminal device does not need a high data rate requirement, and / or the power consumption of the terminal device needs to be further reduced, the access network device can deactivate the configured SCG, so that the terminal device temporarily disconnects the communication link with the SCG and only maintains data communication through the MCG. Once the data rate requirement of the terminal device changes from low to high, the access network device can reactivate the SCG that has been in a deactivated state to restore the communication link between the terminal device and the SCG.

[0151] Please refer to Figure 6 , Figure 6 FIG. 1 is a flow chart of a method for deactivating or activating an SCG event in the prior art. Figure 6 As shown, the method comprises steps S601 and S602, wherein:

[0152] S601: The terminal device sends auxiliary information to the access network device.

[0153] Step S601 is optional, and the auxiliary information can be used to assist the access network device (hereinafter, the access network device in this application may be MN or SN, etc., which is not limited here) to determine whether the terminal device performs the operation of deactivating the SCG. The type of the auxiliary information may be at least one of an RRC message, a MAC message, or a physical layer message, etc., which is not limited here. This application also does not limit the form of the auxiliary information, which may include the following three forms, among which:

[0154] The first type is a data buffer report, which is used to indicate the amount of data to be sent by the current terminal device. The amount of data to be sent can be the amount of data to be sent by at least one logical channel group configured by the access network device for the terminal device, or the amount of data to be sent by all logical channel groups configured by the access network device for the terminal device. Among them, at least one logical channel group can be a logical channel group configured by the access network device, and the amount of data to be sent by the logical channel group can be obtained by configuring the access network device through a buffer status report (BSR).

[0155] The second type is the status indication of the amount of data to be sent, which is used to indicate the status of the amount of data to be sent of the current terminal device, for example, a high / medium / low indication, reflecting the status of the current amount of data to be sent.

[0156] The third type is power consumption status indication, which is used to indicate the power consumption status of the current terminal device or the expected power consumption level. For example, the current power consumption of the terminal device is high, or the current power consumption level is expected to be reduced.

[0157] S602: The access network device sends a deactivation instruction or an activation instruction to the terminal device.

[0158] In the embodiment of the present application, the information used to indicate that the SCG is in a deactivated state may be referred to as a deactivation SCG instruction, and the information used to indicate that the SCG is in an activated state may be referred to as an activation SCG instruction. That is, after the terminal device receives the deactivation SCG instruction, the SCG is deactivated. After the terminal device receives the activation SCG instruction, the SCG is activated.

[0159] In an embodiment of the present application, a terminal device receiving an SCG deactivation instruction sent from an access network device may be referred to as determining that an SCG deactivation event has occurred, and a terminal device receiving an SCG activation instruction sent from an access network device may be referred to as determining that an SCG deactivation event has recovered.

[0160] It should be noted that the access network device that sends the deactivation SCG instruction and the activation SCG instruction to the terminal device can be the MN or the SN. The access network devices that send the deactivation SCG instruction and the activation SCG instruction can be the same or different, and are not limited here. Figure 6 In the embodiment, the access network device that receives the auxiliary information and the access network device that sends the SCG deactivation instruction or the SCG activation instruction are the same access network device. In actual scenarios, they may also be different access network devices.

[0161] The types of the SCG deactivation instruction and the SCG activation instruction may be at least one of an RRC message, a MAC message (e.g., MAC CE) or a physical layer message (e.g., downlink control signaling (DCI)), etc., and are not limited here. The SCG deactivation instruction may include an SCG deactivation indication, for example, carrying a displayed information element to instruct the SCG to perform a deactivation operation. Optionally, the SCG deactivation indication may also carry at least one cell identifier or cell set identifier configured by the SCG, used to instruct at least one cell or cell set of the SCG to perform a deactivation operation or a sleep operation. The SCG activation instruction may include an SCG activation indication, for example, carrying a displayed information element to instruct the SCG to perform an activation operation. Optionally, the SCG activation indication may also carry at least one cell identifier or cell set identifier configured by the SCG, used to instruct at least one cell or cell set of the SCG to perform an activation operation.

[0162] However, in the existing mechanism, the processing method of SCG deactivation event and the processing method of SCG deactivation event recovery have not been defined. If the processing method of SCG connection failure event is referred to, the transmission link of SCG will be suspended, and the RLC layer data of SCG that has been processed cannot be sent in time, resulting in data transmission failure. If the processing method of SCG connection failure event recovery is referred to, the data that the RLC layer has started or has completed processing during the SCG failure recovery process will be lost.

[0163] (4) Target event.

[0164] In an embodiment of the present application, the target event may be the above-mentioned SCG connection failure event, MCG connection failure event or SCG deactivation event, or may be a connection failure event between an access network device and a terminal device in other multi-connection architectures, a deactivation event of a cell in a single access network device, etc., which is not limited here.

[0165] (5) The first cell group and the second cell group.

[0166] In an embodiment of the present application, the first cell group can be understood as a cell group that performs data transmission in a target event, or can be understood as a cell group that may be suspended. For example, the first cell group corresponding to an SCG connection failure event and an SCG deactivation event is SCG, and the first cell group corresponding to an MCG connection failure event is MCG. The second cell group and the first cell group correspond to different access network devices, that is, the first cell group and the second cell group correspond to different access network devices. For example, when the first cell group is SCG, the second cell group can be MCG; when the first cell group is MCG, the second cell group can be SCG.

[0167] (6) Target PDCP entity.

[0168] In the embodiment of the present application, the target PDCP entity may be all PDCP entities associated with the first cell group, for example, Figure 3 As shown, when the first cell group is MCG, the target PDCP entity may be at least one of PDCP#1, PDCP#2 or PDCP#3. When the first cell group is SCG, the target PDCP entity may be at least one of PDCP#4, PDCP#5 or PDCP#6. The target PDCP entity may also be a PDCP entity specified in the first cell group by signaling by an access network device (for example, MN or SN, etc.). The target PDCP entity may also be a PDCP entity of a specified bearer type in the first cell group, for example, the target PDCP entity is a split bearer or a duplicate bearer PDCP entity, or a PDCP entity of the same type as the target event, etc. The present application does not limit the target PDCP entity, nor does it limit the number of target PDCP entities. For example, as Figure 3 As shown, when the first cell group is an MCG, the target PDCP entity may be at least one of PDCP#1 or PDCP#3. When the first cell group is an SCG, the target PDCP entity may be at least one of PDCP#4 or PDCP#6.

[0169] (7) A first RLC entity and a second RLC entity.

[0170] In the embodiment of the present application, the first RLC entity may be all RLC entities associated with the first cell group, for example, Figure 3 As shown, when the first cell group is MCG, the first RLC entity may be at least one of RLC#1, RLC#2, RLC#3 or RLC#4. When the first cell group is SCG, the first RLC entity may be at least one of RLC#5, RLC#6, RLC#7 or RLC#8. The first RLC entity may also be an RLC entity specified by an access network device (e.g., MN or SN, etc.) through signaling in the first cell group, or an RLC entity corresponding to an SCG connection failure event or an MCG connection failure event. The first RLC entity may also be an RLC entity of a specified bearer type in the first cell group, for example, the first RLC entity is an RLC entity associated with a split bearer or a copy bearer for a target PDCP entity in the first cell group, or a type that is the same as the target event, etc. The present application does not limit the first RLC entity, and does not limit the number of first RLC entities. For example, as Figure 3As shown, when the first cell group is an MCG, the first RLC entity may be at least one of RLC#1 or RLC#3. When the first cell group is an SCG, the first RLC entity may be at least one of RLC#5 or RLC#8.

[0171] In the embodiment of the present application, the RLC entity in the second cell group used to transmit data of the target PDCP entity may be referred to as a second RLC entity. The second RLC entity may include any RLC entity in the second cell group, for example, Figure 3 As shown, when the first cell group is MCG, the second RLC entity may be RLC#5, RLC#6, RLC#7 or RLC#8. When the first cell group is SCG, the second RLC entity may be RLC#1, RLC#2, RLC#3 or RLC#4. The second RLC entity access network device (e.g., MN or SN, etc.) copies the RLC entity associated with the bearer in the second cell group for the target PDCP entity, or may include the access network device separating the RLC entity associated with the bearer in the second cell group for the target PDCP entity. Figure 3 As shown, when the first cell group is MCG, the second RLC entity may be RLC#6. When the first cell group is SCG, the second RLC entity may be RLC#4. The second RLC entity may also include an access network device (e.g., MN or SN, etc.) as an RLC entity associated with the bearer corresponding to the target event in the second cell group, that is, the second RLC entity is used to carry data in the second cell group that is different from the access network device corresponding to the first cell group. Figure 3 As shown, when the target event is SCG connection failure, or SCG deactivation event, the second RLC entity is the RLC entity associated with the MCG bearer, and the second RLC entity can be RLC#1 or RLC#3; when the target event is MCG connection failure, the second RLC entity is the RLC entity associated with the SCG bearer, and the second RLC entity can be RLC#5 or RLC#8.

[0172] When the second RLC entity is an access network device that copies the RLC entity associated with the target PDCP entity in the second cell group, and the second RLC entity is in an activated state, the terminal device can control the target PDCP entity to send data to the RLC entity, and can transmit the copied data through the first RLC entity and the second RLC entity respectively, thereby improving data transmission reliability.

[0173] When the second RLC entity is an access network device that is a target PDCP entity and separates the RLC entity associated with the bearer in the second cell group, the terminal device can directly control the target PDCP entity to send data to the second RLC entity without considering the uplink data threshold. That is to say, when the amount of data to be sent by the terminal device is greater than or equal to the uplink data threshold, or when the amount of data to be sent by the terminal device is less than the uplink data threshold, the target PDCP entity is controlled to send data to the main RLC entity. It is also possible to control the target PDCP entity to send data to the main RLC entity when the amount of data to be sent by the terminal device is less than the uplink data threshold. That is to say, when the second RLC entity is an access network device that is a target PDCP entity and separates the RLC entity associated with the bearer in the second cell group, and the second RLC entity is the main RLC entity, the terminal device can control the target PDCP entity to send data to the second RLC entity. When the first RLC entity is an access network device that is a RLC entity associated with the bearer in the first cell group, and the first RLC entity is the main RLC entity, the terminal device can control the target PDCP entity to send data to the first RLC entity. The main RLC entity and the uplink data threshold are specified by the access network device. If the sub-data packets of the same service are transmitted through the first RLC entity and the second RLC entity respectively, the data transmission throughput is improved.

[0174] (8)Target entity.

[0175] In an embodiment of the present application, the target entity may be a target PDCP entity or a first RLC entity in the first cell group. The present application does not limit the number of target entities, which may be multiple target PDCP entities or multiple first RLC entities, or a target PDCP entity and a first RLC entity.

[0176] (9) First indication information.

[0177] In an embodiment of the present application, after the terminal device determines that a target event has occurred, a first indication message may be sent to the target entity, and the first indication message is used to indicate the occurrence of the target event, or to indicate that the target entity does not perform data transmission based on the first cell group, or to indicate that the target entity performs data transmission based on the second cell group. The present application does not limit the operation of the target entity not performing data transmission based on the first cell group, and the target entity may not transmit the data when the target entity receives the data, or may suspend the target entity so that the target entity does not receive data and does not send data. The present application does not limit the operation of the target entity performing data transmission based on the second cell group, and may instruct the target PDCP entity to perform data transmission based on the second RLC entity. It can be understood that after the target entity receives the first indication message, it can be directly controlled by the terminal device according to the first indication message, thereby improving the processing efficiency of the target entity.

[0178] (10) Second indication information.

[0179] In an embodiment of the present application, after the terminal device determines that a target event has occurred, a second indication message may be sent to the access network device, and the second indication message is used to indicate the occurrence of the target event, the type of the target event, or the measurement result of the terminal device. Among them, the type of the target event may be one of an SCG connection failure event, an MCG connection failure event, or an SCG deactivation event, or may be a type of connection failure caused by an SCG connection failure event or an MCG connection failure event (for example, RLF, HOF, integrity check failure, RRC connection reconfiguration failure, etc., or a continuous out-of-sync indication is detected in RLF, or a synchronization indication is not received for a long time, or a random access problem occurs, or RLC retransmission reaches the maximum number of transmissions, or a continuous LBT failure, etc.), or may be a type of SCG deactivation event (for example, a reduction in data rate requirements, a reduction in power consumption requirements, etc.), etc., which is not limited here. The measurement results can refer to the description of step S403 and step S503, which will not be repeated here. It can be understood that the access network device can determine the occurrence of the target event and the relevant information of the target event in the terminal device through the second indication message, which facilitates the access network device to process the target event and improves the processing efficiency.

[0180] The present application does not limit the access network device that receives the second indication information. When the target event is an SCG connection failure event, a transmission failure may occur when the terminal device sends information to the SN. Therefore, the access network device may be an MN to notify the SN to perform MCG failure recovery. When the target event is an MCG connection failure event, a transmission failure may occur when the terminal device sends information to the MN. Therefore, the access network device may be an SN, and the second indication information is forwarded to the MN through the SN to notify the MN to perform MCG failure recovery. When the target event is an SCG deactivation event, the access network device may be an MN or an SN.

[0181] (11) Third indication information.

[0182] In an embodiment of the present application, after the access network device determines that the target event has been restored, a third indication message may be sent to the terminal device, and the third indication message is used to indicate that the target event has been restored. The present application does not limit the access network device that sends the third indication message. When the target event is an SCG connection failure event or an MCG connection failure event, the MN performs failure recovery. Therefore, the access network device is an MN. When the target event is an SCG deactivation event, the access network device may be an MN or an SN. Optionally, the access network device that receives the auxiliary information sent by the terminal device sends the third indication message to the terminal device. It can be understood that after receiving the third indication message, the terminal device can determine that the target event has been restored, thereby controlling the target entity to use the transmission resources of the first cell group corresponding to the target event for data transmission, thereby avoiding data loss.

[0183] (12) Fourth indication information.

[0184] In an embodiment of the present application, after the terminal device determines that the target event is restored, a fourth indication message may be sent to the target entity, and the fourth indication message is used to indicate the recovery of the target event, or to indicate the target entity to perform data transmission based on the first cell group. The present application does not limit the operation of the target entity to perform data transmission based on the first cell group. Data transmission can be performed when the target entity receives data, or the target entity can be restored so that the target entity receives data and sends data. The fourth indication message may also be used to indicate the operation of the target entity to perform data transmission based on the second cell group. The present application does not limit the operation of the target entity to perform data transmission based on the second cell group, and the target PDCP entity may be indicated to perform data transmission based on the second RLC entity. It can be understood that after the target entity receives the fourth indication message, it can be directly controlled by the terminal device according to the fourth indication message, thereby improving the processing efficiency of the target entity. If the target entity can perform data transmission based on the first cell group and the second cell group, the data transmission efficiency can be further improved.

[0185] The embodiment of the present application provides a data transmission processing method. When the terminal device determines that a target event has occurred, the target entity in the first cell group corresponding to the target event is controlled not to perform data transmission based on the first cell group. In other words, by not using the transmission resources of the first cell group corresponding to the target event for data transmission, the first cell group can be prevented from communicating with the access network device, thereby avoiding the occurrence of data transmission failure. In addition, when it is determined that the target event has been restored, the target entity is controlled to perform data transmission based on the first cell group, that is, by using the transmission resources corresponding to the target event for data transmission, data loss can be avoided.

[0186] Please refer to Figure 7 , Figure 7 1 is a flow chart of the first data transmission processing method provided in the embodiment of the present application. Figure 7 As shown, the method includes the following steps S701 and S702, wherein:

[0187] S701: The terminal device determines that a target event occurs.

[0188] Among them, the target event includes an SCG connection failure event, an MCG connection failure event or an SCG deactivation event, or it may be an event in which a connection failure occurs between an access network device and a terminal device in other multi-connection architectures, a deactivation event occurs in a cell in a single access network device, etc. When the terminal device detects an SCG connection failure or an MCG connection failure, it can be determined that an SCG connection failure event or an MCG connection failure event has occurred. When the terminal device receives a deactivation instruction sent by the access network device, it can be determined that an SCG deactivation event has occurred. The target event and the method for determining the occurrence of the target event can be referred to the aforementioned description and will not be repeated here.

[0189] In a possible example, after step S701, the method further includes: the terminal device sends second indication information to the access network device.

[0190] Among them, the second indication information is used to indicate the occurrence of the target event, the type of target event or the measurement result of the terminal device, which can be referred to the above description and will not be repeated here. When the target event is an SCG connection failure event, the MN can restore the communication link between the terminal device and the SCG by releasing the transmission link of the SCG, or triggering the switching process to change the primary cell of the SCG, etc. When the target event is an MCG connection failure event, the MN can restore the communication link between the terminal device and the SCG by releasing the transmission link of the MCG, or triggering the switching process to change the primary cell of the MCG, etc.

[0191] S702: The terminal device controls the target entity not to transmit data based on the first cell group corresponding to the target event.

[0192] The target entity and the first cell group corresponding to the target event can refer to the above description and will not be repeated here. The target entity does not perform data transmission based on the first cell group corresponding to the target event. It can be understood that the target PDCP entity does not send uplink data to the first RLC entity, or the first RLC entity does not send uplink data to the MAC entity in the first cell group. In other words, the transmission resources of the first cell group corresponding to the target event are not used for data transmission. For example, Figure 8As shown, if the target event is an MCG connection failure event, PDCP#1 does not send uplink data to RLC#1 in MCG, or RLC#1 does not send uplink data to MAC#1 in MCG. If the target event is an SCG connection failure event or an SCG deactivation event, PDCP#2 does not send uplink data to RLC#2 in SCG, or RLC#2 does not send uplink data to MAC#2 in SCG.

[0193] It should be noted that, in addition to the second RLC entity being controlled by the target PDCP entity to perform data transmission, the second RLC entity can also perform data transmission based on the source PDCP entity. Figure 8 As shown, when the second RLC entity is RLC#2, the second RLC entity can transmit uplink data from PDCP#1 and uplink data from PDCP#2.

[0194] Understandably, Figure 7 In the method shown, when the terminal device determines that a target event has occurred, the target entity in the first cell group corresponding to the target event is controlled not to perform data transmission based on the first cell group. In other words, by not using the transmission resources of the first cell group corresponding to the target event for data transmission, the first cell group can be prevented from communicating with the access network device, thereby avoiding the occurrence of data transmission failure.

[0195] In a possible example, after step S702, the target entity is a target PDCP entity, and the method further includes: the terminal device controls the target PDCP entity to send data to a second RLC entity in a second cell group, and the access network devices corresponding to the second cell group and the first cell group are different.

[0196] Among them, the second cell group can refer to the above, which will not be repeated here. The second RLC entity may include any RLC entity in the second cell group, and may specifically include an access network device (for example, MN or SN, etc.) as an RLC entity associated with the bearer corresponding to the target event in the second cell group, or may include an access network device that copies the bearer-associated RLC entity in the second cell group for the target PDCP entity, or may include an access network device that separates the bearer-associated RLC entity in the second cell group for the target PDCP entity, etc. In a possible example, the second RLC entity includes an access network device that copies the bearer-associated RLC entity in the second cell group for the target PDCP entity, and in response to the second RLC entity being in an activated state, the terminal device controls the target PDCP entity to send data to the second RLC entity.

[0197] When the second RLC entity is in an activated state, the terminal device can directly control the target PDCP entity to send data to the second RLC entity. When the second RLC entity is in an inactive state, the terminal device first configures the second RLC entity to be in an activated state, and then controls the target PDCP entity to send data to the second RLC entity.

[0198] The second RLC entity includes an RLC entity associated with the access network device as the target PDCP entity separated bearer in the second cell group. As mentioned above, when the amount of data to be sent by the terminal device is greater than or equal to the uplink data threshold, the terminal device can decide to submit the PDCP data to the RLC entity associated with the MCG or the RLC entity associated with the SCG. It can be understood that the terminal device does not consider the uplink data threshold and directly controls the target PDCP entity to send data to the second RLC entity. When the amount of data to be sent by the terminal device is less than the uplink data threshold, the terminal device can only submit the PDCP data to the main RLC entity. In other words, when considering the uplink data threshold, the terminal device sends data to the main RLC entity. Based on this, in a possible example, in response to the second RLC entity being the main RLC entity, the terminal device controls the target PDCP entity to send data to the second RLC entity.

[0199] It can be understood that when the second RLC entity is the primary RLC entity, the terminal device can directly control the target PDCP entity to send data to the second RLC entity. When the second RLC entity is not the primary RLC entity, the terminal device first modifies the second RLC entity to be the primary RLC entity, and then controls the target PDCP entity to send data to the second RLC entity.

[0200] In a possible example, the second RLC entity includes an RLC entity associated with a bearer corresponding to a target event in a second cell group of an access network device, and the terminal device controls the target PDCP entity to send data to the second RLC entity.

[0201] When the second RLC entity accesses the RLC entity associated with the bearer corresponding to the target event in the second cell, the second RLC entity can also transmit data corresponding to the target PDCP entity, and the terminal device can control the target PDCP entity to send data to the second RLC entity.

[0202] For example, Fig. 9 As shown, when an MCG connection failure event occurs, the target PDCP entity is PDCP#1, the first RLC entity is RLC#1, and the second RLC entity is RLC#2. In this way, PDCP#1 may transmit uplink data based on RLC#2 instead of RLC#1.

[0203] Through the above three examples, the target PDCP entity can send data to the second RLC entity, so that when the target PDCP entity does not send data to the first RLC entity, the data of the target PDCP entity is transmitted based on the second RLC entity, thereby avoiding data transmission interruption in the target PDCP entity and improving data transmission efficiency.

[0204] In a possible example, before step S702, the method further includes: the terminal device sends first indication information to the target entity.

[0205] The first indication information is used to indicate the occurrence of a target event, or to indicate that the target entity does not perform a data transmission operation based on the first cell group, or to indicate that the target entity performs a data transmission operation based on the second cell group, etc., which can be referred to the above description and is not limited here. It can be understood that after the target entity receives the first indication information, it can be directly controlled by the terminal device according to the first indication information, thereby improving the processing efficiency of the target entity.

[0206] In a possible example, after step S701, the method further includes: the terminal device suspends the transmission link of the first cell group.

[0207] In a possible example, after step S701, the method further includes: the terminal device suspends or deactivates the preconfigured authorization resources configured on the first cell group. The preconfigured authorization resources are semi-static transmission resources configured by the access network device. The preconfigured authorization resources can take effect after the access network device configures the semi-static resources, or after the semi-static resources are activated through the PDCCH. After suspending or deactivating the preconfigured authorization resources, the terminal device cannot use the preconfigured authorization resources to perform data transmission with the access network device, thereby avoiding data transmission based on the first cell group.

[0208] It can be understood that when the target event is determined to have occurred, the transmission link of the first cell group is suspended, which can prevent the target entity from sending uplink data to the first cell group and prevent the first cell group from receiving the uplink data, further avoiding data transmission failure.

[0209] Optionally, the target event is an SCG deactivation event. After step S701, the method further includes: the terminal device stops or suspends monitoring of the PDCCH on the SCG.

[0210] Among them, the terminal device stops or suspends monitoring the PDCCH on the SCG, including but not limited to the SCell or the primary secondary cell (PSCell). It can be understood that after the SCG deactivation event occurs, the channel quality on the SCG does not need to be paid attention to, so the terminal device can stop or suspend monitoring the PDCCH on the SCG to save power consumption.

[0211] Optionally, the target event is an SCG deactivation event. After step S701, the method further includes: the terminal device resetting the MAC entity of the SCG.

[0212] Among them, the terminal device resets the MAC entity of the SCG, including but not limited to stopping all running MAC layer timers, stopping the ongoing random access process, clearing the cache corresponding to the HARQ, etc., so that the terminal device can be consistent with the access network device.

[0213] Optionally, the target event is an SCG deactivation event. After step S701, the method further includes: the terminal device continues to run a synchronization timer (time alignment timer, TAT) associated with the SCG.

[0214] Among them, TAT is used for the terminal equipment to maintain the uplink synchronization timing with the access network equipment. If TAT times out, the terminal equipment considers that it is out of sync with the access network equipment uplink, so that the terminal equipment can continue to maintain uplink synchronization and is not affected by SCG failure.

[0215] Optionally, the target event is an SCG deactivation event. After step S701, the method further includes: the terminal device deactivates one or more cells on the SCG.

[0216] Among them, the terminal device deactivates one or more cells on the SCG, which may be to deactivate all secondary cells on the SCG, or to deactivate all cells on the SCG, including the primary cell and the secondary cell. After deactivating one or more cells, the terminal device cannot send or receive data in the cell, so that the terminal device can stop monitoring the PDCCH on the cell, which is convenient for saving power consumption.

[0217] Please refer to Fig.10 , Fig.10 It is a flow chart of the second data transmission processing method provided in an embodiment of the present application.

[0218] like Fig.10 As shown, the method includes the following steps S1001 and S1002, wherein:

[0219] S1001: The terminal device determines that a target event occurs.

[0220] Among them, step S1001 can refer to the description of step S701, which will not be repeated here.

[0221] S1002: The terminal device suspends the target entity.

[0222] This application does not limit the steps for suspending the target entity. After the target entity is suspended, the target entity no longer transmits data.

[0223] It can be understood that when it is determined that the target event occurs, if the target PDCP entity is suspended, the target PDCP entity can be prevented from sending data to the first RLC entity. If the first RLC entity is suspended, the first RLC entity can be prevented from sending data to the MAC entity in the first cell group. In this way, the target entity can be prevented from transmitting uplink data, thereby avoiding the use of the first cell group to communicate with the access network device corresponding to the first cell group, and avoiding the occurrence of data transmission failure.

[0224] For example, Figure 8 As shown, when an MCG connection failure event occurs, PDCP#1 or RLC#1 can be suspended, which can avoid using PDCP#1 to transmit uplink data to RLC#1, or avoid using RLC#1 to transmit uplink data to MAC#1.

[0225] In a possible example, the target entity is the first RLC entity, and the method may further include: the terminal device suspends the target PDCP entity. That is, when it is determined that the target event occurs, the first RLC entity and the target PDCP entity are suspended, which can prevent the target PDCP entity from sending uplink data to the first RLC entity, and prevent the first RLC entity from sending uplink data, further avoiding the occurrence of data transmission failure.

[0226] In a possible example, the target entity is a target PDCP entity, and the method may further include: the terminal device suspends the first RLC entity. That is, when it is determined that the target event occurs, the target PDCP entity and the first RLC entity are suspended, which can prevent the target PDCP entity from sending uplink data to the first RLC entity, and prevent the first RLC entity from sending uplink data, further avoiding the occurrence of data transmission failure.

[0227] For example, Figure 8 As shown, when an MCG connection failure event occurs, PDCP#1 and RLC#1 can be suspended, thereby avoiding the use of PDCP#1 to transmit uplink data to RLC#1, and avoiding the use of RLC#1 to transmit uplink data to MAC#1.

[0228] exist Fig.10In the method shown, when the terminal device determines that the target event occurs, the target entity is suspended, so that the target entity does not perform data transmission based on the first cell group by suspending the target entity. In other words, the transmission resources of the first cell group corresponding to the target event are not used for data transmission, which can avoid the first cell group from communicating with the access network device, thereby avoiding the situation where data transmission fails.

[0229] In a possible example, the target entity is a first RLC entity, and the method may further include: the terminal device discards the RLC SDU that has been partially sent in the first RLC entity.

[0230] The partially sent RLC SDU refers to the segment of the RLC SDU sent by the RLC before the target event occurs. For example, RLC SDU#1 includes two segments, RLC SDU segment #1 and RLC SDU segment #2. If RLC SDU segment #1 is sent before the target event occurs, both RLC SDU segment #1 and RLC SDU #2 are discarded. It can be understood that before the target event occurs, if the segment of the RLC SDU has been sent, the RLC SDU is also discarded. After the target event is restored, the terminal device can reprocess the RLC SDU to avoid data loss.

[0231] In a possible example, the target entity is the first RLC entity, and the method may further include: the terminal device discards all saved RLC PDUs, but does not discard RLC SDUs. It can be understood that the terminal device discards the data packets that have been processed in the RLC layer, that is, RLC PDUs, but the terminal device saves the original data received by the RLC layer, that is, RLC SDUs, and the RLC SDUs can be called suspended RLC SDUs, so that after the target event is restored, the terminal device can reprocess the RLC SDUs to avoid data discard.

[0232] In a possible example, the target entity is the first RLC entity, and the method may further include: the terminal device stops and resets the running RLC layer timer (including the RLC layer reassembly timer (t-Reassembly), which is used to wait for at least one segment of the unreceived complete RLC SDU or the complete RLC SDU). In this way, the RLC state of the terminal device and the service cell of the access network device are consistent, which can improve the probability of successful data transmission, and after the target event is restored, the terminal device can continue to run the RLC layer timer.

[0233] In a possible example, the target entity is the first RLC entity, and the method may further include: the terminal device sets the state variable of the RLC layer to an initial value. In this way, the RLC state of the service cell of the terminal device and the access network device remains consistent.

[0234] In a possible example, the target entity is a target PDCP entity, and the method further includes: the terminal device discards all stored PDCP PDUs of the target PDCP entity and saves the suspended PDCP SDUs. In this way, after the target event is restored, the terminal device can reprocess the PDCP SDUs to avoid data discarding.

[0235] In a possible example, the target entity is a target PDCP entity, and the method may further include: the terminal device stops and resets the timer of the running PDCP layer (including the reassembly timer (t-Reassembly) of the PDCP layer). In this way, the PDCP state of the service cell of the terminal device and the access network device is consistent, which can improve the probability of successful data transmission, and after the target event is restored, the terminal device can continue to run the reordering timer.

[0236] In a possible example, the target entity is a target PDCP entity, and the method may further include: the terminal device sets the state variable of the PDCP layer to an initial value. In this way, the PDCP state of the serving cell of the terminal device and the access network device remains consistent.

[0237] In a possible example, before step S1002, the method further includes: the terminal device sends first indication information to the target entity. It can be understood that after the target entity receives the first indication information, it can be directly controlled by the terminal device according to the first indication information, thereby improving the processing efficiency of the target entity.

[0238] In a possible example, after step S1001, the method further includes: the terminal device suspends the transmission link of the first cell group. It can be understood that when it is determined that the target event occurs, the transmission link of the first cell group is suspended, which can prevent the target entity from sending uplink data to the first cell group and prevent the first cell group from receiving the uplink data, further avoiding the occurrence of data transmission failure.

[0239] In a possible example, after step S1001, the method further includes: the terminal device suspends or deactivates the preconfigured authorization resources configured on the first cell group. The preconfigured authorization resources are semi-static transmission resources configured by the access network device. The preconfigured authorization resources can take effect after the access network device configures the semi-static resources, or after the semi-static resources are activated through the PDCCH. After suspending or deactivating the preconfigured authorization resources, the terminal device cannot use the preconfigured authorization resources to perform data transmission with the access network device, thereby avoiding data transmission based on the first cell group.

[0240] Optionally, the target event is an SCG deactivation event, and after step S1001, the method further includes: the terminal device stops or suspends monitoring the PDCCH on the SCG. It can be understood that after the SCG deactivation event occurs, the channel quality on the SCG does not need to be paid attention to, so the terminal device can stop or suspend monitoring the PDCCH on the SCG, which is convenient for saving power consumption.

[0241] Optionally, the target event is an SCG deactivation event. After step S1001, the method further includes: the terminal device resets the MAC entity of the SCG.

[0242] Among them, the terminal device resets the MAC entity of the SCG, including but not limited to stopping all running MAC layer timers, stopping the ongoing random access process, clearing the cache corresponding to the HARQ, etc., so that the terminal device can be consistent with the access network device.

[0243] Optionally, the target event is an SCG deactivation event. After step S1001, the method further includes: the terminal device continues to run a synchronization timer (time alignment timer, TAT) associated with the SCG.

[0244] Among them, TAT is used for the terminal equipment to maintain the uplink synchronization timing with the access network equipment. If TAT times out, the terminal equipment considers that it is out of sync with the access network equipment uplink, so that the terminal equipment can continue to maintain uplink synchronization and is not affected by SCG failure.

[0245] Optionally, the target event is an SCG deactivation event. After step S1001, the method further includes: the terminal device deactivates one or more cells on the SCG.

[0246] Among them, the terminal device deactivates one or more cells on the SCG, which may be to deactivate all secondary cells on the SCG, or to deactivate all cells on the SCG, including the primary cell and the secondary cell. After deactivating one or more cells, the terminal device cannot send or receive data in the cell, so that the terminal device can stop monitoring the PDCCH on the cell, which is convenient for saving power consumption.

[0247] Please refer to Fig.11 , Fig.11 is a flow chart of a third data transmission processing method provided in an embodiment of the present application. Fig.11 As shown, the method includes the following steps S1101 to S1103, wherein:

[0248] S1101: The access network device sends third indication information to the terminal device.

[0249] The access network device sends the third indication information to the terminal device, which can be understood as the terminal device receiving the third indication information from the access network device. In an embodiment of the present application, the third indication information is used to indicate the recovery of the target event. When the target event is an SCG connection failure event or an MCG connection failure event, the access network device in step S801 is MN, that is, the third indication information can be the SCG recovery information sent by MN to the terminal device in step S405, or the MCG recovery information sent by MN to the terminal device in step S506. When the target event is an SCG deactivation event, the access network device in step S801 can be MN or SN, that is, the third indication information can be the SCG activation instruction sent by MN or SN to the terminal device. The target event and the third indication information can refer to the above description and will not be repeated here.

[0250] S1102: The terminal device determines target event recovery based on the third indication information.

[0251] S1103: The terminal device controls the target entity to transmit data based on the first cell group corresponding to the target event.

[0252] The target entity and the first cell group corresponding to the target event can refer to the above description and will not be repeated here. The target entity transmits data based on the first cell group corresponding to the target event, which can be understood as the target PDCP entity sending uplink data to the first RLC entity, or the first RLC entity sending uplink data to the MAC entity in the first cell group. In other words, the transmission resources of the first cell group corresponding to the target event are used for data transmission. For example, Figure 8 As shown, if the target event is an MCG connection failure event, PDCP#1 sends uplink data to RLC#1 in MCG, or RLC#1 sends uplink data to MAC#1 in MCG. If the target event is an SCG connection failure event or an SCG deactivation event, PDCP#2 sends uplink data to RLC#2 in SCG, or RLC#2 sends uplink data to MAC#2 in SCG.

[0253] Understandably, Fig.11In the method shown, when the terminal device receives the third indication information sent from the access network device, it can be determined that the target event is restored, and the target entity in the first cell group corresponding to the target event can be controlled to perform data transmission based on the first cell group. That is to say, after the terminal device receives the third indication information, it can be determined that the target event is restored, so that the target entity can be controlled to use the transmission resources of the first cell group corresponding to the target event for data transmission, which can avoid data loss.

[0254] In a possible example, the target entity is a target PDCP entity, and the method further includes: the terminal device controls the target PDCP entity to send data to a second RLC entity in a second cell group, and the second cell group and the first cell group correspond to different access network devices. It can be understood that by transmitting data for the target PDCP entity at the same time by the first RLC entity and the second RLC entity, data transmission efficiency can be improved.

[0255] In one possible example, the target entity is a target PDCP entity, and the first RLC entity includes an access network device that copies the RLC entity associated with the target PDCP entity in the first cell group. In response to the first RLC entity being in an activated state, the terminal device controls the target PDCP entity to send data to the first RLC entity.

[0256] As mentioned above, when the first RLC entity is an access network device (for example, MN or SN, etc.) that replicates the RLC entity associated with the target PDCP entity in the first cell group, and the first RLC entity is in an activated state, the terminal device can control the target PDCP entity to send data to the first RLC entity. When the first RLC entity is in an inactive state, the terminal device first configures the first RLC entity to be in an activated state, and then controls the target PDCP entity to send data to the first RLC entity.

[0257] Optionally, the second RLC entity includes an access network device that replicates the RLC entity associated with the bearer in the second cell group for the target PDCP entity, and in response to the second RLC entity being in an activated state, the terminal device controls the target PDCP entity to send data to the second RLC entity. That is, when the second RLC entity access network device (e.g., MN or SN, etc.) replicates the RLC entity associated with the bearer in the second cell group for the target PDCP entity, and the second RLC entity is also in an activated state, the terminal device can transmit uplink data through the first RLC entity and the second RLC entity, thereby improving data transmission efficiency.

[0258] The target entity is the target PDCP entity, and the first RLC entity includes an RLC entity associated with the target PDCP entity separated by the access network device in the first cell group. As mentioned above, when the amount of data to be sent by the terminal device is greater than or equal to the uplink data threshold, the terminal device can decide to submit the PDCP data to the RLC entity associated with the MCG or the RLC entity associated with the SCG. It can be understood that the terminal device does not consider the uplink data threshold and directly controls the target PDCP entity to send data to the first RLC entity. When the amount of data to be sent by the terminal device is less than the uplink data threshold, the terminal device can only submit the PDCP data to the main RLC entity. In other words, when considering the uplink data threshold, the terminal device sends data to the main RLC entity. Based on this, in a possible example, in response to the first RLC entity being the main RLC entity, the terminal device controls the target PDCP entity to send data to the first RLC entity.

[0259] It can be understood that when the first RLC entity is the primary RLC entity, the terminal device can directly control the target PDCP entity to send data to the first RLC entity. If the first RLC entity is not the primary RLC entity, or the second RLC entity is the primary RLC entity, the terminal device first modifies the first RLC entity to be the primary RLC entity, and then controls the target PDCP entity to send data to the first RLC entity.

[0260] When the target entity is a target PDCP entity, in a possible example, after step S1102, the method further includes: the terminal device reestablishing the first RLC entity.

[0261] Among them, rebuilding the first RLC entity may include the following steps: discarding all RLC data such as RLC SDU, RLC SDU segments, RLC PDU, etc.; stopping and resetting all RLC layer timers (including the RLC layer reassembly timer (t-Reassembly), which is used to wait for at least one segment of the complete RLC SDU that has not been received or the complete RLC SDU); initializing the first RLC entity parameters.

[0262] It can be understood that after the target event is restored, the terminal device rebuilds the first RLC entity, which can ensure that the RLC state of the terminal device is consistent with that of the service cell of the new SCG, thereby increasing the probability of successful data transmission.

[0263] Further, in a possible example, after step S1102, the method further includes: the terminal device discards the data stored in the first RLC entity. It can be understood that after the terminal device reconstructs the first RLC entity, the data stored in the first RLC entity is discarded, and the data received by the first RLC entity can be reprocessed to avoid repeated transmission.

[0264] In another possible example, after step S1102, the method further includes: the terminal device reestablishing the target PDCP entity.

[0265] Among them, rebuilding the target PDCP entity can be achieved by discarding all stored data (including PDCP SDU and PDCP PDU). In the UM mode, for the PDCP SDUs that have been assigned SNs but have not been transmitted to the lower layer, these PDCP SDUs are transmitted in the order of increasing SNs, and then the steps of rebuilding the PDCP entity are performed. In the AM mode, starting from the first PDCP SDU that has not received ARQ feedback, retransmission is performed and all stored PDCP SDUs are sent in the order of increasing SNs. After sending, the steps of rebuilding the PDCP entity are performed.

[0266] It can be understood that after the target event is recovered, the terminal device rebuilds the target PDCP entity so that the target PDCP entity is reconnected with the first RLC entity in the first cell group, which can ensure that the RLC state of the terminal device is consistent with that of the service cell of the new SCG and increase the probability of successful data transmission.

[0267] Further, in a possible example, after step S1102, the method also includes: the terminal device retransmits the unsent data of the target PDCP entity.

[0268] Among them, the unsent data refers to the data that the target PDCP entity has not sent. It can be understood that when the target entity is suspended in step S702, the unsent data refers to the data that is not sent through the first RLC entity. In step S702, the target PDCP entity does not transmit data through the first RLC entity, but transmits data through the second RLC entity. The unsent data refers to the data that is not sent through the first RLC entity, and the data that is not sent through the second RLC entity. It can be understood that after the terminal device reestablishes the target PDCP entity, the unsent data of the target PDCP entity is retransmitted to avoid data loss.

[0269] In a possible example, before step S1103, the method further includes: the terminal device sends fourth indication information to the target entity.

[0270] Among them, the fourth indication information indicates that the target event is restored, or indicates that the target entity performs data transmission based on the first cell group, etc., which can refer to the above description and is not limited here. It can be understood that after the target entity receives the fourth indication information, it can be directly controlled by the terminal device according to the fourth indication information, thereby improving the processing efficiency of the target entity. If the target entity can perform data transmission based on the first cell group and the second cell group, the data transmission efficiency can be further improved.

[0271] In a possible example, after step S1102, the method further includes: the terminal device restores the transmission link of the first cell group.

[0272] It can be understood that when the target event is determined to be restored, the transmission link of the first cell group can be restored on the basis of controlling the target entity to perform data transmission based on the first cell group, thereby avoiding the situation where data transmission failure occurs when the target entity sends uplink data to the first cell group.

[0273] In a possible example, after step S1102, the method further includes: the terminal device restores or activates or reactivates the preconfigured authorization resources configured on the first cell group. The preconfigured authorization resources are semi-static transmission resources configured by the access network device. The preconfigured authorization resources can take effect after the access network device configures the semi-static resources, or after the semi-static resources are activated through the PDCCH. After restoring or activating or reactivating the preconfigured authorization resources, the terminal device can use the preconfigured authorization resources that have been suspended or deactivated before to transmit data with the access network device.

[0274] Optionally, the target event is an SCG deactivation event, and after step S1102, the method further includes: the terminal device continues or resumes monitoring the PDCCH on the SCG. It can be understood that after the SCG deactivation event is restored, the channel quality on the SCG needs to be re-focused, so that the terminal device can continue or resume monitoring the PDCCH on the SCG to save power consumption.

[0275] Optionally, the target event is an SCG deactivation event. After step S1102, the method further includes: the terminal device resets the MAC entity of the SCG.

[0276] Among them, the terminal device resets the MAC entity of the SCG, including but not limited to stopping all running MAC layer timers, stopping the ongoing random access process, clearing the cache corresponding to the HARQ, etc., so that the terminal device can be consistent with the access network device.

[0277] Optionally, the target event is an SCG deactivation event. After step S1102, the method further includes: the terminal device activates or reactivates one or more cells on the SCG.

[0278] Among them, the terminal device deactivates one or more cells on the SCG, which may be to deactivate all secondary cells on the SCG, or to deactivate all cells on the SCG, including the primary cell and the secondary cell. After activating or reactivating one or more cells, the terminal device can send and receive data in the cell, so that the terminal device can monitor the PDCCH on the cell and resume data transmission with the access network device.

[0279] Please refer to Fig.12 , Fig.12 It is a flow chart of the fourth data transmission processing method provided in an embodiment of the present application.

[0280] like Fig.12 As shown, the method includes the following steps S1201 to S1203, wherein:

[0281] S1201: The access network device sends third indication information to the terminal device.

[0282] S1202: The terminal device determines target event recovery based on the third indication information.

[0283] Among them, step S1201 and step S1202 can refer to the description of step S1101 and step S1102, and will not be repeated here.

[0284] S1203: The terminal device restores the target entity.

[0285] It can be understood that after the target event is restored, the terminal device restores the target PDCP entity so that the target PDCP entity is reconnected with the first RLC entity in the first cell group, which can ensure that the RLC state of the terminal device is consistent with that of the service cell of the new SCG, and improve the probability of successful data transmission. After the target PDCP entity is restored, the target PDCP entity can send data to the first RLC entity. For details, please refer to the description of step S1103, which will not be repeated here.

[0286] After the target event is restored, the terminal device restores the first RLC entity, which can ensure that the RLC state of the terminal device is consistent with that of the service cell of the new SCG, and can improve the probability of successful data transmission. After the first RLC entity is restored, the first RLC entity can send data to the MAC entity in the first cell group. For details, please refer to the description of step S1103, which will not be repeated here.

[0287] When the target entity is a target PDCP entity, in a possible example, after step S1202, the method further includes: the terminal device reestablishes the first RLC entity. It can be understood that after the target event is recovered, the terminal device reestablishes the first RLC entity, which can ensure that the RLC state of the terminal device is consistent with that of the service cell of the new SCG, and can improve the probability of successful data transmission.

[0288] Further, in a possible example, after step S1202, the method further includes: the terminal device discards the data stored in the first RLC entity. It can be understood that after the terminal device reconstructs the first RLC entity, the data stored in the first RLC entity is discarded, and the data received by the first RLC entity can be reprocessed to avoid repeated transmission.

[0289] In another possible example, after step S1202, the method further includes: the terminal device reestablishes the target PDCP entity. It can be understood that after the target event is recovered, the terminal device reestablishes the target PDCP entity so that the target PDCP entity is reconnected with the first RLC entity in the first cell group, which can ensure that the RLC state of the terminal device is consistent with that of the service cell of the new SCG, and improve the probability of successful data transmission.

[0290] Further, in a possible example, after step S1202, the method further includes: the terminal device retransmits the unsent data of the target PDCP entity. It can be understood that after the terminal device reestablishes the target PDCP entity, retransmitting the unsent data of the target PDCP entity can avoid data loss.

[0291] When the target entity is the first RLC entity, in a possible example, after step S1202, the method further includes: the terminal device reprocesses the RLC SDU stored in the first RLC entity. It can be understood that after the terminal device reconstructs the first RLC entity, reprocessing the data RLC SDU stored in the first RLC entity can avoid data loss.

[0292] In a possible example, before step S1203, the method further includes: the terminal device sends fourth indication information to the target entity. It can be understood that after the target entity receives the fourth indication information, it can be directly controlled by the terminal device according to the fourth indication information, thereby improving the processing efficiency of the target entity.

[0293] In a possible example, after step S1202, the method further includes: the terminal device restores the transmission link of the first cell group. It can be understood that when it is determined that the target event is restored, the transmission link of the first cell group can be restored on the basis of suspending the target entity, further avoiding the situation where the target entity sends uplink data to the first cell group and a data transmission failure occurs.

[0294] In a possible example, after step S1202, the method further includes: the terminal device restores or activates or reactivates the preconfigured authorization resources configured on the first cell group. The preconfigured authorization resources are semi-static transmission resources configured by the access network device. The preconfigured authorization resources can take effect after the access network device configures the semi-static resources, or after the semi-static resources are activated through the PDCCH. After restoring or activating or reactivating the preconfigured authorization resources, the terminal device can use the preconfigured authorization resources that have been suspended or deactivated before to transmit data with the access network device.

[0295] Optionally, the target event is an SCG deactivation event, and after step S1202, the method further includes: the terminal device continues or resumes monitoring the PDCCH on the SCG. It can be understood that after the SCG deactivation event is restored, the channel quality on the SCG needs to be re-focused, so that the terminal device can continue or resume monitoring the PDCCH on the SCG to save power consumption.

[0296] Optionally, the target event is an SCG deactivation event. After step S1202, the method further includes: the terminal device resets the MAC entity of the SCG.

[0297] Among them, the terminal device resets the MAC entity of the SCG, including but not limited to stopping all running MAC layer timers, stopping the ongoing random access process, clearing the cache corresponding to the HARQ, etc., so that the terminal device can be consistent with the access network device.

[0298] Optionally, the target event is an SCG deactivation event. After step S1202, the method further includes: the terminal device activates or reactivates one or more cells on the SCG.

[0299] Among them, the terminal device deactivates one or more cells on the SCG, which may be to deactivate all secondary cells on the SCG, or to deactivate all cells on the SCG, including the primary cell and the secondary cell. After activating or reactivating one or more cells, the terminal device can send and receive data in the cell, so that the terminal device can monitor the PDCCH on the cell and resume data transmission with the access network device.

[0300] The method of the embodiment of the present application is described in detail above, and the device of the embodiment of the present application is provided below.

[0301] See also Fig.13 , Fig.13 Schematic diagram of a data transmission processing device provided in an embodiment of the present application. Fig.13 As shown, the data transmission processing device includes a processing unit 1301 and a communication unit 1302, wherein each unit is described in detail as follows.

[0302] In one embodiment:

[0303] Processing unit 1301 is used to determine the occurrence of a target event, the target event including at least one of the following: a primary cell group connection failure event, a secondary cell group connection failure event, and a secondary cell group deactivation event; controlling the target entity not to transmit data based on the first cell group corresponding to the target event, or suspending the target entity, the target entity being a target packet data convergence protocol PDCP entity or a first radio link control layer protocol RLC entity in the first cell group.

[0304] Optionally, the target entity is a target PDCP entity, and the processing unit 1301 is further used to control the target PDCP entity to send data to a second RLC entity in a second cell group, and the access network devices corresponding to the second cell group and the first cell group are different.

[0305] Optionally, the second RLC entity includes an access network device that copies the RLC entity associated with the target PDCP entity in the second cell group, and the processing unit 1301 is specifically used to control the target PDCP entity to send data to the second RLC entity in response to the second RLC entity being in an activated state.

[0306] Optionally, the second RLC entity includes an access network device that separates the RLC entity associated with the target PDCP entity in the second cell group, and the processing unit 1301 is specifically used to control the target PDCP entity to send data to the second RLC entity in response to the second RLC entity being the main RLC entity.

[0307] Optionally, the target entity is a first RLC entity, and the processing unit 1301 is further configured to discard a partially sent RLC SDU in the first RLC entity.

[0308] Optionally, the processing unit 1301 is further used to suspend the target PDCP entity.

[0309] Optionally, the communication unit 1302 is used to send first indication information to the target entity, where the first indication information is used to indicate the occurrence of a target event, or to indicate that the target entity does not perform a data transmission operation based on the first cell group.

[0310] Optionally, the processing unit 1301 is further used to suspend the transmission link of the first cell group.

[0311] Optionally, the communication unit 1302 is further used to send second indication information to the access network device, where the second indication information is used to indicate the occurrence of a target event, the type of the target event, or a measurement result of the terminal device.

[0312] In another embodiment:

[0313] The communication unit 1302 is configured to receive third indication information from the access network device;

[0314] Processing unit 1301 is used to determine the target event recovery based on the third indication information, and the target event includes at least one of the following: a main cell group connection failure event, a secondary cell group connection failure event, and a secondary cell group deactivation event; control the target entity to transmit data based on the first cell group corresponding to the target event, or restore the target entity, the target entity is the target PDCP entity or the first RLC entity in the first cell group.

[0315] Optionally, the target entity is a target PDCP entity, and the processing unit 1301 is further used to reconstruct the first RLC entity.

[0316] Optionally, the processing unit 1301 is further configured to discard data stored in the first RLC entity.

[0317] Optionally, the target entity is a target PDCP entity, and the processing unit 1301 is further used to reconstruct the target PDCP entity.

[0318] Optionally, the processing unit 1301 is further configured to retransmit unsent data of the target PDCP entity.

[0319] Optionally, the processing unit 1301 is further used to control the target PDCP entity to send data to a second RLC entity in a second cell group, and the access network devices corresponding to the second cell group and the first cell group are different.

[0320] Optionally, the first RLC entity includes an access network device that copies the RLC entity associated with the target PDCP entity in the first cell group, and the processing unit 1301 is specifically used to control the target PDCP entity to send data to the first RLC entity in response to the first RLC entity being in an activated state.

[0321] Optionally, the first RLC entity includes an access network device that separates the RLC entity associated with the target PDCP entity in the first cell group, and the processing unit 1301 is specifically used to control the target PDCP entity to send data to the first RLC entity in response to the first RLC entity being the main RLC entity.

[0322] Optionally, the target entity is the first RLC entity, and the processing unit 1301 is further used to reprocess the RLC SDU stored in the first RLC entity.

[0323] Optionally, the communication unit 1302 is further used to send fourth indication information to the target entity, where the fourth indication information is used to indicate target event recovery, or to instruct the target entity to perform a data transmission operation based on the first cell group.

[0324] Optionally, the processing unit 1301 is further used to restore the transmission link of the first cell group.

[0325] See also Fig.14 , Fig.14 1404 , which is a schematic diagram of another data transmission processing device provided in an embodiment of the present application. The data transmission processing device includes a processor 1401 , a memory 1402 , and a communication interface 1403 , which are interconnected via a bus 1404 .

[0326] The memory 1402 includes, but is not limited to, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), or a portable read-only memory (CD-ROM), and the memory 1402 is used for related computer programs and side data. The communication interface 1403 is used to receive and send side data.

[0327] The processor 1401 may be one or more central processing units (CPUs). When the processor 1401 is a CPU, the CPU may be a single-core CPU or a multi-core CPU.

[0328] In one embodiment, the processor 1401 is used to read the computer program code stored in the memory 1402 and perform the following operations:

[0329] Determining that a target event occurs, where the target event includes at least one of the following: a primary cell group connection failure event, a secondary cell group connection failure event, and a secondary cell group deactivation event;

[0330] The target entity is controlled not to perform data transmission based on the first cell group corresponding to the target event, or the target entity is suspended, and the target entity is a target packet data convergence protocol PDCP entity or a first radio link control layer protocol RLC entity in the first cell group.

[0331] Optionally, the target entity is a target PDCP entity, and the processor 1401 is further configured to perform the following operations:

[0332] The target PDCP entity is controlled to send data to the second RLC entity in the second cell group, and the access network devices corresponding to the second cell group and the first cell group are different.

[0333] Optionally, the second RLC entity includes an RLC entity associated with the access network device copying the bearer in the second cell group as the target PDCP entity, and the processor 1401 is specifically configured to perform the following operations:

[0334] In response to the second RLC entity being in an activated state, controlling the target PDCP entity to send data to the second RLC entity.

[0335] Optionally, the second RLC entity includes an RLC entity associated with the access network device separating the bearer in the second cell group as the target PDCP entity, and the processor 1401 is specifically configured to perform the following operations:

[0336] In response to the second RLC entity being the master RLC entity, the target PDCP entity is controlled to send data to the second RLC entity.

[0337] Optionally, the target entity is a first RLC entity, and the processor 1401 is further configured to perform the following operations:

[0338] The partially transmitted RLC SDU in the first RLC entity is discarded.

[0339] Optionally, the processor 1401 is further configured to perform the following operations:

[0340] Suspend the target PDCP entity.

[0341] Optionally, the processor 1401 is further configured to perform the following operations:

[0342] First indication information is sent to the target entity, where the first indication information is used to indicate the occurrence of a target event, or to indicate that the target entity does not perform a data transmission operation based on the first cell group.

[0343] Optionally, the processor 1401 is further configured to perform the following operations:

[0344] Suspend the transmission link of the first cell group.

[0345] Optionally, the processor 1401 is further configured to perform the following operations:

[0346] Send second indication information to the access network device, where the second indication information is used to indicate the occurrence of a target event, the type of the target event, or the measurement result of the terminal device.

[0347] In another embodiment, the processor 1401 is used to read the computer program code stored in the memory 1402 and perform the following operations:

[0348] receiving third indication information from the access network device;

[0349] Determine target event recovery based on the third indication information, where the target event includes at least one of the following: a main cell group connection failure event, a secondary cell group connection failure event, and a secondary cell group deactivation event; control the target entity to transmit data based on the first cell group corresponding to the target event, or restore the target entity, where the target entity is the target PDCP entity or the first RLC entity in the first cell group.

[0350] Optionally, the target entity is a target PDCP entity, and the processor 1401 is further configured to perform the following operations:

[0351] The first RLC entity is re-established.

[0352] Optionally, the processor 1401 is further configured to perform the following operations:

[0353] The data stored in the first RLC entity is discarded.

[0354] Optionally, the target entity is a target PDCP entity, and the processor 1401 is further configured to perform the following operations:

[0355] Re-establish the target PDCP entity.

[0356] Optionally, the processor 1401 is further configured to perform the following operations:

[0357] Retransmit the unsent data of the target PDCP entity.

[0358] Optionally, the processor 1401 is further configured to perform the following operations:

[0359] The target PDCP entity is controlled to send data to the second RLC entity in the second cell group, and the access network devices corresponding to the second cell group and the first cell group are different.

[0360] Optionally, the first RLC entity includes an RLC entity associated with the access network device and copied bearer in the first cell group for the target PDCP entity, and the processor 1401 is specifically configured to perform the following operations:

[0361] In response to the first RLC entity being in an activated state, controlling the target PDCP entity to send data to the first RLC entity.

[0362] Optionally, the first RLC entity includes an RLC entity associated with a bearer separated by an access network device as a target PDCP entity in a first cell group, and the processor 1401 is specifically configured to perform the following operations:

[0363] In response to the first RLC entity being the master RLC entity, the target PDCP entity is controlled to send data to the first RLC entity.

[0364] Optionally, the target entity is a first RLC entity, and the processor 1401 is further configured to perform the following operations:

[0365] The RLC SDU stored in the first RLC entity is reprocessed.

[0366] Optionally, the processor 1401 is further configured to perform the following operations:

[0367] Send fourth indication information to the target entity, where the fourth indication information is used to indicate target event recovery, or to instruct the target entity to perform a data transmission operation based on the first cell group.

[0368] Optionally, the processor 1401 is further configured to perform the following operations:

[0369] Restore the transmission link of the first cell group.

[0370] The present application provides a chip, including a processor, for calling and executing instructions stored in a memory from a memory, so that a terminal device equipped with the chip executes Figure 7 , Fig.10 , Fig.11 and Fig.12 The method shown.

[0371] The present application also provides another chip, which can be a chip in a terminal device or an access network device, and the chip includes: an input interface, an output interface and a processing circuit, wherein the input interface, the output interface and the circuit are connected through an internal connection path, and the processing circuit is used to execute Figure 7 , Fig.10 , Fig.11 and Fig.12 The method shown.

[0372] The present application also provides another chip, including: an input interface, an output interface, a processor, and optionally, a memory, wherein the input interface, the output interface, the processor, and the memory are connected through an internal connection path, and the processor is used to execute the code in the memory. When the code is executed, the processor is used to execute Figure 7 , Fig.10 , Fig.11 and Fig.12 The method shown.

[0373] The embodiment of the present application also provides a chip system, which includes at least one processor, a memory and an interface circuit, wherein the memory, the transceiver and the at least one processor are interconnected through a line, and a computer program is stored in the at least one memory; when the computer program is executed by the processor, Figure 7 , Fig.10 , Fig.11 and Fig.12 The method flow shown is realized.

[0374] The embodiment of the present application further provides a computer-readable storage medium, in which a computer program is stored. When the computer-readable storage medium is run on a communication device, Figure 7 , Fig.10 , Fig.11 and Fig.12 The method flow shown is realized.

[0375] The embodiment of the present application further provides a computer program product. When the computer program product is run on a communication device, Figure 7 , Fig.10 , Fig.11 and Fig.12 The method flow shown is realized.

[0376] An embodiment of the present application also provides a communication system, which includes the terminal device and access network device involved in any of the above embodiments.

[0377] In summary, by implementing the embodiments of the present application, after the terminal device determines that the target event has occurred, the target entity in the first cell group is controlled not to use the transmission resources of the first cell group corresponding to the target event for data transmission, or the target entity is suspended to achieve that the target entity does not use the transmission resources of the first cell group corresponding to the target event for data transmission, thereby avoiding the use of the first cell group to communicate with the access network device corresponding to the first cell group, and avoiding the situation where data transmission failure occurs. And after determining that the target event has been restored, the target entity can be directly controlled to use the transmission resources of the first cell group corresponding to the target event for data transmission, or the target entity can be restored to achieve that the target entity uses the transmission resources of the first cell group corresponding to the target event for data transmission, which can avoid data loss.

[0378] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiments can be implemented by a computer program or hardware related to the computer program, and the computer program can be stored in a computer-readable storage medium. When the computer program is executed, it can include the processes of the above-mentioned method embodiments. The aforementioned storage medium includes: ROM or random access memory RAM, magnetic disk or optical disk and other media that can store computer program codes.

Claims

1. A data transmission processing method, characterized in that: The method is applicable to a terminal device or a chip in the terminal device, and the method comprises: Determining that a target event occurs, the target event includes at least one of the following: a primary cell group connection failure event, a secondary cell group connection failure event, and the secondary cell group deactivation event; Controlling a target entity not to perform data transmission based on a first cell group corresponding to the target event, the target entity being a target Packet Data Convergence Protocol PDCP entity in the first cell group; and Control the target PDCP entity to send data to the second RLC entity in the second cell group, the second cell group and the first cell group correspond to different access network devices, when the first cell group is the main cell group, the second cell group is the secondary cell group; when the first cell group is the secondary cell group, the second cell group is the main cell group, and the data includes the RLC layer data of the first cell group that has been processed.

2. The data transmission processing method according to claim 1, characterized in that: The second RLC entity includes an access network device duplicating a bearer-associated RLC entity for the target PDCP entity in the second cell group, and controlling the target PDCP entity to send data to the second RLC entity in the second cell group, including: In response to the second RLC entity being in an activated state, controlling the target PDCP entity to send data to the second RLC entity.

3. The data transmission processing method according to claim 1, characterized in that: The second RLC entity includes an access network device separating a bearer-associated RLC entity for the target PDCP entity in the second cell group, and controlling the target PDCP entity to send data to the second RLC entity in the second cell group, including: In response to the second RLC entity being a master RLC entity, controlling the target PDCP entity to send data to the second RLC entity.

4. The data transmission processing method according to claim 1, characterized in that: The method further comprises: Suspend the target PDCP entity.

5. The data transmission processing method according to any one of claims 1 to 4, characterized in that: Before the control target entity does not perform data transmission based on the first cell group, the method further includes: Sending first indication information to a target entity, where the first indication information is used to indicate the occurrence of the target event, or to indicate that the target entity does not perform a data transmission operation based on the first cell group.

6. The data transmission processing method according to any one of claims 1 to 4, characterized in that: The method further comprises: Suspend the transmission link of the first cell group.

7. The data transmission processing method according to any one of claims 1 to 4, characterized in that: The method further comprises: Sending second indication information to the access network device, where the second indication information is used to indicate the occurrence of the target event, the type of the target event, or the measurement result of the terminal device.

8. A data transmission processing method, characterized in that: The method is applicable to a terminal device or a chip in the terminal device, and the method comprises: receiving third indication information from the access network device; Determine target event recovery based on the third indication information, where the target event includes at least one of the following: a primary cell group connection failure event, a secondary cell group connection failure event, and the secondary cell group deactivation event; Controlling a target entity to perform data transmission based on a first cell group corresponding to the target event, or restoring the target entity, where the target entity is a target PDCP entity or a first RLC entity in the first cell group; In a case where the target entity is the target PDCP entity, retransmitting unsent data of the target PDCP entity; In a case where the target entity is the first RLC entity, the RLC SDU stored in the first RLC entity is reprocessed.

9. The data transmission processing method according to claim 8, characterized in that: The target entity is the target PDCP entity, and the method further includes: The first RLC entity is reestablished.

10. The data transmission processing method according to claim 9, characterized in that: The method further comprises: The data stored in the first RLC entity is discarded.

11. The data transmission processing method according to claim 8, characterized in that: The target entity is the target PDCP entity, and the method further includes: Re-establish the target PDCP entity.

12. The data transmission processing method according to any one of claims 8 to 11, characterized in that: The method further comprises: The target PDCP entity is controlled to send data to a second RLC entity in a second cell group, and the access network devices corresponding to the second cell group and the first cell group are different.

13. The data transmission processing method according to any one of claims 9 to 11, characterized in that: The first RLC entity includes an RLC entity associated with the target PDCP entity and copied by an access network device in the first cell group, and the control target entity performs data transmission based on the first cell group, including: In response to the first RLC entity being in an activated state, controlling the target PDCP entity to send data to the first RLC entity.

14. The data transmission processing method according to any one of claims 9 to 11, characterized in that: The first RLC entity includes an RLC entity associated with a separate bearer in the first cell group by an access network device for the target PDCP entity, and the control target entity performs data transmission based on the first cell group, including: In response to the first RLC entity being a master RLC entity, the target PDCP entity is controlled to send data to the first RLC entity.

15. The data transmission processing method according to any one of claims 8 to 11, characterized in that: Before the control target entity performs data transmission based on the first cell group corresponding to the target event, the method further includes: Send fourth indication information to the target entity, where the fourth indication information is used to indicate that the target event is recovered, or to instruct the target entity to perform a data transmission operation based on the first cell group.

16. The data transmission processing method according to any one of claims 8 to 11, characterized in that: The method further comprises: Restore the transmission link of the first cell group.

17. A data transmission processing device, characterized in that: It comprises a processing unit and / or a communication unit corresponding to the method according to any one of claims 1 to 16.

18. A communication device, characterized in that: The invention comprises a processor coupled to a memory, wherein the memory is used to store one or more programs, and the one or more programs are executed by the processor to perform the method according to any one of claims 1 to 16.

19. A computer-readable storage medium, characterized in that: It is used to store a computer program, wherein the computer program enables a computer to execute the method according to any one of claims 1 to 16.

Images