CN116156673A - Link configuration method and equipment - Google Patents

Link configuration method and equipment Download PDF

Info

Publication number
CN116156673A
CN116156673A CN202111386186.5A CN202111386186A CN116156673A CN 116156673 A CN116156673 A CN 116156673A CN 202111386186 A CN202111386186 A CN 202111386186A CN 116156673 A CN116156673 A CN 116156673A
Authority
CN
China
Prior art keywords
rlc
link
entity
pdcp
rlc entities
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202111386186.5A
Other languages
Chinese (zh)
Inventor
黄学艳
刘亮
韩星宇
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
China Mobile Communications Group Co Ltd
China Mobile Communications Ltd Research Institute
Original Assignee
China Mobile Communications Group Co Ltd
China Mobile Communications Ltd Research Institute
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by China Mobile Communications Group Co Ltd, China Mobile Communications Ltd Research Institute filed Critical China Mobile Communications Group Co Ltd
Priority to CN202111386186.5A priority Critical patent/CN116156673A/en
Publication of CN116156673A publication Critical patent/CN116156673A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/10Connection setup
    • H04W76/15Setup of multiple wireless link connections
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/10Connection setup
    • H04W76/11Allocation or use of connection identifiers
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W88/00Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02Terminal devices
    • H04W88/04Terminal devices adapted for relaying to or from another terminal or user

Abstract

The invention provides a link configuration method and related equipment, and relates to the field of communication, wherein the link configuration method comprises the following steps: transmitting packet data convergence protocol PDCP configuration information to a terminal; the PDCP configuration information includes link indication information for indicating that a PDCP entity is connected to at least two radio link control RLC entities including at least one PC5RLC entity. In the embodiment of the invention, the PDCP entity is indicated to be connected with at least two Radio Link Control (RLC) entities including the PC5RLC entity in the PDCP configuration information, and in the PC5 scene, the PDCP entity can carry out data transmission through the at least two RLC entities, so that the transmission efficiency or the transmission reliability of communication data can be improved.

Description

Link configuration method and equipment
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a link configuration method and device.
Background
The Sidelink RELAY (SL RELAY) refers to a technology in which a mobile terminal (or may also be referred to as a remote terminal, remote UE) establishes a PC5 (Proximity Service communication, near-end communication) connection with another terminal (or may also be referred to as a RELAY terminal, RELAY UE), and then uses the terminal (RELAY UE) as a RELAY access network.
In the existing SL RELAY technology, a remote UE may choose to access a single RELAY UE (establish a PC5 link) or access a RAN (establish a uu link) through an air interface based on a certain decision condition, and in this connection manner of a single link, the efficiency or reliability of data transmission is low.
Disclosure of Invention
The embodiment of the invention provides a link configuration method and related equipment, which are used for solving the problem of low data transmission efficiency or reliability in the existing SL RELAY technology.
In order to solve the technical problems, the invention is realized as follows:
in a first aspect, an embodiment of the present invention provides a link configuration method, applied to a network device, where the method includes:
transmitting packet data convergence protocol PDCP configuration information to a terminal;
the PDCP configuration information includes link indication information for indicating that a PDCP entity is connected to at least two radio link control RLC entities including at least one PC5 RLC entity.
Optionally, the at least two RLC entities include a uu RLC entity and at least one PC5 RLC entity; or alternatively
The at least two RLC entities include at least two PC5 RLC entities.
Optionally, in the case that the at least two RLC entities include a uu RLC entity and at least one PC5 RLC entity, the link indication information includes uu RLC indication information and at least one PC5 RLC indication information, which are respectively used to indicate that the PDCP entity connects the uu RLC entity and the at least one PC5 RLC entity;
Alternatively, in case that the at least two RLC entities include at least two PC5 RLC entities, the link indication information includes at least two PC5 RLC indication information for indicating that the PDCP entity connects the at least two PC5 RLC entities.
Optionally, the PC5 RLC indication information carries relay UE identification information and logical channel LCH identification information.
Optionally, the PDCP configuration information is configured through RRC reconfiguration signaling.
Optionally, in the case that the at least two RLC entities include a uu RLC entity and at least one PC5 RLC entity, the PDCP configuration information is further configured to configure a uu link as a main path, where the uu link is established by connecting the uu RLC entity with the PDCP entity;
or in the case that the at least two RLC entities include at least two PC5 RLC entities, the PDCP configuration information is further configured to configure a first PC5 link as a primary path, the first PC5 link being one of the at least two PC5 links, wherein the at least two PC5 links are established by connecting the at least two PC5 RLC entities through the PDCP entity.
Optionally, in a case where one target PC5 link exists in the at least two PC5 links, the first PC5 link is the target PC5 link;
In the case where there are multiple target PC5 links for the at least two PC5 links, the first PC5 link is one of the multiple target PC5 links;
when the at least two PC5 links do not have the target PC5 link, the first PC5 link is determined by the network equipment according to the load condition of each relay UE corresponding to the at least two PC5 links and/or the uu link condition of each corresponding relay UE;
wherein the RLC of the relay UE to which the target PC5 link is connected belongs to the primary cell group.
Optionally, the PDCP configuration includes a bearer separation threshold, where the bearer separation threshold is used to enable the terminal to perform uplink data splitting when the uplink data amount is greater than or equal to the bearer separation threshold.
Optionally, the PDCP configuration further includes a bearer duplication indication.
Optionally, in the case that the at least two RLC entities include a uu RLC entity and at least one PC5 RLC entity, the bearer duplication indication is used to indicate a uu link and a PC5 link bearer duplication;
alternatively, in case the at least two RLC entities comprise at least two PC5 RLC entities, the bearer duplication indication is used to indicate at least two PC5 link bearer duplication.
In a second aspect, an embodiment of the present invention provides a link configuration method, applied to a terminal, where the method includes:
receiving PDCP configuration information sent by network equipment;
the PDCP configuration information comprises link indication information, wherein the link indication information is used for indicating a PDCP entity to be connected with at least two wireless link control (RLC) entities, and the at least two RLC entities comprise at least one PC5 RLC entity;
and establishing multiple connections according to the PDCP configuration information, wherein the PDCP entities in the multiple connections are connected with the at least two RLC entities.
Optionally, the at least two RLC entities include a uu RLC entity and at least one PC5 RLC entity; or alternatively
The at least two RLC entities include at least two PC5 RLC entities.
Optionally, in the case that the at least two RLC entities include a uu RLC entity and at least one PC5 RLC entity, the link indication information includes uu RLC indication information and at least one PC5 RLC indication information, which are respectively used to indicate that the PDCP entity connects the uu RLC entity and the at least one PC5 RLC entity;
alternatively, in case that the at least two RLC entities include at least two PC5 RLC entities, the link indication information includes at least two PC5 RLC indication information for indicating that the PDCP entity connects the at least two PC5 RLC entities.
Optionally, the PC5 RLC indication information carries relay UE identification information and logical channel LCH identification information.
Optionally, the PDCP configuration information is configured through RRC reconfiguration signaling.
Optionally, in the case that the at least two RLC entities include a uu RLC entity and at least one PC5 RLC entity, the PDCP configuration information is further configured to configure a uu link as a main path, where the uu link is established by connecting the uu RLC entity with the PDCP entity;
or in the case that the at least two RLC entities include at least two PC5 RLC entities, the PDCP configuration information is further configured to configure a first PC5 link as a primary path, the first PC5 link being one of the at least two PC5 links, wherein the at least two PC5 links are established by connecting the at least two PC5 RLC entities through the PDCP entity.
Optionally, in a case where one target PC5 link exists in the at least two PC5 links, the first PC5 link is the target PC5 link;
in the case where there are multiple target PC5 links for the at least two PC5 links, the first PC5 link is one of the multiple target PC5 links;
when the at least two PC5 links do not have the target PC5 link, the first PC5 link is determined by the network equipment according to the load condition of each relay UE corresponding to the at least two PC5 links and/or the uu link condition of each corresponding relay UE;
Wherein the RLC of the relay UE to which the target PC5 link is connected belongs to the primary cell group.
Optionally, the method further comprises:
in case that the PDCP entity is disabled for the split or copy function, data transmission is performed using the main path in the multi-connection.
Optionally, the PDCP configuration includes a bearer separation threshold, and the terminal performs uplink data splitting when the uplink data amount is greater than or equal to the bearer separation threshold.
Optionally, the PDCP configuration further includes a bearer duplication indication.
Optionally, in the case that the at least two RLC entities include a uu RLC entity and at least one PC5 RLC entity, the bearer duplication indication is used to indicate a uu link and a PC5 link bearer duplication;
alternatively, in case the at least two RLC entities comprise at least two PC5 RLC entities, the bearer duplication indication is used to indicate at least two PC5 link bearer duplication.
In a third aspect, an embodiment of the present invention provides a network device, including:
a sending module, configured to send packet data convergence protocol PDCP configuration information to a terminal;
the PDCP configuration information includes link indication information for indicating that a PDCP entity is connected to at least two radio link control RLC entities including at least one PC5 RLC entity.
Optionally, the at least two RLC entities include a uu RLC entity and at least one PC5 RLC entity; or alternatively
The at least two RLC entities include at least two PC5 RLC entities.
Optionally, in the case that the at least two RLC entities include a uu RLC entity and at least one PC5 RLC entity, the link indication information includes uu RLC indication information and at least one PC5 RLC indication information, which are respectively used to indicate that the PDCP entity connects the uu RLC entity and the at least one PC5 RLC entity;
alternatively, in case that the at least two RLC entities include at least two PC5 RLC entities, the link indication information includes at least two PC5 RLC indication information for indicating that the PDCP entity connects the at least two PC5 RLC entities.
Optionally, the PC5 RLC indication information carries relay UE identification information and logical channel LCH identification information.
Optionally, the PDCP configuration information is configured through RRC reconfiguration signaling.
Optionally, in the case that the at least two RLC entities include a uu RLC entity and at least one PC5 RLC entity, the PDCP configuration information is further configured to configure a uu link as a main path, where the uu link is established by connecting the uu RLC entity with the PDCP entity;
or in the case that the at least two RLC entities include at least two PC5 RLC entities, the PDCP configuration information is further configured to configure a first PC5 link as a primary path, the first PC5 link being one of the at least two PC5 links, wherein the at least two PC5 links are established by connecting the at least two PC5 RLC entities through the PDCP entity. Optionally, in a case where one target PC5 link exists in the at least two PC5 links, the first PC5 link is the target PC5 link;
In the case where there are multiple target PC5 links for the at least two PC5 links, the first PC5 link is one of the multiple target PC5 links;
when the at least two PC5 links do not have the target PC5 link, the first PC5 link is determined by the network equipment according to the load condition of each relay UE corresponding to the at least two PC5 links and/or the uu link condition of each corresponding relay UE;
wherein the RLC of the relay UE to which the target PC5 link is connected belongs to the primary cell group.
Optionally, the PDCP configuration includes a bearer separation threshold, where the bearer separation threshold is used to enable the terminal to perform uplink data splitting when the uplink data amount is greater than or equal to the bearer separation threshold.
Optionally, the PDCP configuration further includes a bearer duplication indication.
Optionally, in the case that the at least two RLC entities include a uu RLC entity and at least one PC5 RLC entity, the bearer duplication indication is used to indicate a uu link and a PC5 link bearer duplication;
alternatively, in case the at least two RLC entities comprise at least two PC5 RLC entities, the bearer duplication indication is used to indicate at least two PC5 link bearer duplication.
In a fourth aspect, an embodiment of the present invention provides a network device, including a transceiver and a processor, where the transceiver is configured to send packet data convergence protocol PDCP configuration information to a terminal;
the PDCP configuration information includes link indication information for indicating that a PDCP entity is connected to at least two radio link control RLC entities including at least one PC5 RLC entity.
Optionally, the at least two RLC entities include a uu RLC entity and at least one PC5 RLC entity; or alternatively
The at least two RLC entities include at least two PC5 RLC entities.
Optionally, in the case that the at least two RLC entities include a uu RLC entity and at least one PC5 RLC entity, the link indication information includes uu RLC indication information and at least one PC5 RLC indication information, which are respectively used to indicate that the PDCP entity connects the uu RLC entity and the at least one PC5 RLC entity;
alternatively, in case that the at least two RLC entities include at least two PC5 RLC entities, the link indication information includes at least two PC5 RLC indication information for indicating that the PDCP entity connects the at least two PC5 RLC entities.
Optionally, the PC5 RLC indication information carries relay UE identification information and logical channel LCH identification information.
Optionally, the PDCP configuration information is configured through RRC reconfiguration signaling.
Optionally, in the case that the at least two RLC entities include a uu RLC entity and at least one PC5 RLC entity, the PDCP configuration information is further configured to configure a uu link as a main path, where the uu link is established by connecting the uu RLC entity with the PDCP entity;
or in the case that the at least two RLC entities include at least two PC5 RLC entities, the PDCP configuration information is further configured to configure a first PC5 link as a primary path, the first PC5 link being one of the at least two PC5 links, wherein the at least two PC5 links are established by connecting the at least two PC5 RLC entities through the PDCP entity.
Optionally, in a case where one target PC5 link exists in the at least two PC5 links, the first PC5 link is the target PC5 link;
in the case where there are multiple target PC5 links for the at least two PC5 links, the first PC5 link is one of the multiple target PC5 links;
when the at least two PC5 links do not have the target PC5 link, the first PC5 link is determined by the network equipment according to the load condition of each relay UE corresponding to the at least two PC5 links and/or the uu link condition of each corresponding relay UE;
Wherein the RLC of the relay UE to which the target PC5 link is connected belongs to the primary cell group.
Optionally, the PDCP configuration includes a bearer separation threshold, where the bearer separation threshold is used to enable the terminal to perform uplink data splitting when the uplink data amount is greater than or equal to the bearer separation threshold.
Optionally, the PDCP configuration further includes a bearer duplication indication.
Optionally, in the case that the at least two RLC entities include a uu RLC entity and at least one PC5 RLC entity, the bearer duplication indication is used to indicate a uu link and a PC5 link bearer duplication;
alternatively, in case the at least two RLC entities comprise at least two PC5 RLC entities, the bearer duplication indication is used to indicate at least two PC5 link bearer duplication.
In a fifth aspect, an embodiment of the present invention provides a terminal, including:
a receiving module, configured to receive PDCP configuration information sent by a network device; the PDCP configuration information comprises link indication information, wherein the link indication information is used for indicating a PDCP entity to be connected with at least two wireless link control (RLC) entities, and the at least two RLC entities comprise at least one PC5 RLC entity;
A connection module for establishing multiple connections according to the PDCP configuration information; wherein the PDCP entity in the multiple connection is connected to the at least two RLC entities.
Optionally, the at least two RLC entities include a uu RLC entity and at least one PC5 RLC entity; or alternatively
The at least two RLC entities include at least two PC5 RLC entities.
Optionally, in the case that the at least two RLC entities include a uu RLC entity and at least one PC5 RLC entity, the link indication information includes uu RLC indication information and at least one PC5 RLC indication information, which are respectively used to indicate that the PDCP entity connects the uu RLC entity and the at least one PC5 RLC entity;
alternatively, in case that the at least two RLC entities include at least two PC5 RLC entities, the link indication information includes at least two PC5 RLC indication information for indicating that the PDCP entity connects the at least two PC5 RLC entities.
Optionally, the PC5 RLC indication information carries relay UE identification information and logical channel LCH identification information.
Optionally, the PDCP configuration information is configured through RRC reconfiguration signaling.
Optionally, in the case that the at least two RLC entities include a uu RLC entity and at least one PC5 RLC entity, the PDCP configuration information is further configured to configure a uu link as a main path, where the uu link is established by connecting the uu RLC entity with the PDCP entity;
Or in the case that the at least two RLC entities include at least two PC5 RLC entities, the PDCP configuration information is further configured to configure a first PC5 link as a primary path, the first PC5 link being one of the at least two PC5 links, wherein the at least two PC5 links are established by connecting the at least two PC5 RLC entities through the PDCP entity.
Optionally, in a case where one target PC5 link exists in the at least two PC5 links, the first PC5 link is the target PC5 link;
in the case where there are multiple target PC5 links for the at least two PC5 links, the first PC5 link is one of the multiple target PC5 links;
when the at least two PC5 links do not have the target PC5 link, the first PC5 link is determined by the network equipment according to the load condition of each relay UE corresponding to the at least two PC5 links and/or the uu link condition of each corresponding relay UE;
wherein the RLC of the relay UE to which the target PC5 link is connected belongs to the primary cell group.
Optionally, the terminal is further configured to:
in case that the PDCP entity is disabled for the split or copy function, data transmission is performed using the main path in the multi-connection.
Optionally, the PDCP configuration includes a bearer separation threshold, and the terminal performs uplink data splitting when the uplink data amount is greater than or equal to the bearer separation threshold.
Optionally, the PDCP configuration further includes a bearer duplication indication.
Optionally, in the case that the at least two RLC entities include a uu RLC entity and at least one PC5 RLC entity, the bearer duplication indication is used to indicate a uu link and a PC5 link bearer duplication;
alternatively, in case the at least two RLC entities comprise at least two PC5 RLC entities, the bearer duplication indication is used to indicate at least two PC5 link bearer duplication.
In a sixth aspect, an embodiment of the present invention provides a terminal, including a transceiver and a processor,
the transceiver is configured to receive PDCP configuration information sent by the network device; the PDCP configuration information comprises link indication information, wherein the link indication information is used for indicating a PDCP entity to be connected with at least two wireless link control (RLC) entities, and the at least two RLC entities comprise at least one PC5 RLC entity;
the processor is used for establishing multiple connections according to the PDCP configuration information; wherein the PDCP entity in the multiple connection is connected to the at least two RLC entities.
Optionally, the at least two RLC entities include a uu RLC entity and at least one PC5 RLC entity; or alternatively
The at least two RLC entities include at least two PC5 RLC entities.
Optionally, in the case that the at least two RLC entities include a uu RLC entity and at least one PC5 RLC entity, the link indication information includes uu RLC indication information and at least one PC5 RLC indication information, which are respectively used to indicate that the PDCP entity connects the uu RLC entity and the at least one PC5 RLC entity;
alternatively, in case that the at least two RLC entities include at least two PC5 RLC entities, the link indication information includes at least two PC5 RLC indication information for indicating that the PDCP entity connects the at least two PC5 RLC entities.
Optionally, the PC5 RLC indication information carries relay UE identification information and logical channel LCH identification information.
Optionally, the PDCP configuration information is configured through RRC reconfiguration signaling.
Optionally, in the case that the at least two RLC entities include a uu RLC entity and at least one PC5 RLC entity, the PDCP configuration information is further configured to configure a uu link as a main path, where the uu link is established by connecting the uu RLC entity with the PDCP entity;
or in the case that the at least two RLC entities include at least two PC5 RLC entities, the PDCP configuration information is further configured to configure a first PC5 link as a primary path, the first PC5 link being one of the at least two PC5 links, wherein the at least two PC5 links are established by connecting the at least two PC5 RLC entities through the PDCP entity.
Optionally, in a case where one target PC5 link exists in the at least two PC5 links, the first PC5 link is the target PC5 link;
in the case where there are multiple target PC5 links for the at least two PC5 links, the first PC5 link is one of the multiple target PC5 links;
when the at least two PC5 links do not have the target PC5 link, the first PC5 link is determined by the network equipment according to the load condition of each relay UE corresponding to the at least two PC5 links and/or the uu link condition of each corresponding relay UE;
wherein the RLC of the relay UE to which the target PC5 link is connected belongs to the primary cell group.
Optionally, the terminal is further configured to:
in case that the PDCP entity is disabled for the split or copy function, data transmission is performed using the main path in the multi-connection.
Optionally, the PDCP configuration includes a bearer separation threshold, and the terminal performs uplink data splitting when the uplink data amount is greater than or equal to the bearer separation threshold.
Optionally, the PDCP configuration further includes a bearer duplication indication.
Optionally, in the case that the at least two RLC entities include a uu RLC entity and at least one PC5 RLC entity, the bearer duplication indication is used to indicate a uu link and a PC5 link bearer duplication;
Alternatively, in case the at least two RLC entities comprise at least two PC5RLC entities, the bearer duplication indication is used to indicate at least two PC5 link bearer duplication.
In a seventh aspect, an embodiment of the present invention provides a network device, including: a processor, a memory and a program stored on the memory and executable on the processor, which when executed by the processor implements the steps of the link configuration method as described in the first aspect.
In an eighth aspect, an embodiment of the present invention provides a terminal, including: a processor, a memory and a program stored on the memory and executable on the processor, which when executed by the processor implements the steps of the link configuration method as described in the second aspect.
In a ninth aspect, embodiments of the present invention provide a computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of the link configuration method according to the first or second aspect.
In the embodiment of the invention, packet Data Convergence Protocol (PDCP) configuration information is sent to a terminal; the PDCP configuration information includes link indication information for indicating that a PDCP entity is connected to at least two radio link control RLC entities including at least one PC5RLC entity. By indicating the PDCP entity to connect at least two radio link control RLC entities including the PC5RLC entity in the PDCP configuration information, the PDCP entity can perform data transmission through the at least two RLC entities in the PC5 scenario, so that the transmission efficiency or transmission reliability of communication data can be improved.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings that are needed in the description of the embodiments of the present invention will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and other drawings may be obtained according to these drawings without inventive effort to a person of ordinary skill in the art.
Fig. 1 is a flowchart of a link configuration method provided in an embodiment of the present invention;
fig. 2 is a schematic diagram of a terminal and a network framework according to an embodiment of the present invention;
fig. 3 is a flowchart of another link configuration method provided by an embodiment of the present invention;
fig. 4 is a schematic structural diagram of a network device according to an embodiment of the present invention;
fig. 5 is a schematic structural diagram of a terminal according to an embodiment of the present invention;
fig. 6 is a schematic structural diagram of another network device according to an embodiment of the present invention;
fig. 7 is a schematic structural diagram of another terminal according to an embodiment of the present invention.
Detailed Description
The following description of the embodiments of the present invention will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are some, but not all embodiments of the invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
In the embodiment of the invention, a link configuration method is provided to solve the problem of low data transmission efficiency and reliability in the existing SL RELAY technology.
Referring to fig. 1, fig. 1 is a flowchart of a link configuration method provided in an embodiment of the present invention, for a network device, as shown in fig. 1, where the method includes the following steps:
step 101, transmitting packet data convergence protocol PDCP configuration information to a terminal;
the PDCP configuration information includes link indication information for indicating that a PDCP entity is connected to at least two radio link control RLC entities including at least one PC5 RLC entity.
Optionally, the at least two RLC entities include a uu RLC entity and at least one PC5 RLC entity; or alternatively
The at least two RLC entities include at least two PC5 RLC entities.
Optionally, in the case that the at least two RLC entities include a uu RLC entity and at least one PC5 RLC entity, the link indication information includes uu RLC indication information and at least one PC5 RLC indication information, which are respectively used to indicate that the PDCP entity connects the uu RLC entity and the at least one PC5 RLC entity;
alternatively, in case that the at least two RLC entities include at least two PC5 RLC entities, the link indication information includes at least two PC5 RLC indication information for indicating that the PDCP entity connects the at least two PC5 RLC entities.
It can be understood that the PDCP configuration information includes uu RLC indication information and at least one PC5 RLC indication information, which are respectively used for indicating a PDCP entity to connect uu interface radio link control uu RLC entity and at least one PC5 radio link control PC5 RLC entity; or, the PDCP configuration information includes at least two PC5 RLC indication information for indicating that the PDCP entity connects at least two PC5 RLC entities.
The uu link is established by the UE accessing the RAN through an air interface, specifically connecting the uu RLC entity through the PDCP entity. The PC5 link is established by connecting a UE (which may be referred to as a remote terminal, remote UE) with another UE (which may be referred to as a relay terminal, relay UE or UE-to Network Relay UE), and then using the UE (relay UE) as a relay access network, specifically connecting at least the PC5 RLC entity through the PDCP entity. In the PC5 link, single or multiple bearers of the Remote UE are respectively communicated with the access network through the Relay UE.
As shown in fig. 2, for L2 RELAY, there are uu-SDAP (Service Data Adaption Protocol, traffic data adaptation protocol) and uu-PDCP (Packet Data Convergence Protocol ) entities peer to the network on the remote UE, RLC (Radio Link Control ), MAC (Media Access Control, medium access control), PHY (Physical Layer) is a PC5 entity in the remote UE. On the relay UE, there are PC5 RLC corresponding to the remote UE, MAC, PHY entity, and uu RLC for carrying LCH (Logical Channel) corresponding to the PC5 RLC.
In the prior art, a remote UE only selects to access a relay UE or access one of the two UEs through an air interface based on a certain decision condition, and only one relay UE is selected to connect when the relay UE is selected to access. This is difficult to guarantee for traffic with high reliability requirements, such as URLLC (Ultra-Reliable and Low Latency Communications, low latency high reliability connection), which is a single connection scheme, both transmission reliability and latency requirements.
Here, it should be understood that in the method of the specific embodiment of the present invention, packet data convergence protocol PDCP configuration information is sent to a terminal; the PDCP configuration information includes link indication information, where the link indication information is used to indicate that the PDCP entity connects at least two radio link control RLC entities, and the at least two RLC entities include at least one PC5 RLC entity, so that a UE (remote UE) can establish multi-port connection between PC5 and uu or a multi-connection manner between 2 and more than 2 PCs 5 according to the PDCP configuration information.
The PDCP entity is indicated to connect uu interface radio link control uu RLC entity and at least one PC5 radio link control PC5 RLC entity, which may be that the RRC configures the PDCP entity to connect uu RLC and one or more PC5 RLC, so that the UE may implement multi-port connection between PC5 and uu.
Indicating that the PDCP entity connects at least two PC5 RLC entities, may be that the RRC configures the PDCP entity to connect two or more PC5 RLC entities, may enable the remote UE to connect with multiple relay UEs at the same time.
Optionally, the network device performs the step 101 when a DRB (Data Radio Bearer ) corresponding to PDCP of the remote UE is configured as a DRB supporting a multi-connection (multi-RLC-supported) sidelink, or a DRB supporting uu and sidelink of a multi-connection (multi-RLC-supported). The network device can acquire the DRB configuration corresponding to the PDCP of the remote UE through the report of the remote UE.
Optionally, the PC5 RLC indication information is configured to indicate RLC entity information and LCH information of a relay UE to which the PDCP entity is connected, and specifically, the PC5 RLC indication information carries relay UE identification information and logical channel LCH identification information.
It can be understood that if the RLC entity connected by PDCP is a PC5 RLC entity and a uu RLC entity, the PDCP configuration information carries indication information of the corresponding uu RLC entity and PC5 RLC entity, which are used for indicating RLC entity information and LCH information connected by PDCP; if the PDCP connected RLC is PC5 RLC, the PDCP configuration information does not carry uu RLC indication information.
Optionally, in the case that the at least two RLC entities include a uu RLC entity and at least one PC5 RLC entity, the PDCP configuration information is further configured to configure a uu link as a main path, where the uu link is established by connecting the uu RLC entity with the PDCP entity;
Or in the case that the at least two RLC entities include at least two PC5 RLC entities, the PDCP configuration information is further configured to configure a first PC5 link as a primary path, the first PC5 link being one of the at least two PC5 links, wherein the at least two PC5 links are established by connecting the at least two PC5 RLC entities through the PDCP entity.
It can be understood that, in the case that the link indication information includes uu RLC indication information and at least one PC5 RLC indication information, the PDCP configuration information is further configured to configure a uu link as a main path;
or in the case that the link indication information includes at least two PC5 RLC indication information, the PDCP configuration information is further configured to configure a first PC5 link as a main path, where the first PC5 link is one of the at least two PC5 links.
Optionally, in a case where one target PC5 link exists in the at least two PC5 links, the first PC5 link is the target PC5 link;
in the case where there are multiple target PC5 links for the at least two PC5 links, the first PC5 link is one of the multiple target PC5 links;
when the at least two PC5 links do not have the target PC5 link, the first PC5 link is determined by the network equipment according to the load condition of each relay UE corresponding to the at least two PC5 links and/or the uu link condition of each corresponding relay UE;
Wherein the RLC of the relay UE to which the target PC5 link is connected belongs to the primary cell group.
It can be understood that the PDCP configuration information carries indication information of uu RLC and PC5 RLC corresponding to each other, and the uu RLC is configured as a main path; configuring PDCP to be a PC5 RLC main path of which the RLC of RELAY connected with the PC5 RLC is attributed to a main cell group (primary cell group, MCG) when the PDCP is configured to carry only PC5 RLC indication information; if there are a plurality of PC5 RLCs and the PC5 RLCs of RELAY connected with the plurality of PC5 RLCs belong to the main cell group, selecting one of the paths, wherein one of the paths can be selected based on a preset condition, or one of the paths can be selected randomly; if the PC5 RLC of the RELAY connected with the PC5 RLC belongs to the PC5 RLC of the main cell group, the network selects the PC5 RLC corresponding to the better RELAY as the main path based on the connected RELAY load condition and/or the uu link condition of the RELAY.
The PDCP configuration information includes indication information of uu link and indication information of PC5 link or the PDCP configuration information includes indication information of at least two PC5 links, i.e. PDCP configures a plurality of logical channels, and may be configured to support a duplicate function or a split function.
The PDCP configuration information is used to configure the primary path such that the terminal can determine the primary path according to the PDCP configuration information, and when the PDCP entity is disabled from splitting or copying, the terminal can perform data transmission using the primary path in the multi-connection.
Optionally, the PDCP configuration includes a bearer separation threshold, where the bearer separation threshold is used to enable the terminal to perform uplink data splitting when the uplink data amount is greater than or equal to the bearer separation threshold.
Through the shunting mode, the data transmission efficiency can be improved.
The PDCP configuration may be further configured to indicate relay UE identification information and LCH identification information corresponding to the second split while the PDCP configuration includes a bearer separation threshold. And the terminal determines a target relay UE and a target LCH according to UE identification information and LCH identification information corresponding to the second shunt under the condition that the uplink data amount is larger than or equal to the bearer separation threshold value based on the PDCP configuration, and the PDCP executes uplink data shunt by using the target relay UE and the target LCH.
It will be appreciated that in the non-split state, the terminal is able to utilize the main path in the multiple connections for data transmission. In the case that the multi-connection includes uu connection, uu connection is adopted in the state of not splitting, and the PDCP configuration specifically indicates to determine a PC5 link for splitting when splitting is indicated, that is, to determine a target relay UE and a target LCH for splitting.
Optionally, when the bearer separation threshold is empty, it indicates that uplink splitting is not supported.
Optionally, the PDCP configuration further includes a bearer duplication indication.
Optionally, in the case that the at least two RLC entities include a uu RLC entity and at least one PC5 RLC entity, the bearer duplication indication is used to indicate a uu link and a PC5 link bearer duplication;
alternatively, in case the at least two RLC entities comprise at least two PC5 RLC entities, the bearer duplication indication is used to indicate at least two PC5 link bearer duplication.
It may be understood that, in the case that the link indication information includes uu RLC indication information and at least one PC5 RLC indication information, the bearer duplication indication is used to indicate a uu link and a PC5 link bearer duplication;
or in the case that the link indication information includes at least two PC5 RLC indication information, the bearer duplication indication is used to indicate at least two PC5 link bearer duplication.
The transmission reliability can be improved by bearer replication.
The bearer duplication indication indicates duplication of corresponding uu LCH information, relay UE identification information, and relay LCH identification information in case the PDCP configuration information includes indication information of uu links and indication information of PC5 links, and the bearer duplication indication indicates duplication of relay UE identification information and logical channel LCH identification information of PC5 links in case the PDCP configuration information includes indication information of at least two PC5 links. For example, if there are 2 PC5 links, relay identification information and LCH identification information of the 2 PC5 links are indicated, respectively.
Optionally, the PDCP configuration information is configured through RRC reconfiguration signaling (rrcrecon configuration).
For example, the Remote UE selects an access air interface and establishes a PC5 connection with relay1 according to a certain decision criterion, and the RRC reconfiguration signaling configures uu RLC using "uu RLC SEQUENCE" and increases PC5 RLC configuration, which specifically includes:
Figure BDA0003367132260000161
Figure BDA0003367132260000171
in the signaling, the "PC5 RLC SEQUENCE" specifically configures relay UE identification information and logical channel LCH identification information to which the PC5 RLC belongs, and the "uu RLC SEQUENCE" portion is configured for the uu RLC, and specifically includes a primary path configuration "primary path", that is, based on the "primary path" signaling, in the case that the at least two RLC entities include the uu RLC entity and at least one PC5 RLC entity, the uu link is configured as a primary path.
In the embodiment of the invention, packet Data Convergence Protocol (PDCP) configuration information is sent to a terminal; the PDCP configuration information includes link indication information for indicating that a PDCP entity is connected to at least two radio link control RLC entities including at least one PC5 RLC entity. In the embodiment of the invention, the PDCP entity is indicated to be connected with at least two Radio Link Control (RLC) entities including the PC5 RLC entity in the PDCP configuration information, and in the PC5 scene, the PDCP entity can carry out data transmission through the at least two RLC entities, so that the transmission efficiency or the transmission reliability of communication data can be improved.
Referring to fig. 3, fig. 3 is a flowchart of another link configuration method provided in an embodiment of the present invention, for a terminal, as shown in fig. 3, where the method includes the following steps:
step 301, receiving PDCP configuration information sent by a network device;
the PDCP configuration information includes link indication information for indicating that a PDCP entity is connected to at least two radio link control RLC entities including at least one PC5 RLC entity.
Step 302, establishing multiple connections according to the PDCP configuration information; wherein the PDCP entity in the multiple connection is connected to the at least two RLC entities.
Optionally, the at least two RLC entities include a uu RLC entity and at least one PC5 RLC entity; or alternatively
The at least two RLC entities include at least two PC5 RLC entities.
Optionally, in the case that the at least two RLC entities include a uu RLC entity and at least one PC5 RLC entity, the link indication information includes uu RLC indication information and at least one PC5 RLC indication information, which are respectively used to indicate that the PDCP entity connects the uu RLC entity and the at least one PC5 RLC entity;
alternatively, in case that the at least two RLC entities include at least two PC5 RLC entities, the link indication information includes at least two PC5 RLC indication information for indicating that the PDCP entity connects the at least two PC5 RLC entities.
It is understood that the PDCP entity in multiple connection connects uu RLC entity and PC5 RLC entity, or the PDCP entity in multiple connection connects at least two PC5 RLC entities.
Optionally, the PC5 RLC indication information carries relay UE identification information and logical channel LCH identification information.
Optionally, the PDCP configuration information is configured through RRC reconfiguration signaling.
Optionally, in the case that the at least two RLC entities include a uu RLC entity and at least one PC5 RLC entity, the PDCP configuration information is further configured to configure a uu link as a main path, where the uu link is established by connecting the uu RLC entity with the PDCP entity;
or in the case that the at least two RLC entities include at least two PC5 RLC entities, the PDCP configuration information is further configured to configure a first PC5 link as a primary path, the first PC5 link being one of the at least two PC5 links, wherein the at least two PC5 links are established by connecting the at least two PC5 RLC entities through the PDCP entity.
Optionally, in a case where one target PC5 link exists in the at least two PC5 links, the first PC5 link is the target PC5 link;
in the case where there are multiple target PC5 links for the at least two PC5 links, the first PC5 link is one of the multiple target PC5 links;
When the at least two PC5 links do not have the target PC5 link, the first PC5 link is determined by the network equipment according to the load condition of each relay UE corresponding to the at least two PC5 links and/or the uu link condition of each corresponding relay UE;
wherein the RLC of the relay UE to which the target PC5 link is connected belongs to the primary cell group.
Optionally, the method further comprises:
in case that the PDCP entity is disabled for the split or copy function, data transmission is performed using the main path in the multi-connection.
Optionally, the PDCP configuration includes a bearer separation threshold, and the terminal performs uplink data splitting when the uplink data amount is greater than or equal to the bearer separation threshold.
Optionally, the PDCP configuration further includes a bearer duplication indication.
Optionally, in the case that the at least two RLC entities include a uu RLC entity and at least one PC5 RLC entity, the bearer duplication indication is used to indicate a uu link and a PC5 link bearer duplication;
alternatively, in case the at least two RLC entities comprise at least two PC5 RLC entities, the bearer duplication indication is used to indicate at least two PC5 link bearer duplication.
It should be noted that, as an implementation manner of the network device corresponding to the embodiment shown in fig. 1, a specific implementation manner of the embodiment may refer to a related description in the embodiment shown in fig. 1, and in order to avoid repetitive description, the embodiment is not repeated.
In the embodiment of the invention, packet Data Convergence Protocol (PDCP) configuration information sent by network equipment is received; the PDCP configuration information comprises link indication information, wherein the link indication information is used for indicating a PDCP entity to be connected with at least two wireless link control (RLC) entities, and the at least two RLC entities comprise at least one PC5 RLC entity; establishing multiple connections according to the PDCP configuration information, wherein the PDCP entity in the multiple connections connects the at least two RLC entities, and the PDCP entity connects at least two radio link control RLC entities including a PC5 RLC entity according to the PDCP configuration information, and in a PC5 scenario, the PDCP entity may perform data transmission through the at least two RLC entities, so that transmission efficiency or transmission reliability of communication data may be improved.
Referring to fig. 4, fig. 4 is a schematic structural diagram of a network device according to an embodiment of the present invention, and as shown in fig. 4, a network device 400 includes:
a sending module 401, configured to send packet data convergence protocol PDCP configuration information to a terminal;
the PDCP configuration information includes link indication information for indicating that a PDCP entity is connected to at least two radio link control RLC entities including at least one PC5 RLC entity.
Optionally, the at least two RLC entities include a uu RLC entity and at least one PC5 RLC entity; or alternatively
The at least two RLC entities include at least two PC5 RLC entities.
Optionally, in the case that the at least two RLC entities include a uu RLC entity and at least one PC5 RLC entity, the link indication information includes uu RLC indication information and at least one PC5 RLC indication information, which are respectively used to indicate that the PDCP entity connects the uu RLC entity and the at least one PC5 RLC entity;
alternatively, in case that the at least two RLC entities include at least two PC5 RLC entities, the link indication information includes at least two PC5 RLC indication information for indicating that the PDCP entity connects the at least two PC5 RLC entities.
Optionally, the PC5 RLC indication information carries relay UE identification information and logical channel LCH identification information.
Optionally, the PDCP configuration information is configured through RRC reconfiguration signaling.
Optionally, in the case that the at least two RLC entities include a uu RLC entity and at least one PC5 RLC entity, the PDCP configuration information is further configured to configure a uu link as a main path, where the uu link is established by connecting the uu RLC entity with the PDCP entity;
or in the case that the at least two RLC entities include at least two PC5 RLC entities, the PDCP configuration information is further configured to configure a first PC5 link as a primary path, the first PC5 link being one of the at least two PC5 links, wherein the at least two PC5 links are established by connecting the at least two PC5 RLC entities through the PDCP entity.
Optionally, in a case where one target PC5 link exists in the at least two PC5 links, the first PC5 link is the target PC5 link;
in the case where there are multiple target PC5 links for the at least two PC5 links, the first PC5 link is one of the multiple target PC5 links;
when the at least two PC5 links do not have the target PC5 link, the first PC5 link is determined by the network equipment according to the load condition of each relay UE corresponding to the at least two PC5 links and/or the uu link condition of each corresponding relay UE;
wherein the RLC of the relay UE to which the target PC5 link is connected belongs to the primary cell group.
Optionally, the PDCP configuration includes a bearer separation threshold, where the bearer separation threshold is used to enable the terminal to perform uplink data splitting when the uplink data amount is greater than or equal to the bearer separation threshold.
Optionally, the PDCP configuration further includes a bearer duplication indication.
Optionally, in the case that the at least two RLC entities include a uu RLC entity and at least one PC5 RLC entity, the bearer duplication indication is used to indicate a uu link and a PC5 link bearer duplication;
alternatively, in case the at least two RLC entities comprise at least two PC5 RLC entities, the bearer duplication indication is used to indicate at least two PC5 link bearer duplication.
It should be noted that, the network device provided in the embodiment of the present invention is a device capable of executing the link configuration method in fig. 1, and all implementation manners in the embodiment of the link configuration method are applicable to the network device, and the same or similar beneficial effects can be achieved.
Referring to fig. 5, fig. 5 is a schematic structural diagram of a terminal according to an embodiment of the present invention, and as shown in fig. 5, a terminal 500 includes:
a receiving module 501, configured to receive PDCP configuration information sent by a network device; the PDCP configuration information comprises link indication information, wherein the link indication information is used for indicating a PDCP entity to be connected with at least two wireless link control (RLC) entities, and the at least two RLC entities comprise at least one PC5 RLC entity;
a connection module 502, configured to establish multiple connections according to the PDCP configuration information; wherein the PDCP entity in the multiple connection is connected to the at least two RLC entities.
Optionally, the at least two RLC entities include a uu RLC entity and at least one PC5 RLC entity; or alternatively
The at least two RLC entities include at least two PC5 RLC entities.
Optionally, in the case that the at least two RLC entities include a uu RLC entity and at least one PC5 RLC entity, the link indication information includes uu RLC indication information and at least one PC5 RLC indication information, which are respectively used to indicate that the PDCP entity connects the uu RLC entity and the at least one PC5 RLC entity;
Alternatively, in case that the at least two RLC entities include at least two PC5 RLC entities, the link indication information includes at least two PC5 RLC indication information for indicating that the PDCP entity connects the at least two PC5 RLC entities.
Optionally, the PC5 RLC indication information carries relay UE identification information and logical channel LCH identification information.
Optionally, the PDCP configuration information is configured through RRC reconfiguration signaling.
Optionally, in the case that the at least two RLC entities include a uu RLC entity and at least one PC5 RLC entity, the PDCP configuration information is further configured to configure a uu link as a main path, where the uu link is established by connecting the uu RLC entity with the PDCP entity;
or in the case that the at least two RLC entities include at least two PC5 RLC entities, the PDCP configuration information is further configured to configure a first PC5 link as a primary path, the first PC5 link being one of the at least two PC5 links, wherein the at least two PC5 links are established by connecting the at least two PC5 RLC entities through the PDCP entity.
Optionally, in a case where one target PC5 link exists in the at least two PC5 links, the first PC5 link is the target PC5 link;
In the case where there are multiple target PC5 links for the at least two PC5 links, the first PC5 link is one of the multiple target PC5 links;
when the at least two PC5 links do not have the target PC5 link, the first PC5 link is determined by the network equipment according to the load condition of each relay UE corresponding to the at least two PC5 links and/or the uu link condition of each corresponding relay UE;
wherein the RLC of the relay UE to which the target PC5 link is connected belongs to the primary cell group.
Optionally, the terminal is further configured to:
in case that the PDCP entity is disabled for the split or copy function, data transmission is performed using the main path in the multi-connection.
Optionally, the PDCP configuration includes a bearer separation threshold, and the terminal performs uplink data splitting when the uplink data amount is greater than or equal to the bearer separation threshold.
Optionally, the PDCP configuration further includes a bearer duplication indication.
Optionally, in the case that the at least two RLC entities include a uu RLC entity and at least one PC5 RLC entity, the bearer duplication indication is used to indicate a uu link and a PC5 link bearer duplication;
alternatively, in case the at least two RLC entities comprise at least two PC5 RLC entities, the bearer duplication indication is used to indicate at least two PC5 link bearer duplication.
It should be noted that, the terminal provided in the embodiment of the present invention is a device capable of executing the link configuration method of fig. 3, and all implementation manners in the embodiment of the link configuration method are applicable to the terminal, and the same or similar beneficial effects can be achieved.
In particular, referring to fig. 6, an embodiment of the present invention further provides a network device, including a bus 601, a transceiver 602, an antenna 603, a bus interface 604, a processor 605, and a memory 606.
A transceiver 602 for transmitting packet data convergence protocol PDCP configuration information to a terminal.
The PDCP configuration information includes link indication information for indicating that a PDCP entity is connected to at least two radio link control RLC entities including at least one PC5 RLC entity.
Optionally, the at least two RLC entities include a uu RLC entity and at least one PC5 RLC entity; or alternatively
The at least two RLC entities include at least two PC5 RLC entities.
Optionally, in the case that the at least two RLC entities include a uu RLC entity and at least one PC5 RLC entity, the link indication information includes uu RLC indication information and at least one PC5 RLC indication information, which are respectively used to indicate that the PDCP entity connects the uu RLC entity and the at least one PC5 RLC entity;
Alternatively, in case that the at least two RLC entities include at least two PC5 RLC entities, the link indication information includes at least two PC5 RLC indication information for indicating that the PDCP entity connects the at least two PC5 RLC entities.
Optionally, the PC5 RLC indication information carries relay UE identification information and logical channel LCH identification information.
Optionally, the PDCP configuration information is configured through RRC reconfiguration signaling.
Optionally, in the case that the at least two RLC entities include a uu RLC entity and at least one PC5 RLC entity, the PDCP configuration information is further configured to configure a uu link as a main path, where the uu link is established by connecting the uu RLC entity with the PDCP entity;
or in the case that the at least two RLC entities include at least two PC5 RLC entities, the PDCP configuration information is further configured to configure a first PC5 link as a primary path, the first PC5 link being one of the at least two PC5 links, wherein the at least two PC5 links are established by connecting the at least two PC5 RLC entities through the PDCP entity.
Optionally, in a case where one target PC5 link exists in the at least two PC5 links, the first PC5 link is the target PC5 link;
In the case where there are multiple target PC5 links for the at least two PC5 links, the first PC5 link is one of the multiple target PC5 links;
when the at least two PC5 links do not have the target PC5 link, the first PC5 link is determined by the network equipment according to the load condition of each relay UE corresponding to the at least two PC5 links and/or the uu link condition of each corresponding relay UE;
wherein the RLC of the relay UE to which the target PC5 link is connected belongs to the primary cell group.
Optionally, the PDCP configuration includes a bearer separation threshold, where the bearer separation threshold is used to enable the terminal to perform uplink data splitting when the uplink data amount is greater than or equal to the bearer separation threshold.
Optionally, the PDCP configuration further includes a bearer duplication indication.
Optionally, in the case that the at least two RLC entities include a uu RLC entity and at least one PC5 RLC entity, the bearer duplication indication is used to indicate a uu link and a PC5 link bearer duplication;
alternatively, in case the at least two RLC entities comprise at least two PC5 RLC entities, the bearer duplication indication is used to indicate at least two PC5 link bearer duplication.
In fig. 6, a bus architecture (represented by bus 601), the bus 601 may include any number of interconnected buses and bridges, with the bus 601 linking together various circuits, including one or more processors, represented by processor 605, and memory, represented by memory 606. The bus 601 may also link together various other circuits such as peripheral devices, voltage regulators, power management circuits, etc., which are well known in the art and, therefore, will not be described further herein. Bus interface 604 provides an interface between bus 601 and transceiver 602. The transceiver 602 may be one element or may be multiple elements, such as multiple receivers and transmitters, providing a means for communicating with various other apparatus over a transmission medium. The data processed by the processor 605 is transmitted over a wireless medium via an antenna 603, and further, the antenna 603 also receives data and transmits the data to the processor 605.
The processor 605 is responsible for managing the bus 601 and general processing, and may also provide various functions including timing, peripheral interfaces, voltage regulation, power management, and other control functions. And memory 606 may be used to store data used by processor 605 in performing operations.
Alternatively, the processor 605 may be CPU, ASIC, FPGA or a CPLD.
It should be noted that, the network device provided in the embodiment of the present invention is a device capable of executing the link configuration method in fig. 1, and all implementation manners in the embodiment of the link configuration method are applicable to the network device, and the same or similar beneficial effects can be achieved.
Specifically, referring to fig. 7, an embodiment of the present invention further provides a terminal device, including a bus 701, a transceiver 702, an antenna 703, a bus interface 704, a processor 705, and a memory 706.
A transceiver 702, configured to receive packet data convergence protocol PDCP configuration information sent by a network device; the PDCP configuration information comprises link indication information, wherein the link indication information is used for indicating a PDCP entity to be connected with at least two wireless link control (RLC) entities, and the at least two RLC entities comprise at least one PC5 RLC entity; .
Further, a processor 705, configured to establish multiple connections according to the PDCP configuration information; wherein the PDCP entity in the multiple connection is connected to the at least two RLC entities.
Optionally, the at least two RLC entities include a uu RLC entity and at least one PC5 RLC entity; or alternatively
The at least two RLC entities include at least two PC5 RLC entities.
Optionally, in the case that the at least two RLC entities include a uu RLC entity and at least one PC5 RLC entity, the link indication information includes uu RLC indication information and at least one PC5 RLC indication information, which are respectively used to indicate that the PDCP entity connects the uu RLC entity and the at least one PC5 RLC entity;
alternatively, in case that the at least two RLC entities include at least two PC5 RLC entities, the link indication information includes at least two PC5 RLC indication information for indicating that the PDCP entity connects the at least two PC5 RLC entities.
Optionally, the PC5 RLC indication information carries relay UE identification information and logical channel LCH identification information.
Optionally, the PDCP configuration information is configured through RRC reconfiguration signaling.
Optionally, in the case that the at least two RLC entities include a uu RLC entity and at least one PC5 RLC entity, the PDCP configuration information is further configured to configure a uu link as a main path, where the uu link is established by connecting the uu RLC entity with the PDCP entity;
or in the case that the at least two RLC entities include at least two PC5 RLC entities, the PDCP configuration information is further configured to configure a first PC5 link as a primary path, the first PC5 link being one of the at least two PC5 links, wherein the at least two PC5 links are established by connecting the at least two PC5 RLC entities through the PDCP entity.
Optionally, in a case where one target PC5 link exists in the at least two PC5 links, the first PC5 link is the target PC5 link;
in the case where there are multiple target PC5 links for the at least two PC5 links, the first PC5 link is one of the multiple target PC5 links;
when the at least two PC5 links do not have the target PC5 link, the first PC5 link is determined by the network equipment according to the load condition of each relay UE corresponding to the at least two PC5 links and/or the uu link condition of each corresponding relay UE;
wherein the RLC of the relay UE to which the target PC5 link is connected belongs to the primary cell group.
Optionally, the terminal is further configured to:
in case that the PDCP entity is disabled for the split or copy function, data transmission is performed using the main path in the multi-connection.
Optionally, the PDCP configuration includes a bearer separation threshold, and the terminal performs uplink data splitting when the uplink data amount is greater than or equal to the bearer separation threshold.
Optionally, the PDCP configuration further includes a bearer duplication indication.
Optionally, in the case that the at least two RLC entities include a uu RLC entity and at least one PC5 RLC entity, the bearer duplication indication is used to indicate a uu link and a PC5 link bearer duplication;
Alternatively, in case the at least two RLC entities comprise at least two PC5 RLC entities, the bearer duplication indication is used to indicate at least two PC5 link bearer duplication.
In FIG. 7, a bus architecture (represented by bus 701), the bus 701 may include any number of interconnected buses and bridges, with the bus 701 linking together various circuits, including one or more processors, represented by the processor 705, and memory, represented by the memory 706. The bus 701 may also link together various other circuits such as peripheral devices, voltage regulators, power management circuits, etc., which are well known in the art and, therefore, will not be described further herein. Bus interface 704 provides an interface between bus 701 and transceiver 702. The transceiver 702 may be one element or a plurality of elements, such as a plurality of receivers and transmitters, providing a means for communicating with various other apparatus over a transmission medium. The data processed by the processor 705 is transmitted over a wireless medium via the antenna 703, and further, the antenna 703 receives and transmits data to the processor 705.
The processor 705 is responsible for managing the bus 701 and general processing and may also provide various functions including timing, peripheral interfaces, voltage regulation, power management, and other control functions. And memory 706 may be used to store data used by processor 705 in performing operations.
Alternatively, the processor 705 may be a CPU, ASIC, FPGA or CPLD.
It should be noted that, the terminal provided in the embodiment of the present invention is a device capable of executing the link configuration method of fig. 3, and all implementation manners in the embodiment of the link configuration method are applicable to the terminal, and the same or similar beneficial effects can be achieved.
The embodiment of the invention also provides a network device, which comprises: the program is executed by the processor to implement each process of the embodiment of the link configuration method in fig. 1, and the same technical effects can be achieved, so that repetition is avoided and no further description is given here.
The embodiment of the invention also provides a terminal device, which comprises: the program is executed by the processor to implement each process of the embodiment of the link configuration method in fig. 2, and the same technical effects can be achieved, so that repetition is avoided and no further description is given here.
The embodiment of the present invention further provides a computer readable storage medium, on which a computer program is stored, where the computer program when executed by a processor implements each process of the above-mentioned link configuration method embodiment in fig. 1 or fig. 2, and the same technical effects can be achieved, and in order to avoid repetition, a detailed description is omitted herein. Wherein the computer readable storage medium is selected from Read-Only Memory (ROM), random access Memory (Random Access Memory, RAM), magnetic disk or optical disk.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present invention may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (e.g. ROM/RAM, magnetic disk, optical disk) comprising instructions for causing a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the method according to the embodiments of the present invention.
The embodiments of the present invention have been described above with reference to the accompanying drawings, but the present invention is not limited to the above-described embodiments, which are merely illustrative and not restrictive, and many forms may be made by those having ordinary skill in the art without departing from the spirit of the present invention and the scope of the claims, which are to be protected by the present invention.

Claims (28)

1. A link configuration method applied to a network device, the method comprising:
transmitting packet data convergence protocol PDCP configuration information to a terminal;
the PDCP configuration information includes link indication information for indicating that a PDCP entity is connected to at least two radio link control RLC entities including at least one PC5 RLC entity.
2. The method of claim 1, wherein the at least two RLC entities comprise a uu RLC entity and at least one PC5 RLC entity; or alternatively
The at least two RLC entities include at least two PC5 RLC entities.
3. The method of claim 2, wherein the step of determining the position of the substrate comprises,
in the case that the at least two RLC entities include a uu RLC entity and at least one PC5 RLC entity, the link indication information includes uu RLC indication information and at least one PC5 RLC indication information for respectively indicating the PDCP entity to connect the uu RLC entity and the at least one PC5 RLC entity;
Alternatively, in case that the at least two RLC entities include at least two PC5 RLC entities, the link indication information includes at least two PC5 RLC indication information for indicating that the PDCP entity connects the at least two PC5 RLC entities.
4. The method of claim 3, wherein the PC5 RLC indication information carries relay UE identification information and logical channel LCH identification information.
5. The method according to any of claims 1-4, wherein the PDCP configuration information is configured by RRC reconfiguration signaling.
6. The method according to any of claims 2-4, wherein, in case the at least two RLC entities comprise a uu RLC entity and at least one PC5 RLC entity, the PDCP configuration information is further used to configure a uu link as a primary path, wherein the uu link is established by connecting the uu RLC entity through the PDCP entity;
or in the case that the at least two RLC entities include at least two PC5 RLC entities, the PDCP configuration information is further configured to configure a first PC5 link as a primary path, the first PC5 link being one of the at least two PC5 links, wherein the at least two PC5 links are established by connecting the at least two PC5 RLC entities through the PDCP entity.
7. The method of claim 6, wherein the step of providing the first layer comprises,
wherein, in the case that there is one target PC5 link in the at least two PC5 links, the first PC5 link is the target PC5 link;
in the case where there are multiple target PC5 links for the at least two PC5 links, the first PC5 link is one of the multiple target PC5 links;
when the at least two PC5 links do not have the target PC5 link, the first PC5 link is determined by the network equipment according to the load condition of each relay UE corresponding to the at least two PC5 links and/or the uu link condition of each corresponding relay UE;
wherein the RLC of the relay UE to which the target PC5 link is connected belongs to the primary cell group.
8. The method according to any of claims 1-4, wherein the PDCP configuration includes a bearer separation threshold for enabling a terminal to perform upstream data splitting if an upstream data amount is greater than or equal to the bearer separation threshold.
9. The method according to any of claims 2-4, wherein the PDCP configuration further comprises a bearer duplication indication.
10. The method of claim 9, wherein the step of determining the position of the substrate comprises,
In case the at least two RLC entities comprise a uu RLC entity and at least one PC5 RLC entity, the bearer duplication indication is for indicating a uu link and a PC5 link bearer duplication;
alternatively, in case the at least two RLC entities comprise at least two PC5 RLC entities, the bearer duplication indication is used to indicate at least two PC5 link bearer duplication.
11. A link configuration method applied to a terminal, the method comprising:
receiving PDCP configuration information sent by network equipment;
the PDCP configuration information comprises link indication information, wherein the link indication information is used for indicating a PDCP entity to be connected with at least two wireless link control (RLC) entities, and the at least two RLC entities comprise at least one PC5 RLC entity;
and establishing multiple connections according to the PDCP configuration information, wherein the PDCP entities in the multiple connections are connected with the at least two RLC entities.
12. The method of claim 11, wherein the at least two RLC entities include a uu RLC entity and at least one PC5 RLC entity; or alternatively
The at least two RLC entities include at least two PC5 RLC entities.
13. The method of claim 12, wherein the step of determining the position of the probe is performed,
in the case that the at least two RLC entities include a uu RLC entity and at least one PC5 RLC entity, the link indication information includes uu RLC indication information and at least one PC5 RLC indication information for respectively indicating the PDCP entity to connect the uu RLC entity and the at least one PC5 RLC entity;
alternatively, in case that the at least two RLC entities include at least two PC5 RLC entities, the link indication information includes at least two PC5 RLC indication information for indicating that the PDCP entity connects the at least two PC5 RLC entities.
14. The method of claim 13, wherein the PC5 RLC indication information carries relay UE identification information and logical channel LCH identification information.
15. The method according to any of claims 11-14, wherein the PDCP configuration information is configured by RRC reconfiguration signaling.
16. The method according to any of claims 12-14, wherein, in case the at least two RLC entities comprise a uu RLC entity and at least one PC5 RLC entity, the PDCP configuration information is further used to configure a uu link as a primary path, wherein the uu link is established by connecting the uu RLC entity through the PDCP entity;
Or in the case that the at least two RLC entities include at least two PC5 RLC entities, the PDCP configuration information is further configured to configure a first PC5 link as a primary path, the first PC5 link being one of the at least two PC5 links, wherein the at least two PC5 links are established by connecting the at least two PC5 RLC entities through the PDCP entity.
17. The method of claim 16, wherein the step of determining the position of the probe comprises,
wherein, in the case that there is one target PC5 link in the at least two PC5 links, the first PC5 link is the target PC5 link;
in the case where there are multiple target PC5 links for the at least two PC5 links, the first PC5 link is one of the multiple target PC5 links;
when the at least two PC5 links do not have the target PC5 link, the first PC5 link is determined by the network equipment according to the load condition of each relay UE corresponding to the at least two PC5 links and/or the uu link condition of each corresponding relay UE;
wherein the RLC of the relay UE to which the target PC5 link is connected belongs to the primary cell group.
18. The method of claim 16, wherein the method further comprises:
In case that the PDCP entity is disabled for the split or copy function, data transmission is performed using the main path in the multi-connection.
19. The method according to any of claims 11-14, wherein the PDCP configuration includes a bearer separation threshold, the terminal performing upstream data splitting if an amount of upstream data is greater than or equal to the bearer separation threshold.
20. The method according to any of claims 12-14, wherein the PDCP configuration further comprises a bearer duplication indication.
21. The method of claim 20, wherein the step of determining the position of the probe is performed,
in case the at least two RLC entities comprise a uu RLC entity and at least one PC5 RLC entity, the bearer duplication indication is for indicating a uu link and a PC5 link bearer duplication;
alternatively, in case the at least two RLC entities comprise at least two PC5 RLC entities, the bearer duplication indication is used to indicate at least two PC5 link bearer duplication.
22. A network device, comprising:
a sending module, configured to send packet data convergence protocol PDCP configuration information to a terminal;
the PDCP configuration information includes link indication information for indicating that a PDCP entity is connected to at least two radio link control RLC entities including at least one PC5 RLC entity.
23. A network device comprising a transceiver and a processor,
the transceiver is configured to send packet data convergence protocol PDCP configuration information to a terminal;
the PDCP configuration information includes link indication information for indicating that a PDCP entity is connected to at least two radio link control RLC entities including at least one PC5 RLC entity.
24. A terminal, comprising:
a receiving module, configured to receive PDCP configuration information sent by a network device; the PDCP configuration information comprises link indication information, wherein the link indication information is used for indicating a PDCP entity to be connected with at least two wireless link control (RLC) entities, and the at least two RLC entities comprise at least one PC5 RLC entity;
a connection module for establishing multiple connections according to the PDCP configuration information; wherein the PDCP entity in the multiple connection is connected to the at least two RLC entities.
25. A terminal, comprising a transceiver and a processor,
the transceiver is configured to receive PDCP configuration information sent by a network device; the PDCP configuration information comprises link indication information, wherein the link indication information is used for indicating a PDCP entity to be connected with at least two wireless link control (RLC) entities, and the at least two RLC entities comprise at least one PC5 RLC entity;
The processor is used for establishing multiple connections according to the PDCP configuration information; wherein the PDCP entity in the multiple connection is connected to the at least two RLC entities.
26. A network device, comprising: a processor, a memory and a program stored on the memory and executable on the processor, which when executed by the processor implements the steps of the link configuration method according to any one of claims 1 to 10.
27. A terminal, comprising: a processor, a memory and a program stored on the memory and executable on the processor, which when executed by the processor implements the steps of the link configuration method of any of claims 11 to 21.
28. A computer readable storage medium, characterized in that the computer readable storage medium has stored thereon a computer program which, when executed by a processor, implements the steps of the link configuration method according to any of claims 1 to 21.
CN202111386186.5A 2021-11-22 2021-11-22 Link configuration method and equipment Pending CN116156673A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202111386186.5A CN116156673A (en) 2021-11-22 2021-11-22 Link configuration method and equipment

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202111386186.5A CN116156673A (en) 2021-11-22 2021-11-22 Link configuration method and equipment

Publications (1)

Publication Number Publication Date
CN116156673A true CN116156673A (en) 2023-05-23

Family

ID=86360540

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202111386186.5A Pending CN116156673A (en) 2021-11-22 2021-11-22 Link configuration method and equipment

Country Status (1)

Country Link
CN (1) CN116156673A (en)

Similar Documents

Publication Publication Date Title
RU2713442C1 (en) Cell switching system and method
EP3637846B1 (en) Method and device for use in configuring novel quality of service architecture in dual connectivity system
CN109429368B (en) Message sending method, system, device, network element, storage medium and processor
US11018832B2 (en) Method for submitting data in sequence, network device and terminal device
US20230171823A1 (en) Information transmission method, network device and terminal
CN110662299B (en) Communication method, communication apparatus, and storage medium
WO2021213205A1 (en) Information transmission method and device, apparatus, and computer readable storage medium
WO2016184102A1 (en) Method and device for base station selection
CN110383937B (en) Method, baseband unit, UE and medium for connecting UE with RAN
US20210377779A1 (en) Radio station, radio communication method, non-transitory computer readable medium, and radio communication system
US20190182116A1 (en) Configuration Method, Network Device, and User Equipment
CN116156673A (en) Link configuration method and equipment
EP3641468B1 (en) Control methods, nodes and computer storage media
CN114554544B (en) Transmission method, notification method, transmission unit and network side equipment
KR20170094411A (en) Method for enhancing processing capability of base station, baseband device, base station, and system
CN111083699A (en) Key generation method and device, first network entity and base station equipment
CN112970229B (en) Method and equipment for analyzing wireless network flow
US20230012910A1 (en) Layer 2 measurement method and network side device
US20230199614A1 (en) Methods and apparatus of sidelink relay based data transmission with multiple paths
WO2022206544A1 (en) Data scheduling method and apparatus, and device
CN113875285B (en) Management of backhaul bearers for control plane signaling
WO2023098869A1 (en) State control method for secondary device, and related device
WO2023138446A1 (en) Data transmission method and network device
EP4161148A1 (en) Self-backhaul network switching method and apparatus, and network device
CN117459194A (en) Direct communication interface control information transmission method, terminal and storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination