Method and device used for wireless communication

Abstract

The invention discloses a method and a device used for wireless communication. The first node receives a sending opportunity notification from a lower layer of the first node at an RLC entity of the first node; when an AMD PDU to be transmitted comprises a first type of data units, adding 1 to the value of the first counter; if the value of the first counter is not smaller than a first threshold value, the AMD PDU comprises a polling indication, and the value of the first counter is set to be 0; the AMD PDU is submitted to the lower layer of the first node to be sent; wherein at least part of bytes included in the first type of data units are not sent previously, the at least part of bytes belong to a PDU set, and any byte included in the PDU set is not sent previously; the PDU set comprises at least one byte, and the PDU set bears an effective load of an information unit generated at an application level. According to the invention, the retransmission waiting time can be reduced, and the service quality is improved.

Description

Technical Field

[0001] The present application relates to a method and a device in a wireless communication system, and in particular to a method and a device for transmission at an RLC (Radio Link Control) protocol layer in wireless communication. Background Art

[0002] In the future, the application scenarios of wireless communication systems will become more and more diversified, and different application scenarios will put forward different performance requirements for the system. In order to meet the different performance requirements of various application scenarios, the 3rd Generation Partner Project (3GPP) RAN

[0003] At the 3GPP RAN (Radio Access Network) plenary meeting #72, it was decided to study the new air interface technology (NR, New Radio) (or 5G). At the 3GPP RAN plenary meeting #75, the WI (Work Item) of the new air interface technology (NR, New Radio) was passed, and the standardization work on NR began.

[0004] The RLC protocol layer is located between the PDCP (Packet Data Convergence Protocol) protocol layer and the MAC (Medium Access Control) protocol layer. It is used to implement functions such as sending upper-layer PDU (protocol data unit), segmentation and reassembly of RLC SDU (service data unit), and error correction through ARQ (Automatic Repeat Request).

[0005] Designing effective RLC functions for services with different transmission requirements is an important research direction in NR. Summary of the invention

[0006] Through research, the inventors found that some delay-sensitive services have a smaller data packet delay budget (delaybudget), and how to enhance the existing RLC protocol layer functions to adapt to these services needs to be studied. In response to the above problems, the present application discloses a solution. In the absence of conflict, the embodiments of the present application and the features in the embodiments can be combined with each other arbitrarily. Furthermore, although the original intention of the present application is for the RLC protocol layer, the present application can also be used to implement other protocol layers based on polling retransmission. The present application is applicable to Uu interface and PC5 interface. Furthermore, the present application is applicable to terminal and base station scenarios, V2X (Vehicle-to-Everything) scenarios, D2D

[0007] (Device-to-Device, device to device) scenarios, terminal and relay, and communication scenarios between relay and base station. The present application can be applied to a variety of wireless communication scenarios, such as XR (extended reality), eMBB (Enhanced Mobile Broadband), URLLC (Ultra-Reliable Low-Latency Communications), Internet of Vehicles, Internet of Things, NTN (Non-Terrestrial Networks), eMTC (enhanced Machine-Type Communication), etc., and achieve similar technical effects. In addition, the use of a unified solution for different scenarios (including but not limited to V2X scenarios and communication scenarios between terminals and base stations) can also help reduce hardware complexity and costs. In particular, the interpretation of terms (Terminology), nouns, functions, and variables in this application (if not otherwise specified) can refer to the definitions in the 3GPP specification protocols TS36 series, TS38 series, and TS37 series.

[0008] The present application discloses a method in a first node used for wireless communication, characterized by comprising:

[0009] Receiving, at the first node, a transmission opportunity notification from a lower layer of the first node;

[0010] When an AMD PDU to be transmitted includes a first type of data unit, increasing the value of the first counter by 1;

[0011] If the value of the first counter is not less than a first threshold, including a polling indication in the AMD PDU and setting the value of the first counter to 0;

[0012] Submitting the AMD PDU to the lower layer of the first node for sending;

[0013] Among them, at least some of the bytes included in the first type of data unit have not been sent before, and the at least some of the bytes belong to a PDU set, and any byte included in the PDU set has not been sent before; the PDU set includes at least one byte, and the PDU set carries the payload of an information unit generated at the application level.

[0014] As an embodiment, the first type of data unit includes the first batch of data sent for the first time in a PDU set.

[0015] As an embodiment, the above method can implement polling based on PDU set by updating the first counter through the first type of data unit.

[0016] As an embodiment, the above method can reduce the waiting time for retransmission of delay-sensitive services by updating the first counter through the first type of data units.

[0017] As an embodiment, the first counter is neither PDU_WITHOUT_POLL (protocol data unit not polled) nor BYTE_WITHOUT_POLL (byte not polled).

[0018] As an embodiment, the first counter is a counter other than PDU_WITHOUT_POLL and BYTE_WITHOUT_POLL.

[0019] As an embodiment, the PDU_WITHOUT_POLL determines whether to send a polling indication again by accumulating the number of PDUs sent since the last time a polling indication was sent.

[0020] As an embodiment, the BYTE_WITHOUT_POLL determines whether to send a polling indication again by accumulating the number of bytes sent since the last time a polling indication was sent.

[0021] As an embodiment, for some video or interactive services, a PDU set includes the content of a frame or a video slice at the application level. Since the number of PDUs included in each PDU set and the size of the PDU can vary greatly, if the existing polling trigger mechanism based on the number of PDUs or the number of bytes is used, several PDU sets may be sent before the polling is triggered; when there is a need for retransmission, a large delay will be caused, thereby causing damage to the service quality.

[0022] As an embodiment, the above method adds a condition for triggering polling through the first counter.

[0023] As an embodiment, the above method is applicable to services supporting PDU set.

[0024] As an embodiment, the above method enhances the RLC function to better support the PDU set-based services.

[0025] According to one aspect of the present application, it includes:

[0026] The RLC entity at the first node receives an RLC SDU and first information from an upper layer of the first node, wherein at least part of bytes included in the RLC SDU are used to generate the AMD PDU;

[0027] The first information indicates whether the PDU included in the RLC SDU is the first PDU to be sent in the PDU set, or the first information indicates the sequence number of the PDU included in the RLC SDU in the PDU set.

[0028] As an embodiment, the above method obtains PDU set related information through inter-layer interaction.

[0029] As an embodiment, the above method can simplify the protocol layer design.

[0030] According to one aspect of the present application, it includes:

[0031] The PDU set includes at least one PDU, and each PDU included in the PDU set corresponds to a PDCP SDU.

[0032] According to one aspect of the present application, it includes:

[0033] The polling indication is used by the RLC entity of the first node to request a status report from a peer RLC entity.

[0034] According to one aspect of the present application, it includes:

[0035] The RLC entity at the first node receives a status report from the opposite RLC entity, wherein the status report is a response to the polling indication;

[0036] The status report indicates at least one of an RLC SDU or an RLC SDU segment that has not been successfully received.

[0037] As an embodiment, an RLC SDU segment includes part of bytes in an RLC SDU.

[0038] The present application discloses a first node used for wireless communication, characterized in that it includes:

[0039] A first processor receives a transmission opportunity notification from a lower layer of the first node at an RLC entity of the first node; when an AMD PDU to be transmitted includes a first type of data unit, increases a value of a first counter by 1; if the value of the first counter is not less than a first threshold, includes a polling indication in the AMD PDU and sets the value of the first counter to 0; and delivers the AMD PDU to the lower layer of the first node for transmission;

[0040] Among them, at least some of the bytes included in the first type of data unit have not been sent before, and the at least some of the bytes belong to a PDU set, and any byte included in the PDU set has not been sent before; the PDU set includes at least one byte, and the PDU set carries the payload of an information unit generated at the application level.

[0041] According to one aspect of the present application, it includes:

[0042] The first processor receives, at the RLC entity of the first node, an RLC SDU and first information from an upper layer of the first node, wherein at least part of bytes included in the RLC SDU are used to generate the AMD PDU;

[0043] The first information indicates whether the PDU included in the RLC SDU is the first PDU to be sent in the PDU set, or the first information indicates the sequence number of the PDU included in the RLC SDU in the PDU set.

[0044] According to one aspect of the present application, it includes:

[0045] The PDU set includes at least one PDU, and each PDU included in the PDU set corresponds to a PDCP SDU.

[0046] According to one aspect of the present application, it includes:

[0047] The polling indication is used by the RLC entity of the first node to request a status report from a peer RLC entity.

[0048] According to one aspect of the present application, it includes:

[0049] The first processor receives, at the RLC entity of the first node, a status report from the opposite RLC entity, wherein the status report is a response to the polling indication;

[0050] The status report indicates at least one of an RLC SDU or an RLC SDU segment that has not been successfully received. BRIEF DESCRIPTION OF THE DRAWINGS

[0051] Other features, objects and advantages of the present application will become more apparent by reading the detailed description of non-limiting embodiments made with reference to the following drawings:

[0052] Figure 1 A signal processing flow chart in a first node according to an embodiment of the present application is illustrated;

[0053] Figure 2 A schematic diagram illustrating a network architecture according to an embodiment of the present application is illustrated;

[0054] Figure 3 A schematic diagram illustrating a wireless protocol architecture of a user plane and a control plane according to an embodiment of the present application;

[0055] Figure 4 A hardware module schematic diagram of a communication device according to an embodiment of the present application is illustrated;

[0056] Figure 5 An example of a signal transmission flow chart between entities included in a first node according to an embodiment of the present application is provided;

[0057] Figure 6 An example of a polling and status report diagram according to an embodiment of the present application is shown;

[0058] Figure 7 A schematic diagram illustrating that an AMD PDU includes a first type of data unit according to an embodiment of the present application is illustrated;

[0059] Figure 8 The structural block diagram of a processing device in a first node according to an embodiment of the present application is illustrated. DETAILED DESCRIPTION

[0060] The technical solution of the present application will be further described in detail below in conjunction with the accompanying drawings. It should be noted that, in the absence of conflict, the embodiments of the present application and the features in the embodiments can be arbitrarily combined with each other.

[0061] Example 1

[0062] Embodiment 1 illustrates a signal processing flow chart in a first node according to an embodiment of the present application, as shown in the attached Figure 1 shown.

[0063] In Example 1, the first node 100 receives a transmission opportunity notification from the lower layer of the first node at the RLC entity of the first node in step 101; when an AMD PDU to be transmitted includes a first type of data unit, the value of the first counter is increased by 1 in step 102; if the value of the first counter is not less than a first threshold in step 103, a polling indication is included in the AMD PDU and the value of the first counter is set to 0; and the AMD PDU is submitted to the lower layer of the first node for transmission in step 104; wherein, at least some of the bytes included in the first type of data unit have not been previously sent, and the at least some of the bytes belong to a PDU set, and any byte included in the PDU set has not been previously sent; the PDU set includes at least one byte, and the PDU set carries the payload of an information unit generated at the application level.

[0064] As an embodiment, an RLC entity at the first node receives a transmission opportunity notification from a lower layer of the first node.

[0065] As an embodiment, the transmission opportunity notification is inter-layer information.

[0066] As an embodiment, the sending opportunity notification instructs the RLC entity of the first node to deliver the RLC PDU to the lower layer of the first node.

[0067] As an embodiment, the sending opportunity notification includes a data volume delivered to the lower layer of the first node.

[0068] As an embodiment, the transmission opportunity notification includes the RLC PDU size delivered to the lower layer of the first node.

[0069] As an embodiment, the RLC entity of the first node is an AM (Acknowledged Mode) RLC entity.

[0070] As an embodiment, the lower layer of the first node is a MAC sublayer.

[0071] As an embodiment, when an AMD (AM Data, Acknowledged Mode Data) PDU to be transmitted includes a first type of data unit, the value of the first counter is increased by 1.

[0072] As an embodiment, the AMD PDU to be transmitted is generated by a transmitting side of the AM RLC entity of the first node.

[0073] As an embodiment, the AMD PDU to be transmitted includes a complete RLC SDU or a RLC SDU segment.

[0074] As an embodiment, the AMD PDU to be transmitted is a response to the transmission opportunity notification.

[0075] As an embodiment, after the RLC entity receives the sending opportunity notification, it takes an RLC SDU or an RLC SDU segment according to the instruction of the sending opportunity notification and adds an RLC header to generate the AMD PDU to be transmitted.

[0076] As a sub-embodiment of the above embodiment, the RLC SDU or the RLC SDU segment has not been sent before, that is, it is an initial transmission or a new transmission.

[0077] As a sub-embodiment of the above embodiment, the RLC SDU or the RLC SDU segment has been sent previously, that is, it is a retransmission; wherein the RLC SDU segment has not been re-segmented.

[0078] As a sub-embodiment of the above embodiment, the RLC SDU segment includes some bytes that have been previously sent and some bytes that have not been previously sent; wherein the RLC SDU segment is generated by re-segmentation.

[0079] As an embodiment, the first counter accumulates the number of PDUsets sent since the last polling indication was sent.

[0080] As an embodiment, the name of the first counter includes PDUSET (Protocol Data Unit Set).

[0081] As an embodiment, the first counter is PDUSET_WITHOUT_POLL (protocol data unit set not polled).

[0082] As an embodiment, the value of the first counter is set to 0 when the AM RLC entity is established (setup), re-established (re-establish), or reset (reset).

[0083] As an embodiment, if the current value of the first counter is not less than the first threshold, a polling indication (poll) is included in the AMD PDU and the value of the first counter is set to 0.

[0084] As an embodiment, if the current value of the first counter is greater than the first threshold, a polling indication is included in the AMD PDU and the value of the first counter is set to 0.

[0085] As an embodiment, if the current value of the first counter is equal to the first threshold, a polling indication is included in the AMD PDU and the value of the first counter is set to 0.

[0086] As an embodiment, the first threshold is pre-configured.

[0087] As an embodiment, the first threshold is configurable.

[0088] As an embodiment, the first domain value is configured by RRC (Radio Resource Control).

[0089] As an embodiment, the first threshold is a positive integer greater than 0.

[0090] As an embodiment, the first threshold is not infinity.

[0091] As an embodiment, the polling is that the AM RLC entity of the first node requests a peer AM RLC entity to send a status report.

[0092] As an embodiment, the AMD PDU includes a data field and an AMD PDU header, wherein the AMD PDU header includes a P field, the P field includes 1 bit, and the 1 bit indicates polling.

[0093] As an embodiment, including a polling indication in the AMD PDU includes: setting the 1 bit included in the P field to 1, requesting the opposite AM RLC entity of the AM RLC entity of the first node to send a status report.

[0094] As an embodiment, at least part of the bytes included in the first type of data unit have not been sent before, and the at least part of the bytes belong to a PDU set.

[0095] As an embodiment, the at least part of bytes included in the first type of data unit has not been sent before, including: the first type of data unit includes at least part of bytes that are sent for the first time.

[0096] As an embodiment, some bytes included in the first type of data unit have not been sent before, and the some bytes belong to a PDU set.

[0097] As a sub-embodiment of the above embodiment, the first type of data unit is an RLC SDU segment.

[0098] As an embodiment, all bytes included in the first type of data unit have not been sent before, and all bytes belong to a PDU set.

[0099] As a sub-embodiment of the above embodiment, the first type of data unit is an RLC SDU, or the first type of data unit is an RLC SDU segment.

[0100] As an embodiment, the at least part of the bytes included in the first type of data unit belongs to a PDU included in the PDUset.

[0101] As an embodiment, any byte included in the PDU set has not been sent previously.

[0102] As a sub-embodiment of the above embodiment, any byte included in the PDU set has not been sent before the AMD PDU.

[0103] As a sub-embodiment of the above embodiment, any byte included in the PDU set has not been delivered to the lower layer of the first node before the AMD PDU.

[0104] As a sub-embodiment of the above embodiment, the first PDU included in the PDU set is sent for the first time.

[0105] As a sub-embodiment of the above embodiment, the PDU set is a new PDU set.

[0106] As an embodiment, at least part of the bytes included in the first type of data unit have not been sent before, and the at least part of the bytes belong to a new PDU set.

[0107] As an embodiment, the PDU set includes one or more PDUs.

[0108] As an embodiment, each PDU included in the PDU set corresponds to a PDCP SDU.

[0109] As an embodiment, each PDU included in the PDU set includes at least one byte.

[0110] As an embodiment, the PDU set carries a payload of a unit of information generated at an application level.

[0111] As an embodiment, the application level includes a frame or a video slice of the XR service.

[0112] As an embodiment, the AMD PDU is submitted to the lower layer of the first node for sending.

[0113] Example 2

[0114] Embodiment 2 illustrates a schematic diagram of a network architecture according to an embodiment of the present application, as shown in the attached Figure 2 shown. Figure 2A diagram illustrating a network architecture 200 for NR 5G, LTE (Long-Term Evolution) and LTE-A (Long-Term Evolution Advanced) systems. The NR 5G, LTE or LTE-A network architecture 200 may be referred to as 5GS (5G System) / EPS (Evolved Packet System) 200 or some other suitable terminology. The 5GS / EPS 200 may include one or more UEs (User Equipment) 201, NG-RAN (Next Generation Radio Access Network) 202, 5GC (5G Core Network) / EPC (Evolved Packet Core) 210, HSS (Home Subscriber Server) / UDM (Unified Data Management) 220 and Internet Services 230. The 5GS / EPS may be interconnected with other access networks, but these entities / interfaces are not shown for simplicity. As shown, 5GS / EPS provides packet switching services, however, those skilled in the art will readily appreciate that the various concepts presented throughout this application can be extended to networks providing circuit switching services or other cellular networks. NG-RAN includes NR Node B (gNB) 203 and other gNBs 204. gNB 203 provides user and control plane protocol terminations toward UE 201. gNB 203 can be connected to other gNBs 204 via an Xn interface (e.g., backhaul). gNB 203 may also be referred to as a base station, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (Basic Service Set, BSS), an extended service set (Extended Service Set, ESS), a TRP (Transmission Reception Point, sending and receiving node) or some other suitable terminology. In a NTN (Non Terrestrial Network, non-terrestrial / satellite network) network, gNB 203 may be a satellite, an aircraft, or a ground base station relayed by a satellite. gNB 203 provides an access point to 5GC / EPC 210 for UE 201.Examples of UE 201 include cellular phones, smart phones, Session Initiation Protocol (SIP) phones, laptop computers, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, drones, aircraft, narrowband Internet of Things devices, machine type communication devices, land vehicles, cars, vehicle-mounted devices, vehicle-mounted communication units, wearable devices, or any other similar functional devices. Those skilled in the art may also refer to UE 201 as a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable term. gNB203 is connected to 5GC / EPC210 via the S1 / NG interface. 5GC / EPC210 includes MME (Mobility Management Entity) / AMF (Authentication Management Field) / SMF (Session Management Function) 211, other MME / AMF / SMF214, S-GW (Service Gateway) / UPF (User Plane Function) 212, and P-GW (Packet Data Network Gateway) / UPF213. MME / AMF / SMF211 is the control node that handles signaling between UE201 and 5GC / EPC210. ​​In general, MME / AMF / SMF211 provides bearer and connection management. All user IP (Internet Protocol) packets are transmitted through S-GW / UPF212, which itself is connected to P-GW / UPF213. P-GW provides UE IP address allocation and other functions. P-GW / UPF213 is connected to Internet service 230. Internet service 230 includes operator-corresponding Internet protocol services, which may specifically include Internet, Intranet, IMS (IP Multimedia Subsystem) and PS (Packet Switching) streaming services.

[0115] As an embodiment, the UE201 corresponds to the first node in this application.

[0116] As an embodiment, the NR node B203 corresponds to the first node in this application.

[0117] As an embodiment, the gNB203 is a macro cell base station.

[0118] As an embodiment, the gNB203 is a micro cell base station.

[0119] As an embodiment, the gNB203 is a pico cell base station.

[0120] As an embodiment, the gNB203 is a home base station (Femtocell).

[0121] As an embodiment, the gNB203 is a base station device that supports large delay difference.

[0122] As an embodiment, the gNB203 is a flying platform device.

[0123] As an embodiment, the gNB203 is a satellite device.

[0124] As an embodiment, the gNB203 is a testing device (e.g., a transceiver that simulates some functions of a base station, a signaling tester).

[0125] As an embodiment, the gNB204 is a macro cell base station.

[0126] As an embodiment, the gNB204 is a micro cell base station.

[0127] As an embodiment, the gNB204 is a pico cell base station.

[0128] As an embodiment, the gNB204 is a home base station (Femtocell).

[0129] As an embodiment, the gNB204 is a base station device that supports large delay difference.

[0130] As an embodiment, the gNB204 is a flying platform device.

[0131] As an embodiment, the gNB204 is a satellite device.

[0132] As an embodiment, the gNB204 is a testing device (e.g., a transceiver that simulates some functions of a base station, a signaling tester).

[0133] As an embodiment, the wireless link from the UE201 to the gNB203 / the gNB204 is an uplink, and the uplink is used to perform uplink transmission.

[0134] As an embodiment, the wireless link from the gNB203 / the gNB204 to the UE201 is a downlink, and the downlink is used to perform downlink transmission.

[0135] As an embodiment, the UE201 and the gNB203 / the gNB204 are respectively connected via a Uu interface.

[0136] Embodiment 2 does not show the interface between UE and UE. When there are multiple UEs, the communication interface between UE and UE is PC5. The wireless link from one UE to another UE is a sidelink, which is used to perform sidelink transmission.

[0137] Example 3

[0138] Embodiment 3 illustrates a schematic diagram of a wireless protocol architecture of a user plane and a control plane according to an embodiment of the present application, as shown in the attached figure. Figure 3 shown. Figure 3 is a schematic diagram illustrating an embodiment of a radio protocol architecture for a user plane 350 and a control plane 300, Figure 3The radio protocol architecture of the control plane 300 of the UE and gNB is shown in three layers: Layer 1, Layer 2, and Layer 3. Layer 1 (L1 layer) is the lowest layer and implements various PHY (physical layer) signal processing functions. The L1 layer will be referred to as PHY 301 in this article. Layer 2 (L2 layer) 305 is above PHY 301 and is responsible for the link between the UE and the gNB through PHY 301. The L2 layer 305 includes the MAC (Medium Access Control) sublayer 302, the RLC (Radio Link Control) sublayer 303, and the PDCP (Packet Data Convergence Protocol) sublayer 304, which terminate at the gNB on the network side. The PDCP sublayer 304 provides data encryption and integrity protection. The PDCP sublayer 304 also provides support for inter-zone mobility of UEs between gNBs. The RLC sublayer 303 provides segmentation and reassembly of data packets, and retransmission of lost data packets through ARQ. The RLC sublayer 303 also provides duplicate data packet detection and protocol error detection. The MAC sublayer 302 provides mapping between logical and transport channels and multiplexing of logical channel identities. The MAC sublayer 302 is also responsible for allocating various radio resources (e.g., resource blocks) in a cell between UEs. The MAC sublayer 302 is also responsible for HARQ (Hybrid Automatic Repeat Request) operations. The RRC (Radio Resource Control) sublayer 306 in Layer 3 (L3 layer) in the control plane 300 is responsible for obtaining radio resources (i.e., radio bearers) and configuring the lower layers using RRC signaling between the gNB and the UE. Although not shown in the figure, a V2X layer may also be provided above the RRC sublayer 306 in the control plane 300 of the UE. The V2X layer is responsible for generating a PC5 QoS parameter group and QoS rules according to the received service data or service request, generating a PC5 QoS flow corresponding to the PC5 QoS parameter group, and sending the PC5 QoS flow identifier and the corresponding PC5 QoS parameter group to the AS (Access Stratum) layer for the AS layer to perform QoS processing on the data packets belonging to the PC5 QoS flow identifier; the V2X layer also includes a PC5-S signaling protocol (PC5-Signaling Protocol) sublayer, and the V2X layer is responsible for indicating to the AS layer whether each transmission is a PC5-S transmission or a V2X service data transmission.The wireless protocol architecture of the user plane 350 includes layer 1 (L1 layer) and layer 2 (L2 layer). The wireless protocol architecture in the user plane 350 is substantially the same as the corresponding layers and sublayers in the control plane 300 for the physical layer 351, the PDCP sublayer 354 in the L2 layer 355, the RLC sublayer 353 in the L2 layer 355, and the MAC sublayer 352 in the L2 layer 355, but the PDCP sublayer 354 also provides header compression for upper layer data packets to reduce wireless transmission overhead. The L2 layer 355 in the user plane 350 also includes a SDAP (Service Data Adaptation Protocol) sublayer 356, which is responsible for mapping between QoS (Quality of Service) flows and data radio bearers (DRBs) to support the diversity of services. The wireless protocol architecture of the UE in the user plane 350 may include, at the L2 layer, a SDAP sublayer 356, a PDCP sublayer 354, a portion of or all of the protocol sublayers of the RLC sublayer 353 and the MAC sublayer 352. Although not shown, the UE may also have several upper layers above the L2 layer 355, including a network layer (e.g., an IP layer) terminated at the P-GW on the network side and an application layer terminated at the other end of the connection (e.g., a remote UE, a server, etc.).

[0139] As an example, Figure 3 The wireless protocol architecture in is applicable to the first node in this application.

[0140] As an embodiment, the sending opportunity notification in the present application is generated by the MAC302 or the MAC352.

[0141] As an embodiment, the AMD PDU in the present application is generated in the RLC303 or the RLC353.

[0142] As an embodiment, the status report in the present application is generated in the RLC303 or the RLC353.

[0143] As an embodiment, the L2 layer 305 or 355 belongs to a higher layer.

[0144] As an embodiment, the RRC sublayer 306 in the L3 layer belongs to a higher layer.

[0145] As an embodiment, an SDU is data that is passed from an upper layer to this layer and has not been processed yet, and a PDU is data that is passed to a lower layer after being processed by this layer.

[0146] Taking the RLC sublayer as an example, the RLC sublayer receives an RLC SDU from the PDCP sublayer, and after being processed by the RLC sublayer, transmits an RLC PDU to the MAC sublayer.

[0147] On the inter-layer interface, SDU and PDU can be used interchangeably. For example, on the interface between a higher layer and the PDCP sublayer, a higher-layer PDU can also be called a PDCP SDU; on the interface between the PDCP sublayer and the RLC sublayer, an RLC SDU can also be called a PDCP PDU; on the interface between the RLC sublayer and the MAC sublayer, a MAC SDU can also be called an RLC PDU.

[0148] Example 4

[0149] Embodiment 4 illustrates a hardware module schematic diagram of a communication device according to an embodiment of the present application, as shown in the attached Figure 4 shown. Figure 4 is a block diagram of a first communication device 450 and a second communication device 410 communicating with each other in an access network.

[0150] The first communication device 450 includes a controller / processor 459, a memory 460, a data source 467, a transmit processor 468, a receive processor 456, a multi-antenna transmit processor 457, a multi-antenna receive processor 458, a transmitter / receiver 454 and an antenna 452.

[0151] The second communication device 410 includes a controller / processor 475, a memory 476, a data source 477, a receive processor 470, a transmit processor 416, a multi-antenna receive processor 472, a multi-antenna transmit processor 471, a transmitter / receiver 418 and an antenna 420.

[0152] In the transmission from the second communication device 410 to the first communication device 450, at the second communication device 410, the upper layer data packets from the core network or the upper layer data packets from the data source 477 are provided to the controller / processor 475. The core network and the data source 477 represent all the protocol layers above the L2 layer. The controller / processor 475 implements the functionality of the L2 layer. In the transmission from the second communication device 410 to the first communication device 450, the controller / processor 475 provides header compression, encryption, packet segmentation and reordering, multiplexing between logical and transport channels, and radio resource allocation to the first communication device 450 based on various priority metrics. The controller / processor 475 is also responsible for the retransmission of lost packets and signaling to the first communication device 450. The transmit processor 416 and the multi-antenna transmit processor 471 implement various signal processing functions for the L1 layer (i.e., the physical layer). The transmit processor 416 implements coding and interleaving to facilitate forward error correction (FEC) at the second communication device 410, as well as mapping of signal constellations based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The multi-antenna transmit processor 471 performs digital spatial precoding, including codebook-based precoding and non-codebook-based precoding, and beamforming processing on the coded and modulated symbols to generate one or more spatial streams. The transmit processor 416 then maps each spatial stream to a subcarrier, multiplexes it with a reference signal (e.g., a pilot) in the time domain and / or frequency domain, and then uses an inverse fast Fourier transform (IFFT) to generate a physical channel carrying a time-domain multi-carrier symbol stream. The multi-antenna transmit processor 471 then performs a transmit analog precoding / beamforming operation on the time-domain multi-carrier symbol stream. Each transmitter 418 converts the baseband multi-carrier symbol stream provided by the multi-antenna transmit processor 471 into a radio frequency stream, and then provides it to a different antenna 420.

[0153] In the transmission from the second communication device 410 to the first communication device 450, at the first communication device 450, each receiver 454 receives a signal through its corresponding antenna 452. Each receiver 454 recovers the information modulated onto the RF carrier and converts the RF stream into a baseband multi-carrier symbol stream and provides it to the receiving processor 456. The receiving processor 456 and the multi-antenna receiving processor 458 implement various signal processing functions of the L1 layer. The multi-antenna receiving processor 458 performs a receiving analog precoding / beamforming operation on the baseband multi-carrier symbol stream from the receiver 454. The receiving processor 456 uses a fast Fourier transform (FFT) to convert the baseband multi-carrier symbol stream after the receiving analog precoding / beamforming operation from the time domain to the frequency domain. In the frequency domain, the physical layer data signal and the reference signal are demultiplexed by the receiving processor 456, wherein the reference signal will be used for channel estimation, and the data signal is recovered after multi-antenna detection in the multi-antenna receiving processor 458 to any spatial stream destined for the first communication device 450. The symbols on each spatial stream are demodulated and recovered in the receiving processor 456, and soft decisions are generated. The receiving processor 456 then decodes and deinterleaves the soft decisions to recover the upper layer data and control signals transmitted by the second communication device 410 on the physical channel. The upper layer data and control signals are then provided to the controller / processor 459. The controller / processor 459 implements the functions of the L2 layer. The controller / processor 459 may be associated with a memory 460 that stores program codes and data. The memory 460 may be referred to as a computer-readable medium. In the transmission from the second communication device 410 to the first communication device 450, the controller / processor 459 provides multiplexing between transport and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover the upper layer data packets from the second communication device 410. The upper layer data packets are then provided to all protocol layers above the L2 layer. Various control signals may also be provided to the L3 for L3 processing.

[0154] In the transmission from the first communication device 450 to the second communication device 410, at the first communication device 450, the upper layer data packets are provided to the controller / processor 459 using the data source 467. The data source 467 represents all the protocol layers above the L2 layer. Similar to the transmission function at the second communication device 410 described in the transmission from the second communication device 410 to the first communication device 450, the controller / processor 459 implements header compression, encryption, packet segmentation and reordering, and multiplexing between logical and transport channels, and implements L2 layer functions for user plane and control plane. The controller / processor 459 is also responsible for the retransmission of lost packets and signaling to the second communication device 410. The transmit processor 468 performs modulation mapping and channel coding processing, and the multi-antenna transmit processor 457 performs digital multi-antenna spatial precoding, including codebook-based precoding and non-codebook-based precoding, and beamforming processing. Then, the transmit processor 468 modulates the generated spatial stream into a multi-carrier / single-carrier symbol stream, which is then provided to different antennas 452 via the transmitter 454 after analog precoding / beamforming operations in the multi-antenna transmit processor 457. Each transmitter 454 first converts the baseband symbol stream provided by the multi-antenna transmit processor 457 into a radio frequency symbol stream, and then provides it to the antenna 452.

[0155] In the transmission from the first communication device 450 to the second communication device 410, the functions at the second communication device 410 are similar to the reception functions at the first communication device 450 described in the transmission from the second communication device 410 to the first communication device 450. Each receiver 418 receives a radio frequency signal through its corresponding antenna 420, converts the received radio frequency signal into a baseband signal, and provides the baseband signal to the multi-antenna reception processor 472 and the reception processor 470. The reception processor 470 and the multi-antenna reception processor 472 jointly implement the functions of the L1 layer. The controller / processor 475 implements the L2 layer functions. The controller / processor 475 can be associated with a memory 476 that stores program codes and data. The memory 476 can be referred to as a computer-readable medium. In the transmission from the first communication device 450 to the second communication device 410, the controller / processor 475 provides multiplexing between transport and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover the upper layer data packets from the first communication device 450. The upper layer data packets from the controller / processor 475 may be provided to the core network or all protocol layers above the L2 layer, and various control signals may also be provided to the core network or L3 for L3 processing.

[0156] As an embodiment, the first communication device 450 apparatus includes: at least one processor and at least one memory, the at least one memory including computer program code; the at least one memory and the computer program code are configured to be used together with the at least one processor, and the first communication device 450 apparatus at least: receives a transmission opportunity notification from the lower layer of the first node at the RLC entity of the first node; when an AMD PDU to be transmitted includes a first type of data unit, adds 1 to the value of the first counter; if the value of the first counter is not less than a first threshold, includes a polling indication in the AMD PDU and sets the value of the first counter to 0; delivers the AMD PDU to the lower layer of the first node for transmission; wherein at least some of the bytes included in the first type of data unit have not been sent before, and the at least some of the bytes belong to a PDU set, and any byte included in the PDU set has not been sent before; the PDU set includes at least one byte, and the PDU set carries the payload of an information unit generated at the application level.

[0157] As an embodiment, the first communication device 450 apparatus includes: a memory storing a computer-readable instruction program, the computer-readable instruction program generates actions when executed by at least one processor, the actions including: receiving a transmission opportunity notification from a lower layer of the first node at an RLC entity of the first node; when an AMD PDU to be transmitted includes a first type of data unit, adding 1 to the value of a first counter; if the value of the first counter is not less than a first threshold, including a polling indication in the AMD PDU and setting the value of the first counter to 0; delivering the AMD PDU to the lower layer of the first node for transmission; wherein at least some of the bytes included in the first type of data unit have not been previously sent, and the at least some of the bytes belong to a PDU set, and any byte included in the PDU set has not been previously sent; the PDU set includes at least one byte, and the PDU set carries the payload of an information unit generated at the application level.

[0158] As an embodiment, the first communication device 450 corresponds to the first node in the present application, and the second communication device 410 corresponds to the opposite communication node of the first node in the present application.

[0159] As an embodiment, the second communication device 410 corresponds to the first node in the present application, and the second communication device 450 corresponds to the opposite communication node of the first node in the present application.

[0160] As an embodiment, the first communication device 450 is a UE, and the second communication device 410 is a base station device.

[0161] As an embodiment, the first communication device 450 is a relay, and the second communication device 410 is a base station device.

[0162] As an embodiment, the first communication device 450 is a base station device, and the second communication device 410 is a UE.

[0163] As an embodiment, the first communication device 450 is a base station device, and the second communication device 410 is a relay.

[0164] As an embodiment, the first communication device 450 is a UE, and the second communication device 410 is a UE.

[0165] As an embodiment, at least one of the antenna 452, the transmitter 454, the multi-antenna transmit processor 457, the transmit processor 468 or the controller / processor 459 is used to send and receive the transmission opportunity notification in the present application.

[0166] As an embodiment, the transmission opportunity notification in the present application is sent and received between two entities inside the first communication device 450 .

[0167] As an embodiment, at least one of the antenna 420, the transmitter 418, the multi-antenna transmit processor 471, the transmit processor 416 or the controller / processor 475 is used to send and receive the transmission opportunity notification in the present application.

[0168] As an embodiment, the sending opportunity notification in the present application is sent and received between two entities inside the second communication device 410 .

[0169] As an embodiment, at least one of the antenna 452, the transmitter 454, the multi-antenna transmit processor 457, the transmit processor 468 or the controller / processor 459 is used to send and receive the AMD PDU in the present application.

[0170] As an embodiment, the AMD PDU in the present application is sent and received between two entities inside the first communication device 450 .

[0171] As an embodiment, at least one of the antenna 420, the transmitter 418, the multi-antenna transmit processor 471, the transmit processor 416 or the controller / processor 475 is used to send and receive the AMD PDU in the present application.

[0172] As an embodiment, the AMD PDU in the present application is sent and received between two entities inside the second communication device 410 .

[0173] As an embodiment, at least one of the antenna 452, the transmitter 454, the multi-antenna transmit processor 457, the transmit processor 468 or the controller / processor 459 is used to send and receive the RLC SDU in the present application.

[0174] As an embodiment, the RLC SDU in the present application is sent and received between two entities inside the first communication device 450.

[0175] As an embodiment, at least one of the antenna 420, the transmitter 418, the multi-antenna transmit processor 471, the transmit processor 416 or the controller / processor 475 is used to send and receive the RLC SDU in the present application.

[0176] As an embodiment, the RLC SDU in the present application is sent and received between two entities inside the second communication device 410.

[0177] As an embodiment, at least one of the antenna 452, the receiver 454, the multi-antenna reception processor 458, the reception processor 456 or the controller / processor 459 is used to receive the status report in the present application.

[0178] As an embodiment, at least one of the antenna 420, the transmitter 418, the multi-antenna transmit processor 471, the transmit processor 416 or the controller / processor 475 is used to send the status report in the present application.

[0179] As an embodiment, at least one of the antenna 420, the receiver 418, the multi-antenna reception processor 472, the reception processor 470 or the controller / processor 475 is used to receive the status report in the present application.

[0180] As an embodiment, at least one of the antenna 452, the transmitter 454, the multi-antenna transmit processor 457, the transmit processor 468 or the controller / processor 459 is used to send the status report in the present application.

[0181] Example 5

[0182] Embodiment 5 illustrates a signal transmission flow chart between entities included in the first node according to an embodiment of the present application, as shown in the attached figure. Figure 5 As shown in the attached Figure 5In the example, the RLC entity N51 and the MAC entity N52 communicate through an internal interface, and the RLC entity N51 and the PDCP entity N53 communicate through an internal interface. It is particularly noted that the order in this example does not limit the signal transmission order and implementation order in this application.

[0183] for RLC entity N51 , receiving an RLC SDU and first information in step S511; receiving a transmission opportunity notification in step S512; generating an AMD PDU in step S513; and submitting the AMD PDU for transmission in step S514.

[0184] for MAC Entity N52 , submitting a sending opportunity notification in step S521; and receiving an AMD PDU in step S522.

[0185] for PDCP entity N53 , submit an RLC SDU and the first information in step S531.

[0186] In embodiment 5, the RLC entity at the first node receives a transmission opportunity notification from the lower layer of the first node; when an AMD PDU to be transmitted includes a first type of data unit, the value of the first counter is increased by 1; if the value of the first counter is not less than a first threshold, a polling indication is included in the AMD PDU and the value of the first counter is set to 0; the AMD PDU is delivered to the lower layer of the first node for transmission; wherein at least some of the bytes included in the first type of data unit have not been previously sent, and the at least some of the bytes belong to a PDU set, and any byte included in the PDUset has not been previously sent; the PDU set includes at least one byte, and the PDU set carries the payload of an information unit generated at the application level; the RLC entity at the first node receives an RLC SDU and first information from the upper layer of the first node, and at least some of the bytes included in the RLC SDU are used to generate the AMD PDU; wherein the first information indicates whether the PDU included in the RLC SDU is the first PDU to be sent in the PDU set, or the first information indicates the sequence number of the PDU included in the RLC SDU in the PDU set; the PDU The set includes at least one PDU, and each PDU included in the PDU set corresponds to a PDCP SDU.

[0187] For the convenience of description, the RLC SDU delivered from the PDCP entity N53 to the RLC entity N51 is the PDCP PDU.

[0188] The submitting and receiving correspondences in this application are used to describe the information transfer between two different entities in a node.

[0189] As an embodiment, the RLC entity N51, the MAC entity N52 and the PDCP entity N53 are all located in the first node.

[0190] As an embodiment, the first node is a UE.

[0191] As an embodiment, the first node is a base station.

[0192] As an embodiment, the first node is a layer 3 relay.

[0193] As an embodiment, the RLC entity at the first node receives an RLC SDU and first information from an upper layer of the first node.

[0194] As an embodiment, the first information is associated with the RLC SDU.

[0195] As an embodiment, the first information accompanies the RLC SDU.

[0196] As an embodiment, the upper layer is the PDCP sublayer, and the RLC SDU is the PDCP PDU.

[0197] As an embodiment, the upper layer is a SRAP (Sidelink Relay Adaptation Protocol) sublayer, and the RLC SDU is a SRAP PDU.

[0198] As an embodiment, at least part of the bytes included in the RLC SDU are used to generate the AMD PDU.

[0199] As an embodiment, all bytes included in the RLC SDU are used to generate the AMD PDU, and the AMD PDU includes the RLC SDU.

[0200] As an embodiment, part of the bytes included in the RLC SDU are used to generate the AMD PDU, and the AMD PDU includes RLC SDU segments.

[0201] As an embodiment, the AMD PDU is generated by adding at least part of the bytes included in the RLC SDU to the RLC header.

[0202] As an embodiment, the first information is inter-layer information.

[0203] As an embodiment, when the first node is a base station, Figure 2 The UPF included in the PDU identifies the PDU belonging to the PDUset, and indicates the PDU and information of the PDU set to the first node through a GTP-U (GPRS tunnelingprotocol) header: the sequence number of the PDU set, the end PDU (EndPDU) indication of the PDU set, the sequence number of the PDU in the PDU set, the size of the PDU set (in bytes), and the importance of the PDU set.

[0204] As an embodiment, when the first node is a UE, the information of the PDU set is identified by the UE.

[0205] As an embodiment, when the first node is a UE, the information of the PDU set is identified by the application layer of the UE.

[0206] As an embodiment, the first information depends on the information of the PDU set.

[0207] As an embodiment, the first information is delivered to the RLC entity N51 along with the PDU for generating the RLC SDU.

[0208] As an embodiment, the first information indicates whether the PDU included in the RLC SDU is the first PDU of the PDU set.

[0209] As an embodiment, the at least part of the bytes included in the first type of data unit are indicated to belong to the first PDU sent in the PDU set.

[0210] As an embodiment, the first PDU sent in the PDU set is the PDU in the PDU set that first arrives at the PDCP entity N53.

[0211] As an embodiment, the first information indicates the sequence number of the PDU used to generate the RLC SDU in the PDU set.

[0212] As an embodiment, the at least part of the bytes included in the first type of data unit are indicated to belong to the PDU with sequence number K in the PDU set; wherein, the PDUs included in the PDU set are arranged in ascending order starting from sequence number K, and K is a non-negative integer, such as K is 0, or K is 1.

[0213] As an embodiment, when the RLC entity N51 receives the sending opportunity notification, it generates the AMD PDU from the RLC SDU and submits it to the MAC entity N52; the AM PDU is submitted to the physical layer after being processed by the MAC entity N52, and is sent over the air interface after being processed by the physical layer.

[0214] Example 6

[0215] Embodiment 6 illustrates a polling and status report diagram according to an embodiment of the present application, as shown in the attached figure. Figure 6 As shown in the attached Figure 6 In the example, there is a logical interface between the RLC entity N61 and the counterpart RLC entity N62, and the logical interface is an interface between two peer entities.

[0216] for RLC entity N61 , submitting the AMD PDU for sending in step S611; and receiving the status report in step S612.

[0217] for Peer RLC entity N62 , receive AMD PDU in step S621; send status report in step S622.

[0218] As an embodiment, two peer RLC entities are located at two nodes that communicate with each other, and the communication process between the two RLC entities includes: at one node, the RLC PDU generated by the RLC SDU is delivered to the MAC entity to generate a MAC PDU, and then delivered to the physical layer to generate a physical signal and then sent to another node through a wireless interface; at the other node, the MAC PDU is recovered through physical layer processing and delivered to the MAC entity, the MAC entity strips off the MAC header to recover the MAC SDU and then delivers it to the RLC entity, and the RLC entity strips off the RLC header to recover the RLC SDU.

[0219] As an embodiment, the RLC entity N61 is located at the first node, and the opposite RLC entity N62 is located at a node other than the first node.

[0220] As an embodiment, the RLC entity N61 is located in one UE, and the counterpart RLC entity N62 is located in another UE.

[0221] As an embodiment, the RLC entity N61 is located in a UE, and the opposite RLC entity N62 is located in a base station.

[0222] As an embodiment, the RLC entity N61 is located in a base station, and the opposite end RLC entity N62 is located in a UE.

[0223] As a sub-embodiment of the above three embodiments, the UE may be a terminal or a relay UE.

[0224] As an embodiment, the AMD PDU includes the polling indication, and the polling indication is used by the RLC entity N61 to request a status report from the peer RLC entity N62.

[0225] As an embodiment, the counterpart RLC entity N62 is an AM RLC entity.

[0226] As an embodiment, after receiving the polling indication, the opposite-end RLC entity N62 generates and sends a status report.

[0227] As an embodiment, the status report is a response to the polling indication.

[0228] As an embodiment, the RLC entity at the first node receives a status report from the opposite RLC entity.

[0229] As an embodiment, the status report is a STATUS PDU.

[0230] As an embodiment, the status report indicates RLC SDUs that have not been successfully received.

[0231] As an embodiment, the status report includes sequence numbers of RLC SDUs that have not been successfully received.

[0232] As an embodiment, the status report indicates RLC SDU segments that have not been successfully received.

[0233] As an embodiment, the status report includes the sequence number of the RLC SDU to which the RLC SDU segment that has not been successfully received belongs and the position of the RLC SDU segment in the RLC SDU.

[0234] Example 7

[0235] Embodiment 7 illustrates a schematic diagram of an AMD PDU including a first type of data unit according to an embodiment of the present application, as shown in the attached Figure 7 Attached Figure 7 In the figure, the rectangle filled with slashes indicates bytes that have not been sent previously.

[0236] As an embodiment, the byte that has not been sent before is the byte that is sent for the first time.

[0237] As an embodiment, the AMD PDU includes an RLC header and the RLC SDU.

[0238] As an embodiment, the AMD PDU includes an RLC header and the RLC SDU segment.

[0239] In case A of embodiment 7, the AMD PDU includes the RLC SDU or the RLC SDU segment, and all bytes included in the RLC SDU or all bytes included in the RLC SDU segment have not been sent before.

[0240] In situation B of Example 7, the AMD PDU includes the RLC SDU segment, a portion of the bytes included in the RLC SDU segment have been previously sent, and the remaining bytes included in the RLC SDU segment have not been previously sent, and the RLC SDU segment is generated after re-segmentation.

[0241] Specifically, an RLC SDU is composed of two RLC SDU segments, namely RLC SDU segment 1 and RLC SDU segment 2. RLC SDU segment 1 has been previously sent, and RLC SDU segment 2 has not been previously sent; when RLC SDU segment 1 is indicated by a status report as not being successfully sent, if the transmission opportunity notification indication received from the MAC sublayer is greater than the data amount of RLC SDU segment 1, the RLC entity can re-segment the RLC SDU to generate a new RLC SDU segment 3 and a new RLC SDU segment 4, wherein the new RLC SDU segment 3 includes the bytes of the original RLC SDU segment 1 and part of the bytes in the original RLC SDU segment 2; the new RLC SDU segment 4 includes the remaining bytes of the original RLC SDU segment 2.

[0242] Corresponding to situation B of embodiment 7, the RLC SDU segment is a new RLC SDU segment 3 generated after the RLC SDU is re-segmented, which includes the retransmitted bytes belonging to the original RLC SDU segment 1 and a part of the newly transmitted bytes belonging to the original RLC SDU segment 2.

[0243] Example 8

[0244] Embodiment 8 illustrates a structural block diagram of a processing device in a first node according to an embodiment of the present application, as shown in the attached Figure 8 As shown in the attached Figure 8 In the embodiment, the first node processing device 800 includes a first processor 801; the first node 800 is a UE, or the first node 800 is a base station, or the first node 800 is a relay.

[0245] The first processor 801 receives a transmission opportunity notification from the lower layer of the first node at the RLC entity of the first node; when an AMD PDU to be transmitted includes a first type of data unit, adds 1 to the value of the first counter; if the value of the first counter is not less than a first threshold, includes a polling indication in the AMD PDU and sets the value of the first counter to 0; delivers the AMD PDU to the lower layer of the first node for transmission; wherein at least some of the bytes included in the first type of data unit have not been sent before, and the at least some of the bytes belong to a PDU set, and any byte included in the PDUset has not been sent before; the PDU set includes at least one byte, and the PDU set carries the payload of an information unit generated at the application level.

[0246] As an embodiment, the first processor 801, the RLC entity of the first node receives an RLC SDU and first information from the upper layer of the first node, and at least part of the bytes included in the RLC SDU are used to generate the AMD PDU; wherein the first information indicates whether the PDU included in the RLC SDU is the first PDU to be sent in the PDU set, or the first information indicates the sequence number of the PDU included in the RLC SDU in the PDU set.

[0247] As an embodiment, the PDU set includes at least one PDU, and each PDU included in the PDU set corresponds to a PDCP SDU.

[0248] As an embodiment, the polling indication is used by the RLC entity of the first node to request a status report from the RLC entity of the opposite end.

[0249] As an embodiment, the polling indication is used by the RLC entity of the first node to request a status report from the peer RLC entity; the first processor 801, the RLC entity of the first node receives a status report from the peer RLC entity, and the status report is a response to the polling indication; wherein the status report indicates at least one of an RLC SDU or an RLC SDU segment that has not been successfully received.

[0250] As an embodiment, the first processor is an RLC entity of the first node.

[0251] As an embodiment, the first processor is a transmitting side of an RLC entity of the first node.

[0252] As an embodiment, the first processor includes a transmitter.

[0253] As an embodiment, the first processor includes a receiver.

[0254] As an embodiment, the first processor 801 includes the attached Figure 4 At least one of the transmitter 454 (including antenna 452), the transmit processor 468, the multi-antenna transmit processor 457 or the controller / processor 459.

[0255] As an embodiment, the first processor 801 includes the attached Figure 4 At least one of the receiver 454 (including antenna 452), receive processor 456, multi-antenna receive processor 458 or controller / processor 459.

[0256] As an embodiment, the first processor 801 includes a controller / processor 459 .

[0257] A person of ordinary skill in the art can understand that all or part of the steps in the above method can be completed by instructing the relevant hardware through a program, and the program can be stored in a computer-readable storage medium, such as a read-only memory, a hard disk or an optical disk. Optionally, all or part of the steps in the above embodiment can also be implemented using one or more integrated circuits. Accordingly, each module unit in the above embodiment can be implemented in the form of hardware or in the form of a software function module, and the present application is not limited to any specific form of software and hardware combination. The first type of communication node or UE or terminal in the present application includes but is not limited to mobile phones, tablet computers, notebooks, Internet cards, low-power devices, eMTC (enhanced Machine Type Communication, enhanced machine type communication) equipment, NB-IoT equipment, vehicle-mounted communication equipment, aircraft, airplanes, drones, remote-controlled aircraft and other wireless communication equipment. The second type of communication node or base station or network side equipment in the present application includes but is not limited to macrocellular base stations, microcellular base stations, home base stations, relay base stations, eNB, gNB, transmission and reception nodes TRP (Transmission and Reception Point, transmission and reception point), relay satellites, satellite base stations, aerial base stations and other wireless communication equipment.

[0258] The above is only a preferred embodiment of the present application and is not intended to limit the protection scope of the present application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. A first node used for wireless communication, characterized in that: include: A first processor receives a transmission opportunity notification from a lower layer of the first node at an RLC entity of the first node; When an AMD PDU to be transmitted includes a first type of data unit, adding 1 to the value of a first counter; if the value of the first counter is not less than a first threshold, including a polling indication in the AMD PDU and setting the value of the first counter to 0; delivering the AMD PDU to the lower layer of the first node for transmission; Among them, at least some of the bytes included in the first type of data unit have not been sent before, and the at least some of the bytes belong to a PDU set, and any byte included in the PDU set has not been sent before; the PDU set includes at least one byte, and the PDU set carries the payload of an information unit generated at the application level.

2. The first node according to claim 1, characterized in that: include: The first processor receives, at the RLC entity of the first node, an RLC SDU and first information from an upper layer of the first node, wherein at least part of bytes included in the RLC SDU are used to generate the AMD PDU; The first information indicates whether the PDU included in the RLC SDU is the first PDU to be sent in the PDU set, or the first information indicates the sequence number of the PDU included in the RLC SDU in the PDU set.

3. The first node according to claim 1 or 2, characterized in that: The PDU set includes at least one PDU, and each PDU included in the PDU set corresponds to a PDCP SDU.

4. The first node according to any one of claims 1 to 3, characterized in that: The polling indication is used by the RLC entity of the first node to request a status report from a peer RLC entity.

5. The first node according to claim 4, characterized in that: include: The first processor receives, at the RLC entity of the first node, a status report from the opposite RLC entity, wherein the status report is a response to the polling indication; The status report indicates at least one of an RLC SDU or an RLC SDU segment that has not been successfully received.

6. A method in a first node for wireless communication, characterized in that: include: Receiving, at the first node, a transmission opportunity notification from a lower layer of the first node; When an AMD PDU to be transmitted includes a first type of data unit, increasing the value of the first counter by 1; If the value of the first counter is not less than a first threshold, including a polling indication in the AMD PDU and setting the value of the first counter to 0; Submitting the AMD PDU to the lower layer of the first node for sending; Among them, at least some of the bytes included in the first type of data unit have not been sent before, and the at least some of the bytes belong to a PDU set, and any byte included in the PDU set has not been sent before; the PDU set includes at least one byte, and the PDU set carries the payload of an information unit generated at the application level.

7. The method in the first node according to claim 6, characterized in that: include: The RLC entity at the first node receives an RLC SDU and first information from an upper layer of the first node, wherein at least part of bytes included in the RLC SDU are used to generate the AMD PDU; The first information indicates whether the PDU included in the RLC SDU is the first PDU to be sent in the PDU set, or the first information indicates the sequence number of the PDU included in the RLC SDU in the PDU set.

8. The method in the first node according to claim 6 or 7, characterized in that: The PDU set includes at least one PDU, and each PDU included in the PDU set corresponds to a PDCP SDU.

9. The method in the first node according to any one of claims 6 to 8, characterized in that: The polling indication is used by the RLC entity of the first node to request a status report from a peer RLC entity.

10. The method in the first node according to claim 9, characterized in that: include: The RLC entity at the first node receives a status report from the opposite RLC entity, wherein the status report is a response to the polling indication; The status report indicates at least one of an RLC SDU or an RLC SDU segment that has not been successfully received.

Images