Reorganization timer startup method, configuration method, device, equipment and medium
By setting a reorganization offset timer and reorganization timer in a non-terrestrial communication network, the reorganization waiting time of the RLC SDU is extended, and the problem of the reorganization waiting time of the RLC SDU is solved, and the normalization of the RLC SDU is achieved Receive and maintain compatibility with the original design.
Patent Information
- Application Number
- CN202080100474.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2020-07-08
- Publication Date
- 2024-11-26
- Estimated Expiration
- 2040-07-08
AI Technical Summary
In non-terrestrial communication networks, due to the high communication delay between the UE and the network device, the existing restructuring timer cannot work properly, resulting in the problem that the restructuring wait time of the RLC SDU is too short and the RLC SDU cannot be received normally.
By setting the reorganization offset timer and reorganization timer in the RLC entity and starting when a specific condition is met or starting when a timeout is started, the timing time of the reorganization offset timer is increased to extend the reorganization wait time of the RLC SDU, making it a The sum of the recombination offset timer and the recombination timer.
It effectively avoids the problem of the waiting time for reorganization of RLC entities too short, ensures that the RLC SDU can be received normally, and provides backward compatibility of the technical solution while retaining the original design architecture as much as possible.
Smart Images

Figure CN115516912B_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of wireless communications, and in particular to a method for starting a reorganization timer, a configuration method, a device, a equipment and a medium. Background Art
[0002] Each logical channel of the User Equipment (UE) has a Radio Link Control (RLC) entity. The RLC entity has the function of segmenting and reassembling the RLC SDU.
[0003] The RLC entity of the first UE as the sending side will divide the RLC SDU into multiple RLC SDU segments; the RLC entity of the second UE as the receiving side will reassemble the multiple RLC SDU segments to restore the original RLC SDU and submit it to the upper layer (PDCP layer).
[0004] Since different RLC SDU segments of the same RLC SDU may arrive at the second UE out of order, a reassembly timer (t-Reassembly) is set in the second UE to control the time for the second UE to reassemble the RLC SDU. However, under the non-terrestrial communication network (NTN) technology, due to the high communication delay between the UE and the network equipment, the reassembly timer in the related technology cannot work properly. Summary of the invention
[0005] The embodiment of the present application provides a method for starting a reorganization timer, a configuration method, an apparatus, a device and a storage medium. The technical solution is as follows.
[0006] According to one aspect of the present application, a method for starting a reorganization timer is provided, which is used in an RLC entity, and the method includes:
[0007] receiving a first RLC PDU from the MAC layer, the first RLC PDU corresponding to an RLC SDU segment;
[0008] When the first RLC PDU meets a first start condition of a reassembly offset timer and both the reassembly offset timer and the reassembly timer are not started, start the reassembly offset timer;
[0009] When the reassembly offset timer times out, the reassembly timer is started.
[0010] According to one aspect of the present application, a configuration method is provided, the method comprising:
[0011] The network device sends configuration information to the terminal, wherein the configuration information is used to configure the timing duration of the reorganization offset timer of the RLC entity. Alternatively, the configuration information is used to configure the timing duration of the reorganization offset timer and the reorganization timer of the RLC entity.
[0012] According to one aspect of the present application, an RLC entity device is provided, characterized in that the device includes:
[0013] A receiving module, configured to receive a first RLC PDU from a MAC layer, wherein the first RLC PDU corresponds to an RLC SDU segment;
[0014] A timer module is used to start the reorganization offset timer when the first RLC PDU meets the first start condition of the reorganization offset timer and both the reorganization offset timer and the reorganization timer are not started; and start the reorganization timer when the reorganization offset timer times out.
[0015] According to one aspect of the present application, a configuration device is provided, the device comprising:
[0016] A sending module, used to send configuration information to the terminal, wherein the configuration information is used to configure the timing duration of the reorganization offset timer of the RLC entity
[0017] According to one aspect of the present application, a terminal is provided, comprising: a processor; a transceiver connected to the processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to load and execute the executable instructions to implement the method for starting a reorganization timer as described in the above aspects.
[0018] According to one aspect of the present application, a network device is provided, comprising: a processor; a transceiver connected to the processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to load and execute the executable instructions to implement the configuration method as described in the above aspects.
[0019] According to one aspect of the present application, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores executable instructions, and the executable instructions are loaded and executed by the processor to implement the method for starting a reorganization timer as described in the above aspect.
[0020] According to one aspect of the present application, a computer program product is provided, wherein the readable storage medium stores executable instructions, and the executable instructions are loaded and executed by the processor to implement the method for starting or configuring the reorganization timer as described in the above aspects.
[0021] According to one aspect of the present application, a chip is provided, wherein the chip is used to execute and implement the method for starting or configuring the reorganization timer as described in the above aspects.
[0022] The technical solution provided by the embodiments of the present application includes at least the following beneficial effects:
[0023] The network device configures the timer length of the reassembly offset timer of the RLC entity to the terminal, and the terminal adds a reassembly offset timer with the timer length, so that the reassembly waiting time of the RLC entity becomes the sum of the reassembly offset timer and the reassembly timer, thereby avoiding the problem that the reassembly waiting time of the RLC entity is too short and the RLC SDU cannot be received normally. This embodiment can provide the backward compatibility of the technical solution while keeping the original design architecture of the reassembly timer unchanged as much as possible. BRIEF DESCRIPTION OF THE DRAWINGS
[0024] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.
[0025] Figure 1 is a block diagram of a communication system provided by an exemplary embodiment of the present application;
[0026] Figure 2 is a flow chart of a method for starting a reorganization timer provided by an exemplary embodiment of the present application;
[0027] Figure 3 is a schematic diagram of the structure of an RLC PDU provided by an exemplary embodiment of the present application;
[0028] Figure 4 is a flowchart of a configuration method provided by an exemplary embodiment of the present application;
[0029] Figure 5 is a flow chart of a method for starting a reorganization timer provided by an exemplary embodiment of the present application;
[0030] Figure 6 It is a time-frequency schematic diagram of a method for starting a reorganization timer provided by an exemplary embodiment of the present application;
[0031] Figure 7 is a flow chart of a method for starting a reorganization timer provided by an exemplary embodiment of the present application;
[0032] Figure 8 It is a time-frequency schematic diagram of a method for starting a reorganization timer provided by an exemplary embodiment of the present application;
[0033] Fig. 9 is a block diagram of a device for starting a reorganization timer provided by an exemplary embodiment of the present application;
[0034] Fig.10 is a block diagram of a configuration device provided by an exemplary embodiment of the present application;
[0035] Fig.11 It is a structural diagram of a communication device provided by an exemplary embodiment of the present application. DETAILED DESCRIPTION
[0036] In order to make the objectives, technical solutions and advantages of the present application clearer, the implementation methods of the present application will be further described in detail below with reference to the accompanying drawings.
[0037] Non Terrestrial Network (NTN)
[0038] At present, 3GPP is studying NTN technology, which generally uses satellite communication to provide communication services to ground users. Compared with ground cellular network communication, satellite communication has many unique advantages. First, satellite communication is not limited by the user's geographical location. For example, general land communication cannot cover areas such as oceans, mountains, deserts, etc. where communication equipment cannot be set up or where communication coverage is not provided due to sparse population. For satellite communication, since one satellite can cover a large area of land, and satellites can orbit the earth, in theory every corner of the earth can be covered by satellite communication. Secondly, satellite communication has great social value. Satellite communication can cover remote mountainous areas, poor and backward countries or regions at a low cost, so that people in these areas can enjoy advanced voice communication and mobile Internet technology, which is conducive to narrowing the digital divide with developed areas and promoting the development of these areas. Thirdly, satellite communication has a long distance, and the cost of communication does not increase significantly as the communication distance increases; finally, satellite communication has high stability and is not restricted by natural disasters.
[0039] According to the different orbital altitudes, communication satellites are divided into Low-Earth Orbit (LEO) satellites, Medium-Earth Orbit (MEO) satellites, Geostationary Earth Orbit (GEO) satellites, High Elliptical Orbit (HEO) satellites, etc. At the current stage, the main research is on LEO and GEO.
[0040] 1.LEO
[0041] The altitude of low-orbit satellites ranges from 500km to 1500km, and the corresponding orbital period is about 1.5 hours to 2 hours. The signal propagation delay of single-hop communication between users is generally less than 20ms. The maximum satellite visibility time is 20 minutes. The signal propagation distance is short, the link loss is small, and the transmission power requirement for user terminals is not high.
[0042] 2. GEO
[0043] The geosynchronous orbit satellite has an orbit altitude of 35786km and a rotation period around the earth of 24 hours. The signal propagation delay of single-hop communication between users is generally 250ms.
[0044] In order to ensure satellite coverage and improve the system capacity of the entire satellite communication system, satellites use multiple beams to cover the ground. A satellite can form dozens or even hundreds of beams to cover the ground; a satellite beam can cover a ground area with a diameter of tens to hundreds of kilometers.
[0045] New Radio Hybrid Automatic Repeat reQuest, NR HARQ) mechanism
[0046] NR has two levels of retransmission mechanisms: the HARQ mechanism of the Media Access Control (MAC) layer and the ARQ mechanism of the Radio Link Control (RLC) layer. The retransmission of lost or erroneous data is mainly handled by the HARQ mechanism of the MAC layer, supplemented by the retransmission function of the RLC layer. The HARQ mechanism of the MAC layer can provide fast retransmission, and the Automatic Repeat reQuest (ARQ) mechanism of the RLC layer can provide reliable data transmission.
[0047] HARQ uses a stop-and-wait protocol to send data. In the stop-and-wait protocol, after the transmitter sends a TB, it stops and waits for confirmation information. In this way, the transmitter stops and waits for confirmation after each transmission, which will result in very low user throughput. Therefore, NR uses multiple parallel HARQ processes. When a HARQ process is waiting for confirmation information, the transmitter can use another HARQ process to continue sending data. These HARQ processes together form a HARQ entity, which combines the stop-and-wait protocol to allow continuous data transmission. HARQ is divided into uplink HARQ and downlink HARQ. Uplink HARQ is for uplink data transmission, and downlink HARQ is for downlink data transmission. The two are independent of each other.
[0048] Based on the current NR protocol regulations, the terminal has its own HARQ entity for each service cell. Each HARQ entity maintains a set of parallel downlink HARQ processes and a set of parallel uplink HARQ processes. Currently, each uplink and downlink carrier supports a maximum of 16 HARQ processes. The base station can indicate the maximum number of HARQ processes to the UE through RRC signaling semi-static configuration based on the network deployment. If the network does not provide the corresponding configuration parameters, the default number of HARQ processes for the downlink is 8, and the maximum number of HARQ processes supported by each uplink carrier is always 16. Each HARQ process corresponds to a HARQ process ID. For the downlink, BCCH uses a dedicated broadcast HARQ process. For the uplink, Msg3 transmission in the random process uses HARQ ID 0.
[0049] For terminals that do not support downlink spatial division multiplexing, each downlink HARQ process can only process one transport block (TB) at a time; for terminals that support downlink spatial division multiplexing, each downlink HARQ process can process one or two TBs at a time. Each uplink HARQ process of the terminal processes one TB at a time.
[0050] HARQ is divided into two categories: synchronous and asynchronous in the time domain, and non-adaptive and adaptive in the frequency domain. NR uses asynchronous adaptive HARQ mechanism for both uplink and downlink. Asynchronous HARQ means that retransmission can occur at any time, and the time interval between the retransmission of the same TB and the previous transmission is not fixed. Adaptive HARQ means that the frequency domain resources and MCS used for retransmission can be changed.
[0051] NR RLC segmentation and reassembly of RLC service data unit (SDU) functions
[0052] Each logical channel of the UE has an RLC entity. An RLC entity can be configured in one of three modes: Transparent Mode (TM), Un-Acknowledged Mode (UM), and Acknowledged Mode (AM).
[0053] TM: corresponds to the TM RLC entity. This mode can be considered as an empty RLC because it only provides data transparent transmission.
[0054] UM: corresponds to the UM RLC entity. This mode provides all RLC functions except retransmission, resegmentation, duplicate packet detection, and protocol error detection, thus providing an unreliable transmission service.
[0055] AM: For AM RLC entities, this mode provides a reliable transmission service through error detection and retransmission. This mode supports all RLC functions.
[0056] For UM and AM, the segmentation and reassembly functions of RLC SDU can be supported. Since the resource size of each transmission is determined by the MAC scheduler, its size usually cannot completely match the size of the RLC SDU, so the RLC SDU needs to be segmented at the transmitting end so that it matches the size indicated by the MAC layer. Accordingly, the previously segmented RLC SDU needs to be reassembled at the receiving end in order to restore the original RLC SDU and submit it to the upper layer (PDCP layer).
[0057] Figure 1 The schematic diagram of an implementation environment provided by the embodiment of the present application is shown, and the implementation environment describes a satellite access network in the NTN technology. The implementation environment includes a terminal 01, a satellite 02, a gateway 03 and a core network 04.
[0058] In the NTN technology, there may be multiple terminals 01, and the multiple terminals 01 may all be connected to the satellite 02 for communication. Figure 1 Only one terminal 01 is schematically shown. In addition, there may be multiple satellites 02, and the multiple satellites 02 are connected via inter-satellite / aerial links (ISL). Figure 1 Only the situation of one satellite 02 is schematically shown.
[0059] In NTN technology, a terminal may also be referred to as an NTN terminal, which may be a terminal defined by 3GPP, or when a satellite does not directly serve a terminal defined by 3GPP, the NTN terminal may be a terminal specific to a satellite system. The terminal may be a user equipment (UE).
[0060] The terminal 01 and the satellite 02 are connected in communication via a service link, which refers to a radio link between the terminal 01 and the satellite 02. In addition, the terminal 01 may also support a wireless communication connection with a terrestrial access network.
[0061] Satellite 02 may also be referred to as a space / airborne platform, and may implement a bent pipe or regenerative payload configuration.
[0062] The gateway 03 is used to connect the satellite (or aviation access network) 02 and the core network. The gateway 03 and the satellite 02 are connected via feeder links.
[0063] In the implementation environment provided in the embodiment of the present application, the satellite 02 is used to connect the terminal 01 to the core network 04. Of course, other optional implementation environments may also include a base station, and the embodiment of the present application is not limited to this.
[0064] Figure 2 A flowchart of a method for starting a reorganization timer provided by an exemplary embodiment of the present application is shown. This embodiment is illustrated by taking the method being executed by a UE as an example. Optionally, the method is executed by an RLC entity in a UE as a receiver (referred to as a receiving UE). The method includes:
[0065] Step 202, receiving a first RLC PDU from the MAC layer, where the first RLC PDU corresponds to an RLC SDU segment;
[0066] The data received by the RLC entity from the PDCP layer or sent to the PDCP layer is called RLC SDU (or PDCP PDU). The data received by the RLC entity from the MAC layer or sent to the MAC layer is called RLC PDU (or MAC SDU).
[0067] When the UE as the sender (hereinafter referred to as the sending UE) does not segment the RLC SDU, one RLC PDU corresponds to one RLC SDU. When the sending UE segments the RLC SDU, one RLC PDU corresponds to one RLC SDU segment.
[0068] Exemplarily, the RLC PDU includes: an RLC header and an RLC SDU; or, an RLC header and an RLC SDU segment. Figure 3 As shown, it is assumed that the RLC SDU with SN=X is an unsegmented RLC SDU, and the RLC SDU with SN=X+1 is segmented into two segments, wherein RLC PDU 0=RLC header+RLC SDU, RLC PDU 1=RLC header+RLC SDU segment 1, and RLC PDU 2=RLC header+RLC SDU segment 2.
[0069] The RLC entity of the receiving UE receives a first RLC PDU from the MAC layer, where the first RLC PDU corresponds to an RLC SDU segment.
[0070] Step 204, when the first RLC PDU meets the first start condition of the reassembly offset timer and both the reassembly offset timer and the reassembly timer are not started, start the reassembly offset timer;
[0071] In this embodiment, in addition to the reassembly timer (t-Reassembly), a reassembly offset timer (t-Reassembly offset) is additionally set.
[0072] When the start condition is met and both the reorganization offset timer and the reorganization timer are not started, the reorganization offset timer is started first. Optionally, the first start condition includes at least one of the following conditions:
[0073] 1. At least one bit of the first RLC SDU corresponding to the first RLC PDU and located before the first RLC PDU has not been received;
[0074] For example, the first RLC SDU is divided into three RLC SDU segments, the first RLC PDU corresponds to RLC SDU segment 3, and RLC SDU segment 1 and RLC SDU segment 2 have not been received.
[0075] 2. There is at least one bit in the second RLC SDU preceding the first RLC SDU that has not been received.
[0076] For example, the first RLC SDU is an RLC SDU with SN=X, and an RLC SDU segment corresponding to the first RLC SDU has been received, but there is at least one bit in the RLC SDU with SN=X-1 that has not been received.
[0077] The timing duration of the reorganization offset timer is predefined by the communication protocol or preconfigured by the network device. The timing duration of the reorganization offset timer is greater than the round trip time (RTT), which is the RTT when the communication signal is transmitted between the terminal and the network device (satellite). When this embodiment is applied to the NTN scenario, the network device can be a satellite.
[0078] In some embodiments, the timing duration of the reorganization offset timer is greater than or equal to: RTT*max_HARQ_reTx_number, where max_HARQ_reTx_number is the maximum number of retransmissions corresponding to the HARQ mechanism of the MAC layer.
[0079] Step 206: When the reassembly offset timer times out, start the reassembly timer.
[0080] In summary, the method provided in this embodiment aims at the problem of long RTT between the terminal and the network device in the NTN system. By adding a reassembly offset timer, the reassembly waiting time of the RLC entity becomes the sum of the reassembly offset timer and the reassembly timer, thereby avoiding the problem that the reassembly waiting time of the RLC entity is too short and the RLC SDU cannot be received normally. This embodiment can provide the backward compatibility of the technical solution while keeping the original design architecture of the reassembly timer unchanged as much as possible.
[0081] Figure 4 A flowchart of a configuration method provided by an exemplary embodiment of the present application is shown. This embodiment is illustrated by taking the method being executed by a network device as an example. The network device may be a ground base station or a satellite base station. The method includes:
[0082] Step 402: The network device sends configuration information to the terminal, where the configuration information is used to configure the timing duration of the reorganization offset timer of the RLC entity;
[0083] Optionally, the configuration information is RRC configuration information. The reassembly offset timer is used together with the reassembly timer and is started before the reassembly timer.
[0084] The timing duration of the reassembly offset timer is greater than RTT, which is the RTT when the communication signal is transmitted between the terminal and the network device (satellite). When this embodiment is applied to the NTN scenario, the network device may be a satellite.
[0085] In some embodiments, the configuration information is a UE-level configuration, applicable to all wireless bearers within the UE; in other embodiments, the configuration information is a bearer-level configuration, applicable to specified wireless bearers within the UE, and the specified wireless bearers are part of all wireless bearers.
[0086] Step 404: The terminal receives configuration information sent by the network device.
[0087] The terminal configures the reorganization offset timer in the RLC entity according to the configuration information. Optionally, the terminal receives the RRC configuration information sent by the network device, extracts the timer duration from the RRC configuration information, and configures the reorganization offset timer in the RLC entity according to the timer duration.
[0088] In summary, the method provided in this embodiment is that the network device configures the timer length of the reassembly offset timer of the RLC entity to the terminal, and the terminal adds a reassembly offset timer with the timer length, so that the reassembly waiting time of the RLC entity becomes the sum of the reassembly offset timer and the reassembly timer, thereby avoiding the problem that the reassembly waiting time of the RLC entity is too short and the RLC SDU cannot be received normally. This embodiment can provide the backward compatibility of the technical solution while keeping the original design architecture of the reassembly timer unchanged as much as possible.
[0089] When the above method is executed by an RLC entity, it is applicable to the UM mode or the AM mode.
[0090] In UM mode, at least one of an uplink UM RLC sending entity and a downlink UM RLC receiving entity is set in the UE. The above method is executed by the downlink UM RLC receiving entity.
[0091] In the AM mode, an AM RLC entity is provided in the UE, and the AM RLC entity is divided into a sending side and a receiving side.
[0092] UM Mode:
[0093] Figure 5 A flowchart of a method for starting a reorganization timer provided by an exemplary embodiment of the present application is shown. This embodiment is illustrated by taking the method being executed by a UE (RLC entity) as an example. Optionally, the RLC entity in the UE includes: a downlink UM RLC receiving entity. The method includes:
[0094] Step 501, UE receives configuration information sent by a network device;
[0095] The configuration information is at least used to configure the timer duration of the reassembly offset timer in the RLC entity.
[0096] The network device sends RRC configuration information to the UE, where the RRC configuration information is used to configure the RLC function or the function of the RLC entity. The UE receives the RRC configuration information sent by the network device.
[0097] Step 502, the UE configures an RLC function for each radio bearer according to the configuration information;
[0098] The UE configures the RLC function for each radio bearer according to the RRC configuration information. This step includes at least one of the following sub-steps:
[0099] 1. Configure at least one radio bearer as a UM mode, where the UM mode includes: any one of a bidirectional UM mode and a unidirectional UM mode (downlink only);
[0100] 2. In bidirectional UM mode, one uplink UM RLC sending entity and one downlink UM RLC receiving entity are set in the radio bearer; in unidirectional UM mode, one downlink UM RLC receiving entity is set in the radio bearer. The UE sets the RLC reassembly timer t-Reassembly in the downlink UM RLC receiving entity.
[0101] 3. Set the RLC reassembly offset timer t-Reassembly offset in the downlink UM RLC receiving entity.
[0102] The configuration information carries the timer duration (or the start time offset of the reassembly timer). Optionally, the timer duration t-Reassembly offset>=RTT*max_HARQ_reTx_number. The RTT is the RTT when the communication signal is transmitted between the terminal and the network device (satellite). max_HARQ_reTx_number is the maximum number of retransmissions corresponding to the HARQ mechanism of the MAC layer.
[0103] In the case of UE-level configuration (applicable to all radio bearers), if a downlink UM RLC receiving entity is set in the radio bearer, the UE sets the RLC reassembly offset timer t-Reassemblyoffset for the downlink UM RLC receiving entity according to the timer duration. In the case of radio bearer-level configuration (applicable to specified radio bearers), if a downlink UM RLC receiving entity is set in the specified radio bearer, the UE sets the RLC reassembly offset timer t-Reassemblyoffset for the downlink UM RLC receiving entity according to the timer duration.
[0104] Step 503: The UE maintains three variables for each downlink UM RLC receiving entity:
[0105] The downlink UM RLC receiving entity has a function of grouping RLC SDUs. A reassembly receiving window is set in the downlink UM RLC receiving entity. Optionally, the downlink UM RLC receiving entity maintains the following three variables for the reassembly receiving window: a first variable, a second variable, and a third variable.
[0106] For example, the first variable is RX_Next_Highest, the second variable is RX_Next_Reassembly, and the third variable is RX_Timer_Trigger:
[0107] RX_Next_Highest is the next SN of the SN of the second RLC PDU with the largest SN among the received RLC PDUs. The initial value of this variable is 0.
[0108] RX_Timer_Trigger is the next SN of the SN that triggers the start of t-Reassembly offset (or t-Reassembly). The initial value of this variable is null. When t-Reassembly offset (or t-Reassembly) is started, it means that there are RLC PDUs smaller than this variable that have not been received, and it is necessary to wait for the PDUs to be reassembled.
[0109] RX_Next_Reassembly is the minimum SN in the reassembly receiving window. That is, the SN of the earliest RLC PDU currently waiting for reassembly in the reassembly receiving window. The initial value of this variable is 0, and the downlink UM RLC entity assumes by default that RLC SDUs with SNs less than this variable have been successfully received or discarded.
[0110] Step 504: (a certain) downlink UM RLC receiving entity in the UE receives a first RLC PDU from the MAC layer, where the first RLC PDU corresponds to an RLC SDU segment;
[0111] If the downlink UM RLC receiving entity receives an RLC PDU that does not include an SN, the RLC PDU corresponds to an unsegmented RLC SDU, and the RLC header of the RLC PDU is removed to obtain the RLC SDU, which is then sent to an upper layer.
[0112] If the downlink UM RLC receiving entity receives a UMD PDU from the MAC layer, and the header of the UMD PDU contains an SN, indicating that the UMD PDU corresponds to an RLC SDU segment, and the SN is greater than or equal to RX_Next_Reassembly, the received UMD PDU is placed in the receiving buffer.
[0113] SN is the sequence number of the segmented RLC SDU, and different RLC SDU segments have different SNs. When one RLC SDU is segmented into at least two RLC SDU segments, the at least two RLC SDU segments have the same SN. In addition, the at least two RLC SDU segments also have other information for identifying the segmentation sequence and the segmentation start position, and the other information is used to reassemble the at least two RLC SDU segments into an RLC SDU.
[0114] The UE performs at least one of steps 505 to 508:
[0115] Step 505: when both the reorganization offset timer and the reorganization timer are not running and any one of the following first starting conditions is met, the reorganization offset timer is started;
[0116] The first starting condition of the reorganization offset timer includes any one of the following two conditions:
[0117] Start condition 1: If RX_Next_Highest>RX_Next_Reassembly+1;
[0118] Start condition 2: if RX_Next_Highest=RX_Next_Reassembly+1, and for the first RLC SDU with SN equal to RX_Next_Reassembly, there is at least one unreceived bit segment before the last bit of the received first RLC SDU;
[0119] RX_Next_Highest is the next SN of the SN of the second RLC PDU with the largest SN in the received RLC PDU, and RX_Next_Reassembly is the minimum SN in the reassembly receiving window.
[0120] Step 506, when the reassembly offset timer times out, start the reassembly timer;
[0121] Step 507, when the reassembly timer times out and the following first start condition is met, the reassembly offset timer is started, and RX_Timer_Trigger is set to RX_Next_Highest;
[0122] When the reassembly timer times out, the downlink UM RLC receiving entity performs the following operations:
[0123] 1) Update RX_Next_Reassembly to the first SN that is not less than RX_Timer_Trigger and has not completed reassembly.
[0124] 2) discard all segments whose corresponding SN is smaller than the updated RX_Next_Reassembly;
[0125] 3) If any of the start conditions of the reassembly offset timer is met, t-Reassembly offset is started again and RX_Timer_Trigger is set to RX_Next_Highest.
[0126] Step 508: If the reorganization offset timer is running, then if any one of the following stop conditions is met, then the reorganization offset timer is stopped and reset; or, if the reorganization timer is running, then if any one of the following stop conditions is met, then the reorganization timer is stopped and reset.
[0127] The stop condition includes any one of the following three conditions:
[0128] Stop condition 1: If RX_Timer_Trigger <= RX_Next_Reassembly;
[0129] Stop condition 2: If RX_Timer_Trigger falls outside the reassembly receive window and RX_Timer_Trigger is not equal to RX_Next_Highest;
[0130] Stop condition 3: if RX_Next_Highest = RX_Next_Reassembly+1, and for the first RLC SDU corresponding to SN = RX_Next_Reassembly, there is no unreceived bit segment before the last bit of the received first RLC SDU;
[0131] Among them, RX_Next_Highest is the next SN of the SN of the third RLC PDU with the largest SN in the received RLC PDU, RX_Timer_Trigger is the next SN of the SN that triggers the start of the reassembly offset timer, and RX_Next_Reassembly is the minimum SN in the reassembly receiving window.
[0132] In summary, the method provided in this embodiment, by adding a reassembly offset timer, makes the reassembly waiting time of the RLC entity become the sum of the reassembly offset timer and the reassembly timer, thereby avoiding the problem that the reassembly waiting time of the RLC entity is too short and the RLC SDU cannot be received normally. This embodiment can provide the backward compatibility of the technical solution while keeping the original design architecture of the reassembly timer unchanged as much as possible.
[0133] The method provided in this embodiment, for the UM receiving mode, also sets the start condition and stop condition of the reorganization offset timer, so that the reorganization offset timer can be reasonably started or closed, and improves the backward compatibility of the technical solution.
[0134] Combined with reference Figure 6 , it is assumed that the downlink UM RLC receiving entity maintains the following three variables for the reassembly receiving window: RX_Next_Reassembly, RX_Timer_Trigger and RX_Next_Highest are all in the initial state.
[0135] 1. The network device sends UMD PDU1 to the UE. The UE fails to receive the UMD PDU1 (SN=X) and feeds back a negative acknowledgement (NACK) to the network device.
[0136] 2. The network device sends UMD PDU2 to the UE. The UE successfully receives UMD PDU2 (SN=X) and sends an ACK to the network device. Since UMD PDU2 corresponds to segment 2 of RLC SDU n, SN of RLC SDU n=X. After the UE successfully receives UMDPDU2, it puts UMDPDU2 into the receiving buffer. The three state variables at this time are:
[0137] RX_Next_Highest=x+1, RN_Timer_Trigger=0, RX_Next_Reassembly=x.
[0138] Since RX_Next_Highest=RX_Next_Reassembly+1=x+1, and the RLC SDUn of SN=x has a segment 1 before UMD PDU2 that has not been received, the UE starts the reassembly offset timer t-Reassemblyoffset, and the reassembly offset timer t-Reassemblyoffset=3 RTTs.
[0139] At the same time, set RN_Timer_Trigger=RX_Next_Highest=x+1.
[0140] The three state variables at this time are:
[0141] RX_Next_Highest=x+1, RN_Timer_Trigger=x+1, RX_Next_Reassembly=x.
[0142] 3. The network device sends UMD PDU3 to the UE. The UE successfully receives UMD PDU3 and sends an ACK to the network device. Since UMD PDU3 corresponds to RLC SDU n+1, RLC SDU n+1 is an unsplit RLC SDU and does not have an SN. The three state variables at this time are:
[0143] RX_Next_Highest=x+1, RN_Timer_Trigger=x+1, RX_Next_Reassembly=x.
[0144] Since the reassembly offset timer t-Reassembly offset has been running, but the three stop conditions are not met, the reassembly offset timer t-Reassembly offset is kept running. At the same time, the RLC entity of the UE reports RLC SDUn+1 to the MAC layer entity.
[0145] 4. The network device sends UMD PDU4 to the UE. The UE successfully receives UMD PDU4 (SN=X+1) and sends an ACK to the network device. Since UMD PDU4 corresponds to segment 1 of RLC SDU n+2, the SN of RLC SDU n+2 is X+1. The three state variables at this time are:
[0146] RX_Next_Highest=x+2, RN_Timer_Trigger=x+1, RX_Next_Reassembly=x.
[0147] Since the reassembly offset timer t-Reassembly offset has been running, but the three stop conditions are not met, the reassembly offset timer t-Reassembly offset is kept running. Meanwhile, UMD PDU2 and UMD PDU 4 are buffered in the reassembly receiving window waiting for reassembly.
[0148] 5. The network device sends UMD PDU5 to the UE. The UE successfully receives UMD PDU5 (SN=X+1) and sends an ACK to the network device. Since UMD PDU5 corresponds to segment 1 of RLC SDU n+2, the SN of RLC SDU n+2 is X+1. The three state variables at this time are:
[0149] RX_Next_Highest=x+2, RN_Timer_Trigger=x+1, RX_Next_Reassembly=x.
[0150] Since the reassembly offset timer t-Reassembly offset has been running, but none of the three stop conditions are met, the reassembly offset timer t-Reassembly offset continues to run. At the same time, the two segments in UMD PDU4 and UMD PDU 5 are reassembled into RLC SDU n+2, and the UE's RLC entity reports RLC SDUn+2 to the MAC layer entity. UMD PDU2 is buffered in the reassembly receiving window waiting for reassembly.
[0151] 6. The network device sends UMD PDU1 to the UE again. The UE fails to receive UMD PDU1 (SN=X) and sends a negative response (NACK) to the network device. Since UMD PDU1 corresponds to segment 1 of RLC SDU n, SN of RLC SDU n=X. The three state variables at this time are:
[0152] RX_Next_Highest=x+2, RN_Timer_Trigger=x+1, RX_Next_Reassembly=x.
[0153] Since RX_Next_Highest>RX_Next_Reassembly+1 and the reassembly offset timer t-Reassembly offset is running, t-Reassembly offset continues to run.
[0154] 7. The network device sends UMD PDU1 to the UE again. The UE fails to receive UMD PDU1 (SN=X) and sends a negative response (NACK) to the network device. Since UMD PDU1 corresponds to segment 1 of RLC SDU n, SN of RLC SDU n=X. The three state variables at this time are:
[0155] RX_Next_Highest=x+2, RN_Timer_Trigger=x+1, RX_Next_Reassembly=x.
[0156] Since RX_Next_Highest>RX_Next_Reassembly+1 and the timer duration of the reassembly offset timer t-Reassembly offset times out, the UE continues to start the reassembly timer t-Reassembly to run.
[0157] 8. When the reassembly timer t-Reassembly times out, RX_Next_Reassembly is updated to the first SN that is not less than RX_Timer_Trigger and has not yet completed reassembly, that is, x+3. All segments whose corresponding SN is less than the updated RX_Next_Reassembly=x+3 are discarded, that is, UMD PDU2. Since any of the first start conditions of the reassembly offset timer is no longer met, t-Reassembly offset is no longer started.
[0158] The above embodiment can be expressed as follows:
[0159] Behavior when a UMD PDU is in the receive buffer
[0160] When a UMD PDU with SN=x is in the receive buffer, the UM RLC receiving entity shall:
[0161] 1. If all bit fields of SN=x are received:
[0162] - Reassemble the RLC SDU from all bit fields of SN=X, remove the RLC header and submit the reassembled RLC SDU to higher layers.
[0163] - If x=RX_Next_Reassembly, then update RX_Next_Reassembly to: the next SN of the first SN that failed to reassemble and submit to the upper layer, and the first SN is the current RX_Next_Reassembly.
[0164] 2. Otherwise, if x is outside the reassembly receiving window, update RX_Next_Highest to x+1 and discard all UMDPDUs outside the reassembly receiving window;
[0165] If RX_Next_Reassembly falls outside the reassembly receiving window, RX_Next_Reassembly is updated to: the next SN of the second SN that cannot be reassembled and submitted to the higher layer, and the second SN is (RX_Next_Highest-UM_Window_Size).
[0166] 3. If the reassembly timer is running, or if the reassembly offset timer has been configured and the reassembly offset timer is running:
[0167] If RX_Timer_Trigger <= RX_Next_Reassembly; or,
[0168] If RX_Timer_Trigger is outside the reassembly receive window and RX_Timer_Trigger is not equal to RX_Next_Highest; or,
[0169] If RX_Next_Highest=RX_Next_Reassembly+1, and for the RLC SDU with SN=RX_Next_Reassembly, all bit fields before the last bit of the RLC SDU currently being received have been received.
[0170] Stop and reset the reassembly timer (if the reassembly timer is running), or, stop and reset the reassembly offset timer (if the reassembly offset timer is running),
[0171] 4. If the reassembly offset timer is not running and the reassembly timer is not running (including the case where the reassembly offset timer or the reassembly timer is stopped due to the above reasons), then if any of the following two conditions are met, the reassembly offset timer is started and RX_Timer_Trigger is set to RX_Next_Highest.
[0172] Condition 1: If RX_Next_Highest>RX_Next_Reassembly+1;
[0173] Condition 2: If RX_Next_Highest = RX_Next_Reassembly + 1 and for the RLC SDU corresponding to SN = RX_Next_Reassembly, there is at least one unreceived Byte segment before the last bit of the currently received RLC SDU;
[0174] If a reassembly offset timer is configured, start the reassembly offset timer; otherwise, start the reassembly timer. Set RX_Timer_Trigger to RX_Next_Highest.
[0175] When the reassembly offset timer times out, the reassembly timer is started.
[0176] Behavior when the reassembly timer expires:
[0177] If the reassembly timer times out, the downlink UM RLC receiving entity performs the following operations:
[0178] Update RX_Next_Reassembly to the first SN that is not less than RX_Timer_Trigger and has not yet completed reassembly.
[0179] Discard all segments whose corresponding SN is smaller than the updated RX_Next_Reassembly;
[0180] If any of the following two conditions are met:
[0181] -Condition 1: RX_Next_Highest>RX_Next_Reassembly+1;
[0182] - Condition 2: If RX_Next_Highest = RX_Next_Reassembly + 1 and for the RLC SDU corresponding to SN = RX_Next_Reassembly, there is at least one unreceived Byte segment before the last Byte in the currently received segment of the RLC SDU;
[0183] If a reassembly offset timer is configured, the reassembly offset timer is started and RX_Timer_Trigger is set to RX_Next_Highest.
[0184] AM mode:
[0185] Figure 7 A flowchart of a method for starting a reorganization timer provided by an exemplary embodiment of the present application is shown. This embodiment is illustrated by taking the method being executed by a UE (RLC entity) as an example. Optionally, the RLC entity in the UE includes: a downlink AM RLC entity or a receiving side of a downlink AM RLC entity. The method includes:
[0186] Step 701, the UE receives configuration information sent by the network device;
[0187] The configuration information is at least used to configure the timer duration of the reassembly offset timer in the RLC entity.
[0188] The network device sends RRC configuration information to the UE, where the RRC configuration information is used to configure the RLC function or the function of the RLC entity. The UE receives the RRC configuration information sent by the network device.
[0189] Step 702, the UE configures an RLC function for each radio bearer according to the configuration information;
[0190] The UE configures the RLC function for each radio bearer according to the RRC configuration information. This step includes at least one of the following sub-steps:
[0191] 1. Configure at least one radio bearer to AM mode;
[0192] 2. In AM mode, one uplink AM RLC entity and one downlink AM RLC entity are set in the radio bearer. The UE sets the RLC reassembly timer t-Reassembly in the downlink UM RLC receiving entity.
[0193] 3. Set the RLC reassembly offset timer t-Reassembly offset in the downlink AM RLC entity.
[0194] The configuration information carries the timer duration (or the start time offset of the reassembly timer). Optionally, the timer duration t-Reassembly offset>=RTT*max_HARQ_reTx_number. The RTT is the RTT when the communication signal is transmitted between the terminal and the network device (satellite). max_HARQ_reTx_number is the maximum number of retransmissions corresponding to the HARQ mechanism of the MAC layer.
[0195] In the case of UE-level configuration (applicable to all radio bearers), if a downlink AM RLC entity is set in the radio bearer, the UE sets the RLC reassembly offset timer t-Reassemblyoffset for the downlink AM RLC entity according to the timer duration. In the case of radio bearer-level configuration (applicable to specified radio bearers), if a downlink AM RLC entity is set in the specified radio bearer, the UE sets the RLC reassembly offset timer t-Reassemblyoffset for the downlink AM RLC entity according to the timer duration.
[0196] Step 703: The UE maintains three variables for each downlink AM RLC entity:
[0197] The downlink AM RLC entity has a group reassembly function of RLC SDU. A reassembly receiving window is set in the downlink AM RLC entity. Optionally, the downlink AM RLC entity maintains the following four variables for the reassembly receiving window: a first variable, a fourth variable, a fifth variable and a sixth variable.
[0198] Take the first variable as RX_Next_Highest, the fourth variable as RX_Next, the fifth variable as RX_Highest_Status, and the seventh variable as RX_Next_Status_Trigger as an example:
[0199] RX_Next is the next SN of the last RLC SDU received completely in sequence;
[0200] RX_Next_Highest is the next SN of the SN of the third RLC PDU with the largest SN among the received RLC PDUs;
[0201] RX_Next_Status_Trigger is the next SN of the SN that triggers the start of the reassembly timer;
[0202] RX_Highest_Status is the largest SN among all SNs indicated as ACK_SN to the higher layer.
[0203] Step 704: a (certain) downlink AM RLC entity in the UE receives a first RLC PDU from the MAC layer, where the first RLC PDU corresponds to an RLC SDU segment;
[0204] If the downlink AM RLC entity receives an RLC PDU that corresponds to an RLC SDU, the RLC header of the RLC PDU is removed to obtain the RLC SDU, and the RLC SDU is sent to the upper layer.
[0205] If the downlink AM RLC entity receives a UMD PDU from the MAC layer, and the UMD PDU corresponds to an RLC SDU segment, and the SN is greater than or equal to RX_Next_Reassembly, the received UMD PDU is placed in the receiving buffer.
[0206] SN is a sequence number of an RLC SDU, and different RLC SDUs have different SNs. When an RLC SDU is segmented into at least two RLC SDU segments, the at least two RLC SDU segments have the same SN. In addition, the at least two RLC SDU segments also have other information for identifying the segmentation sequence and the segmentation start position, and the other information is used to reassemble the at least two RLC SDU segments into an RLC SDU.
[0207] The UE performs at least one of steps 705 to 708:
[0208] Step 705: when both the reorganization offset timer and the reorganization timer are not running and any one of the following first starting conditions is met, the reorganization offset timer is started;
[0209] The first starting condition of the reorganization offset timer includes any one of the following two conditions:
[0210] Start condition 1: If RX_Next_Highest>RX_Next+1;
[0211] Start condition 2: if RX_Next_Highest = RX_Next + 1, and for the first RLC SDU corresponding to SN = RX_Next, there is at least one unreceived bit segment before the last bit in the segment of the received first RLC SDU;
[0212] Among them, RX_Next_Highest is the next SN of the SN of the third RLC PDU with the largest SN in the received RLC PDU, and RX_Next is the next SN of the last RLC SDU received completely in sequence.
[0213] Step 706, when the reassembly offset timer times out, start the reassembly timer;
[0214] Step 707: When the reassembly timer times out and the following second start condition is met, the reassembly offset timer is started, and RX_Next_Status_Trigger is set to RX_Next_Highest;
[0215] When the reassembly timer times out, the downlink AM RLC entity performs the following operations:
[0216] 1) Update RX_Highest_Status to the SN corresponding to the first RLC SDU that is not less than RX_Next_Status_Trigger and has not received all bytes;
[0217] 2) If any of the following second start conditions is met, t-Reassembly offset is started and RX_Next_Status_Trigger is set to RX_Next_Highest.
[0218] Condition 1: If RX_Next_Highest>RX_Highest_Status+1;
[0219] Condition 2: If RX_Next_Highest=RX_Highest_Status+1 and for the fourth RLC SDU corresponding to SN=RX_Highest_Status, there is at least one unreceived bit segment before the last bit in the segment of the received fourth RLC SDU.
[0220] Step 708: If the reorganization offset timer is running, then if any one of the following stop conditions is met, then the reorganization offset timer is stopped and reset; or, if the reorganization timer is running, then if any one of the following stop conditions is met, then the reorganization timer is stopped and reset.
[0221] If the reassembly timer t-Reassembly is running, or if the reassembly offset timer t-Reassemblyoffset is running, if any of the following three stop conditions is met, the running t-Reassembly offset is stopped and reset (if t-Reassembly offset is running), and the running t-Reassembly is stopped and reset (if t-Reassembly is running).
[0222] Stop condition 1: if RX_Next_Status_Trigger = RX_Next;
[0223] Stop condition 2: if RX_Next_Status_Trigger=RX_Next+1, and for the first RLC SDU corresponding to SN=RX_Next, there is no unreceived bit segment before the last bit in the segment of the currently received first RLC SDU;
[0224] Stop condition 3: RX_Next_Status_Trigger is outside the reassembly receive window and RX_Next_Status_Trigger is not equal to RX_Next + AM_Window_Size. AM_Window_Size is the downlink receive window length of the downlink AM RLC entity.
[0225] In summary, the method provided in this embodiment, by adding a reorganization offset timer, makes the reorganization waiting time of the RLC entity become the sum of the reorganization offset timer and the reorganization timer, thereby avoiding the problem that the reorganization waiting time of the RLC entity is too short and the RLC status report request RLC retransmission cannot be triggered normally. This embodiment can provide the backward compatibility of the technical solution while keeping the original design architecture of the reorganization timer unchanged as much as possible.
[0226] The method provided in this embodiment, for the UM receiving mode, also sets the start condition and stop condition of the reorganization offset timer, so that the reorganization offset timer can be reasonably started or closed, and improves the backward compatibility of the technical solution.
[0227] Combined with reference Figure 8 In an illustrative example, it is assumed that the downlink AM RLC entity maintains the following three variables for the reorganized receive window: the following four variables: RX_Next, RX_Next_Status_Trigger, RX_Highest_Status and RX_Next_Highest;
[0228] 1. The network device sends AMD PDU1 to the UE. The UE fails to receive AMD PDU1 (SN=X) and feeds back a negative acknowledgement (NACK) to the network device.
[0229] 2. The network device sends AMD PDU2 to the UE. The UE successfully receives AMD PDU2 (SN=X) and sends an ACK to the network device. Since AMD PDU2 corresponds to segment 2 of RLC SDU n, SN of RLC SDU n=X. After successfully receiving AMD PDU2,
[0230] RX_Next_Highest=x+1, RX_Next_Status_Trigger=0, RX_Next=x.
[0231] Since RX_Next_Highest=RX_Next+1=x+1, and segment 1 of RLC SDUn of SN=x is not received, the UE starts the reassembly offset timer t-Reassemblyoffset=3 RTTs. At the same time, RX_Next_Status_Trigger=RX_Next_Highest=x+1 is set.
[0232] The state variables at this time are:
[0233] RX_Next_Highest=x+1, RX_Next_Status_Trigger=x+1, RX_Next=x.
[0234] Since the reassembly offset timer t-Reassembly offset has been running, but the three stop conditions are not met, the reassembly offset timer t-Reassembly offset is kept running. Meanwhile, AMD PDU2 is buffered in the reassembly receiving window and waits for reassembly.
[0235] 3. The network device sends AMD PDU3 to the UE. The UE successfully receives AMD PDU3 and sends an ACK to the network device. Since AMD PDU3 corresponds to RLC SDU n+1, RLC SDU n+1 is an unsplit RLC SDU and does not have an SN. The state variables at this time are:
[0236] RX_Next_Highest=x+1, RX_Next_Status_Trigger=x+1, RX_Next=x.
[0237] Since the reassembly offset timer t-Reassembly offset has been running, but the three stop conditions are not met, the reassembly offset timer t-Reassembly offset is kept running. At the same time, the RLC entity of the UE reports RLC SDUn+1 to the MAC layer entity.
[0238] 4. The network device sends AMD PDU4 to the UE. The UE successfully receives AMD PDU4 (SN=X+1) and sends an ACK to the network device. Since AMD PDU4 corresponds to segment 1 of RLC SDU n+2, the SN of RLC SDU n+2 is X+1. The state variables at this time are:
[0239] RX_Next_Highest=x+2, RX_Next_Status_Trigger=x+1, RX_Next=x.
[0240] Since the reassembly offset timer t-Reassembly offset has been running, but the three stop conditions are not met, the reassembly offset timer t-Reassembly offset is kept running. Meanwhile, AMD PDU2 and AMD PDU 4 are buffered in the reassembly receiving window waiting for reassembly.
[0241] 5. The network device sends AMD PDU5 to the UE. The UE successfully receives AMD PDU5 (SN=X+1) and sends an ACK to the network device. Since AMD PDU5 corresponds to segment 1 of RLC SDU n+2, the SN of RLC SDU n+2 is X+1. The state variables at this time are:
[0242] RX_Next_Highest=x+2, RX_Next_Status_Trigger=x+1, RX_Next=x.
[0243] Since the reassembly offset timer t-Reassembly offset has been running, but none of the three stop conditions are met, the reassembly offset timer t-Reassembly offset is kept running. At the same time, the two segments in AMD PDU4 and AMD PDU 5 are reassembled into RLC SDU n+2, and the RLC entity of the UE reports RLC SDUn+2 to the MAC layer entity. AMD PDU2 is buffered in the reassembly receiving window waiting for reassembly.
[0244] 6. The network device sends AMD PDU1 to the UE again. The UE fails to receive AMD PDU1 (SN=X) and sends a negative response (NACK) to the network device. Since AMD PDU1 corresponds to segment 1 of RLC SDU n, SN of RLC SDU n=X. The state variables at this time are:
[0245] RX_Next_Highest=x+2, RX_Next_Status_Trigger=x+1, RX_Next=x.
[0246] Since RX_Next_Highest>RX_Next+1 and the reassembly offset timer t-Reassembly offset is running, t-Reassembly offset continues to run.
[0247] 7. The network device sends AMD PDU1 to the UE again. The UE fails to receive AMD PDU1 (SN=X) and sends a negative response (NACK) to the network device. Since AMD PDU1 corresponds to segment 1 of RLC SDU n, SN of RLC SDU n=X. The state variables at this time are:
[0248] RX_Next_Highest=x+2, RX_Next_Status_Trigger=x+1, RX_Next=x.
[0249] Since RX_Next_Highest>RX_Next+1 and the timer duration of the reassembly offset timer t-Reassembly offset times out, the UE continues to start the reassembly timer t-Reassembly to run.
[0250] 8. When the reassembly timer t-Reassembly times out, RX_Highest_status is updated to the SN of the first RLC SDU that is not less than RX_TNext_Status_Trigger and has not received all bits, triggering a status report. Since any of the start conditions of the reassembly offset timer is no longer met, t-Reassemblyoffset is no longer started.
[0251] The above embodiment can be expressed as follows:
[0252] Behavior when an AMD PDU is in the receive buffer
[0253] When a UMD PDU with SN=x is in the receive buffer, the AM RLC entity shall:
[0254] if x>=RX_Next_Highest;
[0255] - Update RX_Next_Highest to x+1.
[0256] If all bit fields of the RLC SDU with SN=x have been received:
[0257] - reassemble the RLC SDU from the AMD PDU with SN=x, remove the RLC header and submit the reassembled RLC SDU to the upper layer;
[0258] - if x = RX_Highest_Status,
[0259] -Update RX_Highest_Status to the third SN, which is the next SN of the current RX_Highest_Status corresponding to the RLC SDU for which all bits have not been received.
[0260] -if x=RX_Next:
[0261] -Update RX_Next to the fourth SN, which is the next SN of the current RX_Next corresponding to the RLC SDU that has not received all bits.
[0262] If the reassembly timer is running, or if the reassembly offset timer is running, if any of the following three conditions are met, stop and reset the running reassembly offset timer (if the reassembly offset timer is running), stop and reset the running reassembly timer (if the reassembly timer is running).
[0263] Condition 1: If RX_Next_Status_Trigger = RX_Next;
[0264] Condition 2: If RX_Next_Status_Trigger=RX_Next+1, and for the first RLC SDU corresponding to SN=RX_Next, there is no unreceived bit segment before the last bit in the segment of the currently received first RLC SDU;
[0265] Condition 3: RX_Next_Status_Trigger is outside the reassembly receive window and RX_Next_Status_Trigger is not equal to RX_Next+AM_Window_Size;
[0266] If the reassembly offset timer is not running and the reassembly timer is not running (including the case where the reassembly offset timer or the reassembly timer is stopped due to the above reasons), then if any of the following two conditions are met.
[0267] Condition 1: If RX_Next_Highest>RX_Next+1;
[0268] Condition 2: If RX_Next_Highest = RX_Next + 1, and for the first RLC SDU corresponding to SN = RX_Next, there is at least one unreceived bit segment before the last bit in the segment of the received first RLC SDU;
[0269] If a reassembly offset timer is configured, start the reassembly offset timer; otherwise, start the reassembly timer. Set RX_Next_Status_Trigger to RX_Next_Highest at the same time.
[0270] When the reassembly offset timer times out, the reassembly timer is started.
[0271] Behavior when the reassembly timer expires:
[0272] If the reassembly timer expires, the AM RLC entity performs the following operations:
[0273] Update RX_Highest_Status to the SN corresponding to the first RLC SDU that is not less than RX_Next_Status_Trigger and for which all bits have not been received;
[0274] If any of the following two conditions are met:
[0275] Condition 1: If RX_Next_Highest>RX_Highest_Status+1;
[0276] Condition 2: If RX_Next_Highest=RX_Highest_Status+1 and for the RLC SDU corresponding to SN=RX_Highest_Status, there is at least one unreceived bit segment before the last bit in the segment of the currently received RLC SDU.
[0277] If a reassembly offset timer is configured, the reassembly offset timer is started and RX_Next_Status_Trigger is set to RX_Next_Highest.
[0278] Fig. 9 A block diagram of a device for starting a reorganization timer provided by an exemplary embodiment of the present application is shown. The device can be implemented as a terminal or a part of a terminal, and the device includes:
[0279] A receiving module 920 is configured to receive a first RLC PDU from a MAC layer, where the first RLC PDU corresponds to an RLC SDU segment;
[0280] The timer module 940 is used to start the reorganization offset timer when the first RLC PDU meets the first start condition of the reorganization offset timer and both the reorganization offset timer and the reorganization timer are not started; and start the reorganization timer when the reorganization offset timer times out.
[0281] In a possible implementation of this embodiment, the first starting condition includes any one of the following two conditions:
[0282] There is at least one bit in a second RLC SDU preceding the first RLC SDU that has not been received;
[0283] At least one bit of a first RLC SDU corresponding to the first RLC PDU and located before the first RLC PDU has not been received.
[0284] In a possible implementation of this embodiment, the RLC entity includes a downlink unacknowledged mode radio link control UM RLC receiving entity, and the downlink UM RLC receiving entity maintains a first variable and a second variable for the reorganization receiving window;
[0285] The first starting condition includes any one of the following two conditions:
[0286] If the first variable>the second variable+1;
[0287] If the first variable=the second variable+1, and for a first RLC SDU having a sequence number SN equal to the second variable, there is at least one unreceived bit segment before the last bit of the received first RLC SDU;
[0288] The first variable is the next SN of the SN of the third RLC PDU with the largest SN in the received RLC PDUs, and the second variable is the minimum SN in the reassembly receiving window.
[0289] In a possible implementation of this embodiment, the first variable is RX_Next_Highest, and the second variable is RX_Next_Reassembly.
[0290] In a possible implementation of this embodiment, the timer module 940 is further configured to restart the reassembly offset timer when the reassembly timer times out and the first start condition is met.
[0291] In a possible implementation of this embodiment, the timer module 940 is further configured to stop and reset the reorganization offset timer when the reorganization offset timer is running and a stop condition is met.
[0292] In a possible implementation of this embodiment, the RLC entity includes a downlink unacknowledged mode radio link control UM RLC receiving entity, and the downlink UM RLC receiving entity maintains a first variable, a second variable and a third variable for the reorganization receiving window;
[0293] The stop condition includes any one of the following three conditions:
[0294] If the third variable <= the second variable;
[0295] If the third variable falls outside the recombination receiving window, and the third variable is not equal to the first variable;
[0296] The first variable=the second variable+1, and for the first RLC SDU corresponding to the sequence number SN=the second variable, there is no unreceived bit segment before the last bit of the received first RLC SDU;
[0297] Among them, the first variable is the next SN of the SN of the second RLC PDU with the largest SN corresponding to the received RLC PDU, the third variable is the next SN of the SN that triggers the start of the reorganization offset timer, and the second variable is the minimum SN in the reorganization receiving window.
[0298] In a possible implementation of this embodiment, the first variable is RX_Next_Highest, the second variable is RX_Next_Reassembly, and the third variable is RX_Timer_Trigger.
[0299] In a possible implementation of this embodiment, the RLC entity includes a downlink acknowledged mode radio link control AM RLC entity, and the downlink AM RLC entity maintains a first variable and a fourth variable for the reorganized receiving window;
[0300] The first starting condition includes any one of the following two conditions:
[0301] If the first variable>the fourth variable+1;
[0302] If the first variable=the fourth variable+1, and for the first RLC SDU corresponding to the sequence number SN=the fourth variable, there is at least one unreceived bit segment before the last bit in the segment of the first RLC SDU that has been received;
[0303] The first variable is the next SN of the SN of the third RLC PDU with the largest SN in the received RLC PDUs, and the fourth variable is the next SN of the last RLC SDU completely received in sequence.
[0304] In a possible implementation of this embodiment, the first variable is RX_Next_Highest, and the fourth variable is RX_Next.
[0305] In a possible implementation of this embodiment, the RLC entity includes a downlink acknowledged mode radio link control AM RLC entity, and the downlink AM RLC entity maintains a first variable and a fifth variable for the reorganized receiving window;
[0306] The device also includes:
[0307] When the reassembly timer times out and a second start condition is met, starting the reassembly offset timer;
[0308] The second starting condition includes any one of the following two conditions:
[0309] If the first variable>the fifth variable+1;
[0310] If the first variable=the fifth variable+1, and for a fourth RLC SDU corresponding to a sequence number SN=the fifth variable, there is at least one unreceived bit segment before the last bit in the received segment of the fourth RLC SDU;
[0311] The first variable is the next SN of the SN of the third RLC PDU with the largest SN in the received RLC PDU, and the fifth variable is the largest SN among all SNs indicated as ACK_SN to the upper layer.
[0312] In a possible implementation of this embodiment, the first variable is RX_Next_Highest, and the fifth variable is RX_Highest_Status.
[0313] In a possible implementation of this embodiment, the timer module 940 is further configured to stop and reset the reorganization offset timer when the reorganization offset timer is running and a stop condition is met.
[0314] In a possible implementation of this embodiment, the RLC entity includes a downlink acknowledged mode radio link control AM RLC entity, and the downlink AM RLC entity maintains a fourth variable and a sixth variable for the reorganization receiving window; and the stop condition includes any one of the following three conditions:
[0315] If the sixth variable = the fourth variable;
[0316] If the sixth variable=the fourth variable+1, and for the first RLC SDU corresponding to the sequence number SN=the fourth variable, there is no unreceived bit segment before the last bit in the segment of the received first RLC SDU;
[0317] If the sixth variable is outside the recombination receiving window, and the sixth variable is not equal to the fourth variable plus the seventh variable;
[0318] Among them, the sixth variable is the next SN of the SN that triggers the start of the reassembly offset timer, the fourth variable is the next SN of the last RLC SDU received completely in sequence, and the seventh variable is the downlink receiving window length of the downlink AM RLC entity.
[0319] In a possible implementation of this embodiment, the fourth variable is RX_Next, the sixth variable is RX_Next_Status_Trigger, and the seventh variable is AM_Window_Size.
[0320] In a possible implementation of this embodiment, the receiving module 920 is used to receive configuration information, where the configuration information is used to configure the timer duration of the reorganization offset timer of the RLC entity.
[0321] In a possible implementation of this embodiment, the timer length of the reorganization offset timer is greater than the round-trip transmission time RTT, where the RTT is the round-trip transmission time when data is transmitted between the terminal and the network device.
[0322] In a possible implementation of this embodiment, the timer length of the reorganization offset timer is equal to the product of the round-trip transmission time RTT and the maximum number of retransmissions.
[0323] In a possible implementation of this embodiment, the configuration information is applicable to all radio bearers of the terminal; or, the configuration information is applicable to a specified radio bearer among all radio bearers of the terminal.
[0324] Fig.10 A block diagram of a configuration device provided by an exemplary embodiment of the present application is shown. The device can be implemented as a terminal or a part of a terminal, and the device includes:
[0325] The sending module 1020 is used to send configuration information to the terminal, where the configuration information is used to configure the timer length of the reorganization offset timer of the RLC entity.
[0326] In a possible implementation of this embodiment, the timer length of the reorganization offset timer is greater than the round-trip transmission time RTT, where the RTT is the round-trip transmission time when data is transmitted between the UE and the network device.
[0327] In a possible implementation of this embodiment, the timer length of the reorganization offset timer is equal to the product of the round-trip transmission time RTT and the maximum number of retransmissions.
[0328] In a possible implementation of this embodiment, the configuration information is applicable to all radio bearers of the UE; or, the configuration information is applicable to a specified radio bearer among all radio bearers of the UE.
[0329] Fig.11 A schematic diagram of the structure of a communication device (network device or terminal device) provided by an exemplary embodiment of the present application is shown. The communication device includes: a processor 101, a receiver 102, a transmitter 103, a memory 104 and a bus 105.
[0330] The processor 101 includes one or more processing cores. The processor 101 executes various functional applications and information processing by running software programs and modules.
[0331] The receiver 102 and the transmitter 103 may be implemented as a communication component, which may be a communication chip.
[0332] The memory 104 is connected to the processor 101 via a bus 105 .
[0333] The memory 104 may be used to store at least one instruction, and the processor 101 may be used to execute the at least one instruction to implement each step in the above method embodiment.
[0334] In addition, the memory 104 can be implemented by any type of volatile or non-volatile storage device or a combination thereof. The volatile or non-volatile storage device includes but is not limited to: a magnetic disk or an optical disk, an electrically erasable programmable read-only memory (EEPROM), an erasable programmable read-only memory (EPROM), a static random access memory (SRAM), a read-only memory (ROM), a magnetic memory, a flash memory, and a programmable read-only memory (PROM).
[0335] In an exemplary embodiment, a computer-readable storage medium is also provided, in which at least one instruction, at least one program, code set or instruction set is stored. The at least one instruction, the at least one program, the code set or instruction set is loaded and executed by the processor to implement the method for starting the reorganization timer executed by the terminal device or the configuration method executed by the network device provided in the above-mentioned various method embodiments.
[0336] A person skilled in the art will understand that all or part of the steps to implement the above embodiments may be accomplished by hardware or by instructing related hardware through a program, and the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a disk or an optical disk, etc.
[0337] The above description is only an optional embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application shall be included in the protection scope of the present application.
Claims
1. A method for starting a reorganization timer, It is characterized in that Used in a radio link control RLC entity, the method comprises: Receiving a first radio link control protocol data unit RLC PDU from a media access control MAC layer, wherein the first RLC PDU corresponds to a radio link control service data unit RLC SDU segment; When the first RLC PDU meets a first start condition of a reassembly offset timer and both the reassembly offset timer and the reassembly timer are not started, start the reassembly offset timer; When the reassembly offset timer times out, starting the reassembly timer; The first starting condition includes any one of the following two conditions: There is at least one bit in a second RLC SDU preceding the first RLC SDU that has not been received; At least one bit of a first RLC SDU corresponding to the first RLC PDU and located before the first RLC PDU has not been received; The method further comprises: When the reorganization offset timer is running and the following stop conditions are met, stop and reset the reorganization offset timer; The RLC entity includes a downlink acknowledged mode radio link control AM RLC entity, and the downlink AM RLC entity maintains a fourth variable and a sixth variable for the reorganized receiving window; and the stop condition includes any one of the following three conditions: If the sixth variable = the fourth variable; If the sixth variable=the fourth variable plus 1, and for the first RLC SDU corresponding to the sequence number SN=the fourth variable, there is no unreceived bit segment before the last bit in the segment of the received first RLC SDU; If the sixth variable is outside the recombination receiving window, and the sixth variable is not equal to the fourth variable plus the seventh variable; Among them, the sixth variable is the next SN of the SN that triggers the start of the reorganization offset timer, the fourth variable is the next SN of the last RLC SDU received completely in sequence, and the seventh variable is the downlink receiving window length of the downlink AM RLC entity.
2. The method according to claim 1, It is characterized in that The RLC entity comprises a downlink unacknowledged mode radio link control UM RLC receiving entity, and the downlink UM RLC receiving entity maintains a first variable and a second variable for a reorganized receiving window; The first starting condition includes any one of the following two conditions: If the first variable > the second variable + 1; If the first variable=the second variable+1, and for the first RLC SDU whose sequence number SN is equal to the second variable, there is at least one unreceived bit segment before the last bit of the received first RLC SDU; The first variable is the next SN of the SN of the third RLC PDU with the largest SN in the received RLC PDUs, and the second variable is the minimum SN in the reassembly receiving window.
3. The method according to claim 2, It is characterized in that The first variable is RX_Next_Highest and the second variable is RX_Next_Reassembly.
4. The method according to claim 1, It is characterized in that The method further comprises: When the reassembly timer times out and the first start condition is met, the reassembly offset timer is started again.
5. The method according to claim 1, It is characterized in that The RLC entity comprises a downlink acknowledged mode radio link control AM RLC entity, and the downlink AM RLC entity maintains a first variable and a fourth variable for the reorganized receiving window; The first starting condition includes any one of the following two conditions: If the first variable>the fourth variable+1; If the first variable=the fourth variable+1, and for a first RLC SDU corresponding to a sequence number SN=the fourth variable, there is at least one unreceived bit segment before the last bit in the segment of the first RLC SDU that has been received; The first variable is the next SN of the SN of the third RLC PDU with the largest SN in the received RLC PDUs, and the fourth variable is the next SN of the last RLC SDU completely received in sequence.
6. The method according to claim 5, It is characterized in that The first variable is RX_Next_Highest, and the fourth variable is RX_Next.
7. The method according to claim 1, It is characterized in that The RLC entity comprises a downlink acknowledged mode radio link control AM RLC entity, and the downlink AM RLC entity maintains a first variable and a fifth variable for the reorganized receiving window; The method further comprises: When the reassembly timer times out and the following second starting condition is met, starting the reassembly offset timer; The second starting condition includes any one of the following two conditions: If the first variable>the fifth variable+1; If the first variable=the fifth variable+1, and for a fourth RLC SDU corresponding to a sequence number SN=the fifth variable, there is at least one unreceived bit segment before the last bit in the received segment of the fourth RLC SDU; The first variable is the next SN of the SN of the third RLC PDU with the largest SN in the received RLC PDU, and the fifth variable is the largest SN among all SNs indicated as ACK_SN to the upper layer.
8. The method according to claim 7, It is characterized in that The first variable is RX_Next_Highest, and the fifth variable is RX_Highest_Status.
9. The method according to claim 1, It is characterized in that The sixth variable is RX_Next_Status_Trigger, the fourth variable is RX_Next, and the seventh variable is AM_Window_Size.
10. The method according to claim 1, It is characterized in that The method further comprises: Configuration information is received, where the configuration information is used to configure a timer duration of the reorganization offset timer of the RLC entity.
11. The method according to claim 10, It is characterized in that The timer duration of the reorganization offset timer is greater than the round-trip transmission time RTT, where the RTT is the round-trip transmission time when data is transmitted between the terminal and the network device.
12. The method according to claim 10, It is characterized in that The timer duration of the reorganization offset timer is equal to the product of the round-trip transmission time RTT and the maximum number of retransmissions.
13. The method according to claim 10, It is characterized in that The configuration information is applicable to all radio bearers of the terminal; or, The configuration information is applicable to a designated radio bearer among all radio bearers of the terminal.
14. An RLC entity device, It is characterized in that The device comprises: A receiving module, configured to receive a first radio link control protocol data unit RLC PDU from a media access control MAC layer, wherein the first RLC PDU corresponds to a radio link control service data unit RLC SDU segment; A timer module, configured to start the reorganization offset timer when the first RLC PDU meets the first start condition of the reorganization offset timer and both the reorganization offset timer and the reorganization timer are not started; and start the reorganization timer when the reorganization offset timer times out; The first starting condition includes any one of the following two conditions: There is at least one bit in a second RLC SDU preceding the first RLC SDU that has not been received; At least one bit of a first RLC SDU corresponding to the first RLC PDU and located before the first RLC PDU has not been received; The timer module is further configured to stop and reset the reorganization offset timer when the reorganization offset timer is running and a stop condition is met; The RLC entity includes a downlink acknowledged mode radio link control AM RLC entity, and the downlink AM RLC entity maintains a fourth variable and a sixth variable for the reorganized receiving window; and the stop condition includes any one of the following three conditions: If the sixth variable = the fourth variable; If the sixth variable=the fourth variable plus 1, and for the first RLC SDU corresponding to the sequence number SN=the fourth variable, there is no unreceived bit segment before the last bit in the segment of the received first RLC SDU; If the sixth variable is outside the recombination receiving window, and the sixth variable is not equal to the fourth variable plus the seventh variable; Among them, the sixth variable is the next SN of the SN that triggers the start of the reorganization offset timer, the fourth variable is the next SN of the last RLC SDU received completely in sequence, and the seventh variable is the downlink receiving window length of the downlink AM RLC entity.
15. A terminal, It is characterized in that The terminal comprises: processor; a transceiver connected to the processor; a memory for storing executable instructions for the processor; The processor is configured to load and execute the executable instructions to implement the method for starting a reorganization timer as claimed in any one of claims 1 to 13.
16. A computer-readable storage medium, It is characterized in that The readable storage medium stores executable instructions, and the executable instructions are loaded and executed by a processor to implement the method for starting a reorganization timer as claimed in any one of claims 1 to 13.
