WO2019214472A1

WO2019214472A1 - Operating method and terminal

Info

Publication number: WO2019214472A1
Application number: PCT/CN2019/084757
Authority: WO
Inventors: 张艳霞; 吴昱民
Original assignee: 维沃移动通信有限公司
Priority date: 2018-05-10
Filing date: 2019-04-28
Publication date: 2019-11-14
Also published as: CN110475285B; CN110475285A

Abstract

The present invention provides an operating method and a terminal. The method comprises: in a radio link control (RLC) acknowledged mode (AM), if a secondary cell (SCell) failure occurs to a target RLC entity of a duplicate bearer, terminating sending target data to a network side device by means of the target RLC entity, the target data being an RLC data protocol data unit (PDU) and/or RLC control PDU of the target RLC entity; the data of the target RLC entity being only configured on the SCell for transmission.

Description

Operation method and terminal

Cross-reference to related applications

The present application claims priority to Chinese Patent Application No. 20110144524, filed on Jan. 10, s.

Technical field

The embodiments of the present disclosure relate to the field of communications technologies, and in particular, to an operating method and a terminal.

Background technique

In the Radio Link Control (RLC) Acknowledged Mode (AM), the receiving end feeds back to the transmitting end an RLC Status Protocol Data Unit (PDU) for characterizing whether the data is received. In the case that the receiving end does not receive the data packet, the transmitting end retransmits the data packet, and the network side device configures the maximum number of retransmissions of the RLC layer data packet.

In the Long Term Evolution (LTE) system, after the maximum number of retransmissions is reached, the terminal initiates Radio Resource Control (RRC) connection reestablishment and reconstructs the RLC entity and packet data convergence protocol (Packet Data Convergence). Protocol, PDCP) entity, resets the Medium Access Control (MAC) entity, and suspends the corresponding Radio Bearer (RB) (Suspend).

In the radio access (New Radio, NR) system, the network side device can configure the PDCP duplication function (PDCP duplication) function for the RB of the terminal, and after the PDCP replication data function is activated, the PDCP entity replicates data through two (or more) different paths, such as two different RLC entities, and different RLC entities corresponding to different logical channels.

The bearer types of the PDCP data replication function include a Split bearer split bearer and a Duplicate bearer. The Duplicate bearer corresponds to one PDCP entity, two (or more) RLC entities, and one MAC entity are in one cell group, and data from different RLC entities are sent through different cells, and the cell may be auxiliary. Secondary Cell (SCell) or Primary Cell (PCell).

If the RLC entity configured to transmit on the SCell fails to be transmitted, that is, the maximum number of retransmissions is reached, the terminal does not trigger the RRC connection reestablishment process. At this time, the RLC layer of the terminal indicates that the RRC layer has reached the maximum number of retransmissions, and the RRC layer reports the failure of the RLC to the network side through the radio link failure (SCell-RLF) process. However, while the failure message is reported to the network side, the processing behavior of the terminal for each transport protocol stack (eg, PDCP, RLC, MAC) has not been determined. Therefore, it is necessary to propose a solution for the failure of the RLC entity configured to be transmitted on the SCell corresponding to the replication bearer, and the processing behavior of the terminal.

Summary of the invention

An embodiment of the present disclosure provides an operation method and a terminal, where the problem that the RLC entity configured to be transmitted on the SCell fails to be transmitted and the processing behavior of the terminal has not been determined is determined, and only the configuration corresponding to the replication bearer is transmitted on the SCell. The RLC entity fails, and the processing behavior of the terminal proposes a solution.

To solve the above problems, the present disclosure is implemented as follows:

In a first aspect, an embodiment of the present disclosure provides an operation method, where the method includes:

In the radio link control RLC acknowledgment mode AM, if the target RLC entity of the replication bearer fails to send the secondary cell SCell, the target data is stopped from being sent by the target RLC entity to the network side device;

The target data is an RLC data protocol data unit PDU and/or an RLC control PDU of the target RLC entity; the data of the target RLC entity is only configured to be transmitted on the SCell.

In a second aspect, an embodiment of the present disclosure further provides a terminal, where the terminal includes:

a stopping module, configured to send, by the target RLC entity, the target data to the network side device, if the target RLC entity of the replication bearer fails to generate the secondary cell SCell in the radio link control RLC acknowledge mode AM;

In a third aspect, an embodiment of the present disclosure further provides a terminal, where the terminal includes a processor, a memory, and a computer program stored on the memory and executable on the processor, the computer program being the processor The steps of the method of operation as described above are implemented upon execution.

In a fourth aspect, an embodiment of the present disclosure further provides a computer readable storage medium having stored thereon a computer program, the computer program being executed by a processor to implement the steps of the method of operation as described above.

In the embodiment of the present disclosure, in the radio link control RLC acknowledgment mode AM, if the target RLC entity of the replication bearer fails to send the secondary cell SCell, the target data is stopped from being sent to the network side device by the target RLC entity; The target data is an RLC data protocol data unit PDU and/or an RLC control PDU of the target RLC entity; the data of the target RLC entity is only configured to be transmitted on the SCell. Therefore, the processing behavior of the terminal can be regulated, and in addition, the power consumption of the terminal can be reduced, and interference to other terminals can be avoided.

DRAWINGS

In order to more clearly illustrate the technical solutions of the embodiments of the present disclosure, the drawings used in the description of the embodiments of the present disclosure will be briefly described. It is obvious that the drawings in the following description are only some embodiments of the present disclosure. Other drawings may also be obtained from those of ordinary skill in the art in light of the inventive work.

FIG. 1 is a schematic structural diagram of a wireless communication system according to an embodiment of the present disclosure;

2 is a schematic diagram of an application architecture of a replication bearer according to an embodiment of the present disclosure;

3 is a schematic flowchart of an operation method provided by an embodiment of the present disclosure;

4 is a structural diagram of a terminal provided by an embodiment of the present disclosure;

FIG. 5 is a second structural diagram of a terminal according to an embodiment of the present disclosure.

detailed description

The technical solutions in the embodiments of the present disclosure are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present disclosure. It is obvious that the described embodiments are a part of the embodiments of the present disclosure, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present disclosure without departing from the inventive scope are the scope of the disclosure.

The operation method and terminal provided by the embodiments of the present disclosure may be applied to a wireless communication system having a PDCP duplication function, such as an NR (New Radio) system.

Please refer to FIG. 1. FIG. 1 is a schematic structural diagram of a wireless communication system according to an embodiment of the present disclosure. As shown in FIG. 1, the wireless communication system may include: a terminal 11 and a network side device 12, and the terminal 11 may connect and communicate with the network side device 12 through a network. In a practical application, the connection between the terminal 11 and the network side device 12 may be a wireless connection. In order to conveniently and intuitively represent the connection relationship between the terminal 11 and the network side device 12, a dotted line is illustrated in FIG.

The terminal can be understood as a user equipment (User Equipment, UE). Specifically, the terminal can be a mobile phone, a tablet personal computer, a laptop computer, or a personal digital assistant (PDA). , Mobile Internet Device (MID) or Wearable Device.

The network side device may be a base station, a relay station or an access point, or a radio network controller on the network side, and is not limited herein.

It should be noted that the Duplicate bearer of the embodiment of the present disclosure may be applicable to MCG duplication and SCG duplication in a dual connectivity (DC) architecture.

As shown in FIG. 2, in the DC architecture, one PDCP entity corresponding to the bearer is duplicated, and two (or more) RLC entities and one MAC entity are in one cell group. Data from different RLC entities are transmitted through different cells, which may be a secondary cell (SCell) or a primary cell (PCell).

Certainly, the replication bearer of the embodiment of the present disclosure may also be applicable to the replication bearer duplication in the single-connection architecture, and may be determined according to actual needs, which is not limited by the embodiment of the disclosure.

The operation method provided by the embodiment of the present disclosure will be described below.

Please refer to FIG. 3 , which is a schematic flowchart of an operation method provided by an embodiment of the present disclosure. The operation method of the embodiment of the present disclosure may be applied to a terminal, as described in FIG. 3, and may include the following steps:

Step 301: In the radio link control RLC acknowledgment mode AM, if the target RLC entity of the replication bearer fails to send the secondary cell SCell, stopping sending the target data to the network side device by using the target RLC entity;

In this embodiment, the data of the target RLC entity is only configured to be transmitted on the SCell, and may also be referred to as the target RLC entity is only associated with the SCell, and the data representing the target RLC entity is transmitted only through the SCell.

If the secondary cell SCell fails to be generated by the target RLC entity of the replication bearer, the data of the target RLC entity of the replication bearer fails to be transmitted through the SCell, that is, the number of times the UE retransmits the unreceived data packet fed back by the network side. After the maximum number of retransmissions of the RLC layer data packet configured by the network side device is reached, the network side device still does not receive the data.

At this time, if the UE continues to send data to the network side device through the target RLC entity, the probability that the network side device receives the data is extremely low, which is likely to cause waste of the power of the UE and waste of resources, and cause interference to other UEs.

Therefore, in the embodiment of the present disclosure, in the radio link control RLC acknowledgment mode AM, if the target RLC entity of the replica bearer fails to generate the secondary cell SCell, the UE stops sending the target data to the network side device by using the target RLC entity, That is, the target data is not transmitted to the network side device by the target RLC entity. Therefore, the processing behavior of the UE can be standardized. At the same time, the UE can continue to use the target RLC entity to send data to the network side device, which can also reduce the power consumption of the UE, and can avoid interference to other UEs.

In this embodiment, the target data may be an RLC Data Protocol Data Unit (PDU) and/or an RLC Control PDU of the target RLC entity. The RLC data PDU can be interpreted as an RLC data PDU, and the RLC control PDU can be interpreted as an RLC control PDU. Further, the RLC control PDU may include an uplink RLC status report.

In this embodiment, the UE may perform different processing on the behavior of sending data through the target RLC entity, for example, as follows.

Scenario 1. The target data is the RLC data PDU of the target RLC entity.

In this scenario, the UE may stop sending the RLC data PDU to the network side device by using the target RLC entity by stopping the data delivery to the target RLC and clearing the uplink data in the target RLC entity cache, so that the target RLC is passed through the target RLC. The RLC data PDU in the entity cannot enter the air interface. For the RLC control PDU of the target RLC entity, the UE may continue to send on the target RLC entity. Of course, the UE may also stop transmitting on the target RLC entity, which may be determined according to actual needs, which is not limited by the embodiment of the present disclosure.

It can be seen that in this scenario, the UE can only stop transmitting partial uplink data through the target RLC entity.

Scenario 2: The target data is an RLC data PDU and an RLC control PDU of the target RLC entity.

In this scenario, the UE may stop transmitting the RLC data PDU and the RLC control PDU to the network side device through the target RLC entity by the MAC layer not allocating the uplink grant for the data in the target RLC, so that the target RLC entity is in the target RLC entity. The RLC data PDU and the RLC control PDU cannot enter the air interface.

It can be seen that in this scenario, the UE stops transmitting all uplink data through the target RLC entity.

In the radio link control RLC acknowledgment mode AM, if the secondary cell SCell fails to be generated by the target RLC entity of the replica bearer, the target data is stopped from being sent to the network side device by the target RLC entity; The target data is an RLC data protocol data unit PDU and/or an RLC control PDU of the target RLC entity; the data of the target RLC entity is only configured to be transmitted on the SCell. Therefore, the processing behavior of the terminal can be regulated, and in addition, the power consumption of the terminal can be reduced, and interference to other terminals can be avoided.

In the embodiment of the present disclosure, the terminal may perform a processing behavior on different protocol entities to stop sending the target data to the network side device by using the target RLC entity, as described below.

Optionally, the stopping, by the target RLC entity, transmitting data to the network side device, including at least one of the following:

a. Deactivating the PDCP data replication function of the replication bearer;

b. Controlling the PDCP entity corresponding to the replication bearer to stop sending data to the target RLC entity;

c. Stop assigning an uplink grant for transmitting the target data to a logical channel corresponding to the target RLC entity;

d. Stop reporting the data capacity of the target data in the target RLC entity.

Where a and b are the processing behaviors of the UE to the PDCP entity.

For a, when the PDCP data replication function of the replication bearer is in an active state, data of the PDCP entity of the replication bearer is no longer sent by the target RLC entity. Therefore, the UE can deactivate the PDCP data replication function of the replication bearer, so that the target RLC entity cannot receive the data sent by the PDCP entity corresponding to the replication bearer, and the data source of the target RLC entity is cut off, so that the UE can be stopped. The target RLC entity sends the target data to the network side device.

For b, the UE may stop sending data to the target RLC entity by controlling the PDCP entity corresponding to the replication bearer, and cut off the data source of the target RLC entity, so that the target data may be stopped from being sent to the network side device by the target RLC entity.

It should be understood that, for the RLC entity corresponding to the replication bearer that does not have an SCell failure, the PDCP entity corresponding to the replication bearer may continue to submit data to it.

It can be seen that for a and b, the UE stops sending the target data to the network side device through the target RLC entity by cutting off the data source of the target RLC entity.

c and d are the processing behavior of the UE to the MAC entity.

For C, optionally, if the target RLC entity has applied for an uplink grant to the network side device by using a Buffer Status Report (BSR) before the SCell failure occurs, when the target RLC entity fails to generate the SCell, For the data buffered in the target RLC entity (for example, data that has not been transmitted or data that needs to be retransmitted), the UE may stop the target RLC entity in Logical Channel Prioritization (LCP) processing. The corresponding logical channel allocates an uplink grant for transmitting the target data. Among them, stopping the allocation can be understood as not assigning.

In this way, if the logical channel corresponding to the target RLC entity is not allocated to the uplink grant for transmitting the target data, the target data cannot be sent, so that the purpose of stopping the sending of the target data to the network side device by the target RLC entity can be achieved. .

For d, optionally, if the target RLC entity has indicated the data capacity in the target RLC entity to the MAC layer before the SCell failure occurs, but the MAC layer has not sent the BSR, then the target RLC entity occurs. When the SCell fails, the UE may stop reporting the data capacity of the target data in the target RLC entity when generating a Buffer Status Report (BSR). Among them, stopping reporting can be understood as not reporting.

In this way, the network side device cannot know the data capacity of the logical channel corresponding to the target RLC entity for transmitting the target data, and the BR resource will not be allocated to the target data in a targeted manner. The UE does not have the RB resource for uploading the target data, and the target data cannot be sent by the target RLC entity, so that the purpose of stopping sending the target data to the network side device by the target RLC entity can be achieved.

Further, the stopping reporting the data capacity of the target data in the target RLC entity includes any one of the following:

D1, ignoring the data capacity of the target data in the logical channel corresponding to the target RLC entity;

D2, resetting the data capacity of the target data in the logical channel corresponding to the target RLC entity to zero;

D3. Stop reporting the data capacity of the logical channel group LCG, where the LCG includes a logical channel corresponding to the target RLC entity.

For d1, the MAC entity may directly ignore the data capacity of the target data in the logical channel corresponding to the target RLC entity, such that the BSR generated by the MAC entity will not include the logical channel corresponding to the target RLC entity. And a data capacity for transmitting the target data, so that the purpose of stopping reporting the data capacity of the target data in the target RLC entity may be achieved.

For d2, the MAC entity may reset the data capacity of the target data in the logical channel corresponding to the target RLC entity to zero, so that the data capacity of the target data in the BSR generated by the MAC entity will not be correct. The data capacity of the logical channel corresponding to the target RLC entity is contributed, so that the purpose of stopping reporting the data capacity of the target data in the target RLC entity may be achieved.

For d3, it is considered that the BSR applies for resources according to the LCG, that is, the LCG indicates the sum of the data capacities corresponding to the plurality of logical channels. Therefore, for the LCG that includes the logical channel corresponding to the target RLC entity, the UE may stop reporting all data capacity of the LCG, that is, the data capacity of the entire LCG is not reported. Since the LCH includes the logical channel corresponding to the target RLC entity, it can be understood that the data capacity of the target data in the logical channel corresponding to the target RLC entity is not reported to the network side device.

It should be noted that, for d3, stopping the data capacity of the reporting logical channel group LCG can be implemented by two methods, d1 and d2.

In addition, the data capacity of the target data in the logical channel corresponding to the target RLC entity, and the data capacity of the target data in the LCG may be indicated by the PDCP entity, but is not limited thereto.

It should be understood that, in step 301, “stop sending target data to the network side device by the target RLC entity” is used to standardize processing of uplink data of the target RLC entity by the UE, and further, the UE may also perform other operations on the target RLC entity. The processing of data, such as cached data and downstream data, is specified as follows.

Optionally, the method further includes:

Receiving downlink data on the target RLC entity.

It can be seen that the embodiment is used to standardize the processing of the downlink data of the target RLC entity by the UE. It should be understood that this step is the processing behavior of the UE to the RLC entity.

In this embodiment, the UE can still receive downlink data on the target RLC entity, that is, does not affect the reception of the downlink data by the target RLC entity.

Optionally, the method further includes:

Clearing the transmission buffer and retransmission buffer of the target RLC entity.

It can be seen that the embodiment is used to standardize the processing of the cache data of the target RLC entity by the UE. Specifically, the cached data includes a transfer buffer and a retransmission cache. It should be understood that this step is the processing behavior of the UE to the RLC entity.

In this implementation manner, the UE directly clears the transmission buffer and the retransmission buffer of the target RLC entity, so that the UE saves the cached data of the target RLC entity and continues to send the uplink data in the cache, thereby saving resources. At the same time, the impact of the RLC entity on the MAC entity is reduced.

Optionally, the target data is an RLC data PDU of the target RLC entity; the method further includes:

If the trigger condition and the reporting condition of the RLC status report are met, an uplink RLC status report is generated and sent on the target RLC entity.

This embodiment is used to standardize the processing of uplink data by the UE other than the target data of the target RLC entity. It should be understood that this step is the processing behavior of the UE to the RLC entity.

In specific implementation, the trigger condition of the RLC status report is established, and may include any of the following:

Receiving indication information that is sent by the network side device to instruct the UE to send an uplink RLC status report;

The UE did not successfully decode the received data packet.

In the specific implementation, the reporting condition of the RLC status report is established, and may include any one of the following:

The timer that prohibits sending the uplink status report is not running.

The timer that prohibits sending uplink reports times out.

The uplink RLC status report is an RLC control PDU of the target RLC entity, and is used to feed back, to the network side device, the receiving status of the downlink data packet of the target RLC entity.

In this way, by sending the uplink RLC status report on the target RLC entity, the network side device can be notified of the receiving situation of the target RLC entity, so that the network side device resends the target RLC entity to the target RLC entity is unsuccessful. Receive a packet or continue to send a new packet.

It should be understood that the action of the UE transmitting the uplink RLC status report on the target RLC entity requires the uplink RB resource. If the UE does not have any uplink RB resources, the uplink RLC status report cannot be sent on the target RLC entity. The UE needs to send a resource request to the network side device before sending the uplink RLC status report.

Optionally, before the generating and sending the uplink RLC status report on the target RLC entity, the method further includes:

Reporting a data capacity of the uplink RLC status report in the target RLC entity;

And assigning, to the logical channel corresponding to the target RLC entity, an uplink grant for transmitting the uplink RLC status report.

In this embodiment, by reporting the data capacity of the uplink RLC status report in the target RLC entity, the network side device is notified of how much data needs to be sent by the logical channel corresponding to the target RLC entity, so that the network side device is targeted. The RRC resource is allocated by the sending of the uplink RLC status report, and the terminal allocates an uplink grant for transmitting the uplink RLC status report to the logical channel corresponding to the target RLC entity, so that the UE may send the uplink RLC status on the target RLC entity. report.

It should be noted that the various alternative embodiments described in the embodiments of the present disclosure may be implemented in combination with each other, or may be implemented separately, and the embodiments of the present disclosure are not limited thereto. An example is explained below.

Example one

In this example, the target data is the RLC data PDU and the RLC control PDU of the target RLC entity, ie the UE stops transmitting all uplink data through the target RLC entity.

Specifically, in the radio link control RLC acknowledgment mode AM, if the target RLC entity of the replication bearer fails to generate the secondary cell SCell, the UE processes the layer protocol entities as follows:

Step 1: The UE's processing behavior on the PDCP entity includes any combination of one or more of the following:

Deactivating the PDCP data replication function of the replication bearer;

The PDCP entity that controls the replication bearer stops sending data to the target RLC entity, that is, the PDCP entity only submits data to the RLC entity corresponding to the replication bearer that does not have an SCell failure.

Step 2: The processing behavior of the UE on the RLC entity includes any combination of one or more of the following:

Receiving downlink data on the target RLC entity;

The cached data of the target RLC entity is reserved, and the uplink data in the cache is continued to be transmitted.

Step 3: The processing behavior of the UE to the MAC entity includes any combination of one or more of the following:

Stop allocating an uplink grant for transmitting the target data to a logical channel corresponding to the target RLC entity;

Stop reporting the data capacity of the target data in the target RLC entity.

It should be noted that, in this example, the processing procedure of the UE to each layer protocol entity may be performed immediately after the failure of the secondary RNC entity of the replica bearer to generate the secondary cell SCell.

For the present example, in the radio link control RLC acknowledgment mode AM, when the target RLC entity of the replication bearer fails to generate the secondary cell SCell, the UE can standardize the processing behavior of the data of the target RLC entity, and the UE can stop sending the target RLC entity. The uplink data does not affect the downlink data reception at the same time, thereby saving the power of the UE and avoiding interference to other UEs.

Example two

In this example, the target data is the RLC data PDU of the target RLC entity, that is, the UE stops sending the RLC data PDU through the target RLC entity, but may be in the case that the trigger condition and the reporting condition of the RLC status report are established. An uplink RLC status report is generated and sent on the target RLC entity.

Deactivating the PDCP data replication function of the replication bearer;

Receiving downlink data on the target RLC entity;

Clearing the transmission buffer and retransmission buffer of the target RLC entity;

It should be noted that, in this example, steps 1 and 2 (other than the processing behavior of generating and transmitting the uplink RLC status report on the target RLC entity) may fail in the secondary cell SCell of the target RLC entity of the replication bearer. Thereafter, it is executed immediately; in step 2, "the processing behavior other than generating and transmitting the uplink RLC status report on the target RLC entity" and the step 3 may be received by the UE after the secondary RSC entity of the replica bearer fails to generate the secondary cell SCell. Executed during the processing indication sent by the network side device.

For the present example, in the radio link control RLC acknowledgment mode AM, when the target RLC entity of the replication bearer fails to generate the secondary cell SCell, the UE can standardize the processing behavior of the data of the target RLC entity, and the UE can stop sending the target RLC entity. The uplink data except the uplink RLC status report does not affect the downlink data reception, so that the power of the UE can be saved and interference to other UEs can be avoided.

Referring to FIG. 4, FIG. 4 is a structural diagram of a terminal provided by an embodiment of the present disclosure. As shown in FIG. 4, the terminal 400 includes:

The stopping module 401 is configured to stop sending, by the target RLC entity, the target data to the network side device if the target RLC entity of the replication bearer fails to generate the secondary cell SCell in the radio link control RLC acknowledge mode AM;

Based on FIG. 4, the specific modules of the modules and modules included in the terminal 400 will be described below.

Optionally, in the radio link control RLC acknowledgment mode AM, if the target RLC entity of the replication bearer fails to generate the secondary cell SCell, the stopping module 401 is specifically used for at least one of the following:

Deactivating the PDCP data replication function of the replication bearer;

Controlling, by the PDCP entity corresponding to the replication bearer, sending data to the target RLC entity;

Stop reporting the data capacity of the target data in the target RLC entity.

Optionally, when the stopping module 401 is configured to stop reporting the data capacity of the target data in the target RLC entity, the stopping module 401 is specifically used in any one of the following:

Ignoring the data capacity of the target data in the logical channel corresponding to the target RLC entity;

Resetting the data capacity of the target data in the logical channel corresponding to the target RLC entity to zero;

The data capacity of the logical channel group LCG is stopped, and the LCG includes a logical channel corresponding to the target RLC entity.

Optionally, the terminal 400 further includes:

And a receiving module, configured to receive downlink data on the target RLC entity.

Optionally, the terminal 400 further includes:

The clearing module is configured to clear the transmission buffer and the retransmission buffer of the target RLC entity.

Optionally, the target data is an RLC data PDU of the target RLC entity; the terminal 400 further includes:

And a sending module, configured to generate and send an uplink RLC status report on the target RLC entity if the trigger condition and the reporting condition of the RLC status report are met.

Optionally, the terminal 400 further includes:

a reporting module, configured to report a data capacity of the uplink RLC status report in the target RLC entity before generating and sending an uplink RLC status report on the target RLC entity;

And an allocating module, configured to allocate, to the logical channel corresponding to the target RLC entity, an uplink grant for transmitting the uplink RLC status report.

The terminal 400 can implement the various processes in the method embodiments of the present disclosure, and achieve the same beneficial effects. To avoid repetition, details are not described herein again.

Please refer to FIG. 5. FIG. 5 is a second structural diagram of a terminal according to an embodiment of the present disclosure. The terminal may be a hardware structure diagram of a terminal that implements various embodiments of the present disclosure. As shown in FIG. 5, the terminal 500 includes, but is not limited to, a radio frequency unit 501, a network module 502, an audio output unit 503, an input unit 504, a sensor 505, a display unit 506, a user input unit 507, an interface unit 508, a memory 509, and processing. Device 510, and power supply 511 and other components. It will be understood by those skilled in the art that the terminal structure shown in FIG. 5 does not constitute a limitation of the terminal, and the terminal may include more or less components than those illustrated, or combine some components, or different component arrangements. In the embodiments of the present disclosure, the terminal includes, but is not limited to, a mobile phone, a tablet computer, a notebook computer, a palmtop computer, an in-vehicle terminal, a wearable device, and a pedometer.

The processor 510 is configured to:

Optionally, the processor 510 is further configured to perform at least one of the following:

Deactivating the PDCP data replication function of the replication bearer;

Stop reporting the data capacity of the target data in the target RLC entity.

Optionally, the processor 510 is further configured to perform any of the following:

Optionally, the processor 510 is further configured to:

Receiving downlink data on the target RLC entity.

Optionally, the processor 510 is further configured to:

Optionally, the target data is an RLC data PDU of the target RLC entity; the processor 510 is further configured to:

Optionally, the processor 510 is further configured to:

Before the uplink RLC status report is generated and sent on the target RLC entity, reporting the data capacity of the uplink RLC status report in the target RLC entity;

It should be noted that, in the embodiment, the foregoing terminal 500 can implement various processes in the method embodiments in the embodiments of the present disclosure, and achieve the same beneficial effects. To avoid repetition, details are not described herein again.

It should be understood that, in the embodiment of the present disclosure, the radio frequency unit 501 can be used for receiving and transmitting signals during and after receiving or transmitting information, and specifically, receiving downlink data from the base station, and then processing the data to the processor 510; The uplink data is sent to the base station. In general, radio frequency unit 501 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like. In addition, the radio unit 501 can also communicate with the network and other devices through a wireless communication system.

The terminal provides the user with wireless broadband Internet access through the network module 502, such as helping the user to send and receive emails, browse web pages, and access streaming media.

The audio output unit 503 can convert the audio data received by the radio frequency unit 501 or the network module 502 or stored in the memory 509 into an audio signal and output as a sound. Moreover, the audio output unit 503 can also provide audio output (eg, call signal reception sound, message reception sound, etc.) associated with a particular function performed by the terminal 500. The audio output unit 503 includes a speaker, a buzzer, a receiver, and the like.

The input unit 504 is for receiving an audio or video signal. The input unit 504 may include a graphics processing unit (GPU) 5041 and a microphone 5042 that images an still picture or video obtained by an image capturing device (such as a camera) in a video capturing mode or an image capturing mode. The data is processed. The processed image frame can be displayed on the display unit 506. The image frames processed by the graphics processor 5041 may be stored in the memory 509 (or other storage medium) or transmitted via the radio unit 501 or the network module 502. The microphone 5042 can receive sound and can process such sound as audio data. The processed audio data can be converted to a format output that can be transmitted to the mobile communication base station via the radio unit 501 in the case of a telephone call mode.

Terminal 500 also includes at least one type of sensor 505, such as a light sensor, motion sensor, and other sensors. Specifically, the light sensor includes an ambient light sensor and a proximity sensor, wherein the ambient light sensor can adjust the brightness of the display panel 5061 according to the brightness of the ambient light, and the proximity sensor can close the display panel 5061 and/or when the terminal 500 moves to the ear. Or backlight. As a kind of motion sensor, the accelerometer sensor can detect the magnitude of acceleration in all directions (usually three axes). When it is stationary, it can detect the magnitude and direction of gravity. It can be used to identify the terminal attitude (such as horizontal and vertical screen switching, related games, Magnetometer attitude calibration), vibration recognition related functions (such as pedometer, tapping), etc.; sensor 505 may also include fingerprint sensor, pressure sensor, iris sensor, molecular sensor, gyroscope, barometer, hygrometer, thermometer, infrared Sensors, etc., will not be described here.

The display unit 506 is for displaying information input by the user or information provided to the user. The display unit 506 can include a display panel 5061. The display panel 5061 can be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), or the like.

The user input unit 507 can be configured to receive input numeric or character information and to generate key signal inputs related to user settings and function control of the terminal. Specifically, the user input unit 507 includes a touch panel 5071 and other input devices 5072. The touch panel 5071, also referred to as a touch screen, can collect touch operations on or near the user (such as a user using a finger, a stylus, or the like on the touch panel 5071 or near the touch panel 5071. operating). The touch panel 5071 may include two parts of a touch detection device and a touch controller. Wherein, the touch detection device detects the touch orientation of the user, and detects a signal brought by the touch operation, and transmits the signal to the touch controller; the touch controller receives the touch information from the touch detection device, converts the touch information into contact coordinates, and sends the touch information. The processor 510 receives the commands from the processor 510 and executes them. In addition, the touch panel 5071 can be implemented in various types such as resistive, capacitive, infrared, and surface acoustic waves. In addition to the touch panel 5071, the user input unit 507 can also include other input devices 5072. Specifically, the other input devices 5072 may include, but are not limited to, a physical keyboard, function keys (such as a volume control button, a switch button, etc.), a trackball, a mouse, and a joystick, which are not described herein.

Further, the touch panel 5071 can be overlaid on the display panel 5061. When the touch panel 5071 detects a touch operation thereon or nearby, the touch panel 5071 transmits to the processor 510 to determine the type of the touch event, and then the processor 510 according to the touch. The type of event provides a corresponding visual output on display panel 5061. Although the touch panel 5071 and the display panel 5061 are used as two independent components to implement the input and output functions of the terminal in FIG. 5, in some embodiments, the touch panel 5071 and the display panel 5061 may be integrated. The input and output functions of the terminal are implemented, and are not limited herein.

The interface unit 508 is an interface in which an external device is connected to the terminal 500. For example, the external device may include a wired or wireless headset port, an external power (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device having an identification module, and an audio input/output. (I/O) port, video I/O port, headphone port, and more. The interface unit 508 can be configured to receive input from an external device (eg, data information, power, etc.) and transmit the received input to one or more components within the terminal 500 or can be used at the terminal 500 and external devices Transfer data between.

Memory 509 can be used to store software programs as well as various data. The memory 509 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application required for at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may be stored according to Data created by the use of the mobile phone (such as audio data, phone book, etc.). Further, the memory 509 may include a high speed random access memory, and may also include a nonvolatile memory such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device.

The processor 510 is a control center of the terminal, and connects various parts of the entire terminal using various interfaces and lines, by executing or executing software programs and/or modules stored in the memory 509, and calling data stored in the memory 509, executing The terminal's various functions and processing data, so as to monitor the terminal as a whole. The processor 510 can include one or more processing units; optionally, the processor 510 can integrate an application processor and a modem processor, wherein the application processor mainly processes an operating system, a user interface, an application, etc., and a modulation solution The processor mainly handles wireless communication. It can be understood that the above modem processor may not be integrated into the processor 510.

The terminal 500 may further include a power source 511 (such as a battery) for supplying power to various components. Alternatively, the power source 511 may be logically connected to the processor 510 through a power management system to manage charging, discharging, and power management through the power management system. And other functions.

In addition, the terminal 500 includes some functional modules not shown, and details are not described herein again.

Optionally, an embodiment of the present disclosure further provides a terminal, including a processor 510, a memory 509, a computer program stored on the memory 509 and executable on the processor 510, when the computer program is executed by the processor 510 The various processes of the foregoing operation method embodiments are implemented, and the same technical effects can be achieved. To avoid repetition, details are not described herein again.

The embodiment of the present disclosure further provides a computer readable storage medium. The computer readable storage medium stores a computer program. When the computer program is executed by the processor, the processes of the foregoing operation method embodiments are implemented, and the same technical effect can be achieved. To avoid repetition, we will not repeat them here. The computer readable storage medium, such as a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

It is to be understood that the term "comprises", "comprising", or any other variants thereof, is intended to encompass a non-exclusive inclusion, such that a process, method, article, or device comprising a series of elements includes those elements. It also includes other elements that are not explicitly listed, or elements that are inherent to such a process, method, article, or device. An element that is defined by the phrase "comprising a ..." does not exclude the presence of additional equivalent elements in the process, method, item, or device that comprises the element.

Through the description of the above embodiments, those skilled in the art can clearly understand that the foregoing embodiment method can be implemented by means of software plus a necessary general hardware platform, and of course, can also be through hardware, but in many cases, the former is better. Implementation. Based on such understanding, the technical solution of the present disclosure, which is essential or contributes to the related art, may be embodied in the form of a software product stored in a storage medium (such as ROM/RAM, disk, CD-ROM). The instructions include a number of instructions for causing a terminal (which may be a cell phone, computer, server, air conditioner, or network device, etc.) to perform the methods described in various embodiments of the present disclosure.

The embodiments of the present disclosure have been described above with reference to the drawings, but the present disclosure is not limited to the specific embodiments described above, and the specific embodiments described above are merely illustrative and not restrictive, and those skilled in the art In the light of the present disclosure, many forms may be made without departing from the scope of the disclosure and the scope of the appended claims.

Claims

An operation method applied to a terminal, comprising:

In the radio link control RLC acknowledgment mode AM, if the target RLC entity of the replication bearer fails to send the secondary cell SCell, the target data is stopped from being sent by the target RLC entity to the network side device;

The target data is an RLC data protocol data unit PDU and/or an RLC control PDU of the target RLC entity; the data of the target RLC entity is only configured to be transmitted on the SCell.
The method of claim 1, wherein the stopping transmission of data to the network side device by the target RLC entity comprises at least one of the following:

Deactivating the PDCP data replication function of the replication bearer;

Controlling, by the PDCP entity corresponding to the replication bearer, sending data to the target RLC entity;

Stop allocating an uplink grant for transmitting the target data to a logical channel corresponding to the target RLC entity;

Stop reporting the data capacity of the target data in the target RLC entity.
The method of claim 2, wherein the stopping reporting of the data capacity of the target RLC entity for transmitting the target data comprises any one of the following:

Ignoring the data capacity of the target data in the logical channel corresponding to the target RLC entity;

Resetting the data capacity of the target data in the logical channel corresponding to the target RLC entity to zero;

The data capacity of the logical channel group LCG is stopped, and the LCG includes a logical channel corresponding to the target RLC entity.
The method of claim 1 further comprising:

Receiving downlink data on the target RLC entity.
The method of claim 1 further comprising:

Clearing the transmission buffer and retransmission buffer of the target RLC entity.
The method of claim 1, wherein the target data is an RLC data PDU of the target RLC entity; the method further comprising:

If the trigger condition and the reporting condition of the RLC status report are met, an uplink RLC status report is generated and sent on the target RLC entity.
The method according to claim 6, wherein before the generating and transmitting the uplink RLC status report on the target RLC entity, the method further includes:

Reporting a data capacity of the uplink RLC status report in the target RLC entity;

And assigning, to the logical channel corresponding to the target RLC entity, an uplink grant for transmitting the uplink RLC status report.
A terminal comprising:

a stopping module, configured to send, by the target RLC entity, the target data to the network side device, if the target RLC entity of the replication bearer fails to generate the secondary cell SCell in the radio link control RLC acknowledge mode AM;

The target data is an RLC data protocol data unit PDU and/or an RLC control PDU of the target RLC entity; the data of the target RLC entity is only configured to be transmitted on the SCell.
The terminal according to claim 8, wherein the stopping module is specifically configured to: if the secondary cell SCell of the target RLC entity of the replication bearer fails in the radio link control RLC acknowledge mode AM, perform at least one of the following :

Deactivating the PDCP data replication function of the replication bearer;

Controlling, by the PDCP entity corresponding to the replication bearer, sending data to the target RLC entity;

Stop allocating an uplink grant for transmitting the target data to a logical channel corresponding to the target RLC entity;

Stop reporting the data capacity of the target data in the target RLC entity.
The terminal according to claim 9, wherein the stopping module is configured to stop reporting the data capacity of the target data in the target RLC entity, and is specifically used in any one of the following:

Ignoring the data capacity of the target data in the logical channel corresponding to the target RLC entity;

Resetting the data capacity of the target data in the logical channel corresponding to the target RLC entity to zero;

The data capacity of the logical channel group LCG is stopped, and the LCG includes a logical channel corresponding to the target RLC entity.
The terminal according to claim 8, further comprising:

And a receiving module, configured to receive downlink data on the target RLC entity.
The terminal according to claim 8, further comprising:

The clearing module is configured to clear the transmission buffer and the retransmission buffer of the target RLC entity.
The terminal according to claim 8, wherein the target data is an RLC data PDU of the target RLC entity; the terminal further includes:

And a sending module, configured to generate and send an uplink RLC status report on the target RLC entity if a trigger condition of the RLC status report is established and the reporting condition is met.
The terminal of claim 13, further comprising:

a reporting module, configured to report a data capacity of the uplink RLC status report in the target RLC entity before generating and sending an uplink RLC status report on the target RLC entity;

And an allocating module, configured to allocate, to the logical channel corresponding to the target RLC entity, an uplink grant for transmitting the uplink RLC status report.
A terminal comprising a processor, a memory, and a computer program stored on the memory and operable on the processor, the computer program being executed by the processor to implement any one of claims 1 to 7 The steps of the method of operation described in the item.
A computer readable storage medium, wherein the computer readable storage medium stores a computer program, the computer program being executed by a processor to implement the steps of the method of operation according to any one of claims 1 to 7. .