CN109661831B - Method and device for controlling data copying and transmitting function - Google Patents

Method and device for controlling data copying and transmitting function Download PDF

Info

Publication number
CN109661831B
CN109661831B CN201780050539.XA CN201780050539A CN109661831B CN 109661831 B CN109661831 B CN 109661831B CN 201780050539 A CN201780050539 A CN 201780050539A CN 109661831 B CN109661831 B CN 109661831B
Authority
CN
China
Prior art keywords
rlc entity
bearer
srb
data transmission
terminal device
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201780050539.XA
Other languages
Chinese (zh)
Other versions
CN109661831A (en
Inventor
石聪
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Guangdong Oppo Mobile Telecommunications Corp Ltd
Original Assignee
Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Guangdong Oppo Mobile Telecommunications Corp Ltd filed Critical Guangdong Oppo Mobile Telecommunications Corp Ltd
Publication of CN109661831A publication Critical patent/CN109661831A/en
Application granted granted Critical
Publication of CN109661831B publication Critical patent/CN109661831B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/04—Error control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/22—Arrangements for detecting or preventing errors in the information received using redundant apparatus to increase reliability
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/08—Load balancing or load distribution
    • H04W28/082—Load balancing or load distribution among bearers or channels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/18—Management of setup rejection or failure

Abstract

The embodiment of the application provides a method and equipment for controlling a data copying and transmitting function of terminal equipment, which can control the data copying and transmitting function between a cell group and the terminal equipment, and can avoid the influence on subsequent data transmission when a transmission link has a problem. The method comprises the following steps: when data transmitted on a first bearer reaches the maximum retransmission times on a first Radio Link Control (RLC) entity, the terminal equipment suspends the data transmission on the first bearer, wherein the first bearer is a radio bearer for transmitting data in a data copying manner under a Carrier Aggregation (CA) scene; and the terminal equipment reports the RLF message.

Description

Method and device for controlling data copying and transmitting function
Technical Field
The embodiment of the invention relates to the field of communication, in particular to a method and equipment for controlling a data copying and transmitting function.
Background
In a Carrier Aggregation (CA) scenario, a plurality of network nodes (cell groups (CGs)) may serve a terminal device, and data replication may be performed between the network nodes and the terminal device.
In some scenarios, for a specific bearer, when data transmission on a Radio Link Control (RLC) entity of the bearer reaches a maximum transmission number, a data copy transmission function between a Control network node and a terminal device needs to be controlled to avoid affecting subsequent data transmission.
Disclosure of Invention
The embodiment of the application provides a method and equipment for controlling a data copying and transmitting function, which can control the data copying and transmitting function between a network node and terminal equipment and avoid the influence on subsequent data transmission.
In a first aspect, a method for controlling a data copy transmission function is provided, including: when data transmitted on a first bearer reaches the maximum retransmission times on a first Radio Link Control (RLC) entity, the terminal equipment suspends the data transmission on the first bearer, wherein the first bearer is a radio bearer for transmitting data in a data copying manner under a Carrier Aggregation (CA) scene; and the terminal equipment reports the RLF message.
With reference to the first aspect, in a possible implementation manner of the first aspect, the first RLC entity is an RLC entity of a main network node MCG or an RLC entity of a secondary network node SCG.
With reference to the first aspect, in a possible implementation manner of the first aspect, the first RLC entity of the first bearer transmits data only in a secondary cell.
With reference to the first aspect, in a possible implementation manner of the first aspect, the first bearer is a signaling radio bearer SRB or a data radio bearer DRB.
With reference to the first aspect, in a possible implementation manner of the first aspect, the suspending, by the terminal device, data transmission on the first bearer includes: and the terminal equipment suspends the data transmission of the first bearer on the PDCP layer and the RLC layer.
With reference to the first aspect, in a possible implementation manner of the first aspect, the suspending, by the terminal device, data transmission on the first bearer includes: and the terminal equipment suspends the data transmission of the first bearer on the RLC layer.
With reference to the first aspect, in a possible implementation manner of the first aspect, the suspending, by the terminal device, data transmission of the first bearer on an RLC layer includes: the terminal equipment suspends data transmission on the first RLC entity of the RLC layer.
With reference to the first aspect, in a possible implementation manner of the first aspect, the suspending, by the terminal device, data transmission on the first bearer includes: and the terminal equipment suspends data transmission on the first bearer and suspends data transmission on a second bearer at the same time, wherein a carrier set used by a second RLC entity of the second bearer for data transmission is at least partially overlapped with a carrier set used by the first RLC entity of the first bearer for data transmission.
With reference to the first aspect, in a possible implementation manner of the first aspect, at least a partial overlap between a carrier set used by the second RLC entity for data transmission and a carrier set used by the first RLC entity for data transmission of the first bearer includes: the carrier set used by the second RLC entity for data transmission is the same as the carrier set used by the first RLC entity of the first bearer for data transmission; or the carrier set used by the second RLC entity for data transmission includes the carrier set used by the first RLC entity for data transmission of the first bearer; or an intersection exists between the carrier set used by the second RLC entity for data transmission and the carrier set used by the first RLC entity for data transmission of the first bearer.
With reference to the first aspect, in a possible implementation manner of the first aspect, the second bearer is a radio bearer that transmits data in a data replication manner in a CA scenario.
With reference to the first aspect, in a possible implementation manner of the first aspect, the suspending, by the terminal device, data transmission on the second bearer at the same time includes: and the terminal equipment suspends the data transmission of the second bearer on the PDCP layer and the RLC layer.
With reference to the first aspect, in a possible implementation manner of the first aspect, the suspending, by the terminal device, data transmission on the second bearer at the same time includes: and the terminal equipment suspends the data transmission of the second bearer on the RLC layer.
With reference to the first aspect, in a possible implementation manner of the first aspect, the suspending, by the terminal device, data transmission of the second bearer on an RLC layer includes: the terminal equipment suspends data transmission on the second RLC entity of the RLC layer.
With reference to the first aspect, in a possible implementation manner of the first aspect, the suspending, by the terminal device, data transmission on the first bearer includes: and the terminal equipment suspends the data transmission on the first bearer and suspends the data transmission on a third bearer at the same time, wherein a third RLC entity of the third bearer performs the data transmission in a secondary cell.
With reference to the first aspect, in a possible implementation manner of the first aspect, the third bearer is a radio bearer that transmits data in a data replication manner in a CA scenario.
With reference to the first aspect, in a possible implementation manner of the first aspect, the suspending, by the terminal device, data transmission on a third bearer at the same time includes: and the terminal equipment suspends the data transmission of the third bearer on the PDCP layer and the RLC layer.
With reference to the first aspect, in a possible implementation manner of the first aspect, the suspending, by the terminal device, data transmission on a third bearer at the same time includes: and the terminal equipment suspends the data transmission of the third bearer on the RLC layer.
With reference to the first aspect, in a possible implementation manner of the first aspect, the suspending, by the terminal device, data transmission of the third bearer on an RLC layer includes: the terminal equipment suspends data transmission on the third RLC entity of the RLC layer.
With reference to the first aspect, in a possible implementation manner of the first aspect, the reporting, by the terminal device, an RLF message includes: and the terminal equipment sends the RLF message through a first SRB, wherein the first SRB is cut off from the MCG.
With reference to the first aspect, in a possible implementation manner of the first aspect, the sending, by the terminal device, the RLF message through the first SRB includes: and the terminal equipment sends the RLF message through an RLC entity of the MCG of the first SRB.
With reference to the first aspect, in a possible implementation manner of the first aspect, the sending, by the terminal device, the RLF message through the first SRB includes: and the terminal equipment sends the RLF message through an RLC entity of the SCG of the first SRB.
With reference to the first aspect, in a possible implementation manner of the first aspect, the sending, by the terminal device, the RLF message through the first SRB includes: and the terminal equipment sends the RLF message through the RLC entity of the MCG and the RLC entity of the SCG of the first SRB.
With reference to the first aspect, in a possible implementation manner of the first aspect, the sending, by the terminal device, the RLF message through an RLC entity of the MCG of the first SRB includes: and the terminal equipment sends the RLF message through a fourth RLC entity of the MCG of the first SRB, and the fourth RLC entity only uses a secondary cell to transmit data.
With reference to the first aspect, in a possible implementation manner of the first aspect, the sending, by the terminal device, the RLF message through an RLC entity of the MCG of the first SRB includes: and the terminal equipment sends the RLF message through a fifth RLC entity of the MCG of the first SRB, wherein the fifth RLC entity can use the main cell to transmit data.
With reference to the first aspect, in a possible implementation manner of the first aspect, the sending, by the terminal device, the RLF message through an RLC entity of the MCG of the first SRB includes: and the terminal equipment sends the RLF message through a fourth RLC entity and a fifth RLC entity of the MCG of the first SRB, wherein the fourth RLC entity only uses the auxiliary cell to transmit data, and the fifth RLC entity can use the main cell to transmit data.
With reference to the first aspect, in a possible implementation manner of the first aspect, the reporting, by the terminal device, an RLF message includes: and the terminal equipment sends the RLF message through a second SRB, wherein the second SRB is cut off from the SCG.
With reference to the first aspect, in a possible implementation manner of the first aspect, the sending, by the terminal device, the RLF message through the second SRB includes: and the terminal equipment sends the RLF message through a sixth RLC entity of the SCG of the second SRB, wherein the sixth RLC entity only uses the secondary cell to transmit data.
With reference to the first aspect, in a possible implementation manner of the first aspect, the sending, by the terminal device, the RLF message through the second SRB includes: and the terminal equipment sends the RLF message through a seventh RLC entity of the SCG of the second SRB, wherein the seventh RLC entity can use the main cell to transmit data.
With reference to the first aspect, in a possible implementation manner of the first aspect, the sending, by the terminal device, the RLF message through the second SRB includes: and the terminal equipment sends the RLF message through a sixth RLC entity and a seventh RLC entity of the SCG of the second SRB, wherein the sixth RLC entity only uses the auxiliary cell to transmit data, and the seventh RLC entity can use the main cell to transmit data.
In a second aspect, a method for controlling a data copy transmission function is provided, including: the method comprises the steps that a network device receives a Radio Link Failure (RLF) message reported by a terminal device, wherein the RLF message is used for indicating that data transmitted on a first bearer of the terminal device reaches the maximum retransmission times on a first Radio Link Control (RLC) entity, and the first bearer is a radio bearer for transmitting the data in a data copying mode under a Carrier Aggregation (CA) scene.
With reference to the second aspect, in a possible implementation manner of the second aspect, the first RLC entity is an RLC entity of a main network node MCG or an RLC entity of a secondary network node SCG.
With reference to the second aspect, in a possible implementation manner of the second aspect, the first RLC entity of the first bearer transmits data only in a secondary cell.
With reference to the second aspect, in a possible implementation manner of the second aspect, the first bearer is a signaling radio bearer SRB or a data radio bearer DRB.
With reference to the second aspect, in a possible implementation manner of the second aspect, the receiving, by the network device, an RLF message reported by a terminal device includes: and the network equipment receives the RLF message sent by the terminal equipment through a first SRB, wherein the first SRB is cut off from the MCG.
With reference to the second aspect, in a possible implementation manner of the second aspect, the receiving, by the network device, the RLF message sent by the terminal device through the first SRB includes: and the network equipment receives the RLF message sent by the terminal equipment through an RLC entity of the MCG of the first SRB.
With reference to the second aspect, in a possible implementation manner of the second aspect, the receiving, by the network device, the RLF message sent by the terminal device through the first SRB includes: and the network equipment receives the RLF message sent by the terminal equipment through an RLC entity of the SCG of the first SRB.
With reference to the second aspect, in a possible implementation manner of the second aspect, the receiving, by the network device, the RLF message sent by the terminal device through the first SRB includes: and the network equipment receives the RLF message sent by the terminal equipment through the RLC entity of the MCG and the RLC entity of the SCG of the first SRB.
With reference to the second aspect, in a possible implementation manner of the second aspect, the receiving, by the network device, the RLF message sent by the terminal device through an RLC entity of the MCG of the first SRB includes: and the network equipment receives the RLF message sent by the terminal equipment through a fourth RLC entity of the MCG of the first SRB, wherein the fourth RLC entity only transmits data in a secondary cell.
With reference to the second aspect, in a possible implementation manner of the second aspect, the receiving, by the network device, the RLF message sent by the terminal device through an RLC entity of the MCG of the first SRB includes: and the network equipment receives the RLF message sent by the terminal equipment through a fifth RLC entity of the MCG of the first SRB, wherein the fifth RLC entity can transmit data in a main cell.
With reference to the second aspect, in a possible implementation manner of the second aspect, the receiving, by the network device, the RLF message sent by the terminal device through an RLC entity of the MCG of the first SRB includes: and the network equipment receives the RLF message sent by the terminal equipment through a fourth RLC entity and a fifth RLC entity of the MCG of the first SRB, wherein the fourth RLC entity only transmits data in the auxiliary cell, and the fifth RLC entity can transmit data in the main cell.
With reference to the second aspect, in a possible implementation manner of the second aspect, the receiving, by the network device, an RLF message reported by a terminal device includes: and the network equipment receives the RLF message sent by the terminal equipment through a second SRB, wherein the second SRB is cut off from the SCG.
With reference to the second aspect, in a possible implementation manner of the second aspect, the receiving, by the network device, the RLF message sent by the terminal device through a second SRB includes: and the network equipment receives the RLF message sent by the terminal equipment through a sixth RLC entity of the SCG of the second SRB, wherein the sixth RLC entity only uses the secondary cell to transmit data.
With reference to the second aspect, in a possible implementation manner of the second aspect, the receiving, by the network device, the RLF message sent by the terminal device through a second SRB includes: and the network equipment receives the RLF message sent by the terminal equipment through a seventh RLC entity of the SCG of the second SRB, wherein the seventh RLC entity can use the main cell to transmit data.
With reference to the second aspect, in a possible implementation manner of the second aspect, the receiving, by the network device, the RLF message sent by the terminal device through a second SRB includes: and the network equipment receives the RLF message sent by the terminal equipment through a sixth RLC entity and a seventh RLC entity of the SCG of the second SRB, wherein the sixth RLC entity only uses the auxiliary cell to transmit data, and the seventh RLC entity can use the main cell to transmit data.
In a third aspect, a terminal device is provided, configured to perform the method in the first aspect or any possible implementation manner of the first aspect. In particular, the terminal device comprises functional modules for performing the method of the first aspect or any possible implementation manner of the first aspect.
In a fourth aspect, a terminal device is provided that includes a processor, a memory, and a transceiver. The processor, the memory and the transceiver communicate with each other via an internal connection path to transmit control and/or data signals, so that the network device performs the method of the first aspect or any possible implementation manner of the first aspect.
In a fifth aspect, a network device is provided for performing the method of the second aspect or any possible implementation manner of the second aspect. In particular, the control device comprises functional modules for performing the method of the second aspect described above or any possible implementation of the second aspect.
In a sixth aspect, a network device is provided that includes a processor, a memory, and a transceiver. The processor, the memory and the transceiver communicate with each other via the internal connection path to transmit control and/or data signals, so that the network device performs the method of the second aspect or any possible implementation manner of the second aspect.
In a seventh aspect, a computer-readable medium is provided for storing a computer program comprising instructions for performing any one of the above methods or any possible implementation.
Therefore, in the embodiment of the present application, when data transmission is performed in a data replication manner in a CA scenario, when an RLC entity of an MCG or an SCG reaches a maximum retransmission number, a terminal device suspends transmission of at least part of data on its radio bearer and reports an RLF message, thereby implementing control over a data replication transmission function of the terminal device.
Drawings
Fig. 1 is a schematic diagram of a protocol architecture for data replication according to an embodiment of the present application.
Fig. 2 is a schematic diagram of a protocol architecture for data replication according to an embodiment of the application.
Fig. 3 is a schematic flowchart of a method for controlling a data copy transmission function of a terminal device according to an embodiment of the present application.
Fig. 4 is a schematic block diagram of a terminal device according to an embodiment of the present application.
Fig. 5 is a schematic block diagram of a network device according to an embodiment of the present application.
FIG. 6 is a schematic block diagram of a system chip according to an embodiment of the present application.
Fig. 7 is a schematic block diagram of a communication device according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings.
It should be understood that the technical solutions of the embodiments of the present application may be applied to various communication systems, for example: a Global System for Mobile communications (GSM) System, a Code Division Multiple Access (CDMA) System, a Wideband Code Division Multiple Access (WCDMA) System, a Long Term Evolution (Long Term Evolution) System, an LTE (frequency Division Duplex) System, an LTE Time Division Duplex (FDD) System, a Time Division Duplex (TDD), a Universal Mobile Telecommunications System (UMTS), and a future 5G Communication System.
Various embodiments are described herein in connection with a terminal device. A terminal device may also refer to a User Equipment (UE), an access terminal, a subscriber unit, a subscriber station, a mobile station, a remote terminal, a mobile device, a user terminal, a wireless communication device, a user agent, or a user equipment. An access terminal may be a cellular telephone, a cordless telephone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device with wireless communication capability, a computing device or other processing device connected to a wireless modem, a vehicle mounted device, a wearable device, a terminal device in a future 5G network or a terminal device in a future evolved Public Land Mobile Network (PLMN) network, etc.
Various embodiments are described herein in connection with a network device. The network device may be a device for communicating with the terminal device, and for example, may be a Base Transceiver Station (BTS) in a GSM system or a CDMA system, a Base Station (NodeB, NB) in a WCDMA system, an evolved node B (eNB, or eNodeB) in an LTE system, or may be a relay Station, an access point, a vehicle-mounted device, a wearable device, and a network-side device in a future 5G network or a network-side device in a future evolved PLMN network.
In the 5G system, a plurality of network nodes (Cell groups (CGs)) may serve a terminal device, and data may be transmitted between the Cell groups and the terminal device by way of data replication.
It should be understood that, in the embodiment of the present application, the CG may be equivalent to a network node or a network device, etc.
Alternatively, the protocol architecture of the data replication transport may be as shown in fig. 1 and 2. The data replication transmission mode adopts a protocol architecture of a split bearer (split bearer); for uplink and downlink, a Packet Data Convergence Protocol (PDCP) is located at a CG (Master CG, MCG) or SCG (Secondary CG, SCG), which is an anchor CG (anchor CG). In any CG, the PDCP may copy a PDCP Protocol Data Unit (PDU) into two identical copies, for example, one is a PDCP PDU, and the other is a copied PDCP PDU, where the two PDCP layers pass through a Radio Link Control (RLC) layer and a Media Access Control (MAC) layer of different CGs, and arrive at corresponding MAC and RLC layers of a terminal (downlink) or a base station (uplink) through an air interface, and finally converge to the PDCP, and the PDCP layer monitors that the two PDCP layers are the same copied version, that is, one of the two PDCP layers is discarded, and the other PDCP layer is delivered to an upper layer.
When the number of data transmissions on the RLC entity reaches the maximum number of retransmissions, it is necessary to control the data copy transmission function between the control network node and the terminal device, so as to avoid an influence on the subsequent data transmission.
For this reason, the following solutions are provided in the embodiments of the present application to solve this problem, thereby implementing control of the data copy transmission function of the terminal device.
Fig. 3 is a flowchart of an interaction method 300 for controlling a data copy transmission function according to an embodiment of the application. The method 300 includes at least some of the following.
In 310, the terminal device suspends data transmission on the first bearer when the maximum number of retransmissions of data transmitted on the first bearer is reached on the first RLC entity.
The first bearer is a radio bearer for transmitting data in a data replication manner in a CA scenario.
In particular, for data transmitted on a first bearer, during the transmission, if the maximum number of retransmissions is reached on the first RLC entity, the terminal device may suspend transmission of at least part of the data on the first bearer.
Alternatively, the first RLC entity may be an RLC entity of the primary network node MCG or an RLC entity of the secondary network node SCG.
Optionally, the first RLC entity of the first bearer transmits data only in the secondary cell.
Optionally, the first Bearer is a Signaling Radio Bearer (SRB) or a Data Radio Bearer (DRB).
Optionally, in 310, the suspending, by the terminal device, data transmission on the first bearer includes: the terminal device suspends data transmission of the first bearer on the PDCP layer and the RLC layer.
Optionally, in 310, the suspending, by the terminal device, data transmission on the first bearer includes: the terminal equipment suspends the data transmission of the first bearer on the RLC layer.
Further, optionally, the suspending, by the terminal device, data transmission of the first bearer on the RLC layer includes: the terminal device suspends data transmission on the first RLC entity of the RLC layer.
In particular, the terminal device may suspend transmission of at least part of the data on the first bearer when the data transmission on the first RLC entity reaches the maximum number of retransmissions. For example, transmission of all data on the first bearer may be suspended; or suspending data transmission of the first bearer on the PDCP layer and the RLC layer; alternatively, only the data transmission of the first bearer on the RLC layer may be suspended; or only suspend the data transmission of the first bearer on the first RLC entity of the RLC layer.
Optionally, in 310, the suspending, by the terminal device, data transmission on the first bearer includes: the terminal device suspends data transmission on the first bearer while suspending data transmission on the second bearer. The carrier set used by the second RLC entity of the second bearer for data transmission at least partially overlaps with the carrier set used by the first RLC entity of the first bearer for data transmission.
That is, since there is an overlap between the set of carriers mapped by the second RLC entity of the second bearer and the set of carriers mapped by the first RLC entity of the first bearer, when suspending data transmission on the first bearer, data transmission on the second bearer may also be suspended at the same time.
Wherein, the carrier set used by the second RLC entity for data transmission at least partially overlaps with the carrier set used by the first RLC entity for data transmission of the first bearer, and includes: the carrier set used by the second RLC entity for data transmission is the same as the carrier set used by the first RLC entity for data transmission of the first bearer; or the carrier set used by the second RLC entity for data transmission includes the carrier set used by the first RLC entity for data transmission of the first bearer; or an intersection exists between the carrier set used by the second RLC entity for data transmission and the carrier set used by the first RLC entity for data transmission of the first bearer.
Optionally, the second bearer is a radio bearer for transmitting data in a data replication manner in a CA scenario.
Optionally, the suspending, by the terminal device, data transmission on the second bearer simultaneously includes: the terminal device suspends data transmission of the second bearer on the PDCP layer and the RLC layer.
Optionally, the suspending, by the terminal device, data transmission on the second bearer simultaneously includes: the terminal equipment suspends the data transmission of the second bearer on the RLC layer.
Further, optionally, the suspending, by the terminal device, data transmission of the second bearer on the RLC layer includes: the terminal device suspends data transmission on the second RLC entity of the RLC layer.
For the second bearer, the terminal device may suspend transmission of all data on the second bearer when the data of the first RLC entity reaches the maximum retransmission number; alternatively, data transmission of the second bearer on the PDCP layer and the RLC layer may be suspended; alternatively, only the data transmission of the second bearer on the RLC layer may be suspended; or only suspend data transmission of the second bearer on the second RLC entity of the RLC layer, e.g. only suspend the RLC entity of the second bearer whose carrier set overlaps with the carrier set corresponding to the first RLC entity.
Optionally, in 310, the suspending, by the terminal device, data transmission on the first bearer includes: the terminal device suspends data transmission on the first bearer while suspending data transmission on a third bearer. And the third RLC entity of the third bearer performs data transmission only in the secondary cell.
That is to say, since the third RLC entity of the third bearer performs data transmission only in the secondary cell, that is, the set of carriers mapped by the third RLC entity of the third bearer includes only the secondary carrier, when suspending data transmission on the first bearer, it is also possible to suspend data transmission on the third bearer at the same time.
Optionally, the third bearer is a radio bearer for transmitting data in a data replication manner in a CA scenario.
Optionally, the suspending, by the terminal device, data transmission on the third bearer simultaneously includes: the terminal device suspends data transmission of the third bearer on the PDCP layer and the RLC layer.
Optionally, the suspending, by the terminal device, data transmission on the third bearer simultaneously includes: the terminal device suspends data transmission of the third bearer on the RLC layer.
Further, optionally, the suspending, by the terminal device, data transmission of the third bearer on the RLC layer includes: the terminal device suspends data transmission on the third RLC entity of the RLC layer.
For the third bearer, the terminal device may suspend transmission of all data on the third bearer when the data on the first RLC entity reaches the maximum retransmission number; alternatively, data transmission of the third bearer on the PDCP layer and the RLC layer may be suspended; alternatively, only the data transmission of the third bearer on the RLC layer may be suspended; or only suspend the data transmission of the third bearer on the third RLC entity of the RLC layer, e.g. only suspend the one of the third bearers which transmits data only in the secondary cell.
Of course, the terminal device may also suspend data transmission on the first bearer, the second bearer, and the third bearer simultaneously.
At 320, the terminal device reports the RLF message.
Specifically, if the data transmitted on the first bearer reaches the maximum retransmission number on the first RLC entity, the terminal device suspends transmission of at least part of the data on the first bearer, and also reports a Radio Link Failure (RLF) message to the network device, so that the network device receives the RLF message reported by the terminal device, and may instruct the terminal device to control a data copy transmission function according to the received RLF message, for example, deactivate the data copy transmission function of the first bearer of the terminal device, or reconfigure the first bearer, and so on.
Wherein, the RLF message is used to indicate that the data transmitted on the first bearer of the terminal device reaches the maximum retransmission times on the first RLC entity.
In this embodiment, the terminal device may report the RLF message to the network device through the first SRB or the second SRB, which is described below respectively.
Mode 1
Optionally, in 320, the reporting, by the terminal device, the RLF message includes: the terminal device sends the RLF message via a first SRB, the first SRB being terminated by the MCG.
The first SRB may also be referred to as SRB1, and the SRB1 is cut off from the MCG and may be used for transmitting RRC signaling. The SRB1 may be transported and processed by the MCG, or may be transported to and processed by the MCG via the SCG for control signaling carried by the SRB 1.
Optionally, the sending, by the terminal device, the RLF message through the first SRB includes: the terminal device transmits the RLF message through the RLC entity of the MCG of the first SRB.
Optionally, the sending, by the terminal device, the RLF message through the first SRB includes: the terminal device transmits the RLF message through the RLC entity of the SCG of the first SRB.
Optionally, the sending, by the terminal device, the RLF message through the first SRB includes: the terminal equipment sends the RLF message through the RLC entities of the MCG and the SCG of the first SRB.
For example, if the RLF message is not reported by means of data replication, the RLF message may be carried in the SRB1 and reported through a path of MCG (MCG path). If the RLF message is reported in a data replication manner, the RLF message may be carried in the SRB1 and reported through a path of the MCG and a path of the SCG (SCG path), or reported through the SCG path.
And further, when the RLF message is reported through the MCG path, optionally, the terminal device sends the RLF message through a fourth RLC entity of the MCG of the first SRB; or the terminal equipment sends the RLF message through a fifth RLC entity of the first SRB; or the terminal equipment simultaneously sends the RLF message through the fourth RLC entity and the fifth RLC entity of the MCG of the first SRB. The fourth RLC entity transmits data only on the secondary cell, and the fifth RLC entity is capable of transmitting data on the primary carrier and the secondary carrier.
In other words, in the MCG path, the RLF message may be transmitted through the SRB1 of the fourth RLC entity, when the RLF message is transmitted only in the secondary cell (secondary carrier); or the RLF message may be transmitted through a fifth RLC entity, in which case the RLF message may be transmitted through a primary carrier (primary cell) or a secondary cell (secondary carrier); or the RLF message may also be transmitted simultaneously on the fourth RLC entity and the fifth RLC entity.
Mode 2
Optionally, in 320, the reporting, by the terminal device, the RLF message includes: the terminal device sends the RLF message via a second SRB, the second SRB being cut off from SCG.
The second SRB may also be referred to as SRB3, the SRB3 is cut off from SCG, the SRB3 is transmitted only on SCG path, and the terminal device processes the SRB3 after receiving it on SCG.
Optionally, the sending, by the terminal device, the RLF message through the second SRB includes: the terminal equipment sends the RLF message through a sixth RLC entity of the SCG of the second SRB, the sixth RLC entity transmitting data using only the secondary cell.
Optionally, the sending, by the terminal device, the RLF message through the second SRB includes: the terminal device sends the RLF message through a seventh RLC entity of the SCG of the second SRB, the seventh RLC entity being capable of transmitting data using the primary cell.
Optionally, the sending, by the terminal device, the RLF message through the second SRB includes: the terminal equipment sends the RLF message through a sixth RLC entity and a seventh RLC entity of the SCG of the second SRB, the sixth RLC entity transmits data only using the secondary cell, and the seventh RLC entity can transmit data using the primary cell.
In other words, in the SCG path, the RLF message may be transmitted through the SRB1 of the sixth RLC entity, when the RLF message is transmitted only in the secondary cell (secondary carrier); or the RLF message may be transmitted through a seventh RLC entity, in which case the RLF message may be transmitted through the primary carrier (primary cell) or the secondary cell (secondary carrier); or the RLF message may also be transmitted simultaneously on the sixth RLC entity and the seventh RLC entity.
In 330, the network device receives the RLF message reported by the terminal device.
Wherein, the RLF message is used to indicate that the data transmitted on the first bearer of the terminal device reaches the maximum retransmission times on the first RLC entity.
Similarly, in this embodiment of the present application, the network device may also receive, through the first SRB or the second SRB, the RLF message reported by the terminal device.
Optionally, in 330, the receiving, by the network device, the RLF message reported by the terminal device includes: the network device receives the RLF message sent by the terminal device through a first SRB, wherein the first SRB is cut off from the MCG.
Optionally, the receiving, by the network device, the RLF message sent by the terminal device through the first SRB includes: the network device receives the RLF message sent by the terminal device through the RLC entity of the MCG of the first SRB.
Optionally, the receiving, by the network device, the RLF message sent by the terminal device through the first SRB includes: the network device receives the RLF message sent by the terminal device through the RLC entity of the SCG of the first SRB.
Optionally, the receiving, by the network device, the RLF message sent by the terminal device through the first SRB includes: the network device receives the RLF message sent by the terminal device through the RLC entity of the MCG and the RLC entity of the SCG of the first SRB.
Further, optionally, the receiving, by the network device, the RLF message sent by the terminal device through the RLC entity of the MCG of the first SRB includes: and the network equipment receives the RLF message sent by the terminal equipment through a fourth RLC entity of the MCG of the first SRB, wherein the fourth RLC entity only transmits data in the secondary cell.
Optionally, the receiving, by the network device, the RLF message sent by the terminal device through the RLC entity of the MCG of the first SRB includes: and the network equipment receives the RLF message sent by the terminal equipment through a fifth RLC entity of the MCG of the first SRB, wherein the fifth RLC entity can transmit data in the main cell.
Optionally, the receiving, by the network device, the RLF message sent by the terminal device through the RLC entity of the MCG of the first SRB includes: the network device receives the RLF message sent by the terminal device through a fourth RLC entity and a fifth RLC entity of the MCG of the first SRB, wherein the fourth RLC entity transmits data only in the secondary cell, and the fifth RLC entity can transmit data in the primary cell.
Optionally, in 330, the receiving, by the network device, the RLF message reported by the terminal device includes: and the network equipment receives the RLF message sent by the terminal equipment through a second SRB, wherein the second SRB is cut off from the SCG.
Optionally, the receiving, by the network device, the RLF message sent by the terminal device through the second SRB includes: and the network equipment receives the RLF message sent by the terminal equipment through a sixth RLC entity of the SCG of the second SRB, wherein the sixth RLC entity only uses the secondary cell to transmit data.
Optionally, the receiving, by the network device, the RLF message sent by the terminal device through the second SRB includes: the network device receives the RLF message sent by the terminal device through a seventh RLC entity of the SCG of the second SRB, the seventh RLC entity being capable of transmitting data using the primary cell.
Optionally, the receiving, by the network device, the RLF message sent by the terminal device through the second SRB includes: the network device receives the RLF message sent by the terminal device through a sixth RLC entity and a seventh RLC entity of the SCG of the second SRB, the sixth RLC entity uses only the secondary cell to transmit data, and the seventh RLC entity can use the primary cell to transmit data.
The first SRB is, for example, SRB1, and the second SRB is, for example, SRB 3.
Therefore, when data transmission is performed in a data replication mode in a CA scenario, when the RLC entity of the MCG or SCG reaches the maximum retransmission number, the terminal device suspends transmission of at least part of data on its radio bearer and reports an RLF message, thereby implementing control over the data replication transmission function of the terminal device.
Fig. 4 is a schematic block diagram of a terminal device 400 according to an embodiment of the application. As shown in fig. 4, the terminal device 400 includes a processing unit 410 and a transmitting unit 420, wherein:
the processing unit 410 is configured to: when data transmitted on a first bearer reaches the maximum retransmission times on a first Radio Link Control (RLC) entity, suspending data transmission on the first bearer, wherein the first bearer is a radio bearer for transmitting data in a data copying manner in a CA scene;
the sending unit 420 is configured to: and reporting the RLF message.
Therefore, when data transmission is performed in a data replication mode in a CA scenario, when the RLC entity of the MCG or SCG reaches the maximum retransmission number, the terminal device suspends transmission of at least part of data on its radio bearer and reports an RLF message, thereby implementing control over the data replication transmission function of the terminal device.
The first RLC entity is an RLC entity of a main network node MCG or an RLC entity of a secondary network node SCG.
Optionally, the first RLC entity of the first bearer transmits data only in a secondary cell.
Optionally, the first bearer is a signaling radio bearer SRB or a data radio bearer DRB.
Optionally, the processing unit 410 is specifically configured to: suspending data transmission of the first bearer on the PDCP layer and the RLC layer.
Optionally, the processing unit 410 is specifically configured to: suspending data transmission of the first bearer on the RLC layer.
Optionally, the processing unit 410 is specifically configured to: suspending data transmission on the first RLC entity of the RLC layer.
Optionally, the processing unit 410 is specifically configured to: and suspending data transmission on the first bearer and simultaneously suspending data transmission on a second bearer, wherein a carrier set used for data transmission by a second RLC entity of the second bearer at least partially overlaps with a carrier set used for data transmission by the first RLC entity of the first bearer.
Optionally, at least a part of a carrier set used for data transmission by the second RLC entity of the second bearer overlaps with a carrier set used for data transmission by the first RLC entity of the first bearer, including: the carrier set used by the second RLC entity for data transmission is the same as the carrier set used by the first RLC entity of the first bearer for data transmission; or the carrier set used by the second RLC entity for data transmission includes the carrier set used by the first RLC entity for data transmission of the first bearer; or an intersection exists between the carrier set used by the second RLC entity for data transmission and the carrier set used by the first RLC entity for data transmission of the first bearer.
Optionally, the second bearer is a radio bearer for transmitting data in a data replication manner in a CA scenario.
Optionally, the processing unit 410 is specifically configured to: suspending data transmission of the second bearer on the PDCP layer and the RLC layer.
Optionally, the processing unit 410 is specifically configured to: suspending data transmission of the second bearer on the RLC layer.
Optionally, the processing unit 410 is specifically configured to: suspending data transmission on the second RLC entity of the RLC layer.
Optionally, the processing unit 410 is specifically configured to: and suspending data transmission on the first bearer and simultaneously suspending data transmission on a third bearer, wherein a third RLC entity of the third bearer performs data transmission only in a secondary cell.
Optionally, the third bearer is a radio bearer for transmitting data in a data replication manner in a CA scenario.
Optionally, the processing unit 410 is specifically configured to: suspending data transmission of the third bearer on the PDCP layer and the RLC layer.
Optionally, the processing unit 410 is specifically configured to: suspending data transmission of the third bearer on the RLC layer.
Optionally, the processing unit 410 is specifically configured to: suspending data transmission on the third RLC entity of the RLC layer.
Optionally, the sending unit 420 is specifically configured to: sending the RLF message through a first SRB, the first SRB being cut off from the MCG.
Optionally, the sending unit 420 is specifically configured to: transmitting the RLF message through an RLC entity of the MCG of the first SRB.
Optionally, the sending unit 420 is specifically configured to: transmitting the RLF message through an RLC entity of the SCG of the first SRB.
Optionally, the sending unit 420 is specifically configured to: and sending the RLF message through the RLC entity of the MCG and the RLC entity of the SCG of the first SRB.
Optionally, the sending unit 420 is specifically configured to: sending the RLF message through a fourth RLC entity of the MCG of the first SRB, the fourth RLC entity transmitting data using only the secondary cell.
Optionally, the sending unit 420 is specifically configured to: and sending the RLF message through a fifth RLC entity of the MCG of the first SRB, wherein the fifth RLC entity can use the primary cell to transmit data.
Optionally, the sending unit 420 is specifically configured to: and sending the RLF message through a fourth RLC entity and a fifth RLC entity of the MCG of the first SRB, wherein the fourth RLC entity only uses the secondary cell to transmit data, and the fifth RLC entity can use the primary cell to transmit data.
Optionally, the sending unit 420 is specifically configured to: sending the RLF message over a second SRB, the second SRB being cut off from the SCG.
Optionally, the sending unit 420 is specifically configured to: transmitting the RLF message through a sixth RLC entity of the SCG of the second SRB, the sixth RLC entity transmitting data using only the secondary cell.
Optionally, the sending unit 420 is specifically configured to: transmitting the RLF message through a seventh RLC entity of the SCG of the second SRB, the seventh RLC entity being capable of transmitting data using the primary cell.
Optionally, the sending unit 420 is specifically configured to: and sending the RLF message through a sixth RLC entity and a seventh RLC entity of the SCG of the second SRB, wherein the sixth RLC entity only uses the secondary cell to transmit data, and the seventh RLC entity can use the primary cell to transmit data.
It should be understood that the terminal device 400 may correspond to the terminal device in the method 300, and operations implemented by the terminal device in the method 300 may be implemented, which are not described herein again for brevity.
Fig. 5 is a schematic block diagram of a network device 500 according to an embodiment of the present application. As shown in fig. 5, the terminal device 500 includes a receiving unit 510 for:
receiving an RLF message reported by a terminal device, where the RLF message is used to indicate that data transmitted on a first bearer of the terminal device reaches a maximum retransmission time on a first Radio Link Control (RLC) entity, and the first bearer is a radio bearer for transmitting data in a data replication manner in a Carrier Aggregation (CA) scenario.
Therefore, when data transmission is performed in a data replication mode in a CA scenario, when the RLC entity of the MCG or SCG reaches the maximum retransmission number, the network device receives the RLF message reported by the terminal device, thereby implementing control of the data replication transmission function of the terminal device, and when a transmission link has a problem, the influence on subsequent data transmission can be avoided.
Optionally, the first RLC entity is an RLC entity of a main network node MCG or an RLC entity of a secondary network node SCG.
Optionally, the first RLC entity of the first bearer transmits data only in a secondary cell.
Optionally, the first bearer is a signaling radio bearer SRB or a data radio bearer DRB.
Optionally, the receiving unit 510 is specifically configured to: and receiving the RLF message sent by the terminal equipment through a first SRB, wherein the first SRB is cut off from the MCG.
Optionally, the receiving unit 510 is specifically configured to: and the network equipment receives the RLF message sent by the terminal equipment through an RLC entity of the MCG of the first SRB.
Optionally, the receiving unit 510 is specifically configured to: and receiving the RLF message sent by the terminal equipment through an RLC entity of the SCG of the first SRB.
Optionally, the receiving unit 510 is specifically configured to: and receiving the RLF message sent by the terminal equipment through the RLC entity of the MCG and the RLC entity of the SCG of the first SRB.
Optionally, the receiving unit 510 is specifically configured to: and receiving the RLF message sent by the terminal equipment through a fourth RLC entity of the MCG of the first SRB, wherein the fourth RLC entity only uses a secondary cell to transmit data.
Optionally, the receiving unit 510 is specifically configured to: and receiving the RLF message sent by the terminal equipment through a fifth RLC entity of the MCG of the first SRB, wherein the fifth RLC entity can use a main cell to transmit data.
Optionally, the receiving unit 510 is specifically configured to: and receiving the RLF message sent by the terminal equipment through a fourth RLC entity and a fifth RLC entity of the MCG of the first SRB, wherein the fourth RLC entity only uses the auxiliary cell to transmit data, and the fifth RLC entity can use the main cell to transmit data.
Optionally, the receiving unit 510 is specifically configured to: and receiving the RLF message sent by the terminal equipment through a second SRB, wherein the second SRB is cut off from SCG.
Optionally, the receiving unit 510 is specifically configured to: and receiving the RLF message sent by the terminal equipment through a sixth RLC entity of the SCG of the second SRB, wherein the sixth RLC entity only uses the secondary cell to transmit data.
Optionally, the receiving unit 510 is specifically configured to: and receiving the RLF message sent by the terminal equipment through a seventh RLC entity of the SCG of the second SRB, wherein the seventh RLC entity can use the main cell to transmit data.
Optionally, the receiving unit 510 is specifically configured to: and receiving the RLF message sent by the terminal equipment through a sixth RLC entity and a seventh RLC entity of the SCG of the second SRB, wherein the sixth RLC entity only uses the auxiliary cell to transmit data, and the seventh RLC entity can use the main cell to transmit data.
It should be understood that the network device 500 may correspond to the network device in the method 300, and operations implemented by the network device in the method 500 may be implemented, which are not described herein again for brevity.
Fig. 6 is a schematic structural diagram of a system chip 600 according to an embodiment of the present application. The system chip 600 of fig. 6 includes an input interface 601, an output interface 602, the processor 603, and a memory 604, which are connected via an internal communication link, wherein the processor 603 is configured to execute codes in the memory 604.
Optionally, when the code is executed, the processor 603 implements corresponding operations in the method 300, which are performed by the terminal device or the network device. For brevity, no further description is provided herein.
Fig. 7 is a schematic block diagram of a communication device 700 according to an embodiment of the present application. As shown in fig. 7, the communication device 700 includes a processor 710 and a memory 730. The memory 730 can store program codes, and the processor 710 can execute the program codes stored in the memory 730.
Alternatively, as shown in fig. 7, the communication device 700 may include a transceiver 720, and the processor 710 may control the transceiver 720 to communicate externally.
Optionally, the processor 710 may call the program code stored in the memory 730 to perform corresponding operations performed by the terminal device or the network device in the method 300, which are not described herein again for brevity.
It should be understood that the processor of the embodiments of the present application may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method embodiments may be performed by integrated logic circuits of hardware in a processor or instructions in the form of software. The processor may be a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic device, discrete hardware component. The various methods, steps, and logic blocks disclosed in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in a memory, and a processor reads information in the memory and completes the steps of the method in combination with hardware of the processor.
It will be appreciated that the memory in the embodiments of the subject application can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory. The non-volatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable PROM (EEPROM), or a flash Memory. Volatile Memory can be Random Access Memory (RAM), which acts as external cache Memory. By way of example, but not limitation, many forms of RAM are available, such as Static random access memory (Static RAM, SRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic random access memory (Synchronous DRAM, SDRAM), Double Data rate Synchronous Dynamic random access memory (DDR SDRAM), Enhanced Synchronous SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), and direct memory bus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the 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 functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application.
The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims (86)

1. A control method for terminal equipment data copy transmission function is characterized by comprising the following steps:
when data transmitted on a first bearer reaches the maximum retransmission times on a first Radio Link Control (RLC) entity, the terminal equipment suspends the data transmission on the first bearer, wherein the first bearer is a radio bearer for transmitting data in a data copying manner under a Carrier Aggregation (CA) scene;
the terminal equipment reports a Radio Link Failure (RLF) message;
wherein the suspending, by the terminal device, data transmission on the first bearer includes:
and the terminal equipment suspends the data transmission on the first bearer and suspends the data transmission on a second bearer at the same time, wherein at least part of carrier sets used by a second RLC entity of the second bearer for data transmission are overlapped with carrier sets used by a first RLC entity of the first bearer for data transmission.
2. The method of claim 1, wherein the first RLC entity is an RLC entity of a primary network node, MCG, or an RLC entity of a secondary network node, SCG.
3. The method of claim 1, wherein the first RLC entity of the first bearer transmits data only in a secondary cell.
4. The method of claim 1, wherein the first bearer is a Signaling Radio Bearer (SRB) or a Data Radio Bearer (DRB).
5. The method of claim 1, wherein suspending, by the terminal device, data transmission on the first bearer comprises:
and the terminal equipment suspends the data transmission of the first bearer on the PDCP layer and the RLC layer.
6. The method of claim 1, wherein suspending, by the terminal device, data transmission on the first bearer comprises:
and the terminal equipment suspends the data transmission of the first bearer on the RLC layer.
7. The method of claim 6, wherein suspending, by the terminal device, data transmission of the first bearer on the RLC layer comprises:
the terminal equipment suspends data transmission on the first RLC entity of the RLC layer.
8. The method of claim 1, wherein at least a partial overlap between a set of carriers used for data transmission by the second RLC entity and a set of carriers used for data transmission by the first RLC entity of the first bearer comprises:
the carrier set used by the second RLC entity for data transmission is the same as the carrier set used by the first RLC entity of the first bearer for data transmission; or
The carrier set used by the second RLC entity for data transmission includes the carrier set used by the first RLC entity for data transmission of the first bearer; or
And a carrier set used by the second RLC entity for data transmission and a carrier set used by the first RLC entity for data transmission of the first bearer have an intersection.
9. The method of claim 1, wherein the second bearer is a radio bearer for transmitting data by means of data replication in a CA scenario.
10. The method according to any of claims 1 to 9, wherein the terminal device simultaneously suspending data transmission on the second bearer comprises:
and the terminal equipment suspends the data transmission of the second bearer on the PDCP layer and the RLC layer.
11. The method according to any of claims 1 to 9, wherein the terminal device simultaneously suspending data transmission on the second bearer comprises:
and the terminal equipment suspends the data transmission of the second bearer on the RLC layer.
12. The method of claim 11, wherein suspending, by the terminal device, data transmission on the RLC layer by the second bearer comprises:
the terminal equipment suspends data transmission on the second RLC entity of the RLC layer.
13. The method according to any one of claims 1 to 7, wherein the suspension of data transmission on the first bearer by the terminal device comprises:
and the terminal equipment suspends the data transmission on the first bearer and suspends the data transmission on a third bearer at the same time, wherein a third RLC entity of the third bearer only carries out data transmission in a secondary cell.
14. The method of claim 13, wherein the third bearer is a radio bearer for transmitting data by means of data replication in a CA scenario.
15. The method of claim 14, wherein the terminal device concurrently suspending data transmission on a third bearer comprises:
and the terminal equipment suspends the data transmission of the third bearer on the PDCP layer and the RLC layer.
16. The method of claim 14, wherein the terminal device concurrently suspending data transmission on a third bearer comprises:
and the terminal equipment suspends the data transmission of the third bearer on the RLC layer.
17. The method of claim 16, wherein suspending, by the terminal device, data transmission on the RLC layer by the third bearer comprises:
the terminal equipment suspends data transmission on the third RLC entity of the RLC layer.
18. The method of claim 1, wherein the reporting the RLF message by the terminal device comprises:
and the terminal equipment sends the RLF message through a first SRB, wherein the first SRB is cut off from the MCG.
19. The method of claim 18, wherein the terminal device sends the RLF message via a first SRB, comprising:
and the terminal equipment sends the RLF message through an RLC entity of the MCG of the first SRB.
20. The method of claim 18, wherein the terminal device sends the RLF message via a first SRB, comprising:
and the terminal equipment sends the RLF message through an RLC entity of the SCG of the first SRB.
21. The method of claim 18, wherein the terminal device sends the RLF message via a first SRB, comprising:
and the terminal equipment sends the RLF message through the RLC entity of the MCG and the RLC entity of the SCG of the first SRB.
22. The method according to claim 19 or 21, wherein the terminal device sends the RLF message via an RLC entity of the MCG of the first SRB, comprising:
and the terminal equipment sends the RLF message through a fourth RLC entity of the MCG of the first SRB, and the fourth RLC entity only uses a secondary cell to transmit data.
23. The method according to claim 19 or 21, wherein the terminal device sends the RLF message via an RLC entity of the MCG of the first SRB, comprising:
and the terminal equipment sends the RLF message through a fifth RLC entity of the MCG of the first SRB, wherein the fifth RLC entity can use the main cell to transmit data.
24. The method according to claim 19 or 21, wherein the terminal device sends the RLF message via an RLC entity of the MCG of the first SRB, comprising:
and the terminal equipment sends the RLF message through a fourth RLC entity and a fifth RLC entity of the MCG of the first SRB, wherein the fourth RLC entity only uses the auxiliary cell to transmit data, and the fifth RLC entity can use the main cell to transmit data.
25. The method of claim 1, wherein the reporting the RLF message by the terminal device comprises:
and the terminal equipment sends the RLF message through a second SRB, wherein the second SRB is cut off from the SCG.
26. The method of claim 25, wherein the terminal device sends the RLF message via a second SRB, comprising:
and the terminal equipment sends the RLF message through a sixth RLC entity of the SCG of the second SRB, wherein the sixth RLC entity only uses the secondary cell to transmit data.
27. The method of claim 25, wherein the terminal device sends the RLF message via a second SRB, comprising:
and the terminal equipment sends the RLF message through a seventh RLC entity of the SCG of the second SRB, wherein the seventh RLC entity can use the main cell to transmit data.
28. The method of claim 25, wherein the terminal device sends the RLF message via a second SRB, comprising:
and the terminal equipment sends the RLF message through a sixth RLC entity and a seventh RLC entity of the SCG of the second SRB, wherein the sixth RLC entity only uses the auxiliary cell to transmit data, and the seventh RLC entity can use the main cell to transmit data.
29. A control method for terminal equipment data copy transmission function is characterized by comprising the following steps:
the method comprises the steps that a network device receives a Radio Link Failure (RLF) message reported by a terminal device, wherein the RLF message is used for indicating that data transmitted on a first bearer of the terminal device reaches the maximum retransmission times on a first Radio Link Control (RLC) entity, and the terminal device suspends the data transmission on the first bearer and the data transmission on a second bearer, wherein the first bearer is a radio bearer for transmitting data in a data copying mode under a Carrier Aggregation (CA) scene, and a carrier set used by the second RLC entity of the second bearer for data transmission is at least partially overlapped with a carrier set used by the first RLC entity of the first bearer for data transmission.
30. The method of claim 29, wherein the first RLC entity is an RLC entity of a primary network node, MCG, or an RLC entity of a secondary network node, SCG.
31. The method of claim 29 or 30, wherein the first RLC entity of the first bearer transmits data only in a secondary cell.
32. The method of claim 29, wherein the first bearer is a Signaling Radio Bearer (SRB) or a Data Radio Bearer (DRB).
33. The method of claim 29, wherein the receiving, by the network device, the RLF message reported by the terminal device comprises:
and the network equipment receives the RLF message sent by the terminal equipment through a first SRB, wherein the first SRB is cut off from the MCG.
34. The method of claim 33, wherein the network device receives the RLF message sent by the terminal device through a first SRB, comprising:
and the network equipment receives the RLF message sent by the terminal equipment through an RLC entity of the MCG of the first SRB.
35. The method of claim 33, wherein the network device receives the RLF message sent by the terminal device through a first SRB, comprising:
and the network equipment receives the RLF message sent by the terminal equipment through an RLC entity of the SCG of the first SRB.
36. The method of claim 35, wherein the network device receives the RLF message sent by the terminal device through a first SRB, comprising:
and the network equipment receives the RLF message sent by the terminal equipment through the RLC entity of the MCG and the RLC entity of the SCG of the first SRB.
37. The method according to claim 34 or 36, wherein the network device receives the RLF message sent by the terminal device through an RLC entity of the MCG of the first SRB, and comprises:
and the network equipment receives the RLF message sent by the terminal equipment through a fourth RLC entity of the MCG of the first SRB, wherein the fourth RLC entity only transmits data in a secondary cell.
38. The method according to claim 34 or 36, wherein the network device receives the RLF message sent by the terminal device through an RLC entity of the MCG of the first SRB, and comprises:
and the network equipment receives the RLF message sent by the terminal equipment through a fifth RLC entity of the MCG of the first SRB, wherein the fifth RLC entity can transmit data in a main cell.
39. The method according to claim 34 or 36, wherein the network device receives the RLF message sent by the terminal device through an RLC entity of the MCG of the first SRB, and comprises:
and the network equipment receives the RLF message sent by the terminal equipment through a fourth RLC entity and a fifth RLC entity of the MCG of the first SRB, wherein the fourth RLC entity only transmits data in the auxiliary cell, and the fifth RLC entity can transmit data in the main cell.
40. The method of claim 29, wherein the receiving, by the network device, the RLF message reported by the terminal device comprises:
and the network equipment receives the RLF message sent by the terminal equipment through a second SRB, wherein the second SRB is cut off from the SCG.
41. The method of claim 40, wherein the network device receives the RLF message sent by the terminal device through a second SRB, and comprises:
and the network equipment receives the RLF message sent by the terminal equipment through a sixth RLC entity of the SCG of the second SRB, wherein the sixth RLC entity only uses the secondary cell to transmit data.
42. The method of claim 40, wherein the network device receives the RLF message sent by the terminal device through a second SRB, and comprises:
and the network equipment receives the RLF message sent by the terminal equipment through a seventh RLC entity of the SCG of the second SRB, wherein the seventh RLC entity can use the main cell to transmit data.
43. The method of claim 40, wherein the network device receives the RLF message sent by the terminal device through a second SRB, and comprises:
and the network equipment receives the RLF message sent by the terminal equipment through a sixth RLC entity and a seventh RLC entity of the SCG of the second SRB, wherein the sixth RLC entity only uses the auxiliary cell to transmit data, and the seventh RLC entity can use the main cell to transmit data.
44. A terminal device, comprising:
a processing unit, configured to suspend data transmission on a first bearer when data transmitted on the first bearer reaches a maximum retransmission time on a first radio link control, RLC, entity, where the first bearer is a radio bearer that transmits data in a data replication manner in a CA scenario;
a sending unit, configured to report a radio link failure RLF message;
wherein the processing unit is specifically configured to: and suspending data transmission on the first bearer and simultaneously suspending data transmission on a second bearer, wherein a carrier set used for data transmission by a second RLC entity of the second bearer at least partially overlaps with a carrier set used for data transmission by a first RLC entity of the first bearer.
45. A terminal device according to claim 44, wherein the first RLC entity is the RLC entity of a primary network node, MCG, or the RLC entity of a secondary network node, SCG.
46. A terminal device according to claim 44 or 45, wherein the first RLC entity of the first bearer transmits data only in the secondary cell.
47. The terminal device according to claim 44, wherein the first bearer is a Signaling Radio Bearer (SRB) or a Data Radio Bearer (DRB).
48. The terminal device of claim 44, wherein the processing unit is specifically configured to:
suspending data transmission of the first bearer on the PDCP layer and the RLC layer.
49. The terminal device of claim 44, wherein the processing unit is specifically configured to:
suspending data transmission of the first bearer on the RLC layer.
50. The terminal device of claim 49, wherein the processing unit is specifically configured to:
suspending data transmission on the first RLC entity of the RLC layer.
51. The terminal device of claim 44, wherein a set of carriers used for data transmission by the second RLC entity of the second bearer at least partially overlaps with a set of carriers used for data transmission by the first RLC entity of the first bearer, and wherein the set of carriers comprises:
the carrier set used by the second RLC entity for data transmission is the same as the carrier set used by the first RLC entity of the first bearer for data transmission; or
The carrier set used by the second RLC entity for data transmission includes the carrier set used by the first RLC entity for data transmission of the first bearer; or
And a carrier set used by the second RLC entity for data transmission and a carrier set used by the first RLC entity for data transmission of the first bearer have an intersection.
52. The terminal device according to claim 44, wherein the second bearer is a radio bearer for transmitting data by means of data replication in a CA scenario.
53. The terminal device of claim 44, wherein the processing unit is specifically configured to:
suspending data transmission of the second bearer on the PDCP layer and the RLC layer.
54. The terminal device of claim 44, wherein the processing unit is specifically configured to:
suspending data transmission of the second bearer on the RLC layer.
55. The terminal device of claim 54, wherein the processing unit is specifically configured to:
suspending data transmission on the second RLC entity of the RLC layer.
56. The terminal device of claim 44, wherein the processing unit is specifically configured to:
and suspending data transmission on the first bearer and simultaneously suspending data transmission on a third bearer, wherein a third RLC entity of the third bearer performs data transmission in a secondary cell.
57. The terminal device according to claim 56, wherein the third bearer is a radio bearer for transmitting data by means of data replication in a CA scenario.
58. The terminal device of claim 56, wherein the processing unit is specifically configured to:
suspending data transmission of the third bearer on the PDCP layer and the RLC layer.
59. The terminal device of claim 56, wherein the processing unit is specifically configured to:
suspending data transmission of the third bearer on the RLC layer.
60. The terminal device according to claim 59, wherein the processing unit is specifically configured to:
suspending data transmission on the third RLC entity of the RLC layer.
61. The terminal device of claim 44, wherein the sending unit is specifically configured to:
sending the RLF message over a first SRB, the first SRB being cut off from the MCG.
62. The terminal device of claim 61, wherein the sending unit is specifically configured to:
transmitting the RLF message through an RLC entity of the MCG of the first SRB.
63. The terminal device of claim 61, wherein the sending unit is specifically configured to:
transmitting the RLF message through an RLC entity of the SCG of the first SRB.
64. The terminal device of claim 61, wherein the sending unit is specifically configured to:
and sending the RLF message through the RLC entity of the MCG and the RLC entity of the SCG of the first SRB.
65. The terminal device according to claim 62 or 64, wherein the sending unit is specifically configured to:
sending the RLF message through a fourth RLC entity of the MCG of the first SRB, the fourth RLC entity transmitting data using only the secondary cell.
66. The terminal device according to claim 62 or 64, wherein the sending unit is specifically configured to:
and sending the RLF message through a fifth RLC entity of the MCG of the first SRB, wherein the fifth RLC entity can use the primary cell to transmit data.
67. The terminal device according to claim 62 or 64, wherein the sending unit is specifically configured to:
and sending the RLF message through a fourth RLC entity and a fifth RLC entity of the MCG of the first SRB, wherein the fourth RLC entity only uses the secondary cell to transmit data, and the fifth RLC entity can use the primary cell to transmit data.
68. The terminal device of claim 44, wherein the sending unit is specifically configured to:
sending the RLF message over a second SRB, the second SRB being cut off from the SCG.
69. The terminal device of claim 68, wherein the sending unit is specifically configured to:
transmitting the RLF message through a sixth RLC entity of the SCG of the second SRB, the sixth RLC entity transmitting data using only the secondary cell.
70. The terminal device of claim 68, wherein the sending unit is specifically configured to:
transmitting the RLF message through a seventh RLC entity of the SCG of the second SRB, the seventh RLC entity being capable of transmitting data using the primary cell.
71. The terminal device of claim 68, wherein the sending unit is specifically configured to:
and sending the RLF message through a sixth RLC entity and a seventh RLC entity of the SCG of the second SRB, wherein the sixth RLC entity only uses the secondary cell to transmit data, and the seventh RLC entity can use the primary cell to transmit data.
72. A network device, comprising:
a receiving unit, configured to receive an RLF message for radio link failure reported by a terminal device, where the RLF message is used to indicate that data transmitted on a first bearer of the terminal device reaches a maximum retransmission time on a first radio link control RLC entity, and the terminal device suspends data transmission on the first bearer and data transmission on a second bearer, where the first bearer is a radio bearer that transmits data in a data replication manner in a carrier aggregation CA scenario, and a carrier set used by the second RLC entity of the second bearer for data transmission at least partially overlaps with a carrier set used by the first RLC entity of the first bearer for data transmission.
73. The network device of claim 72, wherein the first RLC entity is an RLC entity of a primary network node (MCG) or an RLC entity of a secondary network node (SCG).
74. The network device of claim 72 or 73, wherein the first RLC entity of the first bearer transmits data only in a secondary cell.
75. The network device of claim 72, wherein the first bearer is a Signaling Radio Bearer (SRB) or a Data Radio Bearer (DRB).
76. The network device of claim 72, wherein the receiving unit is specifically configured to:
and receiving the RLF message sent by the terminal equipment through a first SRB, wherein the first SRB is cut off from the MCG.
77. The network device of claim 76, wherein the receiving unit is specifically configured to:
and the network equipment receives the RLF message sent by the terminal equipment through an RLC entity of the MCG of the first SRB.
78. The network device of claim 76, wherein the receiving unit is specifically configured to:
and receiving the RLF message sent by the terminal equipment through an RLC entity of the SCG of the first SRB.
79. The network device of claim 76, wherein the receiving unit is specifically configured to:
and receiving the RLF message sent by the terminal equipment through the RLC entity of the MCG and the RLC entity of the SCG of the first SRB.
80. The network device of claim 77 or 79, wherein the receiving unit is specifically configured to:
and receiving the RLF message sent by the terminal equipment through a fourth RLC entity of the MCG of the first SRB, wherein the fourth RLC entity only transmits data in the main cell.
81. The network device of claim 77 or 79, wherein the receiving unit is specifically configured to:
and receiving the RLF message sent by the terminal equipment through a fifth RLC entity of the MCG of the first SRB, wherein the fifth RLC entity can transmit data in a main cell.
82. The network device of claim 77 or 79, wherein the receiving unit is specifically configured to:
and receiving the RLF message sent by the terminal equipment through a fourth RLC entity and a fifth RLC entity of the MCG of the first SRB, wherein the fourth RLC entity only transmits data in the secondary cell, and the fifth RLC entity can transmit data in the primary cell.
83. The network device of claim 72, wherein the receiving unit is specifically configured to:
and receiving the RLF message sent by the terminal equipment through a second SRB, wherein the second SRB is cut off from SCG.
84. The network device of claim 83, wherein the receiving unit is specifically configured to:
and receiving the RLF message sent by the terminal equipment through a sixth RLC entity of the SCG of the second SRB, wherein the sixth RLC entity only uses a secondary cell to transmit data.
85. The network device of claim 83, wherein the receiving unit is specifically configured to:
and receiving the RLF message sent by the terminal equipment through a seventh RLC entity of the SCG of the second SRB, wherein the seventh RLC entity can use the main cell to transmit data.
86. The network device of claim 83, wherein the receiving unit is specifically configured to:
and receiving the RLF message sent by the terminal equipment through a sixth RLC entity and a seventh RLC entity of the SCG of the second SRB, wherein the sixth RLC entity only uses the auxiliary cell to transmit data, and the seventh RLC entity can use the main cell to transmit data.
CN201780050539.XA 2017-12-28 2017-12-28 Method and device for controlling data copying and transmitting function Active CN109661831B (en)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2017/119606 WO2019127292A1 (en) 2017-12-28 2017-12-28 Method and apparatus for controlling data replication transmission function

Publications (2)

Publication Number Publication Date
CN109661831A CN109661831A (en) 2019-04-19
CN109661831B true CN109661831B (en) 2020-04-21

Family

ID=66110637

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201780050539.XA Active CN109661831B (en) 2017-12-28 2017-12-28 Method and device for controlling data copying and transmitting function

Country Status (2)

Country Link
CN (1) CN109661831B (en)
WO (1) WO2019127292A1 (en)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110475285B (en) * 2018-05-10 2021-03-16 维沃移动通信有限公司 Operation method and terminal
CN112153689B (en) * 2019-06-29 2022-09-02 华为技术有限公司 Data sending method and device
WO2021012123A1 (en) * 2019-07-19 2021-01-28 Oppo广东移动通信有限公司 Processing method, device and apparatus for data duplication and transmission, and storage medium

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104604318A (en) * 2012-08-23 2015-05-06 交互数字专利控股公司 Providing physical layer resources to different serving sites
EP3065483A1 (en) * 2013-10-31 2016-09-07 Ntt Docomo, Inc. Mobile communication method, mobile station, and wireless base station
WO2017182927A1 (en) * 2016-04-19 2017-10-26 Nokia Technologies Oy Split bearer dual/multiple connectivity retransmission diversity

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR102309346B1 (en) * 2010-02-12 2021-10-08 인터디지탈 패튼 홀딩스, 인크 Method and apparatus for enhancing cell-edge user performance and signaling radio link failure conditions via downlink cooperative component carriers
CN102655682B (en) * 2011-03-03 2016-12-07 华为技术有限公司 A kind of method, system and device using carrier aggregation mode transmission data
CN103581942B (en) * 2012-07-31 2017-08-11 电信科学技术研究院 A kind of processing method of Radio Link Failure, apparatus and system
CN105122863A (en) * 2013-01-18 2015-12-02 联发科技股份有限公司 Mechanism for radio link monitoring (RLM) and radio link failure (RLF) handling in small cell networks
WO2015023067A1 (en) * 2013-08-12 2015-02-19 삼성전자 주식회사 Method for processing radio link failure in multiple base station connectivity based radio communication system, and apparatus for same
JP2017208582A (en) * 2014-09-26 2017-11-24 シャープ株式会社 Terminal device, base station device, and communication method
WO2016127666A1 (en) * 2015-02-09 2016-08-18 华为技术有限公司 Rlc data packet offloading method, and base station
CN107040351A (en) * 2016-02-03 2017-08-11 中兴通讯股份有限公司 A kind of method and device for realizing carrier aggregation

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104604318A (en) * 2012-08-23 2015-05-06 交互数字专利控股公司 Providing physical layer resources to different serving sites
EP3065483A1 (en) * 2013-10-31 2016-09-07 Ntt Docomo, Inc. Mobile communication method, mobile station, and wireless base station
WO2017182927A1 (en) * 2016-04-19 2017-10-26 Nokia Technologies Oy Split bearer dual/multiple connectivity retransmission diversity

Also Published As

Publication number Publication date
CN109661831A (en) 2019-04-19
WO2019127292A1 (en) 2019-07-04

Similar Documents

Publication Publication Date Title
CN110741709B (en) Method and apparatus for controlling duplicate data transfer function in dual connection
CN111130719B (en) Method for transmitting data, terminal equipment and network equipment
EP3672128B1 (en) Data transmission method, terminal device and network device
CN109644369B (en) Data transmission method and terminal equipment
CN114222331B (en) Data transmission method and terminal equipment
CN109661831B (en) Method and device for controlling data copying and transmitting function
US20210211932A1 (en) Method for indicating state of pdcp duplicate data, terminal device, and network device
CN109845318B (en) Method, terminal equipment and network equipment for data processing
CN110710246A (en) Method for processing radio link failure, terminal equipment and network equipment
CN113115360B (en) Wireless communication method, communication device, chip and communication system
CN113518401B (en) Wireless communication method, terminal equipment and network equipment
US20210250810A1 (en) Data replication transmission configuration method, apparatus, chip, and computer program
CN113068225B (en) Information indication method and device, and terminal
CN111837419B (en) Data transmission method, terminal equipment and network equipment
CN113455042A (en) Wireless communication method, terminal equipment and network equipment
CN110710317B (en) Wireless communication method and apparatus
CN113543213A (en) Transmission method and device based on copied data
CN109644351B (en) Data processing method and device
CN111989951B (en) Data forwarding method and device, and network equipment
CN109716822B (en) Method for controlling terminal equipment to generate uplink signaling, terminal equipment and network equipment
CN114845345A (en) Wireless communication method, terminal equipment and network equipment

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant