CN117641617A

CN117641617A - Method and apparatus for use in wireless communication

Info

Publication number: CN117641617A
Application number: CN202210963689.2A
Authority: CN
Inventors: 张锦芳; 张晓博
Original assignee: Shanghai Langbo Communication Technology Co Ltd
Current assignee: Shanghai Langbo Communication Technology Co Ltd
Priority date: 2022-08-11
Filing date: 2022-08-11
Publication date: 2024-03-01
Also published as: WO2024032519A1

Abstract

A method and apparatus for use in wireless communications is disclosed. The first node receives a first PDCP SDU; starting a first timer in response to receiving the first pdcsdu; when the first timer is in an operation state, delivering the first PDCPDU to a first RLC entity for transmission; the first PDCP pdu is a data unit of the first PDCP sdu processed by the first PDCP entity; the first RLC entity is one of a first candidate RLC entity and a second candidate RLC entity, and the first RLC entity is the first candidate RLC entity or the second candidate RLC entity is related to the value of the first timer; the first candidate RLC entity and the second candidate RLC entity are respectively associated with the first PDCP entity; the data units included in the first candidate RLC entity are sent through a direct connection path; and the data units included in the second candidate RLC entity are sent through a non-direct connection path. The method and the device can improve the success rate of data transmission.

Description

Method and apparatus for use in wireless communication

Technical Field

The present application relates to methods and apparatus in wireless communication systems, and more particularly, to methods and apparatus for supporting multipath transmission in wireless communications.

Background

For V2X (Vehicle-to-evolution) services, public Safety (Public Safety) services, and business applications and services, 3GPP (3 rd Generation Partner Project, third generation partnership project) RAN (radio access network) initiated SI (Study Item) and WI (Work Item) standardization Work for "new air interface sidelink relay Study" in release 17, but release 17 only supported limited features due to time constraints. To further support the 5G (Fifth Generation) system enhancements, release 18 began a second phase study of proximity services (ProSe), including supporting multi-path (multi-path) transmissions. The multipath transmission may include direct path (directpath) transmission and indirect path (indirect path) transmission, in which there is only one-hop transmission between the source node and the destination receiving node, and in which there is multiple hops between the source node and the destination receiving node. The relay is used as a multi-hop transmission technology, so that throughput can be improved, robustness can be improved, and coverage can be increased. The data of the source node reaches the destination receiving node through the forwarding of the Relay Node (RN). The source node and the destination receiving node are typically base station equipment and user equipment, or may be both user equipment; the relay node may be a network device or a user equipment. Taking the example of relay transmission in the LTE (Long TermEvolution ) system, the transmission from the UE to the relay node adopts a Sidelink (SL) air interface technology, the transmission from the relay node to the base station or an enhanced node B (eNodeB, eNB) adopts an LTE air interface technology, and the relay node is used for data forwarding between the UE (user equipment) and the eNB.

Disclosure of Invention

The inventor finds through research that, for the non-direct connection path, the network splits the total transmission delay into transmission delays on each hop, and in each hop transmission, if a data packet is not successfully sent after reaching the maximum allowable transmission delay, the data packet is discarded. In supporting multipath transmission including a direct path and a non-direct path, a timeout of a packet transmitted on the non-direct path does not mean that the packet is transmitted on the direct path and also in a supermarket, which would cause a decrease in service quality if the packet were discarded directly. So how to select a transmission path among a direct path and a non-direct path needs to be studied.

Aiming at the problems, the application discloses a solution which can effectively improve the success rate of data transmission. Embodiments in a first node and features in embodiments of the present application may be applied to a second node and vice versa without conflict. The embodiments of the present application and features in the embodiments may be combined with each other arbitrarily without conflict. Further, while the present application is initially directed to the Uu air interface, the present application can also be used with the PC5 air interface. Further, although the present application is initially directed to the terminal and base station scenario, the present application is also applicable to the relay and base station, and achieves similar technical effects in the terminal and base station scenario. Furthermore, the adoption of a unified solution for different scenarios (including but not limited to V2X scenarios and communication scenarios of terminals with base stations) also helps to reduce hardware complexity and cost. In particular, the term (Terminology), noun, function, variable in this application may be interpreted (if not specifically stated) with reference to the definitions in the 3GPP specification protocols TS36 series, TS38 series, TS37 series.

The application discloses a method used in a first node of wireless communication, comprising the following steps:

receiving a first PDCP SDU;

starting a first timer in response to receiving the first PDCP SDU;

when the first timer is in an operation state, submitting a first PDCP PDU to a first RLC entity for transmission;

the first PDCP PDU is a data unit of the first PDCP SDU processed by the first PDCP entity; the first RLC entity is one of a first candidate RLC entity and a second candidate RLC entity, and the first RLC entity is the first candidate RLC entity or the second candidate RLC entity is related to the value of the first timer; the first candidate RLC entity and the second candidate RLC entity are respectively associated with the first PDCP entity; the data units included in the first candidate RLC entity are sent through a direct connection path; and the data units included in the second candidate RLC entity are sent through a non-direct connection path.

As an example, the present application is applicable to dual connection (dual connectivity) transmission.

As one example, the present application is applicable to multi-path (multi-path) transmissions.

As an embodiment, the present application is applicable to a scenario including a direct path and a non-direct path in multipath transmission.

As one embodiment, the non-direct path in the present application is forwarded through a UE-to-Network (U2N) relay.

As one embodiment, the non-direct path in the present application is forwarded through Layer (Layer) 2U2N trunking.

As one embodiment, the non-direct path in the present application is forwarded through layer 2U (UE-to-UE, user-to-user) relay.

As an embodiment, the present application is applicable to PDCP (PacketData Convergence Protocol ) recovery.

As an embodiment, the method can improve the data transmission rate and improve the data transmission robustness by sending through a non-direct connection path.

As an embodiment, the above method can reduce transmission delay through direct path transmission.

As an embodiment, the above method determines, by using the value of the first timer, that the first RLC (Radio LinkControl ) entity can increase the transmission rate at the same time, and can also avoid that the first PDCP SDU (Service Data Unit ) has expired when reaching the intended receiver due to the transmission delay introduced by the relay forwarding, thereby causing the service quality to be degraded.

As one embodiment, the above-described approach is backward compatible, helping to reduce hardware complexity and cost.

As one embodiment, the entity (entity) in the present application is a module (module).

As one example, an entity in this application is a module that performs a set of functions.

As one example, an entity in this application is a hardware module that performs a set of functions.

As one example, an entity in this application is a software module that performs a set of functions.

As an embodiment, the relay node and the relay UE in the present application may be interchanged.

According to one aspect of the present application, there is provided:

the first RLC entity is the first candidate RLC entity when the value of the first timer is greater than a first threshold.

As one example, the above method can reduce transmission delay and avoid packet loss beyond packet delay budget (packet delaybudget, PDB).

According to one aspect of the present application, there is provided:

when the value of the first timer is less than the first threshold, whether the first RLC entity is the first candidate RLC entity or the second candidate RLC entity is related to a reference amount of data;

wherein the reference data amount is a total amount of PDCP data amount in the first PDCP entity and RLC data amount waiting for initial transmission (initial transmission) in the first candidate RLC entity and the second candidate RLC entity.

As one embodiment, the above method is compatible with split bearers (split bearers).

As one example, the above method may increase the transmission rate.

As one embodiment, the above method supports traffic with large bandwidth requirements.

According to one aspect of the present application, there is provided:

delivering the first PDCP PDU to the first candidate RLC entity for transmission;

wherein the value of the first timer is greater than the first threshold and the first timer has not expired; the first PDCP entity not receiving an indication of successful transmission of the first PDCP PDU from the second candidate RLC entity; the first RLC entity is the second candidate RLC entity.

As an embodiment, the above method may improve data transmission robustness through retransmission of the first candidate RLC entity.

According to one aspect of the present application, there is provided:

transmitting a first indication, the first indication being used to instruct the first RLC entity to discard the first PDCP PDU; discarding the first RLC SDU when neither the first RLC SDU nor the segmentation of the first RLC SDU is delivered to the lower layer;

wherein the first RLC SDU is the first PDCP PDU.

As an embodiment, the above method may save air interface resources by discarding the first PDCP PDU (Protocol Data Unit ).

According to one aspect of the present application, there is provided:

the direct path includes only one air interface and the non-direct path includes at least two air interfaces.

According to one aspect of the present application, there is provided:

receiving a first message, the first message indicating a first expiration value and the first threshold value;

wherein the first expiration value is used to determine that the first timer expires; the difference of the first expiration value minus the first threshold is used to determine a maximum transmission delay for the first PDCP PDU forwarded through the node where the peer RLC entity of the second candidate RLC entity is located.

As one example, the above method may achieve consistent transmission delay performance for transmissions on each of the multiple paths.

The application discloses a first node used for wireless communication, which is characterized by comprising:

a first transceiver receiving a first PDCP SDU; starting a first timer in response to receiving the first PDCP SDU; when the first timer is in an operation state, submitting a first PDCP PDU to a first RLC entity for transmission;

According to one aspect of the present application, there is provided:

the first transceiver delivering the first PDCP PDU to the first candidate RLC entity for transmission;

According to one aspect of the present application, there is provided:

The first transceiver sending a first indication, the first indication being used to instruct the first RLC entity to discard the first PDCP PDU; discarding the first RLC SDU when neither the first RLC SDU nor the segmentation of the first RLC SDU is delivered to the lower layer;

wherein the first RLC SDU is the first PDCP PDU.

According to one aspect of the present application, there is provided:

the first transceiver receiving a first message, the first message indicating a first expiration value and the first threshold; wherein the first expiration value is used to determine that the first timer expires; the difference of the first expiration value minus the first threshold is used to determine a maximum transmission delay for the first PDCP PDU forwarded through the node where the peer RLC entity of the second candidate RLC entity is located.

Drawings

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

Fig. 1 illustrates a transmission flow diagram of a first node according to one embodiment of the present application;

FIG. 2 illustrates a schematic diagram of a network architecture according to one embodiment of the present application;

fig. 3 illustrates a schematic diagram of a wireless protocol architecture of a user plane and a control plane according to one embodiment of the present application;

FIG. 4 illustrates a hardware module schematic of a communication device according to one embodiment of the present application;

FIG. 5 illustrates a signaling flow diagram according to an embodiment of the present application;

FIG. 6 illustrates another signaling flow diagram according to an embodiment of the present application;

FIG. 7 illustrates a signal processing flow diagram according to an embodiment of the present application;

FIG. 8 illustrates another signal processing flow diagram according to an embodiment of the present application;

fig. 9 illustrates a wireless protocol architecture diagram of relay transmissions according to one embodiment of the present application;

fig. 10 illustrates a schematic diagram of a first PDCP entity, a first candidate RLC entity, and a second candidate RLC entity according to one embodiment of the present application;

FIG. 11 illustrates a topology diagram according to one embodiment of the present application;

fig. 12 illustrates a wireless signal transmission flow diagram according to an embodiment of the present application;

Fig. 13 illustrates a block diagram of a processing arrangement in a first node according to an embodiment of the present application.

Detailed Description

The technical solution of the present application will be further described in detail with reference to the accompanying drawings, and it should be noted that, without conflict, the embodiments of the present application and features in the embodiments may be arbitrarily combined with each other.

Example 1

Embodiment 1 illustrates a transmission flow diagram of a first node according to one embodiment of the present application, as shown in fig. 1.

In embodiment 1, the first node 100 receives a first PDCP SDU in step 101; starting a first timer in step 102 in response to receiving the first PDCP SDU; submitting a first PDCP PDU to a first RLC entity for transmission when the first timer is in an operational state in step 103; the first PDCP PDU is a data unit of the first PDCP SDU processed by the first PDCP entity; the first RLC entity is one of a first candidate RLC entity and a second candidate RLC entity, and the first RLC entity is the first candidate RLC entity or the second candidate RLC entity is related to the value of the first timer; the first candidate RLC entity and the second candidate RLC entity are respectively associated with the first PDCP entity; the data units included in the first candidate RLC entity are sent through a direct connection path; and the data units included in the second candidate RLC entity are sent through a non-direct connection path.

As one embodiment, a first PDCP SDU is received.

As an embodiment, the first PDCP SDU is from a higher layer of the first node.

As an embodiment, a first PDCP entity receives the first PDCP SDU from a higher layer of the first node.

As an embodiment, the higher layer is an SDAP sublayer (sublayer); wherein the first PDCP SDU belongs to a Data Radio Bearer (DRB).

As an embodiment, the higher layer is an RRC sublayer; wherein the first PDCP SDU belongs to a signaling radio bearer (signaling radiobearer, SRB).

In one embodiment, a first timer is started in response to receiving the first PDCP SDU.

As an embodiment, the first timer is maintained at the PDCP sublayer of the first node.

As an embodiment, the first timer is a discard timer.

As one embodiment, the first timer is in an operating state when the first timer starts.

As an embodiment, when the first timer is in an operation state, the first PDCP PDU is submitted to the first RLC entity for transmission.

As an embodiment, the first PDCP SDU and the first PDCP PDU are discarded after the expiration of the first timer.

As a sub-embodiment of the above embodiment, if the first PDCP PDU has been delivered to a lower layer (lower layers), discard is indicated to the lower layer.

As one embodiment, the first PDCP PDU is a PDCP data (data) PDU.

As an embodiment, when the first timer is in an operation state, the first PDCP entity delivers the first PDCP PDU to the first RLC entity for transmission through an inter-layer interface.

As an embodiment, the first PDCP PDU is a data unit of the first PDCP SDU after being processed by the first PDCP entity.

As an embodiment, the processing of the first PDCP SDU at the first PDCP entity includes ROHC (Robust Header Compression ).

As an embodiment, the processing of the first PDCP SDU at the first PDCP entity includes ciphering (ciphering).

As an embodiment, the processing of the first PDCP SDU at the first PDCP entity includes integrity protection and authentication (Integrity protection andverification).

As an embodiment, the first PDCP PDU includes processed bits of the first PDCP SDU.

As an embodiment, the first PDCP PDU is composed of processed bits of the first PDCP SDU and a PDCP header (header).

As an embodiment, the PDCP header includes a Sequence Number (SN) of the first PDCP PDU.

As an embodiment, the first PDCP entity is a transmitting PDCP entity (transmittingPDCP entity).

As an embodiment, the first RLC entity is one of a first candidate RLC entity and a second candidate RLC entity.

As an embodiment, the first candidate RLC entity and the second candidate RLC entity are respectively associated with the first PDCP entity.

As an embodiment, the phrase that the first candidate RLC entity and the second candidate RLC entity are respectively associated with the first PDCP entity comprises: both the first candidate RLC entity and the second candidate RLC entity are used to transmit data units from the first PDCP entity.

As an embodiment, the first PDCP entity is maintained at the first node.

As an embodiment, the first PDCP entity is located in a PDCP sublayer (sublayer).

As an embodiment, the first candidate RLC entity and the second candidate RLC entity are maintained at the first node, respectively.

As an embodiment, the first candidate RLC entity and the second candidate RLC entity are located in RLC sublayers, respectively.

As an embodiment, the first candidate RLC entity and the second candidate RLC entity are in an active state.

As an embodiment, the data units included in the first candidate RLC entity are sent over a direct path.

As an embodiment, the phrase that the first candidate RLC entity includes a data unit transmitted over a direct path includes: the node where the opposite-end RLC entity of the first candidate RLC entity is located is a target receiver of the first PDCP SDU.

As an embodiment, the data units included in the second candidate RLC entity are sent over a non-direct path.

As an embodiment, the phrase that the second candidate RLC entity includes a data unit for transmission over a non-direct path includes: the node of the opposite-end RLC entity of the second candidate RLC entity is not the target receiver of the first PDCP SDU.

As an embodiment, the phrase that the second candidate RLC entity includes a data unit for transmission over a non-direct path includes: and the node where the opposite-end RLC entity of the second candidate RLC entity is located is a relay node of the first PDCP PDU.

As an embodiment, the information element configuring the first candidate RLC entity is RLC-beaderconfig (RLC bearer configuration).

As an embodiment, the first candidate RLC entity is identified by a logical channel identification (Logical Channel Identity, LCID).

As an embodiment, the data processed by the first candidate RLC entity is transmitted on a PUSCH (Physical Uplink SharedChannel ) channel at the physical layer.

As an embodiment, the information element configuring the second candidate RLC entity is SL-RLC-ChannelConfig (sidelink RLC channel configuration).

As an embodiment, the second candidate RLC entity is identified by an RLC channel identity (RLC channel Identity).

As an embodiment, the data processed by the second candidate RLC entity is transmitted over a PSSCH (Physical Sidelink Shared CHannel ) channel at the physical layer.

As an embodiment, the logical channel identity or the RLC channel identity is configured by a base station of a serving cell of the first node.

As an embodiment, a logical channel identity or an RLC channel identity is used to identify an RLC entity at the network side.

As an embodiment, the first candidate RLC entity is used for transmission of the Uu air interface.

As an embodiment, the second candidate RLC entity is used for transmission of the PC5 air interface.

As a sub-embodiment of the above embodiment, the second candidate RLC entity associates a logical channel on the PC5 air interface, the logical channel being allocated by the first node itself.

As an embodiment, whether the first RLC entity is the first candidate RLC entity or the second candidate RLC entity is related to the value of the first timer.

As an embodiment, the value of the first timer is used to determine whether the first RLC entity is the first candidate RLC entity or the second candidate RLC entity.

The above method is applied to the first PDCP PDU being handed over to the RLC entity for the first time.

The above method is applied to each handover when the first PDCP PDU is handed over to the RLC entity multiple times.

As an embodiment, the phrase whether the first RLC entity is the first candidate RLC entity or the second candidate RLC entity is related to the value of the first timer comprises: when the first PDCP PDU is first submitted to the first RLC entity, the first RLC entity is the second candidate RLC entity and the value of the first timer is less than a first threshold; when the first PDCP PDU is first delivered to the first RLC entity, the first RLC entity is the first candidate RLC entity and the value of the first timer is not less than the first threshold.

As an embodiment, the phrase whether the first RLC entity is the first candidate RLC entity or the second candidate RLC entity is related to the value of the first timer comprises: when the first PDCP PDU is first delivered to the first RLC entity, the first RLC entity is the second candidate RLC entity and the value of the first timer is not greater than a first threshold; when the first PDCP PDU is first submitted to the first RLC entity, the first RLC entity is the first candidate RLC entity and the value of the first timer is greater than the first threshold.

As a sub-embodiment of the two embodiments, the second candidate RLC entity belongs to a primary path (primary path).

As an embodiment, the phrase whether the first RLC entity is the first candidate RLC entity or the second candidate RLC entity is related to the value of the first timer comprises: when the first PDCP PDU is first delivered to the first RLC entity, the first RLC entity being one of the first candidate RLC entity or the second candidate RLC entity and the value of the first timer being less than a first threshold; when the first PDCP PDU is first delivered to the first RLC entity, the first RLC entity is the first candidate RLC entity and the value of the first timer is not less than the first threshold.

As an embodiment, the phrase whether the first RLC entity is the first candidate RLC entity or the second candidate RLC entity is related to the value of the first timer comprises: when the first PDCP PDU is first delivered to the first RLC entity, the first RLC entity being one of the first candidate RLC entity or the second candidate RLC entity and the value of the first timer being no greater than a first threshold; when the first PDCP PDU is first submitted to the first RLC entity, the first RLC entity is the first candidate RLC entity and the value of the first timer is greater than the first threshold.

As a sub-embodiment of the two embodiments, the first RLC entity is the first candidate RLC entity or the second candidate RLC entity is the first node implementation related.

As an embodiment, the phrase whether the first RLC entity is the first candidate RLC entity or the second candidate RLC entity is related to the value of the first timer comprises: when the first PDCP PDU is first submitted to the first RLC entity, the first RLC entity is the second candidate RLC entity and the value of the first timer is less than a first threshold; when the first PDCP PDU is delivered again to the first RLC entity, the first RLC entity is the first candidate RLC entity and the value of the first timer is not less than the first threshold.

As an embodiment, the phrase whether the first RLC entity is the first candidate RLC entity or the second candidate RLC entity is related to the value of the first timer comprises: when the first PDCP PDU is first delivered to the first RLC entity, the first RLC entity is the second candidate RLC entity and the value of the first timer is not greater than a first threshold; when the first PDCP PDU is delivered again to the first RLC entity, the first RLC entity is the first candidate RLC entity and the value of the first timer is greater than the first threshold.

As a sub-embodiment of the two embodiments, the second candidate RLC entity belongs to the primary path.

As one embodiment, a first transceiver receives a first PDCP SDU; starting a first timer and a second timer in response to receiving the first PDCP SDU; when the first timer is in an operation state, submitting a first PDCP PDU to a first RLC entity for transmission; the first PDCP PDU is a data unit of the first PDCP SDU processed by the first PDCP entity; the first RLC entity is one of a first candidate RLC entity and a second candidate RLC entity, and whether the first RLC entity is the first candidate RLC entity or the second candidate RLC entity is related to the running state of the first timer and the running state of the second timer; the first candidate RLC entity and the second candidate RLC entity are respectively associated with the first PDCP entity; the data units included in the first candidate RLC entity are sent through a direct connection path; and the data units included in the second candidate RLC entity are sent through a non-direct connection path.

As an embodiment, the running state of the first timer and the running state of the second timer are used to determine whether the first RLC entity is the first candidate RLC entity or the second candidate RLC entity.

As one embodiment, the first RLC entity is the first candidate RLC entity when the first timer is in an on state and the second timer expires.

As an embodiment, the first RLC entity is the second candidate RLC entity when the first timer is in an on state and the second timer is in an on state.

As a sub-embodiment of the above embodiment, the second candidate RLC entity belongs to the primary path.

As an embodiment, when the first timer is in an operating state and the second timer is in an operating state, the first RLC entity is the first candidate RLC entity or the second candidate RLC entity.

As a sub-embodiment of the above embodiment, the first RLC entity is the first candidate RLC entity or the second candidate RLC entity is the first node implementation correlation.

As an embodiment, the expiration value of the first timer is greater than the expiration value of the second timer.

As an embodiment, the expiration value of the first timer indicates a packet delay budget for an end-to-end (peer-to-peer) over an air interface.

As one embodiment, the expiration value of the second timer indicates a point-to-point (point-to-point) packet delay budget over an air interface.

As one embodiment, the expiration value of the second timer indicates a packet delay budget over an air interface.

As an embodiment, the expiration value of the second timer indicates a packet delay budget on a first air interface, wherein the path on which the second candidate RLC entity is located is a non-direct path, the non-direct path comprising at least 2 air interfaces.

Example 2

Embodiment 2 illustrates a network architecture diagram according to one embodiment of the present application, as shown in fig. 2. Fig. 2 illustrates a diagram of a network architecture 200 of NR 5g, LTE (Long-term evolution) and LTE-a (Long-Term EvolutionAdvanced, enhanced Long-term evolution) 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 CoreNetwork)/EPC (EvolvedPacket Core, evolved packet core) 210, hss (Home Subscriber Server )/UDM (Unified Data Management, unified data management) 220, and internet service 230. The 5GS/EPS may interconnect with other access networks, but these entities/interfaces are not shown for simplicity. As shown, 5GS/EPS provides packet switched services, however, those skilled in the art will readily appreciate that the various concepts presented throughout this application may be extended to networks providing circuit switched services or other cellular networks. The NG-RAN includes NR node bs (gnbs) 203 and other gnbs 204. The gNB203 provides user and control plane protocol termination towards the UE 201. The gNB203 may be connected to other gNBs 204 via an Xn interface (e.g., backhaul link). The XnAP protocol of the Xn interface is used to transmit control plane messages of the wireless network and the user plane protocol of the Xn interface is used to transmit user plane data. The gNB203 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), TRP (Transmission Reception Point, transmitting/receiving node), or some other suitable terminology, and in NTN (Non TerrestrialNetwork, non-terrestrial/satellite network) networks, the gNB203 may be a satellite, an aircraft, or a terrestrial base station relayed through a satellite. The gNB203 provides the UE201 with an access point to the 5GC/EPC210. Examples of UEs 201 include a cellular telephone, a smart phone, a session initiation protocol (Session Initiation Protocol, SIP) phone, a laptop, a Personal digital assistant (Personal DigitalAssistant, PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player), a camera, a game console, an drone, an aircraft, a narrowband internet of things device, a machine-type communications device, a land vehicle, an automobile, an in-vehicle device, an in-vehicle communications unit, a wearable device, or any other similar functional device. Those of skill in the art may also refer to the UE201 as a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile 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 terminology. gNB203 is connected to 5GC/EPC210 through an S1/NG interface. The 5GC/EPC210 includes MME (mobility management entity)/AMF (Authentication Management Field, authentication management domain)/SMF (Session Management Function ) 211, other MME/AMF/SMF214, S-GW (Service Gateway)/UPF (User Plane Function), and P-GW (Packet Date Network Gateway, packet data network Gateway)/UPF 213. The MME/AMF/SMF211 is a control node that handles signaling between the UE201 and the 5GC/EPC210. In general, the MME/AMF/SMF211 provides bearer and connection management. All user IP (internet protocol) packets are transported through the S-GW/UPF212, which S-GW/UPF212 itself is connected to the P-GW/UPF213. The P-GW provides UE IP address assignment as well as other functions. The P-GW/UPF213 is connected to the internet service 230. The internet service 230 includes an operator-corresponding internet protocol service, and may specifically include the internet, an intranet, an IMS (IP Multimedia Subsystem ), and a PS (Packet Switching) streaming service.

As an embodiment, the UE201 corresponds to a first node in the present application.

As an embodiment, the gNB203 corresponds to a second node in the present application.

As an embodiment, the UE241 corresponds to a third node in the present application.

As an embodiment, the UE201 is a user equipment.

As an embodiment, the UE241 is a relay node.

As an embodiment, the UE241 is a layer 2 relay node.

As an embodiment, the UE241 is a layer 2U2N relay UE.

As an embodiment, the UE241 is a layer 2U relay UE.

As one example, the gNB203 is a macro Cell (Marco Cell) base station.

As one example, the gNB203 is a Micro Cell (Micro Cell) base station.

As an example, the gNB203 is a Pico Cell (Pico Cell) base station.

As an example, the gNB203 is a home base station (Femtocell).

As an embodiment, the gNB203 is a base station device supporting a large delay difference.

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

As one embodiment, the gNB203 is a satellite device.

As an example, the gNB203 is a test device (e.g., a transceiver device that simulates a base station part function, a signaling tester).

As an embodiment, the radio link from the UE201 to the gNB203 is an uplink, which is used to perform uplink transmission.

As an embodiment, the radio link from the UE241 to the gNB203 is an uplink, which is used to perform uplink transmission.

As an embodiment, the radio link from the gNB203 to the UE201 is a downlink, which is used to perform downlink transmission.

As an embodiment, the radio link from the gNB203 to the UE241 is a downlink, which is used to perform downlink transmission.

As an embodiment, the radio link between the UE201 and the UE241 is a sidelink, which is used to perform sidelink transmission.

As an embodiment, the UE201 and the gNB203 are connected through a Uu air interface.

As an embodiment, the UE241 and the gNB203 are connected through a Uu air interface.

As an embodiment, the UE201 and the UE241 are connected through a PC5 air interface.

Example 3

Embodiment 3 illustrates a schematic diagram of a wireless protocol architecture of a user plane and a control plane according to one embodiment of the present application, as shown in fig. 3. Fig. 3 is a schematic diagram illustrating an embodiment of a radio protocol architecture for a user plane 350 and a control plane 300, fig. 3 shows the radio protocol architecture of the control plane 300 for a UE and a gNB with 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 herein as PHY301. Layer 2 (L2 layer) 305 is above PHY301 and is responsible for the link between the UE and the gNB through PHY301. The L2 layer 305 includes a MAC (MediumAccess Control ) sublayer 302, an RLC (Radio Link Control, radio link layer control protocol) sublayer 303, and a PDCP (Packet Data Convergence Protocol ) sublayer 304, which terminate at the gNB on the network side. The PDCP sublayer 304 provides data ciphering and integrity protection, and the PDCP sublayer 304 also provides handover support for UEs between gnbs. The RLC sublayer 303 provides segmentation and reassembly of data packets, retransmission of lost data packets is achieved through ARQ (Automatic Repeat Request, automatic retransmission request), and the RLC sublayer 303 also provides duplicate data packet detection and protocol error detection. The MAC sublayer 302 provides mapping between logical channels and transport channels and multiplexing of logical channels. The MAC sublayer 302 is also responsible for allocating the various radio resources (e.g., resource blocks) in one cell among the UEs. The MAC sublayer 302 is also responsible for HARQ (Hybrid Automatic RepeatRequest ) 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. The radio protocol architecture of the user plane 350 includes layer 1 (L1 layer) and layer 2 (L2 layer), the radio protocol architecture in the user plane 350 is substantially the same for the physical layer 351, PDCP sublayer 354 in the L2 layer 355, RLC sublayer 353 in the L2 layer 355, and MAC sublayer 352 in the L2 layer 355 as the corresponding layers and sublayers in the control plane 300, but the PDCP sublayer 354 also provides header compression for upper layer data packets to reduce radio transmission overhead. Also included in the L2 layer 355 in the user plane 350 is an SDAP (Service Data Adaptation Protocol ) sublayer 356, the SDAP sublayer 356 being responsible for mapping between QoS flows and data radio bearers (DRBs, data Radio Bearer) to support diversity of traffic. The radio protocol architecture of the UE in the user plane 350 may include some or all of the SDAP sublayer 356, pdcp sublayer 354, rlc sublayer 353 and MAC sublayer 352 at the L2 layer. Although not shown, the UE may also have several upper layers above the L2 layer 355, including a network layer (e.g., IP layer) that terminates at the P-GW on the network side and an application layer that terminates at the other end of the connection (e.g., remote UE, server, etc.).

As an embodiment, the PDCP304 transmits data to the RLC303 or receives data from the RLC303 through an RLC channel.

As an embodiment, the PDCP354 transmits data to the RLC353 or receives data from the RLC353 through an RLC channel.

As an embodiment, the RLC303 transmits data to the MAC302 or receives data from the MAC302 through a logical channel.

For one embodiment, the RLC353 transmits data to the MAC352 or receives data from the MAC352 over a logical channel.

As one embodiment, the MAC302 transmits data to the PHY301 or receives data from the PHY301 through a transmission channel.

As one embodiment, the MAC352 transmits data to the PHY351 or receives data from the PHY351 through a transmission channel.

As an embodiment, the first transceiver is used for inter-layer communication within the first node.

As one embodiment, the inter-layer communication includes communication between two adjacent layers.

As one embodiment, the inter-layer communication includes communication between two non-adjacent layers.

As an embodiment, the inter-layer communication includes inter-layer communication between the first PDCP entity and the first RLC entity.

As an embodiment, the inter-layer communication comprises communication between the higher layer protocol entity and the first PDCP entity.

As one embodiment, the inter-layer communication includes communication between the first RLC entity and a lower layer protocol entity.

As an embodiment, the first transceiver is used by the PDCP304 to transmit to the RLC 303.

As an embodiment, the first transceiver is used by the PDCP304 to receive from the RLC 303.

For one embodiment, the first transceiver is used by the PDCP354 to transmit to the RLC 353.

For one embodiment, the first transceiver is used by the PDCP354 to receive from the RLC 353.

As an embodiment, the first transceiver is used by the RLC303 to transmit to the PDCP 304.

As an embodiment, the first transceiver is used by the RLC303 to receive from the PDCP 304.

For one embodiment, the first transceiver is used by the RLC353 to transmit to the PDCP 354.

For one embodiment, the first transceiver is used by the RLC353 to receive from the PDCP 354.

As an embodiment, the first transceiver includes an inter-layer transceiving primitive.

As one embodiment, the first transceiver includes a set of instructions for performing a transceiving function.

As an example, the entities of the multiple sublayers of the control plane in fig. 3 constitute SRBs in the vertical direction (Signaling Radio Bearer, signaling radio bearers).

As an example, entities of the multiple sublayers of the user plane in fig. 3 constitute a DRB (data radio Bearer) in a vertical direction.

As an example, the entities of the multiple sub-layers of the user plane in fig. 3 constitute an MRB (multicast broadcast service Radio Bearer) in a vertical direction.

As an embodiment, the wireless protocol architecture in fig. 3 is applicable to the first node in the present application.

As an embodiment, the wireless protocol architecture in fig. 3 is applicable to the second node in the present application.

As an embodiment, the wireless protocol architecture in fig. 3 is applicable to the third node in the present application.

As an embodiment, the first PDCP SDU in the present application is generated in the RRC306.

As an embodiment, the first PDCP SDU in the present application is generated in the SDAP356.

As an embodiment, the first PDCP PDU in the present application is generated in the PDCP304.

As an embodiment, the first PDCP PDU in the present application is generated in the PDCP354.

As an embodiment, when the first PDCP PDU is generated in the PDCP304, the first PDCP entity is located in the PDCP304, and the first candidate RLC entity and the second candidate RLC entity are located in the RLC303.

As an embodiment, when the first PDCP PDU is generated in the PDCP354, the first PDCP entity is located in the PDCP354, and the first candidate RLC entity and the second candidate RLC entity are located in the RLC353.

As an embodiment, the PDCP sublayer and the data packets on the RLC sublayer interface are called PDCP PDUs in the PDCP sublayer and RLC SDUs in the RLC sublayer, i.e. the PDCP sublayer delivers PDCP PDUs to the RLC sublayer, which receives RLC SDUs from the PDCP sublayer; the RLC sublayer delivers RLC SDUs to the PDCP sublayer, which receives PDCP PDUs from the RLC sublayer.

As an embodiment, the first PDCP PDU and the first RLC SDU may be interchanged.

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

As an embodiment, the RRC sub-layer 306 in the L3 layer belongs to a higher layer.

Example 4

Embodiment 4 illustrates a hardware module schematic of a communication device according to an embodiment of the present application, as shown in fig. 4. Fig. 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.

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.

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.

In the transmission from the second communication device 410 to the first communication device 450, upper layer packets from the core network or upper layer packets from the data source 477 are provided to the controller/processor 475 at the second communication device 410. The core network and data source 477 represent all 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, a 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 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., physical layer). Transmit processor 416 performs coding and interleaving to facilitate Forward Error Correction (FEC) at the second communication device 410, as well as mapping of signal clusters 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 digitally space-precodes the coded and modulated symbols, including codebook-based precoding and non-codebook-based precoding, and beamforming processing, to generate one or more spatial streams. A transmit processor 416 then maps each spatial stream to a subcarrier, multiplexes with reference signals (e.g., pilots) in the time and/or frequency domain, and then uses an Inverse Fast Fourier Transform (IFFT) to generate a physical channel carrying the time domain multicarrier symbol stream. The multi-antenna transmit processor 471 then performs transmit analog precoding/beamforming operations on the time domain multi-carrier symbol stream. Each transmitter 418 converts the baseband multicarrier symbol stream provided by the multiple antenna transmit processor 471 to a radio frequency stream and then provides it to a different antenna 420.

In a transmission from the second communication device 410 to the first communication device 450, each receiver 454 receives a signal at the first communication device 450 through its respective antenna 452. Each receiver 454 recovers information modulated onto a radio frequency carrier and converts the radio frequency stream into a baseband multicarrier symbol stream that is provided to a receive processor 456. The receive processor 456 and the multi-antenna receive processor 458 implement various signal processing functions for the L1 layer. A multi-antenna receive processor 458 performs receive analog precoding/beamforming operations on the baseband multi-carrier symbol stream from the receiver 454. The receive processor 456 converts the baseband multicarrier symbol stream after receiving the analog precoding/beamforming operation from the time domain to the frequency domain using a Fast Fourier Transform (FFT). In the frequency domain, the physical layer data signal and the reference signal are demultiplexed by the receive processor 456, wherein the reference signal is to be used for channel estimation, and the data signal is subjected to multi-antenna detection in the multi-antenna receive processor 458 to recover any spatial stream destined for the first communication device 450. The symbols on each spatial stream are demodulated and recovered in a receive processor 456 and soft decisions are generated. The receive processor 456 then decodes and deinterleaves the soft decisions to recover the upper layer data and control signals that were 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. 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 higher layer data packets from the second communication device 410. The upper layer packets are then provided to all protocol layers above the L2 layer. Various control signals may also be provided to L3 for L3 processing.

In the transmission from the first communication device 450 to the second communication device 410, an upper layer data packet is provided to a controller/processor 459 at the first communication device 450 using a data source 467. Data source 467 represents all protocol layers above the L2 layer. Similar to the transmit functions 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, implementing L2 layer functions for the user and control planes. The controller/processor 459 is also responsible for retransmission of lost packets and signaling to the second communication device 410. The transmit processor 468 performs modulation mapping, channel coding, and digital multi-antenna spatial precoding, including codebook-based precoding and non-codebook-based precoding, and beamforming, with the multi-antenna transmit processor 457 performing digital multi-antenna spatial precoding, after which the transmit processor 468 modulates the resulting spatial stream into a multi-carrier/single-carrier symbol stream, which is analog precoded/beamformed in the multi-antenna transmit processor 457 before being provided to the different antennas 452 via the transmitter 454. Each transmitter 454 first converts the baseband symbol stream provided by the multi-antenna transmit processor 457 into a radio frequency symbol stream and provides it to an antenna 452.

In the transmission from the first communication device 450 to the second communication device 410, the function at the second communication device 410 is similar to the receiving function 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 radio frequency signals through its corresponding antenna 420, converts the received radio frequency signals to baseband signals, and provides the baseband signals to a multi-antenna receive processor 472 and a receive processor 470. The receive processor 470 and the multi-antenna receive processor 472 collectively implement the functions of the L1 layer. The controller/processor 475 implements L2 layer functions. The controller/processor 475 may be associated with a memory 476 that stores program codes and data. Memory 476 may 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 demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover upper layer data packets from the first communication device 450. Upper layer packets from the controller/processor 475 may be provided to all protocol layers above the core network or L2 layer, and various control signals may also be provided to the core network or L3 for L3 processing.

As an embodiment, the first communication device 450 apparatus includes: at least one processor and at least one memory including computer program code; the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus of the first communication device 450 to at least: receiving a first PDCP SDU; starting a first timer in response to receiving the first PDCP SDU; when the first timer is in an operation state, submitting a first PDCP PDU to a first RLC entity for transmission; the first PDCP PDU is a data unit of the first PDCP SDU processed by the first PDCP entity; the first RLC entity is one of a first candidate RLC entity and a second candidate RLC entity, and the first RLC entity is the first candidate RLC entity or the second candidate RLC entity is related to the value of the first timer; the first candidate RLC entity and the second candidate RLC entity are respectively associated with the first PDCP entity; the data units included in the first candidate RLC entity are sent through a direct connection path; and the data units included in the second candidate RLC entity are sent through a non-direct connection path.

As an embodiment, the first communication device 450 apparatus includes: a memory storing a program of computer-readable instructions that, when executed by at least one processor, produce acts comprising: receiving a first PDCP SDU; starting a first timer in response to receiving the first PDCP SDU; when the first timer is in an operation state, submitting a first PDCP PDU to a first RLC entity for transmission; the first PDCP PDU is a data unit of the first PDCP SDU processed by the first PDCP entity; the first RLC entity is one of a first candidate RLC entity and a second candidate RLC entity, and the first RLC entity is the first candidate RLC entity or the second candidate RLC entity is related to the value of the first timer; the first candidate RLC entity and the second candidate RLC entity are respectively associated with the first PDCP entity; the data units included in the first candidate RLC entity are sent through a direct connection path; and the data units included in the second candidate RLC entity are sent through a non-direct connection path.

As an embodiment, the second communication device 410 apparatus includes: at least one processor and at least one memory including computer program code; the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus of the second communication device 410 to at least: a first message is sent.

As an embodiment, the second communication device 410 apparatus includes: a memory storing a program of computer-readable instructions that, when executed by at least one processor, produce acts comprising: a first message is sent.

As an embodiment, the first communication device 450 corresponds to a first node in the present application.

As an embodiment, the first communication device 450 is a UE.

As an embodiment, the first communication device 450 is a layer 3 relay node.

As an embodiment, the second communication device 410 corresponds to a second node in the present application.

As an embodiment, the second communication device 410 is a base station.

As an embodiment, the second communication device 410 corresponds to a third node in the present application.

As an embodiment, the second communication device 410 is a layer 2 relay node.

As an embodiment, at least one of the antenna 452, the transmitter 454, the multi-antenna receive processor 458, the receive processor 456, or the controller/processor 459 is configured to receive a first PDCP SDU in the present application.

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 submit a first PDCP PDU in the present application.

As one 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 transmit a first indication in this application.

As one embodiment, the antenna 420, the receiver 418, the multi-antenna transmit processor 471, at least one of the transmit processor 416 or the controller/processor 475 is used to send the first message in this application.

As one embodiment, at least one of the antenna 452, the transmitter 454, the multi-antenna receive processor 458, the receive processor 456, or the controller/processor 459 is configured to receive a first message in the present application.

Example 5

Embodiment 5 illustrates a signal transmission flow diagram according to one embodiment of the present application, as shown in fig. 5. In fig. 5, a first PDCP entity E51, a first candidate RLC entity E52 and a second candidate RLC entity E53 are both located at a first node, the first PDCP entity E51 and the first candidate RLC entity E52 communicate through an inter-layer interface, and the first PDCP entity E51 and the second candidate RLC entity E53 communicate through an inter-layer interface.

For the followingFirst PDCP entity E51Receiving a first PDCP SDU in step S511; determining the first RLC entity as a first candidate RLC entity in step S512 a; delivering the first PDCP PDU to the first candidate RLC entity in step S513 a; determining in step S512b that the first RLC entity is a second candidate RLC entity; the first PDCP PDU is delivered to the second candidate RLC entity in step S513 b.

For the followingFirst candidate RLC entity E52The first PDCP PDU is received in step S521.

For the followingSecond candidate RLC entity E53The first PDCP PDU is received in step S531.

It should be noted that, the steps in the dashed box F51 and the dashed box F52 are performed alternatively, i.e., not performed simultaneously.

In embodiment 5, a first PDCP SDU is received; starting a first timer in response to receiving the first PDCP SDU; when the first timer is in an operation state, submitting a first PDCP PDU to a first RLC entity for transmission; the first PDCP PDU is a data unit of the first PDCP SDU processed by the first PDCP entity; the first RLC entity is one of a first candidate RLC entity and a second candidate RLC entity, and the first RLC entity is the first candidate RLC entity or the second candidate RLC entity is related to the value of the first timer; the first candidate RLC entity and the second candidate RLC entity are respectively associated with the first PDCP entity; the data units included in the first candidate RLC entity are sent through a direct connection path; the data units included in the second candidate RLC entity are sent through a non-direct connection path; when the value of the first timer is greater than a first threshold, the first RLC entity is the first candidate RLC entity; when the value of the first timer is less than a first threshold, whether the first RLC entity is the first candidate RLC entity or the second candidate RLC entity is related to a reference amount of data; wherein the reference data amount is a total amount of PDCP data amount in the first PDCP entity and RLC data amount waiting for initial transmission (initial transmission) in the first candidate RLC entity and the second candidate RLC entity.

As an embodiment, the first RLC entity is the first candidate RLC entity when the value of the first timer is greater than a first threshold.

As an embodiment, the first RLC entity is the first candidate RLC entity when the value of the first timer is equal to the first threshold.

As an embodiment, the first RLC entity is the second candidate RLC entity when the value of the first timer is less than the first threshold.

As an embodiment, the first RLC entity is the second candidate RLC entity when the value of the first timer is equal to the first threshold.

As an embodiment, the first RLC entity is one of the first candidate RLC entity or the second candidate RLC entity when the value of the first timer is less than the first threshold.

As an embodiment, the first RLC entity is one of the first candidate RLC entity or the second candidate RLC entity when the value of the first timer is equal to the first threshold.

As a sub-embodiment of the above two embodiments, the first node selects the first RLC entity as the first candidate RLC entity or the second candidate RLC entity by itself.

As a sub-embodiment of the above two embodiments, the first node equiprobability selects the first RLC entity as the first candidate RLC entity or the second candidate RLC entity.

As an embodiment, when the value of the first timer is less than the first threshold, the first RLC entity is the first candidate RLC entity or the second candidate RLC entity is related to a reference amount of data.

As an embodiment, the first RLC entity is the first candidate RLC entity or the second candidate RLC entity is related to a reference data amount when the value of the first timer is equal to the first threshold.

As an embodiment, the reference data amount is used to determine whether the first RLC entity is the first candidate RLC entity or the second candidate RLC entity when the value of the first timer is less than the first threshold.

As an embodiment, the reference data amount is used to determine whether the first RLC entity is the first candidate RLC entity or the second candidate RLC entity when the value of the first timer is equal to the first threshold.

As a sub-embodiment of the four embodiments described above, the first node is configured with a secondary RLC entity (secondary RLC entity).

As an embodiment, when the value of the first timer is less than the first threshold and the reference data amount is less than a second threshold, the first RLC entity is a primary RLC entity (primary RLC entity) which is one of the first candidate RLC entity or the second candidate RLC entity.

As an embodiment, when the value of the first timer is equal to the first threshold and the reference data amount is less than the second threshold, the first RLC entity is a primary RLC entity, which is one of the first candidate RLC entity or the second candidate RLC entity.

As an embodiment, one of the first candidate RLC entity or the second candidate RLC entity is configured by a network to be the primary RLC entity, and the other of the first candidate RLC entity or the second candidate RLC entity is configured to be a secondary RLC entity.

As a sub-embodiment of the foregoing embodiment, the first candidate RLC entity is the primary RLC entity, and the second candidate RLC entity is the secondary RLC entity.

As a sub-embodiment of the foregoing embodiment, the first candidate RLC entity is the secondary RLC entity, and the second candidate RLC entity is the primary RLC entity.

As an embodiment, the primary RLC entity belongs to the primary path.

As an embodiment, the secondary RLC entity belongs to a non-primary path.

As an embodiment, the secondary RLC entity belongs to a secondary path (secondary path).

As an embodiment, the secondary RLC entity is a split secondary RLC entity (split secondaryRLC entity).

As an embodiment, the first RLC entity is one of the first candidate RLC entity or the second candidate RLC entity when the value of the first timer is less than the first threshold and the reference data amount is not less than the second threshold.

As an embodiment, when the value of the first timer is equal to the first threshold and the reference data amount is not less than the second threshold, the first RLC entity is one of the first candidate RLC entity or the second candidate RLC entity.

As an embodiment, the second threshold is configured by the network.

As an embodiment, the second threshold is preconfigured.

As an embodiment, the second threshold is configured to split bearers.

As an embodiment, the second threshold is configured to PDCP entities associated with a plurality of RLC entities.

As an embodiment, the second threshold is configured to the first PDCP entity.

As an embodiment, the second threshold is indicated by ul-datasplit threshold.

As an embodiment, the reference data amount is a total amount of PDCP data amount in the first PDCP entity and RLC data amounts waiting for initial transmission (initial transmission) in the first candidate RLC entity and the second candidate RLC entity.

As an embodiment, the PDCP data amount in the first PDCP entity includes a data amount of PDCP SDUs for which PDCP data PDUs have not been constructed.

As an embodiment, the PDCP data amount in the first PDCP entity includes a data amount of PDCP data PDUs that have not been delivered to a lower layer.

As an embodiment, the PDCP data amount in the first PDCP entity includes a data amount of PDCP SDUs to be retransmitted; wherein the first PDCP entity is used for AM (acknowledgement mode) DRB.

As an embodiment, the PDCP data amount in the first PDCP entity includes a data amount of PDCP data PDUs to be retransmitted; wherein the first PDCP entity is used for AM DRBs.

As an embodiment, the PDCP data size in the first PDCP entity includes a PDCP control PDU data size.

As an embodiment, the RLC data amounts awaiting initial transmission (initial transmission) in the first candidate RLC entity and the second candidate RLC entity respectively include the data amounts of RLC SDU and RLC SDU segments that have not been included in RLC data PDUs.

As an embodiment, the RLC data amounts waiting for initial transmission (initial transmission) in the first candidate RLC entity and the second candidate RLC entity respectively include RLC data PDUs waiting for initial transmission.

As an embodiment, the RLC data amounts waiting for initial transmission (initial transmission) in the first candidate RLC entity and the second candidate RLC entity respectively include an estimated data amount of STATUS PDUs; wherein the STATUS PDU has been activated and the t-STATUS pro hitib (STATUS prohibit timer) is not running or not expired.

Example 6

Embodiment 6 illustrates another signaling flow diagram according to one embodiment of the present application, as shown in fig. 6. In fig. 6, a first PDCP entity E61, a first candidate RLC entity E62 and a second candidate RLC entity E63 are both located at a first node, the first PDCP entity E61 and the first candidate RLC entity E62 communicate through an inter-layer interface, and the first PDCP entity E61 and the second candidate RLC entity E63 communicate through an inter-layer interface.

For the followingFirst PDCP entity E61Receiving a first PDCP SDU in step S611; determining in step S612 that the first RLC entity is a second candidate RLC entity; delivering the first PDCP PDU to the second candidate RLC entity in step S613; determining in step S614 that the value of the first timer is greater than a first threshold and that the first timer has not expired, determining that no indication of successful transmission of the first PDCP PDU has been received from the second candidate RLC entity; determining in step S615 that the first RLC entity is a first candidate RLC entity; delivering the first PDCP PDU to the first candidate RLC entity in step S616; the first indication is sent in step S617.

For the followingFirst candidate RLC entity E62The first PDCP PDU is received in step S621.

For the followingSecond candidate RLC entity E63Receiving a first PDCP PDU in step S631; receiving a first indication in step S632; the first RLC SDU is discarded in step S633.

In embodiment 6, a first PDCP SDU is received; starting a first timer in response to receiving the first PDCP SDU; when the first timer is in an operation state, submitting a first PDCP PDU to a first RLC entity for transmission; the first PDCP PDU is a data unit of the first PDCP SDU processed by the first PDCP entity; the first RLC entity is one of a first candidate RLC entity and a second candidate RLC entity, and the first RLC entity is the first candidate RLC entity or the second candidate RLC entity is related to the value of the first timer; the first candidate RLC entity and the second candidate RLC entity are respectively associated with the first PDCP entity; the data units included in the first candidate RLC entity are sent through a direct connection path; the data units included in the second candidate RLC entity are sent through a non-direct connection path; delivering the first PDCP PDU to the first candidate RLC entity for transmission; wherein the value of the first timer is greater than the first threshold and the first timer has not expired; the first PDCP entity not receiving an indication of successful transmission of the first PDCP PDU from the second candidate RLC entity; the first RLC entity is the second candidate RLC entity; transmitting a first indication, the first indication being used to instruct the first RLC entity to discard the first PDCP PDU; discarding the first RLC SDU when neither the first RLC SDU nor the segmentation of the first RLC SDU is delivered to the lower layer; wherein the first RLC SDU is the first PDCP PDU.

It should be noted that the steps in the dashed box F61 are only performed when the first RLC SDU or the segmentation of said first RLC SDU is not delivered to the lower layer.

As an embodiment, the phrase whether the first RLC entity is the first candidate RLC entity or the second candidate RLC entity is related to the value of the first timer comprises: the first RLC entity is the second candidate RLC entity; when the value of the first timer is greater than the first threshold and the first timer has not expired and the first PDCP entity has not received an indication from the second candidate RLC entity that the first PDCP PDU was successfully transmitted, the first PDCP PDU is submitted to the first candidate RLC entity for transmission.

As an embodiment, the phrase whether the first RLC entity is the first candidate RLC entity or the second candidate RLC entity is related to the value of the first timer comprises: the first RLC entity is the second candidate RLC entity; when the value of the first timer is not less than the first threshold and the first timer is not expired and the first PDCP entity does not receive an indication from the second candidate RLC entity that the first PDCP PDU was successfully transmitted, the first PDCP PDU is handed over to the first candidate RLC entity for transmission.

As one embodiment, a first PDCP SDU is received, and a first timer is started in response to receiving the first PDCP SDU; when the first timer is in an operation state, submitting a first PDCP PDU to a second candidate RLC entity to send the first PDCP PDU; when the value of the first timer is greater than the first threshold and the first timer has not expired, and the first PDCP entity has not received an indication from the second candidate RLC entity that the first PDCP PDU was successfully transmitted, the first PDCP PDU is handed over to the first candidate RLC entity for transmission.

As an embodiment, the second candidate RLC entity is an AM (acknowledged mode) RLC entity, and the first PDCP entity receives an indication (indication) of successfully transmitted PDCP PDUs from the second candidate RLC entity, the indication including a sequence number of the successfully transmitted PDCP PDUs.

As an embodiment, one PDCP data PDU includes one PDCP sequence number.

As an embodiment, the PDCP sequence number is a non-negative integer.

As one embodiment, the second candidate RLC entity sends a poll (poll) to a peer RLC entity of the second candidate RLC entity, the poll being used to trigger the peer RLC entity feedback STATUS (STATUS) PDU of the second candidate RLC entity; the status PDU indicates whether one RLC SDU or a part of one RLC SDU is successfully transmitted.

As an embodiment, a status PDU is received from the peer RLC entity of the second candidate RLC entity, the second candidate RLC entity indicating successful transmission of one RLC SDU to the first PDCP entity when the status PDU indicates a positive acknowledgement (positive acknowledgement) for the one RLC SDU.

As an embodiment, the peer RLC entity of the second candidate RLC entity is located at a node other than the first node.

As an embodiment, the first node is not co-located with a node other than the first node.

As an embodiment, the peer RLC entity of the second candidate RLC entity is located at a third node in the present application.

As an embodiment, the first node and the third node are connected via an air interface.

As an embodiment, the air interface is Uu.

As an example, the air interface is a PC5.

As an embodiment, the first node and a node other than the first node are connected by a wired link.

As an embodiment, the second candidate RLC entity is an AM (acknowledged mode) RLC entity.

As an embodiment, the second candidate RLC entity is composed of a transmitting side (transmitting side) and a receiving side (receiving side).

As one embodiment, the phrase delivering the first PDCP PDU to the first candidate RLC entity for transmission includes: duplicate the first PDCP PDU and submit the first PDCP PDU to the first candidate RLC entity for transmission.

As an embodiment, the first candidate RLC entity is an AM RLC entity.

As an embodiment, the first candidate RLC entity is a UM (unacknowledged mode) RLC entity.

As an embodiment, the first candidate RLC entity is a TM (transparent mode) RLC entity.

As an embodiment, the first candidate RLC entity consists of a transmitting side and a receiving side.

As an embodiment, the first candidate RLC entity is configured to transmit an RLC entity.

As one embodiment, a first indication is sent, the first indication being used to instruct the first RLC entity to discard the first PDCP PDU; wherein the first RLC entity is the second candidate RLC entity.

As an embodiment, the first indication is an inter-layer indication.

As an embodiment, the first PDCP entity sends the first indication to the first RLC entity; wherein the first RLC entity is the second candidate RLC entity.

As an embodiment, the first indication comprises a sequence number of the first PDCP PDU.

As an embodiment, the second candidate RLC entity discards the first RLC SDU when neither the first RLC SDU nor a segment (segment) of the first RLC SDU is delivered to a lower layer; wherein the first RLC SDU is the first PDCP PDU.

As an embodiment, the phrase that the first RLC SDU is the first PDCP PDU includes: the first RLC SDU is a duplicate (duplicate) of the first PDCP PDU.

As an embodiment, the lower layer is a layer below the RLC sublayer.

As an embodiment, the lower layer is a MAC (MediumAccess Control ) sub-layer.

As an embodiment, the segmentation of the first RLC SDU includes at least 1 bit (bit) of the first RLC SDU.

As an embodiment, when receiving the first indication, the second candidate RLC entity discards the RLC SDU indicated by the first indication if neither the first RLC SDU nor the segmentation of the first RLC SDU is delivered to the lower layer.

As an embodiment, when a logical channel corresponding to the second candidate RLC entity is scheduled, data transmitted through the second candidate RLC entity is transferred to the lower layer.

As an embodiment, after the first RLC SDU is processed by the second candidate RLC entity, the first RLC SDU is delivered to the lower layer.

Example 7

Embodiment 7 illustrates a signal processing flow diagram according to one embodiment of the present application, as shown in fig. 7. The steps of fig. 7 are performed at the first node.

In fig. 7, a first PDCP SDU is received in step S701; starting a first timer in step S702; delivering the first PDCP PDU to the second candidate RLC entity for transmission in step S703; in step S704, it is determined whether the value of the first timer is greater than a first threshold, if yes, step S705 is executed, and if no, step S704 is skipped; in step S705, it is determined whether an indication of successful transmission of the first PDCP PDU is received, if yes, the process proceeds to step S708, if no, the process proceeds to step S706; delivering the first PDCP PDU to the first candidate RLC entity for transmission in step S706; the second candidate RLC entity is instructed to discard the first PDCP PDU in step S707.

As an embodiment, the steps in fig. 7 are performed at the first PDCP entity.

Example 8

Embodiment 8 illustrates another signal processing flow diagram according to one embodiment of the present application, as shown in fig. 8. The steps of fig. 8 are performed at the first node.

In fig. 8, a first RLC SDU is received in step S801; receiving a first indication in step S802; in step S803, it is determined whether the first RLC SDU or the segmentation of the first RLC SDU is delivered to a lower layer, if yes, step S805 is skipped, and if no, step S804 is performed; the first RLC SDU is discarded in step S804.

As an embodiment, the steps in fig. 8 are performed at the second candidate RLC entity.

As an embodiment, the first RLC SDU is the first PDCP PDU.

As an embodiment, discarding the first RLC SDU is discarded when the first RLC SDU or a segment of the first RLC SDU is delivered to a lower layer.

Example 9

Embodiment 9 illustrates a wireless protocol architecture diagram of relay transmission according to one embodiment of the present application, as shown in fig. 9.

In fig. 9, in relay transmission, taking an example in which data is transmitted from a first node to a second node through a third node (data is equally available from the second node through the third node to the first node): the first target data sequentially passes through Uu-PDCP sublayer 905, PC5-SRAP (sidelink relay adaptation protocol) sublayer 904 and PC5-RLC sublayer 903 at the first node side, generates a first target MAC PDU at PC5-MAC sublayer 902, then transmits the first target MAC PDU to PC5-PHY layer 901, then transmits the first target PDU to PC5-PHY layer 911 of the third node through a PC5 air interface, and then sequentially passes through PC5-MAC sublayer 912 and PC5-RLC sublayer 913 to recover the first RLC data; the first RLC data is processed by the PC5-SRAP sublayer 914 and the Uu-SRAP sublayer 924, then regenerated into second RLC data in the Uu-RLC sublayer 923, processed by the Uu-MAC sublayer 922, then generated into a second target MAC PDU, and transmitted to the Uu-PHY layer 921; then transmitted to the Uu-PHY layer 931 of the second node through the Uu air interface, the second target MAC PDU is recovered through the Uu-MAC sublayer 932, and then the first target data is recovered through the processing of the Uu-RLC sublayer 933, the Uu-SRAP sublayer 934 and the Uu-PDCP sublayer 935 in sequence.

The third node in fig. 9 is a layer 2U2N relay node.

In fig. 9, data forwarded at the third node is processed by the MAC sublayer, RLC sublayer and SRAP sublayer but not by the PDCP sublayer; the PC5 air interface is an air interface between said first node and said third node, PC5 interface related protocol entities PC5-SRAP904 and PC5-SRAP914, PC5-RLC903 and PC5-RLC913, PC5-MAC902 and PC5-MAC912, PC5-PHY901 and PC5-PHY911 terminate at said first node and said third node, respectively; the Uu air interface is an air interface between the third node and the second node, protocol entities Uu-SRAP924 and Uu-SRAP934, uu-RLC923 and Uu-RLC933, uu-MAC922 and Uu-MAC932, uu-PHY921 and Uu-PHY931 terminating in the third node and the second node, respectively; the higher layer protocol entities Uu-RRC/SDAP906 and Uu-RRC/SDAP936, uu-PDCP905 and Uu-PDCP935 terminate at the first node and the second node, respectively.

As an embodiment, the PC5-SRAP904 is an opposite SRAP entity of the PC5-SRAP 914.

As an embodiment, the Uu-SRAP924 is a peer SRAP entity of the Uu-SRAP 934.

As an embodiment, the PC5-RLC903 is a peer RLC entity of the PC5-RLC 913.

As an embodiment, the Uu-RLC923 is a peer RLC entity of the Uu-RLC 933.

As an embodiment, the Uu-PDCP905 is a peer PDCP entity of the Uu-PDCP 935.

As an embodiment, the first PDCP entity is the Uu-PDCP905, the second candidate RLC entity is the PC5-RLC903, and the peer RLC entity of the second candidate RLC entity is the PC5-RLC913.

As an embodiment, the second candidate RLC entity is located at the first node, and the peer RLC entity of the second candidate RLC entity is located at the third node.

As an embodiment, the first candidate RLC entity is located at a first node, and the RLC entity at the opposite end of the first candidate RLC entity is located at a second node.

As one embodiment, for layer 2 relay transmission, the RLC sublayer, MAC sublayer and PHY (physical) layer are responsible for point-to-point (point-to-point) communication per hop (hop); the PDCP sublayer and the RRC/SDAP sublayer are responsible for end-to-end (peer-to-peer) communications.

As an embodiment, the SRAP sublayer implements UE ID (user equipment identity) and bearer identity decisions.

As an example, the SRAP sublayer implements RLC channel (egress RLC channel) decisions.

As one embodiment, the SRAP sublayer implements a Bearer mapping (bearder mapping) function.

As one embodiment, the SRAP sublayer implements Routing (Routing) functionality.

In fig. 9, the routing function sends a packet from the first node to the second node.

In fig. 9, the second node is an NG-RAN node, and the first node is a UE.

As an embodiment, the first node in fig. 9 corresponds to the UE201 in embodiment 2.

As an embodiment, the third node in fig. 9 corresponds to the UE241 in embodiment 2

As an embodiment, the second node in fig. 9 corresponds to the gNB203 in embodiment 2.

Example 10

Embodiment 10 illustrates a first PDCP entity, a first candidate RLC entity and a second candidate RLC entity according to one embodiment of the present application, as illustrated in fig. 10. In fig. 10, the first PDCP entity, the first candidate RLC entity and the second candidate RLC entity are both located at the first node.

As an embodiment, the first PDCP entity is associated with a first radio bearer.

As an embodiment, the bearers served by the first candidate RLC entity and the second candidate RLC entity are the first radio bearers, and the first PDCP entity is used to transmit data of the first radio bearers.

As an embodiment, the first radio bearer is a DRB or SRB or MRB.

As an embodiment, the protocol structure shown in fig. 10 is used for the first radio bearer.

As an embodiment, the first radio bearer is configured as a split bearer (split bearer).

As an example, the higher layer protocol entity in fig. 10 is RRC and fig. 8 is for SRB.

As an example, the higher layer protocol entity in fig. 10 is an SDAP, and fig. 8 is for a DRB or MRB.

As an embodiment, the first PDCP entity is configured PDCP restoration (recovery).

As an embodiment, the first PDCP entity being configured to PDCP restoration includes: the PDCP PDU is delivered by the first PDCP entity to the first candidate RLC entity for transmission when the second candidate RLC entity does not successfully transmit RLC SDUs within the duration indicated by the first threshold.

As an embodiment, PDCP PDUs formed by processing PDCP SDUs received from a higher layer protocol entity by the first PDCP entity are transmitted by one of the first candidate RLC entity or the second candidate RLC entity.

As an embodiment, the first candidate RLC entity is for uplink communications and the second candidate RLC entity is for sidelink communications.

As a sub-embodiment of the above embodiment, the first radio bearer is an uplink radio bearer.

As one embodiment, the first candidate RLC entity is for sidelink direct path communication and the second candidate RLC entity is for sidelink non-direct path communication

As a sub-embodiment of the above embodiment, the first radio bearer is a sidelink radio bearer (SidelinkRadio Bearer, SLRB).

Example 11

Embodiment 11 illustrates a schematic topology according to one embodiment of the present application, as shown in fig. 11.

As an embodiment, the first node is configured with multiple paths, which include one direct path (directpath) and one non-direct path (directpath).

As an embodiment, the direct path refers to data transmission from the source node to the destination receiver over only one air interface.

As an embodiment, the non-direct path refers to data transmission from a source node to a destination receiver over at least two air interfaces.

As an embodiment, the at least two air interfaces comprise a Uu air interface and a PC5 air interface.

As an embodiment, the at least two air interfaces comprise at least two PC5 air interfaces.

As one embodiment, the at least two air interfaces include a backhaul (backhaul) air interface and an Access (Access) air interface.

As one embodiment, the communication between the first node and the second node is a non-direct path when forwarded through the third node.

As an embodiment, the communication between the first node and the second node is a direct path when not forwarded through the third node.

As a sub-embodiment of the above two embodiments, the non-direct path is a main path.

As a sub-embodiment of the above two embodiments, the direct path is a main path.

As an embodiment, the first node is a UE.

As an embodiment, the third node is shown as a layer 2 relay node.

As an embodiment, the third node shown is a layer 2U2N relay UE.

As an embodiment, the third node and the first node belong to the same cell group.

As an embodiment, the third node and the first node belong to different cell groups.

As an embodiment, the second node is an NG-RAN node.

As an embodiment, the first node in fig. 11 corresponds to the UE201 in embodiment 2.

As an embodiment, the third node in fig. 11 corresponds to the UE241 in embodiment 2

As an embodiment, the second node in fig. 11 corresponds to the gNB203 in embodiment 2.

Example 12

Embodiment 12 illustrates a wireless signal transmission flow diagram according to one embodiment of the present application, as shown in fig. 12. In fig. 12, the first node and the second node communicate via the Uu air interface, the first node and the third node communicate via the PC5 air interface, and the third node and the second node communicate via the Uu air interface.

For the followingFirst node N121Receiving a first message in step S1211 a; the first message is received in step S1211 b.

For the followingSecond node N122Transmitting a first message in step S1221 a; the first message is sent in step S1221 b.

It should be noted that the steps in the dashed box F121 and the dashed box F122 are alternatively performed.

It should be noted that, the first message in the dashed box F121 is transmitted through a direct connection path, and the first message in the dashed box F122 is transmitted through a non-direct connection path, that is, through relay forwarding.

Although not shown in detail, the steps in the dashed box F122 include the third node receiving the first message from the second node, and forwarding the first message to the first node.

As an embodiment, the second node is a base station of a serving cell of the first node.

As an embodiment, the second node is a TRP of a serving cell of the first node.

As an embodiment, the serving cell belongs to a primary cell group (master cell group).

As an embodiment, the serving cell belongs to a secondary cell group (secondary cell group).

As an embodiment, the serving Cell is a Primary Cell (Primary Cell).

As an embodiment, the serving Cell is a Secondary Cell.

As one embodiment, the first transceiver receives a first message indicating a first expiration value and the first threshold; wherein the first expiration value is used to determine that the first timer has expired.

As an embodiment, the first message is a higher layer message.

As an embodiment, the first message is RRC (Radio Resource Control ) signaling.

As an embodiment, the first message includes all or part of an IE (information element) in one RRC signaling.

As an embodiment, the first message includes all or part of a field (field) in an IE in one RRC signaling.

As an embodiment, the first message includes configuration information of the first PDCP entity.

As an embodiment, the first message indicates a first expiration value and the first threshold value.

As an embodiment, the first message comprises a first sub-message and a second sub-message, the first sub-message and the second sub-message indicating the first expiration value and the first threshold value, respectively.

As an embodiment, the first sub-message and the second sub-message respectively include all or part of an IE (information element) in one RRC signaling.

As an embodiment, the first sub-message and the second sub-message respectively include all or part of a field (field) in one IE in one RRC signaling.

As one embodiment, the first message is received from the air interface.

As one embodiment, when the first message is received through a direct path, the first message is received through a PDSCH (Physical Downlink SharedCHannel ) channel; when the first message is received through a non-direct path, the first message is received through a PSSCH channel.

As one embodiment, the first expiration value is used to determine that the first timer has expired.

As one embodiment, when the first timer is in the running state, the first timer is updated in a next time interval, and then it is determined whether the first timer expires.

As an embodiment, the one time interval comprises 1 millisecond.

As an embodiment, the one time interval includes a time length of 1 slot (slot).

As an embodiment, the one time interval includes a time length of 1 subframe (subframe).

As one embodiment, setting the value of the first timer to 0 when the first timer is started, and the phrase updating the first timer includes: adding 1 to the value of the first timer; the first timer expires when the value of the first timer is the first expiration value.

As an embodiment, the first expiration value is used to determine a maximum residence time of the first PDCP SDU at the first PDCP entity.

As one embodiment, the first expiration value is used to determine a remaining packet delay budget (remainingpacket delaybudget).

As one embodiment, in employing mode 2 (mode 2) resource allocation, the first expiration value is used for resource selection.

As a sub-embodiment of the above embodiment, the first expiration value is used to determine a duration indicated by a maximum value of the resource selection window.

As an embodiment, the difference of the first expiration value minus the first threshold is used to determine a maximum transmission delay for the first PDCP PDU to be forwarded through the node where the peer RLC entity of the second candidate RLC entity is located.

As an embodiment, the difference obtained by subtracting the first threshold from the first expiration value is the maximum transmission delay of the first PDCP PDU forwarded by the node where the peer RLC entity of the second candidate RLC entity is located.

As an embodiment, the difference of the first expiration value minus the first threshold is not smaller than the maximum transmission delay forwarded by the first PDCP PDU through the node where the peer RLC entity of the second candidate RLC entity is located.

As an embodiment, the difference of the first expiration value minus the first threshold is greater than a maximum transmission delay forwarded by the first PDCP PDU through a node where a peer RLC entity of the second candidate RLC entity is located.

As one embodiment, the second node divides the transmission delay of the data unit of the first radio bearer between the first node and the second node into a sum of two transmission delays, wherein the first part is the transmission delay between the first node and the third node, the second part is the transmission delay between the third node and the second node, and the sum of the two transmission delays is not greater than the time length indicated by the first expiration value; the transmission delay between the first node and the third node is not greater than a length of time indicated by the first threshold.

As an embodiment, the node where the peer RLC entity of the second candidate RLC entity is located is the third node.

As an embodiment, the node where the opposite RLC entity of the second candidate RLC entity is located is a relay node.

As an embodiment, the node where the opposite RLC entity of the second candidate RLC entity is located is a layer 2U2N relay UE.

As one embodiment, the expiration value of the first timer is the first expiration value.

As one embodiment, the expiration value of the second timer is the first threshold.

Example 13

Embodiment 13 illustrates a block diagram of a processing device in a first node according to one embodiment of the present application, as shown in fig. 13.

In fig. 13, a first node processing apparatus 1300 includes a first transceiver 1301. The first node 1300 is a UE.

In embodiment 13, a first transceiver 1301 receives a first PDCP SDU; starting a first timer in response to receiving the first PDCP SDU; when the first timer is in an operation state, submitting a first PDCP PDU to a first RLC entity for transmission; the first PDCP PDU is a data unit of the first PDCP SDU processed by the first PDCP entity; the first RLC entity is one of a first candidate RLC entity and a second candidate RLC entity, and the first RLC entity is the first candidate RLC entity or the second candidate RLC entity is related to the value of the first timer; the first candidate RLC entity and the second candidate RLC entity are respectively associated with the first PDCP entity; the data units included in the first candidate RLC entity are sent through a direct connection path; and the data units included in the second candidate RLC entity are sent through a non-direct connection path.

As an embodiment, the first RLC entity is the first candidate RLC entity when the value of the first timer is greater than a first threshold; when the value of the first timer is less than the first threshold, whether the first RLC entity is the first candidate RLC entity or the second candidate RLC entity is related to a reference amount of data; wherein the reference data amount is a total amount of PDCP data amount in the first PDCP entity and RLC data amount waiting for initial transmission (initial transmission) in the first candidate RLC entity and the second candidate RLC entity.

As an embodiment, the first RLC entity is the first candidate RLC entity when the value of the first timer is greater than a first threshold; the first transceiver 1301 delivers the first PDCP PDU to the first candidate RLC entity for transmission; wherein the value of the first timer is greater than the first threshold and the first timer has not expired; the first PDCP entity not receiving an indication of successful transmission of the first PDCP PDU from the second candidate RLC entity; the first RLC entity is the second candidate RLC entity.

As an embodiment, the first RLC entity is the first candidate RLC entity when the value of the first timer is greater than a first threshold; the first transceiver 1301 delivers the first PDCP PDU to the first candidate RLC entity for transmission; wherein the value of the first timer is greater than the first threshold and the first timer has not expired; the first PDCP entity not receiving an indication of successful transmission of the first PDCP PDU from the second candidate RLC entity; the first RLC entity is the second candidate RLC entity; the first transceiver 1301 transmits a first indication, which is used to instruct the first RLC entity to discard the first PDCP PDU; discarding the first RLC SDU when neither the first RLC SDU nor the segmentation of the first RLC SDU is delivered to the lower layer; wherein the first RLC SDU is the first PDCP PDU.

As an embodiment, the direct path comprises only one air interface and the non-direct path comprises at least two air interfaces.

As an embodiment, the first transceiver 1301 receives a first message, which indicates a first expiration value and the first threshold value; wherein the first expiration value is used to determine that the first timer expires; the difference of the first expiration value minus the first threshold is used to determine a maximum transmission delay for the first PDCP PDU forwarded through the node where the peer RLC entity of the second candidate RLC entity is located.

The first transceiver 1301 includes, as an example, a receiver 454 (including an antenna 452), a receive processor 456, a multi-antenna receive processor 458, and a controller/processor 459 of fig. 4 of the present application.

As an example, the first transceiver 1301 includes at least one of the receiver 454 (including the antenna 452), the receiving processor 456, the multi-antenna receiving processor 458, or the controller/processor 459 of fig. 4 of the present application.

As an example, the first transceiver 1301 includes a receiver 454 (including an antenna 452), a transmission processor 468, a multi-antenna transmission processor 457, and a controller/processor 459 in fig. 4 of the present application.

As an example, the first transceiver 1301 includes at least one of the receiver 454 (including the antenna 452), the transmission processor 468, the multi-antenna transmission processor 457, or the controller/processor 459 in fig. 4 of the present application.

As an example, the first transceiver 1301 includes the controller/processor 459 of fig. 4 of the present application.

Those of ordinary skill in the art will appreciate that all or a portion of the steps of the above-described methods may be implemented by a program that instructs associated hardware, and the program may be stored on a computer readable storage medium, such as a read-only memory, a hard disk or an optical disk. Alternatively, all or part of the steps of the above embodiments may be implemented using one or more integrated circuits. Accordingly, each module unit in the above embodiment may be implemented in a hardware form or may be implemented in a software functional module form, and the application is not limited to any specific combination of software and hardware. The first type of communication node or UE or terminal in the present application includes, but is not limited to, a mobile phone, a tablet computer, a notebook, an internet card, a low power device, an eMTC (enhancedMachine Type Communication ) device, an NB-IoT device, a vehicle-mounted communication device, an aircraft, an airplane, an unmanned plane, a remote control plane, and other wireless communication devices. The second type of communication node or base station or network side device in the present application includes, but is not limited to, a macro cellular base station, a micro cellular base station, a home base station, a relay base station, an eNB, a gNB, a transmission receiving node TRP (Transmission and Reception Point, a transmitting and receiving point), a relay satellite, a satellite base station, an air base station, a test device, for example, a transceiver device simulating a function of a base station part, a signaling tester, and other wireless communication devices.

It will be appreciated by those skilled in the art that the invention can be embodied in other specific forms without departing from the spirit or essential characteristics thereof. Accordingly, the presently disclosed embodiments are considered in all respects to be illustrative and not restrictive. The scope of the invention is indicated by the appended claims rather than by the foregoing description, and all changes that come within the meaning and range of equivalents are intended to be embraced therein.

Claims

1. A first node for wireless communication, comprising:

a first transceiver that receives a first PDCP SDU; starting a first timer in response to receiving the first pdcsdu; when the first timer is in an operation state, delivering the first PDCPDU to a first RLC entity for transmission;

2. The first node of claim 1, wherein the first RLC entity is the first candidate RLC entity when the value of the first timer is greater than a first threshold.

3. The first node of claim 2, wherein the first RLC entity is the first candidate RLC entity or the second candidate RLC entity is related to a reference amount of data when the value of the first timer is less than the first threshold;

4. The first node of claim 2, comprising:

wherein the value of the first timer is greater than the first threshold and the first timer has not expired; the first PDCP entity does not receive an indication from the second candidate RLC entity that the first PDCP pdu was successfully transmitted; the first RLC entity is the second candidate RLC entity.

5. The first node of claim 4, comprising:

the first transceiver sending a first indication, the first indication being used to instruct the first RLC entity to discard the first pdcp pdu; discarding the first rlc sdu when neither the first rlc sdu nor the fragments of the first rlc sdu are passed to the lower layer;

wherein the first rlc sdu is the first pdcp pdu.

6. The first node according to any of claims 1-5, wherein the direct path comprises only one air interface and the non-direct path comprises at least two air interfaces.

7. The first node according to any of claims 2 to 6, comprising:

the first transceiver receiving a first message, the first message indicating a first expiration value and the first threshold;

wherein the first expiration value is used to determine that the first timer expires; the difference of the first expiration value minus the first threshold is used to determine a maximum transmission delay for the first pdcp pdu to be forwarded through a node where a peer RLC entity of the second candidate RLC entity is located.

8. A method in a first node for wireless communication, comprising:

Receiving a first PDCP SDU;

starting a first timer in response to receiving the first pdcsdu;

when the first timer is in an operation state, delivering the first PDCPDU to a first RLC entity for transmission;

9. The method in the first node of claim 8, wherein the first RLC entity is the first candidate RLC entity when the value of the first timer is greater than a first threshold.

10. The method in the first node according to claim 9, wherein the first RLC entity is the first candidate RLC entity or the second candidate RLC entity is related to a reference data amount when the value of the first timer is less than the first threshold;