CN113259991A - Communication method and device - Google Patents

Abstract

The application provides a communication method and device, relates to the technical field of communication, and can reduce the phenomenon of data transmission failure and save air interface resources. The method comprises the following steps: the terminal equipment determines that a radio link problem occurs on a first Radio Link Control (RLC) entity of a Packet Data Convergence Protocol (PDCP) copy function. And after determining a second RLC entity with the PDCP copying function, the terminal equipment sends uplink data to the network equipment through the second RLC entity. Wherein, the second RLC entity is an RLC entity without radio link problem.

Description

Communication method and device

Technical Field

The present application relates to the field of communications technologies, and in particular, to a communication method and apparatus.

Background

In a data duplication (data duplication) transmission scheme, a Radio Link Failure (RLF) includes a Radio Link Control (RLC) failure and/or an uplink before Listen (LBT) failure. The RLC failure means that the number of retransmissions occurring in a certain RLC entity reaches a preset value 1, and the UL LBT failure means that the terminal device determines that an idle channel does not exist in a certain cell within a preset time period, and the number of times that the idle channel does not exist in the terminal device statistics reaches a preset value 2. If RLC failure occurs, the terminal equipment sends a failure message 1 to the network equipment to inform the network equipment which RLC entity has a problem. If the UL LBT failure occurs, the terminal device sends a failure message 2 to the network device to inform the network device which cell has a problem.

However, when uplink data is still transmitted through a failed RLC entity or a failed cell, transmission failure is easily caused, and air interface resources are wasted.

Disclosure of Invention

The embodiment of the application provides a communication method and device, which can reduce the phenomenon of transmission failure and save air interface resources.

In order to achieve the above purpose, the embodiment of the present application adopts the following technical solutions:

in a first aspect, an execution subject of the method may be a terminal device, or a chip applied to the terminal device. The following description will be given taking as an example that the execution main body is a terminal device. The method comprises the following steps: the terminal equipment determines that a radio link problem occurs on a first Radio Link Control (RLC) entity of a Packet Data Convergence Protocol (PDCP) copy function. And after determining a second RLC entity with the PDCP copying function, the terminal equipment sends uplink data to the network equipment through the second RLC entity. Wherein, the second RLC entity is an RLC entity without radio link problem.

According to the communication method provided by the embodiment of the application, the terminal equipment can determine the first RLC entity which has the radio link problem and the second RLC entity which has no radio link problem. In the case where a radio link problem occurs in the first RLC entity, the terminal apparatus transmits uplink data through the second RLC entity. Because the second RLC entity does not have the radio link problem, the phenomenon of data transmission failure can be reduced, and air interface resources are saved.

In one possible design, the uplink data is first indication information indicating that a radio link problem occurs on the first RLC entity. Therefore, the network equipment can know that the radio link problem occurs on the first RLC entity, and then response processing is executed, so that the terminal equipment stops sending data from the first RLC entity, and unnecessary transmission failure is avoided.

In one possible design, the sending, by the terminal device, uplink data to the network device through the second RLC entity includes: and in a first time length, the terminal equipment sends uplink data to the network equipment through the second RLC entity, wherein the first time length is the time length for forbidding sending the uplink data to the network equipment through the first RLC entity.

Here, since the channel status is changed, the channel of the cell corresponding to the first RLC entity still has a problem for a first time period after the terminal device determines that the radio link problem occurs in the first RLC entity. If the terminal equipment still sends uplink data from the first RLC entity, the probability of uplink data transmission failure is high. Therefore, in the first duration, the terminal equipment does not send the uplink data through the first RLC entity, but sends the uplink data through the second RLC entity, and the phenomenon of data transmission failure does not exist, so that air interface resources are saved.

In one possible design, the communication method according to the embodiment of the present application further includes: and when the second duration is overtime, the terminal equipment retransmits the uplink data.

Therefore, the terminal equipment can ensure that the network equipment can receive the uplink data by retransmitting the uplink data, and the data transmission reliability is improved.

In one possible design, the communication method according to the embodiment of the present application further includes: and when the preset condition is met, the terminal equipment stops retransmitting the uplink data. Wherein the preset condition satisfies at least one of the following conditions: the retransmission times executed by the first RLC entity is less than or equal to a first preset value, the first RLC entity is in a deactivated state, the PDCP copy function of the data radio bearer DRB associated with the first RLC entity is in a deactivated state, the PDCP copy function of the signaling radio bearer SRB associated with the first RLC entity is in a deactivated state, the cell corresponding to the first RLC entity is in a deactivated state, the data transmission process of the cell corresponding to the first RLC entity is suspended, and the uplink data retransmission times reach a second preset value.

Therefore, the problem of air interface resource waste caused by repeated uplink data retransmission of the terminal equipment can be avoided.

In one possible design, the communication method according to the embodiment of the present application further includes: the terminal equipment deactivates the first RLC entity, or deactivates a PDCP copy function of a DRB associated with the first RLC entity, or deactivates a PDCP copy function of a SRB associated with the first RLC entity, or deactivates a cell corresponding to the first RLC entity; or the terminal equipment suspends the data transmission process of the cell corresponding to the first RLC entity.

Therefore, the first RLC entity can not transmit uplink data, thereby avoiding unnecessary transmission failure and saving air interface resources.

In a second aspect, an execution subject of the method may be a terminal device, or a chip applied to the terminal device. The following description will be given taking as an example that the execution main body is a terminal device. The method comprises the following steps: the terminal equipment determines that a radio link problem occurs on a first Radio Link Control (RLC) entity of a Packet Data Convergence Protocol (PDCP) copy function. After the terminal equipment determines the target cell set, uplink data is sent to the network equipment through the cells in the target cell set. The target cell set is a set of cells except for a cell corresponding to the first RLC entity in the allowed serving cell set corresponding to the uplink data, and the RLC entity corresponding to the cell in the target cell set has no radio link problem.

According to the communication method provided by the embodiment of the application, the terminal equipment can determine the first RLC entity and the target cell set, wherein the first RLC entity has a radio link problem. And under the condition that the first RLC entity has a radio link problem, the terminal equipment transmits uplink data through the cells in the target cell set. Because the cell in the target cell set does not include the cell corresponding to the first RLC entity, the RLC entity corresponding to the cell in the target cell set does not have a radio link problem, and thus, the phenomenon of uplink data transmission failure does not exist, and thus, air interface resources are saved.

In one possible design, the uplink data is first indication information indicating that a radio link problem occurs on the first RLC entity.

In one possible design, the sending, by the terminal device, uplink data to the network device through a cell in the target cell set includes: and within a third time length, the terminal equipment sends uplink data to the network equipment through the cells in the target cell set, wherein the third time length is the time length for forbidding sending the uplink data to the network equipment through the cells corresponding to the first RLC entity. The third time period may be the same as or different from the first time period.

In one possible design, the communication method according to the embodiment of the present application further includes: and when the fourth time exceeds the set time, the terminal equipment retransmits the uplink data. Here, the fourth time period may be the same as or different from the second time period.

In one possible design, the communication method according to the embodiment of the present application further includes: and when the preset condition is met, the terminal equipment stops retransmitting the uplink data. Wherein the preset condition satisfies at least one of the following conditions: the retransmission times executed by the first RLC entity is less than or equal to a first preset value, the first RLC entity is in a deactivated state, the PDCP copy function of the data radio bearer DRB associated with the first RLC entity is in a deactivated state, the PDCP copy function of the signaling radio bearer SRB associated with the first RLC entity is in a deactivated state, the cell corresponding to the first RLC entity is in a deactivated state, the data transmission process of the cell corresponding to the first RLC entity is suspended, and the uplink data retransmission times reach a second preset value.

In one possible design, the communication method according to the embodiment of the present application further includes: the terminal equipment deactivates the first RLC entity, or deactivates a PDCP copy function of a DRB associated with the first RLC entity, or deactivates a PDCP copy function of a SRB associated with the first RLC entity, or deactivates a cell corresponding to the first RLC entity; or the terminal equipment suspends the data transmission process of the cell corresponding to the first RLC entity.

In a third aspect, an execution subject of the method may be a terminal device, or a chip applied to the terminal device. The following description will be given taking as an example that the execution main body is a terminal device. The method comprises the following steps: after determining that a radio link problem occurs on a first Radio Link Control (RLC) entity of a Packet Data Convergence Protocol (PDCP) copy function, the terminal device switches a bandwidth part (BWP) of a cell corresponding to the first RLC entity, and then sends uplink data to the network device through the first RLC entity after BWP switching.

The frequency band of the cell corresponding to the first RLC entity after BWP handover has no problem. The terminal equipment can send uplink data to the network equipment through the first RLC entity after BWP switching, and the phenomenon of transmission failure does not exist, so that air interface resources are saved, and robust transmission of the uplink data is realized.

In a fourth aspect, an execution subject of the method may be a terminal device, or a chip applied to the terminal device. The following description will be given taking as an example that the execution main body is a terminal device. The method comprises the following steps: the terminal equipment determines that a radio link problem occurs on a first cell of a packet data convergence protocol PDCP duplication function. And after determining a second cell with the PDCP copy function, the terminal equipment sends uplink data to the network equipment through the second cell. Wherein the second cell is a cell in which no radio link problem occurs.

Therefore, the terminal equipment can determine the first cell with the radio link problem and the second cell without the radio link problem, and then the second cell sends the uplink data.

In one possible design, a first RLC entity corresponding to a first cell is different from a second RLC entity corresponding to a second cell. Therefore, the terminal equipment generates uplink data through the cell corresponding to the second RLC entity, and because no radio link problem occurs in the cell corresponding to the second RLC entity, the probability of successful transmission of the uplink data is higher under the condition that the uplink data is sent through the cell corresponding to the second RLC entity, so that air interface resources are saved.

In one possible design, the communication method according to the embodiment of the present application further includes: and the terminal equipment determines a first RLC entity according to the logic channel LCH associated with the first cell. The terminal equipment deactivates the first RLC entity, or deactivates a PDCP copy function of a DRB associated with the first RLC entity, or deactivates a PDCP copy function of a SRB associated with the first RLC entity, or suspends a data transmission process of a cell corresponding to the first RLC entity.

Therefore, the first RLC entity can not transmit uplink data, thereby avoiding unnecessary transmission failure and saving air interface resources.

In one possible design, the communication method according to the embodiment of the present application further includes: the terminal equipment deletes the corresponding relation between the LCH of the first RLC entity and the first cell, wherein the first RLC entity is the RLC entity corresponding to the first cell.

Therefore, after the correspondence between the LCH of the first RLC entity and the first cell is deleted, it can be ensured that no radio link problem occurs in the cells in the allowed serving cell set corresponding to the LCH of each RLC entity, and uplink data can be transmitted through the cells in the allowed serving cell set corresponding to the LCH of any one RLC entity, which can ensure successful transmission of the uplink data, avoid unnecessary transmission failure, and save air interface resources.

In a fifth aspect, an embodiment of the present application provides a communication apparatus, including: means for performing the steps of any of the above aspects. The communication device may be the terminal device of the first aspect, or a device including the terminal device; alternatively, the communication device may be the terminal device of the second aspect, or a device including the terminal device; alternatively, the communication device may be the terminal device in the third aspect, or a device including the terminal device; alternatively, the communication device may be the terminal device in the fourth aspect, or a device including the terminal device.

In a sixth aspect, an embodiment of the present application provides a communication device, including a processor and an interface circuit, where the processor is configured to communicate with other devices through the interface circuit, and to perform the communication method provided in any one of the above aspects. The processor includes one or more. The communication device may be the terminal device of the first aspect, or a device including the terminal device; alternatively, the communication device may be the terminal device of the second aspect, or a device including the terminal device; alternatively, the communication device may be the terminal device in the third aspect, or a device including the terminal device; alternatively, the communication device may be the terminal device in the fourth aspect, or a device including the terminal device.

In a seventh aspect, an embodiment of the present application provides a communication apparatus, including a processor, connected to a memory, and configured to call a program stored in the memory to execute the communication method provided in any aspect. The memory may be located within the communication device or external to the communication device. And the processor includes one or more. The communication device may be the terminal device of the first aspect, or a device including the terminal device; alternatively, the communication device may be the terminal device of the second aspect, or a device including the terminal device; alternatively, the communication device may be the terminal device in the third aspect, or a device including the terminal device; alternatively, the communication device may be the terminal device in the fourth aspect, or a device including the terminal device.

In an eighth aspect, an embodiment of the present application provides a communication apparatus, including at least one processor and at least one memory, where the at least one processor is configured to execute the communication method provided in any one of the above aspects. The communication device may be the terminal device of the first aspect, or a device including the terminal device; alternatively, the communication device may be the terminal device of the second aspect, or a device including the terminal device; alternatively, the communication device may be the terminal device in the third aspect, or a device including the terminal device; alternatively, the communication device may be the terminal device in the fourth aspect, or a device including the terminal device.

In a ninth aspect, embodiments of the present application provide a computer-readable storage medium, which stores instructions that, when executed on a computer, enable the computer to perform the communication method of any one of the above aspects.

In a tenth aspect, embodiments of the present application provide a computer program product containing instructions that, when executed on a computer, enable the computer to perform the communication method of any one of the above aspects.

In an eleventh aspect, embodiments of the present application provide circuitry comprising processing circuitry configured to perform the communication method of any one of the above aspects.

In a twelfth aspect, an embodiment of the present application provides a chip, where the chip includes a processor, a coupling of the processor and a memory, and the memory stores program instructions, and when the program instructions stored in the memory are executed by the processor, the communication method in any one of the above aspects is implemented.

In a thirteenth aspect, an embodiment of the present application provides a communication system, where the communication system includes the terminal device and the network device in any of the above aspects. For technical effects brought by any one of the design manners in the second aspect to the thirteenth aspect, reference may be made to technical effects brought by different design manners in the first aspect, and details are not repeated here.

Drawings

Fig. 1 is a schematic diagram of an architecture of a packet data convergence protocol replication function provided in the related art;

fig. 2 is a schematic diagram of a communication network architecture according to an embodiment of the present application;

fig. 3 is a flowchart illustrating a communication method according to an embodiment of the present application;

fig. 4 is a flowchart illustrating another communication method according to an embodiment of the present application;

fig. 5(a) is a schematic flowchart of another communication method provided in an embodiment of the present application;

fig. 5(b) is a schematic flowchart of another communication method provided in the embodiment of the present application;

fig. 6 is a flowchart illustrating a further communication method according to an embodiment of the present application;

fig. 7 is a flowchart illustrating a further communication method according to an embodiment of the present application;

fig. 8 is a flowchart illustrating a further communication method according to an embodiment of the present application;

fig. 9 is a flowchart illustrating a further communication method according to an embodiment of the present application;

fig. 10 is a flowchart illustrating a further communication method according to an embodiment of the present application;

fig. 11 is a schematic structural diagram of a communication device according to an embodiment of the present application;

fig. 12 is a schematic hardware structure diagram of a communication device according to an embodiment of the present application;

fig. 13 is a schematic structural diagram of another communication device according to an embodiment of the present application;

fig. 14 is a schematic structural diagram of another communication device according to an embodiment of the present application;

fig. 15 is a schematic structural diagram of another communication device according to an embodiment of the present application;

fig. 16 is a schematic structural diagram of another communication device according to an embodiment of the present application.

Detailed Description

The terms "first" and "second" and the like in the description and drawings of the present application are used for distinguishing different objects or for distinguishing different processes for the same object, and are not used for describing a specific order of the objects. Furthermore, the terms "including" and "having," and any variations thereof, as referred to in the description of the present application, are intended to cover non-exclusive inclusions. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those steps or elements but may alternatively include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus. In the embodiments of the present application, "a plurality" includes two or more. In the embodiments of the present application, words such as "exemplary" or "for example" are used to mean serving as an example, instance, or illustration. Any embodiment or design described herein as "exemplary" or "e.g.," is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the word "exemplary" or "such as" is intended to present concepts related in a concrete fashion.

First, technical terms involved in the related art are introduced:

1. packet Data Convergence Protocol (PDCP) replication function

Ultra-reliable low latency (URLLC) services have very high requirements on transmission latency and transmission reliability. For example, remote industrial control, intelligent transportation system, distributed automation, etc. require a transmission delay of less than 5ms and a transmission error rate of less than 10^-5. Therefore, the third generation partnership project (3 GPP) proposes a data replication (replication) method to meet the requirements of URLLC service.

Referring to fig. 1, a network device configures at least two Radio Link Control (RLC) entities and at least two Logical Channels (LCHs) for a Radio Bearer (RB) of a terminal device. Wherein, one RLC entity corresponds to one LCH. The RB may be a Signaling Radio Bearer (SRB) or a Data Radio Bearer (DRB). Wherein, there are one or more SRBs, and there are multiple RLC entities corresponding to each SRB. One or more DRBs are provided, and a plurality of RLC entities are provided corresponding to each DRB. The RLC entity corresponding to SRB is different from the RLC entity corresponding to DRB. Only two RLC entities are shown in fig. 1, and the two RLC entities shown in fig. 1 are a primary RLC entity and a non-primary RLC entity, respectively. The transmission path in which the primary RLC entity is located may be referred to as a primary path (primary path), and the transmission path in which the non-primary RLC entity is located may be referred to as a secondary path (secondary path) or a non-primary path (non-primary path). The non-primary RLC entity may also be described as a secondary RLC entity.

Referring to fig. 1, a PDCP entity copies a PDCP Protocol Data Unit (PDU) to obtain multiple copies of data, and sends the multiple copies of data to different RLC entities for processing. The PDCP PDU may be SRB data or DRB data. A Medium Access Control (MAC) entity restricts transmission of the original PDCP PDU and the duplicated PDCP PDU on different cells. In fig. 1, the PDCP PDUs transmitted on the primary RLC entity are transmitted by the cell 1b in the serving cell set 1, and the PDCP PDUs transmitted on the non-primary RLC entity are transmitted by the cell 2b in the serving cell set 2, as shown by the thick curve in fig. 1. Here, the set of allowed serving cells (allowed serving cells) corresponding to the LCH of the primary RLC entity is allowed serving cell set 1. Wherein, the allowed serving cell set 1 includes a cell 1a, a cell 1b, and a cell 1 c. The set of allowed serving cells corresponding to the LCH of the non-primary RLC entity is allowed serving cell set 2. Wherein the allowed serving cell set 2 includes a cell 2a, a cell 2b, and a cell 2 c. The LCH of the primary RLC entity can only be transmitted on the serving cells in the allowed serving cell set 1 and cannot be transmitted on other cells than the allowed serving cell set 1. The LCH of the non-primary RLC entity can only be transmitted on the serving cell in the allowed serving cell set 2 and cannot be transmitted on other cells outside the allowed serving cell set 2. The cells in the allowed serving cell set may be licensed spectrum cells or unlicensed spectrum cells. For example, the LCH of the primary RLC entity is transmitted on a licensed spectrum cell and the LCH of the non-primary RLC entity is transmitted on an unlicensed spectrum cell. Therefore, the same PDCP PDU is transmitted through more than one independent paths, so that the reliability of data transmission is guaranteed, and the time delay is reduced.

In the technical solution of the PDCP duplication function, a Radio Link Failure (RLF) includes an RLC failure and/or an uplink before talk (LBT) failure. Among them, the UL LBT failure is also called sustained LBT failure (continuous LBT failure). In the embodiment of the present application, the RLC failure is described as event 1, and the UL LBT failure is described as event 2.

2. RLC failure

In the technical solution of the PDCP replication function, if the number of times that a certain RLC entity (e.g., RLC entity 1) performs retransmission reaches a preset value 1, and all cells in an allowed serving cell set corresponding to an LCH of the RLC entity 1 are secondary cells (scells). At this time, the terminal device does not trigger the RRC reestablishment process, but sends a failure information (failure information)1 to the network device to inform the network device which RLC entity has a problem. This case is an RLC failure.

After the network device receives the failure message 1 from the terminal device, the network device performs at least one of the following operations:

firstly, the network equipment issues first deactivation indication information.

The first deactivation indication information is used for indicating that the PDCP copy function of the RB corresponding to the RLC entity 1 is deactivated, so that the PDCP PDUs are all transmitted from the RLC entities except the RLC entity 1. Here, in the case that two RLC entities are configured, if the allowed serving cell set corresponding to the LCH of the primary RLC entity includes a primary cell (PCell), and all cells in the allowed serving cell set corresponding to the LCH of the non-primary RLC entity are secondary cells, the RLC entity 1 is a non-primary RLC entity. If the allowed serving cell set corresponding to the LCH of the primary RLC entity does not include the primary cell, but all are secondary cells, the RLC entity 1 is an non-primary RLC entity or a primary RLC entity.

Secondly, the network equipment reconfigures the allowed service cell set corresponding to the RLC entity 1, so that the PDCP PDU is sent from the secondary cell where the radio link problem does not occur, thereby avoiding the data transmission failure.

3. UL LBT failure

In a case that cells in the serving cell set are allowed to be unlicensed spectrum cells, before transmitting uplink data, the terminal device performs a Listen Before Talk (LBT) procedure to determine whether there is a free channel for transmitting the uplink data. LBT is a channel access mechanism. On the unlicensed frequency band, the availability of the channel cannot be guaranteed at any time. Before transmitting the uplink data, the terminal equipment carries out idle channel assessment to ensure that the uplink data is transmitted under the condition that the channel is idle. And if the LBT is successful, the terminal equipment transmits uplink data. And if the LBT fails, the terminal equipment gives up transmitting the uplink data, and then transmits the uplink data when the subsequent channel is idle.

In the related art, the terminal device detects whether an UL LBT failure occurs through one timer (timer) and one counter (counter) for each cell in the allowed serving cell set. Specifically, the terminal device increments the counter by 1 every time it determines that the LBT fails, and starts the timer. During the running of the timer, if the counter reaches a preset value of 2, the terminal equipment determines that the UL LBT failure occurs. When the timer times out, the terminal device resets the counter. If the secondary cell fails UL LBT, the terminal device does not trigger the cell re-establishment procedure, and sends a failure message 2 to the network device through the cell where the UL LBT failure does not occur, so as to inform the network device which cell has a problem. Wherein, the failure message 2 is a Control Element (CE) of the MAC. The number of cells in which UL LBT failure occurs may be one or more.

After the network device receives the failure message 2 from the terminal device, the network device performs at least one of the following operations:

first, the network device issues second deactivation indication information.

Wherein the second deactivation indication information is used for indicating the deactivation of the cell in which the UL LBT failure occurs.

Secondly, the network equipment issues data scheduling indication information.

The data scheduling indication information is used to indicate that data, such as uplink data or downlink data, is prohibited from being transmitted in the cell in which the UL LBT failure occurs.

Thirdly, the network device issues a Radio Resource Control (RRC) reconfiguration message to enable the terminal device to avoid the frequency band with radio link problem when transmitting data.

Fourthly, the network equipment issues a bandwidth part (BWP) switching instruction so that the terminal equipment transmits data by adopting a frequency band without the problem of the wireless link.

In addition, in the embodiment of the present application, one cell may correspond to one downlink carrier (carrier), and one cell may also correspond to one downlink carrier and one uplink carrier. In the case of configuring a Supplementary Uplink (SUL), one cell may also correspond to two uplink carriers, namely, a Supplementary Uplink (SUL) carrier and an Uplink (UL) carrier (another referred to as a Normal Uplink (NUL)).

In the related art, when the radio link problem is an RLC failure, after the terminal device sends a failure message 1 to the network device, before the terminal device receives the first deactivation indication information from the network device, or after the terminal device sends the failure message 1 to the network device, before the network device reconfigures the allowed serving cell set corresponding to the RLC entity having the radio link problem, if uplink data is still sent from the RLC entity having the radio link problem or the cell corresponding to the RLC entity having the radio link problem, a transmission failure is easily caused. Although the terminal device can limit the failure message 2 from being sent from the cell with the radio link problem, if the cell corresponding to the RLC entity with the radio link problem is a plurality of secondary cells, the terminal device cannot limit which secondary cell of the plurality of secondary cells the uplink data is not sent from, and the problem of transmission failure still exists, which wastes air interface resources and affects service experience.

In view of this, an embodiment of the present application provides a communication method, which is applicable to various communication systems. The communication method provided by the embodiment of the application can be applied to a Long Term Evolution (LTE) system, or a fifth-generation (5G) communication network, or other similar networks, or other networks in the future. Fig. 2 is a schematic architecture diagram of a communication system applicable to the communication method according to the embodiment of the present application, and the communication system may include a terminal device 20 and a network device 21. Wherein, the terminal device 20 is wirelessly connected with the network device 21. The terminal device 20 may be one or more, and the network device 21 may be one or more. Only one network device and two terminal devices are shown in fig. 2. Fig. 2 is a schematic diagram, and does not limit the application scenario of the communication method according to the embodiment of the present application.

The terminal device 20, also called User Equipment (UE), a Mobile Station (MS), a Mobile Terminal (MT), etc., is a device for providing voice/data connectivity to a user, for example, a handheld device or a vehicle-mounted device with a wireless connection function. The terminal device may specifically be: a mobile phone (mobile phone), a tablet computer, a notebook computer, a palm top computer, a Mobile Internet Device (MID), a wearable device, a Virtual Reality (VR) device, an Augmented Reality (AR) device, a wireless terminal in industrial control (industrial control), a wireless terminal in self driving (self driving), a wireless terminal in remote surgery (remote medical supply), a wireless terminal in smart grid (smart grid), a wireless terminal in transportation safety (smart security), a wireless terminal in city (smart city), a wireless terminal in smart home (smart home), a terminal in a future 5G communication network or a communication network after 5G, and the like, which are not limited in this embodiment.

The network device 21 is a device in a wireless communication network, for example, a Radio Access Network (RAN) node that accesses the terminal device 20 to the wireless communication network. Currently, some examples of RAN nodes are: a gbb, a Transmission Reception Point (TRP), an evolved Node B (eNB), a Radio Network Controller (RNC), a Node B (NB), a Base Station Controller (BSC), a Base Transceiver Station (BTS), a home base station (e.g., home evolved Node B, or home Node B, HNB), a Base Band Unit (BBU), or a wireless fidelity (WiFi) Access Point (AP), or a network side device in a future 5G communication network or a communication network after 5G, and the like.

The communication system and the service scenario described in the embodiment of the present application are for more clearly illustrating the technical solution of the embodiment of the present application, and do not constitute a limitation on the technical solution provided in the embodiment of the present application. As can be known to those skilled in the art, with the evolution of network architecture and the emergence of new service scenarios, the technical solution provided in the embodiments of the present application is also applicable to similar technical problems.

The following specifically explains the communication method provided in the embodiment of the present application.

It should be noted that, in the following embodiments of the present application, the names of messages between network elements or the names of parameters in messages, etc. are only examples, and other names may also be used in specific implementations, which are described in a unified manner herein and will not be described again below.

The embodiment of the application provides a communication method, which is applied to a data transmission process when RLC failure occurs. Referring to fig. 3, the communication method includes the steps of:

s300, the network equipment sends RRC information to the terminal equipment. Accordingly, the terminal device receives the RRC message from the network device.

Wherein the RRC message includes configuration information of the PDCP copy function. The configuration information of the PDCP duplication function is used to configure at least two RLC entities for the RB. The at least two RLC entities include a primary RLC entity and a non-primary RLC entity. Wherein, the number of the main RLC entities is one. The non-primary RLC entities are one or more. The LCH of each RLC entity corresponds to one or more cells in the allowed service cell set. That is, one RLC entity corresponds to one or more cells.

For the DRB or SRB configured with the PDCP duplication function, the RRC message may further indicate an initial activation state of the non-primary RLC entity associated with the DRB or SRB, where the initial activation state of the non-primary RLC entity is an activation state or a deactivation state. If the initial activation condition of the non-master RLC entity is in a deactivated state, the PDCP entity does not deliver PDCP PDUs to the non-master RLC entity, that is, the PDCP PDUs are not transmitted by the non-master RLC entity in the deactivated state, but only by the non-master RLC entity in the activated state.

S301, the terminal device determines that a radio link problem occurs on a first RLC entity of the PDCP copy function.

And the cell corresponding to the first RLC entity is a secondary cell. The first RLC entity may be one RLC entity or a plurality of RLC entities. Here, one RLC entity corresponds to one LCH, and all cells in the set of allowed serving cells corresponding to the LCH of the first RLC entity are secondary cells. The first RLC entity may be an non-primary RLC entity. The first RLC entity may also be a primary RLC entity, when all cells in the allowed serving cell set corresponding to the LCH of the primary RLC entity are secondary cells.

Illustratively, in the PDCP duplication function, the terminal device determines the number of retransmissions on one RLC entity for each RLC entity. If the number of retransmissions on a certain RLC entity reaches a first preset value (i.e., preset value 1), the terminal device determines that an RLC failure occurs on the RLC entity, i.e., a radio link problem occurs on the RLC entity, and the terminal device uses the RLC entity as a first RLC entity.

Here, the terminal device may perform S302 and S303 to transmit uplink data to the network device, as shown in fig. 3. The terminal device may perform S304 and S305 to transmit uplink data to the network device, as shown in fig. 4. Wherein, the specific descriptions of S302 to S305 are as follows:

s302, the terminal equipment determines a second RLC entity with the PDCP copying function.

The second RLC entity is an RLC entity which has no radio link problem in at least two RLC entities configured with the PDCP copy function. Here, if the first RLC entity is a master RLC entity, the second RLC entity is one of the non-master RLC entities. If the first RLC entity is a non-main RLC entity, the second RLC entity is another non-main RLC entity, or the second RLC entity is a main RLC entity. The first RLC entity and the second RLC entity correspond to the same SRB, or the first RLC entity and the second RLC entity correspond to the same DRB.

For example, if the number of retransmissions on a certain RLC entity does not reach the first preset value, the terminal device determines that no radio link problem occurs on the RLC entity, and uses the RLC entity as the second RLC entity. That is, the second RLC entity is an RLC entity other than the first RLC entity of the at least two RRC entities. Further, if the number of RLC entities except the first RLC entity in the at least two RRC entities is equal to or greater than two, the second RLC entity may be all activated RLC entities except the first RLC entity, or may be an RLC entity determined by a certain rule. For example, for all activated RLC entities which do not have radio link problems, the RLC entities are sorted according to the value of the LCH identifier of the RLC entity, and the RLC entity of the LCH with the smallest value or the largest value of the LCH identifier is used as the second RLC entity.

And S303, the terminal equipment sends uplink data to the network equipment through the second RLC entity. Accordingly, the network device receives the uplink data from the terminal device.

The uplink data includes SRB data and/or DRB data. Here, the SRB data is SRB data configured with a PDCP copy function. The DRB data is DRB data configured with a PDCP copy function. That is, when the uplink data is duplicated data, the uplink data may be transmitted through the second RLC entity.

Illustratively, if the DRB1 configures the PDCP copy function and a radio link problem occurs at the first RLC entity associated with the DRB1, the PDCP PDUs (i.e., DRB data) of the DRB1 are transmitted from the second RLC entity and not from the first RLC entity.

S304, the terminal device determines a target cell set.

The target cell set is a set of cells except for a cell in the allowed serving cell set corresponding to the first RLC entity in the allowed serving cell set corresponding to the uplink data. The RLC entity corresponding to the cell in the target cell set has no radio link problem. Here, if the allowed serving cell set is not configured for the uplink data, it is considered that the allowed serving cell set corresponding to the uplink data is a set of all cells configured for the terminal device, and the target cell set is a set of cells, except cells in the allowed serving cell set corresponding to the first RLC entity, in all cells configured for the terminal device.

Illustratively, the allowed serving cell set corresponding to the uplink data is { cell 1, cell 2, cell 3, cell 4}, the allowed serving cell set corresponding to the first RLC entity is { cell 1, cell 2}, and the target cell set is { cell 3, cell 4 }.

S305, the terminal equipment sends uplink data to the network equipment through the cells in the target cell set. Accordingly, the network device receives the uplink data from the terminal device.

The RLC entity corresponding to the uplink data may be denoted as a third RLC entity, and the third RLC entity is an RLC entity not configured with a PDCP copy function. That is, if there is no first RLC entity with radio link problem, the uplink data is sent through a cell in the allowed serving cell set corresponding to the uplink data; if the first RLC entity with the radio link problem exists, the uplink data is sent through the cells in the target cell set. And, no matter whether there is the first RLC entity with radio link problem, the RLC entity transmitting the upload data is always the third RLC entity.

For example, the uplink data may be the first indication information. The first indication information is used to indicate that a radio link problem occurs on the first RLC entity. Under the condition that the network equipment learns that the radio link problem occurs on the first RLC entity, the network equipment executes response processing, such as sending first deactivation indication information to deactivate a PDCP copy function of an RB corresponding to the first RLC entity, or deactivate the first RLC entity, so that the first RLC entity cannot send data, and unnecessary transmission failure is avoided. Here, the first indication information includes an LCH identity and/or a cell group identity. The LCH mark is used for marking a logic channel corresponding to the first RLC entity. The cell group identifier is used for identifying a cell group corresponding to the first RLC entity. The first indication information further includes failure type information. Wherein the failure type information is used to indicate a cause of the radio link problem. The first indication is transmitted through SRB 1. Alternatively, in the case where the terminal device is configured with the SRB3, the first indication information may be transmitted through the SRB 3.

It should be noted that, if the terminal device determines that the second RLC entity does not exist, the terminal device triggers an RRC reestablishment procedure. Or, if the terminal device determines that the target cell set does not exist, the terminal device triggers an RRC reestablishment procedure. The terminal device may first execute S301 and then execute S302, may first execute S302 and then execute S301, and may also execute S301 and S302 at the same time. The execution sequence of S301 and S302 is not limited in the embodiment of the present application.

According to the communication method provided by the embodiment of the application, the terminal equipment can determine the first RLC entity which has the radio link problem and the second RLC entity which has no radio link problem. In the case where a radio link problem occurs in the first RLC entity, the terminal apparatus transmits uplink data through the second RLC entity. Because the second RLC entity does not have the radio link problem, the phenomenon of uplink data transmission failure does not exist, and air interface resources can be saved. Alternatively, the terminal device can determine the target set of cells. And under the condition that the first RLC entity has a radio link problem, the terminal equipment transmits uplink data through the target cell set. Since the target cell set is a set of cells except for the cell corresponding to the first RLC entity in the allowed serving cell set for uplink data, the RLC entity corresponding to the cell in the target cell set does not have a radio link problem, and when uplink data is transmitted through the cell in the target cell set, the phenomenon of uplink data transmission failure does not occur, and air interface resources can be saved.

In some embodiments, the terminal device does not transmit uplink data through the first RLC entity or through a cell in the allowed serving cell set of the first RLC entity for a preset time period.

In this case, S303 may be specifically implemented as: and in the duration 1, the terminal equipment sends uplink data to the network equipment through the second RLC entity. Accordingly, the network device receives the uplink data from the terminal device.

Wherein, the duration 1 is a duration for prohibiting sending uplink data to the network device through the first RLC entity. Duration 1 may be the timed duration for starting the first timer. Duration 1 may also be a preset first time window. The duration 1 may also be a preset first counter, and the first counter is used to record the number of time units, where the time units may be time slots or subframes.

Illustratively, the network device pre-configures the terminal device with a first timer. After the terminal device executes S301, a first timer is started. During the operation of the first timer, the terminal equipment transmits uplink data to the network equipment through the second RLC entity, and the terminal equipment limits the transmission of the uplink data to the network equipment through the first RLC entity.

In this case, S305 may be implemented as: in duration 2, the terminal device sends uplink data to the network device through the cells in the target cell set. Accordingly, the network device receives the uplink data from the terminal device.

Wherein, the duration 2 is a duration for prohibiting sending uplink data to the network device through the cell corresponding to the first RLC entity. Duration 2 may be the timed duration for starting the second timer. Duration 2 may also be a preset second time window. The duration 2 may also be a preset second counter for recording the number of time units. Here, the time period 2 may be the same as or different from the time period 1.

Illustratively, the network device pre-configures the terminal device with the second timer. After the terminal device performs S301, the second timer is started. And during the running period of the second timer, the terminal equipment sends uplink data to the network equipment through the cells in the target cell set. That is, the terminal device restricts uplink data transmission to the network device through the cells in the allowed serving cell set of the first RLC entity.

Because the channel state is changed, the channel of the cell corresponding to the first RLC entity still has a problem within a preset time length after the terminal device determines that the radio link problem occurs to the first RLC entity. If the terminal device still sends uplink data from the first RLC entity or the cell in the allowed serving cell set of the first RLC entity, the probability of uplink data transmission failure is high. That is, within the preset time length, the terminal device does not send uplink data through the first RLC entity, and the terminal device also does not send uplink data through a cell in the allowed serving cell set of the first RLC entity, and sends uplink data through the second RLC entity or through a cell other than the allowed serving cell set of the first RLC entity, so as to avoid data transmission failure and save air interface resources. After the preset time length is exceeded, the probability that the channel of the cell corresponding to the first RLC entity is recovered to be normal is high. If the terminal device sends uplink data from the first RLC entity or the cell in the allowed serving cell set of the first RLC entity, the probability of successful uplink data transmission is high, and it is not necessary to limit sending uplink data from the first RLC entity or the cell in the allowed serving cell set of the first RLC entity, and effective data transmission can be guaranteed.

In some embodiments, the terminal device is also capable of retransmitting the uplink data. For the scenario that uplink data is sent by the second RLC entity, referring to fig. 5(a), the communication method in the embodiment of the present application further includes S306 a:

s306a, when the duration 3 times out, the terminal device retransmits the uplink data through the second RLC entity. Correspondingly, when the duration 3 is over, the network device repeatedly receives the uplink data from the terminal device.

Where duration 3 may be the timing duration for starting the third timer. Duration 3 may also be a preset third time window. Duration 3 may also be a preset third counter for recording the number of time units.

Illustratively, the network device pre-configures the terminal device with a third timer. The uplink data is URLLC traffic data, and after the terminal device executes S303, the third timer is started. And when the third timer is overtime, the terminal equipment retransmits the URLLC service data to the network equipment through the second RLC entity.

For a scenario in which uplink data is sent through a cell in a target cell set, referring to fig. 5(b), the communication method in the embodiment of the present application further includes S306 b:

s306b, when the time length 4 is overtime, the terminal equipment retransmits the uplink data through the cells in the target cell set. Correspondingly, when the duration 4 is over, the network device repeatedly receives the uplink data from the terminal device.

Where the duration 4 may be a timing duration for starting the fourth timer. Duration 4 may also be a preset fourth time window. The duration 4 may also be a preset fourth counter for recording the number of time units. Here, the time length 4 may be the same as or different from the time length 3.

Illustratively, the network device pre-configures the terminal device with a fourth timer. The uplink data is the first indication information, and after the terminal device executes S305, the fourth timer is started. When the fourth timer expires, the terminal device sends the first indication information through the cells in the target cell set (i.e., the cells in the allowed serving cell set corresponding to the first indication information, except for the allowed serving cell set of the first RLC entity).

Therefore, the terminal equipment can ensure that the network equipment can receive the uplink data by retransmitting the uplink data, and the data transmission reliability is improved.

In addition, in order to avoid that the terminal device always retransmits uplink data, referring to fig. 5(a), for a scenario where the uplink data is transmitted through the second RLC entity, after the terminal device executes S306a, the communication method in the embodiment of the present application further includes S307. For the scenario that uplink data is sent through the cells in the target cell set, referring to fig. 5(b), after the terminal device executes S306b, the communication method in the embodiment of the present application further includes S307:

and S307, when the terminal equipment determines that the preset condition is met, the terminal equipment stops retransmitting the uplink data to the network equipment. Accordingly, the network device stops receiving the uplink data from the terminal device.

Wherein the preset condition comprises at least one of the following conditions:

the retransmission times executed by the first RLC entity and the second RLC entity are less than or equal to a first preset value. That is, after the radio link problem occurs on the first RLC entity, the terminal device resets the number of retransmissions of the first RLC entity, and re-counts the number of retransmissions of the first RLC entity. If the number of times of retransmission performed by the first RLC entity is less than or equal to the first preset value, it indicates that the radio link problem on the first RLC entity is solved.

The second and first RLC entities are in a deactivated state. That is, the first RLC entity does not have a function of transmitting data.

And the PDCP copy function of the DRB associated with the third RLC entity is in a deactivated state. That is, the DRB associated with the first RLC entity does not have the PDCP copy function.

And the PDCP copy function of the SRB associated with the fourth RLC entity is in a deactivated state. That is, the SRB associated with the first RLC entity does not have PDCP copy function.

And the cells corresponding to the fifth and the first RLC entities are in a deactivated state. Here, the cell corresponding to the first RLC entity refers to a set of allowed serving cells corresponding to the LCH of the first RLC entity. The cell corresponding to the first RLC entity does not have a function of transmitting data.

And suspending the data transmission process of the cell corresponding to the sixth RLC entity. That is, the terminal device stops the process of transmitting data on the cell corresponding to the first RLC entity.

And seventhly, the times of retransmitting the uplink data reach a second preset value. Here, the second preset value may be preset value 3.

Here, when the uplink data is the first indication information, the preset condition may be at least one of the first to seventh items. If the terminal device determines that the radio link problem on the first RLC entity is solved, the terminal device does not need to send the first indication information to the network device. Or, if the network device successfully receives the first indication information from the terminal device, the network device sends the first activation indication information to the terminal device, or the network device indicates the terminal device to suspend the data transmission process of the cell corresponding to the first RLC entity. The deactivation indication information is used for indicating to deactivate the first RLC entity, or the PDCP copy function of the DRB associated with the first RLC entity, or the PDCP copy function of the SRB associated with the first RLC entity, or the cell corresponding to the first RLC entity. At this time, the terminal device does not need to send the first indication information to the network device. Or when the retransmission times of the first indication information reach a preset value 3, the terminal device considers that the network device has successfully received the first indication information, and the terminal device stops retransmitting the first indication information. Accordingly, the network device stops receiving the first indication information from the terminal device.

When the upstream data is duplicated data, such as DRB data, the preset condition may be the seventh item. And when the retransmission times of the DRB data reach a preset value 3, the terminal equipment stops retransmitting the DRB data. Accordingly, the network device stops receiving the DRB data from the terminal device.

It should be noted that the first RLC entity associated with the SRB and the first RLC entity associated with the DRB are different RLC entities, but both RLC entities have radio link problems. The third item and the fourth item in the preset conditions are applicable to a scenario that the terminal device configures a main RLC entity and a non-main RLC entity. Other items in the preset conditions are applicable to a scenario that the terminal device is configured with at least two RLC entities.

Therefore, when the terminal equipment determines that the preset condition is met, the terminal equipment does not retransmit the uplink data any more, and the problem of air interface resource waste caused by repeated retransmission of the uplink data is avoided.

In some embodiments, after the terminal device performs S301, the terminal device may perform different processing steps to limit the first RLC entity from sending uplink data without waiting for the first deactivation indication information sent by the network device. Referring to fig. 6, the communication method according to the embodiment of the present application further includes S308 and/or S309:

s308, the terminal equipment executes deactivation processing.

Specifically, the terminal device deactivates the first RLC entity, so that the first RLC entity does not transmit uplink data. Or the terminal equipment deactivates the PDCP copy function of the DRB associated with the first RLC entity, so that the first RLC entity cannot transmit DRB data. Or the terminal equipment deactivates the PDCP copy function of the SRB associated with the first RLC entity, so that the first RLC entity cannot transmit SRB data. Or the terminal equipment deactivates the cell corresponding to the first RLC entity, so that the cell corresponding to the first RLC entity does not transmit uplink data, thereby avoiding unnecessary transmission failure.

It should be noted that, in the embodiment of the present application, the deactivation processing refers to that a deactivation processing object is not adopted to send corresponding data. For example, the deactivation processing object is the first RLC entity. The terminal equipment deactivates the first RLC entity, that is, the terminal equipment does not use the first RLC entity to transmit uplink data. The terminal equipment deactivates the PDCP copy function of the DRB associated with the first RLC entity, that is, the terminal equipment does not use the first RLC entity to send DRB data.

S309, the terminal equipment suspends the data transmission process of the cell corresponding to the first RLC entity.

Here, the terminal device stops the data transmission procedure of the cell corresponding to the first RLC entity, but does not release the data transmission resource.

Therefore, after the terminal equipment executes the deactivation processing or suspends the corresponding data sending process, the first RLC entity can not transmit the uplink data, thereby avoiding unnecessary transmission failure and saving air interface resources.

The embodiment of the application provides another communication method, which is applied to the data transmission process of RLC failure. Referring to fig. 7, the communication method includes the steps of:

s300, the network equipment sends RRC information to the terminal equipment. Accordingly, the terminal device receives the RRC message from the network device.

S301, the terminal device determines that a radio link problem occurs on a first RLC entity of the PDCP copy function.

S310, the terminal device switches the BWP of the cell corresponding to the first RLC entity.

Here, after the terminal device executes S301, S310 may be executed without waiting for information issued by the network device. The terminal equipment performs BWP switching on the cell corresponding to the first RLC entity so as to switch to BWP without radio link problem. Here, the BWP after the handover may be the BWP indicated by the network device, or the BWP determined by the terminal device based on the preset rule.

S311, the terminal device sends uplink data to the network device through the first RLC entity after BWP switching.

The uplink data includes SRB data and/or DRB data. Here, the SRB data is SRB data configured with a PDCP copy function. The DRB data is DRB data configured with a PDCP copy function.

For example, if the DRB1 configures the PDCP replication function, and a radio link problem occurs in a first RLC entity associated with the DRB1, a cell corresponding to the first RLC entity performs BWP handover, the PDCP PDU of the DRB1 may be transmitted to the network device from the cell after the handover by the cell corresponding to the first RLC entity.

According to the communication method provided by the embodiment of the application, no problem exists in a radio link in a frequency band where a cell corresponding to a first RLC entity after BWP handover is located. The terminal device can send uplink data to the network device through the first RLC entity after BWP switching, and thus, a transmission failure phenomenon does not exist, so that air interface resources are saved, and robust transmission of the uplink data is realized.

The above description is for the RLC failure handling procedure. In the related art, the radio link problem may also be UL LBT failure. The embodiment of the present application provides another communication method, which is applied in a data transmission process when an UL LBT failure occurs. Referring to fig. 8, the communication method includes the steps of:

s800, the network equipment sends RRC information to the terminal equipment. Accordingly, the terminal device receives the RRC message from the network device.

Wherein the RRC message includes configuration information of the PDCP copy function. Here, the specific implementation of S800 may refer to the related description of S300, and is not described herein again.

S801, the terminal device determines that a radio link problem occurs in a first cell of the PDCP copy function.

And the first cell is a secondary cell which is the cell in the allowable service cell set.

Illustratively, for each secondary cell in the allowed serving cell set, the terminal device determines whether there is LBT failure on each secondary cell within a preset time period. If the terminal device determines that the number of LBT failures in a certain cell reaches preset value 2 within a preset time period, the terminal device determines that UL LBT failures occur in the cell, that is, a radio link problem occurs in the cell.

S802, the terminal equipment determines a second cell of the PDCP copy function.

The second cell is a cell which is configured by the RRC message and has no radio link problem in at least two cells. That is, the first cell and the second cell are different cells. The first cell and the second cell may correspond to the same RLC entity or different RLC entities.

And S803, the terminal equipment sends uplink data to the network equipment through the second cell. Accordingly, the network device receives the uplink data from the terminal device.

The uplink data includes SRB data and/or DRB data. Here, the SRB data is SRB data configured with a PDCP copy function. The DRB data is DRB data configured with a PDCP copy function.

Illustratively, the SRB data includes second indication information. The second indication information is used to indicate that a radio link problem occurs on the first cell. The second indication information comprises a cell identity, or a bitmap of cell identities. Wherein the cell identification is used to identify the first cell in which the UL LBT failure occurred. In the bit map of the cell identifier, each bit corresponds to a cell identifier. If the value of a bit is 1, the first cell identified by the cell identifier corresponding to the bit has an UL LBT failure. The second indication information further includes either a BWP flag, or a bitmap of the BWP flag. Wherein the BWP identification is used to identify the BWP where the UL LBT failure occurred. In the bit map of BWP identifications, each bit may correspond to one BWP identification. If the value of a bit is 1, the BWP corresponding to the bit identifies that an UL LBT failure has occurred on the identified BWP. The second indication is transmitted via SRB 1. Alternatively, in the case where the terminal device is configured with the SRB3, the second indication information may be transmitted through the SRB 3.

According to the communication method provided by the embodiment of the application, the terminal equipment can determine the first cell with the wireless link problem and the second cell without the wireless link problem. Therefore, under the condition that the first cell has the radio link problem, the terminal equipment sends the uplink data through the second cell, and the phenomenon of uplink data transmission failure does not exist because the second cell has no radio link problem, so that air interface resources are saved.

In some embodiments, the first RLC entity corresponding to the first cell is different from the second RLC entity corresponding to the second cell. Here, in the case where all cells in the set of allowed serving cells of the LCH of the primary RLC entity are secondary cells, the first RLC entity may be the primary RLC entity and the second RLC entity is an non-primary RLC entity. That is, the first cell is a cell in the set of allowed serving cells for the LCH of the primary RLC entity. The second cell is a cell in the set of allowed serving cells for the LCH of a certain non-primary RLC entity. Alternatively, the first RLC entity and the second RLC entity are both different RLC entities. That is, the first cell is a cell in the set of allowed serving cells for the LCH of a certain non-primary RLC entity. The second cell is a cell in the set of allowed serving cells for the LCH of another non-primary RLC entity or a cell in the set of allowed serving cells for the LCH of the primary RLC entity.

Therefore, the terminal equipment generates uplink data through the cell corresponding to the second RLC entity, and because the cell corresponding to the second RLC entity does not generate the radio link problem, the success of uplink data transmission can be ensured under the condition that the uplink data are sent through the cell corresponding to the second RLC entity, and unnecessary transmission failure is avoided.

In some embodiments, referring to fig. 9, a communication method according to an embodiment of the present application further includes the following steps:

s804, the terminal equipment determines a first RLC entity according to the LCH associated with the first cell.

Here, one RLC entity corresponds to one LCH. One LCH corresponds to one or more cells in the allowed serving cell set. Therefore, the terminal equipment can determine which LCH the first cell is associated with according to the first cell with the radio link problem, and further determine the first RLC entity.

Illustratively, the terminal device establishes a plurality of LCHs, each LCH having a corresponding set of allowed cells. For example, the set of allowed serving cells for LCH1 includes cell 1 and cell 2, and the set of allowed serving cells for LCH2 includes cell 1 and cell 3. If the first cell is cell 1, that is, if the radio link problem occurs in cell 1, the RLC entity 1 corresponding to LCH1 and the RLC entity 2 corresponding to LCH1 are both the first RLC entities.

In order to ensure that uplink data is not transmitted from the first RLC entity, the terminal device further performs S308 and/or S309.

Therefore, after the terminal equipment executes the deactivation processing or suspends the corresponding data sending process, the first RLC entity can not transmit the uplink data, thereby avoiding unnecessary transmission failure and saving air interface resources.

In some embodiments, the correspondence between the LCH and the cell is configured by RRC messages. And the terminal equipment configures the corresponding relation between the LCH and the cell according to the RRC message. The terminal equipment can also update the corresponding relation between the LCH and the cell. Referring to fig. 10, the communication method according to the embodiment of the present application further includes S805:

s805, the terminal device deletes the correspondence between the LCH of the first RLC entity and the first cell.

The first RLC entity is an RLC entity corresponding to the first cell.

Illustratively, in the case where the first cell is determined to be cell 1, the first RLC entity includes RLC entity 1 and RLC entity 2. After the terminal device deletes the correspondence between the LCH of the first RLC entity and the first cell, the set of allowed serving cells corresponding to the LCH1 includes cell 2 but not cell 1. The set of allowed serving cells for LCH2 includes cell 3 and does not include cell 1.

It should be noted that, if the UL LBT failure occurs in all allowed serving cell sets corresponding to the LCH of the first RCL entity, the terminal device triggers the RRC reestablishment procedure.

Therefore, after the correspondence between the LCH of the first RLC entity and the first cell is deleted, it can be ensured that the cells in the allowed serving cell set corresponding to the LCH of each RLC entity are cells without radio link problems, and uplink data can be transmitted through the cells in the allowed serving cell set corresponding to the LCH of any one RLC entity, which can ensure successful transmission of the uplink data, avoid unnecessary transmission failure, and save air interface resources.

The above-mentioned scheme provided by the embodiment of the present application is introduced mainly from the perspective of interaction between network elements. Correspondingly, the embodiment of the present application further provides a communication device, where the communication device may be a network element in the foregoing method embodiment, or a device including the foregoing network element, or a component that can be used for the network element. It is to be understood that the communication device comprises corresponding hardware structures and/or software modules for performing the respective functions in order to realize the above-mentioned functions. Those of skill in the art would readily appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as hardware or combinations of hardware and computer software. Whether a function is performed as hardware or computer software drives hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

Fig. 11 shows a schematic structural diagram of a communication apparatus 1100. The communication device 1100 includes a transceiver module 1101 and a processing module 1102.

For example, taking the communication apparatus 1100 as the terminal device in fig. 3 in the above method embodiment as an example,

the processing module 1102 is configured to determine that a radio link problem occurs on a first RLC entity of the PDCP duplication function. The processing module 1102 is configured to determine a second RLC entity of the PDCP duplication function. The transceiver module 1101 is configured to send uplink data to the network device through the second RLC entity. Wherein, the second RLC entity is an RLC entity without radio link problem.

In one possible design, the transceiver module 1101 is configured to transmit uplink data to the network device through the second RLC entity, and includes: and the uplink data sending unit is configured to send uplink data to the network device through the second RLC entity within a first time period, where the first time period is a time period during which the uplink data sending to the network device through the first RLC entity is prohibited.

In one possible design, the transceiver module 1101 is further configured to retransmit the uplink data when the second duration expires.

In a possible design, the processing module 1102 determines that the preset condition is met, and the transceiver module 1101 is further configured to stop retransmitting the uplink data when the processing module 1102 determines that the preset condition is met. Wherein the preset condition satisfies at least one of the following conditions: the retransmission times executed by the first RLC entity is less than or equal to a first preset value, the first RLC entity is in a deactivated state, the PDCP copy function of the DRB associated with the first RLC entity is in a deactivated state, the PDCP copy function of the SRB associated with the first RLC entity is in a deactivated state, the cell corresponding to the first RLC entity is in a deactivated state, the data transmission process of the cell corresponding to the first RLC entity is suspended, and the uplink data retransmission times reach a second preset value.

In one possible design, the processing module 1102 is further configured to deactivate the first RLC entity, or deactivate a PDCP copy function of a DRB associated with the first RLC entity, or deactivate a PDCP copy function of a SRB associated with the first RLC entity, or deactivate a cell corresponding to the first RLC entity; alternatively, the processing module 1102 is further configured to suspend a data transmission procedure of a cell corresponding to the first RLC entity.

For example, taking the communication apparatus 1100 as the terminal device in fig. 4 in the above method embodiment as an example,

the processing module 1102 is configured to determine that a radio link problem occurs on a first RLC entity of the PDCP duplication function. The processing module 1102 is also configured to determine a target set of cells. The transceiver module 1101 is configured to send uplink data to the network device through a cell in the target cell set. The target cell set is a set of cells except for a cell corresponding to the first RLC entity in the allowed serving cell set of uplink data, and no radio link problem occurs in the RLC entity corresponding to the cell in the target cell set.

In one possible design, the transceiver module 1101 is configured to transmit uplink data to a network device through a cell in a target cell set, and includes: and the first RLC entity is configured to send uplink data to the network device through the cell in the target cell set within a first duration, where the first duration is a duration for prohibiting sending the uplink data to the network device through the cell corresponding to the first RLC entity.

In one possible design, transceiver module 1101 is further configured to retransmit the uplink data when the fourth time duration expires.

In a possible design, the processing module 1102 is further configured to determine that a preset condition is met, and the transceiver module 1101 is further configured to stop retransmitting the uplink data when the processing module 1102 determines that the preset condition is met. Wherein the preset condition satisfies at least one of the following conditions: the retransmission times executed by the first RLC entity is less than or equal to a first preset value, the first RLC entity is in a deactivated state, the PDCP copy function of the DRB associated with the first RLC entity is in a deactivated state, the PDCP copy function of the SRB associated with the first RLC entity is in a deactivated state, the cell corresponding to the first RLC entity is in a deactivated state, the data transmission process of the cell corresponding to the first RLC entity is suspended, and the uplink data retransmission times reach a second preset value.

In one possible design, the processing module 1102 is further configured to deactivate the first RLC entity, or deactivate a PDCP copy function of a DRB associated with the first RLC entity, or deactivate a PDCP copy function of a SRB associated with the first RLC entity, or deactivate a cell corresponding to the first RLC entity; alternatively, the processing module 1102 is further configured to suspend a data transmission procedure of a cell corresponding to the first RLC entity.

For example, taking the communication apparatus 1100 as the terminal device in fig. 7 in the above method embodiment as an example,

the processing module 1102 is configured to determine that a radio link problem occurs on a first RLC entity of the PDCP copying function, and the processing module 1102 is further configured to switch a BWP in which a cell corresponding to the first RLC entity is located. The transceiving module 1101 is configured to send uplink data to the network device through the first RLC entity after the BWP handover.

For example, taking the communication apparatus 1100 as the terminal device in fig. 8 in the above method embodiment as an example,

the processing module 1102 is configured to determine that a radio link problem occurs on a first cell of the PDCP duplication function. The processing module 1102 is further configured to determine a second cell of the PDCP duplication function. The transceiver module 1101 is configured to send uplink data to the network device through the second cell. Wherein the second cell is a cell in which no radio link problem occurs.

In one possible design, the processing module 1102 may be further configured to determine the first RLC entity based on the LCH associated with the first cell. The processing module 1102 is further configured to deactivate the first RLC entity, or deactivate a PDCP copy function of the DRB associated with the first RLC entity, or deactivate a PDCP copy function of the SRB associated with the first RLC entity, or the processing module 1102 is further configured to suspend a data transmission process of a cell corresponding to the first RLC entity.

In one possible design, the processing module 1102 is further configured to delete a correspondence between an LCH of the first RLC entity and the first cell, where the first RLC entity is an RLC entity corresponding to the first cell.

All relevant contents of each step related to the above method embodiment may be referred to the functional description of the corresponding functional module, and are not described herein again.

It should be understood that the processing module 1102 in the embodiments of the present application may be implemented by a processor or a processor-related circuit component, and the transceiver module 1101 may be implemented by a transceiver or a transceiver-related circuit component.

As shown in fig. 12, an embodiment of the present application further provides a communication apparatus 1200, where the communication apparatus is implemented as a terminal device, the communication apparatus 1200 includes a processor 1210, a memory 1220 and a transceiver 1230. The memory 1220 stores instructions or programs, and the processor 1210 executes the instructions or programs stored in the memory 1220. When the instructions or programs stored in the memory 1220 are executed, the processor 1210 is configured to perform the operations performed by the processing module 1102 in the above embodiments, and the transceiver 1230 is configured to perform the operations performed by the transceiver module 1101 in the above embodiments.

It should be understood that the communication apparatus 1100 or the communication apparatus 1200 of the embodiment of the present application may correspond to the terminal device in the communication method of fig. 3 of the embodiment of the present application, and the operations and/or functions of the respective modules in the communication apparatus 1100 or the communication apparatus 1200 are respectively for realizing the respective flows of the respective methods in fig. 3; alternatively, the communication apparatus 1100 or the communication apparatus 1200 of the embodiment of the present application may correspond to the terminal device in the communication method of fig. 4 of the embodiment of the present application, and the operation and/or function of each module in the communication apparatus 1100 or the communication apparatus 1200 are respectively for realizing the corresponding flow of each method in fig. 4; alternatively, the communication apparatus 1100 or the communication apparatus 1200 of the embodiment of the present application may correspond to the terminal device in the communication method of fig. 7 of the embodiment of the present application, and the operation and/or function of each module in the communication apparatus 1100 or the communication apparatus 1200 are respectively for realizing the corresponding flow of each method in fig. 7; alternatively, the communication apparatus 1100 or the communication apparatus 1200 according to the embodiment of the present application may correspond to the terminal device in the communication method according to fig. 8 according to the embodiment of the present application, and the operation and/or the function of each module in the communication apparatus 1100 or the communication apparatus 1200 are respectively to realize the corresponding flow of each method according to fig. 8. For brevity, no further description is provided herein.

When the communication apparatus is a terminal device, fig. 13 shows a simplified structural diagram of the terminal device. For easy understanding and illustration, in fig. 13, the terminal device is exemplified by a mobile phone. As shown in fig. 13, the terminal device includes a processor, a memory, a radio frequency circuit, an antenna, and an input-output device. The processor is mainly used for processing communication protocols and communication data, controlling the terminal equipment, executing software programs, processing data of the software programs and the like. The memory is used primarily for storing software programs and data. The radio frequency circuit is mainly used for converting baseband signals and radio frequency signals and processing the radio frequency signals. The antenna is mainly used for receiving and transmitting radio frequency signals in the form of electromagnetic waves. Input and output devices, such as touch screens, display screens, keyboards, etc., are used primarily for receiving data input by a user and for outputting data to the user. It should be noted that some kinds of terminal devices may not have input/output devices.

When data needs to be sent, the processor performs baseband processing on the data to be sent and outputs baseband signals to the radio frequency circuit, and the radio frequency circuit performs radio frequency processing on the baseband signals and sends the radio frequency signals to the outside in the form of electromagnetic waves through the antenna. When data is sent to the terminal equipment, the radio frequency circuit receives radio frequency signals through the antenna, converts the radio frequency signals into baseband signals and outputs the baseband signals to the processor, and the processor converts the baseband signals into the data and processes the data. For ease of illustration, only one memory and processor are shown in FIG. 13. In an actual end device product, there may be one or more processors and one or more memories. The memory may also be referred to as a storage medium or a storage device, etc. The memory may be provided independently of the processor, or may be integrated with the processor, which is not limited in this embodiment.

In the embodiment of the present application, the antenna and the radio frequency circuit having the transceiving function may be regarded as a transceiving unit of the terminal device, and the processor having the processing function may be regarded as a processing unit of the terminal device. As shown in fig. 13, the terminal device includes a transceiving unit 1310 and a processing unit 1320. The transceiving unit 1310 may also be referred to as a transceiver, a transceiving means, etc. The processing unit 1320 may also be referred to as a processor, a processing board, a processing module, a processing device, or the like. Alternatively, a device for implementing the receiving function in the transceiving unit 1310 may be regarded as a receiving unit, and a device for implementing the transmitting function in the transceiving unit 1310 may be regarded as a transmitting unit, that is, the transceiving unit 1310 includes a receiving unit and a transmitting unit. The transceiver unit 1310 may also be sometimes referred to as a transceiver, transceiving circuitry, or the like. A receiving unit may also be referred to as a receiver, a receiving circuit, or the like. A transmitting unit may also sometimes be referred to as a transmitter, or a transmitting circuit, etc.

It should be understood that the transceiving unit 1310 is configured to perform the transmitting operation and the receiving operation on the terminal device side in the above method embodiments, and the processing unit 1320 is configured to perform other operations besides the transceiving operation on the terminal device in the above method embodiments.

For example, in one implementation, the transceiving unit 1310 is configured to perform S300 and S303 in fig. 3, and/or the transceiving unit 1310 is further configured to perform other transceiving steps on the terminal device side in the embodiment of the present application. The processing unit 1320 is configured to execute S301 and S302 in fig. 3, and/or the processing unit 1320 is further configured to execute other processing steps on the terminal device side in the embodiment of the present application.

For another example, in another implementation manner, the transceiving unit 1310 is configured to perform S300 and S305 in fig. 4, and/or the transceiving unit 1310 is further configured to perform other transceiving steps on the terminal device side in this embodiment of the present application. The processing unit 1320 is configured to execute S301 and S304 in fig. 3, and/or the processing unit 1320 is further configured to execute other processing steps on the terminal device side in the embodiment of the present application.

For another example, in another implementation manner, the transceiving unit 1310 is configured to perform S300 and S311 in fig. 7, and/or the transceiving unit 1310 is further configured to perform other transceiving steps on the terminal device side in this embodiment of the present application. The processing unit 1320 is configured to execute S301 and S310 in fig. 7, and/or the processing unit 1320 is further configured to execute other processing steps on the terminal device side in the embodiment of the present application.

For another example, in another implementation manner, the transceiving unit 1310 is configured to perform S800 and S803 in fig. 8, and/or the transceiving unit 1310 is further configured to perform other transceiving steps on the terminal device side in this embodiment of the present application. The processing unit 1320 is configured to execute S801 and S802 in fig. 8, and/or the processing unit 1320 is further configured to execute other processing steps on the terminal device side in the embodiment of the present application.

When the communication device is a chip-like device or circuit, the device may comprise a transceiver unit and a processing unit. The transceiver unit may be an input/output circuit and/or a communication interface; the processing unit is an integrated processor or microprocessor or integrated circuit.

When the communication device in the embodiment of the present application is a terminal device, reference may be made to the device shown in fig. 14. As an example, the device may perform functions similar to processor 1210 of FIG. 12. In fig. 14, the apparatus includes a processor 1410, a transmit data processor 1420, and a receive data processor 1430. The processing module 1102 in the above embodiments may be the processor 1410 in fig. 14, and performs corresponding functions. The transceiver module 1101 in the above-described embodiment may be the transmission data processor 1420, and/or the reception data processor 1430 in fig. 14. Although fig. 14 shows a channel encoder, a channel decoder, a symbol generation module, and a channel estimation module, it is to be understood that these modules are not intended to limit the embodiments of the present application, but are merely illustrative.

FIG. 15 shows another form of embodiment of the present application. The processing device 1500 includes modules such as a modulation subsystem, a central processing subsystem, a peripheral subsystem, and a multimedia subsystem. The communication device in the embodiment of the present application may be used as a modulation subsystem therein. Specifically, the modulation subsystem may include a processor 1503 and an interface 1501. The processor 1503 performs the functions of the processing module 1102, and the interface 1501 performs the functions of the transceiver module 1101. As another variation, the modulation subsystem includes a memory 1502, a processor 1503, and a program stored in the memory 1502 and executable on the processor 1503, and the processor 1503 executes the program to implement the method on the terminal device side in the above method embodiment. It should be noted that the memory 1502 may be non-volatile or volatile, and may be located within the modulation subsystem or within the processing device 1500, as long as the memory 1502 is coupled to the processor 1503.

As another form of the embodiment of the present application, there is provided a computer-readable storage medium having stored thereon instructions that, when executed, perform the method on the terminal device side in the above-described method embodiment.

As another form of the embodiments of the present application, there is provided a computer program product containing instructions that, when executed, perform the method on the terminal device side in the above-described method embodiments.

When the communication apparatus in this embodiment of the present application is a network device, the network device may be as shown in fig. 16, and the communication apparatus 1600 includes one or more radio frequency units, such as a Remote Radio Unit (RRU) 1610 and one or more baseband units (BBUs) (which may also be referred to as digital units, DUs) 1620. The RRU1610 may be referred to as a transceiver module, which corresponds to the transceiver module 1101 in fig. 11, and may also be referred to as a transceiver, a transceiver circuit, or a transceiver, which may include at least one antenna 1611 and a radio frequency unit 1612. The RRU1610 portion is mainly used for transceiving radio frequency signals and converting the radio frequency signals into baseband signals, for example, for sending a random access response message to a terminal device. The BBU1620 is mainly used for performing baseband processing, controlling a base station, and the like. The RRU1610 and the BBU1620 may be physically located together or physically located separately, that is, distributed base stations.

The BBU1620 is a control center of the base station, and may also be referred to as a processing module, and may correspond to the processing module 1102 in fig. 11, and is mainly used for completing baseband processing functions, such as channel coding, multiplexing, modulation, spreading, and the like. For example, the BBU (processing module) may be configured to control the base station to perform an operation procedure related to the network device in the foregoing method embodiment, for example, to generate the foregoing random access response message.

In an example, the BBU1620 may be formed by one or more boards, and the boards may collectively support a radio access network of a single access system (e.g., an LTE network), or may respectively support radio access networks of different access systems (e.g., an LTE network, a 5G network, or other networks). BBU1620 also includes a memory 1621 and a processor 1622. The memory 1621 is used to store the necessary instructions and data. The processor 1622 is configured to control the base station to perform necessary actions, for example, to control the base station to execute the operation procedure related to the network device in the above method embodiment. The memory 1621 and processor 1622 may serve one or more boards. That is, the memory and processor may be provided separately on each board. Multiple boards may share the same memory and processor. In addition, each single board can be provided with necessary circuits.

It should be understood that the processor mentioned in the embodiments of the present application may be a Central Processing Unit (CPU), and may also be other general purpose processors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

It will also be appreciated that the memory referred to in the embodiments of the application may be either volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The non-volatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an electrically Erasable EPROM (EEPROM), or a flash memory. Volatile memory can be Random Access Memory (RAM), which acts as external cache memory. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), double data rate SDRAM, enhanced SDRAM, SLDRAM, Synchronous Link DRAM (SLDRAM), and direct rambus RAM (DR RAM).

It should be noted that when the processor is a general-purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, the memory (memory module) is integrated in the processor.

It should be noted that the memory described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

It should be understood that the term "and/or" herein is merely one type of association relationship that describes an associated object, meaning that three relationships may exist, e.g., a and/or B may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter related objects are in an "or" relationship.

It should be understood that, in the various embodiments of the present application, the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiments of the present application.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a read-only memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims (22)

1. A method of communication, comprising:

the terminal equipment determines that a radio link problem occurs on a first Radio Link Control (RLC) entity of a Packet Data Convergence Protocol (PDCP) copy function;

the terminal equipment determines a second RLC entity with the PDCP copying function, wherein the second RLC entity is an RLC entity without a radio link problem;

and the terminal equipment sends uplink data to network equipment through the second RLC entity.

2. The communication method according to claim 1, wherein the uplink data is first indication information, and the first indication information is used to indicate that a radio link problem occurs on the first RLC entity.

3. The communication method according to claim 1 or 2, wherein the terminal device sends uplink data to a network device through the second RLC entity, comprising:

and within a first time length, the terminal equipment sends the uplink data to the network equipment through the second RLC entity, wherein the first time length is the time length for forbidding sending the uplink data to the network equipment through the first RLC entity.

4. A communication method according to any of claims 1 to 3, characterized in that the method further comprises:

and when the second duration is overtime, the terminal equipment retransmits the uplink data.

5. The communication method of claim 4, wherein the method further comprises:

when a preset condition is met, the terminal equipment stops retransmitting the uplink data;

wherein the preset condition satisfies at least one of the following conditions:

the retransmission execution times of the first RLC entity is less than or equal to a first preset value;

the first RLC entity is in a deactivated state;

a PDCP copy function of a Data Radio Bearer (DRB) associated with the first RLC entity is in a deactivated state;

the PDCP copy function of a Signaling Radio Bearer (SRB) associated with the first RLC entity is in a deactivated state;

a cell corresponding to the first RLC entity is in a deactivated state;

the data transmission process of the cell corresponding to the first RLC entity is suspended;

and the times of retransmitting the uplink data reach a second preset value.

6. The communication method according to any one of claims 1 to 5, characterized in that the method further comprises:

the terminal equipment deactivates the first RLC entity, or deactivates a PDCP copy function of a DRB associated with the first RLC entity, or deactivates a PDCP copy function of a SRB associated with the first RLC entity, or deactivates a cell corresponding to the first RLC entity; alternatively, the first and second electrodes may be,

and the terminal equipment suspends the data transmission process of the cell corresponding to the first RLC entity.

7. A method of communication, comprising:

the terminal equipment determines that a radio link problem occurs on a first Radio Link Control (RLC) entity of a Packet Data Convergence Protocol (PDCP) copy function;

the terminal equipment switches the bandwidth part BWP where the cell corresponding to the first RLC entity is located;

and the terminal equipment sends uplink data to the network equipment through the first RLC entity after BWP switching.

8. A method of communication, comprising:

the terminal equipment determines that a radio link problem occurs on a first cell of a Packet Data Convergence Protocol (PDCP) copy function;

the terminal equipment determines a second cell of the PDCP copy function, wherein the second cell is a cell without a radio link problem;

and the terminal equipment sends uplink data to network equipment through the second cell.

9. The communications method of claim 8, wherein a first RLC entity corresponding to the first cell is different from a second RLC entity corresponding to the second cell.

10. The communication method of claim 9, wherein the method further comprises:

the terminal equipment determines the first RLC entity according to the logic channel LCH associated with the first cell;

and the terminal equipment deactivates the first RLC entity, or deactivates a PDCP copy function of a DRB associated with the first RLC entity, or deactivates a PDCP copy function of a SRB associated with the first RLC entity, or suspends a data transmission process of a cell corresponding to the first RLC entity.

11. The communication method of claim 8, wherein the method further comprises:

and the terminal equipment deletes the corresponding relation between the LCH of the first RLC entity and the first cell, wherein the first RLC entity is the RLC entity corresponding to the first cell.

12. A communications apparatus, comprising: means for performing the steps of any of claims 1 to 6.

13. A communications apparatus, comprising: a processor for invoking a program in a memory to cause the communication device to perform the communication method of any of claims 1 to 6.

14. A communications apparatus, comprising: a processor and an interface circuit for communicating with other devices, the processor being configured to perform the communication method of any one of claims 1 to 6.

15. A communications apparatus, comprising: means for performing the steps recited in claim 7.

16. A communications apparatus, comprising: a processor for invoking a program in a memory to cause the communication device to perform the communication method of claim 7.

17. A communications apparatus, comprising: a processor and an interface circuit for communicating with other devices, the processor being configured to perform the communication method of claim 7.

18. A communications apparatus, comprising: means for performing the steps of any of claims 8 to 11.

19. A communications apparatus, comprising: a processor for invoking a program in a memory to cause the communication device to perform the communication method of any one of claims 8 to 11.

20. A communications apparatus, comprising: a processor and an interface circuit for communicating with other devices, the processor being configured to perform the communication method of any one of claims 8 to 11.

21. A computer-readable storage medium characterized by storing a program that when called by a processor, executes the communication method of any one of claims 1 to 6, or executes the communication method of claim 7, or executes the communication method of any one of claims 8 to 11.

22. A computer program, characterized in that when said program is called by a processor, the communication method of any one of claims 1 to 6 is executed, or the communication method of claim 7 is executed, or the communication method of any one of claims 8 to 11 is executed.

Images