Sidelink data transmission method, and device and readable storage medium

By determining the head format parameters and RLC channel configuration of the PC5 SRAP layer, the uncertainty problem of data transmission in the L2 U2U Relay scenario is solved, and the correct transmission of SL-SRB and SL-DRB data is achieved, which improves the reliability of transmission and efficiency.

WO2024235040A1PCT designated stage expired Publication Date: 2024-11-21VIVO MOBILE COMM CO LTD
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2024/091304
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-12
Filing Date
2024-05-07
Publication Date
2024-11-21

AI Technical Summary

Technical Problem

In the L2 U2U Relay scenario, the prior art does not clearly explain how the PC5 relay adapter layer specifically implements data forwarding and how related parameters are determined, resulting in uncertainty and error possibility of data transmission.

Method used

By determining the BEARER ID and UE ID in the header format of the PC5 SRAP layer, the RLC channel is configured with the relay terminal to ensure the correct transmission of SL-SRB and SL-DRB data, including in the first terminal and the relay terminal The appropriate RLC channel configuration is determined intermittently, and the data removal header format processing is performed in the second terminal.

Benefits of technology

It ensures the correct transmission of SL-SRB and SL-DRB data, improves the reliability and efficiency of data transmission, and solves the uncertainty problem in the data transmission process.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2024091304_21112024_PF_FP_ABST
    Figure CN2024091304_21112024_PF_FP_ABST
Patent Text Reader

Abstract

The present application belongs to the technical field of communications. Disclosed are a sidelink (SL) data transmission method, and a device and a readable storage medium. The method comprises: when SL-SRB data to be transmitted is present between a first user equipment (UE) and a second UE, the first UE executing at least one of the following operations according to an SRAP SDU: determining the value of a bearer identity (ID) in a header format of a PC5 SRAP layer, determining the value of a UE ID in the header format of the PC5 SRAP layer, and determining a first PC5 radio link control (RLC) channel between the first UE and a relay UE; and when SL-DRB data to be transmitted is present between the first UE and the second UE, the first UE executing at least one of the following operations according to dedicated configurations of the SRAP SDU and an SL-DRB: determining the value of the bearer ID in the header format of the PC5 SRAP layer, determining the value of the UE ID in the header format of the PC5 SRAP layer, and determining a second PC5 RLC channel between the first UE and the relay UE.
Need to check novelty before this filing date? Find Prior Art

Description

Secondary link data transmission method, device and readable storage medium

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to Chinese Patent Application No. 202310542631.5 filed in China on May 12, 2023, the entire contents of which are incorporated herein by reference. Technical Field

[0003] The present application belongs to the field of communication technology, and specifically relates to a side link data transmission method, device and readable storage medium. Background Art

[0004] In the Layer 2 U2U Relay (L2 U2U Relay) scenario, data between two remote UEs is forwarded via the PC5 Sidelink Relay Adaptation Protocol (SRAP). However, it is currently unclear how this process is implemented and how the relevant parameters are determined.

[0005] Summary of the Invention

[0006] The embodiments of the present application provide a side link data transmission method, device, and readable storage medium, which can determine the relevant parameters required to forward data through the PC5 relay adaptation layer and determine the transmission data channel.

[0007] In a first aspect, a secondary link data transmission method is provided, the method comprising:

[0008] In a case where SL-SRB data to be transmitted exists between a first terminal and a second terminal, the first terminal performs at least one of the following operations according to the SRAP SDU received from the first layer:

[0009] Determine the value of BEARER ID in the header format of the PC5 SRAP layer;

[0010] Determine the value of UE ID in the header format of the PC5 SRAP layer;

[0011] Determine a first PC5 RLC channel with the relay terminal;

[0012] The first layer is an upper layer of the PC5 SRAP layer of the first terminal.

[0013] In a second aspect, a secondary link data transmission method is provided, the method comprising:

[0014] In a case where SL-DRB data to be transmitted exists between a first terminal and a second terminal, the first terminal performs at least one of the following operations according to the SRAP SDU received from the first layer and the dedicated configuration of the SL-DRB:

[0015] Determine the value of BEARER ID in the header format of the PC5 SRAP layer;

[0016] Determine the value of UE ID in the header format of the PC5 SRAP layer;

[0017] Determine a second PC5 RLC channel with the relay terminal;

[0018] The first layer is an upper layer of the PC5 SRAP layer of the first terminal.

[0019] In a third aspect, a secondary link data transmission method is provided, the method comprising:

[0020] The relay terminal determines, based on the SRAP PDU received from the first terminal, a third PC5 RLC channel between the relay terminal and the second terminal, or the relay terminal determines, based on the SRAP PDU received from the first terminal and the dedicated configuration of the SL-DRB, a fourth PC5 RLC channel between the relay terminal and the second terminal;

[0021] The relay terminal delivers the SRAP PDU to the third PC5 RLC channel for transmission, or the relay terminal delivers the SRAP PDU to the fourth PC5 RLC channel for transmission;

[0022] The SL-DRB is an SL-DRB between the first terminal and the second terminal.

[0023] In a fourth aspect, a secondary link data transmission method is provided, the method comprising:

[0024] The second terminal removes the header format of the SRAP PDU received from the relay terminal and then delivers it to the target entity;

[0025] Alternatively, the second terminal removes a header format from the SRAP PDU and delivers it to the target entity based on the dedicated configuration of the SRAP PDU and SL-DRB received from the relay terminal;

[0026] The SL-DRB is an SL-DRB between the first terminal and the second terminal, and the target entity is an RRC entity or a PDCP entity of the second terminal.

[0027] In a fifth aspect, a secondary link data transmission device is provided, the device being applied to a first terminal, the device including:

[0028] The first execution module is configured to, when there is SL-SRB data to be transmitted between the first terminal and the second terminal, cause the first terminal to perform at least one of the following operations according to the SRAP SDU received from the first layer:

[0029] Determine the value of BEARER ID in the header format of the PC5 SRAP layer;

[0030] Determine the value of UE ID in the header format of the PC5 SRAP layer;

[0031] Determine a first PC5 RLC channel with the relay terminal;

[0032] The first layer is an upper layer of the PC5 SRAP layer of the first terminal.

[0033] In a sixth aspect, a secondary link data transmission device is provided, the device being applied to a first terminal, the device including:

[0034] The second execution module is configured to, when there is SL-DRB data to be transmitted between the first terminal and the second terminal, cause the first terminal to perform at least one of the following operations according to the SRAP SDU received from the first layer and the dedicated configuration of the SL-DRB:

[0035] Determine the value of BEARER ID in the header format of the PC5 SRAP layer;

[0036] Determine the value of UE ID in the header format of the PC5 SRAP layer;

[0037] Determine a second PC5 RLC channel with the relay terminal;

[0038] The first layer is an upper layer of the PC5 SRAP layer of the first terminal.

[0039] In a seventh aspect, a secondary link data transmission device is provided, the device being applied to a relay terminal, the device comprising:

[0040] a third execution module, configured for the relay terminal to determine, based on the SRAP PDU received from the first terminal, a third PC5 RLC channel between the relay terminal and the second terminal, or to determine, based on the SRAP PDU received from the first terminal and a dedicated configuration of the SL-DRB, a fourth PC5 RLC channel between the relay terminal and the second terminal;

[0041] The relay terminal delivers the SRAP PDU to the third PC5 RLC channel for transmission, or the relay terminal delivers the SRAP PDU to the fourth PC5 RLC channel for transmission;

[0042] The SL-DRB is an SL-DRB between the first terminal and the second terminal.

[0043] In an eighth aspect, a secondary link data transmission device is provided, the device being applied to a second terminal, the device including:

[0044] The fourth execution module is used to:

[0045] The second terminal removes the header format of the SRAP PDU received from the relay terminal and then delivers it to the target entity;

[0046] Alternatively, the second terminal removes a header format from the SRAP PDU and delivers it to the target entity based on the dedicated configuration of the SRAP PDU and SL-DRB received from the relay terminal;

[0047] The SL-DRB is an SL-DRB between the first terminal and the second terminal, and the target entity is an RRC entity or a PDCP entity of the second terminal.

[0048] In the ninth aspect, a terminal is provided, comprising a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the method described in the first aspect, or the steps of the method described in the second aspect, or the steps of the method described in the third aspect, or the steps of the method described in the fourth aspect are implemented.

[0049] In a tenth aspect, a terminal is provided, comprising a processor and a communication interface, wherein:

[0050] In the case where the terminal is the first terminal:

[0051] The processor is configured to, when there is SL-SRB data to be transmitted between the first terminal and the second terminal, perform, by the first terminal according to the SRAP SDU received from the first layer, at least one of the following operations:

[0052] Determine the value of BEARER ID in the header format of the PC5 SRAP layer;

[0053] Determine the value of UE ID in the header format of the PC5 SRAP layer;

[0054] Determine a first PC5 RLC channel with the relay terminal;

[0055] The first layer is an upper layer of the PC5 SRAP layer of the first terminal.

[0056] In the case where the terminal is the first terminal:

[0057] The processor is configured to, when there is SL-DRB data to be transmitted between a first terminal and a second terminal, perform, by the first terminal, at least one of the following operations according to the SRAP SDU received from the first layer and the dedicated configuration of the SL-DRB:

[0058] Determine the value of BEARER ID in the header format of the PC5 SRAP layer;

[0059] Determine the value of UE ID in the header format of the PC5 SRAP layer;

[0060] Determine a second PC5 RLC channel with the relay terminal;

[0061] The first layer is an upper layer of the PC5 SRAP layer of the first terminal.

[0062] In the case where the terminal is a relay terminal:

[0063] The processor is configured to determine, by the relay terminal, a third PC5 RLC channel between the relay terminal and the second terminal based on the SRAP PDU received from the first terminal, or determine, by the relay terminal, a fourth PC5 RLC channel between the relay terminal and the second terminal based on the SRAP PDU received from the first terminal and a dedicated configuration of the SL-DRB;

[0064] The relay terminal delivers the SRAP PDU to the third PC5 RLC channel for transmission, or the relay terminal delivers the SRAP PDU to the fourth PC5 RLC channel for transmission;

[0065] The SL-DRB is an SL-DRB between the first terminal and the second terminal.

[0066] In the case where the terminal is a second terminal:

[0067] The processor is configured to remove the header format of the SRAP PDU received from the relay terminal by the second terminal and then deliver the SRAP PDU to the target entity;

[0068] Alternatively, the second terminal removes a header format from the SRAP PDU and delivers it to the target entity based on the dedicated configuration of the SRAP PDU and SL-DRB received from the relay terminal;

[0069] The SL-DRB is an SL-DRB between the first terminal and the second terminal, and the target entity is an RRC entity or a PDCP entity of the second terminal.

[0070] In the eleventh aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented, or the steps of the method described in the second aspect are implemented, or the steps of the method described in the third aspect are implemented, or the steps of the method described in the fourth aspect are implemented.

[0071] In the twelfth aspect, a wireless communication system is provided, including: a first terminal, a relay terminal and a second terminal, wherein the first terminal can be used to execute the steps of the method described in the first aspect or the second aspect, the relay terminal can be used to execute the steps of the method described in the third aspect, and the second terminal can be used to execute the steps of the method described in the fourth aspect.

[0072] In the thirteenth aspect, a chip is provided, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps of the method described in the first aspect, or the steps of the method described in the second aspect, or the steps of the method described in the third aspect, or the steps of the method described in the fourth aspect.

[0073] In the fourteenth aspect, a computer program / program product is provided, which is stored in a storage medium and is executed by at least one processor to implement the steps of the method described in the first aspect, or the steps of the method described in the second aspect, or the steps of the method described in the third aspect, or the steps of the method described in the fourth aspect.

[0074] In an embodiment of the present application, when there is SL-SRB data to be transmitted between a first terminal and a second terminal, the first terminal performs at least one of the following operations based on the SRAP SDU: determining the value of the bearer identifier BEARER ID in the header format of the PC5 SRAP layer; determining the value of the terminal identifier UE ID in the header format of the PC5 SRAP layer; and determining a first PC5 radio link control channel RLC channel between the relay terminal. When there is SL-DRB data to be transmitted between the first terminal and the second terminal, the first terminal performs at least one of the following operations based on the SRAP SDU and the dedicated configuration of the SL-DRB: determining the value of the BEARER ID in the header format of the PC5 SRAP layer; determining the value of the UE ID in the header format of the PC5 SRAP layer; and determining a second PC5 RLC channel between the relay terminal. The header format content setting of the SL relay adaptation layer and how to determine the PC5 RLC channel configuration used for forwarding to the next hop are clarified, so that the remote UE and the L2 U2U relay UE can correctly deliver the data transmitted on the SL-SRB or SL-DRB, ensuring the correctness of data transmission and reception. BRIEF DESCRIPTION OF THE DRAWINGS

[0075] FIG1a is a block diagram of a wireless communication system applicable to embodiments of the present application;

[0076] Figure 1b is a schematic diagram of a Relay scenario based on the Sidelink wireless air interface;

[0077] Figure 1c is a schematic diagram of the L2 U2U relay protocol stack;

[0078] Figure 1d is the second schematic diagram of the L2 U2U relay protocol stack;

[0079] FIG2 is a flowchart of a secondary link data transmission method according to an embodiment of the present application;

[0080] FIG3 is a second flow chart of a secondary link data transmission method according to an embodiment of the present application;

[0081] FIG4 is a third flow chart of a secondary link data transmission method according to an embodiment of the present application;

[0082] FIG5 is a fourth flow chart of a secondary link data transmission method according to an embodiment of the present application;

[0083] FIG6 is a schematic diagram of a secondary link data transmission device according to an embodiment of the present application;

[0084] FIG7 is a second structural diagram of a secondary link data transmission device according to an embodiment of the present application;

[0085] FIG8 is a third structural diagram of a secondary link data transmission device according to an embodiment of the present application;

[0086] FIG9 is a fourth structural diagram of a secondary link data transmission device according to an embodiment of the present application;

[0087] FIG10 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0088] FIG11 is a schematic diagram of the structure of a terminal provided in an embodiment of the present application. DETAILED DESCRIPTION

[0089] The following will be combined with the accompanying drawings in the embodiments of this application to clearly describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field are within the scope of protection of this application.

[0090] The terms "first", "second", etc. in this application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable where appropriate, so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same type, and do not limit the number of objects, for example, the first object can be one or more. In addition, "or" in this application represents at least one of the connected objects. For example, "A or B" covers three options, namely, Option 1: including A but not including B; Option 2: including B but not including A; Option 3: including both A and B. The character " / " generally indicates that the objects associated before and after are in an "or" relationship.

[0091] The term "indication" in this application can be either a direct indication (or explicit indication) or an indirect indication (or implicit indication). A direct indication can be understood as the sender explicitly informing the receiver of specific information, the operation to be performed, or the requested result, etc. in the instruction sent; an indirect indication can be understood as the receiver determining the corresponding information based on the instruction sent by the sender, or making a judgment and determining the operation to be performed or the requested result, etc. based on the judgment result.

[0092] It is worth noting that the technology described in the embodiments of the present application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA) or other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the technology described can be used for the systems and radio technologies mentioned above, as well as for other systems and radio technologies. The following description describes a New Radio (NR) system for illustrative purposes, and NR terminology is used in most of the following description, but these technologies can also be applied to systems other than NR systems, such as 6th generation (6G) systems. th Generation, 6G) communication system.

[0093] FIG1a shows a block diagram of a wireless communication system applicable to an embodiment of the present application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 may be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), a notebook computer, a personal digital assistant (PDA), a handheld computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile internet device (MID), an augmented reality (AR), a virtual reality (VR) device, a robot, a wearable device (Wearable Device), an aircraft (flight vehicle), a vehicle user equipment (VUE), a ship-borne device, a pedestrian user equipment (PUE), a smart home (home appliances with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), a game console, a personal computer (PC), an ATM, or a self-service machine, or other terminal-side devices. Wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among them, the vehicle-mounted device can also be called a vehicle-mounted terminal, a vehicle-mounted controller, a vehicle-mounted module, a vehicle-mounted component, a vehicle-mounted chip or a vehicle-mounted unit, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application. The network side device 12 may include an access network device, wherein the access network device may also be called a radio access network (Radio Access Network, RAN) device, a radio access network function or a radio access network unit. The access network device may include a base station, a wireless local area network (Wireless Local Area Network, WLAN) access point (Access Point, AS) or a wireless fidelity (Wireless Fidelity, WiFi) node, etc.Among them, the base station can be referred to as Node B (NB), Evolved Node B (eNB), the next generation Node B (gNB), New Radio Node B (NR Node B), access point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), radio base station, radio transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home Evolved Node B (home evolved Node B), Transmission Reception Point (TRP) or other appropriate terms in the field. As long as the same technical effect is achieved, the base station is not limited to specific technical vocabulary. It should be noted that in the embodiment of the present application, only the base station in the NR system is used as an example for introduction, and the specific type of the base station is not limited.

[0094] To better understand the technical solution of this application, the following contents are first introduced:

[0095] 1. Introduction to Sidelink (SL)

[0096] Starting with Release 12, the Long Term Evolution (LTE) system supports sidelinks (SLs), which are used for direct data transmission between user equipment (UEs) without going through network equipment. SLs can also be translated as sidelinks or edge links.

[0097] LTE sidelink is designed for specific public safety matters (such as emergency communications in disaster areas such as fires or earthquakes) or vehicle-to-everything (V2X) communications. Vehicle-to-everything (V2X) communications include various services, such as basic safety communications, advanced (autonomous) driving, platooning, sensor expansion, etc. Since LTE sidelink only supports broadcast communications, it is mainly used for basic safety communications. Other advanced V2X services with strict quality of service (QoS) requirements in terms of latency and reliability will be supported through the 5G (5G) technology. thGeneration, 5G)NR sidelink support.

[0098] 2. NR Sidelink transmission mode

[0099] NR sidelink transmission types include broadcast (BC), groupcast (GC), and unicast (UC). Unicast, as the name suggests, is one-to-one transmission. Multicast is one-to-many transmission. Broadcast is also one-to-many transmission, but broadcast does not have the concept of UEs belonging to the same group.

[0100] 3. Sidelink-based U2U (UE-to-UE) relay mechanism

[0101] To achieve better coverage and terminal power saving, NR will study the relay mechanism based on the sidelink wireless air interface. A typical scenario is shown in Figure 1b, using a single-hop relay (only one U2U relay) as an example:

[0102] A source UE needs to transmit data to a target UE. However, due to poor coverage, a U2U relay UE is used to relay the data. The sidelink (PC5) interface between the relay UE and the source UE is used, and the sidelink (PC5) interface between the relay UE and the remote UE is also used. Generally speaking, the relay UE is open and can serve any source UE and target UE.

[0103] Here, the Source UE may also be referred to as Remote UE-1, and the Target UE may also be referred to as Destination UE or Remote UE-2.

[0104] In a multi-hop relay scenario, there is more than one U2U Relay. For example, if there are N hops, the packet will be transferred through N U2U Relays.

[0105] The L2 U2U relay protocol stack (taking a single hop as an example, signaling plane (Control Plane, CP), SL signaling radio bearer (SL-SRB) transmission) is shown in Figure 1c, and the L2 U2U relay protocol stack (taking a single hop as an example, user plane (User Plane, UP), SL data radio bearer (SL-DRB) transmission) is shown in Figure 1d.

[0106] The following describes in detail the secondary link data transmission method provided by the embodiment of the present application through some embodiments and their application scenarios in conjunction with the accompanying drawings.

[0107] It should be noted that the technical solution of the present application is aimed at a single-hop relay scenario, that is, the scenario shown in Figure 1b; the sending end is the first terminal, which can also be referred to as the sending terminal, Remote UE-1; the receiving end is the second terminal, which can also be referred to as the receiving terminal, Remote UE-2; the terminal used to transfer data is the relay terminal, which can also be referred to as Relay UE. The embodiments of the present application do not make specific limitations on this.

[0108] 2 , an embodiment of the present application provides a secondary link data transmission method, executed by a first terminal, and comprising:

[0109] Step 201: When there is SL-SRB data to be transmitted between a first terminal and a second terminal, the first terminal performs at least one of the following operations according to the SRAP SDU received from the first layer:

[0110] (1) Determine the value of the bearer ID in the header format of the PC5 SRAP layer;

[0111] (2) Determine the value of the terminal identifier (UE ID) in the header format of the PC5 SRAP layer;

[0112] (3) Determine a first PC5 Radio Link Control channel (RLC channel) with the relay terminal;

[0113] The first layer is an upper layer of the PC5 SRAP layer of the first terminal.

[0114] In an embodiment of the present application, the situation is that there is SL-SRB data to be transmitted between the first terminal and the second terminal. The SL-SRB data to be transmitted between the first terminal and the second terminal can be simply referred to as end-to-end (E2E) SL-SRB data.

[0115] In an embodiment of the present application, when there is SL-SRB data to be transmitted between the first terminal and the second terminal, the first terminal performs at least one of the following operations based on the SRAP signaling data unit (Signaling Data Unit, SDU): determining the value of the BEARER ID in the header format of the PC5 SRAP layer; determining the value of the UE ID in the header format of the PC5 SRAP layer; determining the first PC5 RLC channel between the relay terminal; for signaling plane data transmission, clarifying the header format content setting of the SL relay adaptation layer and how to determine the PC5 RLC channel configuration used to forward to the next hop, so that the Remote UE and the L2 U2U Relay UE can correctly deliver the data transmitted on the SL-SRB, ensuring the correctness of data transmission and reception.

[0116] It should be noted that the value of UE ID in the header format of the PC5 SRAP layer may include: 1) the value of the first terminal identifier 2) the value of the second terminal identifier 3) the value of the relay terminal identifier;

[0117] In one possible implementation, the method further includes:

[0118] The first terminal generates a SRAP data unit (Protocol Data Unit, PDU) according to the value of the BEARER ID or the value of the UE ID.

[0119] In one possible implementation, the method further includes:

[0120] The first terminal delivers the SRAP PDU generated according to the SRAP SDU to the first PC5 RLC channel for transmission.

[0121] In one possible implementation, the method further includes:

[0122] When a PC5 signaling (PC5-S) connection between the first terminal and the second terminal is established, the first terminal establishes a PC5 SRAP entity according to a PC5 SRAP configuration agreed upon in the protocol or by default;

[0123] The PC5 SRAP configuration includes the bearer identifier value of the SL-SRB.

[0124] Optionally, the bearer identifier value of the E2E SL-SRB specifically includes at least one of the following:

[0125] (1) The bearer identifier value of E2E SL-SRB0 is 0;

[0126] (2) The bearer identifier value of E2E SL-SRB1 is 1;

[0127] (3) The bearer identifier value of E2E SL-SRB2 is 2;

[0128] (4) The bearer identifier value of E2E SL-SRB3 is 3;

[0129] It should be noted that the embodiments of the present application include but are not limited to the standard E2E SL-SRB types 0, 1, 2, and 3; as an extension, the bearer identification value of E2E SL-SRBX can be X.

[0130] In a possible implementation, the first terminal determines, based on the SRAP SDU received from the first layer, a value of the BEARER ID in the header format of the PC5 SRAP layer, including:

[0131] The first terminal determines a value of the BEARER ID according to a type of data of the SL-SRB used to send the SRAP SDU;

[0132] The data category of each SL-SRB corresponds to a different BEARER ID value.

[0133] In an embodiment of the present application, the value of the BEARER ID is set according to the category of the data of the SL-SRB used to send the SRAP SDU, wherein it is necessary to ensure that the category of the data of each SL-SRB corresponds to a different value of the BEARER ID.

[0134] In a possible implementation, the first terminal determines a value of the BEARER ID according to a type of data of the SL-SRB used to send the SRAP SDU, including at least one of the following:

[0135] (1) When the SL-SRB data type is SL-SRB0 between the first terminal and the second terminal (i.e., secondary link signaling bearer 0 between Remote UE-1 and Remote UE-2), the value of BEARER ID is set to the first value;

[0136] (2) When the SL-SRB data type is SL-SRB1 between the first terminal and the second terminal (i.e., secondary link signaling bearer 1 between Remote UE-1 and Remote UE-2), the value of BEARER ID is set to the second value;

[0137] (3) When the SL-SRB data type is SL-SRB2 between the first terminal and the second terminal (i.e., secondary link signaling bearer 2 between Remote UE-1 and Remote UE-2), the value of BEARER ID is set to the third value;

[0138] (4) When the SL-SRB data type is SL-SRB3 between the first terminal and the second terminal (i.e., secondary link signaling bearer 3 between Remote UE-1 and Remote UE-2), the value of BEARER ID is set to the fourth value;

[0139] The first value, the second value, the third value, and the fourth value are different. Optionally, the first value is 0; the second value is 1; the third value is 2; and the fourth value is 3. It should be noted that the example of the BEARER ID value is only an example of an example in which the SL-SRB bearer identifier value is equal to the corresponding BEARER ID value. Optionally, other values ​​can be selected for the BEARER ID value, as long as the data category of each SL-SRB corresponds to a different BEARER ID value.

[0140] In a possible implementation manner, the value of the UE ID includes at least one of the following:

[0141] (1) UE identity of Remote UE-1, where the UE identity can be the local ID value assigned by PC5 RRC or the L2 ID value assigned by PC5-S;

[0142] (2) UE identity of Remote UE-2, where the UE identity can be the local ID value assigned by PC5 RRC or the L2 ID value assigned by PC5-S;

[0143] In one possible implementation, the first terminal determines, based on the SRAP SDU received from the first layer, a first PC5 RLC channel between the first terminal and the relay terminal, including:

[0144] (1) The first terminal determines the PC5 RLC channel configuration between the first terminal and the relay terminal according to the data type of the SL-SRB used to send the SRAP SDU;

[0145] (2) The first terminal determines the first PC5 RLC channel between the first terminal and the relay terminal according to the PC5 RLC channel configuration between the first terminal and the relay terminal.

[0146] In the embodiment of the present application, the PC5 RLC channel configuration between the corresponding relay terminal is determined according to the data type of the SL-SRB used to send the SRAP SDU.

[0147] In a possible implementation, the first terminal determines the PC5 RLC channel configuration according to the type of data of the SL-SRB used to send the SRAP SDU, including at least one of the following:

[0148] (1) When the type of the SL-SRB data is SL-SRB0 data between the first terminal and the second terminal, the PC5 RLC channel configuration is determined to be the first PC5 RLC channel configuration;

[0149] (2) When the type of the SL-SRB data is SL-SRB1 data between the first terminal and the second terminal, the PC5 RLC channel configuration is determined to be the second PC5 RLC channel configuration;

[0150] (3) When the type of the SL-SRB data is SL-SRB2 data between the first terminal and the second terminal, the PC5 RLC channel configuration is determined to be the third PC5 RLC channel configuration;

[0151] (4) When the type of the SL-SRB data is SL-SRB3 data between the first terminal and the second terminal, the PC5 RLC channel configuration is determined as the fourth PC5 RLC channel configuration.

[0152] In a possible implementation manner, any PC5 RLC channel configuration is a protocol-specified or default configuration, and any PC5 RLC channel configuration includes at least one of the following parameter values:

[0153] (1) RLC sequence number field length;

[0154] (2) RLC reassembly timer;

[0155] (3) RLC polling retransmission timer;

[0156] (4) RLC polling PDU;

[0157] (5) RLC polling byte;

[0158] (6) RLC maximum retransmission threshold

[0159] (7) RLC status prohibit timer;

[0160] (8) Logical channel identifier, which is used to uniquely identify the PC5 RLC channel;

[0161] (9) Media Access Control (MAC) logical channel priority;

[0162] (10) MAC priority bit rate;

[0163] (11) MAC logical channel group;

[0164] (12) MAC scheduling request identifier.

[0165] Optionally, the PC5 RLC channel configuration can be set as shown in Table 1:

[0166] Table 1

[0167] It should be noted that the specific information values ​​and descriptions in Table 1 above are only examples and do not constitute substantial limitations.

[0168] In a possible implementation, the PC5 RLC channel configurations corresponding to the data categories of different SL-SRBs are the same or different;

[0169] In the case of different PC5 RLC channel configurations, the logical channel identifier values ​​in different PC5 RLC channel configurations are different. That is, under the premise of different configurations, they are distinguished by different values ​​of logicalChannelIdentity in Table 1 above. For example, the first PC5 RLC channel configuration, the second PC5 RLC channel configuration, the third PC5 RLC channel configuration, and the fourth PC5 RLC channel configuration can be the same configuration or different configurations. Under the premise of different configurations, they are distinguished by setting different logicalChannelIdentity values, such as 59, 60, 61, and 62 respectively.

[0170] 3 , an embodiment of the present application provides a secondary link data transmission method, executed by a first terminal, and comprising:

[0171] Step 301: When there is SL-DRB data to be transmitted between a first terminal and a second terminal, the first terminal performs at least one of the following operations according to the SRAP SDU received from the first layer and the dedicated configuration of the SL-DRB:

[0172] (1) Determine the value of the BEARER ID in the header format of the PC5 SRAP layer;

[0173] (2) Determine the value of the UE ID in the header format of the PC5 SRAP layer;

[0174] (3) Determine the second PC5 RLC channel with the relay terminal;

[0175] The first layer is an upper layer of the PC5 SRAP layer of the first terminal.

[0176] In the embodiment of the present application, the situation is that there is SL-DRB data to be transmitted between the first terminal and the second terminal. The SL-DRB data to be transmitted between the first terminal and the second terminal can be simply referred to as E2E SL-DRB data.

[0177] In an embodiment of the present application, when there is SL-DRB data to be transmitted between the first terminal and the second terminal, the first terminal performs at least one of the following operations based on the SRAP SDU: determining the value of the BEARER ID in the header format of the PC5 SRAP layer; determining the value of the UE ID in the header format of the PC5 SRAP layer; determining the first PC5 RLC channel between the relay terminal; for user plane data transmission, clarifying the header format content setting of the SL relay adaptation layer and how to determine the PC5 RLC channel configuration used to forward to the next hop, so that the Remote UE and the L2 U2U Relay UE can correctly deliver the data transmitted on the SL-DRB, ensuring the correctness of data transmission and reception.

[0178] In one possible implementation, the method further includes:

[0179] The first terminal generates an SRAP PDU according to the value of the BEARER ID or the value of the UE ID.

[0180] In a possible implementation, the first terminal delivers the SRAP PDU generated according to the SRAP SDU to the second PC5 RLC channel for transmission.

[0181] In one possible implementation, the method further includes:

[0182] The first terminal obtains a dedicated configuration of the SL-DRB, where the dedicated configuration of the SL-DRB includes at least one of the following:

[0183] (1) SL-DRB configuration index value; for example: SLRB-PC5-ConfigIndex::=INTEGER(1..maxNrofSLRB-r16);

[0184] (2) configuration of the fifth PC5 RLC channel between the first terminal and the relay terminal;

[0185] (3) The association between the configuration index value of the SL-DRB and the configuration of the fifth PC5 RLC channel.

[0186] In an embodiment of the present application, the dedicated configuration of the above-mentioned SL-DRB can be obtained based on the PC5 RRC signaling interaction between UEs.

[0187] In one possible implementation, the first terminal determines the value of the BEARER ID in the header format of the PC5 SRAP layer according to the SRAP SDU and the dedicated configuration of the SL-DRB received from the first layer, including:

[0188] The first terminal sets the value of the BEARER ID to the configuration index value of the SL-DRB minus 1, or sets the value of the BEARER ID to the configuration index value of the SL-DRB minus 1 and partially truncates it.

[0189] In an embodiment of the present application, since the configuration index value of the SL-DRB is counted from 1, and the value of the BEARER ID is counted from 0 based on the bit information, in order to clearly correspond, the value of the BEARER ID is set to the configuration index value of the SL-DRB minus 1, or, after setting the value of the BEARER ID to the configuration index value of the SL-DRB minus 1, it is partially truncated, for example, it is set to the LSB 5-bit of {E2E SL-DRB configuration index value -1} to be compatible with the shorter SRAP PDU header format. Here, the "partial truncation" operation refers to binary encoding the value after the configuration index value of the SL-DRB is minus 1, taking the encoding of the lower N bits (N is a positive integer) to obtain the corresponding value. For example, when maxNrofSLRB-r16 = 512, N = 5, and the SL-DRB configuration index value is 391, the 9-bit binary encoding 0001 1000 0111 can be performed. The encoding of the lower 5 bits (0 0111) corresponds to the value 7. The value of the BEARER ID is then set to 7. The goal of the "partial truncation" operation is to further reduce the signaling overhead of the header format. Considering the total number of E2E SL-DRBs actually used by the first and second terminals when using the PC5 SRAP layer for transmission, the length of the BEARER ID can be designed to be N, where N is a positive integer less than or equal to 9.

[0190] In one possible implementation, the first terminal determines, based on the SRAP SDU received from the first layer and the dedicated configuration of the SL-DRB, a second PC5 RLC channel between the first terminal and the relay terminal, including:

[0191] (1) The first terminal determines the PC5 RLC channel configuration between the first terminal and the relay terminal as the fifth PC5 RLC channel configuration associated with the configuration index value of the SL-DRB;

[0192] (2) The first terminal determines the second PC5 RLC channel between the first terminal and the relay terminal according to the fifth PC5 RLC channel configuration.

[0193] It should be noted that when the BEARER ID values ​​of SL-SRB and SL-DRB can be shared (for example, the BEARER ID values ​​of both are 0, 1, 2, 3 as in the example above), the dedicated configuration of SL-DRB needs to ensure that the PC5 RLC channel configuration of SL-DRB is different from the PC5 RLC channel configuration of SL-SRB (for example, different values ​​of logicalChannelIdentity) to distinguish between SRB and DRB types.

[0194] 4 , an embodiment of the present application provides a secondary link data transmission method, which is executed by a relay terminal and includes:

[0195] Step 401: The relay terminal determines a third PC5 RLC channel between the relay terminal and the second terminal based on the SRAP PDU received from the first terminal, or the relay terminal determines a fourth PC5 RLC channel between the relay terminal and the second terminal based on the SRAP PDU received from the first terminal and the dedicated configuration of the SL-DRB.

[0196] Step 402: The relay terminal delivers the SRAP PDU to the third PC5 RLC channel for transmission, or the relay terminal delivers the SRAP PDU to the fourth PC5 RLC channel for transmission;

[0197] The SL-DRB is an SL-DRB between the first terminal and the second terminal.

[0198] In the embodiment of the present application, the relay terminal needs to determine, based on the SRAP PDU received from the first terminal, the PC5 RLC channel used for subsequent transmission of the SRAP PDU to the second terminal.

[0199] It is understandable that, since the data received from the first terminal may be SL-SRB data or SL-SRB data, the PC5 RLC channel used for subsequent transmission of the SRAP PDU to the second terminal also needs to be different.

[0200] In a possible implementation, the relay terminal determines, based on the SRAP PDU received from the first terminal, a third PC5 RLC channel between the relay terminal and the second terminal, including:

[0201] (1) When the value of the BEARER ID in the header format of the SRAP PDU is a value in the first set and the PC5 RLC channel for receiving the SRAP PDU is a protocol-agreed or default configuration, the relay terminal determines the PC5 RLC channel configuration between the relay terminal and the second terminal based on the value of the BEARER ID;

[0202] (2) The relay terminal determines a third PC5 RLC channel between the relay terminal and the second terminal according to the PC5 RLC channel configuration between the relay terminal and the second terminal;

[0203] The first set is a set of BEARER ID values ​​when transmitting SL-SRB data between the first terminal and the second terminal, such as 0, 1, 2, and 3 in the above example.

[0204] In the embodiment of the present application, since the relay terminal cannot directly know whether the SRAP PDU received from the first terminal is SL-SRB data or SL-DRB data, it is necessary to make a judgment based on the value of the BEARER ID in the header format of the SRAP PDU and the PC5 RLC channel of the received SRAP PDU;

[0205] The specific judgment process is: first look at the value of the BEARER ID in the header format of the SRAP PDU. If the value of the BEARER ID is a value in the first set, there may be two situations at this time. One is that the SRAP PDU transmits SL-SRB data, and the other is that the SRAP PDU transmits SL-DRB data. Because the BEARER ID values ​​of SL-SRB and SL-DRB can be shared, it is not enough to rely solely on the value of the BEARER ID in the header format of the SRAP PDU to determine the data type. Therefore, it is necessary to further determine the PC5 RLC channel for receiving the SRAP PDU. If the PC5 RLC channel for receiving the SRAP PDU is protocol-agreed or default-configured, it can be proved that the SRAP PDU transmits SL-SRB data. Accordingly, the PC5 RLC channel configuration between the second terminal can be directly determined based on the value of the BEARER ID.

[0206] In a possible implementation, when the SRAP PDU transmits SL-SRB data, the relay terminal determines the PC5 RLC channel configuration between the relay terminal and the second terminal based on the value of the BEARER ID, including:

[0207] (1) When the value of the BEARER ID is equal to 0, the relay terminal determines that the PC5 RLC channel configuration between the relay terminal and the second terminal is the first PC5 RLC channel configuration;

[0208] (2) When the value of the BEARER ID is equal to 1, the relay terminal determines that the PC5 RLC channel configuration between the relay terminal and the second terminal is the second PC5 RLC channel configuration;

[0209] (3) When the value of the BEARER ID is equal to 2, the relay terminal determines that the PC5 RLC channel configuration between the relay terminal and the second terminal is the third PC5 RLC channel configuration;

[0210] (4) When the value of the BEARER ID is equal to 3, the relay terminal determines that the PC5 RLC channel configuration between the relay terminal and the second terminal is the fourth PC5 RLC channel configuration.

[0211] In a possible implementation manner, any PC5 RLC channel configuration is a protocol-specified or default configuration, and any PC5 RLC channel configuration includes at least one of the following parameter values:

[0212] (1) RLC sequence number field length;

[0213] (2) RLC reassembly timer;

[0214] (3) RLC polling retransmission timer;

[0215] (4) RLC polling PDU;

[0216] (5) RLC polling byte;

[0217] (6) RLC maximum retransmission threshold

[0218] (7) RLC status prohibit timer;

[0219] (8) Logical channel identifier, which is used to uniquely identify the PC5 RLC channel;

[0220] (9) MAC logical channel priority;

[0221] (10) MAC priority bit rate;

[0222] (11) MAC logical channel group;

[0223] (12) MAC scheduling request identifier.

[0224] Optionally, the PC5 RLC channel configuration can be set as shown in Table 1 above:

[0225] In a possible implementation, the PC5 RLC channel configurations corresponding to the data categories of different SL-SRBs are the same or different;

[0226] In the case of different PC5 RLC channel configurations, the logical channel identifier values ​​in different PC5 RLC channel configurations are different. That is, under the premise of different configurations, they are distinguished by different values ​​of logicalChannelIdentity in Table 1 above. For example, the first PC5 RLC channel configuration, the second PC5 RLC channel configuration, the third PC5 RLC channel configuration, and the fourth PC5 RLC channel configuration can be the same configuration or different configurations. Under the premise of different configurations, they are distinguished by setting different logicalChannelIdentity values, such as 59, 60, 61, and 62 respectively.

[0227] In one possible implementation, the method further includes:

[0228] The relay terminal obtains the dedicated configuration of the SL-DRB. The dedicated configuration of the SL-DRB includes at least one of the following:

[0229] (1) SL-DRB configuration index value;

[0230] (2) configuration of the sixth PC5 RLC channel between the relay terminal and the second terminal;

[0231] (3) The association between the configuration index value of the SL-DRB and the configuration of the sixth PC5 RLC channel.

[0232] In one possible implementation, the relay terminal determines, based on the SRAP PDU and dedicated configuration of the SL-DRB received from the first terminal, a fourth PC5 RLC channel between the relay terminal and the second terminal, including:

[0233] (1) When the value of the BEARER ID in the header format of the SRAP PDU is a value in the first set and the PC5 RLC channel for receiving the SRAP PDU is not a protocol-agreed or default configuration, the relay terminal determines the PC5 RLC channel configuration between itself and the second terminal as the sixth PC5 RLC channel configuration associated with the configuration index value of the SL-DRB equal to the value of the BEARER ID plus 1;

[0234] (2) The relay terminal determines the fourth PC5 RLC channel between the relay terminal and the second terminal according to the configuration of the sixth PC5 RLC channel;

[0235] The first set is a set of BEARER ID values ​​when transmitting SL-SRB data between the first terminal and the second terminal.

[0236] In the embodiment of the present application, since the relay terminal cannot directly know whether the SRAP PDU received from the first terminal is SL-SRB data or SL-DRB data, it is necessary to make a judgment based on the value of the BEARER ID in the header format of the SRAP PDU and the PC5 RLC channel of the received SRAP PDU;

[0237] The specific judgment process is as follows: First, the BEARER ID value in the SRAP PDU header format is checked. If the BEARER ID value is in the first set, there are two possible situations: one is that the SRAP PDU is transmitting SL-SRB data, and the other is that the SRAP PDU is transmitting SL-DRB data. Because SL-SRB and SL-DRB can share the same BEARER ID value, relying solely on the BEARER ID value in the SRAP PDU header format is not sufficient to determine the data type. Therefore, the PC5 RLC channel used to receive the SRAP PDU must be further determined. If the PC5 RLC channel used to receive the SRAP PDU is not specified by the protocol or configured by default, it proves that the SRAP PDU is transmitting SL-DRB data. Accordingly, the PC5 RLC channel configuration between the relay terminal and the second terminal can be determined based on the BEARER ID value and the SL-DRB's dedicated configuration. Specifically, the relay terminal determines the PC5 RLC channel configuration between the relay terminal and the second terminal as the sixth PC5 RLC channel configuration associated with the SL-DRB configuration index value equal to the BEARER ID value plus 1.

[0238] In one possible implementation, the relay terminal determines the fourth PC5 RLC channel between the relay terminal and the second terminal according to the SRAP PDU and the dedicated configuration of the SL-DRB received from the first terminal, including:

[0239] (1) When the value of the BEARER ID in the header format of the SRAP PDU is not a value in the first set, the relay terminal determines the PC5 RLC channel configuration between the relay terminal and the second terminal as the sixth PC5 RLC channel configuration associated when the configuration index value of the SL-DRB is equal to the value of the BEARER ID plus 1;

[0240] (2) The relay terminal determines the fourth PC5 RLC channel between the relay terminal and the second terminal according to the configuration of the sixth PC5 RLC channel;

[0241] The first set is a set of BEARER ID values ​​when transmitting SL-SRB data between the first terminal and the second terminal.

[0242] In this embodiment of the present application, since the BEARER ID value in the SRAP PDU header format is not a value in the first set, the possibility that the SL-SRB and SL-DRB share the same BEARER ID value can be directly ruled out. Therefore, it can be directly determined that the SRAP PDU transmits SL-DRB data. Accordingly, the PC5 RLC channel configuration between the relay terminal and the second terminal can be determined based on the BEARER ID value and the dedicated configuration of the SL-DRB. Specifically, the relay terminal determines the PC5 RLC channel configuration between the relay terminal and the second terminal as the sixth PC5 RLC channel configuration associated when the configuration index value of the SL-DRB is equal to the BEARER ID value plus 1.

[0243] 5 , an embodiment of the present application provides a secondary link data transmission method, executed by a second terminal, including:

[0244] Step 501: The second terminal removes the header format of the SRAP PDU received from the relay terminal and then delivers it to the target entity;

[0245] Alternatively, the second terminal removes the header format of the SRAP PDU and delivers it to the target entity based on the dedicated configuration of the SRAP PDU and SL-DRB received from the relay terminal;

[0246] The SL-DRB is an SL-DRB between a first terminal and a second terminal, and the target entity is a Radio Resource Control (RRC) entity or a Packet Data Convergence Protocol (PDCP) entity of the second terminal.

[0247] In the embodiment of the present application, the second terminal needs to determine the target entity for subsequent delivery based on the SRAP PDU received from the relay terminal.

[0248] It is understandable that, since the data received from the relay terminal may be SL-SRB data or SL-SRB data, the target entity for subsequent delivery also needs to be different.

[0249] In a possible implementation, the second terminal removes the header format of the SRAP PDU received from the relay terminal and then delivers it to the target entity, including:

[0250] When the value of the BEARER ID in the header format of the SRAP PDU is a value in the first set and the PC5 RLC channel for receiving the SRAP PDU is a protocol agreement or a default configuration, the second terminal removes the header format of the SRAP PDU and submits it to the RRC entity of the second terminal;

[0251] The first set is a set of BEARER ID values ​​when transmitting SL-SRB data between the first terminal and the second terminal.

[0252] In the embodiment of the present application, since the second terminal cannot directly know whether the SRAP PDU received from the relay terminal is SL-SRB data or SL-DRB data, it is necessary to judge based on the value of the BEARER ID in the header format of the SRAP PDU and the PC5 RLC channel of the received SRAP PDU;

[0253] The specific judgment process is: first look at the value of the BEARER ID in the header format of the SRAP PDU. If the value of the BEARER ID is a value in the first set, there may be two situations at this time. One is that the SRAP PDU transmits SL-SRB data, and the other is that the SRAP PDU transmits SL-DRB data. Because the BEARER ID values ​​of SL-SRB and SL-DRB can be shared, it is not enough to rely solely on the value of the BEARER ID in the header format of the SRAP PDU to determine the data type. Therefore, it is necessary to further determine the PC5 RLC channel that receives the SRAP PDU. If the PC5 RLC channel that receives the SRAP PDU is agreed upon by the protocol or configured by default, it can be proved that the SRAP PDU transmits SL-SRB data. Accordingly, the SRAP PDU is removed from the header format and submitted to the RRC entity of the second terminal.

[0254] In one possible implementation, the method further includes:

[0255] The second terminal obtains a dedicated configuration of the SL-DRB, where the dedicated configuration of the SL-DRB includes at least one of the following:

[0256] (1) SL-DRB configuration index value;

[0257] (2) The association between the configuration index value of the SL-DRB and the PDCP entity configuration of the second terminal.

[0258] In a possible implementation, the second terminal removes the header format of the SRAP PDU and delivers it to the target entity according to the dedicated configuration of the SRAP PDU and SL-DRB received from the relay terminal, including:

[0259] (1) When the value of the BEARER ID in the header format of the SRAP PDU is a value in the first set and the PC5 RLC channel receiving the SRAP PDU is not a protocol agreement or a default configuration, the second terminal removes the header format of the SRAP PDU and delivers it to the PDCP entity of the second terminal associated with the SL-DRB whose configuration index value is equal to the value of the BEARER ID plus 1;

[0260] Alternatively, (2) when the value of the BEARER ID in the header format of the SRAP PDU is not a value in the first set, the second terminal removes the header format of the SRAP PDU and delivers it to the PDCP entity of the second terminal associated with the SL-DRB whose configuration index value is equal to the value of the BEARER ID plus 1;

[0261] The first set is a set of BEARER ID values ​​when transmitting SL-SRB data between the first terminal and the second terminal.

[0262] In the embodiment of the present application, since the second terminal cannot directly know whether the SRAP PDU received from the relay terminal is SL-SRB data or SL-DRB data, it is necessary to judge based on the value of the BEARER ID in the header format of the SRAP PDU and the PC5 RLC channel of the received SRAP PDU;

[0263] The specific judgment process is as follows: first look at the value of the BEARER ID in the header format of the SRAP PDU. If the value of the BEARER ID is a value in the first set, there may be two situations at this time. One is that the SRAP PDU transmits SL-SRB data, and the other is that the SRAP PDU transmits SL-DRB data. Because the BEARER ID value of SL-SRB and SL-DRB can be shared, it is not enough to rely solely on the value of the BEARER ID in the header format of the SRAP PDU to determine the data type. Therefore, it is necessary to further determine the PC5 RLC channel for receiving the SRAP PDU. If the PC5 RLC channel for receiving the SRAP PDU is not a protocol agreement or a default configuration, it can be proved that the SRAP PDU transmits SL-DRB data. Accordingly, the corresponding PDCP entity can be determined according to the dedicated configuration of the SL-DRB, and the SRAP PDU is removed from the header format and submitted to the PDCP entity. Specifically, the SRAP PDU is removed from the header format and submitted to the PDCP entity of the second terminal associated with the SL-DRB when the configuration index value is equal to the BEARER ID value plus 1;

[0264] If the value of the BEARER ID in the header format of the SRAP PDU is not a value in the first set, it can be directly ruled out that the BEARER ID value of SL-SRB and SL-DRB is shared. Therefore, it can be directly determined that the SRAP PDU transmits SL-DRB data. Accordingly, the corresponding PDCP entity can be determined according to the dedicated configuration of the SL-DRB, and the SRAP PDU is submitted to the PDCP entity after removing the header format. Specifically, the SRAP PDU is submitted to the PDCP entity of the second terminal associated with the SL-DRB when the configuration index value is equal to the BEARER ID value plus 1.

[0265] The secondary link data transmission method provided in the embodiment of the present application can be executed by a secondary link data transmission device. In the embodiment of the present application, the secondary link data transmission device performing the secondary link data transmission method is used as an example to illustrate the secondary link data transmission device provided in the embodiment of the present application.

[0266] 6 , an embodiment of the present application provides a secondary link data transmission device 600, which is applied to a first terminal and includes:

[0267] The first execution module 601 is configured to, when there is SL-SRB data to be transmitted between the first terminal and the second terminal, perform at least one of the following operations according to the SRAP SDU received from the first layer:

[0268] Determine the value of BEARER ID in the header format of the PC5 SRAP layer;

[0269] Determine the value of UE ID in the header format of the PC5 SRAP layer;

[0270] Determine a first PC5 RLC channel with the relay terminal;

[0271] The first layer is an upper layer of the PC5 SRAP layer of the first terminal.

[0272] Optionally, the device further comprises:

[0273] The first generating module is used for the first terminal to generate a secondary link relay adaptation layer protocol data unit SRAP PDU according to the value of the BEARER ID or the value of the UE ID.

[0274] Optionally, the device further comprises:

[0275] The first delivery module is used for the first terminal to deliver the SRAP PDU generated according to the SRAP SDU to the first PC5 RLC channel for transmission.

[0276] Optionally, the device further comprises:

[0277] an establishing module, configured to establish, when the PC5-S connection between the first terminal and the second terminal is established, the first terminal establishing a PC5 SRAP entity according to a PC5 SRAP configuration agreed upon in the protocol or by default;

[0278] The PC5 SRAP configuration includes the value of the SL-SRB BEARER ID.

[0279] Optionally, the first execution module is configured to:

[0280] The first terminal determines a value of the BEARER ID according to a type of data of the SL-SRB used to send the SRAP SDU;

[0281] The data category of each SL-SRB corresponds to a different BEARER ID value.

[0282] Optionally, the first execution module is configured to perform at least one of the following:

[0283] When the type of the SL-SRB data is SL-SRB0 data between the first terminal and the second terminal, the value of the BEARER ID is set to the first value;

[0284] When the type of the SL-SRB data is SL-SRB1 data between the first terminal and the second terminal, the value of the BEARER ID is set to the second value;

[0285] When the type of the SL-SRB data is SL-SRB2 data between the first terminal and the second terminal, the value of the BEARER ID is set to the third value;

[0286] When the type of the SL-SRB data is SL-SRB3 data between the first terminal and the second terminal, the value of the BEARER ID is set to the fourth value;

[0287] Among them, the first value, the second value, the third value and the fourth value are different.

[0288] Optionally, the first execution module is configured to:

[0289] The first terminal determines the PC5 RLC channel configuration between the first terminal and the relay terminal according to the type of the SL-SRB data used to send the SRAP SDU;

[0290] The first terminal determines a first PC5 RLC channel between the first terminal and the relay terminal according to the PC5 RLC channel configuration between the first terminal and the relay terminal.

[0291] Optionally, the first execution module is configured to perform at least one of the following:

[0292] When the type of the SL-SRB data is SL-SRB0 data between the first terminal and the second terminal, the PC5 RLC channel configuration is determined to be the first PC5 RLC channel configuration;

[0293] When the type of the SL-SRB data is SL-SRB1 data between the first terminal and the second terminal, the PC5 RLC channel configuration is determined to be a second PC5 RLC channel configuration;

[0294] When the type of the SL-SRB data is SL-SRB2 data between the first terminal and the second terminal, the PC5 RLC channel configuration is determined to be a third PC5 RLC channel configuration;

[0295] When the type of the SL-SRB data is SL-SRB3 data between the first terminal and the second terminal, the PC5 RLC channel configuration is determined as the fourth PC5 RLC channel configuration.

[0296] Optionally, any PC5 RLC channel configuration is a protocol-agreed or default configuration, and any PC5 RLC channel configuration includes at least one of the following parameter values:

[0297] RLC sequence number field length;

[0298] RLC reassembly timer;

[0299] RLC polling retransmission timer;

[0300] RLC polls PDU;

[0301] RLC polling byte;

[0302] RLC maximum retransmission threshold

[0303] RLC state prohibit timer;

[0304] Logical channel identifier, which is used to uniquely identify the PC5 RLC channel;

[0305] MAC logical channel priority;

[0306] MAC priority bit rate;

[0307] MAC logical channel group;

[0308] MAC scheduling request identifier.

[0309] Optionally,

[0310] The PC5 RLC channel configurations corresponding to the data types of different SL-SRBs are the same or different;

[0311] In the case of different PC5 RLC channel configurations, the values ​​of the logical channel identifiers in different PC5 RLC channel configurations are different.

[0312] 7 , an embodiment of the present application provides a secondary link data transmission device 700, which is applied to a first terminal and includes:

[0313] The second execution module 701 is configured to, when there is SL-DRB data to be transmitted between the first terminal and the second terminal, cause the first terminal to perform at least one of the following operations according to the SRAP SDU received from the first layer and the dedicated configuration of the SL-DRB:

[0314] Determine the value of BEARER ID in the header format of the PC5 SRAP layer;

[0315] Determine the value of UE ID in the header format of the PC5 SRAP layer;

[0316] Determine a second PC5 RLC channel with the relay terminal;

[0317] The first layer is an upper layer of the PC5 SRAP layer of the first terminal.

[0318] Optionally, the device further comprises:

[0319] The second generating module is used for the first terminal to generate an SRAP PDU according to the value of the BEARER ID or the value of the UE ID.

[0320] Optionally, the device further comprises:

[0321] A second delivery module is configured for the first terminal to deliver the SRAP PDU generated according to the SRAP SDU to the second PC5 RLC channel for transmission;

[0322] The first layer is an upper layer of the PC5 SRAP layer of the first terminal.

[0323] Optionally, the device further comprises:

[0324] A first acquisition module is configured for the first terminal to acquire a dedicated configuration of the SL-DRB. The dedicated configuration of the SL-DRB includes at least one of the following:

[0325] SL-DRB configuration index value;

[0326] A fifth PC5 RLC channel configuration between the first terminal and the relay terminal;

[0327] The association between the configuration index value of the SL-DRB and the configuration of the fifth PC5 RLC channel.

[0328] Optionally, the second execution module is configured to:

[0329] The first terminal sets the value of the BEARER ID to the configuration index value of the SL-DRB minus 1, or sets the value of the BEARER ID to the configuration index value of the SL-DRB minus 1 and partially truncates it.

[0330] Optionally, the second execution module is configured to:

[0331] The first terminal determines the PC5 RLC channel configuration between the first terminal and the relay terminal as the fifth PC5 RLC channel configuration associated with the configuration index value of the SL-DRB;

[0332] The first terminal determines, according to the fifth PC5 RLC channel configuration, a second PC5 RLC channel between the first terminal and the relay terminal.

[0333] 8 , an embodiment of the present application provides a secondary link data transmission device 800 , which is applied to a relay terminal and includes:

[0334] The third execution module 801 is configured to determine, by the relay terminal, a third PC5 RLC channel between the relay terminal and the second terminal based on the SRAP PDU received from the first terminal, or determine, by the relay terminal, a fourth PC5 RLC channel between the relay terminal and the second terminal based on the SRAP PDU received from the first terminal and a dedicated configuration of the SL-DRB;

[0335] The relay terminal delivers the SRAP PDU to the third PC5 RLC channel for transmission, or the relay terminal delivers the SRAP PDU to the fourth PC5 RLC channel for transmission;

[0336] The SL-DRB is an SL-DRB between the first terminal and the second terminal.

[0337] Optionally, the third execution module is configured to:

[0338] When the value of the BEARER ID in the header format of the SRAP PDU is a value in the first set and the PC5 RLC channel for receiving the SRAP PDU is a protocol-agreed or default configuration, the relay terminal determines the PC5 RLC channel configuration between the relay terminal and the second terminal according to the value of the BEARER ID;

[0339] The relay terminal determines, based on the PC5 RLC channel configuration between the relay terminal and the second terminal, a third PC5 RLC channel between the relay terminal and the second terminal;

[0340] The first set is a set of BEARER ID values ​​when transmitting SL-SRB data between the first terminal and the second terminal.

[0341] Optionally, the third execution module is configured to:

[0342] When the value of the BEARER ID is equal to 0, the relay terminal determines that the PC5 RLC channel configuration between the relay terminal and the second terminal is the first PC5 RLC channel configuration;

[0343] When the value of the BEARER ID is equal to 1, the relay terminal determines that the PC5 RLC channel configuration between the relay terminal and the second terminal is the second PC5 RLC channel configuration;

[0344] When the value of the BEARER ID is equal to 2, the relay terminal determines that the PC5 RLC channel configuration between the relay terminal and the second terminal is the third PC5 RLC channel configuration;

[0345] When the value of the BEARER ID is equal to 3, the relay terminal determines that the PC5 RLC channel configuration between the relay terminal and the second terminal is the fourth PC5 RLC channel configuration.

[0346] Optionally, any PC5 RLC channel configuration includes at least one of the following parameter values:

[0347] RLC sequence number field length;

[0348] RLC reassembly timer;

[0349] RLC polling retransmission timer;

[0350] RLC polls PDU;

[0351] RLC polling byte;

[0352] RLC maximum retransmission threshold

[0353] RLC state prohibit timer;

[0354] Logical channel identifier, which is used to uniquely identify the PC5 RLC channel;

[0355] MAC logical channel priority;

[0356] MAC priority bit rate;

[0357] MAC logical channel group;

[0358] MAC scheduling request identifier.

[0359] Optionally,

[0360] The PC5 RLC channel configurations corresponding to different BEARER ID values ​​are the same or different;

[0361] In the case of different PC5 RLC channel configurations, the values ​​of the logical channel identifiers in different PC5 RLC channel configurations are different.

[0362] Optionally, the device further comprises:

[0363] The second acquisition module is configured for the relay terminal to acquire a dedicated configuration of the SL-DRB. The dedicated configuration of the SL-DRB includes at least one of the following:

[0364] SL-DRB configuration index value;

[0365] a sixth PC5 RLC channel configuration between the relay terminal and the second terminal;

[0366] The association between the configuration index value of the SL-DRB and the configuration of the sixth PC5 RLC channel.

[0367] Optionally, the third execution module is configured to:

[0368] When the value of the BEARER ID in the header format of the SRAP PDU is a value in the first set and the PC5 RLC channel for receiving the SRAP PDU is not a protocol-agreed or default configuration, the relay terminal determines the PC5 RLC channel configuration between itself and the second terminal as the sixth PC5 RLC channel configuration associated with the configuration index value of the SL-DRB equal to the value of the BEARER ID plus 1;

[0369] The relay terminal determines, based on the sixth PC5 RLC channel configuration, a fourth PC5 RLC channel between the relay terminal and the second terminal;

[0370] The first set is a set of BEARER ID values ​​when transmitting SL-SRB data between the first terminal and the second terminal.

[0371] Optionally, the third execution module is configured to:

[0372] When the value of the BEARER ID in the header format of the SRAP PDU is not a value in the first set, the relay terminal determines the PC5 RLC channel configuration between the relay terminal and the second terminal as the sixth PC5 RLC channel configuration associated when the configuration index value of the SL-DRB is equal to the value of the BEARER ID plus 1;

[0373] The relay terminal determines, based on the sixth PC5 RLC channel configuration, a fourth PC5 RLC channel between the relay terminal and the second terminal;

[0374] The first set is a set of BEARER ID values ​​when transmitting SL-SRB data between the first terminal and the second terminal.

[0375] 9 , an embodiment of the present application provides a secondary link data transmission device 900, which is applied to a second terminal and includes:

[0376] The fourth execution module 901 is configured to:

[0377] The second terminal removes the header format of the SRAP PDU received from the relay terminal and then delivers it to the target entity;

[0378] Alternatively, the second terminal removes the header format of the SRAP PDU and delivers it to the target entity based on the dedicated configuration of the SRAP PDU and SL-DRB received from the relay terminal;

[0379] The SL-DRB is the SL-DRB between the first terminal and the second terminal, and the target entity is the RRC entity or PDCP entity of the second terminal.

[0380] Optionally, the fourth execution module is configured to:

[0381] When the value of the BEARER ID in the header format of the SRAP PDU is a value in the first set and the PC5 RLC channel for receiving the SRAP PDU is a protocol agreement or a default configuration, the second terminal removes the header format of the SRAP PDU and submits it to the RRC entity of the second terminal;

[0382] The first set is a set of BEARER ID values ​​when transmitting SL-SRB data between the first terminal and the second terminal.

[0383] Optionally, the device further comprises:

[0384] The third acquisition module is configured for the second terminal to acquire a dedicated configuration of the SL-DRB. The dedicated configuration of the SL-DRB includes at least one of the following:

[0385] SL-DRB configuration index value;

[0386] The association between the configuration index value of the SL-DRB and the PDCP entity configuration of the second terminal.

[0387] Optionally, the fourth execution module is configured to:

[0388] When the value of the BEARER ID in the header format of the SRAP PDU is a value in the first set and the PC5 RLC channel for receiving the SRAP PDU is not a protocol agreement or a default configuration, the second terminal removes the header format of the SRAP PDU and delivers it to the PDCP entity of the second terminal associated with the SL-DRB whose configuration index value is equal to the value of the BEARER ID plus 1;

[0389] or,

[0390] If the value of the BEARER ID in the header format of the SRAP PDU is not a value in the first set, the second terminal removes the header format of the SRAP PDU and delivers it to the PDCP entity of the second terminal associated with the SL-DRB configuration index value equal to the value of the BEARER ID plus 1;

[0391] The first set is a set of BEARER ID values ​​when transmitting SL-SRB data between the first terminal and the second terminal.

[0392] The secondary link data transmission device in the embodiment of the present application can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or chip. The electronic device can be a terminal, or it can be other devices other than a terminal. For example, the terminal can include but is not limited to the types of terminal 11 listed above, and other devices can be servers, network attached storage (NAS), etc., which are not specifically limited in the embodiment of the present application.

[0393] The side-link data transmission device provided in the embodiment of the present application can implement the various processes implemented in the method embodiments of Figures 2 to 5 and achieve the same technical effects. To avoid repetition, they will not be described here.

[0394] As shown in Figure 10, an embodiment of the present application further provides a communication device 1000, including a processor 1001 and a memory 1002. The memory 1002 stores a program or instruction that can be run on the processor 1001. For example, when the communication device 1000 is a terminal, the program or instruction is executed by the processor 1001 to implement the various steps of the above-mentioned embodiment of the side-link data transmission method, and can achieve the same technical effect. When the communication device 1000 is a network-side device, the program or instruction is executed by the processor 1001 to implement the various steps of the above-mentioned embodiment of the side-link data transmission method, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0395] The present application also provides a terminal including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to execute a program or instruction to implement the steps of the method embodiments shown in Figures 2 to 5. This terminal embodiment corresponds to the aforementioned terminal-side method embodiment, and each implementation process and implementation method of the aforementioned method embodiment can be applied to this terminal embodiment and achieve the same technical effects. Specifically, Figure 11 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of the present application.

[0396] The terminal 1100 includes but is not limited to: a radio frequency unit 1101, a network module 1102, an audio output unit 1103, an input unit 1104, a sensor 1105, a display unit 1106, a user input unit 1107, an interface unit 1108, a memory 1109 and at least some of the components of the processor 1110.

[0397] Those skilled in the art will appreciate that the terminal 1100 may also include a power supply (such as a battery) to power various components. The power supply may be logically connected to the processor 1110 via a power management system, thereby enabling the power management system to manage charging, discharging, and power consumption. The terminal structure shown in FIG11 does not limit the terminal. The terminal may include more or fewer components than shown, or combine certain components, or arrange the components differently, which will not be described in detail here.

[0398] It should be understood that in an embodiment of the present application, the input unit 1104 may include a graphics processing unit (GPU) 11041 and a microphone 11042, and the graphics processor 11041 processes the image data of a static picture or video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 1106 may include a display panel 11061, and the display panel 11061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 1107 includes a touch panel 11071 and at least one of other input devices 11072. The touch panel 11071 is also called a touch screen. The touch panel 11071 may include two parts: a touch detection device and a touch controller. Other input devices 11072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which will not be repeated here.

[0399] In the embodiment of the present application, after receiving downlink data from a network-side device, the RF unit 1101 may transmit the data to the processor 1110 for processing. Furthermore, the RF unit 1101 may send uplink data to the network-side device. Typically, the RF unit 1101 includes, but is not limited to, an antenna, an amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, and the like.

[0400] The memory 1109 can be used to store software programs or instructions and various data. The memory 1109 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, applications or instructions required for at least one function (such as a sound playback function, an image playback function, etc.). In addition, the memory 1109 may include a volatile memory or a non-volatile memory. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DRRAM). The memory 1109 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.

[0401] Processor 1110 may include one or more processing units. Optionally, processor 1110 integrates an application processor and a modem processor. The application processor primarily handles operations related to the operating system, user interface, and application programs, while the modem processor primarily processes wireless communication signals, such as a baseband processor. It is understood that the modem processor may not be integrated into processor 1110.

[0402] When terminal 1100 is the first terminal:

[0403] Processor 1110 is configured to, when there is SL-SRB data to be transmitted between the first terminal and the second terminal, perform, on the first terminal according to the SRAP SDU received from the first layer, at least one of the following operations:

[0404] Determine the value of BEARER ID in the header format of the PC5 SRAP layer;

[0405] Determine the value of UE ID in the header format of the PC5 SRAP layer;

[0406] Determine a first PC5 RLC channel with the relay terminal;

[0407] The first layer is an upper layer of the PC5 SRAP layer of the first terminal.

[0408] Optionally, the processor 1110 is configured to enable the first terminal to generate a secondary link relay adaptation layer protocol data unit (SRAP PDU) according to a value of the BEARER ID or a value of the UE ID.

[0409] Optionally, the processor 1110 is configured to enable the first terminal to deliver the SRAP PDU generated according to the SRAP SDU to the first PC5 RLC channel for transmission.

[0410] Optionally, the processor 1110 is configured to, when the PC5-S connection between the first terminal and the second terminal is established, establish, by the first terminal, a PC5 SRAP entity according to a PC5 SRAP configuration agreed upon in the protocol or by default;

[0411] The PC5 SRAP configuration includes the value of the SL-SRB BEARER ID.

[0412] Optionally, the processor 1110 is configured to:

[0413] The first terminal determines a value of the BEARER ID according to a type of data of the SL-SRB used to send the SRAP SDU;

[0414] The data category of each SL-SRB corresponds to a different BEARER ID value.

[0415] Optionally, the processor 1110 is configured to perform at least one of the following:

[0416] When the type of the SL-SRB data is SL-SRB0 data between the first terminal and the second terminal, the value of the BEARER ID is set to the first value;

[0417] When the type of the SL-SRB data is SL-SRB1 data between the first terminal and the second terminal, the value of the BEARER ID is set to the second value;

[0418] When the type of the SL-SRB data is SL-SRB2 data between the first terminal and the second terminal, the value of the BEARER ID is set to the third value;

[0419] When the type of the SL-SRB data is SL-SRB3 data between the first terminal and the second terminal, the value of the BEARER ID is set to the fourth value;

[0420] Among them, the first value, the second value, the third value and the fourth value are different.

[0421] Optionally, the processor 1110 is configured to:

[0422] The first terminal determines the PC5 RLC channel configuration between the first terminal and the relay terminal according to the type of the SL-SRB data used to send the SRAP SDU;

[0423] The first terminal determines a first PC5 RLC channel between the first terminal and the relay terminal according to the PC5 RLC channel configuration between the first terminal and the relay terminal.

[0424] Optionally, the processor 1110 is configured to perform at least one of the following:

[0425] When the type of the SL-SRB data is SL-SRB0 data between the first terminal and the second terminal, the PC5 RLC channel configuration is determined to be the first PC5 RLC channel configuration;

[0426] When the type of the SL-SRB data is SL-SRB1 data between the first terminal and the second terminal, the PC5 RLC channel configuration is determined to be a second PC5 RLC channel configuration;

[0427] When the type of the SL-SRB data is SL-SRB2 data between the first terminal and the second terminal, the PC5 RLC channel configuration is determined to be a third PC5 RLC channel configuration;

[0428] When the type of the SL-SRB data is SL-SRB3 data between the first terminal and the second terminal, the PC5 RLC channel configuration is determined as the fourth PC5 RLC channel configuration.

[0429] Optionally, any PC5 RLC channel configuration is a protocol-agreed or default configuration, and any PC5 RLC channel configuration includes at least one of the following parameter values:

[0430] RLC sequence number field length;

[0431] RLC reassembly timer;

[0432] RLC polling retransmission timer;

[0433] RLC polls PDU;

[0434] RLC polling byte;

[0435] RLC maximum retransmission threshold

[0436] RLC state prohibit timer;

[0437] Logical channel identifier, which is used to uniquely identify the PC5 RLC channel;

[0438] MAC logical channel priority;

[0439] MAC priority bit rate;

[0440] MAC logical channel group;

[0441] MAC scheduling request identifier.

[0442] Optionally,

[0443] The PC5 RLC channel configurations corresponding to the data types of different SL-SRBs are the same or different;

[0444] In the case of different PC5 RLC channel configurations, the values ​​of the logical channel identifiers in different PC5 RLC channel configurations are different.

[0445] When terminal 1100 is the first terminal:

[0446] Processor 1110 is configured to, when there is SL-DRB data to be transmitted between the first terminal and the second terminal, perform, at least one of the following operations, based on the SRAP SDU and the dedicated configuration of the SL-DRB received from the first layer:

[0447] Determine the value of BEARER ID in the header format of the PC5 SRAP layer;

[0448] Determine the value of UE ID in the header format of the PC5 SRAP layer;

[0449] Determine a second PC5 RLC channel with the relay terminal;

[0450] The first layer is an upper layer of the PC5 SRAP layer of the first terminal.

[0451] Optionally, the processor 1110 is configured to enable the first terminal to generate an SRAP PDU according to a value of a BEARER ID or a value of a UE ID.

[0452] Optionally, the processor 1110 is configured to deliver, by the first terminal, a SRAP PDU generated according to the SRAP SDU to a second PC5 RLC channel for transmission;

[0453] The first layer is an upper layer of the PC5 SRAP layer of the first terminal.

[0454] Optionally, the processor 1110 is configured to enable the first terminal to obtain a dedicated configuration of the SL-DRB, where the dedicated configuration of the SL-DRB includes at least one of the following:

[0455] SL-DRB configuration index value;

[0456] A fifth PC5 RLC channel configuration between the first terminal and the relay terminal;

[0457] The association between the configuration index value of the SL-DRB and the configuration of the fifth PC5 RLC channel.

[0458] Optionally, the processor 1110 is configured to:

[0459] The first terminal sets the value of the BEARER ID to the configuration index value of the SL-DRB minus 1, or sets the value of the BEARER ID to the configuration index value of the SL-DRB minus 1 and partially truncates it.

[0460] Optionally, the processor 1110 is configured to:

[0461] The first terminal determines the PC5 RLC channel configuration between the first terminal and the relay terminal as the fifth PC5 RLC channel configuration associated with the configuration index value of the SL-DRB;

[0462] The first terminal determines, according to the fifth PC5 RLC channel configuration, a second PC5 RLC channel between the first terminal and the relay terminal.

[0463] When terminal 1100 is a relay terminal:

[0464] Processor 1110 is configured to: determine, by the relay terminal, a third PC5 RLC channel between the relay terminal and the second terminal based on the SRAP PDU received from the first terminal; or determine, by the relay terminal, a fourth PC5 RLC channel between the relay terminal and the second terminal based on the SRAP PDU received from the first terminal and a dedicated configuration of the SL-DRB;

[0465] The relay terminal delivers the SRAP PDU to the third PC5 RLC channel for transmission, or the relay terminal delivers the SRAP PDU to the fourth PC5 RLC channel for transmission;

[0466] The SL-DRB is an SL-DRB between the first terminal and the second terminal.

[0467] Optionally, the processor 1110 is configured to:

[0468] When the value of the BEARER ID in the header format of the SRAP PDU is a value in the first set and the PC5 RLC channel for receiving the SRAP PDU is a protocol-agreed or default configuration, the relay terminal determines the PC5 RLC channel configuration between the relay terminal and the second terminal according to the value of the BEARER ID;

[0469] The relay terminal determines, based on the PC5 RLC channel configuration between the relay terminal and the second terminal, a third PC5 RLC channel between the relay terminal and the second terminal;

[0470] The first set is a set of BEARER ID values ​​when transmitting SL-SRB data between the first terminal and the second terminal.

[0471] Optionally, the processor 1110 is configured to:

[0472] When the value of the BEARER ID is equal to 0, the relay terminal determines that the PC5 RLC channel configuration between the relay terminal and the second terminal is the first PC5 RLC channel configuration;

[0473] When the value of the BEARER ID is equal to 1, the relay terminal determines that the PC5 RLC channel configuration between the relay terminal and the second terminal is the second PC5 RLC channel configuration;

[0474] When the value of the BEARER ID is equal to 2, the relay terminal determines that the PC5 RLC channel configuration between the relay terminal and the second terminal is the third PC5 RLC channel configuration;

[0475] When the value of the BEARER ID is equal to 3, the relay terminal determines that the PC5 RLC channel configuration between the relay terminal and the second terminal is the fourth PC5 RLC channel configuration.

[0476] Optionally, any PC5 RLC channel configuration includes at least one of the following parameter values:

[0477] RLC sequence number field length;

[0478] RLC reassembly timer;

[0479] RLC polling retransmission timer;

[0480] RLC polls PDU;

[0481] RLC polling byte;

[0482] RLC maximum retransmission threshold

[0483] RLC state prohibit timer;

[0484] Logical channel identifier, which is used to uniquely identify the PC5 RLC channel;

[0485] MAC logical channel priority;

[0486] MAC priority bit rate;

[0487] MAC logical channel group;

[0488] MAC scheduling request identifier.

[0489] Optionally,

[0490] The PC5 RLC channel configurations corresponding to different BEARER ID values ​​are the same or different;

[0491] In the case of different PC5 RLC channel configurations, the values ​​of the logical channel identifiers in different PC5 RLC channel configurations are different.

[0492] Optionally, the processor 1110 is configured to enable the relay terminal to obtain a dedicated configuration of the SL-DRB, where the dedicated configuration of the SL-DRB includes at least one of the following:

[0493] SL-DRB configuration index value;

[0494] a sixth PC5 RLC channel configuration between the relay terminal and the second terminal;

[0495] The association between the configuration index value of the SL-DRB and the configuration of the sixth PC5 RLC channel.

[0496] Optionally, the processor 1110 is configured to:

[0497] When the value of the BEARER ID in the header format of the SRAP PDU is a value in the first set and the PC5 RLC channel for receiving the SRAP PDU is not a protocol-agreed or default configuration, the relay terminal determines the PC5 RLC channel configuration between itself and the second terminal as the sixth PC5 RLC channel configuration associated with the configuration index value of the SL-DRB equal to the value of the BEARER ID plus 1;

[0498] The relay terminal determines, based on the sixth PC5 RLC channel configuration, a fourth PC5 RLC channel between the relay terminal and the second terminal;

[0499] The first set is a set of BEARER ID values ​​when transmitting SL-SRB data between the first terminal and the second terminal.

[0500] Optionally, the processor 1110 is configured to:

[0501] When the value of the BEARER ID in the header format of the SRAP PDU is not a value in the first set, the relay terminal determines the PC5 RLC channel configuration between the relay terminal and the second terminal as the sixth PC5 RLC channel configuration associated when the configuration index value of the SL-DRB is equal to the value of the BEARER ID plus 1;

[0502] The relay terminal determines, based on the sixth PC5 RLC channel configuration, a fourth PC5 RLC channel between the relay terminal and the second terminal;

[0503] The first set is a set of BEARER ID values ​​when transmitting SL-SRB data between the first terminal and the second terminal.

[0504] When terminal 1100 is the second terminal:

[0505] Processor 1110 is configured to:

[0506] The second terminal removes the header format of the SRAP PDU received from the relay terminal and then delivers it to the target entity;

[0507] Alternatively, the second terminal removes the header format of the SRAP PDU and delivers it to the target entity based on the dedicated configuration of the SRAP PDU and SL-DRB received from the relay terminal;

[0508] The SL-DRB is the SL-DRB between the first terminal and the second terminal, and the target entity is the RRC entity or PDCP entity of the second terminal.

[0509] Optionally, the processor 1110 is configured to:

[0510] When the value of the BEARER ID in the header format of the SRAP PDU is a value in the first set and the PC5 RLC channel for receiving the SRAP PDU is a protocol agreement or a default configuration, the second terminal removes the header format of the SRAP PDU and submits it to the RRC entity of the second terminal;

[0511] The first set is a set of BEARER ID values ​​when transmitting SL-SRB data between the first terminal and the second terminal.

[0512] Optionally, the processor 1110 is configured to enable the second terminal to obtain a dedicated configuration of the SL-DRB, where the dedicated configuration of the SL-DRB includes at least one of the following:

[0513] SL-DRB configuration index value;

[0514] The association between the configuration index value of the SL-DRB and the PDCP entity configuration of the second terminal.

[0515] Optionally, the processor 1110 is configured to:

[0516] When the value of the BEARER ID in the header format of the SRAP PDU is a value in the first set and the PC5 RLC channel for receiving the SRAP PDU is not a protocol agreement or a default configuration, the second terminal removes the header format of the SRAP PDU and delivers it to the PDCP entity of the second terminal associated with the SL-DRB whose configuration index value is equal to the value of the BEARER ID plus 1;

[0517] or,

[0518] If the value of the BEARER ID in the header format of the SRAP PDU is not a value in the first set, the second terminal removes the header format of the SRAP PDU and delivers it to the PDCP entity of the second terminal associated with the SL-DRB configuration index value equal to the value of the BEARER ID plus 1;

[0519] The first set is a set of BEARER ID values ​​when transmitting SL-SRB data between the first terminal and the second terminal.

[0520] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by the processor, the various processes of the above-mentioned embodiment of the sub-link data transmission method are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0521] The processor is the processor in the terminal described in the above embodiment. The readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk. In some examples, the readable storage medium may be a non-transitory readable storage medium.

[0522] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned embodiment of the sub-link data transmission method, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0523] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0524] An embodiment of the present application further provides a computer program / program product, which is stored in a storage medium. The computer program / program product is executed by at least one processor to implement the various processes of the above-mentioned side-link data transmission method embodiment and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0525] An embodiment of the present application also provides a wireless communication system, including: a first terminal, a relay terminal and a second terminal, wherein the first terminal can be used to execute the steps of the first terminal side method as described above, the relay terminal can be used to execute the steps of the relay terminal side method as described above, and the second terminal can be used to execute the steps of the second terminal side method as described above.

[0526] It should be noted that, in this article, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device comprising the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in the opposite order according to the functions involved. For example, the described method may be performed in an order different from that described, and various steps may also be added, omitted or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0527] Through the description of the above embodiments, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of a computer software product plus a hardware platform, or of course, by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes a number of instructions for enabling a terminal or network-side device to execute the methods described in each embodiment of the present application.

[0528] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of this application, ordinary technicians in this field can also make many forms of implementation methods without departing from the purpose of this application and the scope of protection of the claims. These implementation methods are all within the protection of this application.

Claims

1. A secondary link data transmission method, the method include: In a case where there is data of a secondary link signaling radio bearer SL-SRB to be transmitted between the first terminal and the second terminal, the first terminal performs at least one of the following operations according to a secondary link relay adaptation layer signaling data unit SRAP SDU received from the first layer: Determine the value of the bearer identifier BEARER ID in the header format of the PC5 SRAP layer; Determine the value of the terminal identifier UE ID in the header format of the PC5 SRAP layer; Determine a first PC5 radio link control channel RLC channel between the relay terminal; The first layer is an upper layer of the PC5 SRAP layer of the first terminal.

2. The method according to claim 1, in, The method further comprises: The first terminal generates a secondary link relay adaptation layer protocol data unit SRAP PDU according to the value of the BEARER ID or the value of the UE ID.

3. The method according to claim 1, in, The method further comprises: The first terminal delivers the SRAP PDU generated according to the SRAP SDU to the first PC5 RLC channel for transmission.

4. The method according to claim 1, in, The method further comprises: When the PC5-S connection between the first terminal and the second terminal is established, the first terminal establishes a PC5 SRAP entity according to a PC5 SRAP configuration agreed upon in the protocol or by default; The PC5 SRAP configuration includes the bearer identification value of the SL-SRB.

5. The method according to claim 1, in, The first terminal determines, according to the SRAP SDU received from the first layer, a value of a BEARER ID in a header format of a PC5 SRAP layer, including: The first terminal determines a value of the BEARER ID according to a type of data of the SL-SRB used to send the SRAP SDU; The data category of each SL-SRB corresponds to different BEARER ID values.

6. The method according to claim 5, in, The first terminal determines the value of the BEARER ID according to the type of data of the SL-SRB used to send the SRAP SDU, including at least one of the following: When the category of the SL-SRB data is SL-SRB0 data between the first terminal and the second terminal, setting the value of the BEARER ID to a first value; When the category of the SL-SRB data is SL-SRB1 data between the first terminal and the second terminal, setting the value of the BEARER ID to a second value; When the category of the SL-SRB data is SL-SRB2 data between the first terminal and the second terminal, setting the value of the BEARER ID to a third value; When the category of the SL-SRB data is SL-SRB3 data between the first terminal and the second terminal, setting the value of the BEARER ID to a fourth value; The first value, the second value, the third value and the fourth value are different.

7. The method according to claim 1, in, The first terminal determines, according to the SRAP SDU received from the first layer, a first PC5 RLC channel between the first terminal and the relay terminal, including: The first terminal determines the PC5 RLC channel configuration between the first terminal and the relay terminal according to the type of data of the SL-SRB used to send the SRAP SDU; The first terminal determines a first PC5 RLC channel between the first terminal and the relay terminal according to a PC5 RLC channel configuration between the first terminal and the relay terminal.

8. The method according to claim 7, in, The first terminal determines the PC5 RLC channel configuration according to the type of data of the SL-SRB used to send the SRAP SDU, including at least one of the following: In a case where the category of the SL-SRB data is SL-SRB0 data between the first terminal and the second terminal, determining the PC5 RLC channel configuration as a first PC5 RLC channel configuration; In a case where the category of the SL-SRB data is SL-SRB1 data between the first terminal and the second terminal, determining the PC5 RLC channel configuration as a second PC5 RLC channel configuration; In a case where the category of the SL-SRB data is SL-SRB2 data between the first terminal and the second terminal, determining the PC5 RLC channel configuration as a third PC5 RLC channel configuration; In a case where the type of the SL-SRB data is SL-SRB3 data between the first terminal and the second terminal, the PC5 RLC channel configuration is determined as a fourth PC5 RLC channel configuration.

9. The method according to claim 7, in, Any of the PC5 RLC channel configurations is a protocol agreed or default configuration, and any of the PC5 RLC channel configurations includes at least one of the following parameter values: RLC sequence number field length; RLC reassembly timer; RLC polling retransmission timer; RLC polls PDU; RLC polling byte; RLC maximum retransmission threshold RLC state prohibit timer; A logical channel identifier, where the logical channel identifier is used to uniquely identify a PC5 RLC channel; MAC logical channel priority; MAC priority bit rate; MAC logical channel group; MAC scheduling request identifier.

10. The method according to claim 9, in, The PC5 RLC channel configurations corresponding to the data categories of different SL-SRBs are the same or different; When the PC5 RLC channel configurations are different, the values ​​of the logical channel identifiers in different PC5 RLC channel configurations are different.

11. A secondary link data transmission method, the method include: In a case where there is data of the SL-DRB to be transmitted between the first terminal and the second terminal, the first terminal performs at least one of the following operations according to the SRAP SDU received from the first layer and the dedicated configuration of the SL-DRB: Determine the value of BEARER ID in the header format of the PC5 SRAP layer; Determine the value of UE ID in the header format of the PC5 SRAP layer; Determine a second PC5 RLC channel with the relay terminal; The first layer is an upper layer of the PC5 SRAP layer of the first terminal.

12. The method according to claim 11, in, The method further comprises: The first terminal generates a SRAP PDU according to the value of the BEARER ID or the value of the UE ID.

13. The method according to claim 11, in, The method further comprises: The first terminal delivers the SRAP PDU generated according to the SRAP SDU to the second PC5 RLC channel for transmission.

14. The method according to claim 11, in, The method further comprises: The first terminal obtains a dedicated configuration of the SL-DRB, where the dedicated configuration of the SL-DRB includes at least one of the following: The configuration index value of the SL-DRB; a fifth PC5 RLC channel configuration between the first terminal and the relay terminal; The association between the configuration index value of the SL-DRB and the configuration of the fifth PC5 RLC channel.

15. The method according to claim 14, in, The first terminal determines the value of the BEARER ID in the header format of the PC5 SRAP layer according to the SRAP SDU received from the first layer and the dedicated configuration of the SL-DRB, including: The first terminal sets the value of the BEARER ID to the configuration index value of the SL-DRB minus 1, or sets the value of the BEARER ID to the configuration index value of the SL-DRB minus 1 and partially truncates it.

16. The method according to claim 14, in, The first terminal determines, according to the SRAP SDU received from the first layer and the dedicated configuration of the SL-DRB, a second PC5 RLC channel between the first terminal and the relay terminal, including: The first terminal determines the PC5 RLC channel configuration between the first terminal and the relay terminal as the fifth PC5 RLC channel configuration associated with the configuration index value of the SL-DRB; The first terminal determines a second PC5 RLC channel between the first terminal and the relay terminal according to the fifth PC5 RLC channel configuration.

17. A secondary link data transmission method, the method include: The relay terminal determines the third PC5 RLC channel between the relay terminal and the second terminal according to the SRAP PDU received from the first terminal, or the relay terminal determines the fourth PC5 RLC channel between the relay terminal and the second terminal according to the SRAP PDU received from the first terminal and the dedicated configuration of the SL-DRB; The relay terminal delivers the SRAP PDU to the third PC5 RLC channel for transmission, or the relay terminal delivers the SRAP PDU to the fourth PC5 RLC channel for transmission; The SL-DRB is a SL-DRB between the first terminal and the second terminal.

18. The method according to claim 17, in, The relay terminal determines, according to the SRAP PDU received from the first terminal, a third PC5 RLC channel between the relay terminal and the second terminal, including: When the value of the BEARER ID in the header format of the SRAP PDU is a value in the first set and the PC5 RLC channel for receiving the SRAP PDU is a protocol agreement or a default configuration, the relay terminal determines the PC5 RLC channel configuration between the relay terminal and the second terminal according to the value of the BEARER ID; The relay terminal determines, according to the PC5 RLC channel configuration between the relay terminal and the second terminal, a third PC5 RLC channel between the relay terminal and the second terminal; The first set is a set of values ​​of the BEARER ID when transmitting SL-SRB data between the first terminal and the second terminal.

19. The method according to claim 18, in, The relay terminal determines the PC5 RLC channel configuration between the relay terminal and the second terminal according to the value of the BEARER ID, including: When the value of the BEARER ID is equal to 0, the relay terminal determines that the PC5 RLC channel configuration between the relay terminal and the second terminal is the first PC5 RLC channel configuration; When the value of the BEARER ID is equal to 1, the relay terminal determines that the PC5 RLC channel configuration between the relay terminal and the second terminal is the second PC5 RLC channel configuration; When the value of the BEARER ID is equal to 2, the relay terminal determines that the PC5 RLC channel configuration between the relay terminal and the second terminal is a third PC5 RLC channel configuration; When the value of the BEARER ID is equal to 3, the relay terminal determines that the PC5 RLC channel configuration between the relay terminal and the second terminal is the fourth PC5 RLC channel configuration.

20. The method according to claim 18, in, Any of the PC5 RLC channel configurations includes at least one of the following parameter values: RLC sequence number field length; RLC reassembly timer; RLC polling retransmission timer; RLC polls PDU; RLC polling byte; RLC maximum retransmission threshold RLC state prohibit timer; A logical channel identifier, where the logical channel identifier is used to uniquely identify a PC5 RLC channel; MAC logical channel priority; MAC priority bit rate; MAC logical channel group; MAC scheduling request identifier.

21. The method according to claim 20, in, The PC5 RLC channel configurations corresponding to different BEARER ID values ​​are the same or different; Among them, when the PC5 RLC channel configuration is different, the value of the logical channel identifier in different PC5 RLC channel configurations is different.

22. The method according to claim 17, in, The method further comprises: The relay terminal obtains the dedicated configuration of the SL-DRB, where the dedicated configuration of the SL-DRB includes at least one of the following: The configuration index value of the SL-DRB; a sixth PC5 RLC channel configuration between the relay terminal and the second terminal; The association between the configuration index value of the SL-DRB and the configuration of the sixth PC5 RLC channel.

23. The method according to claim 22, in, The relay terminal determines, according to the SRAP PDU received from the first terminal and the dedicated configuration of the SL-DRB, a fourth PC5 RLC channel between the relay terminal and the second terminal, including: When the value of the BEARER ID in the header format of the SRAP PDU is a value in the first set and the PC5 RLC channel for receiving the SRAP PDU is not a protocol agreement or a default configuration, the relay terminal determines the PC5 RLC channel configuration between the relay terminal and the second terminal as the sixth PC5 RLC channel configuration associated when the configuration index value of the SL-DRB is equal to the value of the BEARER ID plus 1; The relay terminal determines, according to the sixth PC5 RLC channel configuration, a fourth PC5 RLC channel between the relay terminal and the second terminal; The first set is a set of values ​​of the BEARER ID when transmitting SL-SRB data between the first terminal and the second terminal.

24. The method according to claim 22, in, The relay terminal determines, according to the SRAP PDU received from the first terminal and the dedicated configuration of the SL-DRB, a fourth PC5 RLC channel between the relay terminal and the second terminal, including: When the value of the BEARER ID in the header format of the SRAP PDU is not a value in the first set, the relay terminal determines the PC5 RLC channel configuration between the relay terminal and the second terminal as the sixth PC5 RLC channel configuration associated when the configuration index value of the SL-DRB is equal to the value of the BEARER ID plus 1; The relay terminal determines, according to the sixth PC5 RLC channel configuration, a fourth PC5 RLC channel between the relay terminal and the second terminal; The first set is a set of values ​​of the BEARER ID when transmitting SL-SRB data between the first terminal and the second terminal.

25. A secondary link data transmission method, the method include: The second terminal removes the header format of the SRAP PDU received from the relay terminal and then submits it to the target entity; Alternatively, the second terminal removes the header format of the SRAP PDU and submits it to the target entity according to the dedicated configuration of the SRAP PDU and SL-DRB received from the relay terminal; The SL-DRB is a SL-DRB between the first terminal and the second terminal, and the target entity is a radio resource control RRC entity or a packet data convergence protocol PDCP entity of the second terminal.

26. The method according to claim 25, in, The second terminal removes a header format of the SRAP PDU received from the relay terminal and submits the SRAP PDU to the target entity, including: When the value of the BEARER ID in the header format of the SRAP PDU is a value in the first set and the PC5 RLC channel for receiving the SRAP PDU is a protocol agreement or a default configuration, the second terminal removes the header format of the SRAP PDU and submits it to the RRC entity of the second terminal; The first set is a set of values ​​of the BEARER ID when transmitting SL-SRB data between the first terminal and the second terminal.

27. The method according to claim 25, in, The method further comprises: The second terminal obtains a dedicated configuration of the SL-DRB, where the dedicated configuration of the SL-DRB includes at least one of the following: The configuration index value of the SL-DRB; The association between the configuration index value of the SL-DRB and the PDCP entity configuration of the second terminal.

28. The method according to claim 27, in, The second terminal removes a header format of the SRAP PDU and submits it to the target entity according to the SRAP PDU received from the relay terminal and the dedicated configuration of the SL-DRB, including: When the value of the BEARER ID in the header format of the SRAP PDU is a value in the first set and the PC5 RLC channel receiving the SRAP PDU is not a protocol agreement or a default configuration, the second terminal removes the header format of the SRAP PDU and submits it to the PDCP entity of the second terminal associated with the configuration index value of the SL-DRB equal to the value of the BEARER ID plus 1; or, In the case where the value of the BEARER ID in the header format of the SRAP PDU is not a value in the first set, the second terminal removes the header format of the SRAP PDU and submits it to the PDCP entity of the second terminal associated with the configuration index value of the SL-DRB equal to the value of the BEARER ID plus 1; The first set is a set of values ​​of the BEARER ID when transmitting SL-SRB data between the first terminal and the second terminal.

29. A secondary link data transmission device, the device being applied to a first terminal, the device include: The first execution module is configured to, when there is SL-SRB data to be transmitted between the first terminal and the second terminal, cause the first terminal to perform at least one of the following operations according to the SRAP SDU received from the first layer: Determine the value of BEARER ID in the header format of the PC5 SRAP layer; Determine the value of UE ID in the header format of the PC5 SRAP layer; Determine a first PC5 RLC channel with the relay terminal; The first layer is an upper layer of the PC5 SRAP layer of the first terminal.

30. A secondary link data transmission device, the device being applied to a first terminal, the device include: The second execution module is configured to, when there is SL-DRB data to be transmitted between the first terminal and the second terminal, the first terminal performing at least one of the following operations according to the SRAP SDU received from the first layer and the dedicated configuration of the SL-DRB: Determine the value of BEARER ID in the header format of the PC5 SRAP layer; Determine the value of UE ID in the header format of the PC5 SRAP layer; Determine a second PC5 RLC channel with the relay terminal; The first layer is an upper layer of the PC5 SRAP layer of the first terminal.

31. A secondary link data transmission device, the device is applied to a relay terminal, the device include: A third execution module is used for the relay terminal to determine the third PC5 RLC channel between the relay terminal and the second terminal according to the SRAP PDU received from the first terminal, or the relay terminal to determine the fourth PC5 RLC channel between the relay terminal and the second terminal according to the SRAP PDU received from the first terminal and the dedicated configuration of the SL-DRB; The relay terminal delivers the SRAP PDU to the third PC5 RLC channel for transmission, or the relay terminal delivers the SRAP PDU to the fourth PC5 RLC channel for transmission; The SL-DRB is a SL-DRB between the first terminal and the second terminal.

32. A secondary link data transmission device, the device is applied to a second terminal, the device include: The fourth execution module is used for: The second terminal removes the header format of the SRAP PDU received from the relay terminal and then submits it to the target entity; Alternatively, the second terminal removes the header format of the SRAP PDU and submits it to the target entity according to the dedicated configuration of the SRAP PDU and SL-DRB received from the relay terminal; The SL-DRB is a SL-DRB between the first terminal and the second terminal, and the target entity is an RRC entity or a PDCP entity of the second terminal.

33. A terminal comprising a processor and a memory, in, The memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the steps of the side-link data transmission method as described in any one of claims 1 to 10 are implemented, or, when executed, the steps of the side-link data transmission method as described in any one of claims 11 to 16 are implemented, or, when executed, the steps of the side-link data transmission method as described in any one of claims 17 to 24 are implemented, or, when executed, the steps of the side-link data transmission method as described in any one of claims 25 to 28 are implemented.

34. A readable storage medium storing a program or an instruction, in, When the program or instruction is executed by the processor, it implements the steps of the side-link data transmission method as described in any one of claims 1 to 10, or, when executed, it implements the steps of the side-link data transmission method as described in any one of claims 11 to 16, or, when executed, it implements the steps of the side-link data transmission method as described in any one of claims 17 to 24, or, when executed, it implements the steps of the side-link data transmission method as described in any one of claims 25 to 28.

Citation Information

Patent Citations

  • Method and device for relay transmission

    CN108886682A

  • Sidelink relay communication method and device, equipment and medium

    CN111901847A

  • Information transmission method, device and equipment and computer readable storage medium

    CN113543367A

  • Remote terminal service identification method, apparatus and device, and storage medium

    CN114630389A

  • Data transmission method and related device

    CN115996108A