CN112740825A

CN112740825A - Transmission method of duplicated data, terminal equipment and access network equipment

Info

Publication number: CN112740825A
Application number: CN201980062120.5A
Authority: CN
Inventors: 石聪
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2019-02-01
Filing date: 2019-02-01
Publication date: 2021-04-30
Anticipated expiration: 2039-02-01
Also published as: WO2020155124A1; CN112740825B

Abstract

The embodiment of the application provides a transmission method of duplicated data, terminal equipment and access network equipment. The transmission method of the copy data comprises the following steps: the terminal equipment receives first information, wherein the first information is used for indicating that: at least two radio links of the same radio bearer or of duplicate data of the same packet data convergence protocol PDCP entity control RLC transmission modes. The embodiment of the application can realize flexible configuration of the RLC transmission mode, and further can meet the requirements of various service scenes.

Description

Transmission method of duplicated data, terminal equipment and access network equipment

Technical Field

The present disclosure relates to communications technologies, and in particular, to a method for transmitting duplicated data, a terminal device, and an access network device.

Background

The radio access network protocol of a Long Term Evolution (LTE) system is divided into three layers: a physical layer (L1), a data link layer (L2), and a radio resource control layer (L3). The Data Link layer (L2) may include a Medium Access Control (MAC) layer, a Radio Link Control (RLC) layer, and a Packet Data Convergence Protocol (PDCP) layer.

The Mode type of the RLC entity in the RLC layer may be configured as a Transparent Mode (TM), an Unacknowledged Mode (UM), or an Acknowledged Mode (AM).

However, with the development of wireless communication technology, the fifth generation communication technology (5G) has higher requirements on time delay and reliability to meet the service requirements of application scenarios such as enhanced mobile bandwidth (eMBB), mass machine type communication (mtc), ultra-reliable and low-latency (urrllc), and the configuration mode of each RLC entity in the RLC layer cannot meet the requirements of 5G on time delay and reliability.

Disclosure of Invention

The embodiment of the application provides a transmission method of duplicated data, terminal equipment and access network equipment, so as to meet the requirements of 5G on time delay and reliability.

In a first aspect, an embodiment of the present application provides a method for transmitting duplicate data, including:

the terminal equipment receives first information, wherein the first information is used for indicating that: at least two radio links of the same radio bearer or of duplicate data of the same packet data convergence protocol PDCP entity control RLC transmission modes.

In a second aspect, an embodiment of the present application provides a method for transmitting duplicate data, including:

the access network equipment determines first information, wherein the first information is used for indicating that: at least two radio links of the duplicated data of the same radio bearer or the same packet data convergence protocol PDCP entity control RLC transmission modes;

and the access network equipment sends the first information.

In a third aspect, an embodiment of the present application provides a terminal device, including:

a receiving module, configured to receive first information, where the first information is used to indicate: at least two radio links of the same radio bearer or of duplicate data of the same packet data convergence protocol PDCP entity control RLC transmission modes.

In a fourth aspect, an embodiment of the present application provides an access network device, including:

a processing module configured to determine first information, the first information indicating: at least two radio links of the duplicated data of the same radio bearer or the same packet data convergence protocol PDCP entity control RLC transmission modes;

and the sending module is used for sending the first information.

In a fifth aspect, an embodiment of the present application provides a terminal device, including: a processor and a memory;

the memory stores computer-executable instructions;

the processor executes computer-executable instructions stored by the memory, causing the processor to perform the method of transferring replicated data according to the first aspect.

In a sixth aspect, an embodiment of the present application provides an access network device, including: a processor and a memory;

the memory stores computer-executable instructions;

the processor executes the computer-executable instructions stored by the memory, causing the processor to perform the method of transferring replicated data according to the second aspect.

In a seventh aspect, an embodiment of the present application provides a computer-readable storage medium, where computer-executable instructions are stored, and when executed by a processor, the computer-executable instructions are used to implement the transmission method for duplicated data according to the first aspect, or the transmission method for duplicated data according to the second aspect.

According to the transmission method of the duplicated data, the terminal device and the access network device, the access network device sends the first information to the terminal device, the first information is used for indicating at least two RLC transmission modes of the duplicated data of the same radio bearer or the same PDCP entity, so that flexible configuration of the RLC transmission modes is achieved, requirements of transmission delay and transmission reliability are met, a more flexible and effective transmission mode of the duplicated data is achieved, and requirements of various service scenes can be met.

Drawings

Reference will now be made in brief to the accompanying drawings, which are needed for purposes of illustration and description of the prior art.

FIG. 1 is a schematic diagram of an application scenario according to an embodiment of the present application;

fig. 2 is a flowchart of a transmission method of duplicated data according to an embodiment of the present application;

fig. 3A is a schematic diagram of a plurality of RLC entities corresponding to a radio bearer according to an embodiment of the present application;

fig. 3B is a schematic diagram of a plurality of RLC entities corresponding to a radio bearer according to an embodiment of the present application;

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

fig. 5 is a flowchart of a transmission method of duplicated data according to an embodiment of the present application;

fig. 6 is a flowchart of a transmission method of duplicated data according to an embodiment of the present application;

fig. 7 is a flowchart of a transmission method of duplicated data according to an embodiment of the present application;

fig. 8A is a schematic configuration diagram of a plurality of RLC entities corresponding to a radio bearer according to an embodiment of the present application;

FIG. 8B is a flowchart of a process of copying data in the scenario shown in FIG. 8A according to an embodiment of the present application;

fig. 9A is a schematic view of an application scenario of a process of copying data according to an embodiment of the present application;

FIG. 9B is a flowchart of a process of copying data in the scenario shown in FIG. 9A according to an embodiment of the present application;

FIG. 10 is a flowchart of a process of copying data in the scenario shown in FIG. 9A according to an embodiment of the present application;

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

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

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

fig. 14 is a schematic structural diagram of an access network device according to an embodiment of the present application.

Detailed Description

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.

Fig. 1 is a schematic diagram of an application scenario according to an embodiment of the present application. As shown in fig. 1, the application scenario includes: terminal equipment 11 and access network equipment 12. Terminal device 11 establishes a communication connection with access network device 12. For example, for uplink data transmission, the terminal device 11 serves as a transmitting end, the access network device 12 serves as a receiving end, for downlink data transmission, the terminal device 12 serves as a receiving end, and the access network device 12 serves as a transmitting end. For both uplink data transmission and downlink data transmission, the transmission method of duplicated data in the embodiment of the present application can be used to meet the requirements of service on time delay and reliability, and for a specific implementation manner, reference may be made to the following explanation of the embodiment.

A Terminal device (also referred to as a User Equipment (UE), a Mobile Terminal (MT), a Mobile User Equipment (ms), etc., may communicate with one or more core networks via a Radio Access Network (RAN). The user equipment may be mobile terminals such as mobile telephones (or so-called "cellular" telephones) and computers having mobile capabilities, e.g. mobile devices which may be portable, pocket, hand-held, computer-included or vehicle-mounted. Or may be a Communication device in Machine Type Communication (MTC).

An access network device may be an apparatus deployed in a radio access network to provide wireless communication functionality for terminal devices. The access network device may include various forms of macro base stations, micro base stations (also referred to as small stations), relay stations, access points, etc., and may also include various forms of control nodes, such as a network controller. The control node may be connected to a plurality of base stations, and configure resources for a plurality of terminal devices under the coverage of the plurality of base stations. In systems using different radio access technologies, names of devices having functions of base stations may be different, such as an eNB or an e-NodeB in LTE, or base stations or transmitting/receiving endpoints in 5G or NR, such as a gNB, which is not limited in the embodiments of the present application.

The processing method for data replication and transmission in the embodiment of the present application can be applied to various communication systems for data processing, for example: such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), single carrier frequency division multiple access (SC-FDMA), and other systems. The term "system" may be used interchangeably with "network". CDMA systems may implement wireless technologies such as Universal Terrestrial Radio Access (UTRA), CDMA2000, and the like. UTRA may include Wideband CDMA (WCDMA) technology and other CDMA variant technologies. CDMA2000 may cover the Interim Standard (IS) 2000(IS-2000), IS-95 and IS-856 standards. TDMA systems may implement wireless technologies such as global system for mobile communications (GSM). The OFDMA system may implement wireless technologies such as evolved universal terrestrial radio access (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11(Wi-Fi), IEEE 802.16(WiMAX), IEEE 802.20, Flash OFDMA, etc. UTRA and E-UTRA are UMTS as well as UMTS evolved versions. Various versions of 3GPP in Long Term Evolution (LTE) and LTE-based evolution are new versions of UMTS using E-UTRA. The fifth Generation (5Generation, abbreviated as "5G") communication system, New Radio ("NR"), is the next Generation communication system under study. In addition, the communication system can also be applied to future-oriented communication technologies, and all the technical solutions provided by the embodiments of the present application are applied. The system architecture and the service scenario described in the embodiment of the present application are for more clearly illustrating the technical solution of the embodiment of the present application, and do not form a limitation on the technical solution provided in the embodiment of the present application, and as a person of ordinary skill in the art knows that along with the evolution of the network architecture and the appearance of a new service scenario, the technical solution provided in the embodiment of the present application is also applicable to similar technical problems.

The embodiments of the present application refer to "a plurality" or "a plurality". "and/or" describes the association relationship of the 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.

The "RLC entity identifier" referred to in the embodiments of the present application may be replaced with a logical channel identifier.

The "radio bearer" according to the embodiment of the present application may correspond to at least one PDCP entity, one PDCP entity may correspond to one or more RLC entities, and one RLC entity may correspond to one MAC entity.

The "duplicate data" referred to in the embodiments of the present application includes the original PDCP data PDU and a duplicate of the original PDCP data PDU.

The PDCP entity in the PDCP layer may correspond to one or two RLC entities, and different RLC entities may correspond to the same or different MAC entities. In data replication transmission (data replication), each RLC entity in the RLC layer is generally configured to the same RLC mode. Configuring each RLC entity in the RLC layer to the same RLC mode cannot meet the requirements of 5G on delay and reliability. Specifically, for example, each RLC entity in the RLC layer is configured as an AM, which has a large transmission delay, and each RLC entity in the RLC layer is configured as an UM, which has a low transmission reliability.

The method for transmitting the duplicated data in the embodiment of the application relates to a configuration process, wherein the configuration process in the embodiment of the application can configure at least two RLC transmission modes to terminal equipment, and explains the transmission characteristics of different RLC transmission modes. UM data transmission is characterized by providing certain reliability guarantee and small time delay compared with TM. AM data transmission is characterized by high reliability, but longer latency compared to the first two transmission modes. In the embodiment of the application, multiple RLC transmission modes are configured for the copied data of the same radio bearer or the same PDCP entity, so that flexible configuration of the RLC transmission modes can be realized, and requirements of transmission delay and transmission reliability are met, thereby meeting requirements of some service scenarios, where the service scenarios may include enhanced mobile bandwidth (eMBB), mass machine type communication (mtc), ultra-reliable low-latency (urrllc), Industrial internet (IIoT), and the like.

The following specifically explains a configuration procedure related to the transmission method of the duplicated data according to the embodiment of the present application with reference to an application scenario shown in fig. 1.

It should be noted that, regardless of uplink data transmission or downlink data transmission, the configuration process related to the transmission method of the duplicated data in the embodiment of the present application is applicable.

Fig. 2 is a flowchart of a transmission method of duplicated data according to an embodiment of the present application, and as shown in fig. 2, the method of this embodiment may include:

step 101, the access network device determines first information.

Wherein the first information is used for indicating: at least two RLC transmission modes of duplicate data of the same radio bearer or the same PDCP entity. The RLC transmission modes involved may be, for example, TM, UM, and AM, but are not limited to the three RLC transmission modes, and the at least two RLC transmission modes may include at least two of TM, UM, and AM.

The access network device configures at least two RLC transmission modes to the duplicated data of the same radio bearer or the same PDCP entity of the terminal device through the first information, and the terminal device can select one or more or all of the at least two RLC transmission modes to transmit the duplicated data according to requirements. For example, the first information is used to indicate that the duplicated data of the same PDCP entity supports UM and AM transmission, and the terminal device transmits the duplicated data of the same PDCP entity using UM, AM, or UM and AM.

In some embodiments, the access network device may determine the first information according to one or more of information such as traffic transmission characteristics, channel transmission quality, cell load, data size of data to be transmitted, data characteristics/priority, and the like.

Step 102, the access network device sends the first information to the terminal device.

Correspondingly, the terminal device receives the first information sent by the access network device.

The first information of the embodiment of the present application is information indicating at least two RLC transmission modes of duplicated data of the same radio bearer or the same PDCP entity, and the name thereof is not limited thereto. The access network device may send the first information to the terminal device through a higher layer signaling, where the higher layer signaling may be a Radio Resource Control (RRC) signaling, and the RRC signaling may be an RRC reconfiguration signaling.

The PDCP entity of the embodiment of the present application corresponds to a Radio Bearer, where the Radio Bearer may include a Data Radio Bearer (DRB) and/or a Signaling Radio Bearer (SRB). Optionally, one radio bearer may correspond to at least one PDCP entity. The duplicated data of the DRB or the SRB may support at least two RLC transmission modes for transmission, or the duplicated data of the PDCP entity may support at least two RLC transmission modes for transmission, and when one radio bearer corresponds to one PDCP entity, the duplicated data of the PDCP entity may also be understood as the duplicated data of the radio bearer, that is, the duplicated data of the DRB or the SRB, where the duplicated data of the DRB or the SRB may include two duplicated data, or any number of duplicated data. The duplicated Data may be obtained by duplicating Data to be transmitted (e.g., original PDCP Data PDU), and the Data to be transmitted may be Packet Data Convergence Protocol (PDCP) Data Protocol Data Unit (PDU) to be transmitted.

In this embodiment, the access network device determines first information, and the access network device sends the first information to the terminal device, where the first information is used to indicate at least two RLC transmission modes of duplicated data of the same radio bearer or the same PDCP entity, so as to implement flexible configuration of the RLC transmission modes, and meet requirements of transmission delay and transmission reliability, thereby implementing a more flexible and effective transmission mode of duplicated data, and further meeting requirements of some service scenarios (e.g., IIoT).

In some embodiments, the first information is specifically used to indicate: each radio bearer or each PDCP entity corresponds to a plurality of RLC entities corresponding to at least two RLC transmission modes.

Taking the PDCP entity as the PDCP entity corresponding to the radio bearer DRB1 as an example, the first information may be used to indicate that the PDCP entity of the DRB1 corresponds to multiple RLC entities, and the multiple RLC entities correspond to two RLC transmission modes. The terminal device may configure the transmission modes of the plurality of RLC entities corresponding to the PDCP entity of the DRB1 as UM and AM, or UM and TM, or TM and AM according to the first indication information. The implementation manner of the specific configuration of the transmission mode of each RLC entity may be a manner one or a manner two. The first method is as follows: determined by the terminal device (see the following explanation specifically), in a second way: indicated by the access network equipment (see the following explanation in detail).

It should be noted that the first information may be applied to a scenario of multiple Cell Groups (CGs), for example, the radio bearer DRB1 corresponds to one PDCP entity, and the PDCP entity corresponds to four RLC entities, where two RLC entities correspond to a Master Cell Group (MCG) and two RLC entities correspond to a Secondary Cell Group (SCG), and then the first information may be used to indicate that the four RLC entities correspond to at least two RLC transmission modes. The first information may also be applied to a scenario where one cell group corresponds to more than two RLC entities, for example, if the radio bearer DRB1 corresponds to one PDCP entity, the PDCP entity corresponds to two RLC entities, and the two RLC entities correspond to MCGs, the first information may be used to indicate that the two RLC entities correspond to at least two RLC transmission modes. This first information can also be applied to a combination of the first two scenarios.

On the basis of the embodiment, a first mode is explained, in which the terminal device configures one or more RLC entities of the same cell group (cell group) to have the same transmission mode according to the first information, for example, when the access network device configures the transmission modes of the RLC entities of the PDCP entity to be UM and AM through the first information, the terminal device may configure the transmission mode of one or more RLC entities of the Master Cell Group (MCG) to be AM and the transmission mode of one or more RLC entities of the Secondary Cell Group (SCG) to be UM. And the terminal equipment determines the transmission mode of each RLC entity according to the first information. It should be noted that, in this manner, the transmission mode of the RLC entity may or may not be related to the CG. For example, the terminal device may configure one RLC entity as UM and the other RLC entities as AM according to the first information.

It should be noted that, in the specific configuration process of determining the transmission mode of each RLC entity by the terminal device according to the first information, the terminal device may select one or more of the at least two RLC transmission modes indicated by the first information to configure the transmission mode of each RLC entity. In some embodiments, the terminal device may further determine a specific configuration of the transmission mode of each RLC entity by combining one or more of information of channel transmission quality, data size of data to be transmitted, data characteristics/priority, and the like.

On the basis of this embodiment, a second mode is explained, and the first information is specifically used to indicate: the one or more RLC entities may correspond to one RLC transmission mode, that is, the first information may indicate that the PDCP entity corresponds to a plurality of RLC entities corresponding to at least two RLC transmission modes, and may indicate that the one or more RLC entities correspond to the RLC transmission mode. For example, the first information may indicate that the transmission mode of one or more RLC entities of the MCG is AM and the transmission mode of one or more RLC entities of the SCG is UM. It should be noted that, in this manner, the transmission mode of the RLC entity may or may not be related to the CG. For example, the first information may indicate that one RLC entity is UM and the other RLC entities are AM. For another example, the first information may indicate that one or more RLC entities are AM and other RLC entities are UM. The terminal device may perform corresponding configuration on the corresponding RLC entity according to the first information.

Optionally, one or more RLC entities in the same cell group use one RLC transmission mode, that is, one or more RLC entities in the same cell group use the same RLC transmission mode.

It can also be understood that: for duplicated data transmission from the same radio bearer, RLC transmission modes of RLC entities mapped to one CG are the same, and RLC transmission modes of RLC entities mapped to different CGs are different.

For example, when duplicate data transmission (duplicate) is activated, RLC entities or logical channels configured to have the same transmission mode of only the RLC entity can be activated at the same time, which has the advantage of less impact on the existing protocol; alternatively, RLC entities or logical channels having different RLC entity transmission modes may be activated simultaneously, which has the advantage of increasing the flexibility of duplicated data transmission.

Taking fig. 3A for example, fig. 3A is a schematic diagram of a radio bearer corresponding to multiple RLC entities according to an embodiment of the present application, where the present embodiment takes DRB1 and DRB2 as examples, as shown in fig. 3A, according to first information sent by an access network device, a terminal device completes the following configuration: the PDCP entity of the DRB1 of the terminal device corresponds to four RLC entities, wherein, from left to right, the first two RLC entities correspond to MCG MAC entities, the second two RLC entities correspond to SCG MAC entities, the transmission mode of the first two RLC entities is AM, and the transmission mode of the second two RLC entities is UM. The PDCP entity of the DRB2 of the terminal device corresponds to two RLC entities, wherein the two RLC entities correspond to an SCG MAC entity, and the transmission mode of the two RLC entities is UM.

Optionally, one or more RLC entities in the same cell group use different RLC transmission modes.

It can also be understood that: for duplicate data transmission from the same radio bearer, the RLC transmission modes of the related RLC entities may be the same or different. Further, RLC transmission modes of RLC entities mapped to one CG may be the same or different. This has the advantage of more flexibility in the configuration and use of the transmission mode of the RLC entity.

Specifically, when duplicate data transmission (duplicate) is activated, RLC entities or logical channels configured only in the same RLC entity transmission mode may be activated at the same time, which has the advantage of less impact on the existing protocol; alternatively, RLC entities or logical channels with different transmission modes of the configured RLC entities may be activated simultaneously, which has the advantage of increasing the flexibility of duplicated data transmission.

Fig. 3B is an exemplary illustration, where fig. 3B is a schematic diagram of a radio bearer corresponding to multiple RLC entities according to an embodiment of the present application, and in this embodiment, DRB1 and DRB2 are taken as examples for illustration, as shown in fig. 3B, according to first information sent by an access network device, a terminal device completes the following configuration: the PDCP entity of the DRB1 of the terminal device corresponds to four RLC entities, wherein, from left to right, the first two RLC entities correspond to MCG MAC entities, the second two RLC entities correspond to SCG MAC entities, the transmission mode of the first and fourth RLC entities is UM, and the transmission mode of the second and third RLC entities is AM. The PDCP entity of the DRB2 of the terminal device corresponds to two RLC entities, wherein the two RLC entities correspond to an SCG MAC entity, a transmission mode of the first RLC entity is AM, and a transmission mode of the second RLC entity is UM.

Optionally, there may be an association relationship or no association between RLC entity modes between different Cell Groups (CGs). For example, the transmission mode of the RLC entity of one CG is AM, and the transmission mode of the RLC entity of the other CG is a transmission mode other than AM. For example, the transmission mode of the RLC entity of one CG is AM, and the transmission mode of the RLC entity of another CG may be AM or other transmission modes.

In an implementation manner of the first information of the above embodiment, the first information may include at least one of the following information: the apparatus includes RLC mode information indicating a transmission mode type of an RLC entity, and RLC activation indication information indicating that a plurality of RLC entities activate data duplication transmission. Wherein the RLC activation indication information is used for indicating a data duplication transmission state of the RLC entity, and the data duplication transmission state includes at least one of: and (5) activating and deactivating. For example, the RLC mode information is used to indicate that the transmission modes of four RLC entities corresponding to the DRB1 are AM and UM, and the terminal device determines that the RLC entity of AM is activated according to the RLC activation indication information, or the terminal device determines that the RLC entities of AM and UM are activated according to the RLC activation indication information, or the terminal device determines that the RLC entity activated in the corresponding RLC entities is activated according to the RLC activation indication information.

It should be noted that, the activation and deactivation are used to indicate whether to use the RLC entity for duplicated data transmission, and may also be: the terms used and not used are used and not replaced to indicate the same functions, and the names are not limited by the terms.

In one implementation, the RLC activation indication information may include at least one of an identification of an RLC entity, an identification of a logical channel, and an identification of a CG. It is understood that, of course, the RLC entity identifier and the CG identifier may be replaced by other information to implement the same function as the RLC entity identifier and the CG identifier of the RLC activation indication information, which is not necessarily illustrated in this embodiment of the present invention.

It should be noted that, on the basis of the foregoing embodiment, the method of the embodiment of the present application may further include: when the access network equipment determines that the transmission mode of the duplicated data needs to be changed, updated RLC activation indication information can be sent to the terminal equipment through the dedicated message, and the updated RLC activation indication information is used for indicating one or more RLC entities to activate/deactivate data duplication transmission.

For example, the access network device configures the transmission of the duplicated data into the configuration shown in fig. 3A by using the first information, and instructs the first RLC entity and the second RLC entity to activate data duplication transmission, that is, activate the RLC entity whose transmission mode is AM, that is, the RLC entity of AM transmits the duplicated data, and then, when the access network device needs to change the transmission mode of the duplicated data, the access network device sends updated RLC activation indication information to the terminal device, so as to implement that the RLC entity of UM is activated, and switches to the RLC entity of UM to transmit the duplicated data.

The above implementation manner can implement the transmission flexibility of the duplicated data, for example, the transmission manner of the duplicated data can be configured or updated according to the channel quality, so as to improve the utilization rate of the wireless resource while ensuring the transmission delay and the transmission reliability.

The transmission method of the duplicated data in the embodiment of the present application further relates to a data transmission process, and specifically, refer to the specific description of the embodiment shown in fig. 4.

Fig. 4 is a flowchart of a transmission method of duplicated data according to an embodiment of the present application, and as shown in fig. 4, in this embodiment, transmission of duplicated data is implemented on the basis of the configuration process of the embodiment shown in fig. 2, and the method of this embodiment may include:

step 201, the access network device determines the first information.

Step 202, the access network device sends the first information to the terminal device.

For the explanation of step 201 to step 202, refer to step 101 to step 102 in the embodiment shown in fig. 2, which is not described herein again.

Step 203, the terminal device transmits the copied data according to the first information.

And the terminal equipment adopts one or more RLC transmission modes to transmit the duplicated data of the same radio bearer or the same PDCP entity according to the first information. The transmission may be uplink data transmission or downlink data transmission.

Taking fig. 3A as an example for further illustration, through the above step 201 and step 202, the configuration shown in fig. 3A can be implemented, and the step 203 is explained by taking the duplicated data transmission of the DRB1 as an example, the PDCP entity of the terminal device can send 4 pieces of duplicated data (the original PDCP data PDU and 3 pieces of duplicated data of the original PDCP data PDU) to the corresponding RLC entities, respectively, and each RLC entity transmits the duplicated data according to its own transmission mode configuration.

The embodiment of the application configures a plurality of RLC transmission modes for the duplicated data of the same radio bearer or the same PDCP entity, can realize flexible configuration of the RLC transmission modes, and meets the requirements of transmission delay and transmission reliability. The terminal device may transmit the duplicated data in one or more RLC transmission modes based on the first information, thereby implementing a more flexible and efficient transmission mode of the duplicated data, and further satisfying the requirements of some service scenarios (e.g., IIoT).

The transmission method of the duplicated data in the embodiment of the present application further relates to a processing procedure of the duplicated data, and the following embodiments are adopted to specifically explain the processing procedure of the duplicated data related to the transmission method of the duplicated data in the embodiment of the present application.

It should be noted that, an execution main body of the processing procedure of the duplicated data in the following embodiments of the present application is a sending end, where the sending end may be a terminal device or an access network device, where for uplink data transmission, the sending end is a terminal device, that is, the terminal device executes the method steps in the following embodiments, and for downlink data transmission, the sending end is an access network device, that is, the access network device executes the method steps in the following embodiments.

It should be further noted that the processing procedure of the duplicated data according to the following embodiments of the present application is applicable to any transmission mode of the duplicated data. For example, the transmission may be performed in a manner of a mixture of RLC transmission modes as described in the above embodiment, or in a manner of one RLC transmission mode.

The following embodiments may be executed after the method steps shown in fig. 2 or fig. 4, or may be executed after the RLC entity is configured by using the configuration mode of other RLC entities.

Fig. 5 is a flowchart of a transmission method of duplicated data according to an embodiment of the present application, where as shown in fig. 5, an execution main body of this embodiment is a sending end, and this embodiment may perform packet loss processing to reduce redundant transmission of duplicated data and reduce waste of air interface resources, where the method of this embodiment may include:

step 301, determining whether the set condition is satisfied, if yes, executing step 302.

The set condition is used to indicate that the transmission of the duplicated data of the PDCP entity is completed, or the transmission is successful, or can be discarded. As illustrated in fig. 3A, four RLC entities of the PDCP entity of the DRB1 are all in an active state/configured to transmit duplicated data, assuming that the PDCP entity of the DRB1 at the transmitting end duplicates data to four duplicated data, and sends the duplicated data to the four RLC entities respectively, and the four RLC entities transmit the received duplicated data and transmit the duplicated data to the receiving end through an air interface, during transmission of the duplicated data, it may be determined through step 301 whether transmission of the duplicated data by the PDCP entity of the DRB1 is completed, or transmission is successful, or the duplicated data may be discarded. When the setting condition is satisfied, the following step 302 is executed. For example, when the third RLC entity transmits the duplicated data completely, or successfully, or exceeds a predetermined time period as shown in fig. 3A, it is determined that the set condition is satisfied.

Step 302, discard the duplicated data of the PDCP entity.

Through step 302, the duplicated data of the PDCP entity may be discarded to reduce air interface resource waste. As further illustrated in fig. 3A, the sending end may discard the duplicated data transmitted by the first RLC entity, the second RLC entity, and the fourth RLC entity of the DRB1, that is, discard the duplicated data in the sending end, which is the same as the duplicated data transmitted by the third RLC entity. Since the transmission mode of the third RLC entity is UM, the transmission modes of the first RLC entity and the second RLC entity are AM, and the third RLC entity transmits the duplicated data earlier than the first RLC entity and the second RLC entity, the reason may be that the RLC entity of AM still has a buffer of the duplicated data due to link or ARQ, that is, the RLC entity of UM has been transmitted completely due to resource limitation or transmission failure due to channel quality problem. Optionally, the discarded duplicated data may be at least one of: the duplicated data sent by the RLC PDU is formed, the duplicated data not sent by the RLC PDU is formed, the PDCP PDU of the RLC PDU is not formed, and the RLC SDU corresponding to the duplicated data is formed. By the embodiment of the application, when the transmission of the duplicated data of the PDCP entity is finished or successfully transmitted, other identical duplicated data can be discarded, so that redundant transmission of the duplicated data is reduced, and waste of air interface resources is reduced.

In this embodiment, for the duplicated data transmitted by any PDCP entity, if a set condition is satisfied, the duplicated data of the PDCP entity is discarded, where the set condition is used to indicate that the transmission of the duplicated data of the PDCP entity is completed, or the transmission is successful, or the duplicated data can be discarded, so as to reduce redundant transmission of the duplicated data and reduce waste of air interface resources.

The specific setting of the setting conditions can be flexibly set according to the requirements,

one implementation, the set condition includes a duplicate data transmission timeout.

In another implementation manner, the setting condition is to determine second information, where the second information is used to indicate that the transmission of the duplicated data is successful.

The second information may be based on any of the following granularities: one radio bearer, one or more radio bearers carrying duplicated data, a plurality of radio bearers, one or more PDCP entities.

The second information may be determined by at least one of: HARQ feedback information, ARQ feedback information, PDCP status PDU. Optionally, the sending end determines whether the transmission of the duplicated data is successful according to at least one of HARQ feedback information, ARQ feedback information, and PDCP status PDU. For example, optionally, the sending end determines whether the transmission of the duplicated data is successful according to at least one of HARQ-ACK, ARQ-ACK, PDCP status PDU, SN, and HARQ process identification (process ID). And if the transmission is successful, determining the second information.

Explanation is made on the setting condition including the copy data transmission timeout: step 301 is to determine whether the transmission of the duplicated data is overtime, and if yes, step 302 is executed, so as to reduce redundant transmission of the duplicated data and reduce waste of air interface resources.

One way to implement the timeout of the transmission of the duplicated data is that the transmission time of the duplicated data exceeds a first set time, which may be preset or indicated by the access network device. The duration of the first set time and the starting point of the first set time may be flexibly set according to requirements, for example, a PDCP entity of the radio bearer may transmit the duplicated data downwards as the starting point, and determine whether the duplicated data of the PDCP entity is transmitted for more than a duration. When the transmission time of the duplicated data of the PDCP entity exceeds the first set time, the PDCP entity of the radio bearer at the transmitting end sends a first indication to an RLC entity transmitting the same duplicated data, where the first indication is used to indicate that the duplicated data is discarded.

Alternatively, the first set time may be implemented by a timer. Namely, the first timer set by the PDCP entity of the radio bearer is overtime, the duplicated data of the PDCP entity is discarded. The first timer may be predefined or indicated by the network (e.g., access network device). The triggering condition of the first timer may be that the PDCP entity of the radio bearer transmits the duplicate data downward, and a specific embodiment is used to explain an implementation manner of the first timer.

Fig. 6 is a flowchart of a transmission method of duplicated data according to an embodiment of the present application, as shown in fig. 6, this embodiment is a specific implementable manner of performing packet loss processing according to the embodiment shown in fig. 5, in this embodiment, each functional entity of one radio bearer at a sending end adopts DRB1 configuration shown in fig. 3A for example, and the method of this embodiment may include:

step 401, when the PDCP entity of the radio bearer delivers the copied data downwards, the first timer is started.

Specifically, for example, when there is data to be transmitted that needs to be transmitted through the DRB1 and duplicate data transmission needs to be performed, the PDCP entity duplicates the data to be transmitted into four copies of the data and transmits the four copies of the data to the four RLC entities, and when the PDCP entity delivers the duplicate data downward, the first timer is started, that is, the triggering condition of the first timer is that the PDCP entity delivers the duplicate data downward.

Step 402, when the first timer is expired, the PDCP entity sends a first indication to the corresponding RLC entity, where the first indication is used to indicate that the duplicated data is discarded. The corresponding RLC entity refers to an RLC entity that transmits the same duplicated data.

This is further explained by the above example, wherein the PDCP entity sends the first indication to the four RLC entities, and the first indication is used to indicate that duplicate data is discarded.

Step 403, the RLC entity discards the duplicated data according to the first indication.

Specifically, the four RLC entities discard the duplicated data transmitted by the PDCP according to the first indication, and specifically, the duplicated data that needs to be discarded may be determined according to the PDCP sequence number and discarded, that is, the duplicated data is not retransmitted through an air interface.

In this embodiment, when the PDCP entity of the radio bearer submits the duplicated data downward, the first timer is started, and when the first timer expires, the PDCP entity sends a first indication to the corresponding RLC entity, and the RLC entity discards the duplicated data according to the first indication, thereby reducing redundant transmission of the duplicated data and reducing waste of air interface resources.

The "corresponding RLC entity" referred to in the above embodiments specifically refers to an RLC entity corresponding to the PDCP entity and used for transmitting the same duplicated data.

Another implementation manner of the duplicated data transmission timeout is that the duplicated data transmission time of any first RLC entity exceeds a second set time, and any first RLC entity is any RLC entity corresponding to the PDCP entity. The second predetermined duration of any one of the first RLC entities may or may not be related. The second set time may be preset or may be indicated by the access network device. The duration of the second set time and the starting point of the first set time can be flexibly set according to requirements, for example, the RLC entity of the PDCP entity transmits the duplicated data downwards as the starting point, and whether the duplicated data is transmitted for more than a duration is determined. When the transmission time of the duplicated data of any first RLC entity exceeds a second set time, the first RLC entity of the sending end sends a second instruction to a PDCP entity of the radio bearer, wherein the second instruction is used for instructing to discard the duplicated data, and the PDCP entity sends the second instruction to other RLC entities which transmit the same duplicated data in the radio bearer.

The first RLC entity refers to an RLC entity for triggering packet loss processing among a plurality of RLC entities transmitting the same duplicated data, and the first RLC entity is only used for distinguishing the RLC entity for triggering packet loss processing from the RLC entity for performing packet loss processing among the plurality of RLC entities. The transmission mode of the first RLC entity includes, but is not limited to, at least one of: AM, UM, TM. In particular, the first RLC entity may be a specific RLC entity, such as a specific transmission mode RLC entity, a network-specific RLC entity, or a primary RLC entity, or a predetermined RLC entity.

Another implementation manner of discarding the duplicated data may be that the first RLC entity sends information indicating a transmission status of the duplicated data to the PDCP entity, and the PDCP entity sends a second indication to other RLC entities transmitting the same duplicated data corresponding to the same PDCP entity according to the information indicating the transmission status of the duplicated data. Further, the information for indicating the status of the duplicated data transmission may further include PDCP SNs.

Alternatively, the second set time may be implemented by a timer. That is, if the second timer times out, the copied data is discarded. The second timer may be predefined or indicated by the network (e.g., access network device). The triggering condition of the second timer may be that the first RLC entity transmits the duplicated data downwards or that the first RLC entity receives the duplicated data from the PDCP entity, and a specific embodiment is used to explain an implementation of the second timer.

Fig. 7 is a flowchart of a transmission method of duplicated data according to an embodiment of the present application, as shown in fig. 7, this embodiment is a specific implementation manner of performing packet loss processing according to the embodiment shown in fig. 5, in this embodiment, each functional entity of one radio bearer of a sending end adopts the DRB1 configuration shown in fig. 3A, and a third RLC entity of DRB1 is taken as an example for illustration, where a transmission mode of the third RLC entity is UM, and the method of this embodiment may include:

step 501, when the first RLC entity submits to the MAC entity or the first RLC entity receives the duplicated data from the PDCP entity, starting a second timer of the first RLC entity.

Specifically, for example, when there is data to be transmitted that needs to be transmitted through the DRB1 and duplicate data transmission needs to be performed, the PDCP entity duplicates the data to be transmitted into four copies of data (including the data itself to be transmitted) and transmits the data to four RLC entities, each RLC entity is provided with a second timer, and a trigger condition of the second timer is that the RLC entity receives the duplicate data or the RLC entity transmits the duplicate data to the MAC entity.

Step 502, when a second timer of any first RLC entity times out, the PDCP entity sends a second indication to the other RLC entities, where the second indication is used to indicate that the duplicated data is discarded.

The other RLC entities are RLC entities other than the first RLC entity that transmit the same duplicated data.

Specifically, when the second timer of any first RLC entity times out, the first RLC entity may notify the PDCP entity, so that the PDCP entity sends the second indication to other RLC entities.

The second timer of the third RLC entity is expired, and the third RLC entity triggers the PDCP entity to send a second indication to other RLC entities (such as the first RLC entity, the second RLC entity, and the fourth RLC entity in fig. 3A) that transmit the same duplicated data in the same radio bearer, where the second indication is used to indicate that the duplicated data is discarded.

In one implementation, the third RLC entity sends a second indication to the first RLC entity, the second RLC entity, and the fourth RLC entity through the PDCP entity to indicate that duplicate data is discarded.

In another implementation, the third RLC entity sends information indicating that the transmission of the duplicated data is successful to the PDCP entity, and the PDCP entity sends a second indication to the first RLC entity, the second RLC entity, and the fourth RLC entity according to the information indicating that the transmission of the duplicated data is successful, so as to indicate that the duplicated data is discarded.

In step 503, other RLC entities transmitting the same duplicated data discard the duplicated data according to the second indication.

Specifically, the first RLC entity, the second RLC entity, and the fourth RLC entity discard the duplicated data transmitted by the PDCP according to the second indication, and may specifically determine the duplicated data that needs to be discarded according to the PDCP sequence number, and discard the duplicated data, that is, the duplicated data is not retransmitted through an air interface.

In this embodiment, when the first RLC entity submits to the MAC entity or the first RLC entity receives the duplicated data from the PDCP entity, the second timer is started, and when the second timer expires, the first RLC entity sends a second instruction to other RLC entities transmitting the same duplicated data, where the second instruction is used to instruct to discard the duplicated data, and the other RLC entities transmitting the same duplicated data discard the duplicated data according to the second instruction, so that redundant transmission of the duplicated data is reduced, and waste of air interface resources is reduced.

Explaining that the setting condition includes determining second information which is used for indicating that the transmission of the duplicated data is successful: step 301 is to determine whether to determine the second information for the duplicated data transmitted by any PDCP entity, and if so, step 302 is executed, thereby reducing redundant transmission of duplicated data and reducing waste of air interface resources.

The second information may be determined by the first RLC entity, or the first MAC entity, or the PDCP entity, and when/after the first RLC entity, or the first MAC entity, or the PDCP entity determines the second information, the PDCP entity instructs the corresponding RLC entity to discard the duplicated data.

Wherein, one realizable mode of the second information is as follows: the second information is determined by the first RLC entity.

For example, the second RLC entity determines the second information according to ARQ feedback information, which may include acknowledgement information for duplicated data, and accordingly, a specific implementation manner of step 302 is: the second RLC entity sends a third indication to a higher layer (e.g., PDCP entity), the third indication indicating duplicate data discard or transmission success acknowledgement, the third indication including at least one of: the second information, the RLC sequence number of the duplicated data of the second RLC entity, the PDCP sequence number of the duplicated data, the PDCP entity instructing the corresponding RLC entity to discard the duplicated data. The RLC entity discards the duplicated data according to the indication of the PDCP entity.

Wherein, another realizable way of the second information is: the second information is determined by a first MAC entity, which is a MAC entity corresponding to the PDCP entity.

For example, the first MAC entity determines the second information according to Hybrid Automatic Repeat reQuest (HARQ) feedback information, where a MAC PDU corresponding to the HARQ feedback information includes duplicated data of at least one third RLC entity of the radio bearer. The HARQ feedback information may include an Acknowledgement (ACK) message for the duplicated data, and one specific implementation manner of step 302 is: the first MAC entity transmits the second information or information indicating duplicate data discard or transmission success acknowledgement to a higher layer (e.g., the third RLC entity); the third RLC entity sends a fourth indication to a higher layer (e.g., PDCP entity), the fourth indication indicating duplicate data discard or transmission success acknowledgement, the fourth indication including at least one of: the second information, the RLC sequence number of the duplicated data of the third RLC entity, and the PDCP sequence number of the duplicated data, the PDCP entity instructing the corresponding RLC entity to send the discarded duplicated data.

It should be noted that the RLC sequence number and the PDCP sequence number may be determined by at least one of: the MAC entity determination, the RLC entity determination, the PDCP entity determination, or the MAC entity determination may be carried in the feedback information.

Another implementation of the second information is: the second information is determined by the PDCP entity.

For example, the PDCP entity determines the second information according to the received PDCP status PDU, which may include an acknowledgement message for the duplicated data, and accordingly, a specific implementation manner of step 302 is: the PDCP entity transmits a fifth indication for indicating the discard of duplicated data to the corresponding RLC entity.

A specific application scenario is used to explain the processing procedure of the second information being the duplicated data determined according to the HARQ feedback information.

Fig. 8A is a schematic configuration diagram of multiple RLC entities corresponding to a radio bearer according to an embodiment of the present application, and as shown in fig. 8A, according to first information sent by an access network device, a terminal device completes the following configuration: the PDCP entity of the DRB1 of the terminal device corresponds to two RLC entities, wherein, from left to right, the first RLC entity corresponds to an MCG MAC entity, the second RLC entity corresponds to an SCG MAC entity, the transmission mode of the first RLC entity is UM, and the transmission mode of the second RLC entity is AM. And the other DRB: the PDCP entity of the DRB2 corresponds to two RLC entities corresponding to the SCG MAC entity, wherein from left to right, the transmission mode of the first RLC entity is AM, and the transmission mode of the second RLC entity is UM. Therein, it is assumed that duplicate data transmission of two RLC entities of DRB1 is active.

Fig. 8B is a flowchart of a processing procedure of the copied data in the scenario shown in fig. 8A according to an embodiment of the present application, and as shown in fig. 8B, the method of this embodiment may include:

step 601, when the first MAC entity determines the second information according to the HARQ feedback information, the first MAC entity sends the second information to the third RLC entity, the third RLC entity sends a fourth instruction to the PDCP entity, and the PDCP entity instructs the RLC entity transmitting the same duplicated data to discard the duplicated data.

Specifically, when the first MAC entity receives the HARQ feedback information, for example, HARQ-ACK, the second information may be determined according to the HARQ feedback information.

Before step 601, a MAC entity (e.g., an MCG MAC entity shown in fig. 8A) at a transmitting end packages duplicated data of an RLC entity, generates a MAC PDU, transmits the MAC PDU through a physical layer, and stores duplicated data information, which may include at least one of duplicated data existence identification and corresponding RLC SN, PDCP SN, RLC entity or logical channel identification. The duplicated data information may be stored in the MAC PDU, or may be stored in the HARQ process/entity corresponding to the MAC PDU.

The receiving end receives the duplicated data (it is assumed that the successfully received duplicated data is the duplicated data transmitted by the first RLC entity as shown in fig. 8A), and carries the feedback information of the duplicated data in HARQ. A first MAC entity (e.g., an MCG MAC entity shown in fig. 8A) at a transmitting end receives HARQ feedback information from a receiving end, the first MAC entity determines, according to the duplicated data information, that the HARQ feedback information explicitly or implicitly includes the feedback information of the duplicated data, and when the feedback information is HARQ-ACK, the first MAC entity determines, according to the HARQ-ACK, second information and sends the second information to the first RLC entity, that is, the first RLC entity is the third RLC entity. The first RLC entity indicates to other RLC entities transmitting the same duplicated data that have lost packets. In one implementation, the first RLC entity sends the fourth indication to a PDCP entity, and the PDCP entity instructs RLC entities transmitting the same duplicated data to discard the duplicated data. In another implementation, the first RLC entity sends the fourth indication to a PDCP entity, and the PDCP entity sends the fourth indication to RLC entities that transmit the same duplicated data.

The fourth indication includes, but is not limited to, at least one of: RLC SN, PDCP SN, packet loss indication/successful transmission indication.

In step 602, the RLC entity transmitting the same duplicated data discards the duplicated data.

In the scenario shown in fig. 8A, the second RLC entity discards duplicated data. Specifically, the second RLC entity may determine duplicate data that needs to be discarded according to the PDCP SN and discard the duplicate data.

Optionally, the RLC entity may also store and determine the corresponding PDCP SN according to the RLC SN.

Therefore, it can be seen that the HARQ feedback information may determine that the transmission of the duplicated data of the first RLC entity of the UM shown in fig. 8A is successful, so as to improve the transmission reliability of the RLC entity of the UM, and when the transmission of the duplicated data of the first RLC entity is successful, the second RLC entity of the AM is triggered to perform packet loss through the fourth indication, so as to avoid redundant transmission of the duplicated data, and reduce waste of air interface resources.

In this embodiment, when the first MAC entity receives the HARQ feedback information, the first MAC entity determines the second information according to the HARQ feedback information, the first MAC entity sends the second information to the third RLC entity, the third RLC entity sends a fourth instruction to the PDCP entity, the PDCP entity instructs the RLC entities transmitting the same duplicated data to discard the duplicated data, and the RLC entities transmitting the same duplicated data to discard the duplicated data, which can avoid redundant transmission of the duplicated data and reduce waste of air interface resources.

A specific application scenario is used to explain the processing procedure of the second information for the duplicated data determined according to the PDCP status PDU.

Fig. 9A is a schematic view of an application scenario of a processing procedure of duplicated data according to an embodiment of the present application, and as shown in fig. 9A, a UE is taken as a sending end, and a gNB is taken as a receiving end for illustration, and the gNB may configure a transmission mode of the duplicated data of the UE according to the embodiment of the configuration procedure, and configure the transmission mode into a mixture of UM and AM shown in fig. 9A, that is, the transmission modes of two RLC entities corresponding to the PDCP of the DRB1 are respectively configured into UM and AM. It can be understood that the transmission modes of the two RLC entities corresponding to the PDCP of DRB1 of the gNB are the same as the UE.

Fig. 9B is a flowchart of a processing procedure of the copied data in the scenario shown in fig. 9A according to an embodiment of the present application, and as shown in fig. 9B, the method of this embodiment may include:

step 701, when the PDCP entity determines the second information according to the PDCP status PDU, the PDCP entity sends a fifth indication to the RLC entity which transmits the same duplicated data, where the fifth indication is used to indicate to discard the duplicated data.

Specifically, the PDCP entity of the transmitting end receives the PDCP status PDU, and may determine the second information according to the PDCP status PDU.

Before step 701, the MAC entity at the transmitting end (e.g., the MAC entity of the UE shown in fig. 9A) packages the duplicated data from the RLC entity to generate a MAC PDU, and transmits the MAC PDU to the MAC entity at the receiving end (e.g., the MAC entity of the gNB shown in fig. 9A) through the physical layer. The MAC entity of the receiving end transmits the MAC PDU to a high layer, the PDCP entity of the receiving end receives the copied data and sends a PDCP status PDU to the transmitting end for indicating the successful receiving of the copied data. Or, when the PDCP of the receiving end meets a certain period, the receiving end sends a PDCP status PDU to the transmitting end, which is used to indicate the copied data successfully received in the period.

The MAC entity of the sending end receives the PDCP status PDU and transmits the PDCP status PDU to a high layer, and when the PDCP entity of the sending end receives the PDCP status PDU, the MAC entity indicates other RLC entities transmitting the same copied data to perform packet loss. The indication manner may specifically be through the fifth indication, or may be through packet loss indication by using other information, which is not illustrated here.

In step 702, the RLC entity transmitting the same duplicated data discards the duplicated data.

In the application scenario of fig. 9A, assuming that the PDCP status PDU is a transmission acknowledgement of duplicate data of the first RLC entity of the UE, the PDCP entity instructs the second RLC entity to discard the same duplicate data to avoid redundant transmission. Specifically, the second RLC entity may determine duplicate data that needs to be discarded according to the PDCP SN and discard the duplicate data.

Therefore, it can be determined that the duplicated data of the first RLC entity of UM shown in fig. 9A is successfully transmitted through the PDCP status PDU, so as to improve the transmission reliability of the RLC entity of UM, and when the duplicated data of the first RLC entity is successfully transmitted, the second RLC entity of AM is triggered to perform packet loss through the fourth indication, so that redundant transmission of duplicated data can be avoided, and waste of air interface resources is reduced.

In this embodiment, when the PDCP entity of the sending end receives the PDCP status PDU, the PDCP entity determines the second information according to the PDCP status PDU, and the PDCP entity sends a fifth instruction to the RLC entity that transmits the same duplicated data, where the fifth instruction is used to instruct to discard the duplicated data, and the RLC entity that transmits the same duplicated data discards the duplicated data, so that redundant transmission of the duplicated data can be avoided, and waste of air interface resources is reduced.

A specific application scenario is used to explain the processing procedure of the second information being the duplicated data determined according to the ARQ feedback information.

Fig. 10 is a flowchart of a processing procedure of duplicated data in the scenario shown in fig. 9A according to an embodiment of the present application, and this embodiment explains, by using an application scenario configured in the same manner as that in fig. 9A, a processing procedure in which the second information is duplicated data determined according to ARQ feedback information, and as shown in fig. 10, a method according to this embodiment may include:

step 801, when the second RLC entity determines the second information according to the ARQ feedback information, the second RLC entity sends a third indication to the PDCP entity, where the third indication is used to indicate discard of duplicated data or transmission success confirmation, and the PDCP entity indicates the corresponding RLC entity to discard duplicated data.

The second RLC entity of the sending end receives the ARQ feedback information, and the second RLC entity may determine the second information according to the ARQ feedback information.

For example, the PDCP entity receives at least one of the following information from the bottom layer: SN, second information. Optionally, when the PDCP entity receives the above information, the PDCP entity considers that the successful transmission indication of the PDCP packet/duplicate transmission packet is received

For example, the lower layer, e.g., RLC entity, upon receiving an ARQ-ACK, delivers at least one of the following information to the higher layer: SN, second information.

To illustrate by taking the second information as the ARQ-ACK of the RLC entity of the AM of fig. 9A as an example, the PDCP entity instructs to discard the duplicated data to the RLC entity of the UM of fig. 9A.

Step 802, the RLC entity transmitting the same duplicated data discards the duplicated data.

In the application scenario of fig. 9A, the RLC entity of UM may determine the duplicated data that needs to be discarded according to the PDCP SN, and discard the duplicated data.

Therefore, it can be seen that the transmission success of the duplicated data of the RLC entity of the AM shown in fig. 9A can be determined through the ARQ feedback information, and when the transmission success of the duplicated data of the RLC entity of the AM is achieved, the RLC entity of the UM is triggered to perform packet loss through the fifth indication, so that redundant transmission of the duplicated data can be avoided, and waste of air interface resources is reduced.

It should be noted that the ARQ feedback information may also be an acknowledgement of duplicate data transmitted by the UM or TM RLC entity, and the embodiment of the present application is not limited to the above illustration.

In this embodiment, when the second RLC entity of the sending end receives the ARQ feedback information, the second RLC entity determines the second information according to the ARQ feedback information, and sends a third indication to the PDCP entity, where the third indication is used to indicate discard of duplicated data or successful transmission confirmation, the PDCP entity indicates the corresponding RLC entity to discard the duplicated data, and the RLC entity transmitting the same duplicated data discards the duplicated data, so that redundant transmission of the duplicated data can be avoided, and waste of air interface resources is reduced.

The transmission method of the duplicated data provided in the embodiment of the present application is described above in detail, and the terminal device and the access network device provided in the embodiment of the present application are described below.

Fig. 11 is a schematic structural diagram of a terminal device according to an embodiment of the present application. The embodiment provides a terminal device. The terminal device can also be called a UE, access terminal, subscriber unit, subscriber station, mobile station, user terminal, wireless communication device, user agent, or user equipment. The terminal device may be a smartphone, a cellular phone, a cordless phone, a tablet, a PDA device, a handheld device with wireless communication capabilities or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, etc. As shown in fig. 11, the terminal device includes:

a receiving module 101, configured to receive first information, where the first information is used to indicate: at least two radio links of the same radio bearer or of duplicate data of the same packet data convergence protocol PDCP entity control RLC transmission modes.

Optionally, the processing module 102 is configured to transmit the duplicated data according to the first information, and control the sending module 103 to send the duplicated data to the access network device.

Optionally, the first information is specifically used to indicate: and each radio bearer or each PDCP entity corresponds to at least two RLC entities, and the at least two RLC entities correspond to at least two RLC transmission modes.

Optionally, the first information is specifically used to indicate: one or more of the RLC entities correspondingly adopt one of the RLC transmission modes.

Optionally, the RLC transmission mode is cell group dependent, or independent.

Optionally, the first information is further used to indicate: one or more RLC entities of the same cell group correspond to one RLC transmission mode; or, one or more RLC entities of the same cell group correspond to different RLC transmission modes.

Optionally, the first information includes at least one of the following information: the RLC mode information is used for indicating the transmission mode type of an RLC entity, and the RLC activation indication information is used for indicating the data copying transmission state of the RLC entity.

Optionally, the data replication transmission state includes at least one of: and (5) activating and deactivating.

Optionally, the processing module 102 is further configured to: and if the set condition is met, discarding the copied data, wherein the set condition is used for indicating that the copied data is transmitted completely or successfully or can be discarded.

Optionally, the processing module 102 is configured to: instructing, by the PDCP entity, the corresponding RLC entity to discard the duplicated data.

Optionally, the setting conditions include: the replicated data transmission is timed out; or determining second information, wherein the second information is used for indicating that the transmission of the copied data is successful.

Optionally, the time-out of the transmission of the duplicated data includes: the transmission time of the copied data exceeds a first set time.

Optionally, the processing module 102 is configured to: sending a first indication to a corresponding RLC entity through the PDCP entity, wherein the first indication is used for indicating that duplicated data is discarded.

Optionally, the time-out of the transmission of the duplicated data includes: and the transmission time of the duplicated data of any first RLC entity exceeds a second set time, wherein the any first RLC entity is any RLC entity corresponding to the PDCP entity.

Optionally, the processing module 102 is configured to: sending, by the PDCP entity, a second indication to other RLC entities, the second indication being for the other RLC entities to discard duplicate data; the other RLC entities are RLC entities other than the first RLC entity which transmit the same duplicated data.

Optionally, the second information is determined by a second RLC entity.

Optionally, the processing module 102 is further configured to: sending a third indication to a higher layer through the second RLC entity, wherein the third indication is used for indicating the discard of the duplicated data or the successful confirmation of the transmission; the third indication comprises at least one of: the second information, the RLC sequence number of the second RLC entity, the PDCP sequence number.

Optionally, the processing module 102 is further configured to: determining, by the second RLC entity, the second information according to automatic repeat request (ARQ) information.

Optionally, the second information is determined by a first MAC entity, where the first MAC entity is a MAC entity corresponding to the PDCP entity.

Optionally, the processing module 102 is further configured to: sending the second information to a higher layer through the first MAC entity; the third RLC entity sends the fourth indication to a higher layer, wherein the fourth indication is used for indicating the discard of the duplicated data or the successful confirmation of the transmission; the fourth indication comprises at least one of: the second information, the RLC sequence number of the third RLC entity, the PDCP sequence number.

Optionally, the processing module 102 is further configured to: and determining the second information according to hybrid automatic repeat request (HARQ) feedback information through the first MAC entity.

Optionally, the second information is determined by the PDCP entity.

Optionally, the processing module 102 is configured to: sending, by the PDCP entity, the fifth indication to a corresponding RLC entity, the fifth indication indicating that duplicate data is discarded.

Optionally, the processing module 102 is further configured to: determining, by the PDCP entity, the second information according to a PDCP STATUS PDU.

Optionally, the transmitting time of the duplicated data exceeds a first set time, including: the first timer of the PDCP entity expires.

Optionally, the starting time of the first timer is that the PDCP entity sends duplicated data to a plurality of corresponding RLC entities.

Optionally, the transmitting time of the duplicated data of any one of the first RLC entities exceeds a second set time, including: the second timer of the first RLC entity expires.

Optionally, the starting time of the second timer is that the first RLC entity sends the copied data to the medium access MAC entity, or the first RLC entity receives the copied data from the PDCP entity.

The terminal device of the embodiment of the present application may be configured to execute the technical solution executed by the terminal device in each of the method embodiments of the present application, and the implementation principle and the technical effect are similar, which are not described herein again.

Fig. 12 is a schematic structural diagram of a terminal device according to an embodiment of the present application. The terminal device can also be called a UE, access terminal, subscriber unit, subscriber station, mobile station, user terminal, wireless communication device, user agent, or user equipment. The terminal device may be a smartphone, a cellular phone, a cordless phone, a tablet, a PDA device, a handheld device with wireless communication capabilities or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, etc. As shown in fig. 12, the terminal device includes: a processor 111 and a memory 112.

The memory 112 stores computer-executable instructions;

the processor 111 executes the computer-executable instructions stored in the memory 112, so that the processor 112 executes the above-mentioned method for transferring the copied data.

Optionally, the terminal device further includes: a transceiver 113 for enabling communication with other network devices (e.g., access network devices) or terminal devices.

Fig. 13 is a schematic structural diagram of an access network device according to an embodiment of the present application. The embodiment provides an access network device. As shown in fig. 13, the access network device includes:

a processing module 121, configured to determine first information, where the first information is used to indicate: the duplicated data of the same packet data convergence protocol PDCP entity adopts at least two radio links to control the transmission mode transmission of RLC; a sending module 122, configured to send the first information.

Optionally, the access network device may further include a receiving module 123, configured to receive the duplicated data sent by the terminal device.

Optionally, the processing module 121 is further configured to: and transmitting the copied data according to the first information, and controlling the transmitting module 122 to transmit the copied data to the terminal device.

Optionally, the processing module 121 is further configured to: and if the set condition is met, discarding the copied data, wherein the set condition is used for indicating that the copied data is transmitted completely or successfully or can be discarded.

Optionally, the sending module 122 is further configured to: and sending configuration information, wherein the configuration information is used for indicating the first set time or the second set time.

The access network device of the embodiment of the present application may be configured to execute the technical solution executed by the access network device in each of the method embodiments described above, and the implementation principle and the technical effect are similar, which are not described herein again.

Fig. 14 is a schematic structural diagram of an access network device according to an embodiment of the present application. As shown in fig. 14, the access network device includes: a processor 131 and a memory 132.

The memory 132 stores computer-executable instructions;

the processor 131 executes the computer-executable instructions stored by the memory 132, so that the processor 132 executes the random access method described above.

Optionally, the access network device further includes: a transceiver 133 for enabling communication with other network devices (e.g., other access network devices) or terminal devices.

An embodiment of the present application further provides a computer-readable storage medium, where a computer executable instruction is stored in the computer-readable storage medium, and when the computer executable instruction is executed by a processor, the computer executable instruction is used to implement the steps executed by the terminal device or the access network device in any one of the transmission methods for duplicated data.

An embodiment of the present application further provides a computer program product, where the computer program product includes computer executable instructions, and the computer executable instructions, when executed by a processor, are configured to implement the steps executed by the terminal device or the access network device in any one of the transmission methods for duplicated data.

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

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

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 can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

Those of ordinary skill in the art will understand that: all or a portion of the steps of implementing the above-described method embodiments may be performed by hardware associated with program instructions. The computer program may be stored in a computer readable storage medium. The computer program, when executed by a processor, performs steps comprising the method embodiments described above; and the aforementioned storage medium includes: various media that can store program codes, such as ROM, RAM, magnetic or optical disks.

Finally, it should be noted that: the above embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present application.

Claims

A method for transmitting duplicated data, comprising:

the terminal equipment receives first information, wherein the first information is used for indicating that: at least two radio links of the same radio bearer or of duplicate data of the same packet data convergence protocol PDCP entity control RLC transmission modes.
The method of claim 1, further comprising:

and the terminal equipment transmits the copied data according to the first information.
The method according to claim 1 or 2, wherein the first information is specifically configured to indicate: and each radio bearer or each PDCP entity corresponds to at least two RLC entities, and the at least two RLC entities correspond to at least two RLC transmission modes.
The method according to claim 3, wherein the first information is specifically configured to indicate: one or more of the RLC entities corresponds to one of the RLC transmission modes.
Method according to claims 1 to 4, wherein the RLC transmission mode is cell group dependent or not.
The method of claim 5, wherein a plurality of RLC entities of a same cell group correspond to one of the RLC transmission modes;

or, a plurality of RLC entities of the same cell group correspond to different RLC transmission modes.
The method according to any of claims 3-6, wherein the first information comprises at least one of: RLC mode information and RLC activation indication information;

the RLC mode information is used for indicating the transmission mode type of an RLC entity, and the RLC activation indication information is used for indicating the data copying transmission state of the RLC entity.
The method of claim 7, wherein the data replication transmission state comprises at least one of: and (5) activating and deactivating.
The method of claim 1, further comprising:

and if the set condition is met, discarding the copied data, wherein the set condition is used for indicating that the copied data is transmitted completely or successfully or can be discarded.
The method of claim 9, wherein the discarding the duplicate data comprises: instructing, by the PDCP entity, the corresponding RLC entity to discard the duplicated data.
The method according to claim 10, wherein the setting conditions include:

the replicated data transmission is timed out; or determining second information, wherein the second information is used for indicating that the transmission of the copied data is successful.
The method of claim 11, wherein the duplicate data transmission timeout comprises:

the transmission time of the copied data exceeds a first set time.
The method as claimed in claim 12, wherein instructing, by the PDCP entity, the corresponding RLC entity to discard duplicated data comprises:

sending a first indication to a corresponding RLC entity through the PDCP entity, wherein the first indication is used for indicating that duplicated data is discarded.
The method of claim 11, wherein the duplicate data transmission timeout comprises:

and the transmission time of the duplicated data of any first RLC entity exceeds a second set time, wherein the any first RLC entity is any RLC entity corresponding to the PDCP entity.
The method of claim 14, wherein instructing, by the PDCP entity, the corresponding RLC entity to discard duplicate data comprises:

sending, by the PDCP entity, a second indication to other RLC entities, the second indication being for the other RLC entities to discard duplicate data;

the other RLC entities are RLC entities other than the first RLC entity which transmit the same duplicated data.
The method of claim 11, wherein the second information is determined by a second RLC entity.
The method of claim 16, further comprising:

sending a third indication to a higher layer through the second RLC entity, wherein the third indication is used for indicating the discard of the duplicated data or the successful confirmation of the transmission;

the third indication comprises at least one of: the second information, an RLC sequence number of duplicated data of the second RLC entity, and a PDCP sequence number of the duplicated data.
The method according to claim 16 or 17, further comprising:

determining, by the second RLC entity, the second information according to automatic repeat request (ARQ) information.
The method of claim 11, wherein the second information is determined by a first MAC entity, and wherein the first MAC entity is a MAC entity corresponding to the PDCP entity.
The method of claim 19, further comprising:

sending a fourth indication to a higher layer through a third RLC entity, wherein the fourth indication is used for indicating the discard of the duplicated data or the successful confirmation of the transmission, and the third RLC entity is the RLC entity corresponding to the first MAC entity;

the fourth indication comprises at least one of: the second information, an RLC sequence number of duplicated data of the third RLC entity, and a PDCP sequence number of the duplicated data.
The method according to claim 19 or 20, further comprising:

and determining the second information according to hybrid automatic repeat request (HARQ) feedback information through the first MAC entity.
The method of claim 11, wherein the second information is determined by the PDCP entity.
The method of claim 22, wherein instructing, by the PDCP entity, the corresponding RLC entity to discard duplicate data comprises:

sending, by the PDCP entity, a fifth indication to a corresponding RLC entity, the fifth indication indicating that duplicate data is discarded.
The method according to claim 22 or 23, further comprising:

determining, by the PDCP entity, the second information according to a PDCP STATUS PDU.
The method of claim 11, wherein the replicated data transmission time exceeds a first set time, comprising: the first timer of the PDCP entity expires.
The method of claim 25, wherein the first timer is started when the PDCP entity sends duplicate data to a corresponding plurality of RLC entities.
The method of claim 14, wherein the time for the duplicate data transmission of any of the first RLC entities exceeds a second set time, comprising: the second timer of the first RLC entity expires.
The method of claim 27, wherein the second timer is started when the first RLC entity sends the duplicated data to the medium access MAC entity or the first RLC entity receives the duplicated data from the PDCP entity.
A method for transmitting duplicated data, comprising:

the access network equipment determines first information, wherein the first information is used for indicating that: at least two radio links of the duplicated data of the same radio bearer or the same packet data convergence protocol PDCP entity control RLC transmission modes;

and the access network equipment sends the first information.
The method of claim 29, further comprising:

and the access network equipment transmits the copied data according to the first information.
The method of claim 30, further comprising:

and if the set condition is met, discarding the copied data, wherein the set condition is used for indicating that the copied data is transmitted completely or successfully or can be discarded.
The method of claim 31, wherein the setting conditions comprise:

the replicated data transmission is timed out; or determining second information, wherein the second information is used for indicating that the transmission of the copied data is successful.
The method according to any one of claims 29-32, further comprising:

the access network equipment sends configuration information, and the configuration information is used for indicating a first set time or a second set time.
A terminal device, comprising:

a receiving module, configured to receive first information, where the first information is used to indicate: at least two radio links of the same radio bearer or of duplicate data of the same packet data convergence protocol PDCP entity control RLC transmission modes.
The terminal device of claim 34, wherein the terminal device further comprises a processing module configured to transmit duplicate data according to the first information.
The terminal device of claim 35, wherein the processing module is further configured to:

and if the set condition is met, discarding the copied data, wherein the set condition is used for indicating that the copied data is transmitted completely or successfully or can be discarded.
The terminal device of claim 36, wherein the processing module is configured to: instructing, by the PDCP entity, the corresponding RLC entity to discard the duplicated data.
The terminal device according to claim 37, wherein the setting condition comprises:

the replicated data transmission is timed out; or determining second information, wherein the second information is used for indicating that the transmission of the copied data is successful.
The terminal device of claim 38, wherein the second information is determined by a second RLC entity.
The terminal device of claim 39, wherein the processing module is further configured to:

sending a third indication to a higher layer through the second RLC entity, wherein the third indication is used for indicating the discard of the duplicated data or the successful confirmation of the transmission;

the third indication comprises at least one of: the second information, the RLC sequence number of the second RLC entity, the PDCP sequence number.
The terminal device of claim 39 or 40, wherein the processing module is further configured to:

determining, by the second RLC entity, the second information according to automatic repeat request (ARQ) information.
The terminal device of claim 38, wherein the second information is determined by a first MAC entity, and wherein the first MAC entity is a MAC entity corresponding to the PDCP entity.
The terminal device of claim 42, wherein the processing module is further configured to:

sending a fourth indication to a higher layer through a third RLC entity, wherein the fourth indication is used for indicating the discard of the duplicated data or the successful transmission confirmation;

the fourth indication comprises at least one of: the second information, the RLC sequence number of the third RLC entity, the PDCP sequence number.
The terminal device of claim 42 or 43, wherein the processing module is further configured to:

and determining the second information according to hybrid automatic repeat request (HARQ) feedback information through the first MAC entity.
An access network device, comprising:

a processing module configured to determine first information, the first information indicating: at least two radio links of the duplicated data of the same radio bearer or the same packet data convergence protocol PDCP entity control RLC transmission modes;

and the sending module is used for sending the first information.
The access network device of claim 45, wherein the processing module is further configured to:

and transmitting the copied data according to the first information.
The access network device of claim 46, wherein the processing module is further configured to:

and if the set condition is met, discarding the copied data, wherein the set condition is used for indicating that the copied data is transmitted completely or successfully or can be discarded.
A terminal device, comprising: a processor and a memory;

the memory stores computer-executable instructions;

the processor executing the computer-executable instructions stored by the memory causes the processor to perform the method of transferring replicated data as recited in any of claims 1-28.
An access network device, comprising: a processor and a memory;

the memory stores computer-executable instructions;

the processor executing the computer-executable instructions stored by the memory causes the processor to perform the method of transferring replicated data as recited in any of claims 29 to 33.
A computer-readable storage medium having stored thereon computer-executable instructions for implementing the method of transferring replicated data according to any one of claims 1 to 28, or for implementing the method of transferring replicated data according to any one of claims 29 to 33, when the computer-executable instructions are executed by a processor.