CN115694753A

CN115694753A - Communication method, communication apparatus, and storage medium

Info

Publication number: CN115694753A
Application number: CN202110860290.7A
Authority: CN
Inventors: 谌丽; 皮埃尔
Original assignee: Datang Mobile Communications Equipment Co Ltd
Current assignee: Datang Mobile Communications Equipment Co Ltd
Priority date: 2021-07-28
Filing date: 2021-07-28
Publication date: 2023-02-03

Abstract

The application provides a communication method, a communication device and a storage medium, wherein on a terminal side, the method comprises the following steps: determining that the terminal needs to autonomously activate PDCP repeat transmission; sending a first message to the network equipment, wherein the first message is used for requesting the network equipment to pre-allocate uplink resources for PDCP repeated transmission; and receiving a second message from the network equipment, wherein the second message indicates the uplink resource allocated by the network equipment. Therefore, before the PDCP repeat transmission is autonomously activated, the terminal requests the network equipment to allocate the uplink resources in advance based on the prediction of the PDCP repeat transmission which needs to be autonomously activated, so that the terminal can execute the PDCP repeat transmission in time based on the allocated uplink resources after the PDCP repeat transmission is autonomously activated.

Description

Communication method, communication apparatus, and storage medium

Technical Field

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

Background

In order to deal with the high-reliability Low-delay communication (URLLC) service with high requirements on delay and reliability, a Packet Data Convergence Protocol (PDCP) repeated transmission mechanism is introduced into the communication system. In the PDCP retransmission mechanism, the reliability of Data transmission is improved and the transmission delay is reduced by transmitting Protocol Data Units (PDUs) of the same PDCP layer through multiple paths.

In order to meet the requirements of time delay and reliability of URLLC service, the terminal can autonomously activate PDCP repeat transmission under the conditions of data packet loss, data packet transmission errors and the like. After autonomously activating the PDCP retransmission, the terminal may Request the network device for the uplink resource for the PDCP retransmission through a Scheduling Request (SR) procedure of the uplink shared resource.

However, the time consumed in the scheduling request process of the uplink shared resource is long, which causes that the terminal cannot transmit subsequent data packets in time according to the PDCP repeat transmission mode after autonomously activating the PDCP repeat transmission.

Disclosure of Invention

The application provides a communication method, a communication device and a storage medium, which are used for improving the allocation efficiency of uplink resources in PDCP repeat transmission autonomously activated by a terminal so that the PDCP repeat transmission can be executed by utilizing the uplink resources allocated by network equipment in time after the PDCP repeat transmission autonomously activated by the terminal.

In a first aspect, the present application provides a communication method, applied to a terminal, including:

determining that the terminal needs to autonomously activate PDCP repeat transmission;

sending a first message to the network equipment, wherein the first message is used for requesting the network equipment to pre-allocate uplink resources for PDCP (packet data convergence protocol) repeated transmission;

and receiving a second message from the network equipment, wherein the second message indicates the uplink resource allocated by the network equipment.

Optionally, determining that the terminal needs to autonomously activate PDCP retransmission includes:

and if the main RLC entity corresponding to the PDCP entity of the DRB is determined to meet the condition of triggering the pre-scheduling request, determining that the terminal needs to autonomously activate the PDCP repeated transmission.

Optionally, the determining that the main RLC entity corresponding to the PDCP entity of the DRB to be repeatedly transmitted satisfies the condition of triggering the pre-scheduling request includes at least one of the following:

determining that the channel quality of a main RLC entity corresponding to the PDCP entity is less than a quality threshold;

detecting an unauthorized frequency band LBT failure under the condition that a frequency band used for transmitting logical channel data on a main RLC entity is an unauthorized frequency band;

determining that uplink resources of a last data packet of a main RLC entity are preempted by other data packets;

and determining the cell sending the last data packet to trigger BFR.

determining that the terminal needs to convert the PDCP repeated transmission from the inactive state to the active state;

or, in case that the PDCP repeat transmission is in an active state, it is determined that the terminal needs to activate more secondary RLC entities for the PDCP repeat transmission.

Optionally, sending the first message to the network device includes:

and transmitting the first message through the pre-configured PUCCH resource.

Optionally, the PUCCH resource includes at least one of:

the network equipment configures SR resources of a target logical channel, wherein the target logical channel comprises logical channels corresponding to all auxiliary RLC entities used for repeated transmission of the DCP or logical channels corresponding to specified auxiliary RLC entities used for repeated transmission of the PDCP;

a PUCCH resource configured by the network device for transmitting the first message;

and the PUCCH resource of the cell group in which the cell corresponding to the secondary RLC entity for PDCP repeated transmission is located.

Optionally, the first message includes a pre-scheduling request, and the first message is sent to the network device, and includes at least one of the following:

canceling a pre-scheduling request after sending the first message;

and after the first message is sent, canceling the pre-scheduling request when new data arrives at a terminal buffer triggering buffer reporting request or SR (scheduling request) in a target logical channel, wherein the target logical channel comprises logical channels corresponding to all auxiliary RLC entities for PDCP (packet data convergence protocol) repeated transmission or logical channels corresponding to designated auxiliary RLC entities for PDCP repeated transmission.

Optionally, the first message includes a pre-scheduling request, and before determining that the terminal needs to autonomously activate PDCP retransmission, the communication method further includes:

receiving a third message from the network device, where the third message is used to configure PDCP repeated transmission of the terminal, and the third message indicates at least one of the following information:

whether the terminal is allowed to autonomously activate PDCP retransmission;

whether the terminal is allowed to trigger a pre-scheduling request and send a first message;

the secondary RLC entity that triggered the pre-scheduling request and sent the first message is allowed.

Optionally, after receiving the second message from the network device, the communication method further includes:

and if the terminal autonomously activates the PDCP repeat transmission, performing the PDCP repeat transmission on the uplink resource indicated by the second message.

Optionally, after performing PDCP retransmission on the uplink resource allocated by the network device, the communication method further includes:

receiving a fourth message of the network equipment, wherein the fourth message indicates that PDCP repeated transmission is deactivated;

deactivating the PDCP repeat transmission in response to the fourth message.

and if the terminal does not autonomously activate the PDCP repeated transmission, ignoring the uplink resource indicated by the second message.

In a second aspect, the present application provides a communication method, applied to a network device, including:

receiving a first message from a terminal, wherein the first message is used for requesting network equipment to allocate uplink resources in advance for PDCP repeated transmission;

allocating uplink resources in response to the first message;

and sending a second message to the terminal, wherein the second message indicates the uplink resource allocated by the network equipment.

Optionally, after receiving the first message from the terminal, the communication method further includes:

determining to activate PDCP duplicate transmission.

Optionally, after determining to activate PDCP duplicate transmission, the communication method further includes:

activating the repeated transmission of the next PDCP PDU of the DRB to be repeatedly transmitted;

or, activating PDCP repeated transmission of the DRB in the target time length;

or, a fourth message is sent to the terminal, and the fourth message indicates that PDCP repeated transmission is deactivated.

Optionally, the first message includes a pre-scheduling request, and before receiving the first message from the terminal, the communication method further includes:

sending a third message to the terminal, where the third message is used to configure PDCP retransmission of the terminal, and the third message indicates at least one of the following information:

whether the terminal is allowed to autonomously activate PDCP retransmission;

In a third aspect, the present application provides a communication apparatus, applied to a terminal, including a memory, a transceiver, and a processor:

a memory for storing a computer program;

a transceiver for transceiving data under the control of the processor;

a processor for reading the computer program in the memory and performing the following operations:

sending a first message to the network equipment, wherein the first message is used for requesting the network equipment to pre-allocate uplink resources for PDCP repeated transmission;

Optionally, the processor further performs the following operations:

and if the main RLC entity corresponding to the PDCP entity of the DRB is determined to meet the condition of triggering the pre-scheduling request, determining that the terminal needs to autonomously activate the PDCP repeat transmission.

Optionally, the processor further performs at least one of the following operations:

determining that uplink resources of a last data packet of a main RLC entity are occupied by other data packets;

and determining that the cell sending the last data packet triggers the beam failure recovery BFR.

Optionally, the processor further performs the following operations:

and transmitting the first message through the pre-configured PUCCH resource.

Optionally, the PUCCH resource includes at least one of:

the network equipment configures Scheduling Request (SR) resources to a target logical channel, wherein the target logical channel comprises logical channels corresponding to all auxiliary RLC entities used for PDCP repeated transmission or logical channels corresponding to specified auxiliary RLC entities used for PDCP repeated transmission;

Optionally, the first message includes a pre-scheduling request, and the processor further performs at least one of the following operations:

canceling a pre-scheduling request after sending the first message;

and after the first message is sent, canceling the pre-scheduling request when new data arrives at the terminal buffer triggering buffer reporting request or SR in a target logical channel, wherein the target logical channel comprises logical channels corresponding to all auxiliary RLC entities used for PDCP repeated transmission or logical channels corresponding to designated auxiliary RLC entities used for PDCP repeated transmission.

Optionally, the first message includes a pre-scheduling request, and the processor further performs the following operations:

receiving a third message from the network device, where the third message is used to configure PDCP retransmission for the terminal, and the third message indicates at least one of the following information:

whether the terminal is allowed to autonomously activate PDCP retransmission;

Optionally, the processor further performs the following operations:

and if the terminal autonomously activates the PDCP repeated transmission, carrying out the PDCP repeated transmission on the uplink resources allocated by the network equipment.

Optionally, the processor further performs the following operations:

deactivating the PDCP repeat transmission in response to the fourth message.

Optionally, the processor further performs the following operations:

and if the terminal does not autonomously activate the PDCP repeated transmission, ignoring the uplink resource which is pre-allocated by the network equipment and is used for the PDCP repeated transmission.

In a fourth aspect, the present application provides a communication apparatus, applied to a network device, including a memory, a transceiver, and a processor:

a memory for storing a computer program;

a transceiver for transceiving data under the control of the processor;

a processor for reading the computer program in the memory and performing the following:

allocating uplink resources in response to the first message;

Optionally, the processor further performs the following operations:

determining to activate PDCP duplicate transmission.

Optionally, the processor further performs the following operations:

or, activating PDCP repeated transmission of the DRB in the target time length;

or, a fourth message is sent to the terminal, wherein the fourth message indicates that the PDCP repeated transmission is deactivated.

whether the terminal is allowed to autonomously activate PDCP repeat transmission;

In a fifth aspect, the present application provides a communication apparatus, applied to a terminal, including:

the processing unit is used for determining that the terminal needs to autonomously activate PDCP repeated transmission;

a sending unit, configured to send a first message to a network device, where the first message is used to request the network device to pre-allocate uplink resources for PDCP retransmission;

a receiving unit, configured to receive a second message from the network device, where the second message indicates the uplink resource allocated by the network device.

Optionally, the processing unit is specifically configured to:

Optionally, the processing unit is specifically configured to perform at least one of the following operations:

the cell transmitting the last data packet is determined to trigger the BFR.

Optionally, the processing unit is specifically configured to:

alternatively, in case that PDCP repeated transmission is in an active state, it is determined that the terminal needs to activate more secondary RLC entities for PDCP repeated transmission.

Optionally, the sending unit is specifically configured to:

and transmitting the first message through the pre-configured PUCCH resources.

Optionally, the PUCCH resource includes at least one of:

Optionally, the first message includes a pre-scheduling request, and the sending unit is specifically configured to perform at least one of the following operations:

canceling a pre-scheduling request after the first message is sent;

Optionally, the first message includes a pre-scheduling request, and the receiving unit is further configured to:

whether the terminal is allowed to autonomously activate PDCP retransmission;

Optionally, the sending unit is further configured to:

Optionally, the receiving unit is further configured to:

a processing unit further to:

deactivating the PDCP repeat transmission in response to the fourth message.

Optionally, the processing unit is further configured to:

In a sixth aspect, the present application provides a communication apparatus, applied to a network device, including:

a receiving unit, configured to receive a first message from a terminal, where the first message is used to request a network device to pre-allocate uplink resources for PDCP retransmission;

a processing unit, configured to allocate uplink resources in response to the first message;

and the sending unit is used for sending a second message to the terminal, wherein the second message indicates the uplink resource allocated by the network equipment.

Optionally, the processing unit is further configured to:

determining to activate PDCP duplicate transmission.

Optionally, the processing unit is further configured to:

alternatively, the processing unit is further configured to:

activating PDCP repeated transmission of the DRB in the target time length;

or, the sending unit is further configured to:

and sending a fourth message to the terminal, wherein the fourth message indicates that the PDCP repeated transmission is deactivated.

Optionally, the first message includes a pre-scheduling request, and the sending unit is further configured to:

and sending a third message to the terminal, wherein the third message is used for configuring PDCP repeated transmission of the terminal, and the third message indicates at least one of the following information:

whether the terminal is allowed to autonomously activate PDCP retransmission;

In a seventh aspect, the present application provides a processor-readable storage medium storing a computer program for causing a processor to perform the method of the first or second aspect.

In an eighth aspect, the present application provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of the first aspect or the method of the second aspect as described above.

In a ninth aspect, the present application provides a communication system comprising a network device as described in any of the above and at least one terminal as described in any of the above.

The application provides a communication method, a communication device and a storage medium, when determining that a terminal needs to autonomously activate PDCP repeat transmission, the terminal requests a network device to allocate uplink resources for the PDCP repeat transmission in advance and receives the uplink resources allocated by the network device. Therefore, when the PDCP repeat transmission is really autonomously activated, the terminal can utilize the pre-allocated uplink resource to execute the PDCP repeat transmission after autonomously activating the PDCP repeat transmission, and does not need to request the network equipment for the uplink resource and wait for the network equipment to allocate the uplink resource in an interactive mode with the network equipment after autonomously activating the PDCP repeat transmission, so that the efficiency of executing the PDCP repeat transmission after autonomously activating the PDCP repeat transmission by the terminal is improved.

It should be understood that what is described in the summary above is not intended to limit key or critical features of embodiments of the invention, nor is it intended to limit the scope of the invention. Other features of the present invention will become apparent from the following description.

Drawings

In order to more clearly illustrate the technical solutions in the present application or the prior art, the drawings required for the embodiments or the description of the prior art are briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and it is obvious for those skilled in the art that other drawings can be obtained according to the drawings without inventive labor.

FIG. 1 (a) is a diagram of a PDCP retransmission model under CA;

fig. 1 (b) is a schematic diagram of a PDCP repetition transmission model at DC;

FIG. 2 is an exemplary diagram of an SR process of uplink shared resources on time-frequency resources;

fig. 3 is a schematic view of an application scenario provided in an embodiment of the present application;

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

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

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

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

fig. 8 is a first exemplary diagram illustrating uplink resource pre-scheduling and PDCP retransmission performed by a terminal;

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

fig. 10 is a diagram illustrating a second example of uplink resource pre-scheduling and PDCP retransmission performed by the terminal;

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

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

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

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

Detailed Description

The term "and/or" in this application describes an association relationship of associated objects, meaning that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship.

In the embodiments of the present application, the term "plurality" means two or more, and other terms are similar thereto.

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

For the purpose of enhancing understanding of the embodiments of the present application, the PDCP repetition transmission will be explained briefly below.

Referring to fig. 1 (a) and 1 (b), fig. 1 (a) is a schematic diagram of a PDCP repeated transmission model in Carrier Aggregation (CA), and fig. 1 (b) is a schematic diagram of a PDCP repeated transmission model in Dual Connectivity (DC). In fig. 1 (a) and 1 (b), the number of duplicate transmission paths for PDCP duplicate transmission is taken as an example of 4.

As shown in fig. 1 (a) and fig. 1 (b), one Data Radio Bearer (DRB) of the PDCP layer corresponds to one PDCP entity, and one DRB respectively transmits through 4 Logical Channels (LCH) in a Radio Link Control (RLC) layer, where each Logical Channel corresponds to one RLC entity. For example, in fig. 1 (a) and 1 (b), the PDCP entity corresponds to 4 RLC entities: the logical channels of the RLC system are RLC1, RLC2, RLC3 and RLC4, and RLC1, RLC2, RLC3 and RLC4 correspond to the logical channels LCH1, LCH2, LCH3 and LCH4 respectively.

As shown in fig. 1 (a), in the PDCP retransmission model of CA, a plurality of logical channels corresponding to a DRB that is repeatedly transmitted are handled by one MAC entity at a Medium Access Control (MAC) layer. As shown in fig. 1 (b), in the PDCP repeated transmission model in DC, the logical channels corresponding to different nodes are mapped to the respective MAC entities of the nodes for transmission. The DC includes a Master Node (Master Node, main Node or Primary Node, MN or PN) or a Secondary Node (SN). As shown in fig. 1 (a) and 1 (b), data of logical channels corresponding to different RLC entities are mapped to different cells for transmission. In other words, there is a corresponding relationship between RLC entities and cells, and the cells corresponding to different RLC entities are different, where a cell is a Carrier unit (CC), and a different cell is a different Carrier. For example, in fig. 1 (a) and 1 (b), RLC1, RLC2, RLC3, and RLC4 correspond to cells cell1 (CC 1), cell2 (CC 2), cell3 (CC 3), and cell4 (CC 4), respectively.

Before PDCP retransmission activation, the RLC entity carrying DRB data is called a primary RLC entity, and the corresponding logical channel is a primary logical channel, which cannot be deactivated. After the PDCP is repeatedly transmitted, an RLC entity for transmitting a copied PDCP Protocol Data Unit (PDU) is called an auxiliary RLC entity, and a corresponding logical channel is an auxiliary logical channel.

Generally, the network device activates PDCP retransmission, and if the secondary RLC entity has data, the network device allocates uplink resources to the secondary RLC entity to implement actual implementation of uplink DRB PDCP retransmission. For URLLC service, considering that the network equipment cannot send the repeated transmission activation command and allocate uplink resources in time, the terminal autonomously activates PDCP repeated transmission. When the terminal autonomously activates PDCP retransmission, the network device does not know that the terminal activates PDCP retransmission, and the terminal needs to Request the network device for uplink resources for PDCP retransmission through a Scheduling Request (SR) procedure of uplink shared resources, so that the network device knows that the terminal autonomously activates PDCP retransmission and then allocates uplink resources for PDCP retransmission.

Hereinafter, the SR process of the uplink shared resource will be briefly described.

Referring to fig. 2, fig. 2 is an exemplary diagram of an SR process of an uplink shared resource on a time-frequency resource, where t in fig. 2 represents a time domain. With reference to fig. 2, the SR process of the uplink shared resource includes the following steps:

step 1, when uplink data arrives at a Buffer, a User Equipment (UE) triggers a Regular Buffer Status Report (Regular BSR), and further triggers an SR. Wherein, having uplink data to reach the buffer comprises: and the uplink data with high priority arrives at the buffer, and/or the uplink data arrives at the buffer under the condition that the buffer originally has no data.

And 2, the UE sends the SR on the special SR resource configured on the base station side.

Step 3, after receiving the SR, the base station allocates an Uplink resource, which is a Physical Uplink Shared Channel (PUSCH), to the UE through a Physical Downlink Control Channel (PDCCH).

And step 4, the UE sends BSR on the PUSCH allocated by the base station.

And step 5, the base station further allocates the PUSCH by using the PDCCH according to the BSR sent by the UE.

And step 6, the UE sends uplink data on the PUSCH allocated by the base station.

Therefore, the base station and the terminal interact for many times in the SR process of the uplink shared resource, which consumes a long time.

In the PDCP repeat transmission, after the terminal autonomously activates PDCP repeat transmission, it requests the network device for uplink resources used for PDCP repeat transmission through the SR process of the uplink shared resources. After the network device allocates uplink resources for PDCP retransmission, PDCP retransmission is performed on the allocated uplink resources. It can be seen that a long time delay exists between the time when the terminal autonomously activates PDCP retransmission and the time when the terminal executes PDCP retransmission, and for a service with a short period, for example, a service with a 5ms data packet arrival period, after the terminal autonomously activates PDCP retransmission, a subsequent data packet cannot be timely transmitted in a PDCP retransmission mode, which actually causes PDCP retransmission failure.

In order to solve the above problem, embodiments of the present application provide a communication method, an apparatus, and a storage medium, where a terminal requests a network device to pre-allocate uplink resources for PDCP retransmission when it is determined that PDCP retransmission needs to be autonomously activated, and the network device allocates uplink resources for PDCP retransmission in response to the request of the terminal. Therefore, after the terminal autonomously activates the PDCP repeat transmission, the PDCP repeat transmission can be executed in time by using the uplink resource without interacting with the network equipment to request the uplink resource after the PDCP repeat transmission is autonomously activated, so that the efficiency of executing the PDCP repeat transmission after the PDCP repeat transmission is autonomously activated by the terminal is improved.

The method and the device are based on the same application concept, and because the principles of solving the problems of the method and the device are similar, the implementation of the device and the method can be mutually referred, and repeated parts are not described again.

The technical scheme provided by the embodiment of the application can be suitable for various systems, particularly 5G systems. For example, suitable systems may be global system for mobile communications (GSM) systems, code Division Multiple Access (CDMA) systems, wideband Code Division Multiple Access (WCDMA) General Packet Radio Service (GPRS) systems, long Term Evolution (LTE) systems, LTE Frequency Division Duplex (FDD) systems, LTE Time Division Duplex (TDD) systems, long term evolution (long term evolution) systems, LTE-a systems, universal mobile systems (universal mobile telecommunications systems, UMTS), universal internet Access (world interoperability for microwave Access (WiMAX) systems, new Radio interface (NR) systems, etc. These various systems include terminals and network devices. The System may further include a core network portion, such as an Evolved Packet System (EPS), a 5G System (5 GS), and the like.

A terminal as referred to in embodiments of the present application may refer to a device providing voice and/or data connectivity to a user, a handheld device having a wireless connection capability, or other processing device connected to a wireless modem, etc. In different systems, the names of terminals may be different, for example, in a 5G system, a terminal may be called a User Equipment (UE). A wireless terminal, which may be a mobile terminal such as a mobile phone (or called a "cellular" phone) and a computer having a mobile terminal, for example, a portable, pocket, hand-held, computer-included or vehicle-mounted mobile device, may communicate with one or more Core Networks (CNs) via a Radio Access Network (RAN), and may exchange languages and/or data with the RAN. Examples of such devices include Personal Communication Service (PCS) phones, cordless phones, session Initiation Protocol (SIP) phones, wireless Local Loop (WLL) stations, and Personal Digital Assistants (PDAs). A wireless terminal may also be referred to as a system, a subscriber unit (subscriber unit), a subscriber station (subscriber station), a mobile station (mobile), a remote station (remote station), an access point (access point), a remote terminal (remote terminal), an access terminal (access terminal), a user terminal (user terminal), a user agent (user agent), and a user device (user device), which are not limited in this embodiment.

The network device according to the embodiment of the present application may be a base station, and the base station may include a plurality of cells for providing services to a terminal. A base station may also be referred to as an access point, or a device in an access network that communicates over the air-interface, through one or more sectors, with wireless terminals, or by other names, depending on the particular application. The network device may be configured to exchange received air frames with Internet Protocol (IP) packets as a router between the wireless terminal and the rest of the access network, which may include an Internet Protocol (IP) communication network. The network device may also coordinate attribute management for the air interface. For example, the network device according to the embodiment of the present application may be a Base Transceiver Station (BTS) in a Global System for Mobile communications (GSM) or a Code Division Multiple Access (CDMA), a network device (NodeB) in a Wideband Code Division Multiple Access (WCDMA), an evolved Node B (eNB) or an e-NodeB) in a Long Term Evolution (LTE) System, a 5G Base Station (gNB) in a 5G network architecture (next generation System), a Home evolved Node B (HeNB), a relay Node (relay Node), a Home Base Station (femto), a pico Base Station (pico), and the like, which are not limited in the embodiments of the present application. In some network configurations, a network device may include Centralized Unit (CU) nodes and Distributed Unit (DU) nodes, which may also be geographically separated.

Multiple Input Multiple Output (MIMO) transmission may be performed between the network device and the terminal by using one or more antennas, where the MIMO transmission may be Single User MIMO (SU-MIMO) or Multi-User MIMO (MU-MIMO). According to the form and the number of the root antenna combination, the MIMO transmission can be 2D-MIMO, 3D-MIMO, FD-MIMO or massive-MIMO, and can also be diversity transmission, precoding transmission, beamforming transmission, etc.

Referring to fig. 3, fig. 3 is a schematic view of an application scenario provided in an embodiment of the present application. As shown in fig. 3, the present embodiment provides a communication system, which includes a network device 310 and terminals 320, where the present embodiment takes 3 terminals 320 as an example. In the communication system, the terminal 320 and the network device 310 can improve the reliability of uplink data transmission by activating PDCP repeated transmission.

In the following, embodiments are used to describe how to solve the problem that the PDCP retransmission cannot be performed in time after the terminal autonomously activates the PDCP retransmission.

Referring to fig. 4, fig. 4 is a flowchart of a communication method according to an embodiment of the present application, and as shown in fig. 4, the method according to the embodiment may include:

s401, determining that the terminal needs to autonomously activate PDCP repeated transmission.

In this embodiment, the terminal may determine whether it may need to autonomously activate PDCP retransmission in a future time period according to the transmission condition of the uplink DRB, that is, predict whether it may need to activate PDCP retransmission in the future time period. And if the transmission condition of the DRB meets the condition of triggering the pre-scheduling request, determining that the terminal needs to autonomously activate the PDCP repeated transmission, otherwise, determining that the terminal does not need to autonomously activate the PDCP repeated transmission.

Optionally, the terminal may need to autonomously activate PDCP repeated transmission including: the terminal needs to change the PDCP repeated transmission from the inactive state to the active state, or the terminal needs to activate more secondary RLC entities for the PDCP repeated transmission in the active state.

Therefore, in a possible implementation manner of S401, determining that the terminal needs to autonomously activate PDCP repeated transmission includes: determining that the terminal needs to switch the PDCP repeat transmission from an inactive state to an active state, or determining that the terminal needs to autonomously activate more secondary RLC entities for the PDCP repeat transmission in a situation where the PDCP repeat transmission is in the active state. Thus, the present embodiment can improve the efficiency from the autonomous activation of PDCP retransmission to the performance of PDCP retransmission in different situations where the terminal autonomously activates PDCP retransmission.

Optionally, the transmission condition of the DRB satisfies a condition for triggering a pre-scheduling request, including that the main RLC entity corresponding to the PDCP entity of the DRB satisfies the condition for the pre-scheduling request.

Therefore, in another possible implementation manner of the above S401, if it is determined that the primary RLC entity corresponding to the PDCP entity of the DRB satisfies the condition for triggering the pre-scheduling request, it is determined that the terminal needs to autonomously activate PDCP retransmission. Therefore, by utilizing the characteristic that the DRB mainly transmits through the logic channel corresponding to the main RLC entity corresponding to the PDCP entity before the terminal autonomously activates the PDCP repeat transmission, the condition that the main RLC entity meets the pre-scheduling request can fully indicate that the terminal may need to autonomously activate the PDCP repeat transmission of the DRB.

Optionally, the condition of the pre-scheduling request includes at least one of the following: channel quality conditions, channel resource conditions, data transmission conditions, channel stability conditions. When the main RLC entity meets the channel quality condition, the channel quality of a logic channel corresponding to the main RLC entity is reflected to be poor; when the main RLC entity meets the channel resource condition, reflecting that the uplink resource of the logic channel corresponding to the main RLC entity is insufficient; when the main RLC entity meets the data sending condition, the data packet transmitted by the logic channel corresponding to the main RLC entity is reflected to be unsuccessfully sent; and when the main RLC entity meets the channel stability condition, reflecting that the logic channel corresponding to the main RLC entity is unstable. Therefore, whether the terminal needs to autonomously activate the repeated PDCP transmission or not is determined from one or more aspects, and the comprehensiveness and the accuracy of determining whether the terminal needs to autonomously activate the repeated PDCP transmission or not are improved.

Therefore, in a possible implementation manner of the S401, determining that the primary RLC entity corresponding to the PDCP entity of the DRB satisfies the condition for triggering the pre-scheduling request may include at least one of the following:

1) Determining that the channel quality of a main RLC entity corresponding to the PDCP entity is less than a quality threshold; 2) Detecting that a Listen Before Talk (LBT) failure of an unlicensed band is detected in a case where a band for transmitting logical channel data on a main RLC entity is the unlicensed band; 3) Determining that uplink resources of a last data packet of a main RLC entity are preempted by other data packets; 4) It is determined that the cell transmitting the last packet of the primary RLC entity triggered Beam Failure Recovery (BFR). Therefore, whether the terminal needs to autonomously activate the PDCP repeat transmission or not is measured, estimated or predicted from one or more aspects of channel quality, channel resources, data packet sending and channel stability, and the accuracy of determining whether the terminal needs to autonomously activate the PDCP repeat transmission or not is improved.

In this embodiment, when determining whether the channel quality of the main RLC entity corresponding to the PDCP entity is less than the quality threshold, the channel quality detection may be performed on the terminal. In the detection process, the channel quality parameter may be obtained by performing channel quality detection on all or Part of beams (Beam) on a cell or Bandwidth Part (BWP) where logical channel data transmission of the primary RLC entity is performed. It is determined whether the channel quality parameter is less than a quality threshold. If the channel quality parameter is less than the quality threshold, it may be determined that the primary RLC entity satisfies the condition that triggered the pre-scheduling request. Wherein, the detecting the channel quality of the beam may include: channel State Information (CSI) and/or Synchronization signals and PBCH block (SSB) of the detected beam.

In this embodiment, when the frequency band used for transmitting the logical channel data on the main RLC entity is the unlicensed frequency band, it is detected that the unlicensed frequency band LBT fails, which indicates that the resource of the unlicensed frequency band used for transmitting the logical channel data on the main RLC entity is unavailable. Accordingly, upon detecting an unlicensed band LBT failure for transmitting logical channel data on the primary RLC entity, it may be determined that the primary RLC entity satisfies a condition for triggering a pre-scheduling request.

In this embodiment, the uplink resource of the previous data packet of the main RLC entity is preempted by other data packets, which indicates that the previous data packet transmitted through the logical channel corresponding to the main RLC entity is not normally transmitted, and it may be predicted that the current data packet transmitted through the logical channel corresponding to the main RLC entity may also fail to be transmitted, that is, it is predicted that the PDCP retransmission may be autonomously activated when the main RLC entity transmits the current data packet. Therefore, when the uplink resource of the last data packet of the main RLC entity is preempted by other data packets, it can be determined that the main RLC entity meets the condition for triggering the pre-scheduling request.

In this embodiment, the cell that sends the last data packet of the main RLC entity triggers the BFR, which indicates that the logical channel corresponding to the main RLC entity is unstable. In case that a cell transmitting a last data packet of the main RLC entity triggers BFR, it may be determined that the main RLC entity satisfies a condition for triggering a pre-scheduling request.

S402, the terminal sends a first message to the network equipment, wherein the first message is used for requesting the network equipment to pre-allocate uplink resources for PDCP repeated transmission.

The first message includes the foregoing pre-scheduling request, and the type of the pre-scheduling request is SR, and is used to request the network device to schedule the resource in advance.

In this embodiment, when determining that the terminal needs to autonomously activate PDCP retransmission, the terminal sends a first message to the network device, where the first message is used to request the network device to pre-allocate uplink resources for PDCP retransmission. Before the first message is sent, the terminal does not autonomously activate the PDCP retransmission, but after determining that the terminal may autonomously activate the PDCP retransmission in a future time period, in order to avoid that no uplink resource for performing the PDCP retransmission is available after the autonomously activated PDCP retransmission, the terminal requests the network device to pre-allocate the uplink resource through the first message after determining that the autonomously activated PDCP retransmission is needed, so as to achieve the effect of being not rained.

In a possible implementation manner of the foregoing S402, the first message is sent through a pre-configured PUCCH resource. And the pre-configured PUCCH resources are pre-configured for the terminal by the network equipment.

Optionally, the pre-configured PUCCH resources include at least one of the following:

1) Configuring, by a network device, SR resources for a target logical channel, where the target logical channel includes logical channels corresponding to all auxiliary RLC entities for PDCP retransmission or logical channels corresponding to designated auxiliary RLC entities for PDCP retransmission; 2) A PUCCH resource configured by the network device for transmitting the first message; 3) And the PUCCH resource of the cell group of the cell corresponding to the secondary RLC entity for PDCP repeated transmission.

In this embodiment, when the target logical channel includes logical channels corresponding to all the secondary RLC entities for PDCP retransmission, the SR resource configured to the target logical channel by the network device refers to a PUCCH resource for transmitting SR, which is specially configured for the logical channels corresponding to all the secondary RLC entities for PDCP retransmission. When the target logical channel includes a logical channel corresponding to a part of the secondary RLC entities for PDCP retransmission, the SR resource configured to the target logical channel by the network device refers to a PUCCH resource for transmitting SR, which is specially configured for the logical channel corresponding to the designated secondary RLC entity for PDCP retransmission. The designated secondary RLC entity may be a network device designated or protocol designated secondary RLC entity, for example, the network device designates part or all of the secondary RLC entity corresponding to the PDCP entity for PDCP retransmission.

In this embodiment, the PUCCH resource configured by the network device for sending the first message means that the network device has specially configured a corresponding PUCCH resource for sending the first message. The PUCCH resource of the cell group in which the cell corresponding to the secondary RLC entity for PDCP retransmission is located means that, when the first message is sent, the secondary RLC entity for PDCP retransmission can be determined in the secondary RLC entity corresponding to the PDCP entity, and the PUCCH resource of the entire cell group in which the cell corresponding to the secondary RLC entity is located can be used to send the first message.

In another possible implementation manner of S402, the terminal sends a first message to the network device, where the first message includes at least one of the following: and the terminal cancels the pre-scheduling request after sending the first message, and cancels the pre-scheduling request when new data arrives at the terminal buffer triggering buffer report or SR in the target logic channel after sending the first message. For the definition of the target logical channel, reference may be made to the foregoing description, and details are not repeated.

In this embodiment, after determining that repeated transmission of PDCP needs to be autonomously activated, the terminal triggers a pre-scheduling request and sends a first message to the network device, and this embodiment provides two ways as to how to cancel the pre-scheduling request after the first message is sent.

In one mode, the terminal cancels the pre-scheduling request after sending the first message, that is, the trigger of the pre-scheduling request is one-time and is cancelled after sending. In another mode, after the terminal sends the first message, the pre-scheduling request is cancelled when the target logical channel has new data to reach the terminal buffer to trigger buffer reporting or SR, in PDCP retransmission, the target logical channel is used to transmit duplicated PDCP PDUs, and the target logical channel has new data to reach the terminal buffer to trigger buffer reporting (e.g., BSR) or SR, which indicates that the terminal is performing PDCP retransmission and reporting a buffer status or performing a resource request during PDCP retransmission, and the network device knows that PDCP retransmission is active, so the pre-scheduling request does not need to be sent, and can be cancelled. Therefore, the cancellation mode of the pre-scheduling request is enriched in consideration of the actual situation.

S403, the network device responds to the first message and allocates the uplink resource.

In this embodiment, after receiving the first message, the network device determines that the PDCP retransmission that needs to be autonomously activated is allocated with the uplink resource, so that the terminal autonomously activates the PDCP retransmission and then executes PDCP retransmission by using the uplink resource in time.

S404, the network equipment sends a second message to the terminal, and the second message indicates the uplink resource allocated by the network equipment.

In this embodiment, after determining the allocated uplink resource, the network device sends a second message to the terminal, and indicates to the terminal through the second message: the network equipment determines uplink resources which need to be allocated by the autonomously activated PDCP repeated transmission for the terminal.

In the communication method provided in this embodiment, the terminal requests the network device to pre-allocate uplink resources for PDCP retransmission when it is determined that PDCP retransmission needs to be autonomously activated, and the network device allocates uplink resources for PDCP retransmission in response to the request, so as to pre-prepare uplink resources for the terminal to autonomously activate PDCP retransmission, and improve the efficiency from the terminal autonomously activating PDCP retransmission to the execution of PDCP retransmission.

Referring to fig. 5, fig. 5 is a flowchart of a communication method according to another embodiment of the present application. As shown in fig. 5, on the basis of any one of the above embodiments, before performing S401 shown in fig. 4, the present embodiment further includes:

s400, the network equipment sends a third message to the terminal, wherein the third message is used for configuring PDCP repeated transmission of the terminal.

Wherein the third message indicates at least one of: whether the terminal is allowed to autonomously activate PDCP retransmission, whether the terminal is allowed to trigger a pre-scheduling request and transmit the first message, and a secondary RLC entity which is allowed to trigger the pre-scheduling request and transmit the first message.

Under the condition that the network equipment allows the terminal to autonomously activate the PDCP repeated transmission through the third message, the terminal can execute the operation of autonomously activating the PDCP repeated transmission; in case that the network device allows the terminal to trigger the pre-scheduling request and transmit the first message through the third message, the terminal may perform an operation of determining whether autonomous activation of PDCP retransmission is required, triggering the pre-scheduling request and transmitting the first message in case that it is determined that the terminal requires autonomous activation of PDCP retransmission; and under the condition that the network equipment indicates a secondary RLC entity which allows triggering of a pre-scheduling request and sends the first message to the terminal through the third message, after the terminal determines that the PDCP repeat transmission needs to be autonomously activated, the terminal can send the first message through the SR resource of the logical channel corresponding to the secondary RLC entity, or send the first message through the PUCCH resource of the cell group in which the cell corresponding to the secondary RLC entity is located.

Therefore, the network device can flexibly configure one or more aspects of the terminal autonomously activating the PDCP repeated transmission by sending the signaling message to meet the communication service requirement.

On the basis of any of the foregoing embodiments, in a possible implementation manner, after receiving the first message, that is, after performing S403 shown in fig. 4, the network device may determine, in response to the first message, to activate PDCP retransmission for the DRB to be retransmitted. Therefore, when the terminal determines that the PDCP repeated transmission needs to be activated autonomously, the network equipment judges that the PDCP repeated transmission is activated, and does not need extra measures to inform the network equipment.

On the basis of any of the foregoing embodiments, in a possible implementation manner, after determining to activate PDCP retransmission of the DRB to be retransmitted, the network device may activate retransmission of a next PDCP PDU of the DRB to be retransmitted, or activate PDCP retransmission of the DRB to be retransmitted within a target time duration, or send a fourth message to the terminal, where the fourth message is used to indicate that PDCP retransmission is deactivated. Thus, the network device controls the execution of the PDCP retransmission by specifying the amount of data to be retransmitted, the duration of the retransmission, or by indicating signaling.

Wherein, activating the repeated transmission of the next PDCP PDU of the DRB to be repeatedly transmitted means performing the repeated transmission of the next PDCP PDU; activating PDCP repeat transmission of a DRB to be repeatedly transmitted in a target time length, namely performing PDCP repeat transmission in a certain time length, and deactivating the PDCP repeat transmission after the time length; and when the fourth message indicates that the PDCP repeated transmission is deactivated, the terminal deactivates the PDCP repeated transmission in response to the fourth message.

The DRB to be repeatedly transmitted refers to the DRB corresponding to the PDCP entity corresponding to the primary RLC entity that satisfies the condition of triggering the pre-scheduling request in the foregoing embodiment.

Referring to fig. 6, fig. 6 is a flowchart of a communication method according to another embodiment of the present application. As shown in fig. 6, on the basis of any of the above embodiments, after performing S404 shown in fig. 4, this embodiment may further include:

s405, if the terminal autonomously activates the PDCP repeated transmission, the PDCP repeated transmission is carried out on the uplink resource indicated by the second message.

In this embodiment, when the terminal finally performs the PDCP retransmission determined to need to be autonomously activated, the terminal may perform the PDCP retransmission by using the uplink resource indicated by the second message after the PDCP retransmission is autonomously activated, that is, the network device repeatedly transmits the pre-allocated uplink resource for the PDCP, and does not need to request the uplink resource from the network device after the PDCP retransmission is activated and wait for the uplink resource allocated by the network device to perform the PDCP retransmission. The method and the device realize the timely execution of the PDCP repeated transmission after the terminal autonomously activates the PDCP repeated transmission, and are particularly suitable for URLLC services and services with short period.

Optionally, if the terminal does not autonomously activate the PDCP retransmission that is determined to need autonomous activation, the terminal ignores the uplink resource indicated by the second message.

For further understanding of the embodiments of the present application, the embodiments of the present application are described hereinafter from two cases. Two cases include: in the first condition, the terminal triggers a pre-scheduling request and autonomously activates PDCP repeated transmission; and in the second case, the terminal triggers a pre-scheduling request but does not autonomously activate PDCP repeated transmission. In the first case, the terminal determines that the PDCP retransmission needs to be autonomously activated, and then the PDCP retransmission is also autonomously activated; the second case is that the terminal determines that autonomous activation of PDCP retransmission is required, but no subsequent autonomous activation of PDCP retransmission is performed.

Referring to fig. 7, fig. 7 is a flowchart illustrating a communication method according to another embodiment of the present application. Meanwhile, the steps in this embodiment can be understood by referring to fig. 7 and fig. 8, and fig. 8 is a first exemplary diagram of the terminal performing uplink resource pre-scheduling and PDCP retransmission.

First, fig. 8 is explained: for DRB1, the network device configures PDCP duplicate transmission of DRB 1. The PDCP entity corresponding to the DRB1 is PDCP1, the corresponding RLC entities when the PDCP of the DRB1 is repeatedly transmitted are RLC11, RLC12 and RLC13 respectively, and the cells corresponding to the RLC11, the RLC12 and the RLC13 are CC1, CC2 and CC3 respectively. The RLC11 corresponds to the logical channel LCH11, and can only transmit on CC1 when activating repeated transmission; RLC12 corresponds to the logical channel LCH12 and can only transmit on CC2 when repeated transmission is activated; RLC13 corresponds to the logical channel LCH13 and can only transmit on CC3 when repeated transmission is activated. RLC11 is the main RLC entity, LCH11 is the main RLC channel, RLC11 and LCH11 are always activated; RLC12 and RLC13 are secondary RLC channels and can be deactivated. Where fig. 8 is a DC scenario with CC1 on MN and CC2 and CC3 on SN.

Next, as shown in fig. 7, for the first case, the embodiment of the present application includes the following steps:

s701, the network equipment sends a pre-scheduling request configuration to the terminal.

For example, at time T0 in fig. 8, the network device sends the pre-configuration request configuration to the terminal through Radio Resource Control (RRC) signaling.

Optionally, the pre-scheduling request configuration may refer to the description of the third message in the above embodiment.

Optionally, the pre-scheduling request configuration may include a condition for triggering the pre-scheduling request, and PUCCH resources for transmitting the pre-scheduling request. The condition for triggering the pre-scheduling request may refer to the description in the foregoing embodiment, and the PUCCH resource for sending the pre-scheduling request may refer to the description of the pre-configured PUCCH resource for sending the first message in the foregoing embodiment, which is not described in detail again.

S702, when the terminal meets the condition of triggering the pre-scheduling request, triggering and sending the pre-scheduling request to the network device, where the pre-scheduling request is the first message in the foregoing embodiment.

For example, at time T1 or time T6 in fig. 8, the terminal triggers and transmits the pre-scheduling request.

When the terminal meets the condition of triggering the pre-scheduling request, the terminal determines that the PDCP needs to be autonomously activated for repeated transmission, so that the pre-scheduling request is triggered and sent to the network equipment.

It should be noted that the terminal may activate one or more secondary RLC entities when autonomously activating PDCP retransmission, and fig. 8 takes 1 secondary RLC entity activated by the terminal as an example, for example, at time T3, the terminal activates RLC12, and at time T9, the terminal activates RLC13. After receiving the pre-scheduling request, the network device may schedule data transmission of any one of the secondary RLC entities corresponding to the PDCP entity, that is, may allocate uplink resources to any one of the secondary RLC entities corresponding to the PDCP entity.

And S703, the network equipment responds to the pre-scheduling request from the terminal and allocates uplink resources capable of transmitting the logical channel data corresponding to the auxiliary RLC entity to the terminal.

S704, the terminal receives a resource allocation command of the network equipment.

The resource allocation command is the second message in the foregoing embodiment, that is, the PDCCH at time T2 or the PDCCH at time T7 in fig. 8. The uplink resource allocated to the PDCCH at time T2 is on CC2, and the uplink resource allocated to the PDCCH at time T7 is on CC 1.

S705, when the terminal meets the condition of autonomously activating the PDCP repeated transmission, the PDCP repeated transmission is autonomously activated.

For example, the terminal receives a previous transmission failure message (such as HARQ NACK) containing a transport block of a DRB to which it is determined that the autonomously activated PDCP retransmission is required. As shown in fig. 8, the terminal autonomously activates PDCP retransmission at time T4 in response to HARQ NACK of a previous transport block containing DRB1 received at time T3; the terminal autonomously activates PDCP retransmission at time T9 in response to the HARQ NACK of the previous transport block containing DRB1 received at time T8.

In this embodiment, there is no requirement for performing a sequence in S704 and S705, that is, there is no requirement for a sequence between the time when the terminal receives the uplink resource allocated by the network device based on the pre-scheduling request and the time when the terminal autonomously activates PDCP retransmission.

S706, performing PDCP repeated transmission on the uplink resource allocated by the network equipment.

The network equipment receives uplink data on uplink resources allocated based on the pre-scheduling request. If the uplink data includes logical channel data corresponding to the secondary RLC entity (e.g., RLC12 in fig. 8), it is determined to activate PDCP retransmission of the corresponding DRB (e.g., DRB1 in fig. 8).

As an example, in fig. 8, for a Pre-SR (i.e. a Pre-scheduling request) sent by the terminal at time T1, the network device schedules an uplink resource on the CC2 through the PDCCH, where the uplink resource can be used for transmitting uplink data of the logical channel LCH12 corresponding to the RLC 12. The network equipment allocates the uplink resource to the terminal. And after the terminal activates the PDCCH for repeated transmission at the time of T4, transmitting the repeatedly transmitted data packet, namely the copied PDCP PDU, on the uplink resource of the CC2 in a time period from T4 to T5. For Pre-SR sent by the terminal at time T6, the network device schedules uplink resources on the CC3 through the PDCCH, where the uplink resources may be used to transmit uplink data of a logical channel LCH13 corresponding to the RLC13. And the network equipment allocates the uplink resource to the terminal, and the terminal activates the PDCCH for repeated transmission at the time T9 and then transmits the repeatedly transmitted data packet on the uplink resource of the CC3 within the time period from T9 to T10.

It can be seen that, in fig. 8, the procedure from T6 to T10 is similar to that from T1 to T5, except that in the procedure from T6 to T10, after the terminal sends pre-SR, the network device allocates the resource of CC3, so that RLC13 and its corresponding logical channel LCH13 are activated for PDCP retransmission.

Referring to fig. 9, fig. 9 is a flowchart illustrating a communication method according to another embodiment of the present application. Meanwhile, the steps in this embodiment can be understood by combining fig. 9 and fig. 10, and fig. 10 is a second exemplary diagram of the terminal performing uplink resource pre-scheduling and PDCP repeated transmission.

The network structure shown in fig. 10 is the same as the network structure shown in fig. 8, and the same points may be described with reference to the foregoing embodiment for fig. 8, and are not described again.

As shown in fig. 9, for the second case, the embodiment of the present application includes the following steps:

s901, the network equipment sends the pre-scheduling request configuration to the terminal.

For example, at time T0 in fig. 10, the network device sends the pre-configuration request configuration to the terminal through RRC signaling. Wherein, S901 may refer to the description of the foregoing embodiments.

S902, when the terminal meets the condition of triggering the pre-scheduling request, triggering and sending the pre-scheduling request to the network device, where the pre-scheduling request is the first message in the foregoing embodiment.

For example, at time T1 or T4 in fig. 10, the terminal triggers and transmits the pre-scheduling request.

And S903, the network equipment responds to a pre-scheduling request from the terminal and allocates uplink resources capable of transmitting the logical channel data corresponding to the secondary RLC entity to the terminal.

S904, the terminal receives the resource allocation command of the network equipment.

The resource allocation command is the second message in the foregoing embodiment, that is, the PDCCH at time T2 or the PDCCH at time T5 in fig. 10. The uplink resource allocated to the PDCCH at time T2 is on CC2, and the uplink resource allocated to the PDCCH at time T5 is on CC 1.

S905, the terminal does not meet the condition of autonomously activating the PDCP repeated transmission, skips the uplink resource allocated by the network equipment through the resource allocation command, or transmits the data of other logic channels by using the uplink resource.

For example, the terminal does not trigger the condition of autonomously triggering PDCP repetition at time T3 and T6 in fig. 10.

On the terminal side, the embodiment of the present application provides a communication device, and the communication device of the embodiment may be a terminal. As shown in fig. 11, the communication device may include a transceiver 1101, a processor 1102, and a memory 1103.

A transceiver 1101 for receiving and transmitting data under the control of the processor 1102.

Where, in fig. 11, the bus architecture may include any number of interconnected buses and bridges, with one or more processors, represented by the processor 1102, and various circuits, represented by the memory 1103, linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The transceiver 1101 may be a plurality of elements, including a transmitter and a receiver, providing a means for communicating with various other apparatus over a transmission medium, including transmission media such as wireless channels, wired channels, fiber optic cables, and the like. Optionally, the communication apparatus may further comprise a user interface 1104, and for different user devices, the user interface 1104 may also be an interface capable of externally connecting a desired device, the connected device including but not limited to a keypad, a display, a speaker, a microphone, a joystick, etc.

The processor 1102 is responsible for managing the bus architecture and general processing, and the memory 1103 may store data used by the processor 1102 in performing operations.

Alternatively, the processor 1102 may be a Central Processing Unit (CPU), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), or a Complex Programmable Logic Device (CPLD), and the processor may also adopt a multi-core architecture.

The processor 1102 is configured to invoke a computer program stored in the memory 1103 for executing any of the methods provided by the embodiments of the present application with respect to the terminal according to the obtained executable instructions. The processor and memory may also be physically separated.

Specifically, the processor 1102 is configured to perform the following operations: determining that the terminal needs to autonomously activate PDCP repeat transmission; sending a first message to the network equipment, wherein the first message is used for requesting the network equipment to pre-allocate uplink resources for PDCP repeated transmission; and receiving a second message from the network equipment, wherein the second message indicates the uplink resource allocated by the network equipment.

Optionally, the processor 1102 further performs the following operations: and if the main RLC entity corresponding to the PDCP entity of the DRB is determined to meet the condition of triggering the pre-scheduling request, determining that the terminal needs to autonomously activate the PDCP repeated transmission.

Optionally, the processor 1102 further performs at least one of the following operations: determining that the channel quality of a main RLC entity corresponding to the PDCP entity is less than a quality threshold; detecting an unauthorized frequency band LBT failure under the condition that a frequency band used for transmitting logical channel data on a main RLC entity is an unauthorized frequency band; determining that uplink resources of a last data packet of a main RLC entity are occupied by other data packets; and determining that the cell sending the last data packet triggers the beam failure recovery BFR.

Optionally, the processor 1102 further performs the following operations: determining that the terminal needs to convert the PDCP repeated transmission from the inactive state to the active state; or, in case that the PDCP repeat transmission is in an active state, it is determined that the terminal needs to activate more secondary RLC entities for the PDCP repeat transmission.

Optionally, the processor 1102 further performs the following operations: and transmitting the first message through the pre-configured PUCCH resources.

Optionally, the PUCCH resource includes at least one of: the network equipment configures Scheduling Request (SR) resources to a target logical channel, wherein the target logical channel comprises logical channels corresponding to all auxiliary RLC entities used for PDCP repeated transmission or logical channels corresponding to specified auxiliary RLC entities used for PDCP repeated transmission; a PUCCH resource configured by the network device for transmitting the first message; and the PUCCH resource of the cell group in which the cell corresponding to the secondary RLC entity for PDCP repeated transmission is located.

Optionally, the first message includes a pre-scheduling request, and the processor 1102 further performs at least one of the following operations: canceling a pre-scheduling request after the first message is sent; and after the first message is sent, canceling the pre-scheduling request when new data arrives at the terminal buffer triggering buffer reporting request or SR in a target logical channel, wherein the target logical channel comprises logical channels corresponding to all auxiliary RLC entities used for PDCP repeated transmission or logical channels corresponding to designated auxiliary RLC entities used for PDCP repeated transmission.

Optionally, the first message includes a pre-scheduling request, and the processor 1102 further performs the following operations: and receiving a third message from the network equipment, wherein the third message is used for configuring PDCP repeated transmission of the terminal. The third message indicates at least one of the following: whether the terminal is allowed to autonomously activate PDCP retransmission; whether the terminal is allowed to trigger a pre-scheduling request and send a first message; the secondary RLC entity that triggered the pre-scheduling request and sent the first message is allowed.

Optionally, the processor 1102 further performs the following operations: and if the terminal autonomously activates the PDCP repeated transmission, performing the PDCP repeated transmission on the uplink resources distributed by the network equipment.

Optionally, the processor 1102 further performs the following operations: receiving a fourth message of the network device, the fourth message indicating that PDCP repeat transmission is deactivated; deactivating the PDCP repeat transmission in response to the fourth message.

Optionally, the processor 1102 further performs the following operations: and if the terminal does not autonomously activate the PDCP repeated transmission, ignoring the uplink resource which is pre-allocated by the network equipment and is used for the PDCP repeated transmission.

It should be noted that, the apparatus provided in the present application can implement all the method steps implemented by the terminal in the foregoing method embodiment, and can achieve the same technical effect, and details of the same parts and beneficial effects as those in the method embodiment are not described herein again.

On a network side, an embodiment of the present application provides a communication apparatus, and the communication apparatus of this embodiment may be a network device. As shown in fig. 12, the communication apparatus includes: a transceiver 1201, a processor 1202, and a memory 1203.

A transceiver 1201 for receiving and transmitting data under the control of the processor 1202.

Where in fig. 12 the bus architecture may include any number of interconnected buses and bridges, with one or more processors, represented by the processor 1202, and various circuits, represented by the memory 1203, being linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The transceiver 1201 may be a plurality of elements including a transmitter and a receiver that provide a means for communicating with various other apparatus over a transmission medium including wireless channels, wired channels, fiber optic cables, and the like. The processor 1202 is responsible for managing the bus architecture and general processing, and the memory 1203 may store data used by the processor 1202 in performing operations.

The processor 1202 may be a CPU, ASIC, FPGA or CPLD, and the processor may also employ a multi-core architecture.

The processor 1202 is configured to invoke a computer program stored in the memory 1203 for executing any of the methods provided by the embodiments of the present application with respect to the network device according to the obtained executable instructions. The processor and memory may also be physically separated.

Specifically, the processor 1202 is configured to perform the following operations: receiving a first message from a terminal, wherein the first message is used for requesting network equipment to allocate uplink resources in advance for PDCP repeated transmission; allocating uplink resources in response to the first message; and sending a second message to the terminal, wherein the second message indicates the uplink resource allocated by the network equipment.

Optionally, the processor 1202 further performs the following operations: determining to activate PDCP duplicate transmission.

Optionally, the processor 1202 further performs the following operations: activating the repeated transmission of the next PDCP PDU of the DRB to be repeatedly transmitted; or, activating PDCP repeated transmission of the DRB in the target time length; or, a fourth message is sent to the terminal, wherein the fourth message indicates that the PDCP repeated transmission is deactivated.

Optionally, the first message includes a pre-scheduling request, and the processor 1202 further performs the following operations: and sending a third message to the terminal, wherein the third message is used for configuring PDCP repeated transmission of the terminal. The third message indicates at least one of the following: whether the terminal is allowed to autonomously activate PDCP retransmission; whether the terminal is allowed to trigger a pre-scheduling request and send a first message; the secondary RLC entity that triggered the pre-scheduling request and sent the first message is allowed.

It should be noted that, the apparatus provided in the present application can implement all the method steps implemented by the network device in the foregoing method embodiment, and can achieve the same technical effect, and details of the same parts and beneficial effects as those in the method embodiment are not described herein again.

On the terminal side, the embodiment of the present application further provides a communication device, and the communication device of the present embodiment may be a terminal. As shown in fig. 13, the communication apparatus includes: processing unit 1301, transmitting unit 1302, and receiving unit 1303.

A processing unit 1301, configured to determine that the terminal needs to autonomously activate PDCP retransmission;

a sending unit 1302, configured to send a first message to a network device, where the first message is used to request the network device to pre-allocate uplink resources for PDCP retransmission;

a receiving unit 1303, configured to receive a second message from the network device, where the second message indicates the uplink resource allocated by the network device.

Optionally, the processing unit 1301 is specifically configured to: and if the main RLC entity corresponding to the PDCP entity of the DRB is determined to meet the condition of triggering the pre-scheduling request, determining that the terminal needs to autonomously activate the PDCP repeated transmission.

Optionally, the processing unit 1301 is specifically configured to perform at least one of the following operations: determining that the channel quality of a main RLC entity corresponding to the PDCP entity is less than a quality threshold; detecting an unauthorized frequency band LBT failure under the condition that a frequency band used for transmitting logical channel data on a main RLC entity is an unauthorized frequency band; determining that uplink resources of a last data packet of a main RLC entity are occupied by other data packets; and determining the cell sending the last data packet to trigger BFR.

Optionally, the processing unit 1301 is specifically configured to: determining that the terminal needs to convert the PDCP repeated transmission from the inactive state to the active state; or, in case that the PDCP repeat transmission is in an active state, it is determined that the terminal needs to activate more secondary RLC entities for the PDCP repeat transmission.

Optionally, the sending unit 1302 is specifically configured to: and transmitting the first message through the pre-configured PUCCH resources.

Optionally, the first message includes a pre-scheduling request, and the sending unit 1302 is specifically configured to perform at least one of the following operations: canceling a pre-scheduling request after sending the first message; and after the first message is sent, canceling the pre-scheduling request when new data arrives at the terminal buffer triggering buffer reporting request or SR in a target logical channel, wherein the target logical channel comprises logical channels corresponding to all auxiliary RLC entities used for PDCP repeated transmission or logical channels corresponding to designated auxiliary RLC entities used for PDCP repeated transmission.

Optionally, the first message includes a pre-scheduling request, and the receiving unit 1303 is further configured to: and receiving a third message from the network equipment, wherein the third message is used for configuring PDCP repeated transmission of the terminal. The third message indicates at least one of the following: whether the terminal is allowed to autonomously activate PDCP repeat transmission; whether the terminal is allowed to trigger a pre-scheduling request and send a first message; the secondary RLC entity that triggered the pre-scheduling request and sent the first message is allowed.

Optionally, the sending unit 1302 is further configured to: and if the terminal autonomously activates the PDCP repeated transmission, carrying out the PDCP repeated transmission on the uplink resources allocated by the network equipment.

Optionally, the receiving unit 1303 is further configured to: receiving a fourth message of the network device, the fourth message indicating deactivation of PDCP duplicate transmissions. The processing unit 1301 is further configured to: deactivating the PDCP repeat transmission in response to the fourth message.

Optionally, the processing unit 1301 is further configured to: and if the terminal does not autonomously activate the PDCP repeated transmission, ignoring the uplink resource which is pre-allocated by the network equipment and is used for the PDCP repeated transmission.

On the network side, an embodiment of the present application further provides a communication device, and the communication device of this embodiment may be a network device. As shown in fig. 14, the communication apparatus includes: a receiving unit 1401, a processing unit 1402 and a transmitting unit 1403.

A receiving unit 1401, configured to receive a first message from a terminal, where the first message is used to request a network device to pre-allocate uplink resources for PDCP retransmission;

a processing unit 1402, configured to allocate an uplink resource in response to the first message;

a sending unit 1403, configured to send a second message to the terminal, where the second message indicates the uplink resource allocated by the network device.

Optionally, the processing unit 1402 is further configured to: determining to activate PDCP duplicate transmission.

Optionally, the processing unit 1402 is further configured to: activating the repeated transmission of the next PDCP PDU of the DRB to be repeatedly transmitted. Alternatively, the processing unit 1402 is further configured to: and activating PDCP repeated transmission of the DRB in the target time length. Alternatively, the sending unit 1403 is further configured to: and sending a fourth message to the terminal, wherein the fourth message indicates that the PDCP repeated transmission is deactivated.

Optionally, the first message includes a pre-scheduling request, and the sending unit 1403 is further configured to: and sending a third message to the terminal, wherein the third message is used for configuring PDCP repeated transmission of the terminal. The third message indicates at least one of the following: whether the terminal is allowed to autonomously activate PDCP retransmission; whether the terminal is allowed to trigger a pre-scheduling request and send a first message; the secondary RLC entity that triggered the pre-scheduling request and sent the first message is allowed.

It should be noted that the division of the unit in the embodiment of the present application is schematic, and is only a logic function division, and there may be another division manner in actual implementation. 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 integrated unit may be implemented in the form of hardware, or may also be implemented in the form of a software functional unit.

The integrated unit, if implemented as a software functional unit and sold or used as a stand-alone product, may be stored in a processor readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, a network device, or the like) or a processor (processor) 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.

On the terminal side, embodiments of the present application provide a processor-readable storage medium, where a computer program is stored, where the computer program is configured to enable a processor to execute any one of the methods provided in the embodiments of the present application and related to a terminal. The processor is enabled to implement all the method steps implemented by the terminal in the above method embodiment, and achieve the same technical effect, and detailed descriptions of the same parts and beneficial effects as those of the method embodiment in this embodiment are omitted here.

On the network side, an embodiment of the present application provides a processor-readable storage medium, where a computer program is stored in the processor-readable storage medium, and the computer program is configured to enable a processor to execute any one of the methods provided in the embodiment of the present application with respect to a network device. All the method steps implemented by the network device in the method embodiment can be implemented by the processor, and the same technical effects can be achieved, so detailed descriptions of the same parts and beneficial effects as those in the method embodiment in this embodiment are omitted here.

The processor-readable storage medium may be any available medium or data storage device that can be accessed by a processor, including, but not limited to, magnetic memory (e.g., floppy disks, hard disks, magnetic tape, magneto-optical disks (MOs), etc.), optical memory (e.g., CDs, DVDs, BDs, HVDs, etc.), and semiconductor memory (e.g., ROMs, EPROMs, EEPROMs, non-volatile memories (NAND FLASH), solid State Disks (SSDs)), etc.

As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, optical storage, and the like) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus, and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer-executable instructions. These computer-executable instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These processor-executable instructions may also be stored in a processor-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the processor-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These processor-executable instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.

Claims

1. A communication method is applied to a terminal and comprises the following steps:

determining that the terminal needs to autonomously activate Packet Data Convergence Protocol (PDCP) repeat transmission;

sending a first message to a network device, wherein the first message is used for requesting the network device to pre-allocate uplink resources for the PDCP repeated transmission;

2. The communication method according to claim 1, wherein the determining that the terminal needs to autonomously activate Packet Data Convergence Protocol (PDCP) repeat transmission comprises:

and if determining that a main Radio Link Control (RLC) entity corresponding to a PDCP entity of the radio data bearer (DRB) meets the condition of triggering a pre-scheduling request, determining that the PDCP repeated transmission needs to be autonomously activated by the terminal.

3. The communication method according to claim 2, wherein the determining that the primary radio link control, RLC, entity corresponding to the PDCP entity of the radio data bearer, DRB, satisfies the condition for triggering the pre-scheduling request includes at least one of:

detecting that the unlicensed frequency band fails to Listen Before Talk (LBT) under the condition that the frequency band for transmitting the logical channel data on the main RLC entity is the unlicensed frequency band;

determining that uplink resources of a last data packet of the main RLC entity are occupied by other data packets;

and determining that the cell sending the previous data packet triggers the beam failure recovery BFR.

4. The communication method according to claim 1, wherein the determining that the terminal needs to autonomously activate Packet Data Convergence Protocol (PDCP) repeat transmission comprises:

determining that the terminal needs to transition the PDCP repeated transmission from an inactive state to an active state;

or, in a situation that the PDCP repeated transmission is in an active state, determining that the terminal needs to activate more secondary RLC entities for the PDCP repeated transmission.

5. The communication method according to any of claims 1-4, wherein said sending a first message to a network device comprises:

and transmitting the first message through a pre-configured Physical Uplink Control Channel (PUCCH) resource.

6. The communication method according to claim 5, wherein the PUCCH resources comprise at least one of:

scheduling Request (SR) resources configured by the network device to a target logical channel, where the target logical channel includes logical channels corresponding to all secondary RLC entities for the PDCP repeat transmission or logical channels corresponding to designated secondary RLC entities for the PDCP repeat transmission;

and the PUCCH resource of the cell group in which the cell corresponding to the secondary RLC entity for the PDCP repeated transmission is located.

7. The communication method according to any of claims 1 to 4, wherein the first message comprises a pre-scheduling request, and wherein the sending the first message to the network device comprises at least one of:

canceling the pre-scheduling request after the first message is sent;

and after the first message is sent, canceling the pre-scheduling request when new data arrives at a terminal buffer trigger buffer reporting request or SR (scheduling request) in a target logical channel, wherein the target logical channel comprises logical channels corresponding to all auxiliary RLC entities used for the PDCP (packet data convergence protocol) repeated transmission or logical channels corresponding to designated auxiliary RLC entities used for the PDCP repeated transmission.

8. The communication method according to any of claims 1-4, wherein the first message comprises a pre-scheduling request, and wherein before determining that the terminal needs to autonomously activate Packet Data Convergence Protocol (PDCP) repeat transmission, the communication method further comprises:

receiving a third message from the network device, the third message being used for configuring PDCP retransmission of the terminal, the third message indicating at least one of the following information:

whether to allow the terminal to autonomously activate PDCP duplicate transmission;

whether the terminal is allowed to trigger the pre-scheduling request and send the first message;

and allowing the secondary RLC entity to trigger the pre-scheduling request and send the first message.

9. The communication method according to any one of claims 1 to 4, wherein after receiving the second message from the network device, the communication method further comprises:

10. The communication method according to claim 9, wherein after performing the PDCP repeated transmission on the uplink resource allocated by the network device, the communication method further comprises:

receiving a fourth message of the network device, the fourth message indicating deactivation of the PDCP repeat transmission;

deactivating the PDCP repeat transmission in response to the fourth message.

11. The communication method according to any one of claims 1 to 4, wherein after receiving the second message from the network device, the communication method further comprises:

12. A communication method applied to a network device includes:

allocating uplink resources in response to the first message;

13. The communication method according to claim 12, wherein after receiving the first message from the terminal, the communication method further comprises:

determining to activate the PDCP repeat transmission.

14. The communications method of claim 13, wherein after determining to activate the PDCP duplicate transmission, the communications method further comprises:

activating the repeated transmission of the next PDCP protocol data unit PDU of the DRB to be repeatedly transmitted;

or, activating the PDCP repeat transmission of the DRB in the target time length;

or sending a fourth message to the terminal, wherein the fourth message indicates that the PDCP repeated transmission is deactivated.

15. The communication method according to any of claims 12 to 14, wherein the first message comprises a pre-scheduling request, and wherein before the receiving the first message from the terminal, the communication method further comprises:

whether to allow the terminal to autonomously activate PDCP repeat transmission;

whether the terminal is allowed to trigger a pre-scheduling request and send the first message;

and the secondary RLC entity which triggers the pre-scheduling request and sends the first message is allowed.

16. A communication apparatus, applied to a terminal, comprising a memory, a transceiver, and a processor:

the memory for storing a computer program;

the transceiver is used for transceiving data under the control of the processor;

the processor is used for reading the computer program in the memory and executing the following operations:

receiving a second message from the network device, wherein the second message indicates the uplink resource allocated by the network device.

17. The communications apparatus of claim 16, wherein the processor is further configured to:

18. The communications apparatus of claim 17, wherein the processor is further configured to:

detecting that the LBT of the unauthorized frequency band fails under the condition that the frequency band used for transmitting the logical channel data on the main RLC entity is the unauthorized frequency band;

determining that uplink resources of a last data packet of the main RLC entity are preempted by other data packets;

and determining that the cell sending the last data packet triggers BFR.

19. A communication apparatus, applied to a network device, comprising a memory, a transceiver, and a processor:

the memory for storing a computer program;

receiving a first message from a terminal, wherein the first message is used for requesting network equipment to determine PDCP repeated transmission needing autonomous activation for the terminal and pre-allocate uplink resources;

allocating uplink resources in response to the first message;

20. A communication apparatus, applied to a terminal, comprising:

a processing unit, configured to determine that the terminal needs to autonomously activate PDCP retransmission;

21. A communication apparatus, applied to a network device, comprising:

a sending unit, configured to send a second message to the terminal, where the second message indicates the uplink resource allocated by the network device.

22. A processor-readable storage medium, characterized in that the processor-readable storage medium stores a computer program for causing the processor to execute the communication method of any one of claims 1 to 15.