CN110710255B - Method for terminal equipment to trigger data to stop transmission and terminal equipment - Google Patents
Method for terminal equipment to trigger data to stop transmission and terminal equipment Download PDFInfo
- Publication number
- CN110710255B CN110710255B CN201880036879.1A CN201880036879A CN110710255B CN 110710255 B CN110710255 B CN 110710255B CN 201880036879 A CN201880036879 A CN 201880036879A CN 110710255 B CN110710255 B CN 110710255B
- Authority
- CN
- China
- Prior art keywords
- rlc entity
- secondary cell
- data transmission
- rlc
- radio bearer
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/04—Error control
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
The invention discloses a method for triggering data to stop transmission by a terminal device, the terminal device and a computer storage medium, wherein the method comprises the following steps: and when the data transmitted on the first radio bearer reaches the maximum retransmission times on the first RLC entity, the terminal equipment suspends the data transmission of the first RLC entity.
Description
Technical Field
The present invention relates to the field of information processing technologies, and in particular, to a method for a terminal device to trigger data to stop transmission, a terminal device, and a computer storage medium.
Background
For data copy transmission, in the current discussion of NR, data copy transmission based on PDCP duplication mode has been performed at the same time to improve data transmission reliability. NR currently defines data replication transmission: for the Carrier Aggregation (CA), the scheme supporting data replication transmission utilizes the data replication function of the PDCP, so that the replicated PDCP PDUs are respectively transmitted to two RLC entries (two different logical channels), and finally the replicated PDCP PDUs can be transmitted on different physical layer aggregation carriers, thereby achieving frequency diversity gain to improve data transmission reliability.
However, there is currently no discussion of how to configure the cell group configuration of the primary RLC entity.
Disclosure of Invention
In order to solve the above technical problem, embodiments of the present invention provide a method for a terminal device to trigger data to stop transmission, a terminal device, and a computer storage medium.
The embodiment of the invention provides a method for triggering data to stop transmission by terminal equipment, which comprises the following steps:
and when the data transmitted on the first radio bearer reaches the maximum retransmission times on the first RLC entity, the terminal equipment suspends the data transmission of the first RLC entity.
An embodiment of the present invention provides a terminal device, including:
and the processing unit suspends the data transmission of the first RLC entity when the data transmitted on the first radio bearer reaches the maximum retransmission times on the first RLC entity.
The terminal device provided by the embodiment of the invention comprises: a processor and a memory for storing a computer program capable of running on the processor,
wherein the processor is configured to perform the steps of the aforementioned method when running the computer program.
Embodiments of the present invention provide a computer storage medium, which stores computer-executable instructions, and when executed, implement the foregoing method steps.
The technical scheme of the embodiment of the invention can control whether the terminal equipment suspends the data transmission of the first RLC entity or not based on the maximum retransmission times. Therefore, for the RLC entity, if all the cell groups configured by the corresponding logical channel are secondary cells, the RRC reconfiguration is not triggered, and only the event that the retransmission reaches the maximum number of times needs to be reported, so that the influence of the reconfiguration on the terminal equipment is reduced.
Drawings
Fig. 1 is a schematic flowchart of a method for a terminal device to trigger data transmission stop according to an embodiment of the present invention;
FIG. 2 is a schematic diagram of a dual connectivity network architecture;
FIG. 3 is a schematic diagram of a structure of a terminal device according to an embodiment of the present invention;
fig. 4 is a schematic diagram of a hardware architecture according to an embodiment of the present invention.
Detailed Description
So that the manner in which the features and aspects of the embodiments of the present invention can be understood in detail, a more particular description of the embodiments of the invention, briefly summarized above, may be had by reference to the embodiments, some of which are illustrated in the appended drawings.
The first embodiment,
The embodiment of the invention provides a method for triggering data to stop transmission by terminal equipment, which comprises the following steps:
and when the data transmitted on the first radio bearer reaches the maximum retransmission times on the first RLC entity, the terminal equipment suspends the data transmission of the first RLC entity.
Specifically, as shown in fig. 1, the method provided in this embodiment includes the following steps:
step 101: and when the data transmitted on the first radio bearer reaches the maximum retransmission times on the first RLC entity, the terminal equipment suspends the data transmission of the first RLC entity.
Step 102: and the terminal equipment reports the RLF message to the network side.
Here, the terminal device may be a terminal device in a mobile communication system, such as a smart terminal, a mobile phone, and the like.
Wherein the first radio bearer is a signaling radio bearer SRB or a data radio bearer DRB. By adopting the above scheme, for a certain radio bearer (DRB or SRB) adopting the CA architecture for PDCP duplexing, the associated first RLC entity triggers the SCell-RLF, and the UE suspends (suspend) the RLC entity.
Further, the first radio bearer is: a radio bearer configured with the data copy transmission function, or a radio bearer not configured with the data copy transmission function.
And when the first radio bearer is a radio bearer configured with a data copy transmission function, the data copy transmission of the first radio bearer is in an activated state or a deactivated state.
It should also be understood that the first radio bearer and the first RLC entity are in a corresponding relationship with each other.
The first RLC entity is an Acknowledged Mode (AM) RLC entity, and data carrying a logical channel of the first RLC entity is transmitted only in a secondary cell or a secondary cell group.
The present embodiment may be directed to a carrier aggregation CA architecture, and one form of the CA architecture may refer to fig. 2, where each RLC entity corresponds to one radio carrier. Based on the architecture provided in fig. 2, a logical channel corresponding to an RLC entity may be configured with one or a group of cells (groups), and the cells (groups) configured by two logical channels under CA duplicate are different, so that duplicate PDCP PDUs are transmitted on different carriers, and it may be further defined that p-leg is a transmission path corresponding to a primary RLC entity (e.g., RLC entity a in the figure) and s-leg corresponds to a transmission path corresponding to a secondary RLC entity (e.g., RLC entity b in the figure). Wherein p-leg means that when CA duplexing is deactivated, PDCP defaults to using leg, such as: both p-leg and s-leg belong to a non-primary cell or a non-primary cell group; p-leg corresponds to PCell/PSCell, and s-leg does not correspond to PCell; p-leg does not belong to Pcell/PScell, s-leg belongs to PCcell/PScell.
In the foregoing step 102, the suspending, by the terminal device, data transmission of the first RLC entity includes:
suspending data transmission of the first RLC entity after re-establishing the first RLC entity.
Wherein the suspending of data transmission of the first RLC entity comprises: suspending data transmission of a PDCP entity associated with the first RLC entity. In conjunction with the architecture described in fig. 2, it can be seen that the RLC entity and the PDCP entity have a data transmission relationship with each other, and therefore, suspending data transmission of the first RLC entity may include suspending data transmission between the first RLC entity and the PDCP entity.
In addition, the suspending data transmission of the first RLC entity may further include: and deactivating the secondary cell or the secondary cell group corresponding to the first RLC entity.
In addition, when suspending the data transmission of the first RLC entity, the method further includes: data transmission of the second RLC entity is suspended.
The second RLC entity and the first RLC entity are both configured with RLC under the radio bearer for duplicated data transmission, and both the first RLC entity and the second RLC entity correspond to the first PDCP. That is, the second RLC entity and the first RLC entity may be a primary RLC entity and a secondary RLC entity, i.e., the RLC entity a and the RLC entity b in fig. 2, and both entities correspond to the same one PDCP entity.
Or the second RLC entity corresponds to a second PDCP, and the second PDCP is different from the first PDCP corresponding to the first RLC; the second PDCP configures a duplicated data transmission function or is not configured with a duplicated data transmission function; at least one auxiliary cell or auxiliary cell group which is the same as the auxiliary cell or auxiliary cell group corresponding to the first RLC entity exists in the auxiliary cell or auxiliary cell group corresponding to the second RLC entity; the first RLC entity and the second RLC entity belong to MCG, SCG or different CG respectively. That is, there may also be a case where two RLC entities respectively belong to different PDCP; correspondingly, two RLC entities may also belong to the same MCG and SCG, respectively, or belong to different CGs, for example, one belongs to MCG and one belongs to SCG.
Specifically, the suspending of data transmission of the second RLC entity includes at least one of:
suspending data transmission of the second RLC entity after re-establishing the second RLC entity;
suspending data transmission of a second PDCP entity associated with the second RLC entity;
and deactivating the secondary cell or the secondary cell group corresponding to the second RLC entity.
Wherein, when suspending the second RLC entity data transmission, further comprises: deactivating an auxiliary cell intersected with an auxiliary cell or an auxiliary cell group corresponding to the first RLC entity; and after the secondary cell is deactivated, the second RLC entity suspends data transmission or keeps data transmission. For example, the secondary cell group corresponding to the second RLC entity is {1234}, and the secondary cell group corresponding to the first RLC entity is {456}, in which case, the second RLC entity may deactivate the secondary cell 4, and may select to suspend data transmission or maintain data transmission.
The method further comprises at least one of:
in the message of reporting the RLF, the identifier ID of the logic channel of the suspended RLC entity is contained;
the message for reporting the RLF comprises the identifier index of the deactivated secondary cell;
and the message for reporting the RLF comprises a bearer identification ID corresponding to the PDCP for stopping data transmission.
The suspension of the RLC entity by the UE means that the data transmission or reception of the RLC is stopped, that is, the PDCP stops delivering new data to the RLC.
The method further comprises the following steps:
determining an auxiliary cell or an auxiliary cell group configured by a logical channel corresponding to the first RLC entity or the second RLC entity; determining a secondary cell or a secondary cell group in an active state from the secondary cell or the secondary cell group; and suspending at least one RLC entity corresponding to the auxiliary cell or the auxiliary cell group in the activated state.
That is, the UE suspends the RLC entity, determines the SCells in the active state in one or a group of SCells configured in the logical channel corresponding to the RLC entity, finds the logical channel (if any) in which the SCells in the active state are configured (partially or fully configured), and suspends the RLC entity corresponding to the logical channel. Such as:
the SCells corresponding to the logical channel configuration of the RLC entity triggering the SCell-RLF are {1, 2, 3, 4, 5}, wherein {3, 4} is in an activated state, and the SCells corresponding to the logical channel configuration of the other two RLC entities are {3, 4} and {1, 3, 6}, so that the two RLC entities also need to be suspended;
and the radio bearer corresponding to the RLC entity may be a bearer configured with a data copy transmission function, or a bearer not configured with a data copy transmission function.
The first RLC entity or the second RLC entity is a main RLC or a secondary RLC entity of a PDCP copy function radio bearer in a carrier aggregation architecture. The RLC entity may be a primary RLC corresponding to the CA architecture PDCP duplicate radio bearer, or a secondary RLC: the primary RLC is the RLC to which the PDCP delivers new data after the duplicate deactivation, and is the primary RLC; the secondary RLC means that after the duplicate deactivation, the PDCP stops delivering new data to the RLC, which is the secondary RLC.
The action of the UE suspending the RLC entity is triggered by the SCell-RLF, and specifically, the maximum number of retransmissions of data transmitted on the first radio bearer is reached on the first RLC entity, further comprising:
and when the retransmission counter corresponding to the RLC SDU of the first RLC entity reaches a configured threshold value, determining that the maximum retransmission times on the first RLC entity are reached.
That is to say, the triggering of the SCell-RLF is when a retransmission counter RETX _ COUNT corresponding to a certain RLC SDU of the RLC entity reaches a configured threshold maxRetxThreshold.
Then, the method may further include setting a retransmission counter corresponding to the first RLC entity to zero. For the suspended RLC entity, its corresponding UE suspended RLC entity RETX _ COUNT is set to zero:
when the first RLC entity is suspended, setting a retransmission counter corresponding to the first RLC entity to zero;
or, when resuming after suspending the first RLC entity, setting a retransmission counter corresponding to the first RLC entity to zero.
And the UE deactivates all SCells in the activated state and having the mapping relation with the RLC entity, and when the first RLC entity or the second RLC entity is suspended, the UE deactivates the data copying and transmitting function of the radio bearer corresponding to the auxiliary cell or the auxiliary cell group in the activated state and having the mapping relation with the first RLC entity or the second RLC entity. That is, the UE may deactivate the data copy transmission function of the corresponding bearer.
Therefore, by adopting the scheme, whether the terminal equipment suspends the data transmission of the first RLC entity or not can be controlled based on the maximum retransmission times. Therefore, for the RLC entity, if all the cell groups configured by the corresponding logical channel are secondary cells, the RRC reconfiguration is not triggered, and only the event that the retransmission reaches the maximum number of times needs to be reported, so that the influence of the reconfiguration on the terminal equipment is reduced.
Example II,
An embodiment of the present invention provides a terminal device, as shown in fig. 3, including:
the processing unit 31 suspends data transmission of the first RLC entity when the maximum retransmission times of the data transmitted on the first radio bearer is reached on the first RLC entity.
The communication unit 32 reports the RLF message to the network side.
Here, the terminal device may be a terminal device in a mobile communication system, such as a smart terminal, a mobile phone, and the like.
Wherein the first radio bearer is a signaling radio bearer SRB or a data radio bearer DRB. By adopting the above scheme, for a certain radio bearer (DRB or SRB) adopting the CA architecture for PDCP duplexing, the associated first RLC entity triggers the SCell-RLF, and the UE suspends (suspend) the RLC entity.
Further, the first radio bearer is: a radio bearer configured with the data copy transmission function, or a radio bearer not configured with the data copy transmission function.
And when the first radio bearer is a radio bearer configured with a data copy transmission function, the data copy transmission of the first radio bearer is in an activated state or a deactivated state.
It should also be understood that the first radio bearer and the first RLC entity are in a corresponding relationship with each other.
The first RLC entity is an Acknowledged Mode (AM) RLC entity, and data carrying a logical channel of the first RLC entity is transmitted only in a secondary cell or a secondary cell group.
The present embodiment may be directed to a carrier aggregation CA architecture, and one form of the CA architecture may refer to fig. 2, where each RLC entity corresponds to one radio carrier. Based on the architecture provided in fig. 2, a logical channel corresponding to an RLC entity may be configured with one or a group of cells (groups), and the cells (groups) configured by two logical channels under CA duplicate are different, so that duplicate PDCP PDUs are transmitted on different carriers, and it may be further defined that p-leg is a transmission path corresponding to a primary RLC entity (e.g., RLC entity a in the figure) and s-leg corresponds to a transmission path corresponding to a secondary RLC entity (e.g., RLC entity b in the figure). Wherein p-leg means that when CA duplexing is deactivated, PDCP defaults to using leg, such as: both p-leg and s-leg belong to a non-primary cell or a non-primary cell group; p-leg corresponds to PCell/PSCell, and s-leg does not correspond to PCell; p-leg does not belong to Pcell/PScell, s-leg belongs to PCcell/PScell.
The communication unit 32 suspends data transmission of the first RLC entity after reconstructing the first RLC entity.
Wherein the suspending of data transmission of the first RLC entity comprises: suspending data transmission of a PDCP entity associated with the first RLC entity. In conjunction with the architecture described in fig. 2, it can be seen that the RLC entity and the PDCP entity have a data transmission relationship with each other, and therefore, suspending data transmission of the first RLC entity may include suspending data transmission between the first RLC entity and the PDCP entity.
In addition, the suspending data transmission of the first RLC entity may further include: and deactivating the secondary cell or the secondary cell group corresponding to the first RLC entity.
In addition, when suspending the data transmission of the first RLC entity, the method further includes: data transmission of the second RLC entity is suspended.
The second RLC entity and the first RLC entity are both configured with RLC under the radio bearer for duplicated data transmission, and both the first RLC entity and the second RLC entity correspond to the first PDCP. That is, the second RLC entity and the first RLC entity may be a primary RLC entity and a secondary RLC entity, i.e., the RLC entity a and the RLC entity b in fig. 2, and both entities correspond to the same one PDCP entity.
Or the second RLC entity corresponds to a second PDCP, and the second PDCP is different from the first PDCP corresponding to the first RLC; the second PDCP configures a duplicated data transmission function or is not configured with a duplicated data transmission function; at least one auxiliary cell or auxiliary cell group which is the same as the auxiliary cell or auxiliary cell group corresponding to the first RLC entity exists in the auxiliary cell or auxiliary cell group corresponding to the second RLC entity; the first RLC entity and the second RLC entity belong to MCG, SCG or different CG respectively. That is, there may also be a case where two RLC entities respectively belong to different PDCP; correspondingly, two RLC entities may also belong to the same MCG and SCG, respectively, or belong to different CGs, for example, one belongs to MCG and one belongs to SCG.
Specifically, the processing unit 31 includes at least one of:
suspending data transmission of the second RLC entity after re-establishing the second RLC entity;
suspending data transmission of a second PDCP entity associated with the second RLC entity;
and deactivating the secondary cell or the secondary cell group corresponding to the second RLC entity.
Wherein, when suspending the second RLC entity data transmission, further comprises: the processing unit 31 deactivates an auxiliary cell having an intersection with an auxiliary cell or an auxiliary cell group corresponding to the first RLC entity; and after the secondary cell is deactivated, the second RLC entity suspends data transmission or keeps data transmission. For example, the secondary cell group corresponding to the second RLC entity is {1234}, and the secondary cell group corresponding to the first RLC entity is {456}, in which case, the second RLC entity may deactivate the secondary cell 4, and may select to suspend data transmission or maintain data transmission.
The communication unit 32 includes at least one of:
in the message of reporting the RLF, the identifier ID of the logic channel of the suspended RLC entity is contained;
the message for reporting the RLF comprises the identifier index of the deactivated secondary cell;
and the message for reporting the RLF comprises a bearer identification ID corresponding to the PDCP for stopping data transmission.
The suspension of the RLC entity by the UE means that the data transmission or reception of the RLC is stopped, that is, the PDCP stops delivering new data to the RLC.
The processing unit 31 determines an auxiliary cell or an auxiliary cell group configured by a logical channel corresponding to the first RLC entity or the second RLC entity; determining a secondary cell or a secondary cell group in an active state from the secondary cell or the secondary cell group; and suspending at least one RLC entity corresponding to the auxiliary cell or the auxiliary cell group in the activated state.
That is, the UE suspends the RLC entity, determines the SCells in the active state in one or a group of SCells configured in the logical channel corresponding to the RLC entity, finds the logical channel (if any) in which the SCells in the active state are configured (partially or fully configured), and suspends the RLC entity corresponding to the logical channel. Such as:
the SCells corresponding to the logical channel configuration of the RLC entity triggering the SCell-RLF are {1, 2, 3, 4, 5}, wherein {3, 4} is in an activated state, and the SCells corresponding to the logical channel configuration of the other two RLC entities are {3, 4} and {1, 3, 6}, so that the two RLC entities also need to be suspended;
and the radio bearer corresponding to the RLC entity may be a bearer configured with a data copy transmission function, or a bearer not configured with a data copy transmission function.
The first RLC entity or the second RLC entity is a main RLC or a secondary RLC entity of a PDCP copy function radio bearer in a carrier aggregation architecture. The RLC entity may be a primary RLC corresponding to the CA architecture PDCP duplicate radio bearer, or a secondary RLC: the primary RLC is the RLC to which the PDCP delivers new data after the duplicate deactivation, and is the primary RLC; the secondary RLC means that after the duplicate deactivation, the PDCP stops delivering new data to the RLC, which is the secondary RLC.
The action of the UE suspending the RLC entity is triggered by the SCell-RLF, and specifically, the maximum number of retransmissions of data transmitted on the first radio bearer is reached on the first RLC entity, further comprising:
the processing unit 31 determines that the maximum retransmission times on the first RLC entity is reached when the retransmission counter corresponding to the RLC SDU of the first RLC entity reaches the configured threshold.
That is to say, the triggering of the SCell-RLF is when a retransmission counter RETX _ COUNT corresponding to a certain RLC SDU of the RLC entity reaches a configured threshold maxRetxThreshold.
Then, the method may further include setting a retransmission counter corresponding to the first RLC entity to zero. For the suspended RLC entity, its corresponding UE suspended RLC entity RETX _ COUNT is set to zero:
a processing unit 31, configured to set a retransmission counter corresponding to the first RLC entity to zero when the first RLC entity is suspended;
or, the processing unit 31 sets a retransmission counter corresponding to the first RLC entity to zero when resuming after suspending the first RLC entity.
And the UE deactivates all SCells in the activated state and having the mapping relation with the RLC entity, and when the first RLC entity or the second RLC entity is suspended, the UE deactivates the data copying and transmitting function of the radio bearer corresponding to the auxiliary cell or the auxiliary cell group in the activated state and having the mapping relation with the first RLC entity or the second RLC entity. That is, the UE may deactivate the data copy transmission function of the corresponding bearer.
Therefore, by adopting the scheme, whether the terminal equipment suspends the data transmission of the first RLC entity or not can be controlled based on the maximum retransmission times. Therefore, for the RLC entity, if all the cell groups configured by the corresponding logical channel are secondary cells, the RRC reconfiguration is not triggered, and only the event that the retransmission reaches the maximum number of times needs to be reported, so that the influence of the reconfiguration on the terminal equipment is reduced.
An embodiment of the present invention further provides a hardware composition architecture of a user equipment or a receiver device, as shown in fig. 4, including: at least one processor 41, memory 42, at least one network interface 43. The various components are coupled together by a bus system 44. It will be appreciated that the bus system 44 is used to enable communications among the components. The bus system 44 includes a power bus, a control bus, and a status signal bus in addition to the data bus. For clarity of illustration, however, the various buses are labeled as bus system 44 in fig. 4.
It will be appreciated that memory 42 in embodiments of the invention may be either volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory.
In some embodiments, memory 42 stores the following elements, executable modules or data structures, or a subset thereof, or an expanded set thereof:
an operating system 421 and application programs 422.
Wherein the processor 41 is configured to: the method steps of the first embodiment can be processed, and are not described herein again.
The computer storage medium stores computer-executable instructions, and when executed, the computer-executable instructions implement the method steps of the first embodiment.
The device according to the embodiment of the present invention may also be stored in a computer-readable storage medium if it is implemented in the form of a software functional module and sold or used as an independent product. Based on such understanding, the technical solutions of the embodiments of the present invention may be essentially implemented or a part contributing to the prior art may be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the methods described in the embodiments of the present invention. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read Only Memory (ROM), a magnetic disk, or an optical disk. Thus, embodiments of the invention are not limited to any specific combination of hardware and software.
Correspondingly, the embodiment of the present invention further provides a computer storage medium, in which a computer program is stored, and the computer program is configured to execute the data scheduling method of the embodiment of the present invention.
Although the preferred embodiments of the present invention have been disclosed for illustrative purposes, those skilled in the art will appreciate that various modifications, additions and substitutions are possible, and the scope of the invention should not be limited to the embodiments described above.
Claims (38)
1. A method for triggering data to stop transmission by a terminal device, the method comprising:
when the data transmitted on the first radio bearer reaches the maximum retransmission times on the first RLC entity, the terminal equipment suspends the data transmission of the first RLC entity; the first RLC entity is an AM mode RLC entity, and data bearing a logical channel of the first RLC entity is only transmitted on a secondary cell or a secondary cell group;
when the suspending of the data transmission of the first RLC entity, the method further comprises: suspending data transmission of the second RLC entity; wherein, in the secondary cell or the secondary cell group corresponding to the second RLC entity, at least one secondary cell or the secondary cell group same as the secondary cell or the secondary cell group corresponding to the first RLC entity exists; the second RLC entity corresponds to a second PDCP, and the second PDCP is different from the first PDCP corresponding to the first RLC entity;
and the terminal equipment reports the RLF message to the network side.
2. The method of claim 1, wherein the first radio bearer is a Signaling Radio Bearer (SRB) or a Data Radio Bearer (DRB).
3. The method of claim 1, wherein the first radio bearer is: a radio bearer configured with the data copy transmission function, or a radio bearer not configured with the data copy transmission function.
4. The method of claim 3, wherein the method further comprises:
when the first radio bearer is a radio bearer configured with a data copy transmission function, the data copy transmission of the first radio bearer is in an activated state or a deactivated state.
5. The method of claim 1, wherein the suspension of data transmission by the terminal device for the first RLC entity comprises:
suspending data transmission of the first RLC entity after re-establishing the first RLC entity.
6. The method of claim 5, wherein the suspending data transmission of the first RLC entity comprises:
suspending data transmission of a PDCP entity associated with the first RLC entity.
7. The method of claim 1, wherein the suspending data transmission of the first RLC entity comprises:
and deactivating the secondary cell or the secondary cell group corresponding to the first RLC entity.
8. The method of claim 1, wherein the second RLC entity and the first RLC entity are both RLC under a radio bearer configured for duplicate data transmission.
9. The method of claim 1, wherein,
the second PDCP configures a duplicated data transmission function or is not configured with a duplicated data transmission function;
wherein the first RLC entity and the second RLC entity both belong to MCG, SCG, or belong to different CGs respectively.
10. The method of claim 1, wherein the suspending data transmission of the second RLC entity comprises at least one of:
suspending data transmission of the second RLC entity after re-establishing the second RLC entity;
suspending data transmission of a second PDCP entity associated with the second RLC entity;
and deactivating the secondary cell or the secondary cell group corresponding to the second RLC entity.
11. The method of claim 10, wherein the suspending the second RLC entity data transmission further comprises:
deactivating an auxiliary cell intersected with an auxiliary cell or an auxiliary cell group corresponding to the first RLC entity;
and after the secondary cell is deactivated, the second RLC entity suspends data transmission or keeps data transmission.
12. The method of claim 1, wherein the method further comprises at least one of:
in the message of reporting the RLF, the identifier ID of the logic channel of the suspended RLC entity is contained;
the message for reporting the RLF comprises the identifier index of the deactivated secondary cell;
and the message for reporting the RLF comprises a bearer identification ID corresponding to the PDCP for stopping data transmission.
13. The method of claim 1, wherein the method further comprises:
determining an auxiliary cell or an auxiliary cell group configured by a logical channel corresponding to the first RLC entity or the second RLC entity;
determining a secondary cell or a secondary cell group in an active state from the secondary cell or the secondary cell group;
and suspending at least one RLC entity corresponding to the auxiliary cell or the auxiliary cell group in the activated state.
14. The method of claim 1, wherein the first RLC entity or the second RLC entity is a primary RLC or a secondary RLC entity of a PDCP duplication function radio bearer in a carrier aggregation architecture.
15. The method of claim 1, wherein the data transmitted on the first radio bearer reaches a maximum number of retransmissions at the first RLC entity, further comprising:
and when the retransmission counter corresponding to the RLC SDU of the first RLC entity reaches a configured threshold value, determining that the maximum retransmission times on the first RLC entity are reached.
16. The method of claim 15, wherein the method further comprises:
and setting a retransmission counter corresponding to the first RLC entity to be zero.
17. The method of claim 16, wherein the zeroing the retransmission counter for the first RLC entity comprises:
when the first RLC entity is suspended, setting a retransmission counter corresponding to the first RLC entity to zero;
or, when resuming after suspending the first RLC entity, setting a retransmission counter corresponding to the first RLC entity to zero.
18. The method of claim 1, wherein the method further comprises:
and when the first RLC entity is suspended or the second RLC entity is suspended, deactivating a data copy transmission function of a radio bearer corresponding to an activated auxiliary cell or an auxiliary cell group which has a mapping relation with the first RLC entity or the second RLC entity.
19. A terminal device, comprising:
the processing unit suspends the data transmission of a first Radio Link Control (RLC) entity when the data transmitted on the first radio bearer reaches the maximum retransmission times on the first RLC entity; the first RLC entity is an AM mode RLC entity, and data bearing a logical channel of the first RLC entity is only transmitted on a secondary cell or a secondary cell group;
the processing unit suspends data transmission of a second RLC entity when suspending data transmission of a first RLC entity; wherein, in the secondary cell or the secondary cell group corresponding to the second RLC entity, at least one secondary cell or the secondary cell group same as the secondary cell or the secondary cell group corresponding to the first RLC entity exists; the second RLC entity corresponds to a second PDCP, and the second PDCP is different from the first PDCP corresponding to the first RLC entity;
and the communication unit reports the RLF message to the network side.
20. The terminal device of claim 19, wherein the first radio bearer is a Signaling Radio Bearer (SRB) or a Data Radio Bearer (DRB).
21. The terminal device of claim 19, wherein the first radio bearer is: a radio bearer configured with the data copy transmission function, or a radio bearer not configured with the data copy transmission function.
22. The terminal device of claim 21, wherein the processing unit is configured to, when the first radio bearer is a radio bearer configured with a data copy transmission function, perform data copy transmission of the first radio bearer in an activated state or a deactivated state.
23. The terminal device of claim 19, wherein the processing unit suspends data transmission of a PDCP entity associated with the first RLC entity.
24. The terminal device of claim 19, wherein the processing unit deactivates the secondary cell or the secondary cell group corresponding to the first RLC entity.
25. The terminal device of claim 19, wherein the processing unit suspends data transmission of the second RLC entity.
26. The terminal device of claim 25, wherein the second RLC entity and the first RLC entity are both RLC under a radio bearer configured for duplicate data transmission.
27. The terminal device of claim 25, wherein,
the second PDCP configures a duplicated data transmission function or is not configured with a duplicated data transmission function;
wherein the first RLC entity and the second RLC entity both belong to MCG, SCG, or belong to different CGs respectively.
28. The terminal device of claim 25, wherein the processing unit performs at least one of:
suspending data transmission of the second RLC entity after re-establishing the second RLC entity;
suspending data transmission of a second PDCP entity associated with the second RLC entity;
and deactivating the secondary cell or the secondary cell group corresponding to the second RLC entity.
29. The terminal device of claim 28, wherein the processing unit deactivates a secondary cell that intersects with a secondary cell or a secondary cell group corresponding to the first RLC entity;
and after the secondary cell is deactivated, the second RLC entity suspends data transmission or keeps data transmission.
30. The terminal device of claim 19, wherein the communication unit performs at least one of:
in the message of reporting the RLF, the identifier ID of the logic channel of the suspended RLC entity is contained;
the message for reporting the RLF comprises the identifier index of the deactivated secondary cell;
and the message for reporting the RLF comprises a bearer identification ID corresponding to the PDCP for stopping data transmission.
31. The terminal device of claim 25, wherein the processing unit determines a secondary cell or a secondary cell group configured by a logical channel corresponding to the first RLC entity or the second RLC entity; determining a secondary cell or a secondary cell group in an active state from the secondary cell or the secondary cell group; and suspending at least one RLC entity corresponding to the auxiliary cell or the auxiliary cell group in the activated state.
32. The terminal device of claim 25, wherein the first RLC entity or the second RLC entity is a primary RLC or a secondary RLC entity of a PDCP duplication function radio bearer in a carrier aggregation architecture.
33. The terminal device of claim 19, wherein the processing unit determines that the maximum number of retransmissions has been reached on the first RLC entity when a retransmission counter corresponding to the RLC SDU of the first RLC entity reaches a configured threshold.
34. The terminal device of claim 32, wherein the processing unit is configured to set a retransmission counter corresponding to the first RLC entity to zero.
35. The terminal device of claim 34, wherein the processing unit, when suspending the first RLC entity, sets a retransmission counter corresponding to the first RLC entity to zero;
or, when resuming after suspending the first RLC entity, setting a retransmission counter corresponding to the first RLC entity to zero.
36. The terminal device of claim 25, wherein, when suspending the first RLC entity or suspending the second RLC entity, the processing unit deactivates a data copy transmission function of a radio bearer corresponding to an activated secondary cell or a secondary cell group having a mapping relationship with the first RLC entity or the second RLC entity.
37. A terminal device, comprising: a processor and a memory for storing a computer program capable of running on the processor,
wherein the processor is adapted to perform the steps of the method of any one of claims 1-18 when running the computer program.
38. A computer storage medium having computer-executable instructions stored thereon that, when executed, perform the steps of the method of any one of claims 1-18.
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| PCT/CN2018/074760 WO2019148369A1 (en) | 2018-01-31 | 2018-01-31 | Method for terminal device to trigger termination of data transmission and terminal device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110710255A CN110710255A (en) | 2020-01-17 |
| CN110710255B true CN110710255B (en) | 2021-03-02 |
Family
ID=67477796
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201880036879.1A Active CN110710255B (en) | 2018-01-31 | 2018-01-31 | Method for terminal equipment to trigger data to stop transmission and terminal equipment |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN110710255B (en) |
| WO (1) | WO2019148369A1 (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP4258731A4 (en) * | 2020-12-10 | 2024-02-21 | Huawei Technologies Co., Ltd. | Data transmission processing method and related apparatus |
Family Cites Families (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20130006603A (en) * | 2010-02-12 | 2013-01-17 | 인터디지탈 패튼 홀딩스, 인크 | Method and apparatus for enhancing cell-edge user performance and signaling radio link failure conditions via downlink cooperative component carriers |
| EP2803235A1 (en) * | 2012-01-10 | 2014-11-19 | Nokia Solutions and Networks Oy | Providing a radio bearer on a plurality of component carriers |
| US9838158B2 (en) * | 2013-07-17 | 2017-12-05 | Lg Electronics Inc. | Method for reporting a radio link control re-transmission failure and a device therefor |
| EP3031281B1 (en) * | 2013-08-09 | 2021-04-14 | Nokia Solutions and Networks Oy | Use of packet status report from secondary base station to master base station in wireless network |
| KR20150070637A (en) * | 2013-12-17 | 2015-06-25 | 한국전자통신연구원 | Apparatus and Method for Stopping Transmitting Sensor Data in MAC Layer of Wireless Sensor Network |
| ES2773348T3 (en) * | 2014-01-29 | 2020-07-10 | Huawei Tech Co Ltd | Data processing procedure, device and communication system |
| CN105704739A (en) * | 2014-11-26 | 2016-06-22 | 深圳市中兴微电子技术有限公司 | User plane reinitializing method and device |
| CN106922038A (en) * | 2015-12-24 | 2017-07-04 | 中兴通讯股份有限公司 | The management method and device of data transfer |
-
2018
- 2018-01-31 CN CN201880036879.1A patent/CN110710255B/en active Active
- 2018-01-31 WO PCT/CN2018/074760 patent/WO2019148369A1/en active Application Filing
Non-Patent Citations (5)
| Title |
|---|
| Nokia, Nokia Shanghai Bell.PDCP data duplication in LTE.《3GPP TSG-RAN WG2 #99bis R2-1711001》.2017, * |
| OPPO.RLF on the duplication leg.《3GPP TSG RAN WG2 #99 R2-1707746》.2017, * |
| RLF on the duplication leg;OPPO;《3GPP TSG RAN WG2 #99 R2-1707746》;20170825;参见1-3部分 * |
| Samsung.Discussion on CA Duplication.《3GPP TSG-RAN WG2 Meeting #100 R2-1713830》.2017, * |
| Sharp.Impacts of PDCP Duplication to RLF Triggering When Reaching Maximum Number of RLC Retransmission.《3GPP TSG-RAN2 Meeting #99 R2-1708259》.2017, * |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2019148369A1 (en) | 2019-08-08 |
| CN110710255A (en) | 2020-01-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10772155B2 (en) | Radio link failure handling method and related product | |
| CN110012454B (en) | User equipment and related methods | |
| US11758422B2 (en) | User equipment and related method | |
| US20210068186A1 (en) | Data processing method, terminal-side device and network-side device | |
| US11943657B2 (en) | PDCP duplication function activation method and device, terminal and base station | |
| US11218256B2 (en) | Data transmission method, terminal device and network device | |
| EP3764573A1 (en) | Flexible network control of uplink data duplication | |
| US20210314969A1 (en) | Data sending method and apparatus, storage medium, and sending end | |
| CN113170357A (en) | Data transmission method and terminal equipment | |
| CA3077130C (en) | Control method for duplicate data transmission function, terminal, and computer storage medium | |
| CN113498152A (en) | Method performed by user equipment and user equipment | |
| CN110710255B (en) | Method for terminal equipment to trigger data to stop transmission and terminal equipment | |
| CN110710324B (en) | Method for terminal equipment to deactivate secondary cell, terminal equipment and storage medium | |
| CN111480389B (en) | Information transmission method and device and computer storage medium | |
| CN113498220A (en) | User equipment and method thereof, base station and method thereof | |
| CN112788787A (en) | Network connection control method, terminal and storage medium | |
| CN111052798A (en) | Method and device for controlling data copying function and computer storage medium | |
| US11968728B2 (en) | Method of configuring service data adaptation protocol entity and device | |
| WO2024120319A1 (en) | Information processing method and apparatus, terminal, and network-side device | |
| WO2021102968A1 (en) | Wireless communication method, terminal device, and network device | |
| CN115696638A (en) | Method executed by user equipment and user equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |