CN116938405A

CN116938405A - Method and apparatus for wireless communication

Info

Publication number: CN116938405A
Application number: CN202210347302.0A
Authority: CN
Inventors: 陈宇; 张晓博
Original assignee: Shanghai Langbo Communication Technology Co Ltd
Current assignee: Shanghai Langbo Communication Technology Co Ltd
Priority date: 2022-04-01
Filing date: 2022-04-01
Publication date: 2023-10-24
Also published as: WO2023186162A1

Abstract

A method and apparatus for wireless communication includes receiving first signaling used to configure a first PDCP entity and a first RLC entity set; the first RLC entity set includes at least one secondary link RLC entity and a primary link RLC entity; any RLC entity in the first set of RLC entities is associated with the first PDCP entity; the primary path of the first PDCP entity is associated with a first RLC entity of the first set of RLC entities; receiving second signaling, wherein the second signaling comprises a first bit string, and N1 bits of the first bit string have a one-to-one mapping relation with N1 RLC entities except the first RLC entity in the first RLC entity set; the first bit string is used to indicate activation or deactivation of PDCP duplication of RLC entities in the first set of RLC entities; transmitting a first PDCP data PDU of the first PDCP entity; the application is helpful to improve the reliability of communication and avoid communication interruption through the first signaling.

Description

Method and apparatus for wireless communication

Technical Field

The present application relates to a transmission method and apparatus in a wireless communication system, and more particularly, to a method and apparatus for optimizing a network in communication, improving service quality, relaying communication, and the like.

Background

Future wireless communication systems have more and more diversified application scenes, and different application scenes have different performance requirements on the system. To meet the different performance requirements of various application scenarios, a New air interface technology (NR) is decided to be researched in the 3GPP (3 rd Generation Partner Project, third Generation partnership project) RAN (Radio Access Network ) #72 times of the whole meeting, and standardized Work is started on NR by the 3GPP RAN #75 times of the whole meeting through the WI (Work Item) of NR.

In communication, both LTE (Long Term Evolution ) and 5G NR can be involved in reliable accurate reception of information, optimized energy efficiency ratio, determination of information validity, flexible resource allocation, scalable system structure, efficient non-access layer information processing, lower service interruption and disconnection rate, support for low power consumption, which is significant for normal communication between a base station and a user equipment, reasonable scheduling of resources, balancing of system load, so that it can be said as high throughput, meeting communication requirements of various services, improving spectrum utilization, improving a base stone of service quality, whether embbe (ehanced Mobile BroadBand, enhanced mobile broadband), URLLC (Ultra Reliable Low Latency Communication, ultra-high reliability low latency communication) or eMTC (enhanced Machine Type Communication ) are indispensable. Meanwhile, in the internet of things in the field of IIoT (Industrial Internet of Things), in V2X (vehicle to X) communication (Device to Device) in the field of industry, in communication of unlicensed spectrum, in monitoring of user communication quality, in network planning optimization, in NTN (Non Territerial Network, non-terrestrial network communication), in TN (Territerial Network, terrestrial network communication), in dual connectivity (Dual connectivity) system, in radio resource management and codebook selection of multiple antennas, in signaling design, neighbor management, service management, and beamforming, there is a wide demand, and the transmission modes of information are broadcast and unicast, both transmission modes are indispensable for 5G system, because they are very helpful to meet the above demands.

With the increasing of the scene and complexity of the system, the system has higher requirements on reducing the interruption rate, reducing the time delay, enhancing the reliability, enhancing the stability of the system, and the flexibility of the service, and saving the power, and meanwhile, the compatibility among different versions of different systems needs to be considered in the system design.

The 3GPP standardization organization performs related standardization work for 5G to form a series of standards, and the standard content can be referred to:

https://www.3gpp.org/ftp/Specs/archive/38_series/38.211/38211-g60.zip

https://www.3gpp.org/ftp/Specs/archive/38_series/38.213/38213-g60.zip

https://www.3gpp.org/ftp/Specs/archive/38_series/38.331/38331-g60.zip

https://www.3gpp.org/ftp/Specs/archive/38_series/38.331/38323-g60.zip

disclosure of Invention

In various communication scenarios, the use of relay may be involved, for example, when one UE (User Equipment) is at the cell edge and coverage is poor, the network may be accessed through the relay, and the relay node may be another UE. The relay mainly comprises a layer 3 relay and a layer 2 relay (L2U 2N relay), which are used for providing network access service for a remote node (U2N remote UE) through a relay node, wherein the layer 3 relay is transparent to an access network, namely the remote UE only establishes connection with a core network, and the access network cannot identify whether data come from the remote node or the relay node; while layer 2 relay, remote node (U2N remote UE) and access network (RAN) have RRC connection, the access network can manage the remote node, and radio bearers can be established between the access network and the remote node. The relay may be another UE, and in a system supporting layer 2 relay, the UE may communicate with the network through an L2 relay UE (L2U 2N relay UE), that is, using an indirect path (direct path), or may communicate with the network directly without relay, that is, using a direct path (direct path). In some scenarios, one UE may use both the direct path and the indirect path to achieve better reliability and higher throughput. The direct path and the indirect path are different in terms of radio resource management and network optimization. The direct and indirect paths, one without relaying and one with relaying, may provide traffic to multiple nodes, so the throughput, qoS, and functionality of two or more paths may not be the same, which is different from the traditional network architecture, and the solution must be adapted to this new network architecture. When the direct path and the indirect path are simultaneously used, especially when the direct path further includes a plurality of carriers, one PDCP entity may be associated with a plurality of RLC entities, where the plurality of RLC entities correspond to the plurality of paths, and the network may preferably dynamically activate and deactivate PDCP copy functions of a portion of the RLC entities according to transmission quality, load conditions, and occupied resources of different paths. Because the configuration modes of the direct path and the indirect path RLC entities are very different, the prior art cannot support to activate and deactivate the PDCP copy function of the RLC entity on the indirect path, and the introduction of the indirect path can cause the PDCP copy function of the RLC entity indicating the direct path to be problematic. These problems are addressed by the present application. Of course, the solution proposed by the present application may also solve other problems in the communication system, without being limited to the above, such as the case where there are multiple indirect paths and/or where there are no direct paths and only multiple indirect paths, such as the case where there is both an MCG and an SCG and there is an indirect path at the same time.

The present application provides a solution to the above-mentioned problems.

It should be noted that, in the case of no conflict, the embodiments of any node of the present application and the features in the embodiments may be applied to any other node. The embodiments of the application and the features of the embodiments may be combined with each other arbitrarily without conflict.

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

receiving first signaling, the first signaling being used to configure a first PDCP entity and a first RLC entity set; the first RLC entity set includes at least one secondary link RLC entity and a primary link RLC entity; any RLC entity in the first set of RLC entities is associated with the first PDCP entity; the primary path of the first PDCP entity is associated with a first RLC entity of the first set of RLC entities;

receiving second signaling, wherein the second signaling comprises a first bit string, and N1 bits of the first bit string have a one-to-one mapping relation with N1 RLC entities except the first RLC entity in the first RLC entity set; the first bit string is used to indicate activation or deactivation of PDCP duplication of RLC entities in the first set of RLC entities;

Transmitting a first PDCP data PDU of the first PDCP entity; the act of transmitting a first PDCP data PDU of the first PDCP entity includes: duplicating the first PDCP data PDU of the first PDCP entity and submitting duplicated copies to PDCP duplication activated RLC entities in the first RLC entity set, respectively;

wherein N1 is a positive integer, any RLC entity in the first RLC entity set being associated with one logical channel identity in a first logical channel identity list; the one-to-one mapping relationship of the first bit string to the N1 RLC entities other than the first RLC entity in the first set of RLC entities is related to a logical channel identity on a primary link in the first list of logical channel identities, and the one-to-one mapping relationship of the first bit string to the N1 RLC entities other than the first RLC entity in the first set of RLC entities is unrelated to a logical channel identity on a secondary link in the first list of logical channel identities.

As one embodiment, the problems to be solved by the present application include: in the scenario of using L2 relay, especially when the direct path and the indirect path are used simultaneously, how to support activation and deactivation of PDCP duplication functions to ensure normal operation of communication, while taking into account requirements and characteristics of relay communication.

As one example, the benefits of the above method include: when the L2 relay is supported, especially when a plurality of paths are simultaneously used for communication with a network, the PDCP copying function of the RLC entity can be dynamically activated and deactivated, so that the time delay is reduced, the interruption of communication is reduced, the service quality is improved, the coverage is increased, the consumption of resources is reduced, the resource utilization rate is improved, and the mobility and the service continuity are better supported.

Specifically, according to one aspect of the present application, the first signaling is used to indicate activation of PDCP duplication of any RLC entity of the first set of RLC entities associated with a logical channel identity on a secondary link in the first list of logical channel identities; the second signaling is only used to instruct activation or deactivation of PDCP duplication of RLC entities associated with the primary link in the first logical channel identity list other than the first RLC entity in the first set of RLC entities; mapping the lowest bit in the first bit string with a second RLC entity, wherein the second RLC entity belongs to the first RLC entity set; the second RLC entity is associated with a first logical channel identity; the logical channel identity with the smallest value in the logical channel identities of the main link in the first logical channel identity list associated with RLC entities other than the first RLC entity in the first RLC entity set is the first logical channel identity;

Wherein any RLC entity in the first set of RLC entities is for communication with an MCG.

Specifically, according to one aspect of the present application, the first RLC entity set includes N1+1 RLC entities, N2 RLC entities of the N1+1 RLC entities being associated with logical channel identities on secondary links in the first logical channel identity list; the N2 bits in the first bit string have a first mapping relation with the N2 RLC entities; N1-N2 bits in the first bit string have a second mapping relation with the N2 RLC entities in the first RLC entity set and the RLC entities other than the first RLC entity; the value of the logical channel identity in the first logical channel identity list associated with the N2 RLC entities in the first RLC entity set and RLC entities other than the first RLC entity is used to determine the second mapping relationship;

wherein the N2 bits and the N1-N2 bits in the first bit string are different, N2 is a positive integer not greater than N1, and the first mapping relationship and the second mapping relationship are both one-to-one mappings.

Specifically, according to an aspect of the present application, the sub-link RLC channel identities associated with the N2 RLC entities are used to determine the first mapping relationship.

In particular, according to one aspect of the application, the N2 bits of the first bit string are consecutive; the N1-N2 bits of the first bit string are consecutive.

Specifically, according to one aspect of the present application, third signaling is received, the third signaling being used to instruct activation or deactivation of PDCP duplicates of all RLC entities in the first set of RLC entities associated with logical channel identities on secondary links in the first list of logical channel identities;

wherein the logical channel identity in the first logical channel identity list associated with the first RLC entity is a primary link logical channel identity.

Specifically, according to one aspect of the present application, third signaling is received, the third signaling being used to instruct activation or deactivation of PDCP duplication of the first PDCP entity;

transmitting a second PDCP data PDU of the first PDCP entity, the act of transmitting the second PDCP data PDU of the first PDCP entity comprising: submitting the second PDCP data PDU of the first PDCP entity to either the first RLC entity or a third RLC entity;

wherein a split secondary path of the first PDCP entity is associated with the third RLC entity in the first set of RLC entities; the first RLC entity and the third RLC entity are both configured to communicate with an MCG; one of the first RLC entity and the third RLC entity is associated with a logical channel identity on a primary link in the first logical channel identity list and the other is associated with a logical channel identity on a secondary link in the first logical channel identity list; at least one of the first signaling and the third signaling is used to implicitly indicate a split secondary path of the first PDCP entity.

Specifically, according to an aspect of the present application, the radio bearer corresponding to the first PDCP entity is an SRB, and the peer RLC entity of the first RLC entity is in a node other than the MCG.

Specifically, according to an aspect of the present application, the first node is an internet of things terminal.

In particular, according to one aspect of the application, the first node is a relay.

Specifically, according to one aspect of the present application, the first node is a U2N remote UE.

Specifically, according to one aspect of the present application, the first node is a vehicle-mounted terminal.

In particular, according to one aspect of the application, the first node is an aircraft.

Specifically, according to one aspect of the present application, the first node is a mobile phone.

In particular, according to one aspect of the application, the first node is a communication terminal supporting multi-SIM card communication.

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

transmitting first signaling, the first signaling being used to configure a first PDCP entity and a first RLC entity set; the first RLC entity set includes at least one secondary link RLC entity and a primary link RLC entity; any RLC entity in the first set of RLC entities is associated with the first PDCP entity; the primary path of the first PDCP entity is associated with a first RLC entity of the first set of RLC entities;

Transmitting a second signaling, wherein the second signaling comprises a first bit string, and N1 bits of the first bit string have a one-to-one mapping relation with N1 RLC entities except the first RLC entity in the first RLC entity set; the first bit string is used to indicate activation or deactivation of PDCP duplication of RLC entities in the first set of RLC entities;

receiving a first PDCP data PDU of the first PDCP entity; the act of receiving a first PDCP data PDU of the first PDCP entity includes: receiving a copy of the first PDCP data PDU of the first PDCP entity from a peer RLC entity of at least one of the activated RLC entities in the first set of RLC entities;

Specifically, according to one aspect of the present application, third signaling is sent, the third signaling being used to instruct activation or deactivation of PDCP duplicates of all RLC entities in the first set of RLC entities associated with logical channel identities on secondary links in the first list of logical channel identities;

Specifically, according to one aspect of the present application, third signaling is transmitted, the third signaling being used to instruct activation or deactivation of PDCP duplication of the first PDCP entity;

Receiving a second PDCP data PDU of the first PDCP entity, the act of receiving the second PDCP data PDU of the first PDCP entity comprising: receiving the second PDCP data PDU from one of the first RLC entity or a peer entity in a third RLC entity;

In particular, according to one aspect of the application, the second node is a base station.

In particular, according to one aspect of the application, the second node is an access point.

In particular, according to one aspect of the application, the second node is a relay.

Specifically, according to an aspect of the present application, the second node is a vehicle-mounted terminal.

In particular, according to one aspect of the application, the second node is an aircraft.

In particular, according to one aspect of the application, the second node is a satellite.

The application discloses a first node used for wireless communication, comprising:

a first receiver receiving first signaling, the first signaling being used to configure a first PDCP entity and a first RLC entity set; the first RLC entity set includes at least one secondary link RLC entity and a primary link RLC entity; any RLC entity in the first set of RLC entities is associated with the first PDCP entity; the primary path of the first PDCP entity is associated with a first RLC entity of the first set of RLC entities;

the first receiver receives a second signaling, where the second signaling includes a first bit string, and N1 bits of the first bit string have a one-to-one mapping relationship with N1 RLC entities other than the first RLC entity in the first RLC entity set; the first bit string is used to indicate activation or deactivation of PDCP duplication of RLC entities in the first set of RLC entities;

A first transmitter transmitting a first PDCP data PDU of the first PDCP entity; the act of transmitting a first PDCP data PDU of the first PDCP entity includes: duplicating the first PDCP data PDU of the first PDCP entity and submitting duplicated copies to PDCP duplication activated RLC entities in the first RLC entity set, respectively;

The application discloses a second node used for wireless communication, comprising:

a second transmitter transmitting first signaling, the first signaling being used to configure a first PDCP entity and a first RLC entity set; the first RLC entity set includes at least one secondary link RLC entity and a primary link RLC entity; any RLC entity in the first set of RLC entities is associated with the first PDCP entity; the primary path of the first PDCP entity is associated with a first RLC entity of the first set of RLC entities;

The second transmitter sends second signaling, wherein the second signaling comprises a first bit string, and N1 bits of the first bit string have a one-to-one mapping relation with N1 RLC entities except the first RLC entity in the first RLC entity set; the first bit string is used to indicate activation or deactivation of PDCP duplication of RLC entities in the first set of RLC entities;

a second receiver for receiving a first PDCP data PDU of the first PDCP entity; the act of receiving a first PDCP data PDU of the first PDCP entity includes: receiving a copy of the first PDCP data PDU of the first PDCP entity from a peer RLC entity of at least one of the activated RLC entities in the first set of RLC entities;

As an embodiment, the present application has the following advantages over the conventional scheme:

activation and deactivation of PDCP duplication of RLC supporting relay, especially when relaying UE using L2U 2N (UE to Network).

Activation and deactivation of PDCP duplication when direct and indirect paths are used simultaneously, including one direct path and one indirect path, multiple direct paths and one indirect path, one direct path and multiple indirect paths, multiple direct paths and multiple indirect paths.

The supporting network configures and handles the radio links connecting the cell groups and the radio links connecting the relays differently, i.e. functionally differently.

Support for radio bearers, especially bearer architectures where SRB1 uses split (split bearer) on direct and indirect paths.

The support signaling bearer uses the indirect path as the primary path.

The support of separate slave and master paths is associated with the MCG at the same time.

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 flow chart of receiving first signaling, receiving second signaling, and transmitting a first PDCP data PDU of a first PDCP entity according to an embodiment of the present application;

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

fig. 3 shows a schematic diagram of an embodiment of a radio protocol architecture of a user plane and a control plane according to an embodiment of the application;

FIG. 4 shows a schematic diagram of a first communication device and a second communication device according to one embodiment of the application;

fig. 5 shows a flow chart of wireless signal transmission according to an embodiment of the application;

FIG. 6 shows a schematic diagram of a protocol stack for relaying communications according to one embodiment of the application;

fig. 7 shows a radio bearer diagram according to an embodiment of the application;

FIG. 8 shows a schematic diagram of a topology according to one embodiment of the application;

fig. 9 shows a schematic diagram of a mapping relationship of a first bit string to a first RLC entity set according to one embodiment of the present application;

fig. 10 shows a schematic diagram in which first signaling is used to indicate activation of PDCP duplication of any RLC entity in the first set of RLC entities associated with a logical channel identity on a secondary link in the first list of logical channel identities in accordance with an embodiment of the present application;

fig. 11 is a diagram illustrating that second signaling is used only to indicate activation or deactivation of PDCP duplication of RLC entities associated with a primary link in a first logical channel identity list, other than a first RLC entity in a first set of RLC entities, according to an embodiment of the present application;

Fig. 12 is a schematic diagram showing that the magnitudes of the values of the logical channel identities in the first logical channel identity list associated with the N2 RLC entities in the first RLC entity set and the RLC entities other than the first RLC entity are used to determine the second mapping relationship according to one embodiment of the present application;

fig. 13 is a schematic diagram showing that sub-link RLC channel identities associated with N2 RLC entities are used to determine a first mapping relationship according to one embodiment of the present application;

FIG. 14 illustrates a schematic diagram of a processing apparatus for use in a first node in accordance with one embodiment of the application;

fig. 15 illustrates a schematic diagram of a processing arrangement for use in a second node according to an embodiment of the application.

Description of the embodiments

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

Example 1

Embodiment 1 illustrates a flowchart of receiving a first signaling, receiving a second signaling, and transmitting a first PDCP data PDU of a first PDCP entity according to an embodiment of the present application, as shown in fig. 1. In fig. 1, each block represents a step, and it is emphasized that the order of the blocks in the drawing does not represent temporal relationships between the represented steps.

In embodiment 1, a first node in the present application receives a first signaling in step 101, receives a second signaling in step 102, and transmits a first PDCP data PDU of a first PDCP entity in step 103;

wherein the first signaling is used to configure a first PDCP entity and a first RLC entity set; the first RLC entity set includes at least one secondary link RLC entity and a primary link RLC entity; any RLC entity in the first set of RLC entities is associated with the first PDCP entity; the primary path of the first PDCP entity is associated with a first RLC entity of the first set of RLC entities; the second signaling comprises a first bit string, and N1 bits of the first bit string have a one-to-one mapping relation with N1 RLC entities except the first RLC entity in the first RLC entity set; the first bit string is used to indicate activation or deactivation of PDCP duplication of RLC entities in the first set of RLC entities; the act of transmitting a first PDCP data PDU of the first PDCP entity includes: duplicating the first PDCP data PDU of the first PDCP entity and submitting duplicated copies to PDCP duplication activated RLC entities in the first RLC entity set, respectively; the N1 is a positive integer, any RLC entity in the first set of RLC entities is associated with one logical channel identity in a first list of logical channel identities; the one-to-one mapping relationship of the first bit string to the N1 RLC entities other than the first RLC entity in the first set of RLC entities is related to a logical channel identity on a primary link in the first list of logical channel identities, and the one-to-one mapping relationship of the first bit string to the N1 RLC entities other than the first RLC entity in the first set of RLC entities is unrelated to a logical channel identity on a secondary link in the first list of logical channel identities.

As an embodiment, the first node is a UE (User Equipment).

As an embodiment, the first node is in an RRC connected state.

As an embodiment, the direct path refers to a UE-to-network transmission path, by which data is transmitted between a remote UE of the UE-to-network (U2N) and the network without being relayed.

As a sub-embodiment of this embodiment, the data includes higher layer data and signaling.

As a sub-embodiment of this embodiment, the data comprises RRC signaling.

As a sub-embodiment of this embodiment, the data comprises a string or block of bits.

As a sub-embodiment of this embodiment, the data includes only signaling or data carried by RBs (radio bearers).

As an embodiment, the indirect path refers to a UE-to-Network transmission path, through which data is transmitted between a remote UE of the UE-to-Network (U2N) and the Network via a relay UE of the UE-to-Network (U2N).

As a sub-embodiment of this embodiment, the data comprises RRC signaling.

As an embodiment, a wireless link is either the direct path or the indirect path.

As one embodiment, a U2N relay UE refers to a UE that provides functionality to support the connection of a U2N remote UE to a network.

As one embodiment, a U2N remote UE refers to a UE that needs to communicate with a network via a U2N relay UE.

As one embodiment, a U2N remote UE refers to a UE that communicates with a network supporting relay services.

As one embodiment, the U2N relay is a U2N relay UE.

As an embodiment, when unicast service is sent and received with the network, both the U2N relay and the U2N remote node are in RRC connected state.

As an embodiment, when the U2N remote UE is in an RRC idle state or an RRC inactive state, the U2N relay UE may be in any RRC state, including an RRC connected state, an RRC idle state, and an RRC inactive state.

As an embodiment, not transmitting over a direct path is equal to transmitting over an indirect path.

As one embodiment, not transmitting over a direct path includes transmitting over a relay.

As one embodiment, transmitting over a direct path is or includes transmitting without relaying.

As one embodiment, transmitting over the direct path is or includes forwarding without relaying.

As one embodiment, the U2N relay UE is a UE that provides functionality (functionality) support for a U2N remote UE to connect to a network.

As a sub-embodiment of this embodiment, the U2N relay UE is a UE.

As a sub-embodiment of this embodiment, the U2N relay UE provides relay services to the network for the U2N remote UE.

As one embodiment, the U2N remote UE is a UE that communicates with the network through a U2N relay UE.

As one embodiment, a direct mode is a mode using the direct path.

As one embodiment, the direct mode is a mode in which the U2N remote UE communicates with the network using the direct path.

As an embodiment, the direct mode is a mode in which the U2N remote UE uses the direct path to transmit RRC signaling or establish an RRC connection with the network.

As one embodiment, the indirect (indirect) mode is a mode using the indirect path.

As an embodiment, the indirect mode is a mode using the indirect path.

As one embodiment, the direct mode is a mode in which the U2N remote UE communicates with the network using the indirect path.

As an embodiment, the direct mode is a mode in which the U2N remote UE uses the indirect path to transmit RRC signaling or establish an RRC connection with the network.

As an embodiment, the serving cell is or includes a cell in which the UE resides. Performing a cell search includes the UE searching for a suitable (subscriber) cell of the selected PLMN (Public land mobile Network ) or SNPN (Stand-alone Non-Public Network), selecting the suitable cell to provide available service, monitoring a control channel of the suitable cell, which is defined as camping on the cell; that is, a camped cell, with respect to the UE, is the serving cell for the UE. Camping on one cell in RRC idle state or RRC inactive state has the following benefits: such that the UE may receive system messages from the PLMN or SNPN; after registration, if the UE wishes to establish an RRC connection or continue a suspended RRC connection, the UE may perform initial access on the control channel of the camping cell; the network may page to the UE; so that the UE can receive ETWS (Earthquake and Tsunami Warning System, earthquake tsunami warning system) and CMAS (Commercial Mobile Alert System ) notifications.

As an embodiment, for a U2N remote node, the serving cell is or includes the cell in which the U2N relay resides or is connected.

As an embodiment, for a UE in RRC connected state without CA/DC (carrier aggregation/dual connectivity ) configuration, only one serving cell includes the primary cell. For UEs in RRC connected state that are CA/DC (carrier aggregation/dual connectivity ) configured, the serving Cell is used to indicate the set of cells including the Special Cell (SpCell) and all the secondary cells. The Primary Cell (Primary Cell) is a MCG (Master Cell Group) Cell, operating on the Primary frequency, on which the UE performs an initial connection establishment procedure or initiates connection re-establishment. For the dual connectivity operation, the special Cell refers to a PCell (Primary Cell) of MCG or a PSCell (Primary SCG Cell) of SCG (Secondary Cell Group); if not dual connectivity operation, the special cell is referred to as a PCell.

As an example, the frequency at which the SCell (Secondary Cell, slave Cell) operates is the slave frequency.

For one embodiment, the individual content of the information element is referred to as a field.

As an example, MR-DC (Multi-Radio Dual Connectivity ) refers to dual connectivity of E-UTRA and NR nodes, or dual connectivity between two NR nodes.

As an embodiment, in MR-DC, the radio access node providing the control plane connection to the core network is a master node, which may be a master eNB, a master ng-eNB, or a master gNB.

As an embodiment, MCG refers to a set of serving cells associated with a primary node, including SpCell, and optionally, one or more scells, in MR-DC.

As an example, PCell is SpCell of MCG.

As one example, PSCell is the SpCell of SCG.

As an embodiment, in MR-DC, the radio access node that does not provide control plane connection to the core network, providing additional resources to the UE, is a slave node. The slave node may be an en-gNB, a slave ng-eNB or a slave gNB.

As an embodiment, in MR-DC, the set of serving cells associated with the slave node is SCG (secondary cell group, slave cell group), including SpCell and, optionally, one or more scells.

As one embodiment, the access layer function that enables V2X (Vehicle-to-evaluation) communications defined in 3GPP standard TS 23.285 is V2X sidelink communications (V2X sidelink communication), which occur between nearby UEs and which use E-UTRA technology but do not traverse network nodes.

As one embodiment, at least the access layer function enabling V2X (Vehicle-to-evaluation) communications defined in 3GPP standard TS 23.287 is NR sidelink communications (NR sidelink communication), where the NR sidelink communications occur between two or more UEs in close proximity and use NR technology but do not traverse a network node.

As one embodiment, a Sidelink (SL) is a direct communication link between UEs-to-UEs using sidelink resource allocation patterns, physical layer signals or channels, and physical layer procedures.

As an example, in the present application, the signaling name or domain name or message name beginning with "SL-" is for the sidelink.

As an example, not or not within or outside of the coverage is equal to the coverage.

As one embodiment, the in-coverage is equal to the in-coverage.

As an embodiment, the out-of-coverage is equal to the out-of-coverage.

As an embodiment, the first node is a U2N remote node.

As an embodiment, PDCP entities corresponding to radio bearers terminated between the UE and the network are located within the UE and the network, respectively.

As an embodiment, the direct path is a communication link or channel or bearer used when transmitting over the direct path.

As an embodiment, the direct path transmission refers to that data carried by at least SRB (Signaling radio bearer ) between the UE and the network is not relayed or forwarded by other nodes.

As an embodiment, the direct path transmission refers to that RLC bearers associated with at least SRBs (Signaling radio bearer, signaling radio bearers) between the UE and the network are terminated by the UE and the network, respectively.

As an embodiment, the direct path transmission refers to that RLC entities associated with at least SRBs (Signaling radio bearer, signaling radio bearers) between the UE and the network are terminated by the UE and the network, respectively.

As an embodiment, the direct path transmission refers to that there is a direct communication link between the UE and the network.

As an embodiment, the direct path transmission refers to that a Uu interface exists between the UE and the network.

As an embodiment, the direct path transmission refers to a MAC layer where a Uu interface exists between the UE and the network, and the MAC layer of the Uu interface carries RRC signaling.

As an embodiment, the direct path transmission refers to a physical layer where a Uu interface exists between the UE and the network.

As an embodiment, the direct path transmission refers to the presence of a logical channel and/or a transport channel between the UE and the network.

As an embodiment, the indirect path is an indirect path or a communication link or channel or bearer used when transmitting over the indirect path.

As an embodiment, the indirect path transmission refers to the relay or forwarding of data carried by at least SRB (Signaling radio bearer ) between the UE and the network via other nodes.

As an embodiment, the indirect path transmission refers to that RLC bearers associated with at least SRB (Signaling radio bearer ) between the UE and the network are terminated by the UE and other nodes, other nodes and the network, respectively.

As an embodiment, the indirect path transmission refers to that RLC entities associated with at least SRBs (Signaling radio bearer, signaling radio bearers) between the UE and the network are terminated by the UE and other nodes, respectively, the other nodes and the network.

As an embodiment, the meaning of the phrase at least SRB includes at least one of { SRB0, SRB1, SRB2, SRB3 }.

As an embodiment, the phrase at least the meaning of SRB includes SRB and DRB (data radio bearer ).

As an embodiment, the indirect path transmission refers to that there is no direct communication link between the UE and the network.

As an embodiment, the indirect path transmission refers to a MAC layer where a Uu interface does not exist between the UE and the network.

As an embodiment, the indirect path transmission refers to a physical layer where no Uu interface exists between the UE and the network.

As an embodiment, the indirect path transmission refers to that there is no logical channel or no transmission channel between the UE and the network.

As an embodiment, the network comprises a Radio Access Network (RAN) and/or a serving cell and/or a base station.

As an embodiment, the phrase UE and the UEs in the phrase network comprise the first node.

As an embodiment, the other nodes comprise relay nodes or other UEs.

As one embodiment, the UE may send physical layer signaling to the network when using direct path transmission; when using indirect path transmission, the UE cannot send or directly send physical layer signaling to the network;

as one embodiment, the UE may send a MAC CE to the network when using direct path transmission; when indirect path transmission is used, the UE cannot send or directly send MAC CEs to the network;

as an embodiment, when direct path transmission is used, no other protocol layer exists between the PDCP layer and RLC layer of the first node; when indirect path transmission is used, there are other protocol layers between the PDCP layer and the RLC layer of the first node.

As a sub-embodiment of this embodiment, the other protocol layer is or comprises an adaptation layer.

As an embodiment, when using direct path transmission, the network directly schedules uplink transmission of the first node through DCI; when indirect path transmission is used, the network does not directly schedule uplink transmission of the first node through DCI.

As an embodiment, when using direct path transmission, the SRB of the first node is associated with an RLC entity and/or RLC layer and/or RLC bearer; when using indirect path transmission, the SRB of the first node is associated with the RLC entity of the PC5 interface.

As an embodiment, when using direct path transmission, there is a mapping relationship between the SRB of the first node and the RLC entity of the Uu interface; when indirect path transmission is used, the SRB of the first node has a mapping relation with the RLC entity of the PC5 interface.

As an embodiment, a direct path and/or an indirect path exists between the first node and the network.

As an embodiment, the meaning of converting from a direct path to an indirect path is: the indirect path starts to be used while the direct path stops to be used.

As an embodiment, the meaning of converting from a direct path to an indirect path is: the indirect path transmission is started while the direct path transmission is stopped.

As an embodiment, the meaning of converting from a direct path to an indirect path is: from direct path transmission to indirect path transmission.

As an embodiment, the meaning of converting from a direct path to an indirect path is: the first node associates an SRB with an RLC entity of a PC5 interface while releasing the RLC entity of the Uu interface associated with the SRB.

As an embodiment, the meaning of converting from a direct path to an indirect path is: the first node associates SRBs and DRBs with RLC entities of the PC5 interface while releasing RLC entities of the Uu interface associated with the SRBs and DRBs.

As an embodiment, the meaning of converting from an indirect path to a direct path is: the direct path starts to be used while the indirect path stops to be used.

As an embodiment, the meaning of converting from an indirect path to a direct path is: direct path transmission is started while indirect path transmission is stopped.

As an embodiment, the meaning of converting from an indirect path to a direct path is: from indirect path transmission to direct path transmission.

As an embodiment, the meaning of converting from an indirect path to a direct path is: the first node releases the RLC entity of the PC5 interface associated with the SRB while associating the SRB with the RLC entity of the Uu interface.

As an embodiment, the meaning of converting from an indirect path to a direct path is: the first node releases all RLC entities of the PC5 interface associated with the DRB while associating the DRB with RLC entities of the Uu interface.

As an embodiment, the first node supports an indirect path to indirect path conversion.

As an embodiment, when the first node uses an indirect path, the relay used by the indirect path is a first relay.

As an embodiment, the relay in the present application refers to a U2N relay UE.

As an embodiment, the first node is in an RRC connected state.

As an embodiment, the first node in the present application does not use DC (dual connectivity ).

As an embodiment, the first node in the present application is not configured with DC (dual connectivity ).

As an embodiment, the first node in the present application is configured with DC (dual connectivity ).

As an embodiment, the first node in the present application has only one cell group.

As an embodiment, the first node in the present application has only one cell group, i.e. a Master Cell Group (MCG).

As an embodiment, the first node in the present application is not configured as a Slave Cell Group (SCG).

As an embodiment, the relay in the present application refers to an L2U 2N relay UE.

As an embodiment, the first node in the present application uses both a direct path and an indirect path.

As an embodiment, the first signaling is RRC signaling.

As an embodiment, the first signaling is or includes an rrcrecon configuration message.

As an embodiment, the first signaling is or includes other rrcrecon configuration messages encapsulated by a container in rrcrecon configuration.

As an embodiment, the first signaling occupies a DCCH channel.

As an embodiment, the first signaling is sent via SRB 1.

As an embodiment, the first signaling is sent via SRB 3.

As an embodiment, the first signaling comprises a partial field in rrcrecon configuration.

As an embodiment, the first signaling includes a PDCP-Config field, and the PDCP-Config included in the first signaling is used to configure the first PDCP entity.

As an embodiment, the first signaling includes a PDCP-Config field, and the PDCP-Config included in the first signaling is used to configure the first RLC entity set.

As an embodiment, the first signaling includes an SRB-ToAddMod domain, and the SRB-ToAddMod included in the first signaling is used to configure at least one of the first PDCP entity and the first RLC entity set.

As an embodiment, the first signaling includes a DRB-ToAddMod domain, and the DRB-ToAddMod included in the first signaling is used to configure at least one of the first PDCP entity and the first RLC entity set.

As an embodiment, the first signaling includes an sl-RLC-beaderconfig field, and the sl-RLC-beaderconfig included in the first signaling is used to configure the first RLC entity set.

As an embodiment, the first signaling includes an RLC-beaderconfig field, and the RLC-beaderconfig included in the first signaling is used to configure the first RLC entity set.

As an embodiment, the first signaling includes a CellGroupConfig field, and the CellGroupConfig included in the first signaling is used to configure at least one of the first PDCP entity and the first RLC entity set.

As an embodiment, the first signaling includes an RLC-Config domain, and the RLC-Config included in the first signaling is used to configure the first RLC entity set.

As an embodiment, the first PDCP entity is a PDCP entity for radio bearers between the first node and a serving cell or group of cells of the first node.

As an embodiment, the peer PDCP entity of the first PDCP entity is located at a serving cell or cell group or MCG of the first node.

As an embodiment, the first signaling is used to configure the first PDCP entity including: and configuring the length of the sequence number domain of the first PDCP entity.

As an embodiment, the first signaling is used to configure the first PDCP entity including: and configuring a header compression algorithm of the first PDCP entity.

As an embodiment, the first signaling is used to configure the first PDCP entity including: at least one parameter of the first PDCP entity is configured.

As an embodiment, the first signaling is used to configure the first PDCP entity including: and configuring a main path of the first PDCP entity.

As an embodiment, the first signaling is used to configure the first PDCP entity including: and configuring ul-DataSplitThreshold of the first PDCP entity, wherein the ul-DataSplitThreshold is used for path selection when splitting a slave path.

As an embodiment, the first signaling is used to configure the first PDCP entity including: whether the first PDCP entity uses PDCP duplication is configured.

As an embodiment, the first signaling is used to configure the first PDCP entity including: configuring whether the first PDCP entity activates PDCP duplication.

As an embodiment, the first signaling is used to configure the first PDCP entity including: whether the first PDCP entity is configured for PDCP duplication is configured.

As an embodiment, the first signaling is used to configure the first PDCP entity including: a timer of the first PDCP entity is configured.

As an embodiment, RLC entities of the first set of RLC entities are all configured to communicate with a serving cell of the first node.

As an embodiment, RLC entities of the first set of RLC entities are all configured to communicate with a primary serving cell of the first node.

As an embodiment, RLC entities in the first set of RLC entities are all configured to communicate with a group of serving cells of the first node.

As an embodiment, RLC entities in the first set of RLC entities are all configured to communicate with a primary serving cell group of the first node.

As an embodiment, the first set of RLC entities comprises at least 2 RLC entities.

As an embodiment, the meaning that the first signaling is used to configure the first RLC entity set includes: the first signaling configures each of the first RLC entities.

As an embodiment, the meaning that the first signaling is used to configure the first RLC entity set includes: the first signaling configures each of the first RLC entities to be associated with the first PDCP entity and a radio bearer to which the first PDCP entity corresponds.

As an embodiment, the meaning that the first signaling is used to configure the first RLC entity set includes: the first signaling configures an RLC bearer or a sidelink RLC bearer corresponding to each RLC entity in the first RLC entity.

As an embodiment, the meaning that the first signaling is used to configure the first RLC entity set includes: the first signaling configures whether any of the first RLC entities uses PDCP duplication.

As an embodiment, the meaning that the first signaling is used to configure the first RLC entity set includes: the first signaling configures a logical channel identity corresponding to any RLC entity in the first RLC entity.

As an embodiment, the meaning that the first signaling is used to configure the first RLC entity set includes: the first signaling configures a logical channel identity of a main link corresponding to an RLC bearer corresponding to any RLC entity in the first RLC entities.

As an embodiment, the meaning that the first signaling is used to configure the first RLC entity set includes: and the first signaling configures the logic channel identity on the sidelink corresponding to the sidelink RLC bearing corresponding to any one of the first RLC entities.

As an embodiment, the meaning that the first signaling is used to configure the first RLC entity set includes: the first signaling configures whether a mode of any RLC entity of the first RLC entities is AM mode or UM mode.

As an embodiment, the meaning that the first signaling is used to configure the first RLC entity set includes: the first signaling configures at least one parameter of any one of the first RLC entities.

As an embodiment, the meaning that the first signaling is used to configure the first RLC entity set includes: the first signaling configures an identity of a radio bearer served by any one of the first RLC entities.

As a sub-embodiment of this embodiment, the radio bearer served by any one of the first RLC entities is the radio bearer corresponding to the first PDCP entity.

As an embodiment, the meaning that the first signaling is used to configure the first RLC entity set includes: the first signaling configures at least one timer of at least one of the first RLC entities.

As an embodiment, the meaning that the first signaling is used to configure the first RLC entity set includes: the first signaling configures a length of a sequence number field used by at least one of the first RLC entities.

As an embodiment, the meaning that the first signaling is used to configure the first RLC entity set includes: the first signaling indicates to query (poll) at least one RLC entity of the first RLC entities.

As an embodiment, the sidelink RLC entity is a sidelink RLC entity, which is a link with which the UE communicates.

As a sub-embodiment of this embodiment, the sidelink RLC entities of the first set of RLC entities are established for communication between the first node and a network.

As a sub-embodiment of this embodiment, the sidelink RLC entity of the first set of RLC entities is an RLC entity between the first node and an L2U 2N relay UE of the first node.

As one embodiment, the sidelink RLC entity is a sidelink RLC entity, which is a link including RLC, MAC and physical layers for UE-to-UE communication.

As a sub-embodiment of this embodiment, the communication of the first node with the network is an end-to-end communication based on a radio bearer, and the lower layer of the radio bearer between the first node and the network is a sidelink between the first node and a relay and a link between the relay of the first node to the network.

As an embodiment, the secondary link is relative to the primary link.

As an embodiment, the secondary link RLC entity is an RLC entity for processing PDUs of the first PDCP entity, and a peer entity of the secondary link RLC entity is located in a relay of the first node.

As an embodiment, the main link corresponds to a link or a wireless link of the Uu interface.

As an embodiment, the secondary link corresponds to a link or a wireless link of the PC5 interface.

As an embodiment, the main link RLC entity is a link between the first node and a network.

As an embodiment, the primary RLC entity is a link between the first node and a primary serving cell or group of primary serving cells.

As an embodiment, the main link comprises a link between the first node and NG-RAN.

As a sub-embodiment of this embodiment, the main link comprises RLC layer, MAC and physical layer.

As a sub-embodiment of this embodiment, the main link comprises an RLC layer, a MAC and a physical layer for the set of serving cells of the first node.

As an embodiment, the RLC layer, MAC layer and physical layer comprised by the sidelink are not for the serving cell group of the first node.

As a sub-embodiment of this embodiment, the sidelink communication is a link established for the first node to communicate with the NG-RAN through a relay.

As an embodiment, the main link is a link between the first node and NG-RAN.

As a sub-embodiment of this embodiment, the main link comprises an RLC layer, a MAC layer and a physical layer for the NG-RAN.

As an embodiment, the main link is relative to the side link.

As an embodiment, the direct path refers to the main link or uses the main link to communicate.

As an embodiment, the indirect path refers to a sidelink or uses sidelink communication.

As an embodiment, the sidelink RLC entity is a PC5 interface RLC entity.

As an embodiment, the sidelink RLC entity corresponds to the RLC layer of the PC5 interface.

As an embodiment, the first signaling indicates that the Identity of the radio bearer corresponding to the first PDCP entity is sl-RemoteUE-RB-Identity.

As an embodiment, the first signaling indicates, through a radio bearconfig field, an identity of a radio bearer corresponding to the first PDCP entity.

As an embodiment, the first signaling indicates an Identity of a radio bearer corresponding to the first PDCP entity through an sl-RemoteUE-RB-Identity field.

As a sub-embodiment of this embodiment, the sl-RemoteUE-RB-Identity field indicates a first radio bearer configured by the radio bearconfig field, and the PDCP entity corresponding to the first radio bearer is the first PDCP entity.

As a sub-embodiment of this embodiment, the sl-RemoteUE-RB-Identity field indicates that at least one RLC entity field on the sidelink path is associated with the first radio bearer.

As an embodiment, the main link RLC entity and the sidelink RLC entity are configured by different domains of the first signaling.

As a sub-embodiment of this embodiment, the main link RLC entity is configured by the RLC-beaderconfig domain of the first signaling.

As a sub-embodiment of this embodiment, the sidelink RLC entity is configured by the SL-RLC-ChannelConfig-PC5 domain of the first signaling.

As a sub-embodiment of this embodiment, the sidelink RLC entity is configured by means of the SL-RLC-ChannelConfig domain of the first signaling.

As an embodiment, the phrase that any RLC entity of the first set of RLC entities is associated with the first PDCP entity means that: any RLC entity in the first RLC entity set has a mapping relationship with the first PDCP entity.

As an embodiment, the phrase that any RLC entity of the first set of RLC entities is associated with the first PDCP entity means that: the RLC bearer corresponding to any RLC entity in the first RLC entity set has a mapping relationship with the first PDCP entity.

As an embodiment, the phrase that any RLC entity of the first set of RLC entities is associated with the first PDCP entity means that: any RLC entity of the first set of RLC entities is configured to transmit and/or process PDUs of the first PDCP entity.

As an embodiment, the phrase that any RLC entity of the first set of RLC entities is associated with the first PDCP entity means that: the PDCP entity corresponding to a radio bearer served by an RLC bearer corresponding to any RLC entity in the first RLC entity set is the first PDCP entity.

As an embodiment, the phrase that any RLC entity of the first set of RLC entities is associated with the first PDCP entity means that: the PDCP entity corresponding to a radio bearer served by a sidelink RLC bearer corresponding to any RLC entity in the first RLC entity set is the first PDCP entity.

As an embodiment, at least for reception, any RLC entity corresponds to and only one RLC bearer or sidelink RLC bearer.

As an embodiment, at least for transmission, any RLC entity corresponds to and only one RLC bearer or sidelink RLC bearer.

As an embodiment, any PDCP entity corresponds to and only corresponds to one radio bearer.

As an embodiment, the first RLC entity is a primary link RLC entity.

As an embodiment, the first RLC entity is a sidelink RLC entity.

As an embodiment, the first signaling indicates that the cell group identity of the primary path of the first PDCP entity is a first cell group identity; the first signaling indicates that a logical channel identity of a primary path of the first PDCP entity is a first primary logical channel identity.

As a sub-embodiment of this embodiment, the first RLC entity is for the cell group identified by the first cell group identity; and the logical channel corresponding to the first RLC entity is identified by the first main logical channel identity.

As a sub-embodiment of this embodiment, the first RLC entity is a primary link RLC entity.

As an embodiment, the first signaling indicates an identity of a secondary link RLC channel of a primary path of the first PDCP entity.

As a sub-embodiment of this embodiment, the first RLC entity is a sidelink RLC entity; and the identity of the secondary link RLC channel of the main path of the first PDCP entity indicated by the first signaling of the secondary link RLC channel corresponding to the first RLC entity.

As an embodiment, the first signaling indicates a secondary link RLC channel identity of a primary path of the first PDCP entity.

As a sub-embodiment of this embodiment, the first RLC entity is a sidelink RLC entity; and the identity of the secondary link RLC channel corresponding to the first RLC entity is indicated by the first signaling and the identity of the secondary link RLC channel of the main path of the first PDCP entity.

As an embodiment, the first signaling indicates an identity of the relay node for which the primary path of the first PDCP entity is directed.

As a sub-embodiment of this embodiment, the first RLC entity is a sidelink RLC entity; the identity of the node for which the first RLC entity is directed is indicated by the first signaling by the identity of the relay node for which the primary path of the first PDCP entity is directed.

As an embodiment, the radio bearer corresponding to the first PDCP entity is a first radio bearer.

As an embodiment, the serving cell of the first node may instruct to activate or deactivate PDCP copy functions of the first radio bearer.

As an embodiment, the serving cell of the first node may instruct to activate PDCP copy functions of any primary link RLC entity in the first RLC entity set, when the PDCP copy functions of any primary link RLC entity in the first RLC entity set are activated, the PDCP copy functions of the first radio bearer are also activated.

As an embodiment, the serving cell of the first node may instruct to activate PDCP copy functions of any of the secondary link RLC entities in the first set of RLC entities, when the PDCP copy functions of any of the secondary link RLC entities in the first set of RLC entities are activated, the PDCP copy functions of the first radio bearer are also activated.

As an embodiment, the serving cell of the first node may instruct to activate PDCP copy functions of any RLC entity in the first RLC entity set, when the PDCP copy function of any RLC entity in the first RLC entity set is activated, the PDCP copy function of the first radio bearer is also activated.

As an embodiment, the serving cell of the first node may instruct to deactivate PDCP duplicates of all RLC entities in the first set of RLC entities, when all PDCP duplicates of RLC entities in the first set of RLC entities are deactivated, the PDCP duplicates of the first radio bearer is also deactivated.

As an embodiment, the primary path of the first PDCP entity corresponds to a primary RLC entity associated with the first PDCP entity.

As an embodiment, any RLC entity included in the first set of RLC entities is either a primary link RLC entity or a secondary link RLC entity.

As an embodiment, when PDCP duplication of the first radio bearer is activated, PDCP control PDUs of the first PDCP entity are transmitted through a primary RLC entity of the first PDCP entity.

As an embodiment, when PDCP duplication of the first radio bearer is activated, PDCP control PDUs of the first PDCP entity are not transmitted through RLC entities other than the primary RLC entity of the first PDCP entity.

As an embodiment, after the PDCP duplication of the first radio bearer is activated, PDCP data PDUs of the first PDCP entity are duplicated and then sent through RLC entities associated with the first PDCP entity, where PDCP duplication is activated, respectively.

As an embodiment, when PDCP of the first radio bearer is not duplicated and activated, PDCP PDUs of the first PDCP entity are transmitted through a primary RLC entity of the first PDCP.

As an embodiment, the meaning of the main path of the first PDCP entity being associated with a first RLC entity of the first set of RLC entities is that the main path of the first PDCP entity is for the first RLC entity.

As an embodiment, the meaning that the primary path of the first PDCP entity of the sentence is associated with a first RLC entity of the first set of RLC entities is that the primary RLC entity corresponding to the primary path of the first PDCP entity is the first RLC entity.

As an embodiment, the first signaling includes a first sub-signaling and a second sub-signaling, where the first sub-signaling and the second sub-signaling configure a main link RLC entity and a sidelink RLC entity in the first RLC entity set, respectively.

As a sub-embodiment of this embodiment, the first sub-signaling is RRC signaling of the Uu interface; the second sub-signaling is RRC signaling of the PC5 interface.

As a sub-embodiment of this embodiment, the first sub-signaling is RRC signaling of the Uu interface; the second sub-signaling is RRC signaling of the Uu interface.

As an embodiment, the second signaling is higher layer signaling.

As an embodiment, the second signaling is or includes signaling of a MAC layer.

As an embodiment, the second signaling is or includes PC5-S signaling.

As an embodiment, the second signaling is or includes RRC signaling.

As an embodiment, the second signaling is or includes a MAC CE.

As an embodiment, the first bit string includes a number of bits greater than N1.

As an embodiment, the first bit string comprises N1 bits, wherein N1 is a positive integer.

As a sub-embodiment of this embodiment, said N1 is equal to 3.

As a sub-embodiment of this embodiment, said N1 is equal to one of {4,5,6 }.

As a sub-embodiment of this embodiment, said N1 is equal to one of {1,2,3 }.

As a sub-embodiment of this embodiment, said N1 is equal to one of {4,5,6,7,8 }.

As a sub-embodiment of this embodiment, the N1 is configurable.

As a sub-embodiment of this embodiment, said N1 is predefined.

As a sub-embodiment of this embodiment, the first bit string is N1 least significant bits in the second signaling, the second signaling comprising one byte.

As a sub-embodiment of this embodiment, the size of the second signaling is one byte.

As a sub-embodiment of this embodiment, the second signaling includes an identity of the first radio bearer.

As a sub-embodiment of this embodiment, the second signaling is two bytes in size.

As an embodiment, the meaning that the first bit string has a one-to-one mapping relationship with N1 RLC entities other than the first RLC entity in the first RLC entity set includes: the first RLC entity set includes N1+1 RLC entities, there is a one-to-one mapping relationship between N1 RLC entities in the first RLC entity set and N1 bits of the first bit string, and the N1 RLC entities in the first RLC entity set do not include the first RLC entity.

As an embodiment, the meaning that the first bit string has a one-to-one mapping relationship with N1 RLC entities other than the first RLC entity in the first RLC entity set includes: the first RLC entity set includes N1+ x RLC entities, where x is a positive integer, there is a one-to-one mapping relationship between N1 RLC entities in the first RLC entity set and N1 bits of the first bit string, and the N1 RLC entities in the first RLC entity set do not include the first RLC entity.

As a sub-embodiment of this embodiment, any RLC entity other than the first RLC entity in the first set of RLC entities has a one-to-one mapping relationship with a bit in one of the first bit strings.

As a sub-embodiment of this embodiment, at least any one main link RLC entity other than the first RLC entity in the first set of RLC entities has a one-to-one mapping relationship with a bit in one of the first bit strings.

As a sub-embodiment of this embodiment, x RLC entities other than the N1 RLC entities in the first RLC entity set do not have a mapping relationship with the first bit string.

As an embodiment, the first RLC entity does not have a mapping relationship with any bit in the first bit string.

As an embodiment, the phrase one-to-one mapping means that at most any one bit in the first bit string is mapped with one RLC entity in the first set of RLC entities; RLC entities in the first set of RLC entities map with at most one bit in the first bit string.

As an embodiment, the meaning that the first bit string is used to indicate activation or deactivation of PDCP duplication of RLC entities in the first RLC entity set includes: any bit in the first bit string being 0 for indicating deactivation of PDCP copying of the RLC entity associated with the any bit in the first bit string; any bit of the first bit string is 1 for indicating activation of PDCP duplication of the RLC entity associated with the any bit of the first bit string.

As an embodiment, the meaning that the first bit string is used to indicate activation or deactivation of PDCP duplication of RLC entities in the first RLC entity set includes: the value of any bit in the first bit string is used to indicate activation and deactivation of PDCP duplication of the RLC entity associated with the any bit.

As an embodiment, the meaning that the first bit string is used to indicate activation or deactivation of PDCP duplication of RLC entities in the first RLC entity set includes: the first bit string has significance in the value of the bit having a one-to-one mapping relationship with the RLC entities in the first RLC entity set.

As an embodiment, the meaning that the first bit string is used to indicate activation or deactivation of PDCP duplication of RLC entities in the first RLC entity set includes: the value of the bit in the first bit string, which does not have a one-to-one mapping relation with the RLC entities in the first RLC entity set, is meaningless.

As an embodiment, the meaning that the first bit string is used to indicate activation or deactivation of PDCP duplication of RLC entities in the first RLC entity set includes: and the value of the bit with one-to-one mapping relation with the RLC entities in the first RLC entity set in the first bit string is used for indicating the PDCP duplication of the RLC entity set with the mapping activated or deactivated.

As an embodiment, the first PDCP data PDU is a PDU for carrying RRC signaling.

As an embodiment, the first PDCP data PDU is a PDU for carrying an SDAP PDU.

As an embodiment, the D/C field indication of the first PDCP data PDU is data.

As an embodiment, the first PDCP data PDU is generated by the first PDCP entity.

As one embodiment, the first PDCP data PDU is transmitted using the first radio bearer.

As an embodiment, the first PDCP data PDU is any PDCP data PDU generated by the first PDCP entity after receiving the second signaling.

As an embodiment, there are Y RLC entities in the first RLC entity set that activate PDCP duplication, and the act of transmitting the first PDCP data PDU of the first PDCP entity includes: copying Y copies of the first PDCP data PDU and submitting the Y copies to the Y RLC entity processing in the first RLC entity set respectively.

As a sub-embodiment of this embodiment, the processing of the first PDCP data PDU by the Y RLC entities in the first RLC entity set includes segmentation.

As a sub-embodiment of this embodiment, the processing of the first PDCP data PDU by the Y RLC entities of the first RLC entity set includes adding an RLC header.

As a sub-embodiment of this embodiment, the processing of the first PDCP data PDU by the Y RLC entities in the first RLC entity set includes encapsulation into RLC PDUs and transmission to lower layers.

As an embodiment, PDCP copying of any RLC entity other than the first RLC entity in the first set of RLC entities is either activated or not activated.

As an embodiment, PDCP duplication of at least one main link RLC entity is activated for the first set of RLC entities.

As an embodiment, PDCP duplication of at least one secondary link RLC entity is activated for the first set of RLC entities.

As an embodiment, PDCP duplication of at least one RLC entity of the first set of RLC entities is activated.

As an embodiment, PDCP duplication in which the first RLC entity set exists at least one RLC entity other than the first RLC entity is activated.

As an embodiment, the first signaling indicates to activate PDCP duplication of the first RLC entity.

As an embodiment, the first logical channel identity list is composed of logical channel identities and includes at least one logical channel identity.

As an embodiment, the first logical channel identity list comprises a logical channel identity on at least one primary link and a logical channel identity on at least one secondary link.

As an embodiment, the logical channel identity of the main link is a logical channel identity of the Uu interface.

As an embodiment, the logical channel identity of the main link is the identity of the logical channel between the first node and the NG-RAN.

As an embodiment, the RLC entity associated with the logical channel identity of the primary link is a primary link RLC entity.

As an embodiment, the logical channel identity on the secondary link is a logical channel identity of a PC5 interface.

As an embodiment, the logical channel identity on the secondary link is an identity of a logical channel between the first node and the L2U 2N relay UE.

As an embodiment, the RLC entity associated with the logical channel identity on the secondary link is a secondary link RLC entity.

As an embodiment, the logical channel identity of the primary link is configured by the primary cell group of the first node.

As an embodiment, the logical channel identity on the secondary link is self-configured by the first node.

As one embodiment, the logical channel identity on the secondary link is configured by the L2U 2N relay UE of the first node.

As an embodiment, the first signaling is used to configure logical channel identities of a main link in the first logical channel identity list.

As an embodiment, RRC signaling of the PC5 interface is used to configure logical channel identities on secondary links in the first logical channel identity list.

As an embodiment, the primary link RLC entities in the first set of RLC entities are associated with only the primary link channel identities in the first list of logical channel identities.

As an embodiment, the secondary link RLC entities in the first set of RLC entities are associated with only logical channel identities on secondary links in the first list of logical channel identities.

As an embodiment, the logical channel identities of the primary links in the first logical channel identity list are associated with only primary link RLC entities in the first set of RLC entities.

As an embodiment, the logical channel identities on the secondary links in the first list of logical channel identities are associated with only the secondary link RLC entities in the first set of RLC entities.

As an embodiment, the meaning of any RLC entity in the first set of RLC entities associated with one logical channel identity in the first list of logical channel identities comprises: any RLC entity in the first RLC entity set has a mapping relationship with one logical channel identity in the first logical channel identity list.

As an embodiment, the meaning of any RLC entity in the first set of RLC entities associated with one logical channel identity in the first list of logical channel identities comprises: the identity of the logical channel corresponding to any RLC entity in the first RLC entity set belongs to the first logical channel identity list.

As an embodiment, any RLC entity in the first set of RLC entities corresponds to and only corresponds to one logical channel.

As an embodiment, the meaning of any RLC entity in the first set of RLC entities associated with one logical channel identity in the first list of logical channel identities comprises: and the corresponding RLC bearer of any RLC entity in the first RLC entity set has a mapping relation or an incidence relation with one logical channel identity in the first logical channel identity list.

As an embodiment, the meaning of any RLC entity in the first set of RLC entities associated with one logical channel identity in the first list of logical channel identities comprises: and the side link RLC channel corresponding to any RLC entity in the first RLC entity set has a mapping relation or an association relation with one logical channel identity in the first logical channel identity list.

As an embodiment, the meaning of any RLC entity in the first set of RLC entities associated with one logical channel identity in the first list of logical channel identities comprises: and the RLC bearing configuration index corresponding to any RLC entity in the first RLC entity set has a mapping relation or an association relation with one logical channel identity in the first logical channel identity list.

As an embodiment, the meaning of the one-to-one mapping relation of the first bit string to the N1 RLC entities other than the first RLC entity in the first RLC entity set with respect to the logical channel identities of the main link in the first logical channel identity list is: the logical channel identities of the primary link in the first logical channel identity list influence or determine how the first bit string maps with N1 RLC entities other than the first RLC entity in the first set of RLC entities.

As an embodiment, the meaning that the one-to-one mapping relationship between the first bit string and the N1 RLC entities other than the first RLC entity in the first RLC entity set is independent of the logical channel identities on the secondary link in the first logical channel identity list includes: the logical channel identities on the secondary link in the first logical channel identity list do not affect nor determine the mapping relationship between the first bit string and N1 RLC entities other than the first RLC entity in the first RLC entity set.

As an embodiment, the logical channel identities of the main links in the first logical channel identity list are different.

As an embodiment, the logical channel identities of the MCGs in the first logical channel identity list are different.

As an embodiment, the logical channel identities of the SCGs in the first logical channel identity list are different.

As an embodiment, the logical channel identities on the secondary links in the first logical channel identity list are different.

As an embodiment, the logical channel identities on the secondary links in the first logical channel identity list may be the same as the logical channel identities on the primary links.

As an embodiment, the one-to-one mapping relationship of the first bit string to N1 RLC entities other than the first RLC entity in the first set of RLC entities is only related to a logical channel identity of a main link in the first logical channel identity list.

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

As an embodiment, the first radio bearer is an MRB.

As an embodiment, the first radio bearer is an SRB.

As a sub-embodiment of this embodiment, the first radio bearer is SRB1.

As an embodiment, the peer entity of the first RLC entity is located in the SCG of the first node.

As a sub-embodiment of this embodiment, the first RLC entity is an RLC entity of the main link.

As a sub-embodiment of this embodiment, the first RLC entity is an RLC entity of the Uu interface.

As an embodiment, the peer entity of the first RLC entity is located in the L2U 2N relay UE of the first node.

As a sub-embodiment of this embodiment, the first RLC entity is an RLC entity on a secondary link.

As a sub-embodiment of this embodiment, the first RLC entity is an RLC entity of the PC5 interface.

As an embodiment, the peer entity of the first RLC entity is located in the MCG of the first node.

As an embodiment, the first signaling is used to indicate activation of PDCP duplication of any RLC entity of the first set of RLC entities associated with a logical channel identity on a secondary link in the first list of logical channel identities; the second signaling is only used to instruct activation or deactivation of PDCP duplication of RLC entities associated with the primary link in the first logical channel identity list other than the first RLC entity in the first set of RLC entities; mapping the lowest bit in the first bit string with a second RLC entity, wherein the second RLC entity belongs to the first RLC entity set; the second RLC entity is associated with a first logical channel identity; the logical channel identity with the smallest value in the logical channel identities of the main link in the first logical channel identity list associated with RLC entities other than the first RLC entity in the first RLC entity set is the first logical channel identity;

As a sub-embodiment of this embodiment, the second RLC entity is not the first RLC entity.

As a sub-embodiment of this embodiment, the second RLC entity maps only with the least significant bits of the first bit string.

As a sub-embodiment of this embodiment, the least significant bit of the first bit string being 0 is used to indicate that PDCP duplication of the second RLC entity is deactivated; the least significant bit of the first bit string being 1 is used to indicate activation of PDCP duplication of the second RLC entity.

As a sub-embodiment of this embodiment, the first logical channel identity belongs to the first logical channel identity list.

As an embodiment, the meaning of the sentence that the second RLC entity is associated with the first logical channel identity comprises: and the second RLC entity has a mapping relation with the first logic channel identity.

As an embodiment, the meaning of the sentence that the second RLC entity is associated with the first logical channel identity comprises: and the logical channel corresponding to the second RLC entity is identified by the first logical channel identity.

As an embodiment, the meaning of the sentence that the second RLC entity is associated with the first logical channel identity comprises: and the RLC bearer corresponding to the second RLC entity has a mapping relation with the first logic channel identity.

As an embodiment, the meaning of the sentence that the second RLC entity is associated with the first logical channel identity comprises: and the secondary link RLC channel corresponding to the second RLC entity has a mapping relation with the first logic channel identity.

As an embodiment, the meaning of the sentence that the second RLC entity is associated with the first logical channel identity comprises: the first logical channel identity is for the second RLC entity.

As an embodiment, the meaning of the sentence that the second RLC entity is associated with the first logical channel identity comprises: the first logical channel identity is for a secondary link RLC channel corresponding to the second RLC entity.

As an embodiment, the meaning of the sentence that the second RLC entity is associated with the first logical channel identity comprises: the first logical channel identity is for an RLC bearer corresponding to the second RLC entity.

As an embodiment, the meaning of the lowest value of the logical channel identities in the main link channel identities in the first logical channel identity list associated with RLC entities other than the first RLC entity in the first RLC entity set is that the meaning of the first logical channel identity includes: logical channel identities associated with main link RLC entities other than the first RLC entity in the first RLC entity set all belong to the first logical channel identity list; the logical channel identities associated with the main link RLC entities other than the first RLC entity in the first RLC entity set are all logical channel identities of the main link; the logical channel identity with the smallest value in the logical channel identities associated with the main link RLC entities other than the first RLC entity in the first RLC entity set is the first logical channel identity.

As an embodiment, the meaning of the lowest value of the logical channel identities in the main link channel identities in the first logical channel identity list associated with RLC entities other than the first RLC entity in the first RLC entity set is that the meaning of the first logical channel identity includes: the first logical channel identity is the smallest one of the values of the logical channel identities of the main link in the first logical channel identity list.

As a sub-embodiment of this embodiment, the first RLC entity is a sidelink RLC entity.

As a sub-embodiment of this embodiment, the first RLC entity is a primary link RLC entity; the value of the logical channel identity in the first logical channel identity list associated with the first RLC entity is greater than the value of the first logical channel identity.

As an embodiment, any two logical channel identities in the first logical channel identity list have different values.

As an embodiment, any logical channel identity in the first logical channel identity list is a value comprising N bits, where N is a positive integer.

As an embodiment, any logical channel identity in the first list of logical channel identities is a 5-bit or 6-bit value.

As an embodiment, the meaning of the lowest value of the logical channel identities in the main link channel identities in the first logical channel identity list associated with RLC entities other than the first RLC entity in the first RLC entity set is that the meaning of the first logical channel identity includes: the first logical channel identity is the next smallest one of the values of the logical channel identities of the main link in the first logical channel identity list.

As a sub-embodiment of this embodiment, the first RLC entity is a primary link RLC entity; the value of the logical channel identity in the first logical channel identity list associated with the first RLC entity is less than the value of the first logical channel identity.

As a sub-embodiment of this embodiment, the logical channel identity associated with the first RLC entity is not the first logical channel identity.

As a sub-embodiment of this embodiment, the value of the logical channel identity associated with the first RLC entity is the smallest of the logical channel identities in the primary link in the first list of logical channel identities.

As an embodiment, the meaning of any RLC entity in the first set of RLC entities for communication with the MCG includes: the opposite end RLC entity of any main link RLC entity in the first RLC entity set is positioned in the MCG.

As an embodiment, the meaning of any RLC entity in the first set of RLC entities for communication with the MCG includes: the RLC bearer corresponding to any main link RLC entity in the first RLC entity set is an RLC bearer between the first node and the MCG of the first node.

As an embodiment, the meaning of any RLC entity in the first set of RLC entities for communication with the MCG includes: the logical channel corresponding to any main link RLC entity in the first RLC entity set is a logical channel of a Uu interface with an MCG.

As an embodiment, the meaning of any RLC entity in the first set of RLC entities for communication with the MCG includes: the logical channel corresponding to any main link RLC entity in the first RLC entity set is a logical channel of a main link with the MCG.

As an embodiment, the meaning of any RLC entity in the first set of RLC entities for communication with the MCG includes: any primary link RLC entity of the first set of RLC entities is for transmitting data or signaling for the MCG.

As an embodiment, the meaning of any RLC entity in the first set of RLC entities for communication with the MCG includes: any primary link RLC entity of the first set of RLC entities is configured to receive data or signaling from the MCG.

As an embodiment, the meaning of any RLC entity in the first set of RLC entities for communication with the MCG includes: any secondary link RLC entity of the first set of RLC entities is used to transmit data or signaling for a radio bearer of the MCG.

As an embodiment, the meaning of any RLC entity in the first set of RLC entities for communication with the MCG includes: the radio bearer associated with any of the sidelink RLC entities in the first set of RLC entities is a radio bearer between the first node and the MCG.

As an embodiment, the meaning of any RLC entity in the first set of RLC entities for communication with the MCG includes: any secondary link RLC entity of the first set of RLC entities is for indirect path transmission.

As an embodiment, the meaning of any RLC entity in the first set of RLC entities for communication with the MCG includes: any secondary link RLC entity of the first set of RLC entities is used for communication with the MCG by the first node via relay.

As an embodiment, the meaning of any RLC entity in the first set of RLC entities for communication with the MCG includes: any secondary link RLC entity of the first set of RLC entities is associated with a radio bearer of the primary link.

As an embodiment, the meaning of any RLC entity in the first set of RLC entities for communication with the MCG includes: any secondary link RLC entity of the first set of RLC entities is not associated with a radio bearer on a secondary link.

As an embodiment, the first set of RLC entities comprises less than n1+1 RLC entities.

As a sub-embodiment of this embodiment, the first set of RLC entities comprises N1 RLC entities.

As an embodiment, the first set of RLC entities comprises more than n1+1 RLC entities.

As an embodiment, the first bit string only has a mapping relation with RLC entities in the main chain of the first RLC entity set.

As a sub-embodiment of this embodiment, the first bit string does not have a mapping relationship with RLC entities on the sidelink in the first set of RLC entities.

As an embodiment, the first bit string only has a mapping relation with RLC entities other than the first RLC entity on a main link in the first RLC entity set, where the first RLC entity is an RLC entity on the main link.

As an embodiment, the first set of RLC entities comprises N1+1 RLC entities, N2 RLC entities of the N1+1 RLC entities being associated with logical channel identities on secondary links in the first list of logical channel identities; the N2 bits in the first bit string have a first mapping relation with the N2 RLC entities; N1-N2 bits in the first bit string have a second mapping relation with the N2 RLC entities in the first RLC entity set and the RLC entities other than the first RLC entity; the value of the logical channel identity in the first logical channel identity list associated with the N2 RLC entities in the first RLC entity set and RLC entities other than the first RLC entity is used to determine the second mapping relationship;

As a sub-embodiment of this embodiment, the first RLC entity set includes RLC entities on N2 secondary links in total, and the N2 RLC entities in the first RLC entity set are all secondary link RLC entities.

As a sub-embodiment of this embodiment, the first set of RLC entities comprises altogether RLC entities on N2+1 secondary links, wherein the first RLC entity is an RLC entity on a secondary link.

As a sub-embodiment of this embodiment, the N2 is smaller than N1.

As an embodiment, the meaning of N2 RLC entities of the N1+1 RLC entities associated with a logical channel identity on a secondary link in the first logical channel identity list comprises: the first RLC entity set includes n1+1 RLC entities; the N2 RLC entities in the first RLC entity set have a mapping relationship with logical channel identities on a secondary link in the first logical channel identity list.

As an embodiment, the meaning of N2 RLC entities of the N1+1 RLC entities associated with a logical channel identity on a secondary link in the first logical channel identity list comprises: the first RLC entity set includes n1+1 RLC entities; the logical channels corresponding to the RLC bearers of the N2 RLC entities in the first RLC entity set are logical channels on a secondary link, and identities of the logical channels corresponding to the RLC bearers of the N2 RLC entities in the first RLC entity set belong to the first logical channel identity list.

As an embodiment, the meaning of N2 RLC entities of the N1+1 RLC entities associated with a logical channel identity on a secondary link in the first logical channel identity list comprises: the first RLC entity set includes n1+1 RLC entities; the sidelink RLC channels of the N2 RLC entities in the first RLC entity set are sidelink RLC channels on a sidelink, and logical channel identities associated with the sidelink RLC channels of the N2 RLC entities in the first RLC entity set belong to the first logical channel identity list.

As an embodiment, the meaning of N2 RLC entities of the N1+1 RLC entities associated with a logical channel identity on a secondary link in the first logical channel identity list comprises: the N2 RLC entities are sidelink RLC entities.

As an embodiment, the meaning that N1-N2 bits in the first bit string of the sentence have a second mapping relationship with the N2 RLC entities in the first RLC entity set and RLC entities other than the first RLC entity includes: the RLC entity of the first set of RLC entities that is mapped with the first bit string is not the first RLC entity nor the N2 RLC entities, and phrase mapping refers to the second mapping.

As an embodiment, the meaning that N1-N2 bits in the first bit string of the sentence have a second mapping relationship with the N2 RLC entities in the first RLC entity set and RLC entities other than the first RLC entity includes: the second mapping relation exists between N1-N2 bits in the first bit string and N1-N2 RLC entities in the first RLC entity set; any RLC entity of the N1-N2 RLC entities in the first set of RLC entities does not belong to the N2 RLC entities in the first set of RLC entities; the N1-N2 RLC entities in the first set of RLC entities also do not include the first RLC entity.

As an embodiment, the meaning that N1-N2 bits in the first bit string of the sentence have a second mapping relationship with the N2 RLC entities in the first RLC entity set and RLC entities other than the first RLC entity includes: the second mapping relation exists between N1-N2 bits in the first bit string and N1-N2 RLC entities in the first RLC entity set; the N1-N2 RLC entities in the first set of RLC entities are different from the N2 RLC entities in the first set of RLC entities; the N1-N2 RLC entities in the first set of RLC entities also do not include the first RLC entity.

As an embodiment, the meaning of the N2 bits and the N1-N2 bits in the first bit string of a sentence are different is: the N2 bits in the first bit string are different from bits occupied by the N1-N2 bits.

As an embodiment, the meaning of the N2 bits and the N1-N2 bits in the first bit string of a sentence being different is independent of whether the value is 0 or 1.

As an embodiment, the meaning of the N2 bits and the N1-N2 bits in the first bit string of a sentence are different is: the first bit string comprises N1 bits, the N1 bits of the first bit string are divided into two groups, the first group comprises N1-N2 bits, and the second group comprises N2 bits; the N1-N2 bits of the first bit string are the first set of bits; the N2 bits of the first bit string are the second set of bits.

As an embodiment, the first signaling indicates the first mapping relation.

As an embodiment, the first signaling indicates the second mapping relation.

As an embodiment, the first mapping relation is determined by a predefined algorithm.

As an embodiment, the second mapping is determined by a predefined algorithm.

As an embodiment, the N2 bits of the first bit string are consecutive; the N1-N2 bits of the first bit string are consecutive.

As a sub-embodiment of this embodiment, the meaning that the N2 bits of the first bit string of a sentence are consecutive is: the N2 bits of the first bit string are consecutive N2 bits in position in the first bit string.

As a sub-embodiment of this embodiment, the meaning that the N2 bits of the first bit string of a sentence are consecutive is: the N2 bits of the first bit string are consecutive regardless of the value of the N2 bits.

As a sub-embodiment of this embodiment, the meaning that the N2 bits of the first bit string of a sentence are consecutive is: the N2 bits of the first bit string are contiguous in the first bit string.

As a sub-embodiment of this embodiment, the meaning that the N2 bits of the first bit string of a sentence are consecutive is: the N2 bits of the first bit string are adjacent in the first bit string.

As a sub-embodiment of this embodiment, the meaning that the N1-N2 bits of the first bit string of a sentence are consecutive is: the positions of the N1-N2 bits of the first bit string in the first bit string are consecutive N1-N2 bits.

As a sub-embodiment of this embodiment, the meaning that the N1-N2 bits of the first bit string of a sentence are consecutive is: the N1-N2 bits of the first bit string are consecutive irrespective of the value of the N1-N2 bits.

As a sub-embodiment of this embodiment, the meaning that the N1-N2 bits of the first bit string of a sentence are consecutive is: the N1-N2 bits of the first bit string are contiguous in the first bit string.

As a sub-embodiment of this embodiment, the meaning that the N1-N2 bits of the first bit string of a sentence are consecutive is: the N1-N2 bits of the first bit string are adjacent in the first bit string.

As an embodiment, the first set of RLC entities comprises n1+n2+1 RLC entities, the first set of RLC entities comprises N2 sidelink RLC entities and is associated with logical channel identities on a sidelink in the first list of logical channel identities; the first set of RLC entities includes N1 primary link RLC entities and is associated with a primary link channel identity in the first list of logical channel identities; the first RLC entity does not belong to the N1 primary link RLC entities in the first set of RLC entities nor to the N2 secondary link RLC entities in the first set of RLC entities; the N2 bits in the first bit string have a first mapping relation with the N2 sidelink RLC entities in the first RLC entity set; the N1 bits in the first bit string have a second mapping relation with the N1 main link RLC entities in the first RLC entity set; the magnitude of the value of the logical channel identity in the first logical channel identity list associated with the N1 primary link RLC entities in the first set of RLC entities is used to determine the second mapping relationship;

The N2 bits and the N1 bits in the first bit string are different, the N2 and the N1 are positive integers, and the first mapping relationship and the second mapping relationship are both one-to-one mappings.

As a sub-embodiment of this embodiment, the smaller the value of the logical channel identity in the first logical channel identity list associated with the N1 main chain RLC entities in the first RLC entity set, the lower the position of the N1 bits of the first bit string associated with the N1 main chain RLC entities in the first RLC entity set.

As a sub-embodiment of this embodiment, the lowest bit of the N1 bits in the first bit string of the RLC entity in the first set of RLC entities associated with the smallest value of the logical channel identities in the first logical channel identity list associated with the N1 main link RLC entities in the first set of RLC entities.

As a sub-embodiment of this embodiment, the RLC entity in the first set of RLC entities associated with the largest one of the logical channel identities in the first list of logical channel identities associated with the N1 primary link RLC entities in the first set of RLC entities maps with the highest bit of the N1 bits in the first bit string.

As a sub-embodiment of this embodiment, the N1 bits in the first bit string are consecutive N1 bits in the first bit string.

As a sub-embodiment of this embodiment, the N2 bits in the first bit string are consecutive N2 bits in the first bit string.

As an embodiment, the N2 bits of the first bit string are higher order bits relative to the N1-N2 bits of the first bit string.

As an embodiment, the N2 bits of the first bit string are lower order bits relative to the N1-N2 bits of the first bit string.

Example 2

Embodiment 2 illustrates a schematic diagram of a network architecture according to the present application, as shown in fig. 2.

Fig. 2 illustrates a diagram of a network architecture 200 of a 5g nr, LTE (Long-Term Evolution) and LTE-a (Long-Term Evolution Advanced, enhanced Long-Term Evolution) system. The 5G NR or LTE network architecture 200 may be referred to as 5GS (5 GSystem)/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 disclosure 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). 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 (BSS), an Extended Service Set (ESS), a TRP (transmit receive node), or some other suitable terminology. The gNB203 provides the UE201 with an access point to the 5GC/EPC210. Examples of UE201 include a cellular telephone, a smart phone, a Session Initiation Protocol (SIP) phone, a laptop, a Personal Digital Assistant (PDA), a satellite radio, a non-terrestrial base station communication, a satellite mobile communication, 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-based vehicle, an automobile, 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 Protocal, 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. Internet services 230 include operator-corresponding internet protocol services, which may include, in particular, the internet, intranets, IMS (IP Multimedia Subsystem ) and packet-switched streaming services.

As an embodiment, the first node in the present application is UE201.

As an embodiment, the base station of the first node in the present application is the gNB203.

As an embodiment, the radio link from the UE201 to the NR node B is an uplink.

As an embodiment, the radio link from the NR node B to the UE201 is a downlink.

As an embodiment, the UE201 supports relay transmission.

As an embodiment, the UE201 includes a mobile phone.

As one example, the UE201 is a vehicle including an automobile.

As an embodiment, the UE201 supports sidelink transmission.

As an embodiment, the UE201 supports MBS transmissions.

As an embodiment, the UE201 supports MBMS transmission.

As an embodiment, the gNB203 is a macro cell (marcocelluar) base station.

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

As an embodiment, the gNB203 is a PicoCell (PicoCell) base station.

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

As one embodiment, the gNB203 is a satellite device.

Example 3

Embodiment 3 shows a schematic diagram of an embodiment of a radio protocol architecture of a user plane and a control plane according to the 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 for the control plane 300 for a first node (UE, satellite or aerial in gNB or NTN) and a second node (gNB, satellite or aerial in UE or NTN), or between two UEs, in three layers: layer 1, layer 2 and layer 3. Layer 1 (L1 layer) is the lowest layer and implements various PHY (physical layer) signal processing functions. The L1 layer will be referred to herein as PHY301. Layer 2 (L2 layer) 305 is above PHY301 and is responsible for the links between the first node and the second node and the two UEs 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 second node. The PDCP sublayer 304 provides multiplexing between different radio bearers and logical channels. The PDCP sublayer 304 also provides security by ciphering the data packets and handover support for the first node between second nodes. The RLC sublayer 303 provides segmentation and reassembly of upper layer data packets, retransmission of lost data packets, and reordering of data packets to compensate for out of order reception due to HARQ. The MAC sublayer 302 provides multiplexing between logical and transport channels. The MAC sublayer 302 is also responsible for allocating the various radio resources (e.g., resource blocks) in one cell among the first nodes. The MAC sublayer 302 is also responsible for HARQ 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 second node and the first node. The PC5-S (PC 5Signaling Protocol ) sublayer 307 is responsible for the processing of the signaling protocol of the PC5 interface. The radio protocol architecture of the user plane 350 includes layer 1 (L1 layer) and layer 2 (L2 layer), the radio protocol architecture for the first node and the second node 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 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. SRBs can be regarded as services or interfaces provided by the PDCP layer to higher layers, e.g., RRC layer. In the NR system, SRBs include SRB1, SRB2, and SRB3, and also SRB4 when the sidelink communication is involved, which are used to transmit different types of control signaling, respectively. SRB is a bearer between the UE and the access network for transmitting control signaling including RRC signaling between the UE and the access network. SRB1 is of particular interest for UEs, where after each UE establishes an RRC connection, there is SRB1 for transmitting RRC signaling, most of the signaling is transmitted through SRB1, and if SRB1 is interrupted or unavailable, the UE must perform RRC reestablishment. SRB2 is typically used only for transmitting NAS signaling or security related signaling. The UE may not configure SRB3. In addition to emergency services, the UE must establish an RRC connection with the network for subsequent communications. Although not shown, the first node may have several upper layers above the L2 layer 355. Further included are a network layer (e.g., IP layer) terminating at the P-GW on the network side and an application layer terminating at the other end of the connection (e.g., remote UE, server, etc.). For UEs involving relay services, its control plane may also include an adaptation sublayer SRAP (Sidelink Relay Adaptation Protocol, sidelink relay adaptation may be possible) 308, and its user plane may also include an adaptation sublayer SRAP358, the introduction of which may facilitate multiplexing and/or distinguishing data from multiple source UEs by lower layers, such as the MAC layer, e.g., the RLC layer.

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

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

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

As an embodiment, the second signaling in the present application is generated in RRC306 or MAC302 or PHY301 or PC5-S307.

As an embodiment, the third signaling in the present application is generated in RRC306 or MAC302 or PHY301 or PC5-S307.

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

As an embodiment, the second PDCP data PDU of the present application is generated in PDCP354.

Example 4

Embodiment 4 shows a schematic diagram of a first communication device and a second communication device according to an embodiment of the 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, and optionally 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 receive processor 470, a transmit processor 416, and optionally 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 data packets from the core network are provided to a controller/processor 475 at the second communication device 410. The controller/processor 475 implements the functionality of the L2 (Layer-2) 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 second communication device 450, the controller/processor 459 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover upper layer data packets from the core network. 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, a data source 467 is used at the first communication device 450 to provide upper layer data packets to a controller/processor 459. 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 based on radio resource allocations, 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, a 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 UE 450. Upper layer packets from the controller/processor 475 may be provided to the core network.

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 first signaling, the first signaling being used to configure a first PDCP entity and a first RLC entity set; the first RLC entity set includes at least one secondary link RLC entity and a primary link RLC entity; any RLC entity in the first set of RLC entities is associated with the first PDCP entity; the primary path of the first PDCP entity is associated with a first RLC entity of the first set of RLC entities; receiving second signaling, wherein the second signaling comprises a first bit string, and N1 bits of the first bit string have a one-to-one mapping relation with N1 RLC entities except the first RLC entity in the first RLC entity set; the first bit string is used to indicate activation or deactivation of PDCP duplication of RLC entities in the first set of RLC entities; transmitting a first PDCP data PDU of the first PDCP entity; the act of transmitting a first PDCP data PDU of the first PDCP entity includes: duplicating the first PDCP data PDU of the first PDCP entity and submitting duplicated copies to PDCP duplication activated RLC entities in the first RLC entity set, respectively; wherein N1 is a positive integer, any RLC entity in the first RLC entity set being associated with one logical channel identity in a first logical channel identity list; the one-to-one mapping relationship of the first bit string to the N1 RLC entities other than the first RLC entity in the first set of RLC entities is related to a logical channel identity on a primary link in the first list of logical channel identities, and the one-to-one mapping relationship of the first bit string to the N1 RLC entities other than the first RLC entity in the first set of RLC entities is unrelated to a logical channel identity on a secondary link in the first list of logical channel identities.

As an embodiment, the first communication device 450 includes: a memory storing a program of computer-readable instructions that, when executed by at least one processor, produce acts comprising: receiving first signaling, the first signaling being used to configure a first PDCP entity and a first RLC entity set; the first RLC entity set includes at least one secondary link RLC entity and a primary link RLC entity; any RLC entity in the first set of RLC entities is associated with the first PDCP entity; the primary path of the first PDCP entity is associated with a first RLC entity of the first set of RLC entities; receiving second signaling, wherein the second signaling comprises a first bit string, and N1 bits of the first bit string have a one-to-one mapping relation with N1 RLC entities except the first RLC entity in the first RLC entity set; the first bit string is used to indicate activation or deactivation of PDCP duplication of RLC entities in the first set of RLC entities; transmitting a first PDCP data PDU of the first PDCP entity; the act of transmitting a first PDCP data PDU of the first PDCP entity includes: duplicating the first PDCP data PDU of the first PDCP entity and submitting duplicated copies to PDCP duplication activated RLC entities in the first RLC entity set, respectively; wherein N1 is a positive integer, any RLC entity in the first RLC entity set being associated with one logical channel identity in a first logical channel identity list; the one-to-one mapping relationship of the first bit string to the N1 RLC entities other than the first RLC entity in the first set of RLC entities is related to a logical channel identity on a primary link in the first list of logical channel identities, and the one-to-one mapping relationship of the first bit string to the N1 RLC entities other than the first RLC entity in the first set of RLC entities is unrelated to a logical channel identity on a secondary link in the first list of logical channel identities.

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: transmitting first signaling, the first signaling being used to configure a first PDCP entity and a first RLC entity set; the first RLC entity set includes at least one secondary link RLC entity and a primary link RLC entity; any RLC entity in the first set of RLC entities is associated with the first PDCP entity; the primary path of the first PDCP entity is associated with a first RLC entity of the first set of RLC entities; transmitting a second signaling, wherein the second signaling comprises a first bit string, and N1 bits of the first bit string have a one-to-one mapping relation with N1 RLC entities except the first RLC entity in the first RLC entity set; the first bit string is used to indicate activation or deactivation of PDCP duplication of RLC entities in the first set of RLC entities; receiving a first PDCP data PDU of the first PDCP entity; the act of receiving a first PDCP data PDU of the first PDCP entity includes: receiving a copy of the first PDCP data PDU of the first PDCP entity from a peer RLC entity of at least one of the activated RLC entities in the first set of RLC entities; wherein N1 is a positive integer, any RLC entity in the first RLC entity set being associated with one logical channel identity in a first logical channel identity list; the one-to-one mapping relationship of the first bit string to the N1 RLC entities other than the first RLC entity in the first set of RLC entities is related to a logical channel identity on a primary link in the first list of logical channel identities, and the one-to-one mapping relationship of the first bit string to the N1 RLC entities other than the first RLC entity in the first set of RLC entities is unrelated to a logical channel identity on a secondary link in the first list of logical channel identities.

As one embodiment, the second communication device 410 includes: a memory storing a program of computer-readable instructions that, when executed by at least one processor, produce acts comprising: transmitting first signaling, the first signaling being used to configure a first PDCP entity and a first RLC entity set; the first RLC entity set includes at least one secondary link RLC entity and a primary link RLC entity; any RLC entity in the first set of RLC entities is associated with the first PDCP entity; the primary path of the first PDCP entity is associated with a first RLC entity of the first set of RLC entities; transmitting a second signaling, wherein the second signaling comprises a first bit string, and N1 bits of the first bit string have a one-to-one mapping relation with N1 RLC entities except the first RLC entity in the first RLC entity set; the first bit string is used to indicate activation or deactivation of PDCP duplication of RLC entities in the first set of RLC entities; receiving a first PDCP data PDU of the first PDCP entity; the act of receiving a first PDCP data PDU of the first PDCP entity includes: receiving a copy of the first PDCP data PDU of the first PDCP entity from a peer RLC entity of at least one of the activated RLC entities in the first set of RLC entities; wherein N1 is a positive integer, any RLC entity in the first RLC entity set being associated with one logical channel identity in a first logical channel identity list; the one-to-one mapping relationship of the first bit string to the N1 RLC entities other than the first RLC entity in the first set of RLC entities is related to a logical channel identity on a primary link in the first list of logical channel identities, and the one-to-one mapping relationship of the first bit string to the N1 RLC entities other than the first RLC entity in the first set of RLC entities is unrelated to a logical channel identity on a secondary link in the first list of logical channel identities.

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

As an embodiment, the second communication device 410 corresponds to a second 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 an in-vehicle terminal.

As an embodiment, the second communication device 450 is a relay.

As an example, the second communication device 410 is a satellite.

As an example, the second communication device 410 is an aircraft.

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

As an example, a receiver 454 (including an antenna 452), a receive processor 456 and a controller/processor 459 are used in the present application to receive the first signaling.

As an example, a receiver 454 (including an antenna 452), a receive processor 456 and a controller/processor 459 are used in the present application to receive the second signaling.

As an example, a receiver 454 (including an antenna 452), a receive processor 456 and a controller/processor 459 are used in the present application to receive the third signaling.

As an example, a transmitter 454 (including an antenna 452), a transmit processor 468 and a controller/processor 459 are used in the present application to transmit the first PDCP data PDU.

As an example, a transmitter 454 (including an antenna 452), a transmit processor 468 and a controller/processor 459 are used in the present application to transmit the second PDCP data PDU.

As an example, a transmitter 418 (including an antenna 420), a transmit processor 416 and a controller/processor 475 are used in the present application to transmit the first signaling.

As an example, a transmitter 418 (including an antenna 420), a transmit processor 416 and a controller/processor 475 are used in the present application to transmit the second signaling.

As an example, a transmitter 418 (including an antenna 420), a transmit processor 416 and a controller/processor 475 are used in the present application to transmit the third signaling.

As an example, a receiver 418 (including an antenna 420), a receive processor 470 and a controller/processor 475 are used in the present application to receive the first PDCP data PDU.

As an example, a receiver 418 (including an antenna 420), a receive processor 470 and a controller/processor 475 are used in the present application to receive the second PDCP data PDU.

Example 5

Embodiment 5 illustrates a wireless signal transmission flow diagram according to one embodiment of the application, as shown in fig. 5. In fig. 5, U01 corresponds to a first node of the present application, U02 corresponds to a second node of the present application, and it is specifically illustrated that the order in this example is not limited to the order of signal transmission and the order of implementation in the present application, and steps in F51 are optional.

For the followingFirst node U01Receiving a first signaling in step S5101; receiving a second signaling in step S5102; transmitting a first PDCP data PDU in step S5103; receiving a third signaling in step S5104; a second PDCP data PDU is transmitted in step S5105.

For the followingSecond node U02Transmitting a first signaling in step S5201; transmitting a second signaling in step S5202; receiving a first PDCP data PDU in step S5203; transmitting a third signaling in step S5204; a second PDCP data PDU is received in step S5205.

In embodiment 5, the first signaling is used to configure a first PDCP entity and a first RLC entity set; the first RLC entity set includes at least one secondary link RLC entity and a primary link RLC entity; any RLC entity in the first set of RLC entities is associated with the first PDCP entity; the primary path of the first PDCP entity is associated with a first RLC entity of the first set of RLC entities;

The second signaling comprises a first bit string, and N1 bits of the first bit string have a one-to-one mapping relation with N1 RLC entities except the first RLC entity in the first RLC entity set; the first bit string is used to indicate activation or deactivation of PDCP duplication of RLC entities in the first set of RLC entities;

the generator of the first PDCP data PDU is the first PDCP entity; the act of transmitting a first PDCP data PDU of the first PDCP entity includes: duplicating the first PDCP data PDU of the first PDCP entity and submitting duplicated copies to PDCP duplication activated RLC entities in the first RLC entity set, respectively;

As an embodiment, the first node U01 is a U2N relay UE.

As an embodiment, the first node U01 is a U2N remote UE.

As an embodiment, the first node U01 is an NR ProSe U2N remote UE.

As an embodiment, the second node U02 is a base station.

As an embodiment, the second node U02 is a master cell group or a base station of a master cell group.

As an embodiment, the second node U02 is a slave cell group or a base station of a cell group.

As an embodiment, the second node U02 is a primary cell of the first node U01.

As an embodiment, the second node U02 is a master cell group of the first node U01.

As an embodiment, the second node U02 corresponds to a base station corresponding to a cell group of the present application.

As an embodiment, the second signaling is sent after the first signaling.

As an embodiment, the second signaling is received after the first signaling.

As an embodiment, the sending of the first signaling uses a direct path and/or an indirect path.

As an embodiment, the sending of the second signaling uses a direct path and/or an indirect path.

As an embodiment, the first signaling is received by at least one RLC entity of the first set of RLC entities.

As an embodiment, the first signaling is received by RLC entities other than the first set of RLC entities.

As an embodiment, the second signaling is received by at least one RLC entity of the first set of RLC entities.

As an embodiment, the second signaling is received by RLC entities other than the first set of RLC entities.

As an embodiment, the second signaling is signaling below the RLC layer.

As an embodiment, the first signaling is received by the first PDCP entity.

As an embodiment, the first signaling is received by a PDCP entity other than the first PDCP entity.

As an embodiment, the first node U01 establishes the first PDCP entity in response to receiving the first signaling.

As an embodiment, the first node U01 establishes at least one RLC entity of the first set of RLC entities in response to receiving the first signaling.

As an embodiment, the first signaling indicates a logical channel identity of a main link in the first logical channel identity list.

As an embodiment, in response to receiving the first signaling, the first node U01 allocates a logical channel identity associated with a sidelink RLC entity in at least one of the first RLC entity sets; the allocated logical channel identities associated with the sidelink RLC entities in the at least one first set of RLC entities belong to the first list of logical channel identities.

As an embodiment, the logical channel identity associated with the sidelink RLC entity in the first RLC entity set is configured by one of the first node U01 or the relay node of the first node.

As an embodiment, the first signaling is used to indicate that the first PDCP entity is associated with any one of the first RLC entities.

As an embodiment, the first signaling is used to indicate a logical channel identity associated with any of the primary link RLC entities in the first RLC entity.

As an embodiment, the first signaling is used to indicate a sidelink RLC channel associated with any of the first RLC entities associated with a logical channel identity in the first logical channel identity list.

As an embodiment, the first signaling is sent using SRB 1.

As an embodiment, the transmission of the first signaling does not use a relay node.

As an embodiment, the transmission of the second signaling does not use a relay node.

As an embodiment, the first PDCP data PDU is transmitted by a relay node.

As an embodiment, whether the first PDCP data PDU is transmitted via a relay node is related to whether PDCP duplication of a sidelink RLC entity of the first RLC entity set is activated.

As an embodiment, the third signaling is used to instruct to activate or deactivate PDCP duplication of RLC entities in the first set of RLC entities associated with logical channel identities on secondary links in the first list of logical channel identities;

As a sub-embodiment of this embodiment, the third signaling is or includes a MAC CE.

As a sub-embodiment of this embodiment, the third signaling is or includes RRC signaling.

As a sub-embodiment of this embodiment, the meaning that the logical channel identity in the first logical channel identity list associated with the first RLC entity is the logical channel identity of the primary link includes: the first RLC entity is a primary link RLC entity.

As a sub-embodiment of this embodiment, the meaning that the logical channel identity in the first logical channel identity list associated with the first RLC entity is the logical channel identity of the primary link includes: the first RLC entity is associated with a logical channel identity of a primary link; the first RLC entity is not associated with a logical channel identity on a sidelink; the logical channel identity associated with the first RLC entity belongs to the first logical channel identity list.

As a sub-embodiment of this embodiment, in response to receiving the third signaling, PDCP duplicates of all secondary link RLC entities in the first set of RLC entities are activated or PDCP duplicates of all secondary link RLC entities in the first set of RLC entities are deactivated; the first RLC entity is not a sidelink RLC entity.

As a sub-embodiment of this embodiment, in response to receiving the third signaling, PDCP duplicates of all secondary link RLC entities in the first set of RLC entities other than the first RLC entity are activated or PDCP duplicates of all secondary link RLC entities in the first set of RLC entities other than the first RLC entity are deactivated; the first RLC entity is a sidelink RLC entity.

As an embodiment, the third signaling is used to indicate to activate or deactivate PDCP copying of the first PDCP entity.

As an embodiment, the first PDCP entity generates the second PDCP data PDU.

As one embodiment, the second PDCP data PDU is transmitted using the first radio bearer.

As an embodiment, the first node U01 transmits a second PDCP data PDU of the first PDCP entity in step S5105.

As an embodiment, the act of transmitting the second PDCP data PDU of the first PDCP entity includes: submitting the second PDCP data PDU of the first PDCP entity to either the first RLC entity or a third RLC entity;

wherein a split secondary path (split secondary path) of the first PDCP entity is associated with the third RLC entity of the first set of RLC entities; the first RLC entity and the third RLC entity are both configured to communicate with an MCG; one of the first RLC entity and the third RLC entity is associated with a logical channel identity on a primary link in the first logical channel identity list and the other is associated with a logical channel identity on a secondary link in the first logical channel identity list; at least one of the first signaling and the third signaling is used to implicitly indicate a split secondary path of the first PDCP entity.

As a sub-embodiment of this embodiment, the first node U01 determines whether to submit the second PDCP data PDU of the first PDCP entity to the first RLC entity or the third RLC entity according to implementation.

As a sub-embodiment of this embodiment, the first node U01 randomly submits the second PDCP data PDU of the first PDCP entity to the first RLC entity or the third RLC entity.

As a sub-embodiment of this embodiment, the third RLC entity is different from the first RLC entity.

As a sub-embodiment of this embodiment, the third RLC entity is the second RLC entity.

As a sub-embodiment of this embodiment, the third RLC entity is not the second RLC entity.

As a sub-embodiment of this embodiment, the first set of RLC entities comprises at least 3 RLC entities.

As a sub-embodiment of this embodiment, the first signaling indicates a logical channel identity of a split slave path of the first PDCP entity, the logical channel identity of the split slave path belonging to the first logical channel identity list, the third RLC entity being associated with the logical channel identity of the split slave path.

As a sub-embodiment of this embodiment, the logical channel identity of the split slave path indicated by the first signaling is a logical channel identity of a master link.

As a sub-embodiment of this embodiment, the first signaling indicates a sidelink RLC channel identity of a split sidelink RLC channel identity of the first PDCP entity, a logical channel identity corresponding to the sidelink RLC channel identity of the split sidelink RLC channel identity of the first PDCP entity belongs to the first logical channel identity list, and a logical channel identity in the first logical channel identity list associated with the third RLC entity is the logical channel identity corresponding to the sidelink RLC channel identity of the split sidelink RLC entity.

As a sub-embodiment of this embodiment, the first signaling indicates a sub-link RLC channel identity of a split secondary path of the first PDCP entity, and an RLC entity corresponding to the sub-link RLC channel identity of the split secondary path of the first PDCP entity is the third RLC entity; the logical channel identity associated with the third RLC entity is a logical channel identity on a sidelink and belongs to the first list of logical channel identities.

As a sub-embodiment of this embodiment, the logical channel identity of the split secondary path indicated by the first signaling is a logical channel identity on a secondary link.

As a sub-embodiment of this embodiment, the meaning of the sentence that both the first RLC entity and the third RLC entity are used for communication with the MCG includes: the first RLC entity and the third RLC entity are respectively associated with the first PDCP entity, that is, the first RLC entity and the third RLC entity are both used for transmitting data of the first PDCP entity, and a peer PDCP entity of the first PDCP entity is located in an MCG.

As a sub-embodiment of this embodiment, the meaning of the sentence that both the first RLC entity and the third RLC entity are used for communication with the MCG includes: the first RLC entity and the third RLC entity are respectively associated with the first radio bearer, which is a radio bearer between the first node U01 and MCG.

As a sub-embodiment of this embodiment, the meaning of the sentence that both the first RLC entity and the third RLC entity are used for communication with the MCG includes: the data of the first radio bearer is transmitted or processed by the first RLC entity and the third RLC entity, and the first radio bearer is a radio bearer between the first node U01 and the MCG.

As a sub-embodiment of this embodiment, the first RLC entity is associated with a logical channel identity on a primary link in the first logical channel identity list and the third RLC entity is associated with a logical channel identity on a secondary link in the first logical channel identity list.

As a sub-embodiment of this embodiment, the third RLC entity is associated with a logical channel identity on a primary link in the first logical channel identity list, and the first RLC entity is associated with a logical channel identity on a secondary link in the first logical channel identity list.

As a sub-embodiment of this embodiment, the first RLC entity is associated with only one logical channel identity in the first list of logical channel identities.

As a sub-embodiment of this embodiment, the third RLC entity is associated with only one logical channel identity in the first list of logical channel identities.

As a sub-embodiment of this embodiment, the meaning of the sentence that at least one of the first signaling and the third signaling is used to implicitly indicate the split slave path of the first PDCP entity includes: the first signaling is used to implicitly indicate a split slave path of the first PDCP entity.

As a sub-embodiment of this embodiment, the meaning of the sentence that at least one of the first signaling and the third signaling is used to implicitly indicate the split slave path of the first PDCP entity includes: the third signaling is used to implicitly indicate a split slave path of the first PDCP entity.

As a sub-embodiment of this embodiment, the meaning of the sentence that at least one of the first signaling and the third signaling is used to implicitly indicate the split slave path of the first PDCP entity includes: both the first signaling and the third signaling are used to implicitly indicate a split secondary path of the first PDCP entity.

As a sub-embodiment of this embodiment, the meaning of the sentence that at least one of the first signaling and the third signaling is used to implicitly indicate the split slave path of the first PDCP entity includes: said at least one of said first signaling and said third signaling indicates only a sidelink RLC channel identity of said split secondary path of said first PDCP entity and not a logical channel identity; the sidelink RLC channel identity of the split secondary path of the first PDCP entity corresponds one-to-one with the logical channel identity of the split secondary path of the first PDCP entity.

As a sub-embodiment of this embodiment, the meaning of the sentence that at least one of the first signaling and the third signaling is used to implicitly indicate the split slave path of the first PDCP entity includes: said at least one of said first signaling and said third signaling indicates only a sidelink RLC channel identity of said split secondary path of said first PDCP entity and not an identity of a relay node; the first node U01 communicates with the second node U02 through only one relay node.

As a sub-embodiment of this embodiment, the meaning of the sentence that at least one of the first signaling and the third signaling is used to implicitly indicate the split slave path of the first PDCP entity includes: said at least one of said first signaling and said third signaling indicates only a sidelink RLC channel identity of said split secondary path of said first PDCP entity and not whether it is cell group or relay; when a sidelink RLC channel identity of the split secondary path of the first PDCP entity is indicated, the split secondary path of the first PDCP entity uses a sidelink or relay.

As a sub-embodiment of this embodiment, the meaning of the sentence that at least one of the first signaling and the third signaling is used to implicitly indicate the split slave path of the first PDCP entity includes: said at least one of said first signaling and said third signaling indicates only a logical channel identity of said split secondary path of said first PDCP entity and does not indicate said cell group of said split secondary path of said first PDCP entity; the split secondary path of the first PDCP entity belongs to a cell group other than the cell group described by the first RLC entity.

As a sub-embodiment of this embodiment, the first PDCP entity has only one split secondary path.

As a sub-embodiment of this embodiment, the meaning of the sentence that at least one of the first signaling and the third signaling is used to implicitly indicate the split slave path of the first PDCP entity includes: when at least one of the first signaling and the third signaling indicates a sidelink RLC channel identity of a split slave path of the first PDCP entity, the split slave path of the first PDCP entity is for a sidelink or for a relay or PC5 interface; when at least one of the first signaling and the third signaling indicates a logical channel identity of a split secondary path of the first PDCP entity, the split secondary path of the first PDCP entity is for a primary path or Uu interface or MCG or SCG.

Example 6

Embodiment 6 illustrates a schematic diagram of a protocol stack for relaying communications according to one embodiment of the present application, as shown in fig. 6.

And the drawing 6 is divided into three subgraphs (a), (b) and (c).

The protocol stack shown in fig. 6 is applicable to L2U 2N relay communication, and embodiment 6 is based on embodiment 3.

Fig. 6 (a) corresponds to a user plane protocol stack in L2U 2N relay communication; fig. 6 (b) corresponds to a control plane protocol stack in L2U 2N relay communication.

As an embodiment, the first relay is a relay when the first node uses an indirect path.

As one embodiment, the first relay is an L2U 2N relay UE communicating between the first node and the MCG.

As an embodiment, the second node in fig. 6 is a PCell or a gcb corresponding to the PCell of the first node.

As an embodiment, the second node in fig. 6 is the MCG of the first node or the gNB corresponding to the MCG.

As an embodiment, the second node in fig. 6 is a gNB to which the first node is connected.

As an example, the second node in fig. 6 has an RRC connection with the first node.

As an embodiment, the second node in fig. 6 corresponds to the second node of the present application.

In embodiment 6, the PC5 interface is an interface between the first node and the first relay, and the PC5 interface-related protocol entity { PC5-SRAP, PC5-RLC, PC5-MAC, PC5-PHY } terminates at the first node and the first relay; the Uu interface is an interface between the UE and the second node, and protocol entities of the Uu interface are respectively terminated by the UE and the second node.

As an embodiment, the first relay is a U2N relay UE, and the first relay provides an L2U 2N relay service to the first node before performing the first signaling.

As an embodiment, the first relay is a U2N relay UE, the first relay does not provide the L2U 2N relay service to the first node before performing the first signaling, and the first node uses the U2N relay service provided by the first relay after receiving the first signaling.

As an embodiment, the first node and the first relay are both UEs.

As an embodiment, the protocol entity { Uu-SRAP, uu-RLC, uu-MAC, uu-PHY } of the Uu interface terminates in said first relay and gNB.

As an embodiment, in (a), the protocol entity { Uu-SDAP, uu-PDCP } of the Uu interface ends with the first node and the second node, and the SDAP PDU and PDCP PDU of the first node are forwarded using the first relay, but the first relay does not modify the SDAP PDU and PDCP PDU of the first node, that is, the SDAP PDU and PDCP PDU sent by the first node to the gNB are transparent to the first relay.

As an embodiment, in (b), the protocol entity { Uu-RRC, uu-PDCP } of the Uu interface terminates at the first node and the second node, and the RRC PDU and PDCP PDU of the first node are forwarded by the first relay, but the first relay does not modify the RRC PDU and PDCP PDU sent by the first node, that is, the RRC PDU and PDCP PDU sent by the first node to the gNB are transparent to the first relay.

As an example, in (a), PC5-SRAP corresponds to SRAP357 in fig. 3, PC5-RLC corresponds to RLC353 in fig. 3, PC5-MAC corresponds to MAC352 in fig. 3, and PC5-PHY corresponds to PHY351 in fig. 3.

As an example, in (a), uu-SDAP corresponds to SDAP356 in fig. 3, uu-PDCP corresponds to PDCP354 in fig. 3.

As an example, in (b), PC5-SRAP corresponds to SRAP307 in fig. 3, PC5-RLC corresponds to RLC303 in fig. 3, PC5-MAC corresponds to MAC302 in fig. 3, and PC5-PHY corresponds to PHY301 in fig. 3.

As an example, in (b), uu-RRC corresponds to RRC306 in fig. 3 and Uu-PDCP corresponds to PDCP304 in fig. 3.

As an example, one cell of the second node in fig. 6 is the PCell of the first relay, and the first relay is in an RRC connected state.

As an embodiment, the first node is in an RRC connected state.

As an embodiment, the MCG of the first node is also the MCG of the first relay.

As an example, PC5-SRAP is used only for specific RBs or messages or data.

As a sub-embodiment of this embodiment, the PC5-SRAP layer is not used when the first relay forwards the system information of the gNB.

As an embodiment, the SRB1 of the first node is the SRB1 between the first node and the gNB in fig. 6 (b), and the associated protocol entities include Uu-PDCP and Uu-RRC.

As an example, in fig. 6, the communication between the first node and the second node uses an indirect path.

As an example, in fig. 6, the communication between the first node and the second node uses a direct path.

As an example, in fig. 6, the communication between the first node and the second node uses both a direct path and an indirect path.

As an embodiment, the first signaling is generated by the Uu-RRC of the second node in fig. 6 (b), and received by the Uu-RRC of the first node.

As an embodiment, the first signaling is transparent to the first medium and then to the second medium.

As an embodiment, the transmission of the first signaling is applicable to fig. 6 (c) without using the first relay.

As an embodiment, the second signaling is applicable to the protocol structure of fig. 6 (b).

As an embodiment, the third signaling is applicable to the protocol structure of fig. 6 (b).

As an embodiment, the Uu-PDCP of the first node is associated with PC5-RLC, or with PC5-RLC through PC5-SRAP, when using an indirect path.

As an embodiment, when using the direct path, the first node will establish Uu-RLC, with which Uu-PDCP of the first node is associated.

As a sub-embodiment of this embodiment, the first node releases PC5-RLC after switching to the direct path.

As a sub-embodiment of this embodiment, the first node releases the PC5-SRAP after switching to the direct path.

As a sub-embodiment of this embodiment, the first node releases the PC5-MAC and PC5-PHY after switching to the direct path.

As a sub-embodiment of this embodiment, the first node no longer uses PC5-SRAP after switching to the direct path.

As a sub-embodiment of this embodiment, there is no other protocol layer between Uu-PDCP and Uu-RLC of the first node after switching to the direct path.

As an embodiment, (c) in fig. 6 is a protocol stack when the first node and the second node communicate when no relay is used.

As an embodiment, (c) in fig. 6 is a protocol stack when no relay is used, i.e. when a direct path is used, when the first node communicates with the second node.

As an embodiment, the first PDCP entity corresponds to Uu-PDCP of the first node in (a).

As an embodiment, the peer entity of the first PDCP entity corresponds to Uu-PDCP of the second node in (a).

As an embodiment, the first PDCP entity corresponds to Uu-PDCP of the first node in (b).

As an embodiment, the peer entity of the first PDCP entity corresponds to Uu-PDCP of the second node in (b).

As an embodiment, the main RLC entity in the first RLC entity set corresponds to the Uu-RLC of the first node in (c).

As an embodiment, the sidelink RLC entities in the first RLC entity set correspond to the PC5-RLC of the first node in (a).

As a sub-embodiment of this embodiment, the peer RLC entity of the sidelink RLC entity in the first RLC entity set is located in the first relay and corresponds to the PC5-RLC of the first relay.

As an embodiment, the sidelink RLC entities in the first RLC entity set correspond to the PC5-RLC of the first node in (b).

As an embodiment, the first RLC entity corresponds to the PC5-RLC of the first node in (a).

As an embodiment, the first RLC entity corresponds to PC5-RLC of the first node in (b).

As an embodiment, the first RLC entity corresponds to Uu-RLC of the first node in (c).

As an embodiment, the logical channel between the first node and the second node in the logical channel identity (c) of the main link in the first logical channel identity list.

As an embodiment, the first node in the logical channel identity (a) on the secondary link in the first logical channel identity list is the logical channel between the first node and the first relay.

As an embodiment, the first node in the logical channel identity (b) on the secondary link in the first logical channel identity list is the logical channel between the first node and the first relay.

As an embodiment, the first radio bearer corresponding to the first PDCP entity is a radio bearer between the first node and the second node.

As one embodiment, the first PDCP data PDU of the first PDCP is generated in Uu-PDCP of the first node in (a) or (b) or (c).

As an embodiment, the primary link is a link when the first node and the second node employ (c) communication.

As an embodiment, the sidelink is a link between the first node and the first relay when the first node and the second node communicate using (a) and/or (b).

Example 7

Embodiment 7 illustrates a schematic diagram of a radio bearer according to one embodiment of the present application, as shown in fig. 7.

Embodiment 7 further shows on the basis of embodiment 3 that one PDCP entity is associated with two RLC entities, RLC1 and RLC2, wherein each RLC entity is associated with a different MAC, RLC1 is associated with MAC1 and RLC2 is associated with MAC2, respectively.

Embodiment 7 shows a protocol structure of the first node side.

As an example, fig. 7 is applicable to SRBs including SRB 1.

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

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

As an example, the protocol structure shown in fig. 7 is a split SRB, i.e., split SRB.

As an example, the protocol structure shown in fig. 7 is a split DRB, i.e., split DRB.

As an example, fig. 7 is adapted for transmission.

As an example, fig. 7 is adapted for reception.

As an example, the first protocol entity in fig. 7 is RRC, and fig. 7 is for SRBs including SRB 1.

As an embodiment, the first protocol entity in fig. 7 is an SDAP, and fig. 7 is for a DRB.

As an embodiment, PDCP PDUs in which RRC messages are formed by the processing of the PDCP entity are transmitted through RLC 1.

As an embodiment, PDCP PDUs in which RRC messages are formed by the processing of the PDCP entity are transmitted through RLC 2.

As an embodiment, PDCP PDUs in which the RRC message is formed through the processing of the PDCP entity are transmitted through RLC1 or RLC 2.

As an embodiment, the RRC message is duplicated through PDCP PDUs formed by the processing of the PDCP entity, and is transmitted through RLC1 and RLC2 at the same time.

As an embodiment, the SRB1 is configured to carry the first signaling and the first message.

As an embodiment, the primary path of the SRB1 is for RLC 1.

As an embodiment, the primary path of the SRB1 is for RLC 2.

As an embodiment, both RLC2 and MAC2 are for sidelink communications.

As an embodiment, both RLC1 and MAC2 are for primary link communication, i.e. not for secondary link communication.

As an embodiment, the RLC1 and MAC1 are for a primary cell group.

As an embodiment, the RLC1 and MAC1 are for a cell group.

As an embodiment, the first PDCP entity corresponds to PDCP in fig. 7.

As an embodiment, the primary link RLC entity included in the first RLC entity set corresponds to RLC1 in fig. 7, and the secondary link RLC entity included in the first RLC entity set corresponds to RLC2 in fig. 7.

Example 8

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

The first node in embodiment 8 corresponds to the first node of the present application.

As an embodiment, the second node in embodiment 8 corresponds to the second node of the present application.

As an embodiment, the second node in embodiment 8 is a cell group of the first node.

As an embodiment, the second node in embodiment 8 is a primary cell of the first node.

As an embodiment, the second node in embodiment 8 is a gNB corresponding to a master cell group of the first node.

As an embodiment, the second node in embodiment 8 is a PCell of the first node.

As an embodiment, the second node in embodiment 8 is a transmitting point of the primary cell group of the first node.

As an embodiment, the third node in embodiment 8 is a relay node of the first node.

As an embodiment, the third node in embodiment 8 is a U2N relay of the first node.

As an embodiment, the third node in embodiment 8 is a relay between the first node and the network.

As an embodiment, the third node in embodiment 8 is the one L2U 2N relay UE.

As an embodiment, the third node in embodiment 8 is a relay node between the first node and the second node.

As an embodiment, the third node in embodiment 8 is an L2U 2N relay UE of the first node.

As an embodiment, the third node in embodiment 8 is one SCell of the primary cell group of the first node.

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

As an embodiment, the third node in embodiment 8 is a PSCell or SCG of the first node.

As an embodiment, the third node in embodiment 8 is a transmitting point of the primary cell group of the first node.

As an example, the third node in example 8 is a cell other than a PCell.

As an embodiment, the third node in embodiment 8 is a neighbor cell.

As an embodiment, the third node in embodiment 8 is a repeater of the primary cell group of the first node.

As an example, the third node in example 8 is one node of a TN.

As an embodiment, the third node in embodiment 8 is a node of NTN.

As an embodiment, the direct path is a manner or a transmission path in which the first node and the second node do not communicate through the third node.

As an embodiment, the indirect path is a manner or a transmission path by which the first node and the second node communicate through the third node.

As an example, the arrowed lines in fig. 8 represent logical channels.

As an example, the arrowed line in fig. 8 represents an RLC bearer.

As an example, the arrowed line in fig. 8 represents a sidelink RLC channel.

As an example, the bold arrowed line in fig. 8 represents the sidelink RLC channel.

As an example, the bold arrowed line in fig. 8 represents an indirect path.

As an example, the primary link of the present application is the link between the first node and the second node, represented by thin lines in fig. 8; the sidelink of the present application is a link between said first node and said third node, indicated by a bold line in fig. 8.

As an embodiment, the first set of RLC entities includes all RLC entities of the first node for communicating with the MCG.

As an embodiment, when the first RLC entity is a primary link RLC entity, the first node transmits the first PDCP data PDU using both a direct path and an indirect path only when PDCP of a secondary link RLC entity in the first RLC entity set is activated.

As an embodiment, when the first RLC entity is a primary link RLC entity, the first node transmits the first PDCP data PDU using both the primary link RLC entity and the secondary link RLC entity only when PDCP of the secondary link RLC entities in the first set of RLC entities is activated.

As an embodiment, when the first RLC entity is a sidelink RLC entity, the first node transmits the first PDCP data PDU using both a direct path and an indirect path only when PDCP of a main link RLC entity of the first RLC entity set is activated.

As an embodiment, when the first RLC entity is a sidelink RLC entity, the first node transmits the first PDCP data PDU using both the main link RLC entity and the sidelink RLC entity only when PDCP of the main link RLC entity of the first RLC entity set is activated.

As an embodiment, the first set of RLC entities comprises 2 RLC entities.

As an embodiment, the communication interface between the first node and the third node is a PC5 interface, the first node and the third node communicating via a sidelink.

Example 9

Embodiment 9 illustrates a schematic diagram of a mapping relationship between a first bit string and a first RLC entity set according to one embodiment of the present application, as illustrated in fig. 9.

Fig. 9 shows a mapping relationship between the first bit string and the first RLC entity set, and a mapping relationship between the first RLC entity set and logical channel identities in the first logical channel identity list.

The first bit string shown in fig. 9 includes N bits, where N is a positive integer.

As one embodiment, the N is equal to the N1.

As an embodiment, the N is equal to n1+n2.

As a sub-embodiment of this embodiment, N1 bits in the first bit string are mapped one-to-one with the main RLC entity in the first RLC entity set; n2 bits in the first bit string are mapped with the sidelink RLC entities in the first RLC entity set one by one; the N1 bits in the first bit string are different from the N2 bits in the first bit string.

As an embodiment, the first set of RLC entities comprises N RLC entities.

As a sub-embodiment of this embodiment, the N is equal to the N1.

As a sub-embodiment of this embodiment, the N RLC entities in the first set of RLC entities are mapped one-to-one with the N bits of the first bit string.

As an embodiment, the first RLC entity set includes more than N RLC entities, where N1 RLC entities are mapped one-to-one with N1 bits of the first bit string.

As a sub-embodiment of this embodiment, the first set of RLC entities comprises n1+n2 RLC entities.

As a sub-embodiment of this embodiment, the first set of RLC entities comprises N1+1 RLC entities.

As a sub-embodiment of this embodiment, the first set of RLC entities comprises n1+n2+1 RLC entities.

As a sub-embodiment of this embodiment, RLC entities other than the N1 RLC entities in the first set of RLC entities are not mapped with the first bit string.

As an embodiment, the first RLC entity set includes n=n1+1 RLC entities, and the first RLC entity set includes n1+1-N2 primary link RLC entities and N2 secondary link RLC entities; the first RLC entity is a primary link RLC entity.

As an embodiment, the first RLC entity set includes n=n1+1 RLC entities, and the first RLC entity set includes N1-N2 main link RLC entities and n2+1 sub link RLC entities; the first RLC entity is a sidelink RLC entity.

As an embodiment, the first set of RLC entities comprises n=n1+1 RLC entities, N2 RLC entities of the n1+1 RLC entities being associated with logical channel identities on secondary links in the first list of logical channel identities; and N2 bits in the first bit string have a first mapping relation with the N2 RLC entities.

As a sub-embodiment of this embodiment, the sub-link RLC channel identities associated with the N2 RLC entities are used to determine the first mapping relationship.

As a sub-embodiment of this embodiment, the first mapping relationship is: the N2 RLC entities are respectively mapped with the N2 bits of the first bit string from high order to low order according to the value of the associated sidelink RLC channel identity according to the size.

As a sub-embodiment of this embodiment, the first mapping relationship is: and the N2 RLC entities are mapped with the high order of the N2 bits of the first bit string according to the high order of the N2 bits of the associated auxiliary link RLC channel identity, and the N2 RLC entities are mapped with the low order of the N2 bits of the first bit string according to the low order of the N2 bits of the associated auxiliary link RLC channel identity.

As a sub-embodiment of this embodiment, the first mapping relationship is: and the N2 RLC entities are mapped with the high order of the N2 bits of the first bit string according to the low order of the N2 bits of the associated auxiliary link RLC channel identity, and the N2 RLC entities are mapped with the low order of the N2 bits of the first bit string according to the high order of the N2 bits of the associated auxiliary link RLC channel identity.

As a sub-embodiment of this embodiment, the values of the sub-link RLC channel identities associated with the N2 RLC entities are different in size.

As a sub-embodiment of this embodiment, the sub-link RLC channel identities associated with the N2 RLC entities are different.

As a sub-embodiment of this embodiment, the sidelink RLC channels associated with the N2 RLC entities respectively correspond to logical channel identities in the first logical channel identity list.

As a sub-embodiment of this embodiment, the N2 bits of the first bit string are consecutive N2 bits.

As a sub-embodiment of this embodiment, the first mapping relationship is: the RLC entities (i) in the first RLC entity set and the bits b of the first bit string _i Mapping, RLC entities (i) in the first set of RLC entities being associated with a sidelink RLC channel (i); the RLC entity (j) in the first set of RLC entities and the bit b of the first bit string _j Mapping, RLC entities (j) in the first set of RLC entities being associated with a sidelink RLC channel (j); if i>j is b _i Relative to b _j Is higher; then b _j Relative to b _i Is lower; wherein i, j is [ N, n+N2-1 ]Wherein n+n2-1 is not greater than N1, N being a positive integer.

As a sub-embodiment of this embodiment, the first mapping relationship is: the RLC entities (i) in the first RLC entity set and the bits b of the first bit string _i Mapping, RLC entities (i) in the first set of RLC entities being associated with a sidelink RLC channel (i); the RLC entity (j) in the first set of RLC entities and the bit b of the first bit string _j Mapping, RLC entities (j) in the first set of RLC entities being associated with a sidelink RLC channel (j); if i<j is b _i Relative to b _j Is higher; then b _j Relative to b _i Is lower; wherein i, j is [ N, n+N2-1]Wherein n+n2-1 is not greater than N1, N being a positive integer.

As a sub-embodiment of this embodiment, the logical channel identity of the secondary link RLC channel (j) is the logical channel identity (j); the logical channel identity of the sidelink RLC channel (i) is the logical channel identity (i).

As a sub-embodiment of this embodiment, when the first bit string includes more than one byte, any bit of the xth byte is higher than any bit of the yh byte, x < y.

As a sub-embodiment of this embodiment, when the first bit string includes more than one byte, any bit of the xth byte is higher than any bit of the yh byte, x > y.

As an embodiment, the N1-N2 bits in the first bit string have a second mapping relationship with the N2 RLC entities in the first RLC entity set and RLC entities other than the first RLC entity.

As a sub-embodiment of this embodiment, the second mapping relationship is: the RLC entities (i) in the first RLC entity set and the bits b of the first bit string _i Mapping, RLC entities (i) in the first set of RLC entities being associated with a sidelink RLC channel (i); the RLC entity (j) in the first set of RLC entities and the bit b of the first bit string _j Mapping, RLC entities (j) in the first set of RLC entities being associated with a sidelink RLC channel (j); if i>j is b _i Relative to b _j Is higher; then b _j Relative to b _i Is lower; wherein i, j is [ N, n+N1-N2-1]Wherein n+n2-1 is not greater than N1, N being a positive integer.

As a sub-embodiment of this embodiment, the N1-N2 bits of the first bit string are consecutive N1-N2 bits.

As an embodiment, the first mapping relation relates to a sidelink RLC channel of an RLC entity of the first set of RLC entities; the second mapping relationship is related to a logical channel identity associated with an RLC entity in the first RLC entity set.

As an embodiment, any bit in the first bit string is mapped with only one RLC entity in the first set of RLC entities; any RLC entity of the N RLC entities of the first set of RLC entities maps with only one bit of the first string of bits.

As an embodiment, any logical channel identity in the first list of logical channel identities is associated with only one RLC entity in the first set of RLC entities; any RLC entity in the first set of RLC entities is associated with only one logical channel identity in the first list of logical channel identities.

As a sub-embodiment of this embodiment, the first mapping relationship is: the N2 auxiliary link RLC entities in the first RLC entity set are mapped with N2 bits of the first bit string according to the auxiliary link RLC channel identity value corresponding to the N2 auxiliary link RLC entities, wherein the auxiliary link RLC channel identity value is large and mapped with high-order bits in the N2 bits of the first bit string; and mapping the identity of the RLC channel of the secondary link with the lower bit of the N2 bits of the first bit string, wherein the lower bit has a small value.

As a sub-embodiment of this embodiment, the first mapping relationship is: the N2 auxiliary link RLC entities in the first RLC entity set are mapped with N2 bits of the first bit string according to the auxiliary link RLC channel identity value corresponding to the N2 auxiliary link RLC entities, wherein the auxiliary link RLC channel identity value is large and mapped with low bits in the N2 bits of the first bit string; and the identity of the secondary link RLC channel takes a small value and is mapped with the high-order bit in the N2 bits of the first bit string.

As a sub-embodiment of this embodiment, the second mapping relationship is: the N1 main link RLC entities in the first RLC entity set are mapped with N1 bits of the first bit string according to the magnitude of the logical channel identity values associated with the N1 auxiliary link RLC entities, wherein the logical channel identity values are mapped with low bits of the N1 bits of the first bit string; and mapping the logic channel identity with the high-order bit in the N2 bits of the first bit string, wherein the logic channel identity is small in value.

As an embodiment, the first node receives a fourth signaling, where the fourth signaling is a MAC CE, and the fourth signaling includes a second bit string, where the second bit string includes X bits, and the second bit string is mapped to X secondary link RLC entities in the first RLC entity set one-to-one; the second bit string is used to indicate activation or deactivation of PDCP duplication of the X RLC entities in the first set of RLC entities.

As a sub-embodiment of this embodiment, the code point of the logical channel identity corresponding to the fourth signaling is 251, and the index is 314.

As a sub-embodiment of this embodiment, the code point of the logical channel identity corresponding to the fourth signaling is not 251, and the index is not 314.

As a sub-embodiment of this embodiment, the value of the logical channel identity corresponding to the fourth signaling is not "Duplication RLC Activation/Deactivation".

As a sub-embodiment of this embodiment, the second bit string comprises 3 bits.

As a sub-embodiment of this embodiment, X is a positive integer.

As a sub-embodiment of this embodiment, X is a positive integer no greater than 3.

As a sub-embodiment of this embodiment, the one-to-one mapping relationship of the second bit string to the X RLC entities in the first set of RLC entities is independent of logical channel identities in the first list of logical channel identities.

As a sub-embodiment of this embodiment, a value of 0 for bit i in the second bit string indicates that PDCP duplication of RLC entities in the first set of RLC entities mapped with the bit i is deactivated; a value of 1 for bit i in the second bit string indicates that PDCP duplication of RLC entities in the first RLC entity set mapped with the bit i is activated.

As a sub-embodiment of this embodiment, the one-to-one mapping of the second bit string to the X secondary link RLC entities in the first RLC entity set is related to secondary link RLC channel identities corresponding to the X secondary link RLC entities in the first RLC entity set.

As a sub-embodiment of this embodiment, the sidelink RLC channel identities corresponding to the X sidelink RLC entities in the first RLC entity set are associated with X logical channel identities in the first logical channel identity list.

As a sub-embodiment of this embodiment, the one-to-one mapping between the second bit string and the X secondary link RLC entities in the first RLC entity set is related to a magnitude of a secondary link RLC channel identity corresponding to the X secondary link RLC entities in the first RLC entity set; any two RLC entities, RLC entity i and RLC entity j, of the X secondary link RLC entities in the first RLC entity set, if the value of the identity of the secondary link RLC channel corresponding to the RLC entity i is greater than the value of the identity of the secondary link RLC channel corresponding to the RLC entity j, the RLC entity i is mapped with a higher bit in the second bit string relative to the bit in the second bit string mapped by the RLC entity j.

As a sub-embodiment of this embodiment, the fourth signaling includes an identity of the first radio bearer.

As an embodiment, the first node receives a fourth signaling, where the fourth signaling is a MAC CE, and the fourth signaling includes a second bit string, where the second bit string includes X bits, and the second bit string is mapped to X secondary link RLC entities in the first RLC entity set one-to-one; the second bit string is used to indicate activation or deactivation of the X RLC entities in the first set of RLC entities.

As a sub-embodiment of this embodiment, the second bit string comprises 3 bits.

As a sub-embodiment of this embodiment, X is a positive integer.

As a sub-embodiment of this embodiment, a value of 0 for bit i in the second bit string indicates that the RLC entity in the first set of RLC entities mapped with the bit i is deactivated; a value of 1 for bit i in the second bit string indicates that an RLC entity in the first RLC entity set mapped with the bit i is activated.

As a sub-embodiment of this embodiment, the fourth signaling does not include an identity of the first radio bearer.

As a sub-embodiment of this embodiment, the X RLC entities in the first set of RLC entities are respectively associated with X candidate relays.

As a sub-embodiment of this embodiment, the first RLC entity belongs to the X RLC entities in the first set of RLC entities.

As a sub-embodiment of this embodiment, the first RLC entity does not belong to the X RLC entities in the first set of RLC entities.

As a sub-embodiment of this embodiment, activating RLC entities in the first set of RLC entities means activating communication or communication links of candidate relays associated with the RLC entities in the first set of RLC entities.

As an example, N in fig. 9 is equal to X.

As an embodiment, there is a one-to-one mapping relationship between the RLC entities of the first RLC entity set and the RLC channel identity set of the first RLC entity set.

As a sub-embodiment of this embodiment, the serving cell of the first node indicates a sidelink RLC channel identity of any sidelink RLC entity of the first set of RLC entities, the sidelink RLC channel identity of any sidelink RLC entity of the first set of RLC entities belonging to the first set of sidelink RLC channel identities.

As a sub-embodiment of this embodiment, the first set of RLC entities includes Y sidelink RLC entities; the first set of secondary link RLC channel identities includes Y secondary link RLC channel identities, where Y is a positive integer.

Example 10

Embodiment 10 illustrates a schematic diagram in which first signaling is used to indicate activation of PDCP duplication of any RLC entity in the first set of RLC entities associated with a logical channel identity on a secondary link in the first list of logical channel identities, as illustrated in fig. 10, in accordance with an embodiment of the present application.

As an embodiment, any RLC entity in the first set of RLC entities associated with a logical channel identity on a secondary link in the first list of logical channel identities has the meaning: any secondary link RLC entity of the first set of RLC entities.

As an embodiment, any secondary link RLC entity of the first set of RLC entities is associated with a logical channel identity on a secondary link in the first list of logical channel identities; the logical channel identities on any one secondary link in the first list of logical channel identities are associated with a secondary link RLC entity in the first set of RLC entities.

As an embodiment, the sentence first signaling is used to indicate that the meaning of activating PDCP duplication of any RLC entity of the first set of RLC entities associated with a logical channel identity on a secondary link in the first list of logical channel identities is: the first signaling is used to indicate PDCP duplication that activates any of the sidelink RLC entities in the first set of RLC entities.

As an embodiment, the sentence first signaling is used to indicate that the meaning of activating PDCP duplication of any RLC entity of the first set of RLC entities associated with a logical channel identity on a secondary link in the first list of logical channel identities is: the first signaling is used to indicate activation of PDCP duplication of any secondary link RLC entity other than the first RLC entity in the first set of RLC entities; the first RLC entity is a sidelink RLC entity.

Example 11

Embodiment 11 illustrates a schematic diagram in which the second signaling is used only to instruct activation or deactivation of PDCP duplication of RLC entities associated with the primary link in the first logical channel identity list, other than the first RLC entity in the first RLC entity set, as shown in fig. 11, according to one embodiment of the present application.

As an embodiment, the meaning that sentence second signaling is used only to indicate activation or deactivation of PDCP duplication of RLC entities associated with the primary link in the first logical channel identity list other than the first RLC entity in the first set of RLC entities includes: PDCP duplication of the sidelink RLC entity in the first RLC entity set is not activated or deactivated using the second signaling.

As an embodiment, the meaning that sentence second signaling is used only to indicate activation or deactivation of PDCP duplication of RLC entities associated with the primary link in the first logical channel identity list other than the first RLC entity in the first set of RLC entities includes: the second signaling is MAC layer signaling, and activation or deactivation of PDCP duplication of the sidelink RLC entity in the first RLC entity set is achieved through RRC signaling.

As an embodiment, the meaning that sentence second signaling is used only to indicate activation or deactivation of PDCP duplication of RLC entities associated with the primary link in the first logical channel identity list other than the first RLC entity in the first set of RLC entities includes: the first bit string included in the second signaling is mapped only with a primary RLC entity of the first set of RLC entities.

As an embodiment, the meaning that sentence second signaling is used only to indicate activation or deactivation of PDCP duplication of RLC entities associated with the primary link in the first logical channel identity list other than the first RLC entity in the first set of RLC entities includes: the PDCP duplication of the first RLC entity is not indicated by the second signaling.

As an embodiment, the meaning that sentence second signaling is used only to indicate activation or deactivation of PDCP duplication of RLC entities associated with the primary link in the first logical channel identity list other than the first RLC entity in the first set of RLC entities includes: the PDCP duplication of the first RLC entity is not indicated by MAC signaling; the second signaling is MAC signaling.

As an embodiment, the meaning that sentence second signaling is used only to indicate activation or deactivation of PDCP duplication of RLC entities associated with the primary link in the first logical channel identity list other than the first RLC entity in the first set of RLC entities includes: PDCP duplication of the first RLC entity is always active.

As an embodiment, the meaning that sentence second signaling is used only to indicate activation or deactivation of PDCP duplication of RLC entities associated with the primary link in the first logical channel identity list other than the first RLC entity in the first set of RLC entities includes: the PDCP duplication of the first radio bearer is deactivated when PDCP duplication of RLC entities other than the first RLC entity associated with the first PDCP entity are all deactivated.

As an embodiment, the meaning that sentence second signaling is used only to indicate activation or deactivation of PDCP duplication of RLC entities associated with the primary link in the first logical channel identity list other than the first RLC entity in the first set of RLC entities includes: activation or deactivation of PDCP duplication of the sidelink RLC entity in the first RLC entity set is indicated by signaling other than the second signaling.

As a sub-embodiment of this embodiment, the signaling other than the second signaling is RRC signaling.

As a sub-embodiment of this embodiment, the signaling other than the second signaling is a MAC CE, and the MAC CE is different from a logical channel identity corresponding to the second signaling.

Example 12

Embodiment 12 illustrates a schematic diagram in which the magnitudes of the values of the logical channel identities in the first logical channel identity list associated with the N2 RLC entities in the first RLC entity set and the RLC entities other than the first RLC entity are used to determine the second mapping relationship according to an embodiment of the present application, as shown in fig. 12.

As an embodiment, the size of the value of the logical channel identity in the first list of logical channel identities associated with neither the N2 RLC entities nor the first RLC entity in the first set of RLC entities is used to determine the second mapping relationship.

As an embodiment, the first RLC entity set includes n1+1 RLC entities, the n1+1 RLC entities include the N2 RLC entities, and N1-N2 RLC entities of the n1+1 RLC entities do not include RLC entities of the N2 RLC entities nor the first RLC entity; the magnitude of the value of the logical channel identity in the first logical channel identity list associated with the N1-N2 RLC entities is used to determine the second mapping relationship.

As a sub-embodiment of this embodiment, N1-N2 is greater than 1.

As a sub-embodiment of this embodiment, the N1-N2 RLC entities are all primary link RLC entities.

As a sub-embodiment of this embodiment, RLC entity i and RLC entity j are associated with logical channel identity i in the first logical channel identity list for any two RLC entities of the N1-N2 RLC entities; RLC entity j is associated with logical channel identity j in the first logical channel identity list; if the value of the logical channel identity i is greater than the value of the logical channel j, the bit mapped with the RLC entity i in the first bit string is a higher bit than the bit mapped with the RLC entity j in the first bit string.

As one example, N1-N2 is greater than 1.

As one example, N2 is greater than 1.

Example 13

Embodiment 13 illustrates a schematic diagram in which the sub-link RLC channel identities associated with N2 RLC entities are used to determine a first mapping relationship according to one embodiment of the present application, as illustrated in fig. 13.

As an embodiment, the N2 RLC entities belong to the first set of RLC entities.

As an embodiment, any RLC entity of the N2 RLC entities is associated with a sidelink RLC channel identity.

As an embodiment, the first signaling indicates a sidelink RLC channel identity of any RLC entity of the N2 RLC entities.

As one example, N2 is greater than 1.

As an embodiment, for any two RLC entities of the N2 RLC entities, RLC entity i and RLC entity j, RLC entity i is associated with a sidelink RLC channel i; RLC entity j is associated with a secondary link RLC channel j; if the value of the secondary link RLC channel i is greater than the value of the secondary link RLC channel j, the bit in the first bit string mapped with the RLC entity i is a higher bit than the bit in the first bit string mapped with the RLC entity j.

As an embodiment, for any two RLC entities of the N2 RLC entities, RLC entity i and RLC entity j, RLC entity i is associated with a sidelink RLC channel i; RLC entity j is associated with a secondary link RLC channel j; if the value of the secondary link RLC channel i is greater than the value of the secondary link RLC channel j, the bit in the second bit string mapped with the RLC entity i is a higher bit than the bit in the second bit string mapped with the RLC entity j.

As an embodiment, the primary link RLC entities in the first set of RLC entities are not associated with any secondary link RLC channels.

As an embodiment, a UE has a maximum of 512 sidelink RLC channels.

As an embodiment, a UE has a logical channel identity on at most 63 or 64 secondary links.

As an embodiment, a UE may have 63 or 64 logical channel identities for the main link.

As an embodiment, a UE may also have 255 or 256 extended logical channel identities of 1 byte for the main link.

As an embodiment, a UE may also have a 2-byte extended logical channel identity of 65535 or 65536 main links.

As an embodiment, each secondary link RLC channel has a secondary link RLC channel identity.

As an embodiment, each logical channel has a logical channel identity.

As an embodiment, the sidelink RLC channel of one UE is used for the sidelink when communicating with a different UE for the communication with all other UEs, and the logical channel communicating with a different UE may be the same or different and the sidelink RLC channel communicating with a different UE is different.

As a sub-embodiment of this embodiment, communication with all other UEs includes communication between UEs, and communication with the network through relay UEs.

As an example, when one UE communicates with other UEs in a sidelink, the logical channel identities associated with different sidelink RLC channels may be the same or different.

As an embodiment, the logical channel identity of the main link of one UE is for one cell group.

As an embodiment, the logical channel identities of one UE are different for the same cell group.

As an embodiment, the logical channel identity on the secondary link of one UE may be the same as or different from the logical channel identity on the primary link.

Example 14

Embodiment 14 illustrates a block diagram of a processing apparatus for use in a first node according to one embodiment of the application; as shown in fig. 14. In fig. 14, the processing means 1400 in the first node comprises a first receiver 1401 and a first transmitter 1402. In the case of the embodiment of the present application in which the sample is a solid,

a first receiver 1401 receiving first signaling, the first signaling being used to configure a first PDCP entity and a first RLC entity set; the first RLC entity set includes at least one secondary link RLC entity and a primary link RLC entity; any RLC entity in the first set of RLC entities is associated with the first PDCP entity; the primary path of the first PDCP entity is associated with a first RLC entity of the first set of RLC entities;

The first receiver 1401 receives a second signaling, where the second signaling includes a first bit string, and N1 bits of the first bit string have a one-to-one mapping relationship with N1 RLC entities other than the first RLC entity in the first RLC entity set; the first bit string is used to indicate activation or deactivation of PDCP duplication of RLC entities in the first set of RLC entities;

a first transmitter 1402 that transmits a first PDCP data PDU of the first PDCP entity; the act of transmitting a first PDCP data PDU of the first PDCP entity includes: duplicating the first PDCP data PDU of the first PDCP entity and submitting duplicated copies to PDCP duplication activated RLC entities in the first RLC entity set, respectively;

As an embodiment, the secondary link RLC channel identities associated with the N2 RLC entities are used to determine the first mapping relationship.

As an embodiment, the first receiver 1401 receives third signaling, which is used to instruct to activate or deactivate PDCP duplicates of all RLC entities in the first set of RLC entities associated with logical channel identities on a secondary link in the first list of logical channel identities;

As an embodiment, the first receiver 1401 receives third signaling, which is used to instruct activation or deactivation of PDCP duplication of the first PDCP entity;

The first transmitter 1402 transmitting a second PDCP data PDU of the first PDCP entity, the act of transmitting the second PDCP data PDU of the first PDCP entity includes: submitting the second PDCP data PDU of the first PDCP entity to either the first RLC entity or a third RLC entity;

As an embodiment, the radio bearer corresponding to the first PDCP entity is an SRB, and the peer RLC entity of the first RLC entity is in a node other than the MCG.

As an embodiment, the first node is a User Equipment (UE).

As an embodiment, the first node is a terminal supporting a large delay difference.

As an embodiment, the first node is a terminal supporting NTN.

As an embodiment, the first node is an aircraft or a ship.

As an embodiment, the first node is a mobile phone or a vehicle terminal.

As an embodiment, the first node is a relay UE and/or a U2N remote UE.

As an embodiment, the first node is an internet of things terminal or an industrial internet of things terminal.

As an embodiment, the first node is a device supporting low latency and high reliability transmissions.

As an embodiment, the first node is a sidelink communication node.

As an example, the first receiver 1401 includes at least one of the antenna 452, the receiver 454, the receive processor 456, the multi-antenna receive processor 458, the controller/processor 459, the memory 460, or the data source 467 in example 4.

As one example, the first transmitter 1402 includes at least one of the antenna 452, the transmitter 454, the transmit processor 468, the multi-antenna transmit processor 457, the controller/processor 459, the memory 460, or the data source 467 of embodiment 4.

Example 15

Embodiment 15 illustrates a block diagram of a processing apparatus for use in a second node according to one embodiment of the application; as shown in fig. 15. In fig. 15, the processing means 1500 in the second node comprises a second receiver 1502 and a second transmitter 1501. In the case of the embodiment of example 15,

a second transmitter 1501 transmitting first signaling, the first signaling being used to configure a first PDCP entity and a first RLC entity set; the first RLC entity set includes at least one secondary link RLC entity and a primary link RLC entity; any RLC entity in the first set of RLC entities is associated with the first PDCP entity; the primary path of the first PDCP entity is associated with a first RLC entity of the first set of RLC entities;

the second transmitter 1501 sends a second signaling, where the second signaling includes a first bit string, and N1 bits of the first bit string have a one-to-one mapping relationship with N1 RLC entities other than the first RLC entity in the first RLC entity set; the first bit string is used to indicate activation or deactivation of PDCP duplication of RLC entities in the first set of RLC entities;

a second receiver 1502 for receiving a first PDCP data PDU of the first PDCP entity; the act of receiving a first PDCP data PDU of the first PDCP entity includes: receiving a copy of the first PDCP data PDU of the first PDCP entity from a peer RLC entity of at least one of the activated RLC entities in the first set of RLC entities;

As an embodiment, the second transmitter 1501 sends third signaling for indicating to activate or deactivate PDCP duplication of RLC entities in the first set of RLC entities associated with logical channel identities on secondary links in the first list of logical channel identities;

As an embodiment, the second transmitter 1501 transmits third signaling for indicating to activate or deactivate PDCP copying of the first PDCP entity;

the second receiver 1502 receives a second PDCP data PDU of the first PDCP entity, and the act of receiving the second PDCP data PDU of the first PDCP entity includes: receiving the second PDCP data PDU from one of the first RLC entity or a peer entity in a third RLC entity;

As an embodiment, the second node is a satellite.

As an embodiment, the second node is a U2N Relay UE (user equipment).

As one embodiment, the second node is an IoT node.

As an embodiment, the second node is a wearable node.

As an embodiment, the second node is a base station.

As an embodiment, the second node is a relay.

As an embodiment, the second node is an access point.

As an embodiment, the second node is a multicast-enabled node.

As an example, the second transmitter 1501 includes at least one of the antenna 420, the transmitter 418, the transmission processor 416, the multi-antenna transmission processor 471, the controller/processor 475, and the memory 476 in example 4.

As an example, the second receiver 1502 includes at least one of the antenna 420, the receiver 418, the receive processor 470, the multi-antenna receive processor 472, the controller/processor 475, and the memory 476 of example 4.

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 present application is not limited to any specific combination of software and hardware. The user equipment, the terminal and the UE in the present application include, but are not limited to, unmanned aerial vehicles, communication modules on unmanned aerial vehicles, remote control airplanes, aircrafts, mini-planes, mobile phones, tablet computers, notebooks, vehicle-mounted communication devices, wireless sensors, network cards, internet of things terminals, RFID terminals, NB-IoT terminals, MTC (Machine Type Communication ) terminals, eMTC (enhanced MTC) terminals, data cards, network cards, vehicle-mounted communication devices, low-cost mobile phones, low-cost tablet computers, satellite communication devices, ship communication devices, NTN user devices and other wireless communication devices. The base station or system equipment in the present application includes, but is not limited to, wireless communication equipment such as macro cell base stations, micro cell base stations, home base stations, relay base stations, gNB (NR node B) NR node B, TRP (Transmitter Receiver Point, transmitting and receiving node), NTN base stations, satellite equipment, flight platform equipment, and the like.

The present invention may be embodied in other specific forms without departing from its spirit or essential characteristics. 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, wherein the first node,

the first signaling is used to indicate activation of PDCP duplication of any RLC entity of the first set of RLC entities associated with a logical channel identity on a secondary link in the first list of logical channel identities; the second signaling is only used to instruct activation or deactivation of PDCP duplication of RLC entities associated with the primary link in the first logical channel identity list other than the first RLC entity in the first set of RLC entities; mapping the lowest bit in the first bit string with a second RLC entity, wherein the second RLC entity belongs to the first RLC entity set; the second RLC entity is associated with a first logical channel identity; the logical channel identity with the smallest value in the logical channel identities of the main link in the first logical channel identity list associated with RLC entities other than the first RLC entity in the first RLC entity set is the first logical channel identity;

3. The first node of claim 1, wherein the first node,

the first set of RLC entities includes N1+1 RLC entities, N2 RLC entities of the N1+1 RLC entities being associated with logical channel identities on a secondary link in the first list of logical channel identities; the N2 bits in the first bit string have a first mapping relation with the N2 RLC entities; N1-N2 bits in the first bit string have a second mapping relation with the N2 RLC entities in the first RLC entity set and the RLC entities other than the first RLC entity; the value of the logical channel identity in the first logical channel identity list associated with the N2 RLC entities in the first RLC entity set and RLC entities other than the first RLC entity is used to determine the second mapping relationship;

4. The first node of claim 3, wherein the first node,

The sub-link RLC channel identities associated with the N2 RLC entities are used to determine the first mapping relationship.

5. The first node according to claim 3 or 4, characterized in that,

the N2 bits of the first bit string are consecutive; the N1-N2 bits of the first bit string are consecutive;

the N2 bits of the first bit string are higher order bits relative to the N1-N2 bits of the first bit string;

the N2 bits of the first bit string are lower order bits relative to the N1-N2 bits of the first bit string.

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

the first receiver receiving third signaling, the third signaling being used to instruct activation or deactivation of PDCP duplicates of all RLC entities in the first set of RLC entities associated with logical channel identities on a secondary link in the first list of logical channel identities;

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

The first receiver receiving third signaling, the third signaling being used to instruct activation or deactivation of PDCP duplication of the first PDCP entity;

the first transmitter transmitting a second PDCP data PDU of the first PDCP entity, the act of transmitting the second PDCP data PDU of the first PDCP entity comprising: submitting the second PDCP data PDU of the first PDCP entity to either the first RLC entity or a third RLC entity;

8. The first node according to any of the claims 1 to 7, characterized in that,

The radio bearer corresponding to the first PDCP entity is an SRB, and the opposite RLC entity of the first RLC entity is in a node other than the MCG.

9. A second node for wireless communication, comprising:

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

11. A method in a second node for wireless communication, comprising: