WO2023186162A1

WO2023186162A1 - Method and device used for wireless communication

Info

Publication number: WO2023186162A1
Application number: PCT/CN2023/085838
Authority: WO
Inventors: 陈宇; 张晓博
Original assignee: 上海朗帛通信技术有限公司
Priority date: 2022-04-01
Filing date: 2023-04-03
Publication date: 2023-10-05
Also published as: CN116938405A

Abstract

Disclosed in the present application are a method and device used for wireless communication. The method comprises: receiving first signaling, wherein the first signaling is used for configuring a first PDCP entity and a first RLC entity set, the first RLC entity set comprises at least one secondary link RLC entity and a primary link RLC entity, any RLC entity in the first RLC entity set is associated with the first PDCP entity, and a main path of the first PDCP entity is associated with a first RLC entity in the first RLC entity set; receiving second signaling, wherein the second signaling comprises a first bit string, and N1 bits of the first bit string are in a one-to-one mapping relationship with N1 RLC entities in the first RLC entity set other than the first RLC entity, and the first bit string is used for instructing to perform activation or deactivation of PDCP replication of the RLC entities in the first RLC entity set; and sending a first PDCP data PDU of the first PDCP entity. In the present application, by means of the first signaling, an improvement in the reliability of communication is facilitated, and communication interruption is avoided.

Description

A method and device for wireless communications

Technical field

The present application relates to transmission methods and devices in wireless communication systems, and in particular to methods and devices for network optimization in communications, improving business service quality, and relay communications.

Background technique

The application scenarios of future wireless communication systems will become more and more diversified, and different application scenarios impose different performance requirements on the system. In order to meet the different performance requirements of various application scenarios, it was decided at the 3GPP (3rd Generation Partner Project) RAN (Radio Access Network) #72 plenary meeting that new air interface technology (NR, New Radio) (or Fifth Generation, 5G) conducted research, passed the WI (Work Item, work item) of NR at the 3GPP RAN#75 plenary meeting, and began to standardize NR.

In communications, whether it is LTE (Long Term Evolution, Long Term Evolution) or 5G NR, it will involve reliable and accurate reception of information, optimized energy efficiency ratio, determination of information validity, flexible resource allocation, and scalable system structure. Efficient non-access layer information processing, low service interruption and dropout rates, and low power consumption support are important for normal communication between base stations and user equipment, reasonable resource scheduling, and system load balancing. Meaning, it can be said that it is the cornerstone of high throughput, meeting the communication needs of various businesses, improving spectrum utilization, and improving service quality, whether it is eMBB (ehanced Mobile BroadBand, enhanced mobile broadband), URLLC (Ultra Reliable Low Latency Communication, Ultra-high reliability and low-latency communication) or eMTC (enhanced Machine Type Communication, enhanced machine type communication) are indispensable. At the same time, in IIoT (Industrial Internet of Things, the Internet of Things in the industrial field, in V2X (Vehicular to X, vehicle communication), in communication between devices (Device to Device), in communication in unlicensed spectrum, in User communication quality monitoring, in network planning and optimization, in NTN (Non Territerial Network, non-terrestrial network communication), in TN (Territerial Network, terrestrial network communication), in dual connectivity (Dual connectivity) systems, in wireless resource management As well as multi-antenna codebook selection, there are extensive needs in signaling design, neighbor cell management, service management, and beamforming. Information transmission methods are divided into broadcast and unicast. Both transmission methods are 5G. Systems are essential because they are very helpful in meeting the above requirements. The UE can be connected to the network either directly or through a relay.

As the scenarios and complexity of the system continue to increase, higher requirements are put forward to reduce interruption rates, reduce delays, enhance reliability, enhance system stability, business flexibility, and power saving. At the same time, When designing the system, it is also necessary to consider the compatibility between different versions of different systems.

The 3GPP standardization organization has done relevant standardization work for 5G and formed a series of standards. For standard content, please refer 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

Contents of the invention

In various communication scenarios, the use of relays will be involved. For example, when a UE (User Equipment) is at the edge of a cell and the coverage is poor, it can access the network through a relay. The relay node can be another UE. Relay mainly includes layer 3 relay and layer 2 relay (L2U2N relay), which provide network access services to remote nodes (U2N remote UE) through relay nodes. The layer 3 relay is transparent to the access network. , that is, the remote UE only establishes a connection with the core network, and the access network cannot identify whether the data comes from the remote node or the relay node; while in layer 2 relay, the remote node (U2N remote UE) and the access network (RAN ) has an RRC connection, the access network can manage remote nodes, and wireless bearers can be established between the access network and remote nodes. The relay can be another UE. In a system that supports layer 2 relay, the UE can communicate with the network through the L2 relay UE (L2 U2N relay UE), even if it uses an indirect path or not. Relays communicate directly with the network, using a direct path. In some scenarios, a UE can use both direct paths and indirect paths to obtain better reliability and higher throughput. Direct paths and indirect paths are different in terms of radio resource management and network optimization. One of the direct path and the indirect path does not use a relay, and the other uses a relay. The relay node may provide services for multiple nodes, so the throughput rate, QoS, and functions of the two or more paths may not be the same. , these are different from traditional network structures, Solutions must fit into this new network structure. When direct paths and indirect paths are used at the same time, especially when the direct path includes multiple carriers, one PDCP entity will be associated with multiple RLC entities, where multiple RLC entities correspond to multiple paths. It is best for the network to Dynamically activate and deactivate the PDCP replication function of some RLC entities based on the transmission quality, load condition and occupied resources of the path. Because the configuration methods of direct path and non-direct path RLC entities are very different, the existing technology cannot support the activation and deactivation of the PDCP replication function of RLC entities on the non-direct path. At the same time, the introduction of non-direct paths will also cause the existing Technical indication: There is a problem with the PDCP replication function of the RLC entity in the direct path. These problems are exactly what this application aims to solve. Of course, the solution proposed by this application can also solve other problems in the communication system, and is not limited to the above problems, such as when there are multiple indirect paths and/or when there are no direct paths and only multiple indirect paths exist, such as That is, there are situations where both MCG and SCG have indirect paths.

To solve the above problems, this application provides a solution.

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

This application discloses a method used in a first node of wireless communication, including:

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

Receive second signaling, the second signaling including a first bit string, N1 bits of the first bit string and N1 RLC entities other than the first RLC entity in the first RLC entity set There is a one-to-one mapping relationship; the first bit string is used to indicate activation or deactivation of PDCP replication of the RLC entities in the first RLC entity set;

Send the first PDCP data PDU of the first PDCP entity; the act of sending the first PDCP data PDU of the first PDCP entity includes: copying the first PDCP data PDU of the first PDCP entity and copying the first PDCP data PDU of the first PDCP entity. The copies are respectively submitted to the RLC entities whose PDCP replication is activated in the first RLC entity set;

Wherein, the N1 is a positive integer, any RLC entity in the first RLC entity set is associated with a logical channel identity in the first logical channel identity list; the first bit string is associated with the first RLC entity The one-to-one mapping relationship existing among N1 RLC entities other than the first RLC entity in the set is related to the logical channel identity on the main link in the first logical channel identity list, and the first The one-to-one mapping relationship between the bit string and the N1 RLC entities other than the first RLC entity in the first RLC entity set and the logical channel on the secondary link in the first logical channel identity list Identity is irrelevant.

As an embodiment, the problems to be solved by this application include: in the scenario where L2 relay is used, especially when the direct path and the indirect path are used at the same time, how to support the activation and deactivation of the PDCP replication function to ensure the normal communication carried out, taking into account the requirements and characteristics of relay communications.

As an embodiment, the benefits of the above method include: when supporting the use of L2 relays, especially when supporting simultaneous use of multiple paths to communicate with the network, the PDCP replication function of the RLC entity can be dynamically activated and deactivated, reducing delay and reducing It eliminates communication interruptions, improves service quality, increases coverage, reduces resource consumption, improves resource utilization, and provides better support for mobility and business continuity.

Specifically, according to an aspect of the present application, the first signaling is used to indicate activation of a logical channel on a secondary link in any one of the first RLC entity set and the first logical channel identity list. PDCP copy of the RLC entity associated with the identity; the second signaling is only used to indicate activation or deactivation of the first logical channel identity list other than the first RLC entity in the first RLC entity set. PDCP replication of the RLC entity associated with the main link; the lowest bit in the first bit string is mapped to the second RLC entity, and the second RLC entity belongs to the first RLC entity set; the The second RLC entity is associated with the first logical channel identity; the RLC entity other than the first RLC entity in the first RLC entity set is associated with the main link in the first logical channel identity list. The logical channel identity with the smallest value among the logical channel identities is the first logical channel identity;

Wherein, any RLC entity in the first RLC entity set is used for communication with the MCG.

Specifically, according to one aspect of the present application, the first RLC entity set includes N1+1 RLC entities, and N2 RLC entities among the N1+1 RLC entities are identical to those in the first logical channel identity list. The logical channel identity on the secondary link is associated; the N2 bits in the first bit string have a first mapping relationship with the N2 RLC entities; the N1-N2 bits in the first bit string are related to the N2 RLC entities. There is a second mapping relationship between the N2 RLC entities in the first RLC entity set and RLC entities other than the first RLC entity; the N2 RLC entities in the first RLC entity set and the third RLC entity The value size of the logical channel identity in the first logical channel identity list associated with an RLC entity other than an RLC entity is used to determine the second mapping relationship;

Wherein, the N2 bits in the first bit string are different from the N1-N2 bits, the N2 is a positive integer not greater than the N1, the first mapping relationship and the second mapping Relationships are all mapped one-to-one.

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

Specifically, according to one aspect of the present application, the N2 bits of the first bit string are continuous; the N1-N2 bits of the first bit string are continuous.

Specifically, according to one aspect of the present application, third signaling is received, and the third signaling is used to indicate activation or deactivation of logical channel identities on all secondary links in the first logical channel identity list. PDCP replication of the associated RLC entities in the first RLC entity set;

Wherein, the logical channel identity in the first logical channel identity list associated with the first RLC entity is a logical channel identity on the main link.

Specifically, according to one aspect of the present application, third signaling is received, and the third signaling is used to indicate activation or deactivation of PDCP replication of the first PDCP entity;

Send the second PDCP data PDU of the first PDCP entity. The act of sending the second PDCP data PDU of the first PDCP entity includes: submitting the second PDCP data PDU of the first PDCP entity to the Any one of the first RLC entity or the third RLC entity;

Wherein, the split slave path of the first PDCP entity is associated with the third RLC entity in the first RLC entity set; both the first RLC entity and the third RLC entity are used to communicate with MCG Communication; one of the first RLC entity and the third RLC entity is associated with a logical channel identity on the main link in the first logical channel identity list, and the other one is associated with the first logical channel identity Logical channel identities on the secondary links in the list are associated; 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.

Specifically, according to one 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 one aspect of this application, the first node is an Internet of Things terminal.

Specifically, according to one aspect of this application, the first node is a relay.

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

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

Specifically, according to one aspect of this application, the first node is an aircraft.

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

Specifically, according to one aspect of the present application, the first node is a communication terminal that supports multi-SIM card communication.

This application discloses a method used in a second node for wireless communication, including:

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

Send second signaling, the second signaling including a first bit string, N1 bits of the first bit string and N1 RLC entities other than the first RLC entity in the first RLC entity set There is a one-to-one mapping relationship; the first bit string is used to indicate activation or deactivation of PDCP replication of the RLC entities in the first RLC entity set;

Receive the first PDCP data PDU of the first PDCP entity; the act of receiving the first PDCP data PDU of the first PDCP entity includes: PDCP copying the activated RLC entity from the first RLC entity set. The peer RLC entity of at least one RLC entity receives a copy of the first PDCP data PDU of the first PDCP entity;

Specifically, according to an aspect of the present application, the first signaling is used to indicate the activation of any one of the first RLC entity set and the PDCP copy of the RLC entity associated with the logical channel identity on the secondary link in the first logical channel identity list; the second signaling is only used to indicate activation or deactivation of all RLC entities in the first RLC entity set PDCP replication of RLC entities other than the first RLC entity associated with the main link in the first logical channel identity list; the lowest bit in the first bit string is mapped to the second RLC entity, so The second RLC entity belongs to the first RLC entity set; the second RLC entity is associated with a first logical channel identity; the RLC entity other than the first RLC entity in the first RLC entity set is associated with The logical channel identity with the smallest value among the logical channel identities on the main link in the first logical channel identity list is the first logical channel identity;

Specifically, according to one aspect of the present application, third signaling is sent, and the third signaling is used to indicate activation or deactivation of logical channel identities on all secondary links in the first logical channel identity list. PDCP replication of the associated RLC entities in the first RLC entity set;

Specifically, according to one aspect of the present application, third signaling is sent, and the third signaling is used to indicate activation or deactivation of PDCP replication of the first PDCP entity;

Receive the second PDCP data PDU of the first PDCP entity. The act of receiving the second PDCP data PDU of the first PDCP entity includes: receiving the second PDCP data PDU of the first RLC entity or the peer entity of the third RLC entity. Receive the second PDCP data PDU on one;

Specifically, according to one aspect of this application, the second node is a base station.

Specifically, according to one aspect of this application, the second node is an access point.

Specifically, according to one aspect of this application, the second node is a relay.

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

Specifically, according to one aspect of this application, the second node is an aircraft.

Specifically, according to one aspect of the present application, the second node is a satellite.

This application discloses a first node used for wireless communication, including:

The first receiver receives first signaling, which is used to configure a first PDCP entity and a first set of RLC entities; the first set of RLC entities includes at least one secondary link RLC entity and a primary Link RLC entity; any RLC entity in the first RLC entity set is associated with the first PDCP entity; the main path of the first PDCP entity is associated with the first RLC entity in the first RLC entity set Associated;

The first receiver receives second signaling, the second signaling includes a first bit string, and the N1 bits of the first bit string are consistent with the first RLC in the first RLC entity set. There is a one-to-one mapping relationship for N1 RLC entities other than the entity; the first bit string is used to indicate activation or deactivation of PDCP replication of the RLC entity in the first RLC entity set;

The first transmitter sends the first PDCP data PDU of the first PDCP entity; the action of sending the first PDCP data PDU of the first PDCP entity includes: copying the first PDCP data of the first PDCP entity. Data PDU and submit the copied copies to the RLC entities whose PDCP replication is activated in the first RLC entity set;

This application discloses a second node used for wireless communication, including:

The second transmitter sends first signaling. The first signaling is used to configure the first PDCP entity and the first RLC entity set. The first RLC entity set includes at least one secondary link RLC entity and a primary link RLC entity. Link RLC entity; any RLC entity in the first RLC entity set is associated with the first PDCP entity; the main path of the first PDCP entity is associated with the first RLC entity in the first RLC entity set Associated;

The second transmitter sends second signaling, the second signaling includes a first bit string, and the N1 bits of the first bit string are consistent with the first RLC in the first RLC entity set. There is a one-to-one mapping relationship for N1 RLC entities other than the entity; the first bit string is used to indicate activation or deactivation of PDCP replication of the RLC entity in the first RLC entity set;

The second receiver receives the first PDCP data PDU of the first PDCP entity; the action of receiving the first PDCP data PDU of the first PDCP entity includes: PDCP replication is activated from the first RLC entity set. The peer RLC entity of at least one of the RLC entities receives a copy of the first PDCP data PDU of the first PDCP entity;

As an example, compared with traditional solutions, this application has the following advantages:

Supports relaying, especially the activation and deactivation of PDCP replication of RLC when using L2 U2N (UE to Network) to relay UE.

Supports activation and deactivation of PDCP replication when direct paths and indirect paths are used at the same time, including one direct path and one indirect path, multiple direct paths and one indirect path, one direct path and multiple indirect paths, and more direct paths and multiple indirect paths.

The network is supported to configure and process the wireless links connecting the cell groups and the wireless links connecting the relays differently, that is, they are functionally differentiated.

Supports wireless bearers, especially SRB1 using split bearer architecture on direct paths and indirect paths.

Supports signaling bearers using indirect paths as primary paths.

Supports split slave paths and primary paths being associated with MCG at the same time.

Description of drawings

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

Figure 1 shows a flow chart of receiving the first signaling, receiving the second signaling, and sending the first PDCP data PDU of the first PDCP entity according to an embodiment of the present application;

Figure 2 shows a schematic diagram of a network architecture according to an embodiment of the present application;

Figure 3 shows a schematic diagram of an embodiment of a wireless protocol architecture of a user plane and a control plane according to an embodiment of the present application;

Figure 4 shows a schematic diagram of a first communication device and a second communication device according to an embodiment of the present application;

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

Figure 6 shows a schematic diagram of a protocol stack for relay communication according to an embodiment of the present application;

Figure 7 shows a schematic diagram of a radio bearer according to an embodiment of the present application;

Figure 8 shows a schematic diagram of a topology according to an embodiment of the present application;

Figure 9 shows a schematic diagram of the mapping relationship between the first bit string and the first RLC entity set according to an embodiment of the present application;

Figure 10 shows that first signaling is used to indicate activation of any one of the first set of RLC entities associated with a logical channel identity on the secondary link in the first logical channel identity list according to an embodiment of the present application. Schematic diagram of PDCP replication of RLC entities;

Figure 11 shows that the second signaling according to an embodiment of the present application is only used to indicate activation or deactivation of other than the first RLC entity in the first RLC entity set and the first logical channel identity list and the main chain. Schematic diagram of PDCP replication of RLC entities associated with roads;

Figure 12 shows the values of logical channel identities in the first logical channel identity list associated with N2 RLC entities in the first RLC entity set and RLC entities other than the first RLC entity according to an embodiment of the present application. The size of is used to determine the schematic diagram of the second mapping relationship;

Figure 13 shows a schematic diagram in which the secondary link RLC channel identities associated with N2 RLC entities are used to determine the first mapping relationship according to an embodiment of the present application;

Figure 14 illustrates a schematic diagram of a processing device used in a first node according to an embodiment of the present application;

Figure 15 illustrates a schematic diagram of a processing device used in a second node according to an embodiment of the present application.

Implementation

The technical solution of the present application will be further described in detail below with reference to the accompanying drawings. It should be noted that, as long as there is no conflict, the embodiments and features in the embodiments of the present application can be combined with each other arbitrarily.

Example 1

Embodiment 1 illustrates a flow chart of receiving the first signaling, receiving the second signaling, and sending the first PDCP data PDU of the first PDCP entity according to an embodiment of the present application, as shown in FIG. 1 . In Figure 1, each box represents a step. It should be particularly emphasized that the order of the boxes in the figure does not represent the temporal relationship between the steps represented.

In Embodiment 1, the first node in this application receives the first signaling in step 101, receives the second signaling in step 102, and sends the first PDCP data PDU of the first PDCP entity in step 103;

Wherein, the first signaling is used to configure a first PDCP entity and a first set of RLC entities; the first set of RLC entities includes at least one secondary link RLC entity and one primary link RLC entity; the first Any RLC entity in the RLC entity set is associated with the first PDCP entity; the main path of the first PDCP entity is associated with the first RLC entity in the first RLC entity set; the second signaling Including a first bit string, 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 replication of an RLC entity in the first RLC entity set; the behavior of sending a first PDCP data PDU of the first PDCP entity includes: replicating all of the first PDCP entity The first PDCP data PDU and the copied copies are respectively submitted to the RLC entities whose PDCP replication is activated in the first RLC entity set; the N1 is a positive integer, and any RLC entity in the first RLC entity set is A logical channel identity in the first logical channel identity list is associated; the first bit string is associated with each of the N1 RLC entities other than the first RLC entity in the first RLC entity set. The mapping relationship is related to the logical channel identity on the main link in the first logical channel identity list, and the first bit string is related to N1 other than the first RLC entity in the first RLC entity set. The one-to-one mapping relationship existing in the RLC entity has nothing to do with the logical channel identity on the secondary link in the first logical channel identity list.

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

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

As an embodiment, the direct path refers to a transmission path from the UE to the network. Transmission through the direct path means that data is transmitted between the remote UE and the network between the UE and the network (U2N). Sends between do not go through relays.

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

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

As a sub-embodiment of this embodiment, the data includes bit strings or bit blocks.

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

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

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

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

As an embodiment, U2N relay UE refers to a UE that provides the function of supporting the connection of U2N remote UE to the network.

As an embodiment, U2N remote UE refers to a UE that needs to pass through a U2N relay UE to communicate with the network.

As an embodiment, U2N remote UE refers to a UE that supports relay services and communicates with the network.

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

As an embodiment, when sending and receiving unicast services with the network, both the U2N relay and the U2N remote node are in the RRC connection state.

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

As an example, not transmitting via a direct path is equivalent to transmitting via an indirect path.

As one example, transmission not via a direct path includes transmission via a relay.

As one example, transmitting via a direct path is or includes transmitting without a relay.

As one example, transmitting via a direct path is or includes forwarding without a relay.

As an embodiment, a U2N relay UE is a UE that provides functionality (functionality) for U2N remote UE to support connectivity to the 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 an embodiment, the U2N remote UE is a UE that communicates with the network through a U2N relay UE.

As an embodiment, the direct mode is a mode that uses the direct path.

As an embodiment, the direct connection mode is a mode in which the U2N remote UE uses the direct path to communicate with the network.

As an embodiment, the direct connection 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 an embodiment, the indirect mode is a mode using the indirect path.

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

As an embodiment, the direct connection mode is a mode in which the U2N remote UE uses the indirect path to communicate with the network.

As an embodiment, the direct connection 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 where the UE is camped. Performing cell search includes: UE searches for a suitable (suitable) cell of the selected PLMN (Public Land Mobile Network) or SNPN (Stand-alone Non-Public Network, independent non-public network), and selects the A suitable cell provides available services and monitors the control channel of the suitable cell. This process is defined as camping on the cell; that is, a camped cell, relative to the UE, is this The serving cell of the UE. Camping on a cell in RRC idle state or RRC inactive state has the following benefits: it allows the UE to receive system messages from the PLMN or SNPN; after registration, if the UE wants to establish an RRC connection or continue a suspended RRC connection, The UE can be implemented by performing initial access on the control channel of the resident cell; the network can page the UE; allowing the UE to receive ETWS (Earthquake and Tsunami Warning System) and CMAS (Commercial Mobile Alert System), Commercial mobile alarm systems) notifications.

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

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

As an example, the frequency at which SCell (Secondary Cell) works is the secondary frequency.

As one example, the individual contents of an information element are called fields.

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 wireless access node that provides control plane connection to the core network is the master node. The master node may be the master eNB, the master ng-eNB, or the master gNB.

As an embodiment, MCG refers to, in the MR-DC, a group of serving cells associated with the master node, including SpCell, and may also, optionally, include one or more SCells.

As an example, the PCell is MCG's SpCell.

As an example, the PSCell is the SpCell of SCG.

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

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

As an example, the access layer function that enables V2X (Vehicle-to-Everything) communication defined in 3GPP standard TS 23.285 is V2X sidelink communication (V2X sidelink communication), where the V2X sidelink communication occurs Between adjacent UEs, and using E-UTRA technology but not traversing network nodes.

As an embodiment, at least the access layer function that enables V2X (Vehicle-to-Everything) communication defined in 3GPP standard TS 23.287 is NR sidelink communication, where the NR sidelink communication Occurs between two or more adjacent UEs and uses NR technology but does not traverse (traversing) network nodes.

As an embodiment, a sidelink (sidelink, SL) is a direct communication link between UE-to-UE using a side link resource allocation mode, a physical layer signal or channel, and a physical layer process.

As an embodiment, in this application, the signaling name or domain name or message name starting with "SL-" is for the secondary link.

As an example, not or not or not in coverage equals out of coverage.

As an example, within coverage equals within coverage.

As an example, out-of-coverage equals out-of-coverage.

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

As an embodiment, the PDCP entities corresponding to the radio bearers that terminate between the UE and the network are located in the UE and the network respectively.

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

As an embodiment, the direct path transmission refers to that data carried by at least SRB (Signaling radio bearer, signaling radio bearer) between the UE and the network does not pass through the relay or forwarding of other nodes.

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

As an embodiment, the direct path transmission refers to that the RLC entities associated with at least SRB (Signaling radio bearer) between the UE and the network terminate at the UE and the network respectively.

As an embodiment, the direct path transmission refers to the existence of a directly connected communication link between the UE and the network.

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

As an embodiment, the direct path transmission refers to that the MAC layer of the 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 the physical layer of the Uu interface between the UE and the network.

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

As an embodiment, the indirect path is an indirect path or communication link or channel or bearer used when transmitting through 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, signaling radio bearer) between the UE and the network through other nodes.

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

As an embodiment, the non-direct path transmission refers to that the RLC entities associated with at least SRB (Signaling radio bearer) between the UE and the network terminate respectively between the UE and other nodes, other nodes and network.

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

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

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

As an embodiment, the non-direct path transmission refers to that there is no MAC layer of the Uu interface between the UE and the network.

As an embodiment, the non-direct path transmission refers to a physical layer in which there is no Uu interface between the UE and the network.

As an embodiment, the non-direct path transmission means that there is neither a logical channel nor a transmission channel between the UE and the network.

As an embodiment, the network includes a radio access network (RAN) and/or serving cells and/or base stations.

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

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

As an example, when using direct path transmission, the UE can send physical layer signaling to the network; when using indirect path transmission, the UE cannot send or directly send physical layer signaling to the network;

As an example, when using direct path transmission, the UE can send MAC CE to the network; when using indirect path transmission, the UE cannot send MAC CE to the network or directly;

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

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

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

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

As an embodiment, when direct path transmission is used, 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 and the RLC entity of the PC5 interface There is a mapping relationship.

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

As an embodiment, the meaning of converting from a direct path to an indirect path is to start using the indirect path and stop using the direct path at the same time.

As an embodiment, switching from a direct path to an indirect path means: starting to use the indirect path for transmission, and at the same time stopping using the direct path for transmission.

As an embodiment, converting from a direct path to an indirect path means: changing from direct path transmission to indirect path transmission.

As an embodiment, the meaning of converting from a direct path to an indirect path is that the first node associates the SRB with the RLC entity of the PC5 interface and simultaneously releases the RLC entity of the Uu interface associated with the SRB.

As an example, the meaning of converting from a direct path to an indirect path is: the first node associates the SRB and DRB with the RLC entity of the PC5 interface, and at the same time releases the RLC of the Uu interface associated with the SRB and DRB. entity.

As an embodiment, the meaning of converting from an indirect path to a direct path is to start using the direct path and stop using the indirect path at the same time.

As an embodiment, switching from an indirect path to a direct path means: starting to use the direct path for transmission, and at the same time stopping using the indirect path for transmission.

As an embodiment, converting from an indirect path to a direct path means: changing from indirect path transmission to direct path transmission.

As an embodiment, the meaning of switching from an indirect path to a direct path is: the first node releases the PC5 connection associated with the SRB. The RLC entity of the Uu interface and the SRB are associated with the RLC entity of the Uu interface.

As an embodiment, the meaning of switching from an indirect path to a direct path is: the first node releases all RLC entities of the PC5 interface associated with the DRB, and at the same time associates the DRB with the RLC entities of the Uu interface.

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

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

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

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

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

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

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

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

As an embodiment, the first node in this application has only one cell group, that is, the main cell group (MCG).

As an embodiment, the first node in this application is not configured in a slave cell group (SCG).

As an embodiment, the relay in this application refers to L2U2N relay UE.

As an embodiment, the first node in this application uses both direct paths and indirect paths.

As an embodiment, the first signaling is RRC signaling.

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

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

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

As an embodiment, the first signaling is sent through SRB1.

As an embodiment, the first signaling is sent through SRB3.

As an embodiment, the first signaling includes some fields in RRCReconfiguration.

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 field, and the SRB-ToAddMod included in the first signaling is used to configure the first PDCP entity and the first RLC entity set. At least one.

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

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

As an embodiment, the first signaling includes an RLC-BearerConfig field, and the RLC-BearerConfig 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 field, 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 a radio bearer between the first node and a serving cell or cell group of the first node.

As an embodiment, the opposite PDCP entity of the first PDCP entity is located in the serving cell or cell group or MCG of the first node.

As an embodiment, the first signaling being used to configure the first PDCP entity includes: configuring the length of the sequence number field of the first PDCP entity.

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

As an embodiment, the first signaling being used to configure the first PDCP entity includes: configuring at least one parameter of the first PDCP entity.

As an embodiment, the first signaling being used to configure the first PDCP entity includes: configuring a main path of the first PDCP entity.

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

As an embodiment, the first signaling being used to configure the first PDCP entity includes: configuring whether the first PDCP entity uses PDCP replication.

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

As an embodiment, the first signaling being used to configure the first PDCP entity includes: configuring whether the first PDCP entity configures PDCP replication.

As an embodiment, the first signaling being used to configure the first PDCP entity includes: configuring a timer of the first PDCP entity.

As an embodiment, the RLC entities in the first RLC entity set are all used to communicate with the serving cell of the first node.

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

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

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

As an embodiment, the first RLC entity set includes 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 RLC entity in the first RLC entity.

As an embodiment, the meaning of the first signaling being used to configure the first RLC entity set includes: the first signaling configures each RLC entity in the first RLC entity to interact with the first RLC entity. The PDCP entity is associated with the radio bearer corresponding to the first PDCP entity.

As an embodiment, the meaning of the first signaling being used to configure the first RLC entity set includes: the first signaling configures the RLC bearer corresponding to each RLC entity in the first RLC entity. Or secondary link RLC bearer.

As an embodiment, the meaning of the first signaling being used to configure the first RLC entity set includes: the first signaling configures whether any RLC entity in the first RLC entity uses PDCP replication.

As an embodiment, the meaning of the first signaling being used to configure the first RLC entity set includes: the first signaling configures a logical channel corresponding to any one of the first RLC entities. identity.

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

As an embodiment, the meaning of the first signaling being used to configure the first RLC entity set includes: the first signaling configures a secondary link corresponding to any RLC entity in the first RLC entity. The RLC carries the logical channel identity on the corresponding secondary link.

As an embodiment, the meaning of the first signaling being used to configure the first RLC entity set includes: the first signaling configures the mode of any RLC entity in the first RLC entity to be AM mode. Still in 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 RLC entity in the first RLC entity.

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

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 of the first signaling being used to configure the first RLC entity set includes: the first signaling configures at least one timer of at least one RLC entity in the first RLC entity. .

As an embodiment, the meaning of the first signaling being used to configure the first RLC entity set includes: the first signaling configures a sequence number used by at least one RLC entity in the first RLC entity. The length of the domain.

As an embodiment, the meaning of the first signaling being used to configure the first RLC entity set includes: the first signaling indicates querying (poll) at least one RLC entity in the first RLC entity.

As an embodiment, the secondary link RLC entity is a secondary link RLC entity, and the secondary link is a link for communication between UEs.

As a sub-embodiment of this embodiment, the secondary link RLC entity in the first RLC entity set is established for communication between the first node and the network.

As a sub-embodiment of this embodiment, the secondary link RLC entity in the first RLC entity set is an RLC entity between the first node and the L2U2N relay UE of the first node.

As an embodiment, the secondary link RLC entity is a secondary link RLC entity, and the secondary link is a link including RLC, MAC and physical layer for communication between UE and UE.

As a sub-embodiment of this embodiment, the communication between the first node and the network is 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 the first A secondary link between the node and the relay and a link between the relay of the first node and 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 used to process PDUs of the first PDCP entity, and the opposite end entity of the secondary link RLC entity is located in the relay of the first node.

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

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

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

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

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

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

As a sub-embodiment of this embodiment, the main link includes the RLC layer, MAC and physical layer for the serving cell group of the first node.

As an embodiment, the RLC layer, MAC layer and physical layer included in the secondary link are not targeted at the serving cell group of the first node.

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

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 includes the RLC layer, MAC layer and physical layer for NG-RAN.

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

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

As an embodiment, the indirect path refers to a secondary link or communication using a secondary link.

As an embodiment, the secondary link RLC entity is an RLC entity of the PC5 interface.

As an embodiment, the secondary link 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 the identity of the radio bearer corresponding to the first PDCP entity through the RadioBearerConfig field.

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

As a sub-embodiment of this embodiment, the sl-RemoteUE-RB-Identity field indicates the first radio bearer configured in the RadioBearerConfig domain, 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 at least one RLC entity on the secondary link A domain is associated with the first radio bearer.

As an embodiment, the primary link RLC entity and the secondary link RLC entity are configured through different domains of the first signaling.

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

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

As a sub-embodiment of this embodiment, the secondary link RLC entity is configured through the SL-RLC-ChannelConfig domain of the first signaling.

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

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

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

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

As an embodiment, the phrase "any RLC entity in the first RLC entity set is associated with the first PDCP entity" means: the deputy corresponding to any RLC entity in the first RLC entity set. The PDCP entity corresponding to the radio bearer served by the link RLC bearer is the first PDCP entity.

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

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

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

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

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

As an embodiment, the first signaling indicates that the cell group identity of the main path of the first PDCP entity is the first cell group identity; the first signaling indicates the logic of the main path of the first PDCP entity. The channel identity is the 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; the logical channel corresponding to the first RLC entity is determined by the first main logical Channel identity.

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

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

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

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

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

As an embodiment, the first signaling indicates the identity of the relay node targeted by the main path of the first PDCP entity.

As a sub-embodiment of this embodiment, the first RLC entity is a secondary link RLC entity; the identity of the node targeted by the first RLC entity is indicated by the first signaling and the first PDCP entity The identity of the relay node targeted by the main path.

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

As an embodiment, the serving cell of the first node may indicate activation or deactivation of the PDCP replication function of the first radio bearer.

As an embodiment, the serving cell of the first node may instruct to activate the PDCP replication function of any primary link RLC entity in the first RLC entity set. When any primary link RLC entity in the first RLC entity set When the PDCP replication function of the link RLC entity is activated, the PDCP replication function of the first radio bearer is also activated.

As an embodiment, the serving cell of the first node may instruct to activate the PDCP replication function of any secondary link RLC entity in the first RLC entity set. When any secondary link RLC entity in the first RLC entity set When the PDCP replication function of the link RLC entity is activated, all The PDCP replication function of the first radio bearer is also activated.

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

As an example, the serving cell of the first node may instruct to deactivate the PDCP replication function of all RLC entities in the first RLC entity set. When the PDCP replication function of all RLC entities in the first RLC entity set is When the functions are all deactivated, the PDCP replication function of the first radio bearer is also deactivated.

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

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

As an embodiment, when the PDCP replication of the first radio bearer is activated, the PDCP control PDU of the first PDCP entity is sent through the primary RLC entity of the first PDCP entity.

As an embodiment, when the PDCP replication of the first radio bearer is activated, the PDCP control PDU of the first PDCP entity is not sent through an RLC entity other than the primary RLC entity of the first PDCP entity.

As an embodiment, when the PDCP replication of the first radio bearer is activated, the PDCP data PDU of the first PDCP entity is copied and passed through the RLC that activates PDCP replication associated with the first PDCP entity. Entity sent.

As an embodiment, when the PDCP non-replication of the first radio bearer is activated, the PDCP PDU of the first PDCP entity is sent through the main RLC entity of the first PDCP.

As an embodiment, the sentence "the main path of the first PDCP entity is associated with the first RLC entity in the first RLC entity set" means that the main path of the first PDCP entity is for the first RLC entity of.

As an embodiment, the sentence "the main path of the first PDCP entity is associated with the first RLC entity in the first RLC entity set" means that the main RLC entity corresponding to the main path of the first PDCP entity is the The first RLC entity.

As an embodiment, the first signaling includes first sub-signaling and second sub-signaling, and the first sub-signaling and the second sub-signaling respectively configure the first RLC entity set. Primary link RLC entity and secondary link RLC entity.

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 MAC layer signaling.

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 MAC CE.

As an embodiment, the number of bits included in the first bit string is greater than N1.

As an embodiment, the first bit string includes N1 bits, where N1 is a positive integer.

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

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

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

As a sub-embodiment of this embodiment, the 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, the N1 is predefined.

As a sub-embodiment of this embodiment, the first bit string is the N1 lowest bits in the second signaling, and the second signaling includes 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 the identity of the first radio bearer.

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

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

As an embodiment, the meaning of the sentence that there is a one-to-one mapping relationship between the first bit string and N1 RLC entities other than the first RLC entity in the first RLC entity set includes: the first RLC entity set Including 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 first RLC The N1 RLC entities in the entity set do not include the first RLC entity.

As a sub-embodiment of this embodiment, there is a one-to-one mapping relationship between any RLC entity other than the first RLC entity in the first RLC entity set and a bit in the first bit string.

As a sub-embodiment of this embodiment, there is a one-to-one mapping between at least any main link RLC entity other than the first RLC entity in the first RLC entity set and a bit in the first bit string. relation.

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, there is no mapping relationship between the first RLC entity and any bit in the first bit string.

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

As an embodiment, the meaning of the sentence that the first bit string is used to indicate activation or deactivation of PDCP replication of an RLC entity in the first RLC entity set includes: any bit in the first bit string is 0 is used to indicate deactivation of the PDCP replication of the RLC entity associated with the any bit in the first bit string; any bit in the first bit string is 1 to indicate activation with the first bit string. PDCP copy of the RLC entity associated with any bit in a bit string.

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

As an embodiment, the meaning of the sentence that the first bit string is used to indicate activation or deactivation of PDCP replication of an RLC entity in the first RLC entity set includes: the first bit string is the same as the first bit string. The values of the bits in which the RLC entities in the RLC entity set have a one-to-one mapping relationship are meaningful.

As an embodiment, the meaning of the sentence that the first bit string is used to indicate activation or deactivation of PDCP replication of an RLC entity in the first RLC entity set includes: the first bit string does not match the first bit string. The values of bits in which RLC entities in an RLC entity set have a one-to-one mapping relationship are meaningless.

As an embodiment, the meaning of the sentence that the first bit string is used to indicate activation or deactivation of PDCP replication of an RLC entity in the first RLC entity set includes: the first bit string is the same as the first bit string. The value of the bit in which the RLC entities in the RLC entity set have a one-to-one mapping relationship is used to indicate activation or deactivation of PDCP replication of the mapped RLC entity set.

As an embodiment, the first PDCP data PDU is a PDU used to carry RRC signaling.

As an embodiment, the first PDCP data PDU is a PDU used to carry 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 an embodiment, the first PDCP data PDU is sent 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 with PDCP replication activated in the first RLC entity set, and the behavior of sending the first PDCP data PDU of the first PDCP entity includes: sending the first PDCP data PDU Copy Y copies and submit them to the Y RLC entities in the first RLC entity set for processing 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 Y RLC entities in the first RLC entity set respond to the first PDCP data The processing of PDU includes adding 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 encapsulating it into an RLC PDU and sending it to a lower layer.

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

As an embodiment, the PDCP replication of at least one primary link RLC entity in the first RLC entity set is activated.

As an embodiment, the PDCP replication of at least one secondary link RLC entity in the first RLC entity set is activated.

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

As an embodiment, the PDCP replication of at least one RLC entity other than the first RLC entity in the first RLC entity set is activated.

As an embodiment, the first signaling indicates activating PDCP replication of the first RLC entity.

As an embodiment, the first logical channel identity list consists of logical channel identities, including at least one logical channel identity.

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

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

As an embodiment, the logical channel identity on 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 on the main link is the main link RLC entity.

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

As an embodiment, the logical channel identity on the secondary link is the identity of the logical channel between the first node and the L2U2N 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 on 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 configured by the first node itself.

As an embodiment, the logical channel identity on the secondary link is configured by the L2U2N relay UE of the first node.

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

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

As an embodiment, the primary link RLC entity in the first RLC entity set is only associated with the logical channel identity on the primary link in the first logical channel identity list.

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

As an embodiment, the logical channel identity on the main link in the first logical channel identity list is only associated with the main link RLC entity in the first RLC entity set.

As an embodiment, the logical channel identity on the secondary link in the first logical channel identity list is only associated with the secondary link RLC entity in the first RLC entity set.

As an embodiment, the meaning of the sentence that any RLC entity in the first RLC entity set is associated with a logical channel identity in the first logical channel identity list includes: any RLC in the first RLC entity set There is a mapping relationship between the entity and a logical channel identity in the first logical channel identity list.

As an embodiment, the meaning of the sentence that any RLC entity in the first RLC entity set is associated with a logical channel identity in the first logical channel identity list includes: any RLC in the first RLC entity set The identity of the logical channel corresponding to the entity belongs to the first logical channel identity list.

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

As an embodiment, the meaning of the sentence that any RLC entity in the first RLC entity set is associated with a logical channel identity in the first logical channel identity list includes: any RLC in the first RLC entity set There is a mapping relationship or association relationship between the RLC bearer corresponding to the entity and a logical channel identity in the first logical channel identity list.

As an embodiment, the meaning of the sentence that any RLC entity in the first RLC entity set is associated with a logical channel identity in the first logical channel identity list includes: any RLC in the first RLC entity set There is a mapping relationship or association relationship between the secondary link RLC channel corresponding to the entity and a logical channel identity in the first logical channel identity list.

As an embodiment, the meaning of the sentence that any RLC entity in the first RLC entity set is associated with a logical channel identity in the first logical channel identity list includes: any RLC in the first RLC entity set There is a mapping relationship or association relationship between the RLC bearer configuration index corresponding to the entity and a logical channel identity in the first logical channel identity list.

As an embodiment, the one-to-one mapping relationship between the first bit string and N1 RLC entities other than the first RLC entity in the first RLC entity set is related to the first logical channel. The meaning related to the logical channel identity on the main link in the identity list is: the logical channel identity on the main link in the first logical channel identity list affects or determines how the first bit string interacts with the first RLC entity N1 RLC entities other than the first RLC entity in the set are mapped.

As an embodiment, the one-to-one mapping relationship between the first bit string and N1 RLC entities other than the first RLC entity in the first RLC entity set is related to the first logical channel. The meaning that the logical channel identity on the secondary link in the identity list is irrelevant includes: the logical channel identity on the secondary link in the first logical channel identity list will not affect or determine the relationship between the first bit string and the third bit string. A mapping relationship between N1 RLC entities other than the first RLC entity in an RLC entity set.

As an embodiment, the logical channel identities on the main link 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 identity on the secondary link in the first logical channel identity list may be the same as the logical channel identity on the primary link.

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

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

As an embodiment, the first radio bearer is 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 on 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 opposite end entity of the first RLC entity is located in the L2U2N relay UE of the first node.

As a sub-embodiment of this embodiment, the first RLC entity is an RLC entity on the 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 activating any RLC in the first RLC entity set that is associated with a logical channel identity on a secondary link in the first logical channel identity list. PDCP replication of the entity; the second signaling is only used to indicate activation or deactivation of the primary link in the first logical channel identity list other than the first RLC entity in the first RLC entity set. PDCP copy of the associated RLC entity; the lowest bit in the first bit string is mapped to the second RLC entity, and the second RLC entity belongs to the first RLC entity set; the second RLC entity and associated with a first logical channel identity; among the logical channel identities on 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 The logical channel identity with the smallest value 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 is mapped only to the lowest bit in the first bit string.

As a sub-embodiment of this embodiment, the lowest bit of the first bit string is 0 to indicate deactivation of the second RLC entity. PDCP replication; the lowest bit of the first bit string is 1 to indicate activating PDCP replication 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 includes: there is a mapping relationship between the second RLC entity and 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 includes: 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 includes: there is a mapping relationship between the RLC bearer corresponding to the second RLC entity and 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 includes: there is a mapping relationship between the secondary link RLC channel corresponding to the second RLC entity and 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 includes: 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 includes: the first logical channel identity is for the 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 includes: the first logical channel identity is for the RLC bearer corresponding to the second RLC entity.

As an embodiment, the value of the logical channel identity on the main link in the first logical channel identity list associated with the RLC entity other than the first RLC entity in the first RLC entity set is The smallest logical channel identity is the first logical channel identity, which means that the logical channel identities associated with the main link RLC entities other than the first RLC entity in the first RLC entity set all belong to the first logical channel identity. A first logical channel identity list; the logical channel identities associated with main link RLC entities other than the first RLC entity in the first RLC entity set are all logical channel identities on the main link; the first The logical channel identity with the smallest value among the logical channel identities associated with the main link RLC entities other than the first RLC entity in the RLC entity set is the first logical channel identity.

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

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

As a sub-embodiment of this embodiment, the first RLC entity is a main 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, the values of any two logical channel identities in the first logical channel identity list are different.

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

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

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

As a sub-embodiment of this embodiment, the first RLC entity is a main 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 list. 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 value among the logical channel identities on the main link in the first logical channel identity list. .

As an embodiment, the meaning of the sentence that any RLC entity in the first RLC entity set is used for communication with the MCG includes: the peer RLC entity of any main link RLC entity in the first RLC entity set Located at MCG.

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

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

As an embodiment, the meaning of the sentence that any RLC entity in the first RLC entity set is used for communication with the MCG includes: the logical channel corresponding to any main link RLC entity in the first RLC entity set Is the logical channel on the main link to the MCG.

As an embodiment, the meaning of the sentence that any RLC entity in the first RLC entity set is used to communicate with MCG includes: any main link RLC entity in the first RLC entity set is used to transmit messages for MCG data or signaling.

As an embodiment, the meaning of the sentence that any RLC entity in the first RLC entity set is used to communicate with the MCG includes: any main link RLC entity in the first RLC entity set is used to receive messages from the MCG. data or signaling.

As an embodiment, the meaning of the sentence that any RLC entity in the first RLC entity set is used for communication with MCG includes: any secondary link RLC entity in the first RLC entity set is used to transmit messages for MCG The data or signaling carried over the radio.

As an embodiment, the meaning of the sentence that any RLC entity in the first RLC entity set is used for communication with the MCG includes: the radio bearer associated with any secondary link RLC entity in the first RLC entity set is the wireless bearer between the first node and the MCG.

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

As an embodiment, the meaning of the sentence that any RLC entity in the first RLC entity set is used for communication with the MCG includes: any secondary link RLC entity in the first RLC entity set is used for the first RLC entity set. A node communicates with the MCG through a relay.

As an embodiment, the meaning of the sentence that any RLC entity in the first RLC entity set is used for communication with the MCG includes: any secondary link RLC entity in the first RLC entity set is connected to the main link associated with the radio bearer on the .

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

As an embodiment, the first RLC entity set includes less than N1+1 RLC entities.

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

As an embodiment, the first RLC entity set includes more than N1+1 RLC entities.

As an embodiment, the first bit string only has a mapping relationship with the RLC entities on the main link in the first RLC entity set.

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

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

As an embodiment, the first RLC entity set includes N1+1 RLC entities, and N2 RLC entities among the N1+1 RLC entities are identical to those on the secondary link in the first logical channel identity list. Logical channel identities are associated; N2 bits in the first bit string have a first mapping relationship with the N2 RLC entities; N1-N2 bits in the first bit string are related to the first RLC entity There is a second mapping relationship between the N2 RLC entities in the set and RLC entities other than the first RLC entity; the N2 RLC entities in the first RLC entity set and the RLC entities other than the first RLC entity The value size of the logical channel identity in the first logical channel identity list associated with the RLC entity is used to determine the second mapping relationship;

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

As a sub-embodiment of this embodiment, the first RLC entity set includes a total of N2+1 RLC entities on the secondary link, where the first RLC entity is an RLC entity on the secondary link.

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

As an embodiment, the meaning of the sentence that the N2 RLC entities among the N1+1 RLC entities are associated with the logical channel identities on the secondary links in the first logical channel identity list includes: the first RLC The entity set includes N1+1 RLC entities; the first RLC There is a mapping relationship between the N2 RLC entities in the entity set and the logical channel identities on the secondary links in the first logical channel identity list.

As an embodiment, the meaning of the sentence that the N2 RLC entities among the N1+1 RLC entities are associated with the logical channel identities on the secondary links in the first logical channel identity list includes: the first RLC The 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 the secondary link. The identities of the logical channels corresponding to the RLC bearers of the N2 RLC entities belong to the first logical channel identity list.

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

As an embodiment, the meaning of the sentence that the N2 RLC entities among the N1+1 RLC entities are associated with the logical channel identities on the secondary links in the first logical channel identity list includes: the N2 RLCs The entity is a secondary link RLC entity.

As an embodiment, there is a second mapping between N1-N2 bits in the first bit string and the N2 RLC entities in the first RLC entity set and RLC entities other than the first RLC entity. The meaning of the relationship includes: the RLC entity mapped to the first bit string in the first RLC entity set is neither the first RLC entity nor the N2 RLC entities. The phrase mapping refers to the Second mapping.

As an embodiment, there is a second mapping between N1-N2 bits in the first bit string and the N2 RLC entities in the first RLC entity set and RLC entities other than the first RLC entity. The meaning of the relationship includes: there is the second mapping relationship between N1-N2 bits in the first bit string and N1-N2 RLC entities in the first RLC entity set; Any RLC entity among the N1-N2 RLC entities does not belong to the N2 RLC entities in the first RLC entity set; the N1-N2 RLC entities in the first RLC entity set The first RLC entity is also not included.

As an embodiment, there is a second mapping between N1-N2 bits in the first bit string and the N2 RLC entities in the first RLC entity set and RLC entities other than the first RLC entity. The meaning of the relationship includes: there is the second mapping relationship 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 are different from the N2 RLC entities in the first RLC entity set; the N1-N2 RLC entities in the first RLC entity set also do not include the N2 RLC entities in the first RLC entity set. An RLC entity.

As an embodiment, the meaning of the sentence that the N2 bits and the N1-N2 bits in the first bit string are different is: the N2 bits in the first bit string and the N1-N2 bits are different. The N2 bits occupy different bit positions.

As an embodiment, the different meanings of the N2 bits and the N1-N2 bits in the first bit string have nothing to do with whether the value is 0 or 1.

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

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

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

As an embodiment, the first mapping relationship is determined through a predefined algorithm.

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

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

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

As a sub-embodiment of this embodiment, the sentence that the N2 bits of the first bit string are continuous means: the N2 bits of the first bit string are continuous and the N2 bits are continuous. The value of is irrelevant.

As a sub-embodiment of this embodiment, the sentence that the N2 bits of the first bit string are continuous means: the N2 bits of the first bit string in the first bit string are connected.

As a sub-embodiment of this embodiment, the sentence that the N2 bits of the first bit string are continuous means: the N2 bits of the first bit string in the first bit string are Neighboring.

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

As a sub-embodiment of this embodiment, the sentence that the N1-N2 bits of the first bit string are continuous means: the N1-N2 bits of the first bit string are continuous with the The values of the N1-N2 bits are irrelevant.

As a sub-embodiment of this embodiment, the sentence that the N1-N2 bits of the first bit string are continuous means: the N1-N2 bits of the first bit string are in the first The bit strings are connected.

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

As an embodiment, the first RLC entity set includes N1+N2+1 RLC entities, the first RLC entity set includes N2 secondary link RLC entities and is consistent with the secondary link RLC entities in the first logical channel identity list. The logical channel identities on the links are associated; the first RLC entity set includes N1 main link RLC entities and is associated with the logical channel identities on the main links in the first logical channel identity list; the The first RLC entity does not belong to the N1 primary link RLC entities in the first RLC entity set nor the N2 secondary link RLC entities in the first RLC entity set; the first There is a first mapping relationship between N2 bits in the bit string and the N2 secondary link RLC entities in the first RLC entity set; N1 bits in the first bit string and the first RLC entity There is a second mapping relationship between the N1 main link RLC entities in the set; and the first logical channel identity list associated with the N1 main link RLC entities in the first RLC entity set. The value of the logical channel identity is used to determine the second mapping relationship;

Wherein, the N2 bits and the N1 bits in the first bit string are different, the N2 and the N1 are positive integers respectively, and the first mapping relationship and the second mapping relationship are both the same. A mapping.

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

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

As a sub-embodiment of this embodiment, the largest logical channel identity among the logical channel identities in the first logical channel identity list associated with the N1 primary link RLC entities in the first RLC entity set An RLC entity in an associated first RLC entity set is mapped to the highest bit among 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 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 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 Figure 2.

Figure 2 illustrates a diagram of the network architecture 200 of 5G NR, LTE (Long-Term Evolution, Long-Term Evolution) and LTE-A (Long-Term Evolution Advanced, Enhanced Long-Term Evolution) systems. The 5G NR or LTE network architecture 200 may be called 5GS (5G System)/EPS (Evolved Packet System) 200 or some other suitable term. 5GS/EPS 200 may include one or more UE (User Equipment) 201, NG-RAN (Next Generation Radio Access Network) 202, 5GC (5G Core Network, 5G Core Network)/EPC (Evolved Packet Core, Evolved Packet Core) 210, HSS (Home Subscriber Server, Home Subscriber Server)/UDM (Unified Data Management, Unified Data Management) 220 and Internet Services 230. 5GS/EPS Interconnection with other access networks is possible, but these entities/interfaces are not shown for simplicity. As shown, 5GS/EPS provides packet-switched services, however those skilled in the art will readily appreciate that the various concepts presented throughout this application may be extended to networks that provide circuit-switched services or other cellular networks. NG-RAN includes NR Node B (gNB) 203 and other gNBs 204. gNB 203 provides user and control plane protocol termination towards UE 201. gNB 203 may connect to other gNBs 204 via the Xn interface (eg, backhaul). gNB 203 may also be called a base station, base transceiver station, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), TRP (transmitting and receiving node) or some other suitable terminology. gNB203 provides UE201 with an access point to 5GC/EPC210. Examples of UE 201 include cellular phones, smart phones, Session Initiation Protocol (SIP) phones, laptop computers, personal digital assistants (PDAs), satellite radio, non-terrestrial base station communications, satellite mobile communications, global positioning systems, multimedia devices , video devices, digital audio players (e.g., MP3 players), cameras, game consoles, drones, aircraft, narrowband IoT devices, machine type communications devices, land vehicles, automobiles, wearable devices, or any Other similar functional devices. Those skilled in the art may also refer to UE 201 as mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access. terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client or some other suitable term. gNB203 is connected to 5GC/EPC210 through the S1/NG interface. 5GC/EPC210 includes MME (Mobility Management Entity, mobility management entity)/AMF (Authentication Management Field, authentication management domain)/SMF (Session Management Function, session management function) 211. Other MME/AMF/SMF214, S-GW (Service Gateway, Service Gateway)/UPF (User Plane Function, User Plane Function) 212 and P-GW (Packet Date Network Gateway, Packet Data Network Gateway)/UPF213. MME/AMF/SMF211 is the control node that handles signaling between UE201 and 5GC/EPC210. Basically, MME/AMF/SMF211 provides bearer and connection management. All user IP (Internet Protocol) packets are transmitted through S-GW/UPF212, and S-GW/UPF212 itself is connected to P-GW/UPF213. P-GW provides UE IP address allocation and other functions. P-GW/UPF 213 is connected to Internet service 230. The Internet service 230 includes the operator's corresponding Internet protocol service, which may specifically include the Internet, an intranet, IMS (IP Multimedia Subsystem, IP Multimedia Subsystem), and packet switching streaming services.

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

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

As an embodiment, the wireless link from the UE 201 to the NR Node B is an uplink.

As an example, the wireless link from the NR Node B to the UE 201 is the downlink.

As an embodiment, the UE 201 supports relay transmission.

As an embodiment, the UE201 includes a mobile phone.

As an embodiment, the UE 201 is a vehicle including a car.

As an embodiment, the UE 201 supports secondary link transmission.

As an embodiment, the UE 201 supports MBS transmission.

As an embodiment, the UE 201 supports MBMS transmission.

As an embodiment, the gNB 203 is a macro cellular (MarcoCellular) base station.

As an embodiment, the gNB 203 is a Micro Cell base station.

As an embodiment, the gNB 203 is a PicoCell base station.

As an embodiment, the gNB 203 is a flying platform device.

As an embodiment, the gNB 203 is a satellite device.

Example 3

Embodiment 3 shows a schematic diagram of an embodiment of a wireless protocol architecture of a user plane and a control plane according to the present application, as shown in FIG. 3 . Figure 3 is a schematic diagram illustrating an embodiment of a radio protocol architecture for user plane 350 and control plane 300, Figure 3 shows with three layers for a first node (UE, satellite or aircraft in gNB or NTN) and a second Node (gNB, UE or satellite or aircraft in NTN), or radio protocol architecture of the control plane 300 between two UEs: 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 called PHY301 in this article. Layer 2 (L2 layer) 305 is above the PHY 301 and is responsible for the link between the first node and the second node and the two UEs through the PHY 301. The L2 layer 305 includes the MAC (Medium Access Control, media access control) sublayer 302, RLC (Radio Link Control, wireless link layer control) Protocol) sublayer 303 and PDCP (Packet Data Convergence Protocol, Packet Data Convergence Protocol) sublayer 304, these sublayers terminate at the second node. PDCP sublayer 304 provides multiplexing between different radio bearers and logical channels. The PDCP sublayer 304 also provides security by encrypting data packets, and provides handoff 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. MAC sublayer 302 provides multiplexing between logical and transport channels. The MAC sublayer 302 is also responsible for allocating various radio resources (eg, resource blocks) in a cell among the first nodes. MAC sublayer 302 is also responsible for HARQ operations. The RRC (Radio Resource Control, radio resource control) sublayer 306 in layer 3 (L3 layer) in the control plane 300 is responsible for obtaining radio resources (ie, radio bearers) and using the RRC signaling between the second node and the first node. command to configure the lower layer. PC5-S (PC5 Signaling Protocol, PC5 signaling protocol) sublayer 307 is responsible for processing 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. For the physical layer 351, the L2 layer 355 The PDCP sublayer 354, the RLC sublayer 353 in the L2 layer 355 and the MAC sublayer 352 in the L2 layer 355 are substantially the same as the corresponding layers and sublayers in the control plane 300, but the PDCP sublayer 354 also provides for upper Header compression of layer packets to reduce radio transmission overhead. The L2 layer 355 in the user plane 350 also includes an SDAP (Service Data Adaptation Protocol, Service Data Adaptation Protocol) sublayer 356. The SDAP sublayer 356 is responsible for the mapping between QoS flows and data radio bearers (DRB, Data Radio Bearer). , to support business diversity. SRB can be regarded as a service or interface provided by the PDCP layer to a higher layer, such as the RRC layer. In the NR system, SRBs include SRB1, SRB2, SRB3, and when it comes to secondary link communication, there is also SRB4, which are used to transmit different types of control signaling. The SRB is a bearer between the UE and the access network and is used to transmit control signaling including RRC signaling between the UE and the access network. SRB1 has special significance for UE. After each UE establishes an RRC connection, there will be SRB1 for transmitting RRC signaling. Most of the signaling is transmitted through SRB1. If SRB1 is interrupted or unavailable, the UE must perform RRC reconstruction. SRB2 is generally only used to transmit NAS signaling or security-related signaling. The UE may not configure SRB3. Except for emergency services, the UE must establish an RRC connection with the network to conduct subsequent communications. Although not shown, the first node may have several upper layers above the L2 layer 355. Also included are the network layer (eg, IP layer) terminating at the P-GW on the network side and the application layer terminating at the other end of the connection (eg, remote UE, server, etc.). For UEs involved in relay services, the control plane may also include an adaptation sublayer SRAP (Sidelink Relay Adaptation Protocol, secondary link relay adaptation is possible) 308, and its user plane may also include an adaptation sublayer SRAP 358. The introduction of layers helps lower layers, such as the MAC layer, such as the RLC layer, to multiplex and/or differentiate data from multiple source UEs.

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

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

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

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

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

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

As an embodiment, the second PDCP data PDU in this 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 present application, as shown in FIG. 4 . Figure 4 is a block diagram of a first communication device 450 and a second communication device 410 communicating with each other in the 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 may optionally include a multi-antenna transmit processor 457 and a multi-antenna receive processor 458, Transmitter/receiver 454 and antenna 452.

The second communication device 410 includes a controller/processor 475, a memory 476, a receiving processor 470, a transmitting processor 416, and may optionally include a multi-antenna receiving processor 472, a multi-antenna transmitting processor 471, a transmitter/receiving transmitter 418 and antenna 420.

In transmission from the second communication device 410 to the first communication device 450, upper layer data packets from the core network are provided to the controller/processor 475 at the second communication device 410. Controller/processor 475 implements the functionality of the L2 (Layer-2) layer. In transmission from the second communications device 410 to the first communications device 450, the controller/processor 475 provides header compression, encryption, packet segmentation and reordering, multiplexing between logical and transport channels Multiplexing, 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 communications device 450 . hair The transmit processor 416 and the multi-antenna transmit processor 471 implement various signal processing functions for the L1 layer (ie, physical layer). Transmit processor 416 implements encoding and interleaving to facilitate forward error correction (FEC) at the second communications device 410, as well as based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift Mapping of signal clusters for M-phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The multi-antenna transmit processor 471 performs digital spatial precoding on the coded and modulated symbols, including codebook-based precoding and non-codebook-based precoding, and beamforming processing to generate one or more spatial streams. Transmit processor 416 then maps each spatial stream to a subcarrier, multiplexes it with a reference signal (eg, a pilot) in the time and/or frequency domain, and then uses an inverse fast Fourier transform (IFFT) to generate A physical channel carrying a stream of time-domain multi-carrier symbols. Then the multi-antenna transmit processor 471 performs transmit analog precoding/beamforming operations on the time domain multi-carrier symbol stream. Each transmitter 418 converts the baseband multi-carrier symbol stream provided by the multi-antenna transmit processor 471 into a radio frequency stream, which is then provided to a different antenna 420.

In transmission from the second communications device 410 to the first communications device 450 , each receiver 454 receives the signal via its respective antenna 452 at the first communications device 450 . Each receiver 454 recovers the information modulated onto the radio frequency carrier and converts the radio frequency stream into a baseband multi-carrier 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 of the L1 layer. Multi-antenna receive processor 458 performs receive analog precoding/beamforming operations on the baseband multi-carrier symbol stream from receiver 454. The receive processor 456 converts the baseband multi-carrier symbol stream after the received 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 receiving processor 456, where the reference signal will be used for channel estimation, and the data signal is recovered after multi-antenna detection in the multi-antenna receiving processor 458. The first communication device 450 is any spatial stream that is the destination. The symbols on each spatial stream are demodulated and recovered in the receive processor 456, and soft decisions are generated. The receive processor 456 then decodes and deinterleaves the soft decisions to recover upper layer data and control signals transmitted by the second communications device 410 on the physical channel. Upper layer data and control signals are then provided to controller/processor 459. Controller/processor 459 implements the functions of the L2 layer. Controller/processor 459 may be associated with memory 460 which stores program code and data. Memory 460 may be referred to as computer-readable media. In 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 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 transmission from the first communications device 450 to the second communications device 410, at the first communications device 450, a data source 467 is used 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 functionality at the second communications device 410 as described in transmission from the second communications device 410 to the first communications device 450, the controller/processor 459 implements headers based on radio resource allocation Compression, encryption, packet segmentation and reordering, and multiplexing between logical and transport channels, implement L2 layer functions for the user plane and control plane. The controller/processor 459 is also responsible for retransmission of lost packets, and signaling to the second communications device 410 . The transmit processor 468 performs modulation mapping and channel coding processing, and the multi-antenna transmit processor 457 performs digital multi-antenna spatial precoding, including codebook-based precoding and non-codebook-based precoding, and beam forming processing, and then transmits The processor 468 modulates the generated spatial stream into a multi-carrier/single-carrier symbol stream, which undergoes analog precoding/beamforming operations in the multi-antenna transmit processor 457 and then is provided to different antennas 452 via the transmitter 454. Each transmitter 454 first converts the baseband symbol stream provided by the multi-antenna transmission processor 457 into a radio frequency symbol stream, and then provides it to the antenna 452.

In the transmission from the first communication device 450 to the second communication device 410, the functionality at the second communication device 410 is similar to that in the transmission from the second communication device 410 to the first communication device 450. The reception function at the first communication device 450 is described in the transmission. Each receiver 418 receives radio frequency signals through its corresponding antenna 420, converts the received radio frequency signals into baseband signals, and provides the baseband signals to multi-antenna receive processor 472 and receive processor 470. The receiving processor 470 and the multi-antenna receiving processor 472 jointly implement the functions of the L1 layer. Controller/processor 475 implements L2 layer functions. Controller/processor 475 may be associated with memory 476 that stores program code and data. Memory 476 may be referred to as computer-readable media. In transmission from the first communications device 450 to the second communications device 410, the controller/processor 475 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression , control signal processing to recover upper layer data packets from UE450. Upper layer packets from controller/processor 475 may be provided to the core network.

As an embodiment, the first communication device 450 device includes: at least one processor and at least one memory, the at least one memory includes computer program code; the at least one memory and the computer program code are configured to interact with the Using the at least one processor together, the first communication device 450 at least: receives first signaling, the first signaling is used to configure the first PDCP entity and the first RLC entity set; the first RLC The entity set includes at least one secondary link RLC entity and one main link RLC entity; any RLC entity in the first RLC entity set is associated with the first PDCP entity; the main path of the first PDCP entity is The mentioned Associated with a first RLC entity in an RLC entity set; receiving second signaling, where the second signaling includes a first bit string, and N1 bits of the first bit string are the same as those in the first RLC entity set. N1 RLC entities other than the first RLC entity have a one-to-one mapping relationship; the first bit string is used to indicate activation or deactivation of PDCP replication of the RLC entities in the first RLC entity set; send all The first PDCP data PDU of the first PDCP entity; the act of sending the first PDCP data PDU of the first PDCP entity includes: copying the first PDCP data PDU of the first PDCP entity and placing the copied copy Submit to the RLC entities whose PDCP replication is activated in the first RLC entity set respectively; wherein, the N1 is a positive integer, any RLC entity in the first RLC entity set and one of the first logical channel identity lists Logical channel identities are associated; the one-to-one mapping relationship between the first bit string and N1 RLC entities other than the first RLC entity in the first RLC entity set is related to the first logical channel The first bit string is related to the logical channel identity on the main link in the identity list, and the first bit string is related to the existence of N1 RLC entities other than the first RLC entity in the first RLC entity set. The mapping relationship has nothing to do with the logical channel identity on the secondary link in the first logical channel identity list.

As an embodiment, the first communication device 450 includes: a memory that stores a program of computer-readable instructions that, when executed by at least one processor, generates actions, and the actions include: receiving a first A signaling, 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 one primary link RLC entity; the Any RLC entity in the first RLC entity set is associated with the first PDCP entity; the main path of the first PDCP entity is associated with the first RLC entity in the first RLC entity set; receiving the second signal The second signaling includes a first bit string, and there is a one-to-one mapping between N1 bits of the first bit string and N1 RLC entities other than the first RLC entity in the first RLC entity set. relationship; the first bit string is used to indicate activation or deactivation of PDCP replication of the RLC entity in the first RLC entity set; sending the first PDCP data PDU of the first PDCP entity; the behavior sends the The first PDCP data PDU of the first PDCP entity includes: copying the first PDCP data PDU of the first PDCP entity and submitting the copied copies to the RLC in which PDCP replication is activated in the first RLC entity set respectively. Entity; wherein, the N1 is a positive integer, and any RLC entity in the first RLC entity set is associated with a logical channel identity in the first logical channel identity list; the first bit string is associated with the first logical channel identity. The one-to-one mapping relationship existing among the N1 RLC entities other than the first RLC entity in the RLC entity set is related to the logical channel identity on the main link in the first logical channel identity list, and, 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 the same as the one-to-one mapping relationship between the first bit string and the N1 RLC entities in the first logical channel identity list on the secondary link in the first logical channel identity list. Logical channel identity is irrelevant.

As an embodiment, the second communication device 410 includes: at least one processor and at least one memory, the at least one memory includes computer program code; the at least one memory and the computer program code are configured to interact with the Using the at least one processor together, the second communication device 410 at least: sends first signaling, the first signaling is used to configure the first PDCP entity and the first RLC entity set; the first RLC The entity set includes at least one secondary link RLC entity and one main link RLC entity; any RLC entity in the first RLC entity set is associated with the first PDCP entity; the main path of the first PDCP entity is The first RLC entity in the first RLC entity set is associated; sending second signaling, the second signaling includes a first bit string, and N1 bits of the first bit string are related to the first RLC There is a one-to-one mapping relationship for N1 RLC entities other than the first RLC entity in the entity set; the first bit string is used to indicate activation or deactivation of PDCP replication of the RLC entity in the first RLC entity set ; Receive the first PDCP data PDU of the first PDCP entity; the action of receiving the first PDCP data PDU of the first PDCP entity includes: PDCP copying the activated RLC entity from the first RLC entity set The peer RLC entity of at least one RLC entity receives a copy of the first PDCP data PDU of the first PDCP entity; wherein, the N1 is a positive integer, and any RLC entity in the first RLC entity set is associated with a logical channel identity in the first logical channel identity list; the first bit string is associated with the one that exists in N1 RLC entities other than the first RLC entity in the first RLC entity set. A mapping relationship is related to the logical channel identity on the main link in the first logical channel identity list, and the first bit string is related to N1 other than the first RLC entity in the first RLC entity set. The one-to-one mapping relationship existing among RLC entities has nothing to do with the logical channel identity on the secondary link in the first logical channel identity list.

As an embodiment, the second communication device 410 includes: a memory that stores a program of computer-readable instructions that, when executed by at least one processor, generates actions, and the actions include: sending a first A signaling, 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 one primary link RLC entity; the Any RLC entity in the first RLC entity set is associated with the first PDCP entity; the main path of the first PDCP entity is associated with the first RLC entity in the first RLC entity set; sending a second message The second signaling includes a first bit string, and N1 bits of the first bit string are stored with N1 RLC entities other than the first RLC entity in the first RLC entity set. In a one-to-one mapping relationship; the first bit string is used to indicate activation or deactivation of PDCP replication of the RLC entity in the first RLC entity set; receiving the first PDCP data PDU of the first PDCP entity; The described behavior of receiving the first PDCP data PDU of the first PDCP entity includes: receiving the first RLC entity from the peer RLC entity of at least one RLC entity in the RLC entity whose PDCP replication is activated in the first RLC entity set. A copy of the first PDCP data PDU of the PDCP entity; wherein, the N1 is a positive integer, and any RLC entity in the first RLC entity set is associated with a logical channel identity in the first logical channel identity list; The one-to-one mapping relationship between the first bit string and N1 RLC entities other than the first RLC entity in the first RLC entity set and the main link in the first logical channel identity list 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 related to the logical channel identity on the first RLC entity set. The logical channel identity on the secondary link in a logical channel identity list is irrelevant.

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

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

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

As an embodiment, the first communication device 450 is a vehicle-mounted terminal.

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

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

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

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

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

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

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

As one embodiment, transmitter 454 (including antenna 452), transmit processor 468 and controller/processor 459 are used in this application to transmit the first PDCP data PDU.

As one embodiment, transmitter 454 (including antenna 452), transmit processor 468 and controller/processor 459 are used in this application to transmit the second PDCP data PDU.

As one embodiment, transmitter 418 (including antenna 420), transmit processor 416 and controller/processor 475 are used in this application to transmit the first signaling.

As one embodiment, transmitter 418 (including antenna 420), transmit processor 416 and controller/processor 475 are used in this application to transmit the second signaling.

As one embodiment, transmitter 418 (including antenna 420), transmit processor 416 and controller/processor 475 are used in this application to transmit the third signaling.

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

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

Example 5

Embodiment 5 illustrates a wireless signal transmission flow chart according to an embodiment of the present application, as shown in FIG. 5 . In Figure 5, U01 corresponds to the first node of this application, and U02 corresponds to the second node of this application. It is particularly noted that the order in this example does not limit the signal transmission sequence and implementation order in this application, where F51 The steps are optional.

For the first node U01 , receive the first signaling in step S5101; receive the second signaling in step S5102; send the first PDCP data PDU in step S5103; receive the third signaling in step S5104; and in step S5105 Send the second PDCP data PDU.

For the second node U02 , send the first signaling in step S5201; send the second signaling in step S5202; receive the first PDCP data PDU in step S5203; send the third signaling in step S5204; and in step S5205 Receive the second PDCP data PDU.

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 one primary link RLC entity; Any RLC entity in the first RLC entity set is associated with the first PDCP entity; the main path of the first PDCP entity is associated with the first RLC entity in the first RLC entity set;

The second signaling includes a first bit string, and there is a one-to-one mapping relationship between N1 bits of the first bit string and 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 replication of the RLC entity in the first RLC entity set;

The generator of the first PDCP data PDU is the first PDCP entity; the action of sending the first PDCP data PDU of the first PDCP entity includes: copying the first PDCP data of the first PDCP entity PDU and submit the copied copies to the RLC entities in the first RLC entity set for which PDCP replication is activated;

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 primary cell group or a base station of a primary cell group.

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

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

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

As an embodiment, the second node U02 corresponds to the base station corresponding to the cell group of this 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 first signaling is sent using a direct path and/or an indirect path.

As an embodiment, the second signaling is sent using a direct path and/or an indirect path.

As an embodiment, the first signaling is received through at least one RLC entity in the first RLC entity set.

As an embodiment, the first signaling is received through an RLC entity other than the first RLC entity set.

As an embodiment, the second signaling is received through at least one RLC entity in the first RLC entity set.

As an embodiment, the second signaling is received through an RLC entity other than the first RLC entity set.

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

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

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

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

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

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

As an embodiment, in response to receiving the first signaling, the first node U01 allocates at least one logical channel identity associated with a secondary link RLC entity in the first RLC entity set; The logical channel identity associated with the secondary link RLC entity in the at least one first RLC entity set belongs to the first logical channel identity list.

As an embodiment, the logical channel identity associated with the secondary link RLC entity in the first RLC entity set is configured by one of the first node U01 or a 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 RLC entity in the first RLC entity.

As an embodiment, the first signaling is used to indicate the logic associated with any primary link RLC entity in the first RLC entity. Channel identity.

As an embodiment, the first signaling is used to indicate a secondary link RLC channel associated with any secondary link RLC entity in the first RLC entity. The secondary link RLC channel associated with the secondary link RLC entity is associated with the logical channel identity in the first logical channel identity list.

As an embodiment, the first signaling is sent using SRB1.

As an embodiment, the first signaling is transmitted without using a relay node.

As an embodiment, the second signaling is transmitted without using a relay node.

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

As an embodiment, whether the first PDCP data PDU is transmitted through the relay node is related to whether PDCP replication of the secondary link RLC entity in the first RLC entity set is activated.

As an embodiment, the third signaling is used to indicate activation or deactivation of all the first RLC entity sets associated with logical channel identities on the secondary links in the first logical channel identity list. PDCP replication of the RLC entity;

As a sub-embodiment of this embodiment, the third signaling is or includes 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 of the sentence that the logical channel identity in the first logical channel identity list associated with the first RLC entity is a logical channel identity on the main link includes: the first The RLC entity is the main link RLC entity.

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

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

As a sub-embodiment of this embodiment, in response to receiving the third signaling, the PDCP replicas of all secondary link RLC entities in the first RLC entity set except the first RLC entity are Activation, or the PDCP replication of all secondary link RLC entities in the first RLC entity set except the first RLC entity is deactivated; the first RLC entity is a secondary link RLC entity.

As an embodiment, the third signaling is used to indicate activation or deactivation of PDCP replication of the first PDCP entity.

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

As an embodiment, the second PDCP data PDU is sent using the first radio bearer.

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

As an embodiment, the act of sending the second PDCP data PDU of the first PDCP entity includes: submitting the second PDCP data PDU of the first PDCP entity to the first RLC entity or the third RLC. any one of the entities;

Wherein, the split secondary path of the first PDCP entity is associated with the third RLC entity in the first RLC entity set; both the first RLC entity and the third RLC entity For communication with the MCG; one of the first RLC entity and the third RLC entity is associated with the logical channel identity on the main link in the first logical channel identity list, and the other is associated with the The logical channel identities on the secondary links in the first logical channel identity list are associated; at least one of the first signaling and the third signaling is used to implicitly indicate the first PDCP entity Split from path.

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 the 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 RLC entity set includes at least 3 RLC entities.

As a sub-embodiment of this embodiment, the first signaling indicates the logical channel identity of the split slave path of the first PDCP entity, and the logical channel identity of the split slave path belongs to the first logical channel An identity list, the third RLC entity is 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 on the primary link.

As a sub-embodiment of this embodiment, the first signaling indicates the secondary link RLC channel identity of the split secondary path of the first PDCP entity, and the secondary link RLC channel identity of the split secondary path corresponds to The logical channel identity belongs to the first logical channel identity list, and the logical channel identity in the first logical channel identity list associated with the third RLC entity corresponds to the secondary link RLC channel identity of the split slave path. The logical channel identity.

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

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 on the 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 The first PDCP entity is associated, that is, the first RLC entity and the third RLC entity are both used to transmit data of the first PDCP entity, and the peer PDCP entity of the first PDCP entity is located in the 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 The first radio bearer is associated, 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 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 passes through the first RLC entity and the third RLC entity transmits or processes, and the first radio bearer is the radio bearer between the first node U01 and MCG.

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

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

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

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

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 the 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 the 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 the 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 at least one of the first signaling and the third signaling only indicates the The secondary link RLC channel identity of the split slave path of the first PDCP entity does not indicate a logical channel identity; the secondary link RLC channel identity of the split slave path of the first PDCP entity is consistent with the first PDCP entity The splits correspond one-to-one to the logical channel identities of the paths.

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 at least one of the first signaling and the third signaling only indicates the secondary link RLC channel identity of the split slave path of the first PDCP entity but does not indicate the identity of the relay node; The first node U01 communicates with the second node U02 only through 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: The at least one of the first signaling and the third signaling only indicates the secondary link RLC channel identity of the split secondary path of the first PDCP entity and does not indicate whether it is for a cell group or for a middle Relay; when the secondary link 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 secondary link 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: The at least one of the first signaling and the third signaling only indicates the logical channel identity of the split slave path of the first PDCP entity but does not indicate the split slave path of the first PDCP entity. The cell group of the path; the split slave path of the first PDCP entity belongs to a cell group other than the cell group of the first RLC entity.

As a sub-embodiment of this embodiment, the first PDCP entity has only one split slave 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 When at least one of the first signaling and the third signaling indicates the secondary link RLC channel identity of the split secondary path of the first PDCP entity, the split secondary path of the first PDCP entity is for the secondary link. link or for the relay or PC5 interface; when at least one of the first signaling and the third signaling indicates the logical channel identity of the split slave path of the first PDCP entity, the third The split secondary path of a PDCP entity is for the primary path or Uu interface or MCG or SCG.

Example 6

Embodiment 6 illustrates a schematic diagram of a protocol stack for relay communication according to an embodiment of the present application, as shown in FIG. 6 .

Figure 6 is divided into three sub-figures (a), (b) and (c).

The protocol stack shown in Figure 6 is suitable for L2U2N relay communication, and Embodiment 6 is based on Embodiment 3.

(a) in Figure 6 corresponds to the user plane protocol stack in L2U2N relay communication; (b) in Figure 6 corresponds to the control plane protocol stack in L2U2N relay communication.

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

As an embodiment, the first relay is an L2U2N relay UE communicating between the first node and the MCG.

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

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

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

As an embodiment, there is an RRC connection between the second node in Figure 6 and the first node.

As an embodiment, the second node in Figure 6 corresponds to the second node in this application.

In Embodiment 6, the PC5 interface is the interface between the first node and the first relay, and the protocol entities related to the PC5 interface {PC5-SRAP, PC5-RLC, PC5-MAC, PC5-PHY} are terminated Between the first node and the first relay; the Uu interface is the interface between the UE and the second node, and the protocol entities of the Uu interface terminate at the UE and the second node respectively.

As an embodiment, the first relay is a U2N relay UE, and before performing the first signaling, the first relay provides L2 U2N relay services to the first node.

As an embodiment, the first relay is a U2N relay UE. Before executing the first signaling, the first relay does not provide L2 U2N relay service to the first node. After receiving After the first signaling, the first node uses the U2N relay service provided by the first relay.

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

As an embodiment, the protocol entities {Uu-SRAP, Uu-RLC, Uu-MAC, Uu-PHY} of the Uu interface terminate at the first relay and gNB.

As an embodiment, in (a), the protocol entities {Uu-SDAP, Uu-PDCP} of the Uu interface terminate at the first node and the second node, and the SDAP PDU and PDCP PDU of the first node Use the forwarding of the first relay, but the first relay does not modify the SDAP PDU and the PDCP PDU of the first node, that is to say, the SDAP PDU and the PDCP PDU sent by the first node to the gNB PDCP PDU is transparently transmitted to the first relay.

As an embodiment, in (b), the protocol entities {Uu-RRC, Uu-PDCP} of the Uu interface terminate at the first node and the second node, and the RRC PDU and PDCP PDU of the first node After forwarding by the first relay, but the first relay does not modify the RRC PDU and the PDCP PDU sent by the first node, that is to say, the RRC sent by the first node to the gNB PDU and PDCP PDU is transparently transmitted to the first relay.

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

As an embodiment, in (a), Uu-SDAP corresponds to SDAP 356 in Figure 3, and Uu-PDCP corresponds to PDCP 354 in Figure 3.

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

As an embodiment, in (b), Uu-RRC corresponds to RRC 306 in Figure 3, and Uu-PDCP corresponds to PDCP 304 in Figure 3.

As an embodiment, a cell of the second node in Figure 6 is the PCell of the first relay, and the first relay is in the RRC connected state.

As an embodiment, the first node is in an RRC connection 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, when the first relay forwards the system information of the gNB, the PC5-SRAP layer is not used.

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

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

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

As an embodiment, in Figure 6, 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 Figure 6(b) and received by the Uu-RRC of the first node.

As an embodiment, the first signaling is transparently transmitted to the first relay.

As an embodiment, the transmission of the first signaling does not use the first relay, and the transmission of the first signaling is applicable to Figure 6(c).

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

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

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

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

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

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

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

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

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

As an embodiment, (c) in Figure 6 is a protocol stack when communicating between the first node and the second node when relay is not used.

As an embodiment, (c) in Figure 6 is a protocol stack when communicating between the first node and the second node when no relay is used, that is, when a direct path is used.

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

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

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

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

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

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

As a sub-embodiment of this embodiment, the opposite end RLC entity of the secondary link RLC entity in the first RLC entity set is located on the first relay, corresponding to the PC5-RLC of the first relay.

As an embodiment, the secondary link RLC entity in the first RLC entity set corresponds 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 the PC5-RLC of the first node in (b).

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

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

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

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

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 an embodiment, the first PDCP data PDU of the first PDCP is generated from the Uu-PDCP of the first node in (a) or (b) or (c).

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

As an embodiment, the secondary link 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). road.

Example 7

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

Embodiment 7 further shows a PDCP entity based on Embodiment 3, which is associated with two RLC entities, namely RLC1 and RLC2, where each RLC entity is associated with a different MAC, that is, RLC1 is associated with MAC1, and RLC2 Associated with MAC2.

Embodiment 7 shows the protocol structure on the first node side.

As an embodiment, Figure 7 is applicable to SRBs including SRB1.

As an embodiment, Figure 7 is applicable to DRB.

As an embodiment, Figure 7 is applicable to MRB.

As an embodiment, the protocol structure shown in Figure 7 is a split SRB, that is, split SRB.

As an embodiment, the protocol structure shown in Figure 7 is a split DRB, that is, split DRB.

As an embodiment, Figure 7 is suitable for sending.

As an embodiment, Figure 7 is suitable for reception.

As an embodiment, the first protocol entity in Figure 7 is RRC, and Figure 7 is for SRBs including SRB1.

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

As an embodiment, the PDCP PDU formed by processing the RRC message by the PDCP entity is sent through RLC1.

As an embodiment, the PDCP PDU formed by processing the RRC message by the PDCP entity is sent through RLC2.

As an embodiment, the PDCP PDU formed by processing the RRC message by the PDCP entity is sent through RLC1 or RLC2.

As an example, the RRC message is copied into a PDCP PDU formed by processing by the PDCP entity, and is passed through RLC1 and RLC2 at the same time. send.

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

As an example, the main path of SRB1 is for RLC1.

As an embodiment, the main path of SRB1 is for RLC2.

As an embodiment, the RLC2 and MAC2 are both for secondary link communication.

As an embodiment, the RLC1 and MAC2 are both for primary link communication, that is, not for secondary link communication.

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

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

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

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

Example 8

Embodiment 8 illustrates a schematic diagram of a topology structure according to an embodiment of the present application, as shown in FIG. 8 .

The first node in Embodiment 8 corresponds to the first node in this application.

As an embodiment, the second node in Embodiment 8 corresponds to the second node in this 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 the primary cell of the first node.

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

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

As an embodiment, the second node in Embodiment 8 is a transmission 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 the 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 example, the third node in Embodiment 8 is the L2 U2N 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 L2 U2N relay UE of the first node.

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

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

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

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

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

As an example, the third node in Embodiment 8 is a neighboring 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 Embodiment 8 is a node of TN.

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

As an embodiment, a direct path is a method or transmission path through which the first node and the second node communicate without passing through the third node.

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

As an embodiment, the arrowed lines in Figure 8 represent logical channels.

As an embodiment, the arrowed line in Figure 8 represents the RLC bearer.

As an embodiment, the arrowed line in Figure 8 represents the secondary link RLC channel.

As an embodiment, the thick arrowed line in Figure 8 represents the secondary link RLC channel.

As an example, the thick arrowed line in FIG. 8 represents an indirect path.

As an embodiment, the main link of this application is the link between the first node and the second node, which is represented by a thin line in Figure 8 shows; the secondary link in this application is the link between the first node and the third node, which is represented by a thick line in Figure 8.

As an embodiment, the first RLC entity set includes all RLC entities of the first node used to communicate with the MCG.

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

As an embodiment, when the first RLC entity is a primary link RLC entity, the first node simultaneously uses the primary link RLC entity only when the PDCP of the secondary link RLC entity in the first RLC entity set is activated. The link RLC entity and the secondary link RLC entity send the first PDCP data PDU.

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

As an embodiment, when the first RLC entity is a secondary link RLC entity, the first node simultaneously uses the primary link RLC entity only when the PDCP of the primary link RLC entity in the first RLC entity set is activated. The link RLC entity and the secondary link RLC entity send the first PDCP data PDU.

As an embodiment, the first RLC entity set includes 2 RLC entities.

As an embodiment, the communication interface between the first node and the third node is a PC5 interface, and the first node and the third node communicate through a secondary link.

Example 9

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

Figure 9 shows the mapping relationship between the first bit string and the first RLC entity set, and the mapping relationship between the first RLC entity set and the 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 an example, the N is equal to the N1.

As an example, the N is equal to N1+N2.

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

As an embodiment, the first RLC entity set includes 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 RLC entity set are mapped one-to-one to the N bits of the first bit string.

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

As a sub-embodiment of this embodiment, the first RLC entity set includes N1+N2 RLC entities.

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

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

As a sub-embodiment of this embodiment, RLC entities other than the N1 RLC entities in the first RLC entity set are not mapped to 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 main 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 primary link RLC entities and N2+1 secondary link RLC entities; The first RLC entity is a secondary link RLC entity.

As an embodiment, the first RLC entity set includes N=N1+1 RLC entities, and N2 RLC entities among the N1+1 RLC entities are related to the secondary links in the first logical channel identity list. There is a first mapping relationship between the N2 bits in the first bit string and the N2 RLC entities.

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

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

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

As a sub-embodiment of this embodiment, the first mapping relationship is: the smaller value of the N2 RLC entities according to the associated secondary link RLC channel identity and the N2 value of the first bit string. The higher bits of the N2 bits are mapped, and the larger value of the secondary link RLC channel identity associated with the N2 RLC entities is mapped with the lower bits of the N2 bits of the first bit string.

As a sub-embodiment of this embodiment, the secondary link RLC channel identities associated with the N2 RLC entities have different value sizes.

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

As a sub-embodiment of this embodiment, the secondary link 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: RLC entity (i) in the first RLC entity set maps to bit b _i of the first bit string, and the first RLC The RLC entity (i) in the entity set is associated with the secondary link RLC channel (i); the RLC entity (j) in the first RLC entity set is mapped to bit b _j of the first bit string, and the _The RLC entity (j) in the first RLC entity set is associated with the secondary link RLC channel (j); if i>j, then b _i is higher than ·b j; then b _j is higher than ·b _i The lower bit; where, i, j are any two positive integers in [n, n+N2-1], where n+N2-1 is not greater than N1, and n is a positive integer.

As a sub-embodiment of this embodiment, the first mapping relationship is: RLC entity (i) in the first RLC entity set maps to bit b _i of the first bit string, and the first RLC The RLC entity (i) in the entity set is associated with the secondary link RLC channel (i); the RLC entity (j) in the first RLC entity set is mapped to bit b _j of the first bit string, and the The RLC entity (j) in the first RLC entity set is associated with the secondary link RLC channel (j); if i<j, then b _i is higher relative to ·b _j ; then b _j is higher than ·b _i The lower bit; where, i, j are any two positive integers in [n, n+N2-1], where n+N2-1 is not greater than N1, and n is 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 secondary link 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 x-th byte is a higher bit than any bit of the y-th byte, x<y.

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

As an embodiment, there is a second mapping relationship between N1-N2 bits in the first bit string and 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: RLC entity (i) in the first RLC entity set maps to bit b _i of the first bit string, and the first RLC The RLC entity (i) in the entity set is associated with the secondary link RLC channel (i); the RLC entity (j) in the first RLC entity set is mapped to bit b _j of the first bit string, and the _The RLC entity (j) in the first RLC entity set is associated with the secondary link RLC channel (j); if i>j, then b _i is higher than ·b j; then b _j is higher than ·b _i The lower bit; where i, j are any two positive integers in [n, n+N1-N2-1], where n+N2-1 is not greater than N1, and n is 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 relationship is related to the secondary link RLC channel of the RLC entity in the first RLC entity set; the second mapping relationship is associated with the RLC entity in the first RLC entity set. related to the logical channel identity.

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

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

As a sub-embodiment of this embodiment, the first mapping relationship is: the N2 secondary link RLC entities in the first RLC entity set correspond to the secondary links of the N2 secondary link RLC entities. The size of the channel RLC channel identity value is mapped to the N2 bits of the first bit string, wherein the larger secondary link RLC channel identity value is mapped to the high-order bits of the N2 bits of the first bit string. ; The smaller value of the secondary link RLC channel identity is mapped to the lower bits among the N2 bits of the first bit string.

As a sub-embodiment of this embodiment, the first mapping relationship is: the N2 secondary link RLC entities in the first RLC entity set correspond to the secondary links of the N2 secondary link RLC entities. The size of the channel RLC channel identity value is mapped to the N2 bits of the first bit string, wherein the larger secondary link RLC channel identity value is mapped to the lower bits of the N2 bits of the first bit string. ; The smaller value of the secondary link RLC channel identity is mapped to the high-order bits among the N2 bits of the first bit string.

As a sub-embodiment of this embodiment, the second mapping relationship is: the N1 primary link RLC entities in the first RLC entity set are associated with logical channels according to the N1 secondary link RLC entities. The size of the identity value is mapped to the N1 bits of the first bit string, wherein the larger logical channel identity value is mapped to the lower bits among the N1 bits of the first bit string; the logical channel identity value is The small one is mapped to the high-order bits among the N2 bits of the first bit string.

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

As a sub-embodiment of this embodiment, the codepoint 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 codepoint 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 includes 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 not greater than 3.

As a sub-embodiment of this embodiment, the one-to-one mapping relationship between the second bit string and the X RLC entities in the first RLC entity set is related to the first logical channel identity list. The logical channel identity in

As a sub-embodiment of this embodiment, a value of 0 for bit i in the second bit string indicates deactivation of PDCP replication of the RLC entities in the first RLC entity set mapped to the bit i; A value of 1 for bit i in the second bit string indicates activating PDCP replication of the RLC entities in the first RLC entity set mapped to the bit i.

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 mapped to the The identities of the secondary link RLC channels corresponding to the X secondary link RLC entities are related.

As a sub-embodiment of this embodiment, the secondary link RLC channel identities corresponding to the X secondary link RLC entities in the first RLC entity set are the same as the X secondary link RLC channel identities in the first logical channel identity list. Logical channel identities are associated.

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 mapped to the It is related to the value of the secondary link RLC channel identity corresponding to the X secondary link RLC entities; any two RLC entities among the X secondary link RLC entities in the first RLC entity set, RLC Entityi and RLC Entity j, 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, then relative to the value mapped by the RLC entity j bits in the second bit string, and the RLC entity i is mapped to higher bits in the second bit string.

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

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

As a sub-embodiment of this embodiment, the second bit string includes 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 deactivation of the RLC entities in the first RLC entity set mapped to the bit i; The value of bit i in the two-bit string is 1, indicating that the RLC entity in the first RLC entity set mapped to the bit i is activated.

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 mapped to the It is related to the value of the secondary link RLC channel identity corresponding to the X secondary link RLC entities; any two RLC entities among the X secondary link RLC entities in the first RLC entity set, RLC Entity i and RLC entity j, 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, then relative to the RLC The bits in the second bit string mapped by entity j, the RLC entity i and the higher bits in the second bit string are mapped.

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

As a sub-embodiment of this embodiment, the X RLC entities in the first RLC entity set 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 RLC entity set.

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

As a sub-embodiment of this embodiment, activating an RLC entity in the first RLC entity set means activating a communication or communication link of a candidate relay associated with the RLC entity in the first RLC entity set. road.

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

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

As a sub-embodiment of this embodiment, the serving cell of the first node indicates the secondary link RLC channel identity of any secondary link RLC entity in the first RLC entity set, and the first RLC entity set The secondary link RLC channel identity of any secondary link RLC entity belongs to the first secondary link RLC channel identity set.

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

Example 10

Embodiment 10 illustrates that the first signaling according to an embodiment of the present application is used to indicate activation of any one of the first RLC entity set associated with the logical channel identity on the secondary link in the first logical channel identity list A schematic diagram of PDCP replication of an RLC entity is shown in Figure 10.

As an embodiment, the meaning of the sentence "any RLC entity in the first RLC entity set is associated with the logical channel identity on the secondary link in the first logical channel identity list" is: Any secondary link RLC entity.

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

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

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

Example 11

Embodiment 11 illustrates that the second signaling according to an embodiment of the present application is only used to indicate activation or deactivation of other than the first RLC entity in the first RLC entity set and the main chain in the first logical channel identity list. A schematic diagram of PDCP replication of RLC entities associated with the road is shown in Figure 11.

As an embodiment, the sentence second signaling is only used to indicate activation or deactivation of RLC entities other than the first RLC entity in the first RLC entity set that are associated with the primary link in the first logical channel identity list. The meaning of PDCP replication includes: PDCP replication of secondary link RLC entities in the first RLC entity set does not use the second signaling to activate or deactivate.

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

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

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

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

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

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

As an embodiment, the sentence second signaling is only used to indicate activation or deactivation of RLC entities other than the first RLC entity in the first RLC entity set that are associated with the primary link in the first logical channel identity list. The meaning of PDCP replication includes: activation or deactivation of PDCP replication of secondary link RLC entities 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 MAC CE, and the MAC CE is different from the logical channel identity corresponding to the second signaling.

Example 12

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

As an embodiment, the logical channel identity in the first RLC entity set is neither among the N2 RLC entities nor in the first logical channel identity list associated with the first RLC entity. The size of the value 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 of the N1+1 RLC entities The RLC entities do not include the RLC entities among the N2 RLC entities, nor the first RLC entity; the logical channel identities in the first logical channel identity list associated with the N1-N2 RLC entities are The size of the value 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 main link RLC entities.

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

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

As an example, N2 is greater than 1.

Example 13

Embodiment 13 illustrates a schematic diagram in which the secondary link RLC channel identities associated with N2 RLC entities are used to determine the first mapping relationship according to an embodiment of the present application, as shown in FIG. 13 .

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

As an embodiment, any RLC entity among the N2 RLC entities is associated with a secondary link RLC channel identity.

As an embodiment, the first signaling indicates the secondary link RLC channel identity of any one of the N2 RLC entities.

As an example, N2 is greater than 1.

As an embodiment, for any two RLC entities among the N2 RLC entities, RLC entity i and RLC entity j, RLC entity i is associated with the secondary link RLC channel i; RLC entity j is associated with the secondary link RLC channel j is associated; if the value of the secondary link RLC channel i is greater than the value of the secondary link RLC channel j, then relative to the bits mapped to the RLC entity j in the first bit string, the The bits in the first bit string mapped to the RLC entity i are higher bits.

As an embodiment, for any two RLC entities among the N2 RLC entities, RLC entity i and RLC entity j, RLC entity i is associated with the secondary link RLC channel i; RLC entity j is associated with the secondary link RLC channel j is associated; if the value of the secondary link RLC channel i is greater than the value of the secondary link RLC channel j, then relative to the bits mapped to the RLC entity j in the second bit string, the The bits in the second bit string mapped to the RLC entity i are higher bits.

As an embodiment, the primary link RLC entity in the first RLC entity set is not associated with any secondary link RLC channel.

As an embodiment, a UE has up to 512 secondary link RLC channels.

As an embodiment, a UE has at most 63 or 64 logical channel identities on the secondary link.

As an example, a UE may have 63 or 64 logical channel identities on the primary link.

As an example, a UE may also have 255 or 256 1-byte extended logical channel identities on the primary link.

As an example, a UE may also have 65535 or 65536 2-byte extended logical channel identities on the primary link.

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 secondary link RLC channel of a UE is used for communication with all other UEs. The secondary link is not used when communicating with different UEs. The logical channels for communicating with different UEs may be the same or different. The secondary link RLC channels for communication are different.

As a sub-embodiment of this embodiment, communication with all other UEs includes communication between UEs and communication between UEs and the network through relays.

As an embodiment, when a UE performs secondary link communication with other UEs, the logical channel identities associated with different secondary link RLC channels may be the same or different.

As an embodiment, the logical channel identity on the main link of a UE is for a cell group.

As an embodiment, a UE has different logical channel identities for the same cell group.

As an embodiment, the logical channel identity on the secondary link of a UE may be the same as or different from the logical channel identity on the primary link.

Example 14

Embodiment 14 illustrates a structural block diagram of a processing device used in a first node according to an embodiment of the present application; as shown in FIG. 14 . In Figure 14, the processing device 1400 in the first node includes a first receiver 1401 and a first transmitter 1402. In Example 14,

The first receiver 1401 receives the first signaling, which is used to configure the first PDCP entity and the first RLC entity set; the first RLC entity set includes at least one secondary link RLC entity and a Main link RLC entity; any RLC entity in the first RLC entity set is associated with the first PDCP entity; the main path of the first PDCP entity is associated with the first RLC in the first RLC entity set Entity related;

The first receiver 1401 receives second signaling, where the second signaling includes a first bit string, and the N1 bits of the first bit string are identical to the first bits in the first RLC entity set. There is a one-to-one mapping relationship for N1 RLC entities other than the RLC entity; the first bit string is used to indicate activation or deactivation of PDCP replication of the RLC entity in the first RLC entity set;

The first transmitter 1402 sends the first PDCP data PDU of the first PDCP entity; the action of sending the first PDCP data PDU of the first PDCP entity includes: copying the first PDCP data PDU of the first PDCP entity. PDCP data PDU and submit the copied copies to the RLC entities whose PDCP replication is activated in the first RLC entity set;

As an embodiment, the first RLC entity set includes N1+1 RLC entities, and N2 RLCs among the N1+1 RLC entities The entity is associated with the logical channel identity on the secondary link in the first logical channel identity list; there is a first mapping relationship between the N2 bits in the first bit string and the N2 RLC entities; the third There is a second mapping relationship between N1-N2 bits in a bit string and the N2 RLC entities in the first RLC entity set and RLC entities other than the first RLC entity; the first RLC entity set The value size of the logical channel identity in the first logical channel identity list associated with the N2 RLC entities and RLC entities other than the first RLC entity is used to determine the second mapping relationship;

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 indicate activation or deactivation of all secondary links in the first logical channel identity list. PDCP replication of the RLC entities in the first RLC entity set associated with the logical channel identity;

As an embodiment, the first receiver 1401 receives third signaling, and the third signaling is used to indicate activation or deactivation of PDCP replication of the first PDCP entity;

The first transmitter 1402 sends the second PDCP data PDU of the first PDCP entity. The action of sending the second PDCP data PDU of the first PDCP entity includes: converting the second PDCP data PDU of the first PDCP entity. The second PDCP data PDU is submitted to any one of the first RLC entity or the 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 that supports 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 ship.

As an embodiment, the first node is a mobile phone or a vehicle-mounted 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 that supports low-latency and high-reliability transmission.

As an embodiment, the first node is a secondary link communication node.

As an embodiment, the first receiver 1401 includes the antenna 452, receiver 454, receiving processor 456, multi-antenna receiving processor 458, controller/processor 459, memory 460, or data source in Embodiment 4. At least one of 467.

As an embodiment, the first transmitter 1402 includes the antenna 452, transmitter 454, transmit processor 468, multi-antenna transmit processor 457, controller/processor 459, memory 460, or data source in Embodiment 4. At least one of 467.

Example 15

Embodiment 15 illustrates a structural block diagram of a processing device used in a second node according to an embodiment of the present application; as shown in FIG. 15 . In Figure 15, the processing device 1500 in the second node includes a second receiver 1502 and a second transmitter 1501. In Example 15,

The second transmitter 1501 sends first signaling, which is used to configure the first PDCP entity and the first RLC entity set; the first RLC entity set includes at least one secondary link RLC entity and a Main link RLC entity; the first RLC entity set Any RLC entity in is associated with the first PDCP entity; the main path of the first PDCP entity is associated with the first RLC entity in the first RLC entity set;

The second transmitter 1501 sends second signaling, where the second signaling includes a first bit string, and the N1 bits of the first bit string are identical to the first bit in the first RLC entity set. There is a one-to-one mapping relationship for N1 RLC entities other than the RLC entity; the first bit string is used to indicate activation or deactivation of PDCP replication of the RLC entity in the first RLC entity set;

The second receiver 1502 receives the first PDCP data PDU of the first PDCP entity; the behavior of receiving the first PDCP data PDU of the first PDCP entity includes: copying the PDCP data PDU from the first RLC entity set. receiving a copy of the first PDCP data PDU of the first PDCP entity on the peer RLC entity of at least one of the activated RLC entities;

As an embodiment, the second transmitter 1501 sends third signaling, which is used to indicate activation or deactivation of all secondary links in the first logical channel identity list. PDCP replication of the RLC entities in the first RLC entity set associated with the logical channel identity;

As an embodiment, the second transmitter 1501 sends third signaling, and the third signaling is used to indicate activation or deactivation of PDCP replication of the first PDCP entity;

The second receiver 1502 receives the second PDCP data PDU of the first PDCP entity, and the action of receiving the second PDCP data PDU of the first PDCP entity includes: receiving the second PDCP data PDU of the first PDCP entity from the first RLC entity or the third Receive the second PDCP data PDU on one of the peer entities in the RLC entity;

Wherein, the split slave path of the first PDCP entity is associated with the third RLC entity in the first RLC entity set; both the first RLC entity and the third RLC entity are used to communicate with MCG Communication; one of the first RLC entity and the third RLC entity is associated with a logical channel identity on the main link in the first logical channel identity list, and the other one is associated with the first logical channel identity Logical channel identities on the secondary links in the list are associated; at least one of the first signaling and the third signaling is used to implicitly indicate the The first PDCP entity is split from the path.

As an embodiment, the second node is a satellite.

As an embodiment, the second node is U2N Relay UE (user equipment).

As an 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 node that supports multicast.

As an embodiment, 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 Embodiment 4. one.

As an embodiment, the second receiver 1502 includes at least one of the antenna 420, the receiver 418, the receiving processor 470, the multi-antenna receiving processor 472, the controller/processor 475, and the memory 476 in Embodiment 4. one.

Those of ordinary skill in the art can understand that all or part of the steps in the above method can be completed by instructing relevant hardware through a program, and the program can be stored in a computer-readable storage medium, such as a read-only memory, a hard disk or an optical disk. Optionally, all or part of the steps of the above embodiments can also be implemented using one or more integrated circuits. Correspondingly, each module unit in the above embodiments can be implemented in the form of hardware or in the form of software function modules. This application is not limited to any specific form of combination of software and hardware. User equipment, terminals and UEs in this application include but are not limited to drones, communication modules on drones, remote control aircraft, aircraft, small aircraft, mobile phones, tablets, notebooks, vehicle-mounted communication equipment, wireless sensors, Internet cards, Internet of Things terminals, RFID terminals, NB-IoT terminals, MTC (Machine Type Communication) terminals, eMTC (enhancedMTC, enhanced MTC) terminals, data cards, Internet cards, vehicle-mounted communication equipment, low-cost mobile phones, low-cost Tablet computers, satellite communication equipment, ship communication equipment, NTN user equipment and other wireless communication equipment. The base station or system equipment in this application includes but is not limited to macro cell base station, micro cell base station, home base station, relay base station, gNB (NR Node B) NR Node B, TRP (Transmitter Receiver Point, sending and receiving node), NTN base station , satellite equipment, flight platform equipment and other wireless communication equipment.

The invention may be embodied in other specified forms without departing from its core or essential characteristics. Accordingly, the presently disclosed embodiments are to be regarded in any way as illustrative rather than restrictive. The scope of the invention is determined by the appended claims rather than the foregoing description, and all modifications within the meaning and range of equivalents are deemed to be included therein.

Claims

A first node used for wireless communication, which includes:

The first receiver receives first signaling, which is used to configure a first PDCP entity and a first set of RLC entities; the first set of RLC entities includes at least one secondary link RLC entity and a primary Link RLC entity; any RLC entity in the first RLC entity set is associated with the first PDCP entity; the main path of the first PDCP entity is associated with the first RLC entity in the first RLC entity set Associated;

The first receiver receives second signaling, the second signaling includes a first bit string, and the N1 bits of the first bit string are consistent with the first RLC in the first RLC entity set. There is a one-to-one mapping relationship for N1 RLC entities other than the entity; the first bit string is used to indicate activation or deactivation of PDCP replication of the RLC entity in the first RLC entity set;

The first transmitter sends the first PDCP data PDU of the first PDCP entity; the action of sending the first PDCP data PDU of the first PDCP entity includes: copying the first PDCP data of the first PDCP entity. Data PDU and submit the copied copies to the RLC entities whose PDCP replication is activated in the first RLC entity set;

Wherein, the N1 is a positive integer, any RLC entity in the first RLC entity set is associated with a logical channel identity in the first logical channel identity list; the first bit string is associated with the first RLC entity The one-to-one mapping relationship existing among N1 RLC entities other than the first RLC entity in the set is related to the logical channel identity on the main link in the first logical channel identity list, and the first The one-to-one mapping relationship between the bit string and the N1 RLC entities other than the first RLC entity in the first RLC entity set and the logical channel on the secondary link in the first logical channel identity list Identity is irrelevant.
The first node according to claim 1, characterized in that,

The first signaling is used to indicate activating PDCP replication of any RLC entity in the first set of RLC entities associated with a logical channel identity on a secondary link in the first logical channel identity list; The second signaling is only used to indicate activation or deactivation of RLC entities other than the first RLC entity in the first RLC entity set that are associated with the primary link in the first logical channel identity list. PDCP copy; the lowest bit in the first bit string is mapped to the second RLC entity, and the second RLC entity belongs to the first RLC entity set; the second RLC entity is mapped to the first logical channel identity Associated; the smallest logical channel identity on the main link in the first logical channel identity list associated with an RLC entity other than the first RLC entity in the first RLC entity set. The logical channel identity is the first logical channel identity;

Wherein, any RLC entity in the first RLC entity set is used for communication with the MCG.
The first node according to claim 1, characterized in that,

The first set of RLC entities includes N1+1 RLC entities, and N2 RLC entities among the N1+1 RLC entities are associated with logical channel identities on the secondary links in the first logical channel identity list. ; There is a first mapping relationship between the N2 bits in the first bit string and the N2 RLC entities; the N1-N2 bits in the first bit string and the N2 bits in the first RLC entity set; There is a second mapping relationship between N2 RLC entities and RLC entities other than the first RLC entity; the N2 RLC entities in the first RLC entity set are associated with RLC entities other than the first RLC entity. The value size of the logical channel identity in the first logical channel identity list is used to determine the second mapping relationship;

Wherein, the N2 bits in the first bit string are different from the N1-N2 bits, the N2 is a positive integer not greater than the N1, the first mapping relationship and the second mapping Relationships are all mapped one-to-one.
The first node according to claim 3, characterized in that,

The secondary link RLC channel identities associated with the N2 RLC entities are used to determine the first mapping relationship.
The first node according to claim 3 or 4, characterized in that,

The N2 bits of the first bit string are continuous; the N1-N2 bits of the first bit string are continuous.
The first node according to claim 3 or 4 or 5, characterized in that,

The N2 bits of the first bit string are higher bits relative to the N1-N2 bits of the first bit string, or the N2 bits of the first bit string are higher bits relative to the N1-N2 bits of the first bit string. The lower bits of the N1-N2 bits of the first bit string.
The first node according to any one of claims 1 to 6, characterized in that it includes:

The first receiver receives third signaling, and the third signaling is used to indicate activation or deactivation of all logical channel identities associated with the secondary link in the first logical channel identity list. PDCP replication of the RLC entities in the first RLC entity set;

Wherein, the logical channel identity in the first logical channel identity list associated with the first RLC entity is a logical channel identity on the main link.
The first node according to any one of claims 1 to 6, characterized in that it includes:

The first receiver receives third signaling, where the third signaling is used to indicate activation or deactivation of PDCP replication of the first PDCP entity;

The first transmitter sends a second PDCP data PDU of the first PDCP entity, and the action of sending the second PDCP data PDU of the first PDCP entity includes: converting the first PDCP data PDU of the first PDCP entity. The second PDCP data PDU is submitted to any one of the first RLC entity or the third RLC entity;

Wherein, the split slave path of the first PDCP entity is associated with the third RLC entity in the first RLC entity set; both the first RLC entity and the third RLC entity are used to communicate with MCG Communication; one of the first RLC entity and the third RLC entity is associated with a logical channel identity on the main link in the first logical channel identity list, and the other one is associated with the first logical channel identity Logical channel identities on the secondary links in the list are associated; 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.
The first node according to any one of claims 1 to 8, characterized in that,

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.
A second node used for wireless communication, which includes:

The second transmitter sends first signaling. The first signaling is used to configure the first PDCP entity and the first RLC entity set. The first RLC entity set includes at least one secondary link RLC entity and a primary link RLC entity. Link RLC entity; any RLC entity in the first RLC entity set is associated with the first PDCP entity; the main path of the first PDCP entity is associated with the first RLC entity in the first RLC entity set Associated;

The second transmitter sends second signaling, the second signaling includes a first bit string, and the N1 bits of the first bit string are consistent with the first RLC in the first RLC entity set. There is a one-to-one mapping relationship for N1 RLC entities other than the entity; the first bit string is used to indicate activation or deactivation of PDCP replication of the RLC entity in the first RLC entity set;

The second receiver receives the first PDCP data PDU of the first PDCP entity; the action of receiving the first PDCP data PDU of the first PDCP entity includes: PDCP replication is activated from the first RLC entity set. The peer RLC entity of at least one of the RLC entities receives a copy of the first PDCP data PDU of the first PDCP entity;

Wherein, the N1 is a positive integer, any RLC entity in the first RLC entity set is associated with a logical channel identity in the first logical channel identity list; the first bit string is associated with the first RLC entity The one-to-one mapping relationship existing among N1 RLC entities other than the first RLC entity in the set is related to the logical channel identity on the main link in the first logical channel identity list, and the first The one-to-one mapping relationship between the bit string and the N1 RLC entities other than the first RLC entity in the first RLC entity set and the logical channel on the secondary link in the first logical channel identity list Identity is irrelevant.
The second node according to claim 10, characterized in that,

The first signaling is used to indicate activating PDCP replication of any RLC entity in the first set of RLC entities associated with a logical channel identity on a secondary link in the first logical channel identity list; The second signaling is only used to indicate activation or deactivation of RLC entities other than the first RLC entity in the first RLC entity set that are associated with the primary link in the first logical channel identity list. PDCP copy; the lowest bit in the first bit string is mapped to the second RLC entity, and the second RLC entity belongs to the first RLC entity set; the second RLC entity is mapped to the first logical channel identity Associated; the smallest logical channel identity on the main link in the first logical channel identity list associated with an RLC entity other than the first RLC entity in the first RLC entity set. The logical channel identity is the first logical channel identity;

Wherein, any RLC entity in the first RLC entity set is used for communication with the MCG.
The second node according to claim 10, characterized in that,

The first set of RLC entities includes N1+1 RLC entities, and N2 RLC entities among the N1+1 RLC entities are associated with logical channel identities on the secondary links in the first logical channel identity list. ; There is a first mapping relationship between the N2 bits in the first bit string and the N2 RLC entities; the N1-N2 bits in the first bit string and the N2 bits in the first RLC entity set; There is a second mapping relationship between N2 RLC entities and RLC entities other than the first RLC entity; the N2 RLC entities in the first RLC entity set are associated with RLC entities other than the first RLC entity. The value size of the logical channel identity in the first logical channel identity list is used to determine the second mapping relationship;

Wherein, the N2 bits in the first bit string are different from the N1-N2 bits, and the N2 is a positive number that is not greater than the N1. Integer, the first mapping relationship and the second mapping relationship are both one-to-one mapping.
The second node according to claim 12, characterized in that,

The secondary link RLC channel identities associated with the N2 RLC entities are used to determine the first mapping relationship.
The second node according to claim 12 or 13, characterized in that,

The N2 bits of the first bit string are continuous; the N1-N2 bits of the first bit string are continuous.
The second node according to claim 12 or 13 or 14, characterized in that,

The N2 bits of the first bit string are higher bits relative to the N1-N2 bits of the first bit string, or the N2 bits of the first bit string are higher bits relative to the N1-N2 bits of the first bit string. The lower bits of the N1-N2 bits of the first bit string.
The second node according to any one of claims 10 to 15, characterized in that it includes:

The second transmitter sends third signaling, the third signaling being used to indicate activation or deactivation of all logical channel identities associated with the secondary link in the first logical channel identity list. PDCP replication of the RLC entities in the first RLC entity set;

Wherein, the logical channel identity in the first logical channel identity list associated with the first RLC entity is a logical channel identity on the main link.
The second node according to any one of claims 10 to 15, characterized in that it includes:

The second transmitter sends third signaling, where the third signaling is used to indicate activation or deactivation of PDCP replication of the first PDCP entity;

The second receiver receives the second PDCP data PDU of the first PDCP entity; the action of receiving the second PDCP data PDU of the first PDCP entity includes: receiving the second PDCP data PDU of the first PDCP entity from the first RLC entity or the third RLC Receive the second PDCP data PDU on one of the counterpart entities;

Wherein, the split slave path of the first PDCP entity is associated with the third RLC entity in the first RLC entity set; both the first RLC entity and the third RLC entity are used to communicate with MCG Communication; one of the first RLC entity and the third RLC entity is associated with a logical channel identity on the main link in the first logical channel identity list, and the other one is associated with the first logical channel identity Logical channel identities on the secondary links in the list are associated; 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.
The second node according to any one of claims 10 to 17, characterized in that,

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.
A method used in a first node for wireless communication, comprising:

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

Receive second signaling, the second signaling including a first bit string, N1 bits of the first bit string and N1 RLC entities other than the first RLC entity in the first RLC entity set There is a one-to-one mapping relationship; the first bit string is used to indicate activation or deactivation of PDCP replication of the RLC entities in the first RLC entity set;

Send the first PDCP data PDU of the first PDCP entity; the act of sending the first PDCP data PDU of the first PDCP entity includes: copying the first PDCP data PDU of the first PDCP entity and copying the first PDCP data PDU of the first PDCP entity. The copies are respectively submitted to the RLC entities whose PDCP replication is activated in the first RLC entity set;

Wherein, the N1 is a positive integer, any RLC entity in the first RLC entity set is associated with a logical channel identity in the first logical channel identity list; the first bit string is associated with the first RLC entity The one-to-one mapping relationship existing among N1 RLC entities other than the first RLC entity in the set is related to the logical channel identity on the main link in the first logical channel identity list, and the first The one-to-one mapping relationship between the bit string and the N1 RLC entities other than the first RLC entity in the first RLC entity set and the logical channel on the secondary link in the first logical channel identity list Identity is irrelevant.
The method in the first node according to claim 19, characterized in that:

The first signaling is used to indicate activating PDCP replication of any RLC entity in the first set of RLC entities associated with a logical channel identity on a secondary link in the first logical channel identity list; The second signaling is only used to indicate activation or deactivation of RLC entities other than the first RLC entity in the first RLC entity set that are associated with the primary link in the first logical channel identity list. PDCP copy; the lowest bit in the first bit string is mapped to the second RLC entity, and the second RLC entity belongs to the first RLC entity set; the second RLC entity is associated with the first logical channel identity; the primary RLC entity in the first RLC entity set is associated with the first logical channel identity list other than the first RLC entity. The logical channel identity with the smallest value among the logical channel identities on the link is the first logical channel identity;

Wherein, any RLC entity in the first RLC entity set is used for communication with the MCG.
The method in the first node according to claim 19, characterized in that:

The first set of RLC entities includes N1+1 RLC entities, and N2 RLC entities among the N1+1 RLC entities are associated with logical channel identities on the secondary links in the first logical channel identity list. ; There is a first mapping relationship between the N2 bits in the first bit string and the N2 RLC entities; the N1-N2 bits in the first bit string and the N2 bits in the first RLC entity set; There is a second mapping relationship between N2 RLC entities and RLC entities other than the first RLC entity; the N2 RLC entities in the first RLC entity set are associated with RLC entities other than the first RLC entity. The value size of the logical channel identity in the first logical channel identity list is used to determine the second mapping relationship;

Wherein, the N2 bits in the first bit string are different from the N1-N2 bits, the N2 is a positive integer not greater than the N1, the first mapping relationship and the second mapping Relationships are all mapped one-to-one.
The method in the first node according to claim 21, characterized in that:

The secondary link RLC channel identities associated with the N2 RLC entities are used to determine the first mapping relationship.
The method in the first node according to claim 21 or 22, characterized in that:

The N2 bits of the first bit string are continuous; the N1-N2 bits of the first bit string are continuous.
The method in the first node according to claim 21 or 22 or 23, characterized in that,

The N2 bits of the first bit string are higher bits relative to the N1-N2 bits of the first bit string, or the N2 bits of the first bit string are higher bits relative to the N1-N2 bits of the first bit string. The lower bits of the N1-N2 bits of the first bit string.
The method in the first node according to any one of claims 19 to 24, characterized in that it includes:

Receive third signaling, the third signaling being used to indicate activation or deactivation of all the first RLC entity sets associated with logical channel identities on the secondary links in the first logical channel identity list PDCP replication of RLC entities in;

Wherein, the logical channel identity in the first logical channel identity list associated with the first RLC entity is a logical channel identity on the main link.
The method in the first node according to any one of claims 19 to 24, characterized in that it includes:

Receive third signaling, the third signaling being used to indicate activation or deactivation of PDCP replication of the first PDCP entity;

Send the second PDCP data PDU of the first PDCP entity. The act of sending the second PDCP data PDU of the first PDCP entity includes: submitting the second PDCP data PDU of the first PDCP entity to the Any one of the first RLC entity or the third RLC entity;

Wherein, the split slave path of the first PDCP entity is associated with the third RLC entity in the first RLC entity set; both the first RLC entity and the third RLC entity are used to communicate with MCG Communication; one of the first RLC entity and the third RLC entity is associated with a logical channel identity on the main link in the first logical channel identity list, and the other one is associated with the first logical channel identity Logical channel identities on the secondary links in the list are associated; 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.
The method in the first node according to any one of claims 18 to 26, characterized in that:

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.
A method used in a second node for wireless communication, including:

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

Send second signaling, the second signaling including a first bit string, N1 bits of the first bit string and N1 RLC entities other than the first RLC entity in the first RLC entity set There is a one-to-one mapping relationship; the first bit string is used to indicate activation or deactivation of PDCP replication of the RLC entities in the first RLC entity set;

Receive the first PDCP data PDU of the first PDCP entity; the act of receiving the first PDCP data PDU of the first PDCP entity includes: PDCP copying the activated RLC entity from the first RLC entity set. On the peer RLC entity of at least one RLC entity receiving a copy of the first PDCP data PDU of the first PDCP entity;

Wherein, the N1 is a positive integer, any RLC entity in the first RLC entity set is associated with a logical channel identity in the first logical channel identity list; the first bit string is associated with the first RLC entity The one-to-one mapping relationship existing among N1 RLC entities other than the first RLC entity in the set is related to the logical channel identity on the main link in the first logical channel identity list, and the first The one-to-one mapping relationship between the bit string and the N1 RLC entities other than the first RLC entity in the first RLC entity set and the logical channel on the secondary link in the first logical channel identity list Identity is irrelevant.
The method in the second node according to claim 28, characterized in that:

The first signaling is used to indicate activating PDCP replication of any RLC entity in the first set of RLC entities associated with a logical channel identity on a secondary link in the first logical channel identity list; The second signaling is only used to indicate activation or deactivation of RLC entities other than the first RLC entity in the first RLC entity set that are associated with the primary link in the first logical channel identity list. PDCP copy; the lowest bit in the first bit string is mapped to the second RLC entity, and the second RLC entity belongs to the first RLC entity set; the second RLC entity is mapped to the first logical channel identity Associated; the smallest logical channel identity on the main link in the first logical channel identity list associated with an RLC entity other than the first RLC entity in the first RLC entity set. The logical channel identity is the first logical channel identity;

Wherein, any RLC entity in the first RLC entity set is used for communication with the MCG.
The method in the second node according to claim 28, characterized in that:

The first set of RLC entities includes N1+1 RLC entities, and N2 RLC entities among the N1+1 RLC entities are associated with logical channel identities on the secondary links in the first logical channel identity list. ; There is a first mapping relationship between the N2 bits in the first bit string and the N2 RLC entities; the N1-N2 bits in the first bit string and the N2 bits in the first RLC entity set; There is a second mapping relationship between N2 RLC entities and RLC entities other than the first RLC entity; the N2 RLC entities in the first RLC entity set are associated with RLC entities other than the first RLC entity. The value size of the logical channel identity in the first logical channel identity list is used to determine the second mapping relationship;

Wherein, the N2 bits in the first bit string are different from the N1-N2 bits, the N2 is a positive integer not greater than the N1, the first mapping relationship and the second mapping Relationships are all mapped one-to-one.
The method in the second node according to claim 30, characterized in that:

The secondary link RLC channel identities associated with the N2 RLC entities are used to determine the first mapping relationship.
The method in the second node according to claim 30 or 31, characterized in that:

The N2 bits of the first bit string are continuous; the N1-N2 bits of the first bit string are continuous.
The method in the second node according to claim 30 or 31 or 32, characterized in that,

The N2 bits of the first bit string are higher bits relative to the N1-N2 bits of the first bit string, or the N2 bits of the first bit string are higher bits relative to the N1-N2 bits of the first bit string. The lower bits of the N1-N2 bits of the first bit string.
The method in the second node according to any one of claims 28 to 33, characterized in that it includes:

The second transmitter sends third signaling, the third signaling being used to indicate activation or deactivation of all logical channel identities associated with the secondary link in the first logical channel identity list. PDCP replication of the RLC entities in the first RLC entity set;

Wherein, the logical channel identity in the first logical channel identity list associated with the first RLC entity is a logical channel identity on the main link.
The method in the second node according to any one of claims 28 to 33, characterized in that it includes:

The second transmitter sends third signaling, where the third signaling is used to indicate activation or deactivation of PDCP replication of the first PDCP entity;

The second receiver receives the second PDCP data PDU of the first PDCP entity; the action of receiving the second PDCP data PDU of the first PDCP entity includes: receiving the second PDCP data PDU of the first PDCP entity from the first RLC entity or the third RLC Receive the second PDCP data PDU on one of the counterpart entities;

Wherein, the split slave path of the first PDCP entity is associated with the third RLC entity in the first RLC entity set; both the first RLC entity and the third RLC entity are used to communicate with MCG Communication; one of the first RLC entity and the third RLC entity is associated with a logical channel identity on the main link in the first logical channel identity list, and the other one is associated with the first logical channel identity Logical channel identities on the secondary links in the list are associated; at least one of the first signaling and the third signaling is used to implicitly indicate the The first PDCP entity is split from the path.
The method in the second node according to any one of claims 28 to 35, characterized in that:

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.