CN109644359B

CN109644359B - Configuration method of RLC entity and related equipment

Info

Publication number: CN109644359B
Application number: CN201880003256.4A
Authority: CN
Inventors: 石聪
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2018-02-09
Filing date: 2018-02-09
Publication date: 2020-12-04
Anticipated expiration: 2038-02-09
Also published as: CN109644359A; WO2019153285A1

Abstract

The embodiment of the application provides a configuration method of an RLC entity and related equipment, which are applied to user equipment, wherein the user equipment comprises the RLC entity, and the method comprises the following steps: and under the condition that the user equipment fails to trigger a link, the user equipment is configured to suspend the related operation of an RLC entity. By adopting the embodiment of the application, the function of the RLC entity is perfected under the condition of radio link failure, and the power consumption of the equipment is saved.

Description

Configuration method of RLC entity and related equipment

Technical Field

The present application relates to the field of communications technologies, and in particular, to a configuration method of an RLC entity and related devices.

Background

For a User Equipment (UE), the UE generally includes a Radio Resource Control (RRC) entity, a Packet Data Convergence Protocol (PDCP) entity, a Radio Link Control (RLC) entity, and a Media Access Control (MAC) entity. Currently, in the discussion of a New Radio (NR), when a Radio link fails, how to configure the RLC entity accordingly is not discussed.

Disclosure of Invention

The embodiment of the application provides a configuration method of an RLC entity and related equipment, which are used for perfecting the function of the RLC entity under the condition of radio link failure and saving the power consumption of the equipment.

In a first aspect, an embodiment of the present application provides a method for configuring an RLC entity, which is applied to a user equipment, where the user equipment includes the RLC entity, and the method includes:

and under the condition that the user equipment fails to trigger a link, the user equipment is configured to suspend the related operation of an RLC entity.

In a second aspect, an embodiment of the present application provides a user equipment, where the user equipment includes an RLC entity, including:

and the processing unit is used for configuring and suspending the related operation of the RLC entity under the condition that the user equipment triggers the link failure.

In a third aspect, embodiments provide a user equipment comprising one or more processors, one or more memories, one or more transceivers, and one or more programs stored in the memories and configured to be executed by the one or more processors, the programs including instructions for performing the steps in the method according to the first aspect.

In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium storing a computer program for electronic data exchange, wherein the computer program causes a computer to execute instructions of some or all of the steps described in the method according to the first aspect.

In a fifth aspect, embodiments of the present application provide a computer program product comprising a non-transitory computer readable storage medium storing a computer program operable to cause a computer to perform some or all of the steps described for the method according to the first aspect. The computer program product may be a software installation package.

Therefore, in the application, when the user equipment fails to trigger the radio link, the user equipment configures and suspends the related operation of the RLC entity, so that the function of the RLC entity is improved under the condition of the radio link failure. In addition, the radio link failure indicates that the user equipment cannot accurately transmit the data to the network equipment, and at the moment, the user equipment configuration suspends the related operation of the RLC entity, so that the power consumption can be reduced, and the power consumption of the equipment can be saved.

These and other aspects of the present application will be more readily apparent from the following description of the embodiments.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments or the background art of the present application, the drawings required to be used in the embodiments or the background art of the present application will be described below.

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

fig. 2 is a schematic structural diagram of a user equipment according to an embodiment of the present application;

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

fig. 4A is a flowchart illustrating a configuration method of an RLC entity according to an embodiment of the present application;

fig. 4B is a schematic diagram of a protocol stack provided in an embodiment of the present application;

fig. 4C is a schematic diagram of another protocol stack provided in the embodiment of the present application;

fig. 4D is a schematic diagram of an aggregated carrier according to an embodiment of the present application;

fig. 4E is a schematic diagram of another aggregated carrier provided in an embodiment of the present application;

fig. 5 is a schematic structural diagram of another user equipment provided in an embodiment of the present application;

fig. 6 is a schematic structural diagram of another user equipment according to an embodiment of the present application.

Detailed Description

The terminology used in the description of the embodiments section of the present application is for the purpose of describing particular embodiments of the present application only and is not intended to be limiting of the present application.

The terms "first," "second," "third," and "fourth," etc. in the description and claims of this application and in the accompanying drawings are used for distinguishing between different objects and not for describing a particular order. Furthermore, the terms "include" and "have," as well as any variations thereof, are intended to cover non-exclusive inclusions.

Fig. 1 shows a wireless communication system to which the present application relates. The wireless communication system is not limited to a Long Term Evolution (LTE) system, and may be a future-Evolution fifth-Generation mobile communication (5 th Generation, 5G) system, an NR system, a Machine-to-Machine communication (M2M) system, or the like. As shown in fig. 1, the wireless communication system 100 may include: one or more network devices 101 and one or more user devices 102. Wherein:

the network device 101 may be a base station, and the base station may be configured to communicate with one or more user equipments, and may also be configured to communicate with one or more base stations having a function of part of the user equipments (for example, communication between a macro base station and a micro base station, such as an access point). The Base Station may be a Base Transceiver Station (BTS) in a Time Division Synchronous Code Division Multiple Access (TD-SCDMA) system, an evolved Node B (eNB) in an LTE system, and a Base Station in a 5G system or a new air interface (NR) system. In addition, the base station may also be an Access Point (AP), a transmission node (Trans TRP), a Central Unit (CU), or other network entity, and may include some or all of the functions of the above network entities.

The user equipment 102 may be distributed throughout the wireless communication system 100 and may be stationary or mobile. In some embodiments of the present application, terminal 102 may be a mobile device, mobile station (mobile station), mobile unit (mobile unit), M2M terminal, wireless unit, remote unit, user agent, mobile client, or the like.

In particular, the network device 101 may be arranged to communicate with the user equipment 102 via the wireless interface 103 under control of a network device controller (not shown). In some embodiments, the network device controller may be part of the core network or may be integrated into the network device 101. The network device 101 and the network device 101 may also communicate with each other directly or indirectly through a backhaul (backhaul) interface 104 (e.g., an X2 interface).

Therefore, in the application, when the user equipment fails to trigger the radio link, the user equipment configures the related operation of the PDCP entity, so that the corresponding configuration of the PDCP entity is realized when the radio link fails. In addition, the radio link failure indicates that the user equipment cannot accurately transmit the data to the network equipment, and at this time, the user equipment configures the PDCP entity to suspend transmitting the data to the first RLC entity, so that the problem of resource waste caused by the first RLC entity continuing to transmit the data downwards (that is, the user equipment continues to transmit the data to the network equipment) can be avoided.

It should be noted that the wireless communication system 100 shown in fig. 1 is only for more clearly illustrating the technical solution of the present application, and does not constitute a limitation to the present application, and as a person having ordinary skill in the art knows, the technical solution provided in the present application is also applicable to similar technical problems as the network architecture evolves and new service scenarios emerge.

Referring to fig. 2, fig. 2 illustrates a user equipment 200 provided by some embodiments of the present application. As shown in fig. 2, the user equipment 200 may include: one or more user device processors 201, memory 202, communication interface 203, receiver 205, transmitter 206, coupler 207, antenna 208, user interface 202, and input-output modules (including audio input-output module 210, key input module 211, and display 212, etc.). These components may be connected by a bus 204 or otherwise, as illustrated in FIG. 2 by a bus connection. Wherein:

communication interface 203 may be used for user device 200 to communicate with other communication devices, such as network devices. Specifically, the network device may be the network device 300 shown in fig. 3. Specifically, the communication interface 203 may be a Long Term Evolution (LTE) (4G) communication interface, or may be a communication interface of a 5G or future new air interface. Not limited to a wireless communication interface, the user equipment 200 may also be configured with a wired communication interface 203, such as a Local Access Network (LAN) interface.

The transmitter 206 may be used for transmit processing, e.g., signal modulation, of the signal output by the user equipment processor 201. The receiver 205 may be used for performing receive processing, such as signal demodulation, on the mobile communication signal received by the antenna 208. In some embodiments of the present application, the transmitter 206 and the receiver 205 may be considered as one wireless modem. In the user equipment 200, the number of the transmitters 206 and the receivers 205 may be one or more. The antenna 208 may be used to convert electromagnetic energy in the transmission line to electromagnetic energy in free space, or vice versa. The coupler 207 is used to divide the mobile communication signal received by the antenna 308 into a plurality of paths and distribute the plurality of paths to the plurality of receivers 205.

In addition to the transmitter 206 and receiver 205 shown in fig. 2, the user device 200 may also include other communication components, such as a GPS module, a Bluetooth (Bluetooth) module, a Wireless Fidelity (Wi-Fi) module, and so forth. Not limited to the above-expressed wireless communication signals, the user equipment 200 may also support other wireless communication signals, such as satellite signals, short-wave signals, and so on. Not limited to wireless communication, user device 200 may also be configured with a wired network interface (e.g., a LAN interface) to support wired communication.

The input and output module may be used to enable interaction between the user equipment 200 and the user/external environment, and may mainly include an audio input and output module 210, a key input module 211, a display 212, and the like. Specifically, the input/output module may further include: cameras, touch screens, sensors, and the like. Wherein the input output modules are in communication with the user device processor 201 through the user interface 209.

Memory 202 is coupled to terminal processor 201 for storing various software programs and/or sets of instructions. In particular, the memory 202 may include high speed random access memory, and may also include non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid state storage devices. The memory 202 may store an operating system (hereinafter referred to simply as a system), such as an embedded operating system like ANDROID, IOS, WINDOWS, or LINUX. The memory 202 may also store a network communication program that may be used to communicate with one or more additional devices, one or more user devices, one or more network devices. The memory 202 may further store a user interface program, which may vividly display the content of the application program through a graphical operation interface, and receive a control operation of the application program from a user through input controls such as menus, dialog boxes, and buttons.

In some embodiments of the present application, the memory 202 may be used to store an implementation program of the configuration method of the RLC entity provided in one or more embodiments of the present application on the user equipment 200 side. For implementation of the configuration method of the RLC entity provided in one or more embodiments of the present application, please refer to the following method embodiments.

In some embodiments of the present application, the user device processor 201 may be configured to read and execute computer readable instructions. Specifically, the user equipment processor 201 may be configured to invoke a program stored in the memory 212, for example, an implementation program of the configuration method of the RLC entity provided in one or more embodiments of the present application on the user equipment 200 side, and execute instructions contained in the program.

It should be noted that the user equipment 200 shown in fig. 2 is only one implementation manner of the embodiment of the present application, and in practical applications, the user equipment 200 may further include more or less components, which is not limited herein.

Referring to fig. 3, fig. 3 illustrates a network device 300 provided by some embodiments of the present application. As shown in fig. 3, the network device 300 may include: one or more network device processors 301, memory 302, communication interface 303, transmitter 305, receiver 306, coupler 307, and antenna 308. These components may be connected by a bus 304, or otherwise, as illustrated in FIG. 4 by way of example. Wherein:

the communication interface 303 may be used for the network device 300 to communicate with other communication devices, such as user equipment or other network devices. Specifically, the user equipment may be the user equipment 200 shown in fig. 2. Specifically, the communication interface 303 may be a Long Term Evolution (LTE) (4G) communication interface, or may be a communication interface of a 5G or future new air interface. Not limited to wireless communication interfaces, network device 300 may also be configured with a wired communication interface 303 to support wired communication, e.g., a backhaul link between one network device 300 and other network devices 300 may be a wired communication connection.

Transmitter 305 may be used to perform transmit processing, e.g., signal modulation, on the signal output by network device processor 301. Receiver 306 may be used for receive processing of mobile communication signals received by antenna 308. Such as signal demodulation. In some embodiments of the present application, the transmitter 305 and the receiver 306 may be considered as one wireless modem. In the network device 300, the number of the transmitters 305 and the receivers 306 may be one or more. The antenna 308 may be used to convert electromagnetic energy in the transmission line to electromagnetic energy in free space or vice versa. Coupler 307 may be used to multiplex the mobile communications signal to a plurality of receivers 306.

Memory 302 is coupled to network device processor 301 for storing various software programs and/or sets of instructions. In particular, the memory 302 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. The memory 302 may store an operating system (hereinafter, referred to as a system), such as an embedded operating system like uCOS, VxWorks, RTLinux, etc. The memory 402 may also store a network communication program that may be used to communicate with one or more additional devices, one or more terminal devices, one or more network devices.

Network device processor 301 may be configured to perform radio channel management, implement call and communication link setup and teardown, provide cell switching control for users within the control area, and the like. Specifically, the network device processor 301 may include: an Administration/communication Module (AM/CM) (a center for voice channel switching and information switching), a Basic Module (BM) (for performing call processing, signaling processing, radio resource management, management of radio links, and circuit maintenance functions), a code conversion and sub-multiplexing unit (TCSM) (for performing multiplexing/demultiplexing and code conversion functions), and so on.

In the embodiment of the present application, the memory 302 may be used to store an implementation program of the configuration method of the RLC entity provided in one or more embodiments of the present application on the network device 300 side. For implementation of the configuration method of the RLC entity provided in one or more embodiments of the present application, please refer to the following method embodiments.

In embodiments of the present application, the network device processor 301 may be configured to read and execute computer readable instructions. Specifically, the network device processor 301 may be configured to invoke a program stored in the memory 302, for example, an implementation program of the configuration method of the RLC entity provided in one or more embodiments of the present application on the network device 300 side, and execute instructions contained in the program.

It should be noted that the network device 300 shown in fig. 3 is only one implementation manner of the embodiment of the present application, and in practical applications, the network device 300 may further include more or less components, which is not limited herein.

Based on the foregoing embodiments respectively corresponding to the wireless communication system 100, the user equipment 200, and the network equipment 300, the present embodiment provides a configuration method of an RLC entity.

Referring to fig. 4A, fig. 4A is a flowchart illustrating a method for configuring an RLC entity according to an embodiment of the present application, where the method is applied to a user equipment, where the user equipment includes the RLC entity, and the method includes the following steps:

step 401: and under the condition that the user equipment fails to trigger a link, the user equipment is configured to suspend the related operation of an RLC entity.

Wherein, the user equipment comprises one RLC entity, or the user equipment comprises two RLC entities. For example, for Carrier Aggregation (CA), if the ue is not configured for duplicated data transmission, the ue includes an RLC entity, and the specific protocol structure is shown in fig. 4B. As another example, for CA, if the ue is configured with duplicate data transmission, the ue includes two RLC entities, and the specific protocol structure is shown in fig. 4C.

Wherein, the PDCP entity is located above the RLC entity, and is configured to process an RRC message on the control plane and an IP packet on the user plane.

The RLC entity is located above the MAC entity, and is configured to provide segmentation and retransmission services for user data and control data.

The CA technology can aggregate 2-5 carriers together, and the maximum transmission bandwidth of 100MHZ is achieved. The CA function may support continuous CA or discontinuous CA. When multiple available component carriers are adjacent to each other along the frequency band, consecutive CAs are transmitted (as shown in fig. 4D in particular). As shown in fig. 4D, carrier 1, carrier 2, and carrier 3 are adjacent to each other, which may be aggregated for communication between the user equipment and the network device. Non-continuous CA occurs when multiple available component carriers are separated along the frequency band (as shown in particular in fig. 4E). As shown in fig. 4E, carrier 1, carrier 2, and carrier 3 are separated along the frequency band, which may be aggregated for communication between the user equipment and the network device.

Wherein, a radio link failure refers to a communication failure in a communication channel. When the signal quality is reduced to the point that the communication cannot be successfully carried out in the communication process, the wireless link is determined to be failed.

In the present application, the radio link failure triggered by the ue may be triggered by the ue when receiving a radio link failure indication from the network device; or the user equipment is triggered when detecting that one or more carriers have radio link failure; or the user equipment may trigger in case it detects that one or more RLC entities reach a maximum number of retransmissions, etc.

The pause refers to stopping a certain process for a while and then executing the process. In this application, suspending the related operation of the RLC entity refers to that the RLC entity stops a service it processes while the user equipment processes the service, and then the subsequent RLC entity performs the operation.

The specific implementation manner of the configuration of the user equipment to suspend the relevant operation of the RLC entity may be: the user equipment can suspend the related operation of the RLC entity through interactive signaling configuration between the entities.

In an embodiment of the present application, the RLC entity includes a first RLC entity, and the triggering, by the user equipment, a link failure includes:

and under the condition that the retransmission times of the first RLC entity are equal to a set threshold value, the user equipment triggers the link failure.

The retransmission times of the first RLC entity is equal to the set threshold value, which indicates that the first RLC entity reaches the maximum retransmission times, and at this time, the radio link failure occurs in the link where the first RLC entity is located.

The set threshold may be specified by a protocol, or may be configured by the network device for the user equipment, which is not limited herein.

In LTE, the user equipment triggers a radio link failure in case of a radio link failure at any RLC entity. After the failure of triggering the radio link by the user equipment, the user equipment initiates an RRC connection reestablishment process to recover the connection between the user equipment and the network equipment. The RRC connection reestablishment process is too long, so that the time length of the user equipment with poor signal quality is prolonged, and the service processing efficiency of the user equipment is further reduced.

In this application, the user equipment triggers a radio link failure when the number of retransmissions of the first RLC entity is equal to a set threshold. If the user equipment does not need to initiate the RRC reestablishment process after the user equipment fails to trigger the radio link, the unnecessary RRC reestablishment process can be avoided, the time length of the user equipment with poor signal quality is shortened, and the service processing efficiency of the user equipment is further improved.

In an embodiment of the application, the suspending the related operations of the RLC entity includes suspending the transmission of data to the MAC entity by the first RLC entity.

Therefore, in the application, since the link where the first RLC entity is located has a radio link failure, the link where the first RLC entity is located cannot accurately transmit data to the network device, and in this case, the first RLC entity suspends data transmission to the MAC entity, which can avoid the problem of resource waste.

In an embodiment of the present application, in a case where the first RLC entity is configured to CA duplicate data transmission, a logical channel of the first RLC entity maps at least one Secondary Cell (SCell).

In an embodiment of the present application, in a case where CA replication data transmission is not configured, the logical channel of the first RLC entity maps at least one secondary cell.

In CA, a Primary Cell (PCell) refers to a Cell operating at a Primary frequency point. The secondary cell is a cell operating at a secondary frequency point. The frequency point refers to a specific absolute frequency value, and is generally the center frequency of the modulation signal. The center frequency of the main carrier is called as a main frequency point, and the center frequency of the auxiliary carrier is called as an auxiliary frequency point.

In an embodiment of the present application, the user equipment further includes a PDCP entity, and when configured to perform CA duplicated data transmission, the user equipment includes two RLC entities used by the PDCP entity for performing the CA duplicated data transmission, where the two RLC entities include the first RLC entity. Specifically, as shown in fig. 4C, the first RLC entity is one of the entities in fig. 4C.

In an embodiment of the application, the user equipment further includes a second RLC entity, and the suspending of the RLC entity related operation includes suspending transmission of data to the MAC entity by the second RLC entity.

Wherein the first RLC entity is different from the second RLC entity.

Specifically, since the radio link failure has occurred in the link where the first RLC entity is located, the signal quality of the user equipment is degraded at this time, and in this case, the second RLC entity directly suspends data transmission to the MAC entity, thereby avoiding that the second RLC entity continues to transmit data downward (that is, the user equipment continues to transmit data to the network equipment), and further avoiding the problem of resource waste.

In an embodiment of the present application, in a case where the configuration is CA duplicate data transmission, the logical channel of the second RLC entity maps at least one secondary cell.

In an embodiment of the present application, the logical channel of the second RLC entity maps at least one secondary cell without being configured to replicate data transmission for CA.

In an embodiment of the present application, the user equipment further includes a PDCP entity, and in a case where the user equipment is configured to CA duplicate data transmission, the user equipment includes two RLC entities used by the PDCP entity for CA duplicate data transmission, where the two RLC entities include the second RLC entity. Specifically, as shown in fig. 4C, the second RLC entity is one of the entities in fig. 4C.

In an embodiment of the present application, the user equipment further includes a PDCP entity, and in a case where the user equipment is configured to CA duplicate data transmission, the user equipment includes two RLC entities used by the PDCP entity for CA duplicate data transmission, where the two RLC entities include the first RLC entity and the second RLC entity. Specifically, as shown in fig. 4C, the first RLC entity and the second RLC entity are two RLC entities in fig. 4C.

In an embodiment of the present application, the serving Cell groups of the first RLC entity and the second RLC entity are Secondary Cell Groups (SCGs).

In an embodiment of the present application, the serving Cell groups of the first RLC entity and the second RLC entity are Primary Cell groups (SCGs).

In an embodiment of the present application, the serving cell group of the first RLC entity is different from the serving cell group of the second RLC entity. For example, the serving cell group of the first RLC entity is a secondary cell group, and the serving cell group of the second RLC entity is a primary cell group. For another example, the serving cell group of the first RLC entity is a master cell group, and the serving cell group of the second RLC entity is a secondary cell group.

In CA, there are multiple cells, one for each carrier. Among all the cells, the cell operating on the primary frequency point is the primary cell. And the cell operating on the auxiliary frequency point is an auxiliary cell. The plurality of secondary cells constitute a secondary cell group. The plurality of primary cells constitute a primary cell group.

In an embodiment of the present application, the first RLC entity and the second RLC entity correspond to at least one same carrier. For example, if the first RLC entity corresponds to carrier 1, carrier 3, and the second RLC entity corresponds to carrier 1, carrier 2, and carrier 3, it can be seen that the first RLC entity and the second RLC entity correspond to two identical carriers.

In an embodiment of the present application, at least one carrier corresponding to the second RLC entity is deactivated.

In an embodiment of the present application, all carriers corresponding to the second RLC entity are deactivated.

Wherein, the data transmission function of the carrier wave needs to be activated or deactivated through signal indication. The activation of the carrier wave indicates that the data transmission function of the carrier wave is turned on, and the carrier wave can carry out data transmission. The fact that the carrier is deactivated indicates that the data transmission function of the carrier is not started, and the carrier cannot perform data transmission.

Specifically, when a carrier is deactivated, the user equipment performs at least one of the following operations within the carrier: 1) not transmitting a Sounding Reference Signal (SRS); 2) not reporting at least one of a CHannel Quality Indicator (CQI), a Rank Indicator (RI), a Precoding Matrix Indicator (PMI), and a CHannel State Information Reference Signal (CRS) of a Physical Uplink Control CHannel (PUCCH); 3) no uplink data is transmitted; 4) not detecting Physical Downlink Control Channel (PDCCH) information for and transmitted on the carrier; 5) random Access Channel (RACH) information is not transmitted.

In an embodiment of the present application, the suspending the related operation of the RLC entity includes suspending a related counter by the RLC entity.

Specifically, in the case that the first RLC entity suspends data transmission to the MAC entity, the operation related to suspending the RLC entity includes suspending a correlation counter by the first RLC entity; in the case that the second RLC entity suspends data transmission to the MAC entity, the suspending RLC entity related operation comprises the second RLC entity suspending a related counter; in the case where the first RLC entity and the second RLC entity suspend transmission of data to the MAC entity, the suspending of the related operations of the RLC entities includes suspending, by the first RLC entity and the second RLC entity, the related counters.

Wherein the correlation counter comprises at least one of: t-PollRecransmit, t-Reassembly and t-StatusProhibit.

Wherein, t-PollRetransmit refers to a polling retransmission timer, which is used to indicate that the transmitting end controls the retransmission interval of the polling.

Wherein t-Reassembly refers to a Reassembly interval timer.

Wherein, t-StatusProhibit refers to a status report prohibit timer, and is used for indicating the sending interval of the status report controlled by the receiving end.

In an embodiment of the present application, the suspending the related operations of the RLC entity includes the RLC entity modifying related variables of the RLC AM or the RLC UM.

Specifically, in the case that the first RLC entity suspends data transmission to the MAC entity, the operation related to suspending the RLC entity includes the first RLC entity modifying a related variable of RLC AM or RLC UM; in the case that the second RLC entity suspends data transmission to the MAC entity, the operation related to suspending the RLC entity includes the second RLC entity modifying a related variable of RLC AM or RLC UM; in the case where the first RLC entity and the second RLC entity suspend transmission of data to the MAC entity, the suspending of the related operations of the RLC entities includes the first RLC entity and the second RLC entity modifying related variables of RLC AM or RLC UM.

Wherein, the related variable of the RLC AM comprises at least one of the following variables: TX _ Next _ Ack, TX _ Next, POLL _ SN, PDU _ WITHOUT _ POLL, and BYTE _ WITHOUT _ POLL.

Wherein TX _ Next _ Ack denotes a Next transmission signal acknowledgement frame.

Where TX _ Next represents the Next expected transmitted data.

In order to ensure correct transmission of the RLC PDU, a Polling mechanism is introduced in an Automatic Repeat-reQuest (ARQ) process, so that a transmitting end can receive a STATUS report (STATUS PDU) from a receiving end and obtain ACK or NACK information.

The PDU _ WITHOUT _ POLL refers to a total number of acknowledged mode Data Protocol Data units (AMD PDUs) sent after recording the last polling procedure.

Wherein, BYTE _ WITHOUT _ POLL refers to recording the total number of BYTEs sent after the last polling process.

Wherein, POLL _ SN is a sequence number of a Radio Link Control Protocol Data Unit (RLC Data PDU) in which the last discriminant test field is set to 1, and the initial value is 0.

Among the related variables of RLC UM, TX _ next (TX side) is included.

Wherein, TX _ next (TX side) represents a transmission traffic of a next cycle of the transmitting end.

In an embodiment of the present application, the suspending the related operations of the RLC entity includes the RLC entity modifying the corresponding carrier.

Specifically, in the case that the first RLC entity suspends data transmission to the MAC entity, the operation related to suspending the RLC entity includes the first RLC entity modifying a corresponding carrier; under the condition that the second RLC entity suspends data transmission to the MAC entity, the related operation of the suspended RLC entity comprises that the second RLC entity modifies a corresponding carrier; in the case where the first RLC entity and the second RLC entity suspend transmission of data to the MAC entity, the suspending operations of the RLC entities includes the first RLC entity and the second RLC entity modifying corresponding carriers.

Wherein modifying the corresponding carrier comprises at least one of: releasing the limitation of the corresponding carrier set so that the RLC entity corresponds to all carriers; configuring an RLC entity to only correspond to a primary cell (Pcell) or a primary secondary cell (PSCell); and removing the carrier corresponding to the second RLC entity from the carrier set corresponding to the first RLC entity.

In an embodiment of the present application, the suspending the operation related to the RLC entity includes the RLC entity performing a packet loss operation.

Specifically, in the case that the first RLC entity suspends data transmission to the MAC entity, the operation related to suspending the RLC entity includes the first RLC entity performing a packet loss operation; under the condition that the second RLC entity suspends data transmission to the MAC entity, the related operation of the suspended RLC entity comprises that the second RLC entity performs packet loss operation; in the case that the first RLC entity and the second RLC entity suspend data transmission to the MAC entity, the suspending operations of the RLC entities includes the first RLC entity and the second RLC entity performing packet loss operations.

The RLC entity performs packet loss operation, wherein the packet loss operation comprises dropping all or part of data packets which do not correspond to the RLC PDU, and/or the packet loss operation comprises dropping all data packets which do not cause the generation of the RLC SN gap.

Referring to fig. 5, fig. 5 is a user equipment 500 according to an embodiment of the present application, where the user equipment 500 includes an RLC entity, and the user equipment 500 includes: one or more processors, one or more memories, one or more transceivers, and one or more programs;

the one or more programs are stored in the memory and configured to be executed by the one or more processors;

the program includes instructions for performing the steps of:

and configuring to suspend the related operation of the RLC entity under the condition that the user equipment triggers the link failure.

In an embodiment of the application, the suspending operation of the RLC entity comprises suspending transmission of data to a medium access control, MAC, entity by the first RLC entity.

In an embodiment of the present application, the logical channel of the first RLC entity maps at least one secondary cell.

In an embodiment of the present application, the user equipment further includes a PDCP entity, and in a case where the user equipment is configured to CA duplicate data transmission, the user equipment includes two RLC entities used by the PDCP entity for CA duplicate data transmission, where the two RLC entities include the first RLC entity.

In an embodiment of the present application, the logical channel of the second RLC entity maps at least one secondary cell.

In an embodiment of the present application, the user equipment further includes a PDCP entity, and in a case where the user equipment is configured to CA duplicate data transmission, the user equipment includes two RLC entities used by the PDCP entity for CA duplicate data transmission, where the two RLC entities include the second RLC entity.

In an embodiment of the present application, the user equipment further includes a PDCP entity, and when configured as CA duplicated data transmission, the user equipment includes two RLC entities used by the PDCP entity for CA duplicated data transmission, where the two RLC entities include the first RLC entity and the second RLC entity.

In an embodiment of the present application, the first RLC entity and the second RLC entity correspond to at least one same carrier.

In an embodiment of the present application, the serving cell groups of the first RLC entity and the second RLC entity are configured as a secondary cell group.

In an embodiment of the present application, the serving cell groups of the first RLC entity and the second RLC entity are configured as master cell groups.

It should be noted that, the specific implementation manner of the content described in this embodiment may refer to the above method, and will not be described here.

Referring to fig. 6, fig. 6 is a user equipment 600 according to an embodiment of the present application, where the user equipment 600 includes an RLC entity, the user equipment 600 includes a processing unit 601, a communication unit 602, and a storage unit 603, and the processing unit 601 includes a receiving unit and a parameter adjusting unit, where:

a processing unit 601, configured to suspend a relevant operation of an RLC entity in case that the user equipment triggers a link failure.

The Processing Unit 601 may be a Processor or a controller (e.g., a Central Processing Unit (CPU), a general purpose Processor, a Digital Signal Processor (DSP), an Application-Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, a transistor logic device, a hardware component, or any combination thereof). The communication unit 602 may be a transceiver, a transceiver circuit, a radio frequency chip, a communication interface, etc., and the storage unit 603 may be a memory.

When the processing unit 601 is a processor, the communication unit 602 is a communication interface, and the storage unit 603 is a memory, the user equipment according to the embodiment of the present application may be the user equipment shown in fig. 5.

The present application also provides a computer-readable storage medium, where the computer-readable storage medium stores a computer program for electronic data exchange, where the computer program makes a computer perform some or all of the steps described in the user equipment in the above method embodiments.

Embodiments of the present application also provide a computer program product, wherein the computer program product comprises a non-transitory computer-readable storage medium storing a computer program operable to cause a computer to perform some or all of the steps described for the user equipment in the above method. The computer program product may be a software installation package.

The steps of a method or algorithm described in the embodiments of the present application may be implemented in hardware, or may be implemented by a processor executing software instructions. The software instructions may be comprised of corresponding software modules that may be stored in Random Access Memory (RAM), flash Memory, Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), registers, a hard disk, a removable disk, a compact disc Read Only Memory (CD-ROM), or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. Of course, the storage medium may also be integral to the processor. The processor and the storage medium may reside in an ASIC. Additionally, the ASIC may reside in an access network device, a target network device, or a core network device. Of course, the processor and the storage medium may reside as discrete components in an access network device, a target network device, or a core network device.

Those skilled in the art will appreciate that in one or more of the examples described above, the functionality described in the embodiments of the present application may be implemented, in whole or in part, by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the application to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored on a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website, computer, server, or data center to another website, computer, server, or data center via wire (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., Digital Video Disk (DVD)), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.

The above-mentioned embodiments are intended to illustrate the objects, technical solutions and advantages of the embodiments of the present application in further detail, and it should be understood that the above-mentioned embodiments are only specific embodiments of the present application, and are not intended to limit the scope of the embodiments of the present application, and any modifications, equivalent substitutions, improvements and the like made on the basis of the technical solutions of the embodiments of the present application should be included in the scope of the embodiments of the present application.

Claims

1. A configuration method of a Radio Link Control (RLC) layer protocol is applied to user equipment, wherein the user equipment comprises a Packet Data Convergence Protocol (PDCP) entity, a first RLC entity and a second RLC entity, and the first RLC entity and the second RLC entity are used for carrying out Carrier Aggregation (CA) copy data transmission, and the method comprises the following steps:

when the user equipment triggers a link where the first RLC entity is located to generate radio link failure, the user equipment configures to suspend the first RLC entity from transmitting data to a Medium Access Control (MAC) entity and suspend the second RLC entity from transmitting data to the MAC entity, and the user equipment does not initiate a Radio Resource Control (RRC) reestablishment process;

wherein the first RLC entity and the second RLC entity correspond to at least one same carrier, and the suspending RLC entity from transmitting data to the MAC entity includes at least one of: the RLC entity suspends a relevant counter, modifies a relevant variable of an RLC AM or an RLC UM, modifies a corresponding carrier wave and executes packet loss operation.

2. The method of claim 1, wherein the UE triggers radio link failure of a link in which the first RLC entity is located when the number of retransmissions of the first RLC entity is equal to a set threshold.

3. The method of claim 1, wherein a logical channel of the first RLC entity maps at least one secondary cell.

4. The method of claim 1, wherein a logical channel of the second RLC entity maps at least one secondary cell.

5. The method of claim 1, wherein a serving cell group of the first RLC entity and the second RLC entity is configured as a secondary cell group.

6. The method of claim 1, wherein a serving cell group of the first RLC entity and the second RLC entity is configured as a master cell group.

7. The method of claim 1, wherein at least one carrier corresponding to the two RLC entities is deactivated.

8. The method of claim 1, wherein all carriers corresponding to the second RLC entity are deactivated.

9. A user equipment, wherein the user equipment comprises a packet data convergence protocol, PDCP, entity, a first radio link control, RLC, entity and a second RLC entity, wherein the first and second RLC entities are configured to perform carrier aggregation, CA, duplicate data transmission, and wherein the user equipment comprises:

a processing unit, configured to suspend, when the user equipment triggers a radio link failure of a link where the first RLC entity is located, transmission of data from the first RLC entity to a medium access control MAC entity and transmission of data from the second RLC entity to the MAC entity are suspended, and the user equipment does not initiate a radio resource control RRC reestablishment process;

10. A user equipment comprising one or more processors, one or more memories, one or more transceivers, and one or more programs, the one or more programs being stored in the memories and configured to be executed by the one or more processors to implement the steps in the method of any one of claims 1-8.

11. A computer-readable storage medium, characterized in that it stores a computer program for electronic data exchange, wherein the computer program causes a computer to perform the steps in the method according to any one of claims 1-8.