CN110475285B

CN110475285B - Operation method and terminal

Info

Publication number: CN110475285B
Application number: CN201810445241.5A
Authority: CN
Inventors: 张艳霞; 吴昱民
Original assignee: Vivo Mobile Communication Co Ltd
Current assignee: Vivo Mobile Communication Co Ltd
Priority date: 2018-05-10
Filing date: 2018-05-10
Publication date: 2021-03-16
Anticipated expiration: 2038-05-10
Also published as: WO2019214472A1; CN110475285A

Abstract

The invention provides an operation method and a terminal, wherein the method comprises the following steps: under a Radio Link Control (RLC) Acknowledged Mode (AM), if a target RLC entity which is copied to bear fails to generate a secondary cell (SCell), stopping sending target data to network side equipment through 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; data of the target RLC entity is configured to be transmitted on the SCell only. Therefore, the processing behavior of the terminal can be standardized, in addition, the power consumption of the terminal can be reduced, and meanwhile, the interference to other terminals can be avoided.

Description

Operation method and terminal

Technical Field

The embodiment of the invention relates to the technical field of communication, in particular to an operation method and a terminal.

Background

In an RLC (Radio Link Control) AM (Acknowledged Mode), a receiving end feeds back an RLC status PDU (Protocol Data Unit) used for representing whether Data is received to a transmitting end. For the condition that the receiving end does not receive the data packet in the feedback, the sending end retransmits the data packet, and meanwhile, the network side equipment configures the maximum retransmission times of the RLC layer data packet.

In LTE (Long Term Evolution, Long Term Evolution system), after the maximum number of retransmissions is reached, the terminal initiates RRC (Radio Resource Control) connection reestablishment, reestablishes an RLC entity and a PDCP (Packet Data Convergence Protocol) entity at the same time, resets an MAC (Medium Access Control) entity, and suspends a corresponding RB (Radio Bearer).

In an NR (New Radio, Radio access) system, a network side device may configure a PDCP duplication function for an RB of a terminal, and after the configured PDCP duplication function is activated, the duplicated data of a PDCP entity is respectively transmitted through two (or more) different paths, for example, two different RLC entities corresponding to different logical channels.

Bearer types of the PDCP data replication function include a Split bearer and a Duplicate bearer. Wherein, 1 PDCP entity, 2 (or multiple) RLC entities and 1 MAC entity corresponding to the Duplicate bearer are in 1 Cell group, and data from different RLC entities is sent through different cells, where the Cell may be a SCell (Secondary Cell) or a PCell (Primary Cell).

If the RLC entity which is configured only on the SCell and corresponding to the duplicate bearer fails, that is, after the maximum retransmission times is reached, the terminal does not trigger the RRC connection reestablishment process. At this time, the RLC layer of the terminal may indicate that the RRC layer has reached the maximum retransmission number, and the RRC layer reports a message that the RLC has failed to the network side through a SCell-RLF (Radio Link Failure) procedure. However, while reporting the failure message to the network side, the processing behavior of the terminal on each transport protocol stack (e.g., PDCP, RLC, MAC) is not yet determined. Therefore, it is necessary to propose a solution for the processing behavior of the terminal in case of failure of the RLC entity configured only for transmission on the SCell corresponding to the duplicate bearer.

Disclosure of Invention

The embodiment of the invention provides an operation method and a terminal, aiming at solving the problems that an RLC entity which is only configured on an SCell and transmitted and corresponds to a duplicate bearer fails and the processing behavior of the terminal is not determined, and providing a solution for the processing behavior of the terminal aiming at the problem that the RLC entity which is only configured on the SCell and transmitted and corresponds to the duplicate bearer fails.

In order to solve the problems, the invention is realized as follows:

in a first aspect, an embodiment of the present invention provides an operating method, where the method includes:

under a Radio Link Control (RLC) Acknowledged Mode (AM), if a target RLC entity which is copied to bear fails to generate a secondary cell (SCell), stopping sending target data to network side equipment through 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; data of the target RLC entity is configured to be transmitted on the SCell only.

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

a stopping module, configured to, in a radio link control, RLC, acknowledged mode AM, stop sending target data to a network side device through a target RLC entity if a target RLC entity that is duplicated and loaded fails to send a secondary cell SCell;

In a third aspect, an embodiment of the present invention further provides a terminal, where the terminal includes a processor, a memory, and a computer program stored in the memory and being executable on the processor, and when the computer program is executed by the processor, the steps of the operating method described above are implemented.

In a fourth aspect, the embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the steps of the operating method as described above.

In the embodiment of the invention, under a Radio Link Control (RLC) Acknowledged Mode (AM), if a target RLC entity which is copied to bear fails to generate a secondary cell (SCell), target data are stopped from being sent to network side equipment through 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; data of the target RLC entity is configured to be transmitted on the SCell only. Therefore, the processing behavior of the terminal can be standardized, in addition, the power consumption of the terminal can be reduced, and meanwhile, the interference to other terminals can be avoided.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the description of the embodiments of the present invention will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art that other drawings can be obtained according to these drawings without inventive exercise.

Fig. 1 is a schematic architecture diagram of a wireless communication system according to an embodiment of the present invention;

fig. 2 is a schematic diagram of an application architecture of a duplicate bearer according to an embodiment of the present invention;

FIG. 3 is a schematic flow chart diagram of a method of operation provided by an embodiment of the present invention;

fig. 4 is one of the structural diagrams of a terminal provided in the embodiment of the present invention;

fig. 5 is a second structural diagram of a terminal according to an embodiment of the present invention.

Detailed Description

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

The operation method and the terminal provided by the embodiment of the invention can be applied to a wireless communication system with a PDCP data duplication (PDCP duplication) function, such as an NR (New Radio, Wireless Access) system and the like.

Referring to fig. 1, fig. 1 is a schematic diagram of a wireless communication system according to an embodiment of the present invention. As shown in fig. 1, the wireless communication system may include: the terminal 11 and the network side device 12, the terminal 11 can be connected with the network side device 12 for communication through the network. In practical applications, the connection between the terminal 11 and the network-side device 12 may be a wireless connection, and for convenience, the connection relationship between the terminal 11 and the network-side device 12 is shown by a dotted line in fig. 1.

The terminal may be understood as a User Equipment (UE), and specifically, the terminal may be a Mobile phone, a Tablet Personal Computer (Tablet Personal Computer), a Laptop Computer (Laptop Computer), a Personal Digital Assistant (PDA), a Mobile Internet Device (MID), a Wearable Device (Wearable Device), or the like.

The network side device may be a base station, a relay station, 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 (Duplicate bearer) in the embodiment of the present invention may be applied to MCG duplication and SCG duplication in a Dual Connectivity (DC) architecture.

As shown in fig. 2, under the DC architecture, 1 PDCP entity carrying a corresponding duplicate is included, and 2 (or more) RLC entities and 1 MAC entity are included in 1 cell group. Data from different RLC entities is transmitted through different cells, which may be scells (Secondary cells) or pcells (Primary cells).

Of course, the duplicate bearer according to the embodiment of the present invention may also be applicable to duplicate bearer replication (duplication) under a single connection architecture, which may be determined according to actual needs, and the embodiment of the present invention does not limit this.

The operation method provided by the embodiment of the invention is explained below.

Referring to fig. 3, fig. 3 is a flowchart illustrating an operation method according to an embodiment of the invention. The operation method of the embodiment of the present invention may be applied to a terminal, and as shown in fig. 3, may include the following steps:

step 301, in an RLC acknowledged mode AM, if a target RLC entity that is duplicated and loaded fails to send target data to a network side device through the target RLC entity, the target data is stopped from being sent to the network side device;

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

In the RLC AM, if the target RLC entity of the duplicated bearer fails to generate the SCell, it indicates that data of the target RLC entity of the duplicated bearer fails to be transmitted through the SCell, that is, the number of times that the UE retransmits the unreceived data packet fed back by the network side reaches the maximum number of times that the network side device retransmits the RLC layer packet, and 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 power and resources of the UE, and cause interference to other UEs.

Therefore, in the embodiment of the present invention, in the RLC acknowledged mode AM, if the target RLC entity that copies the bearer fails to send the secondary cell SCell, the UE stops sending the target data to the network side device through the target RLC entity, that is, does not send the target data to the network side device through the target RLC entity. Therefore, the processing behavior of the UE can be standardized, and meanwhile, compared with the condition that the UE continues to send data to the network side equipment through the target RLC entity, the power consumption of the UE can be reduced, and meanwhile, interference to other UEs can be avoided.

In this embodiment, the target Data may be an RLC Data PDU (Protocol Data Unit) and/or an RLC control PDU of the target RLC entity. The RLC data PDU may be interpreted as an RLC data PDU, and the RLC control PDU may 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 transmitting data through the target RLC entity according to different expressions of the target data, which is illustrated as follows.

And in the first scenario, 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 through the target RLC entity by stopping submitting data to the target RLC entity and clearing uplink data in the cache of the target RLC entity, so that the RLC data PDU in the target RLC entity cannot enter an air interface. For the RLC control PDU of the target RLC entity, the UE may continue to transmit on the target RLC entity, or may stop transmitting on the target RLC entity, which may be determined specifically according to actual needs, and this is not limited in the embodiment of the present invention.

As can be seen, in this scenario, the UE may stop transmitting only part of the uplink data through the target RLC entity.

And in a second scenario, the target data is the RLC data PDU and the RLC control PDU of the target RLC entity.

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

As can be seen, in this scenario, the UE stops sending all uplink data through the target RLC entity.

In the operation method of this embodiment, in an RLC acknowledged mode AM, if a target RLC entity that replicates a bearer fails to send a secondary cell SCell, the target RLC entity stops sending target data to a 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; data of the target RLC entity is configured to be transmitted on the SCell only. Therefore, the processing behavior of the terminal can be standardized, in addition, the power consumption of the terminal can be reduced, and meanwhile, the interference to other terminals can be avoided.

In the embodiment of the present invention, the terminal may perform processing actions on different protocol entities to stop sending target data to the network side device through the target RLC entity, which is specifically described as follows.

Optionally, the stopping transmitting data to the network side device through the target RLC entity includes at least one of:

a. deactivating a PDCP data copying function of the copied bearer;

b. controlling the PDCP entity corresponding to the duplicated bearer to stop sending data to the target RLC entity;

c. stopping allocating uplink authorization for transmitting the target data to the logical channel corresponding to the target RLC entity;

d. and stopping reporting the data capacity of the target data in the target RLC entity.

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

For a, when the PDCP data copy function of the copied bearer is in an active state, the data of the PDCP entity of the copied bearer is no longer transmitted through the target RLC entity. Therefore, the UE may deactivate the function of copying PDCP data of the duplicated bearer, so that the target RLC entity cannot receive data sent by the PDCP entity corresponding to the duplicated bearer, and a data source of the target RLC entity is cut off, so as to stop sending the target data to the network side device through the target RLC entity.

For b, the UE may stop sending data to the target RLC entity by controlling the PDCP entity corresponding to the duplicated bearer, and cut off a data source of the target RLC entity, so as to stop sending target data to the network side device through the target RLC entity.

It should be understood that for the RLC entity to which no SCell failure occurs to which the duplicate bearer corresponds, the PDCP entity to which the duplicate bearer corresponds may continue to deliver data.

As can be seen, for both 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 behaviors of the UE on the MAC entity.

For c, optionally, if the target RLC entity applies for an uplink grant to the network side device through a BSR (Buffer Status Report) before the SCell fails, when the target RLC entity fails, for data (for example, data that has not been sent or data that needs to be retransmitted) buffered in the target RLC entity, the UE may stop allocating the uplink grant for transmitting the target data to the Logical Channel corresponding to the target RLC entity in LCP (Logical Channel priority) processing. Wherein stopping allocation may be understood as not allocating.

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 transmitted, so that the purpose of stopping transmitting the target data to the network side device through the target RLC entity can be achieved.

For d, optionally, if the target RLC entity already indicates the data capacity in the target RLC entity to the MAC layer before the SCell failure occurs, but the MAC layer has not yet sent a BSR, when the target RLC entity has the SCell failure, the UE may stop reporting the data capacity of the target data in the target RLC entity when generating a BSR (Buffer Status Report). Wherein, stopping reporting may be understood as not reporting.

Thus, 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 will not allocate BR resources to the target data in a targeted manner. The UE does not have RB resources for uploading the target data, and cannot send the target data through the target RLC entity, so that the aim of stopping sending the target data to network side equipment through the target RLC entity can be achieved.

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

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, stopping reporting the data capacity of the LCG of the logical channel group, wherein the LCG comprises the 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, so that the data capacity of the logical channel corresponding to the target RLC entity for transmitting the target data will not be included in the BSR generated by the MAC entity, and 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 contribute to the data capacity of the logical channel corresponding to the target RLC entity, and the purpose of stopping reporting the data capacity of the target data in the target RLC entity may be achieved.

For d3, the BSR is considered to be resource-applied according to the LCG, i.e., the LCG indicates the sum of the corresponding data capacities of a plurality of logical channels. Therefore, for the LCG including the logical channel corresponding to the target RLC entity, the UE may stop reporting all the 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 reporting the data capacity of the LCG may be implemented by two ways, d1 and d 2.

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 "stopping sending the target data to the network side device through the target RLC entity" in step 301 is used to specify the processing of the uplink data of the target RLC entity by the UE, and further, the UE may also specify the processing of other data of the target RLC entity, such as the buffered data and the downlink data, which is described in detail below.

Optionally, the method further includes:

and receiving downlink data on the target RLC entity.

As can be seen, the present 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 UE's processing behavior for the RLC entity.

In this embodiment, the UE may still receive the downlink data on the target RLC entity, i.e. the reception of the downlink data by the target RLC entity is not affected.

Optionally, the method further includes:

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

Therefore, the embodiment is used for standardizing the processing of the UE on the cache data of the target RLC entity. Specifically, buffering data includes a transmission buffer and a retransmission buffer. It should be understood that this step is the UE's processing behavior for the RLC entity.

In this embodiment, the UE directly clears the transmission buffer and the retransmission buffer of the target RLC entity, so that resources can be saved and the influence of the RLC entity on the MAC entity can be reduced, compared with the case where the UE retains the buffer data of the target RLC entity and continues to send the uplink data in the buffer.

Optionally, the target data is an RLC data PDU of the target RLC entity; the method further comprises the following steps:

and if the triggering condition and the reporting condition of the RLC status report are satisfied, generating and sending an uplink RLC status report on the target RLC entity.

The embodiment is used for standardizing the processing of the UE on the uplink data except the target data of the target RLC entity. It should be understood that this step is the UE's processing behavior for the RLC entity.

In a specific implementation, the triggering condition of the RLC status report is satisfied, and may include any one of the following items:

receiving indication information which is sent by network side equipment and used for indicating UE to send an uplink RLC status report;

the UE does not successfully decode the received data packet.

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

the timer for forbidding sending the uplink state report does not run;

the timer for forbidding sending the uplink report is overtime;

and the uplink RLC status report is an RLC control PDU of the target RLC entity and is used for feeding back the receiving condition of the downlink data packet of the target RLC entity to network side equipment.

In this way, by sending the uplink RLC status report on the target RLC entity, the network side device can be informed of the packet receiving condition of the target RLC entity, so that the network side device can conveniently retransmit a data packet which is not successfully received by the target RLC entity or continue to send a new data packet to the target RLC entity.

It should be understood that the action of the UE sending the uplink RLC status report on the target RLC entity requires uplink RB resources per se, and if the UE does not have any uplink RB resources, the UE cannot send the uplink RLC status report on the target RLC entity, so the UE needs to send a resource application to the network side device before sending the uplink RLC status report.

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

reporting the data capacity of the uplink RLC state report in the target RLC entity;

and allocating uplink authorization for transmitting the uplink RLC status report to the logical channel corresponding to the target RLC entity.

In this embodiment, the data capacity of the uplink RLC status report in the target RLC entity is reported to inform the network side device of how much data of the logical channel corresponding to the target RLC entity needs to be sent currently, so that the network side device allocates RB resources for sending the uplink RLC status report, and the terminal allocates uplink grant for transmitting the uplink RLC status report to the logical channel corresponding to the target RLC entity, so that the UE can send the uplink RLC status report on the target RLC entity.

It should be noted that, various optional implementations described in the embodiments of the present invention may be implemented in combination with each other or implemented separately, and the embodiments of the present invention are not limited thereto. Examples are illustrated below.

Example 1

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

Specifically, in the RLC acknowledged mode AM, if the target RLC entity that is duplicated and loaded fails to operate on the secondary cell SCell, the UE processes the protocol entities of each layer as follows:

step 1, the processing action of the UE on the PDCP entity comprises any combination of one or more of the following items:

deactivating a PDCP data copying function of the copied bearer;

and controlling the PDCP entity corresponding to the copied bearer to stop sending data to the target RLC entity, namely the PDCP entity only delivers data to the RLC entity corresponding to the copied bearer and without SCell failure.

And step 2, the processing action of the UE on the RLC entity comprises any combination of one or more of the following items:

receiving downlink data at the target RLC entity;

and reserving the buffered data of the target RLC entity and continuously sending the uplink data in the buffer.

And 3, the processing action of the UE on the MAC entity comprises any combination of one or more of the following items:

stopping allocating uplink authorization for transmitting the target data to the logical channel corresponding to the target RLC entity;

and stopping reporting the data capacity of the target data in the target RLC entity.

It should be noted that, in this example, the processing steps of the UE on the respective layers of protocol entities may be performed immediately after the target RLC entity that copies the bearer fails to generate the secondary cell SCell.

For this example, in the RLC acknowledged mode AM, when the target RLC entity that is copied and loaded fails to receive the SCell in the secondary cell, the UE may specify a processing behavior of various types of data of the target RLC entity, and the UE may stop sending uplink data of the target RLC entity while not affecting downlink data reception, so that power of the UE may be saved and interference to other UEs may be avoided.

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 generate and send the uplink RLC status report on the target RLC entity when the triggering condition and the reporting condition of the RLC status report are satisfied.

deactivating a PDCP data copying function of the copied bearer;

receiving downlink data at the target RLC entity;

clearing a transmission buffer and a retransmission buffer of the target RLC entity;

It should be noted that, in this example, step 1 and step 2 (processing actions other than generating and sending the uplink RLC status report on the target RLC entity) may be performed immediately after the target RLC entity that copies the bearer fails to generate the secondary cell SCell; the "processing action except generating and sending the uplink RLC status report on the target RLC entity" in step 2 and step 3 may be performed after the target RLC entity that copies the bearer fails to generate the secondary cell SCell until the UE receives a processing instruction sent by the network side device.

For this example, in the RLC acknowledged mode AM, when the target RLC entity that is copied and loaded fails to generate the SCell in the secondary cell, the UE may specify processing behaviors of various types of data of the target RLC entity, and the UE may stop sending uplink data of the target RLC entity except for the uplink RLC status report, and at the same time, does not affect downlink data reception, thereby saving power of the UE and avoiding interference to other UEs.

Referring to fig. 4, fig. 4 is a diagram illustrating a structure of a terminal according to an embodiment of the present invention. As shown in fig. 4, the terminal 400 includes:

a stopping module 401, configured to, in a radio link control, RLC, acknowledged mode AM, stop sending target data to a network side device through a target RLC entity if a secondary cell, SCell, fails to occur in the target RLC entity that is duplicated and loaded;

In addition to fig. 4, the following describes modules included in the terminal 400 and specific applications of the modules.

Optionally, in the RLC acknowledged mode AM, if the target RLC entity that is duplicated and loaded fails to operate the secondary cell SCell, the stopping module 401 is specifically configured to at least one of:

deactivating a PDCP data copying function of the copied bearer;

controlling the PDCP entity corresponding to the duplicated bearer to stop sending data to the target RLC entity;

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

ignoring the data capacity of the target data in a 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;

and stopping reporting the data capacity of the LCG of the logical channel group, wherein the LCG comprises the logical channel corresponding to the target RLC entity.

Optionally, the terminal 400 further includes:

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

Optionally, the terminal 400 further includes:

and the clearing module is used for clearing 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 the sending module is used for generating and sending an uplink RLC status report on the target RLC entity if the triggering 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 an uplink RLC status report in the target RLC entity before the uplink RLC status report is generated and sent on the target RLC entity;

and the allocation module is used for allocating uplink authorization for transmitting the uplink RLC status report to the logical channel corresponding to the target RLC entity.

The terminal 400 can implement each process in the method embodiment of the present invention and achieve the same beneficial effects, and is not described herein again to avoid repetition.

Referring to fig. 5, fig. 5 is a second structural diagram of a terminal according to a second embodiment of the present invention, where the terminal may be a hardware structural diagram of a terminal for implementing various embodiments of the present invention. As shown in fig. 5, 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, a processor 510, and a power supply 511. Those skilled in the art will appreciate that the terminal configuration shown in fig. 5 is not intended to be limiting, and that the terminal may include more or fewer components than shown, or some components may be combined, or a different arrangement of components. In the embodiment of the present invention, the terminal includes, but is not limited to, a mobile phone, a tablet computer, a notebook computer, a palm computer, a vehicle-mounted terminal, a wearable device, a pedometer, and the like.

Wherein, the processor 510 is configured to:

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

deactivating a PDCP data copying function of the copied bearer;

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

Optionally, the processor 510 is further configured to:

and 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; processor 510, further configured to:

Optionally, the processor 510 is further configured to:

before generating and sending an uplink RLC status report 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 this embodiment, the terminal 500 may implement each process in the method embodiment of the present invention and achieve the same beneficial effects, and for avoiding repetition, details are not described here again.

It should be understood that, in the embodiment of the present invention, the radio frequency unit 501 may be used for receiving and sending signals during a message sending and receiving process or a call process, and specifically, receives downlink data from a base station and then processes the received downlink data to the processor 510; in addition, the uplink data is transmitted 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 frequency unit 501 can also communicate with a network and other devices through a wireless communication system.

The terminal provides wireless broadband internet access to the user through the network module 502, such as helping the user send and receive e-mails, browse web pages, access streaming media, and the like.

The audio output unit 503 may convert 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 sound. Also, the audio output unit 503 may also provide audio output related to a specific function performed by the terminal 500 (e.g., a call signal reception sound, a message reception sound, etc.). The audio output unit 503 includes a speaker, a buzzer, a receiver, and the like.

The input unit 504 is used to receive an audio or video signal. The input Unit 504 may include a Graphics Processing Unit (GPU) 5041 and a microphone 5042, and the Graphics processor 5041 processes image data of a still picture or video obtained by an image capturing device (e.g., a camera) in a video capturing mode or an image capturing mode. The processed image frames may be displayed on the display unit 506. The image frames processed by the graphic processor 5041 may be stored in the memory 509 (or other storage medium) or transmitted via the radio frequency unit 501 or the network module 502. The microphone 5042 may receive sounds and may be capable of processing such sounds into audio data. The processed audio data may be converted into a format output transmittable to a mobile communication base station via the radio frequency unit 501 in case of the phone call mode.

The terminal 500 also includes at least one sensor 505, such as light sensors, motion sensors, and other sensors. Specifically, the light sensor includes an ambient light sensor that adjusts the brightness of the display panel 5061 according to the brightness of ambient light, and a proximity sensor that turns off the display panel 5061 and/or a backlight when the terminal 500 is moved to the ear. As one of the motion sensors, the accelerometer sensor can detect the magnitude of acceleration in each direction (generally three axes), detect the magnitude and direction of gravity when stationary, and can be used to identify the terminal posture (such as horizontal and vertical screen switching, related games, magnetometer posture calibration), vibration identification related functions (such as pedometer, tapping), and the like; the sensors 505 may also include fingerprint sensors, pressure sensors, iris sensors, molecular sensors, gyroscopes, barometers, hygrometers, thermometers, infrared sensors, etc., which are not described in detail herein.

The display unit 506 is used to display information input by the user or information provided to the user. The Display unit 506 may include a Display panel 5061, and the Display panel 5061 may 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 may be used to receive input numeric or character information and 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. Touch panel 5071, also referred to as a touch screen, may collect touch operations by a user on or near it (e.g., operations by a user on or near touch panel 5071 using a finger, stylus, or any suitable object or attachment). The touch panel 5071 may include two parts of a touch detection device and a touch controller. The touch detection device detects the touch direction of a user, detects a signal brought by touch operation and transmits the signal to the touch controller; the touch controller receives touch information from the touch sensing device, converts the touch information into touch point coordinates, sends the touch point coordinates to the processor 510, and receives and executes commands sent by the processor 510. In addition, the touch panel 5071 may be implemented in various types such as a resistive type, a capacitive type, an infrared ray, and a surface acoustic wave. In addition to the touch panel 5071, the user input unit 507 may include other input devices 5072. In particular, other input devices 5072 may include, but are not limited to, a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which are not described in detail herein.

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

The interface unit 508 is an interface for connecting an external device to the terminal 500. For example, the external device may include a wired or wireless headset port, an external power supply (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device having an identification module, an audio input/output (I/O) port, a video I/O port, an earphone port, and the like. The interface unit 508 may be used to receive input (e.g., data information, power, etc.) from external devices and transmit the received input to one or more elements within the terminal 500 or may be used to transmit data between the terminal 500 and external devices.

The memory 509 may 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 program required by at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may store data (such as audio data, a phonebook, etc.) created according to the use of the cellular phone, and the like. Further, the memory 509 may include high-speed random access memory, and may also include non-volatile 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, connects various parts of the entire terminal using various interfaces and lines, and performs various functions of the terminal and processes data by operating or executing software programs and/or modules stored in the memory 509 and calling data stored in the memory 509, thereby performing overall monitoring of the terminal. Processor 510 may include one or more processing units; preferably, the processor 510 may integrate an application processor, which mainly handles operating systems, user interfaces, application programs, etc., and a modem processor, which mainly handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into processor 510.

The terminal 500 may further include a power supply 511 (e.g., a battery) for supplying power to various components, and preferably, the power supply 511 may be logically connected to the processor 510 through a power management system, so that functions of managing charging, discharging, and power consumption are performed through the power management system.

In addition, the terminal 500 includes some functional modules that are not shown, and are not described in detail herein.

Preferably, an embodiment of the present invention further provides a terminal, including a processor 510, a memory 509, and a computer program stored in the memory 509 and capable of running on the processor 510, where the computer program, when executed by the processor 510, implements each process of the above operation method embodiment, and can achieve the same technical effect, and details are not described here to avoid repetition.

The embodiment of the present invention further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the computer program implements each process of the above operation method embodiment, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here. The computer-readable storage medium may be a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal (such as a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present invention.

While the present invention has been described with reference to the embodiments shown in the drawings, the present invention is not limited to the embodiments, which are illustrative and not restrictive, and it will be apparent to those skilled in the art that various changes and modifications can be made therein without departing from the spirit and scope of the invention as defined in the appended claims.

Claims

1. An operation method applied to a terminal is characterized by comprising the following steps:

wherein the target data is an RLC data Protocol Data Unit (PDU) of the target RLC entity; data of the target RLC entity is only configured to be transmitted on the SCell;

receiving downlink data at the target RLC entity;

the method further comprises the following steps:

if the triggering condition and the reporting condition of the RLC status report are established, generating and sending an uplink RLC status report on the target RLC entity;

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

2. The method of claim 1, wherein the stopping of the target data transmission to the network side device via the target RLC entity comprises at least one of:

deactivating a PDCP data copying function of the copied bearer;

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

4. The method of claim 1, further comprising:

5. A terminal, comprising:

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

the terminal further comprises:

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

and the allocation module allocates uplink authorization for transmitting the uplink RLC status report to the logical channel corresponding to the target RLC entity.

6. The terminal of claim 5, wherein the stop module is specifically configured to: in an RLC acknowledged mode AM, if a secondary cell SCell failure occurs in a target RLC entity that replicates a bearer, at least one of the following is performed:

deactivating a PDCP data copying function of the copied bearer;

7. The terminal of claim 6, wherein the stopping module, when stopping reporting the data capacity of the target data in the target RLC entity, is specifically configured to any one of:

8. The terminal of claim 5, further comprising:

9. A terminal, characterized in that it comprises a processor, a memory and a computer program stored on the memory and executable on the processor, the computer program, when executed by the processor, implementing the steps of the operating method according to any one of claims 1 to 4.

10. A computer-readable storage medium, characterized in that a computer program is stored on the computer-readable storage medium, which computer program, when being executed by a processor, carries out the steps of the operating method according to one of claims 1 to 4.