CN117528703A

CN117528703A - Method and apparatus for use in wireless communication

Info

Publication number: CN117528703A
Application number: CN202210961156.0A
Authority: CN
Inventors: 张锦芳; 张晓博
Original assignee: Shanghai Langbo Communication Technology Co Ltd
Current assignee: Shanghai Langbo Communication Technology Co Ltd
Priority date: 2022-07-28
Filing date: 2022-08-09
Publication date: 2024-02-06

Abstract

A method and apparatus for use in wireless communications is disclosed. The first node copies the first PDCP PDU and submits the first PDCP PDU to each RLC entity in the first RLC entity set for transmission; receiving a first indication from a first RLC entity, the first indication being used to confirm successful transmission of the first PDCP PDU; wherein whether to indicate to a second RLC entity to discard a duplicate of the first PDCP PDU is related to a configuration of the first RLC entity; when the first RLC entity is configured by a first configuration type, indicating to the second RLC entity to discard the duplicate of the first PDCP PDU in response to receiving the first indication; the first RLC entity and the second RLC entity are two RLC entities of the first set of RLC entities, the first set of RLC entities maintained at the first node. The method and the device can effectively save air interface resources and improve data transmission robustness.

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) traffic, public Safety (Public Safety) traffic, and business applications and services, 3GPP (3 rd Generation Partner Project, third generation partnership project) RAN (Radio Access Network ) initiates SI (Study Item) and WI (Work Item) standardization Work in release 17 for "New air interface Sidelink Relay Study" (Study on NR) but release 17 only supports 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 (direct path) transmission and indirect path (indirect path) transmission, in which only one-hop transmission is performed between the source node and the destination receiving node, and in which multiple hops are included 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 sidelink transmission in the LTE (Long Term Evolution ) system as an example, the transmission from the UE to the relay node adopts the sidelink air interface technology, the transmission from the relay node to the base station or the enhanced node B (eNodeB, eNB) adopts the 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 in supporting multipath transmission, a data packet can be submitted to a plurality of lower-layer entities to perform transmission after being copied, namely, the data packet can be transmitted through a plurality of paths, if the paths between a transmitting node and a receiving node are all only one hop, after one lower-layer entity indicates that the data packet is successfully transmitted, the transmission stopped on other paths can be indicated to save air interface resources. When a path between a sending node and a receiving node is forwarded through a relay, a lower entity only indicates that the transmission of the data packet in the current hop is successful, and does not indicate that the transmission of the data packet to the destination receiving node is also successful, and at the moment, if the transmission stopping on other paths is indicated, the risk of failure of the transmission of the data packet is caused.

Aiming at the problems, the application discloses a solution, which can improve the success rate of data transmission on the basis of effectively saving air interface resources. 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:

duplicating a first PDCP PDU and submitting the first PDCP PDU to each RLC entity in a first RLC entity set for transmission;

receiving a first indication from a first RLC entity, the first indication being used to confirm successful transmission of the first PDCP PDU;

wherein whether to indicate to a second RLC entity to discard a duplicate of the first PDCP PDU is related to a configuration of the first RLC entity; when the first RLC entity is configured by a first configuration type, indicating to the second RLC entity to discard the duplicate of the first PDCP PDU in response to receiving the first indication; the first RLC entity and the second RLC entity are two RLC entities of the first set of RLC entities, the first set of RLC entities maintained at the first node.

As an embodiment, the present application is applicable to dual link (dual connectivity) transmission.

As an embodiment, the present application is applicable to multipath transmission.

As an embodiment, the present application is applicable to a scenario in which all paths in the multipath transmission are direct-connected paths, and also applicable to a scenario in which at least one path in the multipath transmission is a non-direct-connected path.

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) relay.

As an embodiment, the present application is applicable to transmission using a duplicate method for multipath.

As an embodiment, the above method may save air interface resources by indicating to discard duplicate (duplicate) of the first PDCP (Packet Data Convergence Protocol ) PDU (Protocol Data Unit, protocol data unit).

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:

and when the first RLC entity is configured by the second configuration type, as a response to receiving the first indication, delaying the copying of the first PDCP PDU to the second RLC entity after a first length of time.

As an embodiment, the above method may obtain the benefits of saving air resources and improving the robustness of data transmission at the same time by delaying the indication to the second RLC (Radio Link Control ) entity to discard the duplicate of the first PDCP PDU.

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

the first time length is related to the number of layer 2 relay nodes included between a node where a peer RLC entity of the first RLC entity is located and a destination receiver of the first PDCP PDU;

the node where the opposite-end RLC entity of the first RLC entity is located is a layer 2 relay node.

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

the first RLC entity is an AM RLC entity, and the second RLC entity is one of an AM RLC entity or an UM RLC entity.

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

discarding the first RLC SDU when neither the first RLC SDU nor the segmentation of the first RLC SDU is delivered to the underlying layer;

Wherein the first RLC SDU is the duplicate of the first PDCP PDU.

As an embodiment, the above method discards the first RLC SDU (Service Data Unit ), i.e. discards the duplicate of the first PDCP PDU, may save air interface resources.

As one embodiment, the above approach may reduce the underlying implementation complexity.

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

discarding the duplicate indicating to the second RLC entity to discard the first PDCP PDU when the first RLC entity is configured by a second configuration type.

As an embodiment, the above method does not indicate to the second RLC entity that discarding the duplicate of the first PDCP PDU may improve data transmission robustness.

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

the first PDCP entity is configured for PDCP duplication, the first PDCP entity being associated with each RLC entity of the first set of RLC entities.

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

a first transceiver duplicating and submitting a first PDCP PDU to each RLC entity in a first RLC entity set for transmission;

The first transceiver receiving a first indication from a first RLC entity, the first indication being used to confirm successful transmission of the first PDCP PDU;

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

the first transceiver, when the first RLC entity is configured by a second configuration type, as a response to receiving the first indication, delays the copying of the first PDCP PDU to the second RLC entity after a first length of time.

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

the first transceiver discarding the first RLC SDU when neither the first RLC SDU nor the segmentation of the first RLC SDU is delivered to the underlying layer;

wherein the first RLC SDU is the duplicate of the first PDCP PDU.

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

the first transceiver, when the first RLC entity is configured by a second configuration type, relinquishes the duplicate of the first PDCP PDU to indicate to the second RLC entity to discard.

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

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 third wireless signal transmission flow diagram according to one embodiment of the present application;

fig. 8 illustrates a schematic diagram of a radio bearer according to one 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 topology diagram according to one embodiment of the present application;

fig. 11 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 duplicates a first PDCP PDU and submits the first PDCP PDU to each RLC entity in the first RLC entity set for transmission in step 101; receiving a first indication from a first RLC entity in step 102, the first indication being used to confirm successful transmission of the first PDCP PDU; wherein whether to indicate to a second RLC entity to discard a duplicate of the first PDCP PDU is related to a configuration of the first RLC entity; when the first RLC entity is configured by a first configuration type, indicating to the second RLC entity to discard the duplicate of the first PDCP PDU in response to receiving the first indication; the first RLC entity and the second RLC entity are two RLC entities of the first set of RLC entities, the first set of RLC entities maintained at the first node.

As one embodiment, a first PDCP PDU is duplicated (duplicate) and submitted to each RLC entity in the first set of RLC entities for transmission.

As an embodiment, the first transceiver generates a first PDCP PDU.

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

As an embodiment, each RLC entity in the first set of RLC entities is activated for PDCP duplication (activated for PDCP duplication).

As an embodiment, the first set of RLC entities includes related RLC entities activated for PDCP duplication.

As an embodiment, any RLC entity in the first set of RLC entities is an AM (Acknowledged Mode ) RLC entity.

As an embodiment, the first RLC entity set includes at least one AM RLC entity.

As an embodiment, one RLC entity of the first set of RLC entities is identified by one of a logical channel identity (Logical Channel Identity, LCID) or an RLC channel identity (RLC channel Identity).

As a sub-embodiment of the above 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 a sub-embodiment of the above embodiment, the logical channel identity or the RLC channel identity is used to identify the one RLC entity at the network side.

As an embodiment, one RLC entity in the first RLC entity set associates a logical channel identifier with a Uu air interface, and a path transmitted through the one RLC entity is a direct connection path.

As an embodiment, one RLC entity in the first RLC entity set associates a logical channel identifier with the PC5 air interface, and a path transmitted through the one RLC entity is a non-direct connection path.

As a sub-embodiment of the above embodiment, the one logical channel identity associated by the one RLC entity at the PC5 interface is allocated by the first node itself.

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

As an embodiment, the first PDCP PDU is a PDCP control (control) PDU.

As an embodiment, the first PDCP PDU is one of a PDCP control PDU or a PDCP data PDU.

As an embodiment, the first transceiver is used for inter-layer communication between the first PDCP entity and any RLC entity of the first set of RLC entities.

As one embodiment, a first indication is received from a first RLC entity, the first indication being used to confirm successful transmission of the first PDCP PDU.

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

As an embodiment, the first indication is used to confirm (confirm) the successful transmission of the first PDCP PDU.

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

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 an embodiment, the PDCP sequence number includes 12 bits.

As an embodiment, the PDCP sequence number includes 18 bits.

As an embodiment, the first RLC entity sends a poll (poll) to a peer RLC entity of the first RLC entity, the poll being used to trigger the peer RLC entity feedback STATUS (STATUS) PDU of the first RLC entity.

As an embodiment, the status PDU indicates whether the first RLC SDU was successfully transmitted.

As one embodiment, receiving a status PDU from the peer RLC entity of the first RLC entity, the first RLC entity sending the first indication to the first PDCP entity when the status PDU indicates a positive acknowledgement (positive acknowledgement) for a first RLC SDU; wherein the first RLC SDU is the first PDCP PDU.

As an embodiment, the peer RLC entity of the first 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 first node and a node other than the first 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, whether to indicate to the second RLC entity to discard the duplicate of the first pdcp pdu relates to the configuration of the first RLC entity.

As a sub-embodiment of the above embodiment, the configuration of the first RLC entity is a network configuration.

As an embodiment, the phrase indicating to a second RLC entity whether to discard duplicates of the first PDCP PDU relates to configuration of the first RLC entity includes: whether to indicate to the second RLC entity to discard the duplicate of the first pdcp pdu is related to configuring the type of the first RLC entity.

As an embodiment, the phrase indicating to a second RLC entity whether to discard duplicates of the first PDCP PDU relates to configuration of the first RLC entity includes: whether to indicate to the second RLC entity to discard the duplicate of the first pdcp pdu relates to the type of information element (Information Element, IE) configuring the first RLC entity.

As an embodiment, the first transceiver, when the first RLC entity is configured by a first configuration type, indicates to the second RLC entity to discard the duplicate of the first PDCP PDU in response to receiving the first indication.

As an embodiment, when the first RLC entity is configured by the first configuration type, if the first indication is received, the second RLC entity is instructed to discard the duplicate of the first PDCP PDU.

As an embodiment, when the first RLC entity is not configured by the first configuration type, if the first indication is received, the discarding of the duplicate of the first PDCP PDU is not indicated to the second RLC entity.

As an embodiment, the first configuration type is an RLC bearer configuration.

As an embodiment, the first configuration type includes a lower layer part (lower layer part) of a radio bearer configuration, including RLC and logical channel (logical channel) configurations.

As an embodiment, when the information element configuring the first RLC entity is RLC-bearconfig (RLC bearer configuration), the first RLC entity is configured by the first configuration type.

As an embodiment, the first RLC entity is configured by the first configuration type when a logical channel identity (logical channel identity) is included in an information element configuring the first RLC entity.

As an embodiment, the first RLC entity is configured by the first configuration type when the first RLC entity is identified by a logical channel identification at the network side.

As an embodiment, when a node where a peer (peer) RLC entity of the first RLC entity is located is an intended receiver of the first PDCP PDU, the first RLC entity is configured by the first configuration type.

As an embodiment, the intended receiver is the final receiver of the first PDCP PDU.

As an embodiment, the first PDCP PDU is uploaded to an application layer of the intended receiver after the intended receiver is processed.

As an embodiment, when the node where the opposite RLC entity of the first RLC entity is located is a NG (next generation) -RAN node, the first RLC entity is configured by the first configuration type.

As an embodiment, the NG-RAN node is a gNB (NR node B) or a NG (next generation) -eNB.

As an embodiment, when data processed by the first RLC entity is transmitted on a PUSCH (Physical Uplink Shared Channel ) channel at a physical layer, the first RLC entity is configured by the first configuration type.

As an embodiment, when the first RLC entity is transmitting for the Uu air interface, the first RLC entity is configured by the first configuration type.

As an embodiment, the first configuration type is not RLC channel configuration.

As an embodiment, the first configuration type is only identified by a logical channel identity at the network side and not by an RLC channel identity.

As an embodiment, the configuration of the first configuration type includes a part or all of an Information Element (IE) in RRC (Radio Resource Control ) signaling.

As an embodiment, the configuration of the first configuration type is an RRC signaling.

As an embodiment, the configuration of the first configuration type includes all or part of IE in one RRC signaling.

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

As an embodiment, the first RLC entity and the second RLC entity are two RLC entities of the first set of RLC entities.

As an embodiment, the second RLC entity is any RLC entity in the first set of RLC entities other than the first RLC entity.

As an embodiment, the first RLC entity set includes at least two RLC entities.

As an embodiment, the first RLC entity set is located at the first node.

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 set of RLC entities is maintained at the first node.

As an embodiment, the first set of RLC entities is located in an RLC sublayer.

As an embodiment, a first transceiver duplicates a first PDCP PDU and submits the first PDCP PDU to each RLC entity in a first RLC entity set for transmission; the first transceiver receiving a first indication from a first RLC entity, the first indication being used to confirm successful transmission of the first PDCP PDU (successful delivery); wherein whether to indicate to a second RLC entity to discard a duplicate of the first PDCP PDU is related to a configuration of the first RLC entity; when the first RLC entity is configured by a first configuration type, indicating to the second RLC entity to discard the duplicate of the first PDCP PDU in response to receiving the first indication; the first RLC entity and the second RLC entity are two RLC entities in the first set of RLC entities, any RLC entity in the first set of RLC entities being maintained at the first node or a node other than the first node.

As a sub-embodiment of the above embodiment, the first Node is a MN (Master Node), and the one Node other than the first Node is a SN (Secondary Node).

As a sub-embodiment of the above embodiment, the first node is SN, and the one node other than the first node is MN.

As a sub-embodiment of the foregoing embodiment, the first node is an NG-RAN node, and the one node other than the first node is a UE.

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 Evolution Advanced, 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 Core Network)/EPC (Evolved Packet 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 Terrestrial Network, 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 Digital Assistant, 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 communication device, a land vehicle, an automobile, an in-vehicle device, an in-vehicle communication 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 ) 212, 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 user equipment.

As an embodiment, the UE241 is an RSU (Road Side Unit).

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 (Medium Access 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 Repeat Request ) operations. The RRC (Radio Resource Control ) sublayer 306 in layer 3 (L3 layer) in the control plane 300 is responsible for obtaining radio resources (i.e., radio bearers) and configuring the lower layers using RRC signaling between the gNB and the UE. 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 data transfer from the bottom layer to the upper layer.

As an embodiment, the first transceiver is used for data transfer from an upper layer to a lower layer.

As a sub-embodiment of the two embodiments, the upper layer and the bottom layer are adjacent layers.

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, the entities of the multiple sub-layers of the user plane in fig. 3 constitute DRBs (Data Radio Bearer, data radio bearers) in the 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 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, the duplication of the first PDCP PDU in the present application is generated in the PDCP304.

As an embodiment, the duplication of 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 any RLC entity in the first RLC entity set is 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 any RLC entity in the first RLC entity set is 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 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: duplicating a first PDCP PDU and submitting the first PDCP PDU to each RLC entity in a first RLC entity set for transmission; receiving a first indication from a first RLC entity, the first indication being used to confirm successful transmission of the first PDCP PDU; wherein whether to indicate to a second RLC entity to discard a duplicate of the first PDCP PDU is related to a configuration of the first RLC entity; when the first RLC entity is configured by a first configuration type, indicating to the second RLC entity to discard the duplicate of the first PDCP PDU in response to receiving the first indication; the first RLC entity and the second RLC entity are two RLC entities of the first set of RLC entities, the first set of RLC entities maintained at the first node.

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: duplicating a first PDCP PDU and submitting the first PDCP PDU to each RLC entity in a first RLC entity set for transmission; receiving a first indication from a first RLC entity, the first indication being used to confirm successful transmission of the first PDCP PDU; wherein whether to indicate to a second RLC entity to discard a duplicate of the first PDCP PDU is related to a configuration of the first RLC entity; when the first RLC entity is configured by a first configuration type, indicating to the second RLC entity to discard the duplicate of the first PDCP PDU in response to receiving the first indication; the first RLC entity and the second RLC entity are two RLC entities of the first set of RLC entities, the first set of RLC entities maintained at the first node.

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 base station.

As an embodiment, the first communication device 450 is an RSU (Road Side Unit).

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, 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 PDCP PDU in this application.

As an example, the antenna 420, the receiver 418, the multi-antenna receive processor 472, at least one of the receive processor 470 or the controller/processor 475 is used to receive the first PDCP PDU 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 RLC entity E52 and a second RLC entity E53 are both located at a first node, the first PDCP entity E51 and the first RLC entity E52 communicate through an inter-layer interface, and the first PDCP entity E51 and the second RLC entity E53 communicate through an inter-layer interface.

For the followingFirst PDCP entity E51Duplicate a first PDCP PDU and submit the first PDCP PDU to each RLC entity in a first RLC entity set in step S511; receiving a first indication in step S512; the duplicate of discarding the first PDCP PDU is indicated to the second RLC entity in step S513.

For the followingFirst RLC entity E52Receiving a first PDCP PDU in step S521; the first indication is sent in step S522.

For the followingSecond RLC entity E53Receiving a first PDCP PDU in step S531; a duplicate of the first PDCP PDU is received and discarded in step S532.

The steps performed in embodiment 5 are applicable to scenarios where the first RLC entity is configured by the first configuration type.

As an embodiment, the second 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 the underlying layer.

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

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

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

As an embodiment, the bottom layer is a MAC sublayer.

As an embodiment, the segmentation of the first RLC SDU comprises at least 1 bit of the first RLC SDU.

As an embodiment, in response to receiving the first indication, the second 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 underlying layer.

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

As an embodiment, the first PDCP PDU is transferred to the base layer after the processing of the first PDCP PDU at the second RLC entity is completed.

As an embodiment, the first RLC entity is an AM RLC entity, and the second RLC entity is one of an AM RLC entity or a UM (Unacknowledged Mode ) RLC entity.

As an embodiment, the first RLC entity is an AM RLC entity, and the second RLC entity is one of an AM RLC entity or an UM RLC entity or a TM (Transparent Mode) RLC entity.

As an embodiment, the first RLC entity is an AM RLC entity and the second RLC entity is an AM RLC entity.

As an embodiment, the first RLC entity is an AM RLC entity and the second RLC entity is an UM RLC entity.

As an embodiment, the first RLC entity is an AM RLC entity and the second RLC entity is a TM RLC entity.

As one example, the AM RLC entity is configured to submit/receive RLC PDUs through logical channels DL (Downlink)/UL (Uplink) DCCH (Dedicated Control Channel ), DL/UL DTCH (Dedicated Traffic Channel, dedicated traffic channel), SCCH (Sidelink Control Channel ) and STCH (Sidelink Traffic CHannel, sidelink traffic channel).

As one embodiment, the AM RLC entity submits/receives RLC data PDUs, which are AMD PDUs that include one complete RLC SDU or one RLC SDU segment (segment).

As one embodiment, the AM RLC entity submits/receives RLC control PDUs, which are status PDUs.

As one embodiment, the UM RLC entity is configured to submit/receive RLC PDUs through DL/UL DTCH, SCCH, STCH, MCCH (MBS Control Channel ) and MTCH (MBS Traffic Channel, MBS traffic channel) these logical channels

As an embodiment, the UM RLC entity submits/receives RLC data PDUs, which are UMD PDUs that include one complete RLC SDU or one RLC SDU segment (segment).

As an example, the TM RLC entity is configured to submit/receive RLC PDUs over logical channels of the BCCH (Broadcast Control CHannel ), DL/UL CCCH (Common Control Channel, common control channel), PCCH (Paging Control CHannel ) and SBCCH (Sidelink Broadcast Control CHannel, sidelink broadcast control channel).

As one embodiment, the TM RLC entity submits/receives RLC data PDUs, which are TMD PDUs.

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

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

As an embodiment, the second RLC entity is configured to transmit RLC entities.

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 RLC entity E62 and a second RLC entity E63 are both located at a first node, the first PDCP entity E61 and the first RLC entity E62 communicate through an inter-layer interface, and the first PDCP entity E61 and the second RLC entity E63 communicate through an inter-layer interface.

For the followingFirst PDCP entity E61Duplicate a first PDCP PDU and submit the first PDCP PDU to each RLC entity in a first RLC entity set in step S611; receiving a first indication in step S612; indicating to the second RLC entity to discard the duplicate of the first PDCP PDU after delaying the first time length in step S613.

For the followingFirst RLC entity E62Receiving a first PDCP PDU in step S521; the first indication is sent in step S522.

For the followingSecond RLC entity E63Receiving a first PDCP PDU in step S531; a duplicate of the first PDCP PDU is received and discarded in step S532.

The steps performed in embodiment 6 are applicable to scenarios where the first RLC entity is configured by the second configuration type.

As an embodiment, the first transceiver, when the first RLC entity is configured by a second configuration type, indicates to the second RLC entity to discard the duplicate of the first PDCP PDU after a delay (delay) for a first length of time in response to receiving the first indication.

As an embodiment, when the first RLC entity is configured by the second configuration type, if the first indication is received, delaying the copying of the first PDCP PDU is indicated to the second RLC entity after the first time period.

As an embodiment, the second configuration type is RLC channel configuration.

As an embodiment, when the information element configuring the first RLC entity is SL-RLC-ChannelConfig (sidelink RLC channel configuration), the first RLC entity is configured by the second configuration type.

As an embodiment, the first RLC entity is configured by the second configuration type when the information element configuring the first RLC entity is Uu-Relay-RLC-ChannelConfig (Uu Relay RLC channel configuration).

As an embodiment, when the information element configuring the first RLC entity is BH-RLC-ChannelConfig (backhaul RLC channel configuration), the first RLC entity is configured by the second configuration type.

As an embodiment, when an RLC channel identity (RLC channel identity) is included in an information element configuring the first RLC entity, the first RLC entity is configured by the second configuration type.

As an embodiment, when the first RLC entity is identified by an RLC channel identification on the network side, the first RLC entity is configured by the second configuration type.

As an embodiment, the first RLC entity is configured by the second configuration type when the first RLC entity is identified by a logical channel identification at the PC5 air interface.

As an embodiment, when the node where the peer RLC entity of the first RLC entity is located is a relay node of the first PDCP PDU, the first RLC entity is configured by the second configuration type.

As an embodiment, when the node where the peer RLC entity of the first RLC entity is located is a layer 2 relay UE, the first RLC entity is configured by the second configuration type.

As an embodiment, when the node where the peer RLC entity of the first RLC entity is located is a layer 2U2N relay UE, the first RLC entity is configured by the second configuration type.

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

As an embodiment, when the first RLC entity is transmitting for a PC5 air interface, the first RLC entity is configured by the second configuration type.

As an embodiment, the second configuration type is not an RLC bearer configuration.

As an embodiment, the second configuration type is only identified by RLC channel identification at the network side and not by logical channel identification.

As an embodiment, the configuration of the second configuration type includes a part or all of an Information Element (IE) in RRC signaling.

As an embodiment, the configuration of the second configuration type is an RRC signaling.

As an embodiment, the configuration of the second configuration type includes all or part of IE in one RRC signaling.

As an embodiment, the configuration of the second configuration type includes all or part of a field (field) in an IE in an RRC signaling.

As an embodiment, the indicating to the second RLC entity to discard the duplicate of the first PDCP PDU after the delay for a first length of time comprises: starting a first timer in response to receiving the first indication; when the first timer expires, indicating to the second RLC entity to discard the duplicate of the first PDCP PDU; the duration indicated by the expiration value of the first timer is the first time duration.

As an embodiment, the first time length is configurable.

As an embodiment, the first time length is configured by a serving cell of the first node.

As an embodiment, the first time length is preconfigured.

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

As an embodiment, the first time length is variable.

As an embodiment, the first time length is fixed.

As an embodiment, the indicating to the second RLC entity to discard the duplicate of the first PDCP PDU after the delay for a first length of time comprises: indicating to the second RLC entity to discard the duplicate of the first PDCP PDU until a second indication is received; wherein the second indication is received later than the first indication, the second indication comprising an acknowledgement of successful transmission of a PDCP PDU having a first sequence number greater than the sequence number of the first PDCP PDU.

As an embodiment, the indicating to the second RLC entity to discard the duplicate of the first PDCP PDU after the delay for a first length of time comprises: indicating to the second RLC entity to discard the duplicate of the first PDCP PDU until a second indication is received; wherein the second indication is an inter-layer indication that is correctly transmitted for PDCP PDUs immediately after the first indication.

As an embodiment, the indicating to the second RLC entity to discard the duplicate of the first PDCP PDU after the delay for a first length of time comprises: until the value of tx_next (NEXT transmission) is not less than the sum of the COUNT value of the first PDCP PDU plus a first Window Size (Window Size), indicating to the second RLC entity to discard the duplicate of the first PDCP PDU.

As an embodiment, the tx_next indicates a COUNT value of the PDCP SDU to be transmitted NEXT.

As one embodiment, the COUNT value consists of HFN and PDCP sequence numbers; wherein the HFN is a superframe number (Hyper Frame Number).

As an embodiment, the first window size is configurable.

As an embodiment, the first window size is configured by a serving cell of the first node.

As an embodiment, the first window size is preconfigured.

As an embodiment, the first window size is variable.

As an embodiment, the first window size is fixed.

As an embodiment, the first time length relates to a number of layer 2 relay nodes included between a node where the peer RLC entity of the first RLC entity is located and an intended receiver of the first PDCP PDU.

As an embodiment, the node where the peer RLC entity of the first RLC entity is located is a layer 2 relay node.

As an embodiment, the node where the peer RLC entity of the first RLC entity is located is a layer 2 relay node for the first PDCP PDU.

As an embodiment, when a node where the peer RLC entity of the first RLC entity is located is distant from the destination receiver of the first pdcp pdu by no layer 2 relay node, the first time length is t1; when at least one layer 2 relay node is included between the node of the opposite RLC entity of the first RLC entity and the destination receiver of the first PDCP PDU, the first time length is t2, where the value of t1 is less than the value of t 2.

As an embodiment, the first time length is proportional to the number of layer 2 relay nodes included between the node where the peer RLC entity of the first RLC entity is located and the intended receiver of the first PDCP PDU.

As an embodiment, the first time length is a product of a first factor and a number of layer 2 relay nodes included between a node where the peer RLC entity of the first RLC entity is located and an intended receiver of the first PDCP PDU.

As an embodiment, the value of the first factor is configurable.

Example 7

Embodiment 7 illustrates a third wireless signal transmission flow diagram according to one embodiment of the present application, as shown in fig. 7. In fig. 7, a first PDCP entity E71, a first RLC entity E72 and a second RLC entity E73 are both located at a first node, the first PDCP entity E71 and the first RLC entity E72 communicate through an inter-layer interface, and the first PDCP entity E71 and the second RLC entity E73 communicate through an inter-layer interface.

For the followingFirst PDCP entity E71Duplicate a first PDCP PDU and submit the first PDCP PDU to each RLC entity in the first RLC entity set in step S711; receiving a first finger in step S712 Shown.

For the followingFirst RLC entity E72Receiving a first PDCP PDU in step S721; the first indication is sent in step S722.

For the followingSecond RLC entity E73The first PDCP PDU is received in step S731.

The steps performed in embodiment 7 are applicable to scenarios where the first RLC entity is configured by the second configuration type.

As an embodiment, the first transceiver, when the first RLC entity is configured by the second configuration type, discards the duplicate of the first PDCP PDU as indicated to the second RLC entity in response to receiving the first indication.

As an embodiment, the discarding of the duplicate of the first PDCP PDU is not indicated to the second RLC entity when the first RLC entity is configured by a second configuration type.

As an embodiment, the first transceiver discards the first PDCP PDU and a PDCP SDU corresponding to the first PDCP PDU as a response to receiving the first indication, where the first PDCP PDU is a PDCP data PDU.

Example 8

Embodiment 8 illustrates a schematic diagram of a radio bearer according to one embodiment of the present application, as shown in fig. 8. In fig. 8, a first PDCP entity, a first RLC entity and a second RLC entity are both located at a first node, the first PDCP entity and the first RLC entity communicate through an inter-layer interface, and the first PDCP entity and the second RLC entity communicate through an inter-layer interface.

As an example, fig. 8 is applicable to SRB.

As an example, fig. 8 is applicable to DRB.

As an example, fig. 8 is applicable to MRB.

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

As an embodiment, the first radio bearer is a split SRB, i.e. split SRB (signaling radio bearer).

As an embodiment, the first radio bearer is a split DRB, i.e. split DRB (data radio bearer).

As an embodiment, the first radio bearer is a split DRB, i.e. split MRB (MBS radio bearer).

As an example, fig. 8 is applicable to transceiving.

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

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

As an embodiment, the first PDCP entity is configured for PDCP duplication, the first PDCP entity being associated with each RLC entity of the first set of RLC entities.

As an embodiment, the first PDCP entity is used for the first radio bearer.

As an embodiment, the first PDCP entity is used to send data belonging to the first radio bearer for which PDCP duplication is activated.

As an embodiment, the phrase that the first PDCP entity is associated with each RLC entity of the first set of RLC entities comprises: the bearer served by each RLC entity in the first set of RLC entities is the first radio bearer for which the first PDCP entity is used.

As an embodiment, the phrase that the first PDCP entity is associated with each RLC entity of the first set of RLC entities comprises: each RLC entity of the first set of RLC entities is used to transmit data from the first PDCP entity.

As an embodiment, the first PDCP entity being configured to PDCP duplication comprises: data transmitted via the first PDCP entity is duplicated and distributed to each RLC entity in the first RLC entity set for transmission.

As an embodiment, the first PDCP entity being configured to PDCP duplication comprises: duplicate PDCP PDUs at the first PDCP entity and distribute the PDCP PDUs to each RLC entity in the first RLC entity set for transmission.

As an embodiment, the first PDCP entity being configured to PDCP duplication comprises: when the PDCP PDU is PDCP DataPDU, copying the PDCP DataPDU in the first PDCP entity and submitting the PDCP DataPDU to each RLC entity in the first RLC entity set for transmission; and when the PDCP PDU is a PDCP Control PDU, submitting the PDCP Control PDU to a primary (primary) RLC entity in the first RLC entity set for transmission.

As an embodiment, PDCP PDUs formed by processing data packets received from a higher layer protocol entity by a PDCP entity are transmitted through one of the first RLC entity or the second RLC entity; wherein the higher layer protocol entity is an RRC protocol entity.

As an embodiment, after the PDCP PDU formed by processing the PDCP entity of the data packet received from the higher layer protocol entity is duplicated, the data packet is simultaneously sent through the first RLC entity and the second RLC entity; wherein the higher layer protocol entity is an SDAP protocol entity.

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

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

As an embodiment, both the first RLC entity and the second RLC entity are for uplink communications.

As an embodiment, both the first RLC entity and the second RLC entity are for sidelink communications.

As an embodiment, both the first RLC entity and the second RLC entity are for a primary cell group (Master Cell Group, MCG).

As an embodiment, the first RLC entity and the second RLC entity are both for a secondary cell group (Secondary Cell Group, SCG).

As an embodiment, the first RLC entity set includes one primary RLC entity and at least one split secondary RLC entity.

As an embodiment, the primary RLC entity is used for data transmission on a primary path (primary path) in a dual connection (dual connectivity, DC); the at least one split secondary RLC entity is used for data transmissions on paths other than the primary path.

As an embodiment, both the primary RLC entity and the at least one split secondary RLC entity are used for data transmission over the Uu air interface.

As an embodiment, the primary RLC entity is used for data transmission over the Uu air interface and the at least one split secondary RLC entity is used for data transmission over the PC5 air interface.

As an embodiment, the primary RLC entity is used for data transmission over the PC5 air interface and the at least one split secondary RLC entity is used for data transmission over the Uu air interface.

As an embodiment, the primary RLC entity is used for data transmission of the control plane and the at least one split secondary RLC entity is used for data transmission of the data plane.

As an embodiment, the first RLC entity is a primary RLC entity and the second RLC entity is a split secondary RLC entity.

As an embodiment, the first RLC entity is a split secondary RLC entity and the second RLC entity is a primary RLC entity.

As an embodiment, the primary RLC entity is configurable.

As an embodiment, the primary RLC entity is associated with a cell group (cell group).

As an embodiment, the cell group is one of a primary cell group or a secondary cell group.

As an embodiment, data belonging to the first radio bearer is sent over at least 2 connections, each of the at least 2 connections being sent over one RLC entity of the first set of RLC entities.

As an embodiment, the at least 2 connections comprise MCG.

As an embodiment, the at least 2 connections include MCG and SCG.

As an embodiment, the at least 2 connections comprise at least one direct path (direct path) and at least one non-direct path (indirect path).

As an embodiment, the direct connection 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 an original node to an intended 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 an embodiment, the at least two air interfaces include a BH (backhaul) air interface and an Access air interface.

As one embodiment, the first radio bearer is an uplink radio bearer.

As one embodiment, the first radio bearer is a sidelink radio bearer (Sidelink Radio Bearer, SLRB).

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 a Uu-PDCP sublayer 905, a PC5-SRAP (Sidelink Relay Adaptation Protocol ) sublayer 904 and a PC5-RLC sublayer 903 on the first node side, generates a first target MAC PDU at a PC5-MAC sublayer 902, then transmits the first target MAC PDU to a PC5-PHY layer 901, then transmits the first target MAC PDU to a PC5-PHY layer 911 of a third node through a PC5 air interface, and then sequentially passes through a PC5-MAC sublayer 912 and a 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 first RLC entity is the PC5-RLC903, the peer RLC entity of the first RLC entity is the PC5-RLC913, the PC5-RLC903 sends a poll (poll) to the PC5-RLC913, the poll is used to trigger the PC5-RLC913 to feed back a status PDU to the PC5-RLC 903; when the status PDU indicates positive acknowledgement for the first RLC SDU, the PC5-RLC903 sends a first indication to the Uu-PDCP 905; wherein the first RLC SDU is the first PDCP PDU.

As one embodiment, for layer 2 relay transmission, the RLC, MAC, and PHY layers are responsible for point-to-point (point-to-point) communication per 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 one embodiment, the SRAP sublayer implements out-link (egress link) 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.

As an embodiment, the second node in fig. 9 corresponds to the second communication device 410 in embodiment 4.

Example 10

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

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 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 third node is a Secondary Cell (SCell) of a primary Cell group of the first node.

As an embodiment, the third node is a cell of a secondary cell group of the first node.

As an example, the third node is a node of a TN (Terrestrial Network, land network).

As an embodiment, the third node is a node of NTN (Non-Terrestrial Network ).

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

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

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

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

As an embodiment, the second node in fig. 10 corresponds to the second communication device 410 in embodiment 4.

Example 11

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

In fig. 11, a first node processing apparatus 1100 includes a first transceiver 1101. The first node 1100 is a UE.

In embodiment 11, a first transceiver 1101 duplicates and submits a first PDCP PDU to each RLC entity in a first set of RLC entities for transmission; the first transceiver 1101 receiving a first indication from a first RLC entity, the first indication being used to confirm successful transmission of the first PDCP PDU; wherein whether to indicate to a second RLC entity to discard a duplicate of the first PDCP PDU is related to a configuration of the first RLC entity; when the first RLC entity is configured by a first configuration type, indicating to the second RLC entity to discard the duplicate of the first PDCP PDU in response to receiving the first indication; the first RLC entity and the second RLC entity are two RLC entities of the first set of RLC entities, the first set of RLC entities maintained at the first node.

As an embodiment, the first transceiver 1101, when the first RLC entity is configured by the second configuration type, indicates to the second RLC entity to discard the duplicate of the first PDCP PDU after delaying for a first length of time in response to receiving the first indication.

As an embodiment, the first transceiver 1101, when the first RLC entity is configured by the second configuration type, indicates to the second RLC entity to discard the duplicate of the first PDCP PDU after delaying for a first length of time in response to receiving the first indication; the first time length is related to the number of layer 2 relay nodes included between a node where a peer RLC entity of the first RLC entity is located and a destination receiver of the first PDCP PDU; the node where the opposite-end RLC entity of the first RLC entity is located is a layer 2 relay node.

As an embodiment, the first RLC entity is an AM RLC entity, and the second RLC entity is one of an AM RLC entity or an UM RLC entity.

As an embodiment, the first transceiver 1101 discards the first RLC SDU when neither the first RLC SDU nor the segmentation of the first RLC SDU is delivered to the bottom layer; wherein the first RLC SDU is the duplicate of the first PDCP PDU.

As an embodiment, the first transceiver 1101, when the first RLC entity is configured by a second configuration type, discards the duplicate indicating to the second RLC entity to discard the first PDCP PDU.

As an embodiment, a first PDCP entity is configured for PDCP duplication, the first PDCP entity being associated with each RLC entity of the first set of RLC entities.

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

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

As an example, the first transceiver 1101 includes a 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 (enhanced Machine 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:

2. The first node of claim 1, comprising:

3. The first node of claim 2, wherein the first length of time relates to a number of layer 2 relay nodes included between a node where a peer RLC entity of the first RLC entity is located and an intended receiver of the first PDCP PDU;

4. A first node according to any of claims 1 to 3, characterized in that the first RLC entity is an AM RLC entity and the second RLC entity is one of an AM RLC entity or an UM RLC entity.

5. The first node according to any of claims 1 to 4, comprising:

Wherein the first RLC SDU is the duplicate of the first PDCP PDU.

6. The first node of claim 1, comprising:

7. The first node according to any of claims 1-6, characterized in that a first PDCP entity is configured for PDCP duplication, the first PDCP entity being associated with each RLC entity of the first set of RLC entities.

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

9. The method in the first node of claim 8, comprising:

10. The method in the first node of claim 8, comprising: