Secondary link data transmission method and device and readable storage medium
By determining the header format content and RLC channel configuration of the PC5 SRAP layer, the unclear problem of data forwarding process in the L2 U2U Relay scenario is solved, ensuring the correct data transmission.
Patent Information
- Application Number
- CN202310542631.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-05-12
- Publication Date
- 2024-11-12
AI Technical Summary
In the Layer 2 terminal-to-terminal relay (L2 U2U Relay) scenario, when the data between the two remote terminals is forwarded through the PC5 relay adaptation layer (SRAP), the specific implementation process and related parameters are not clearly defined.
Provide a sub-link data transmission method, including determining the BEARER ID, UE ID and RLC channel between the relay terminal in the head format of the PC5 SRAP layer between the first terminal and the second terminal, ensuring the correctness of the data channel. Configuration and transfer.
It clarifies the header format content settings of SL-SRB and SL-DRB data in the relay adapter layer and the PC5 RLC channel configuration used for forwarding to ensure that the Remote UE and L2 U2U Relay UE can submit data correctly and ensure the correctness of data transmission and reception. .
Smart Images

Figure CN118945681A_ABST
Abstract
Description
Technical Field
[0001] 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
[0002] For the Layer 2 U2U Relay scenario, data between two remote UEs is forwarded via the PC5 Sidelink Relay Adaptation Protocol (SRAP), but it is not yet clear how the relevant process is implemented and how the relevant parameters are determined. Summary of the invention
[0003] 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 for forwarding data through the PC5 relay adaptation layer, and determine the transmission data channel.
[0004] In a first aspect, a secondary link data transmission method is provided, the method comprising:
[0005] In a case where 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 according to the SRAP SDU received from the first layer:
[0006] Determine the value of BEARER ID in the header format of the PC5 SRAP layer;
[0007] Determine the value of UE ID in the header format of the PC5 SRAP layer;
[0008] Determine a first PC5 RLC channel with the relay terminal;
[0009] The first layer is an upper layer of the PC5 SRAP layer of the first terminal.
[0010] In a second aspect, a secondary link data transmission method is provided, the method comprising:
[0011] 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:
[0012] Determine the value of BEARER ID in the header format of the PC5 SRAP layer;
[0013] Determine the value of UE ID in the header format of the PC5 SRAP layer;
[0014] Determine a second PC5 RLC channel with the relay terminal;
[0015] The first layer is an upper layer of the PC5 SRAP layer of the first terminal.
[0016] In a third aspect, a secondary link data transmission method is provided, the method comprising:
[0017] 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;
[0018] 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;
[0019] The SL-DRB is a SL-DRB between the first terminal and the second terminal.
[0020] In a fourth aspect, a secondary link data transmission method is provided, the method comprising:
[0021] The second terminal removes the header format of the SRAP PDU received from the relay terminal and then submits it to the target entity;
[0022] 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;
[0023] 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.
[0024] In a fifth aspect, a secondary link data transmission device is provided, the device being applied to a first terminal, the device comprising:
[0025] 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:
[0026] Determine the value of BEARER ID in the header format of the PC5 SRAP layer;
[0027] Determine the value of UE ID in the header format of the PC5 SRAP layer;
[0028] Determine a first PC5 RLC channel with the relay terminal;
[0029] The first layer is an upper layer of the PC5 SRAP layer of the first terminal.
[0030] In a sixth aspect, a secondary link data transmission device is provided, the device being applied to a first terminal, the device comprising:
[0031] 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:
[0032] Determine the value of BEARER ID in the header format of the PC5 SRAP layer;
[0033] Determine the value of UE ID in the header format of the PC5 SRAP layer;
[0034] Determine a second PC5 RLC channel with the relay terminal;
[0035] The first layer is an upper layer of the PC5 SRAP layer of the first terminal.
[0036] In a seventh aspect, a secondary link data transmission device is provided, the device being applied to a relay terminal, the device comprising:
[0037] 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;
[0038] 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;
[0039] The SL-DRB is a SL-DRB between the first terminal and the second terminal.
[0040] In an eighth aspect, a secondary link data transmission device is provided, the device being applied to a second terminal, the device comprising:
[0041] The fourth execution module is used for:
[0042] The second terminal removes the header format of the SRAP PDU received from the relay terminal and then submits it to the target entity;
[0043] 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;
[0044] 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.
[0045] In the ninth aspect, a terminal is provided, which includes 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.
[0046] In a tenth aspect, a terminal is provided, including a processor and a communication interface, wherein:
[0047] In the case where the terminal is the first terminal:
[0048] The processor is configured to, when there is SL-SRB 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:
[0049] Determine the value of BEARER ID in the header format of the PC5 SRAP layer;
[0050] Determine the value of UE ID in the header format of the PC5 SRAP layer;
[0051] Determine a first PC5 RLC channel with the relay terminal;
[0052] The first layer is an upper layer of the PC5 SRAP layer of the first terminal.
[0053] In the case where the terminal is the first terminal:
[0054] The processor is configured to, when there is data of the SL-DRB 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:
[0055] Determine the value of BEARER ID in the header format of the PC5 SRAP layer;
[0056] Determine the value of UE ID in the header format of the PC5 SRAP layer;
[0057] Determine a second PC5 RLC channel with the relay terminal;
[0058] The first layer is an upper layer of the PC5 SRAP layer of the first terminal.
[0059] In the case where the terminal is a relay terminal:
[0060] The processor 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;
[0061] 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;
[0062] The SL-DRB is a SL-DRB between the first terminal and the second terminal.
[0063] In the case where the terminal is a second terminal:
[0064] The processor is used for the second terminal to remove the header format of the SRAP PDU received from the relay terminal and then submit it to the target entity;
[0065] 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;
[0066] 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.
[0067] 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, 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.
[0068] 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.
[0069] 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 a program 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.
[0070] In the fourteenth aspect, a computer program / program product is provided, wherein the computer program / program product is stored in a storage medium, and the program / program product 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.
[0071] 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 according to 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; determining the 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 according to 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; determining the 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 to forward to the next hop are clarified, so that the Remote UE and the L2 U2URelay UE can correctly deliver the data transmitted on the SL-SRB or SL-DRB to ensure the correctness of data transmission and reception. BRIEF DESCRIPTION OF THE DRAWINGS
[0072] Figure 1a is a block diagram of a wireless communication system to which the embodiments of the present application can be applied;
[0073] Figure 1b This is a schematic diagram of the Relay scenario based on the Sidelink wireless air interface;
[0074] Figure 1c This is one of the L2 U2U relay protocol stack diagrams;
[0075] Figure 1d This is the second diagram of the L2 U2U relay protocol stack;
[0076] Figure 2 This is one of the flowcharts of the secondary link data transmission method provided in the embodiment of the present application;
[0077] Figure 3 This is the second flowchart of the secondary link data transmission method provided in the embodiment of the present application;
[0078] Figure 4 This is the third flowchart of the secondary link data transmission method provided in the embodiment of the present application;
[0079] Figure 5 This is the fourth flowchart of the secondary link data transmission method provided in the embodiment of the present application;
[0080] Figure 6It is one of the structural schematic diagrams of the secondary link data transmission device provided in the embodiment of the present application;
[0081] Figure 7 This is the second structural diagram of the secondary link data transmission device provided in the embodiment of the present application;
[0082] Figure 8 This is the third structural diagram of the secondary link data transmission device provided in the embodiment of the present application;
[0083] Fig. 9 This is the fourth structural diagram of the secondary link data transmission device provided in the embodiment of the present application;
[0084] Fig.10 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application;
[0085] Fig.11 It is a schematic diagram of the structure of the terminal provided in the embodiment of the present application. DETAILED DESCRIPTION
[0086] The following will be combined with the drawings in the embodiments of the present application to clearly describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field belong to the scope of protection of this application.
[0087] The terms "first", "second", etc. of the present 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 one type, and the number of objects is not limited, for example, the first object can be one or more. In addition, "or" in the present application represents at least one of the connected objects. For example, "A or B" covers three schemes, namely, Scheme 1: including A but not including B; Scheme 2: including B but not including A; Scheme 3: including both A and B. The character " / " generally indicates that the objects associated with each other are in an "or" relationship.
[0088] The term "indication" in this application can be 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, operations to be performed, or request results in the sent indication; an indirect indication can be understood as the receiver determining the corresponding information according to the indication sent by the sender, or making a judgment and determining the operation to be performed or the request result according to the judgment result.
[0089] 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 described technology 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 descriptions, but these technologies can also be applied to systems other than NR systems, such as the 6th generation (6 th Generation, 6G) communication system.
[0090] Figure 1aA block diagram of a wireless communication system applicable to an embodiment of the present application is shown. The wireless communication system includes a terminal 11 and a network side device 12. Among them, the terminal 11 can be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), a notebook computer, a personal digital assistant (Personal Digital Assistant, PDA), a handheld computer, a netbook, an ultra-mobile personal computer (Ultra-mobile Personal Computer, UMPC), a mobile Internet device (Mobile Internet Device, MID), an augmented reality (Augmented Reality, AR), a virtual reality (Virtual Reality, VR) device, a robot, a wearable device (Wearable Device), an aircraft (flight vehicle), a vehicle-mounted device (Vehicle User Equipment, VUE), a ship-mounted device, a pedestrian terminal (Pedestrian User Equipment, PUE), a smart home (home appliances with wireless communication functions, such as refrigerators, televisions, washing machines or furniture, etc.), a game console, a personal computer (Personal Computer, PC), a teller machine or a self-service machine and 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 referred to as 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 may be referred to as a Node B (NB), an evolved Node B (eNB), a next generation Node B (gNB), a New Radio Node B (NR Node B), an access point, a Relay Base Station (RBS), a Serving Base Station (SBS), a Base Transceiver Station (BTS), a radio base station, a radio transceiver, a Basic Service Set (BSS), an Extended Service Set (ESS), a Home Node B (HNB), a Home Evolved Node B, a 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 terms. It should be noted that in the embodiments 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.
[0091] In order to better understand the technical solution of this application, the following contents are first introduced:
[0092] 1. Introduction to Sidelink (SL)
[0093] The Long Term Evolution (LTE) system has supported sidelinks (SL) since its 12th release, which are used for direct data transmission between end-user equipment (UE) without going through network equipment.
[0094] LTE sidelink is designed for specific public safety matters (such as emergency communications at fire sites or disaster sites such as earthquakes), or vehicle to everything (V2X) communications. Vehicle to everything 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, reliability, etc. will be supported by 5G NR sidelink.
[0095] 2. NR Sidelink transmission mode
[0096] NR sidelink transmission is mainly divided into broadcast (BC), groupcast (GC), and unicast (UC) transmission types. Unicast, as the name implies, 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 UE belonging to the same group.
[0097] 3. Sidelink-based U2U (UE-to-UE) Relay Mechanism
[0098] In order to achieve better coverage and terminal power saving, NR will study the Relay mechanism based on the Sidelink wireless air interface. Typical scenarios include Figure 1b , taking a single-hop relay (only one U2U Relay) as an example:
[0099] The source terminal (Source UE) needs to transmit data with the target terminal (Target UE), but due to poor coverage, it finds a U2U Relay UE to transfer the data. The interface between the Relay UE and the Source UE is a sidelink (PC5) interface, and the interface between the Relay UE and the Remote UE is also a sidelink (PC5) interface. Generally speaking, the Relay UE is open and can serve any Source UE and Target UE.
[0100] 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.
[0101] Here, if it is a multi-hop relay scenario, there is more than one U2U Relay. For example, if there are N hops, then the datagram will be transferred through N U2U Relays.
[0102] L2 U2U relay protocol stack (taking a single hop as an example, signaling plane CP, SL-SRB transmission) is as follows Figure 1c As shown, the L2U2Urelay protocol stack (taking a single hop as an example, user plane UP, SL-DRB transmission) is as follows Figure 1d shown.
[0103] The following is a detailed description of the side link data transmission method provided by the embodiment of the present application through some embodiments and their application scenarios in combination with the accompanying drawings.
[0104] It should be noted that the technical solution of this application is aimed at a single-hop relay scenario, that is, Figure 1b The scenario shown; 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, and the embodiments of the present application do not make specific limitations on this.
[0105] See also Figure 2 The embodiment of the present application provides a secondary link data transmission method, the execution subject is a first terminal, and the method includes:
[0106] Step 201: 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 according to the SRAP SDU received from the first layer:
[0107] (1) Determine the value of the bearer ID in the header format of the PC5 SRAP layer;
[0108] (2) Determine the value of the terminal identifier (UE ID) in the header format of the PC5 SRAP layer;
[0109] (3) determining the first PC5 RLC channel between the relay terminal and the relay terminal;
[0110] The first layer is an upper layer of the PC5 SRAP layer of the first terminal.
[0111] In the embodiment of the present application, it is aimed at the situation where 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.
[0112] 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 according to 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 RemoteUE and L2 U2U Relay UE can correctly deliver the data transmitted on the SL-SRB, ensuring the correctness of data transmission and reception.
[0113] 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;
[0114] In a possible implementation, the method further includes:
[0115] 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.
[0116] In a possible implementation, the method further includes:
[0117] The first terminal delivers the SRAP PDU generated according to the SRAP SDU to the first PC5 RLC channel for transmission.
[0118] In a possible implementation, the method further includes:
[0119] When the 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 the PC5 SRAP configuration agreed upon in the protocol or by default;
[0120] Among them, the PC5 SRAP configuration includes the bearer identification value of the SL-SRB.
[0121] Optionally, the bearer identification value of the E2E SL-SRB specifically includes at least one of the following:
[0122] (1) The bearer identification value of E2E SL-SRB0 is 0;
[0123] (2) The bearer identification value of E2E SL-SRB1 is 1;
[0124] (3) The bearer identifier value of E2E SL-SRB2 is 2;
[0125] (4) The bearer identifier value of E2E SL-SRB3 is 3;
[0126] 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.
[0127] In a possible implementation manner, the first terminal determines the value of the BEARER ID in the header format of the PC5SRAP layer according to the SRAP SDU received from the first layer, including:
[0128] 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;
[0129] The data category of each SL-SRB corresponds to different BEARER ID values.
[0130] In an embodiment of the present application, the value of the BEARER ID is set accordingly according to the data category of the SL-SRB used to send the SRAP SDU, wherein it is necessary to ensure that the data category of each SL-SRB corresponds to a different BEARER ID value.
[0131] In a possible implementation manner, the first terminal determines a value of the BEARER ID according to a category of data of the SL-SRB used to send the SRAP SDU, including at least one of the following:
[0132] (1) When the type of SL-SRB data 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;
[0133] (2) when the type of the SL-SRB data 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 the BEARER ID is set to the second value;
[0134] (3) when the type of the SL-SRB data 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 the BEARER ID is set to the third value;
[0135] (4) When the type of the SL-SRB data 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 the BEARER ID is set to the fourth value;
[0136] Among them, 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; the fourth value is 3; it should be noted that the example of the value of the BEARER ID is only an example of the SL-SRB bearer identification value being equal to the corresponding BEARER ID value. Optionally, the value of the BEARER ID can also be selected from other values, as long as the data category of each SL-SRB corresponds to different BEARER ID values.
[0137] In a possible implementation manner, the value of the UE ID includes at least one of the following:
[0138] (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;
[0139] (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;
[0140] In a possible implementation manner, 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:
[0141] (1) 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;
[0142] (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.
[0143] In the embodiment of the present application, the PC5 RLC channel configuration between the corresponding relay terminal is determined according to the type of data of the SL-SRB used to send the SRAP SDU.
[0144] In a possible implementation manner, the first terminal determines the PC5 RLC channel configuration according to the category of the SL-SRB data used to send the SRAP SDU, including at least one of the following:
[0145] (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 as the first PC5 RLC channel configuration;
[0146] (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 as the second PC5 RLC channel configuration;
[0147] (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;
[0148] (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.
[0149] In a possible implementation manner, 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:
[0150] (1) RLC sequence number field length;
[0151] (2) RLC reorganization timer;
[0152] (3) RLC polling retransmission timer;
[0153] (4) RLC polls PDU;
[0154] (5) RLC polling byte;
[0155] (6) RLC maximum retransmission threshold
[0156] (7) RLC status prohibit timer;
[0157] (8) Logical channel identifier, which is used to uniquely identify the PC5 RLC channel;
[0158] (9) MAC logical channel priority;
[0159] (10) MAC priority bit rate;
[0160] (11) MAC logical channel group;
[0161] (12) MAC scheduling request identifier.
[0162] Optionally, the PC5 RLC channel configuration can be set as shown in Table 1:
[0163] Table 1
[0164]
[0165]
[0166] It should be noted that the specific information values and descriptions in the above Table 1 are only examples and do not constitute substantial limitations.
[0167] In a possible implementation manner, the PC5 RLC channel configurations corresponding to the categories of data of different SL-SRBs are the same or different;
[0168] In the case of different PC5 RLC channel configurations, the logical channel identifiers in different PC5 RLC channel configurations have different values, 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 RLCchannel 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, such as 59, 60, 61, and 62 respectively.
[0169] See also Figure 3 The embodiment of the present application provides a secondary link data transmission method, the execution subject is a first terminal, and the method includes:
[0170] Step 301: 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 according to the SRAP SDU received from the first layer and the dedicated configuration of the SL-DRB:
[0171] (1) Determine the value of the BEARER ID in the header format of the PC5 SRAP layer;
[0172] (2) Determine the value of the UE ID in the header format of the PC5 SRAP layer;
[0173] (3) Determine the second PC5 RLC channel with the relay terminal;
[0174] The first layer is an upper layer of the PC5 SRAP layer of the first terminal.
[0175] In the embodiment of the present application, it is aimed at the situation 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.
[0176] 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; and 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, thereby ensuring the correctness of data transmission and reception.
[0177] In a possible implementation, the method further includes:
[0178] The first terminal generates a SRAP PDU according to the value of the BEARER ID or the value of the UE ID.
[0179] In a possible implementation manner, the first terminal delivers the SRAP PDU generated according to the SRAP SDU to the second PC5 RLC channel for transmission.
[0180] In a possible implementation, the method further includes:
[0181] 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:
[0182] (1) Configuration index value of SL-DRB; for example: SLRB-PC5-ConfigIndex::=INTEGER(1..maxNrofSLRB-r16);
[0183] (2) configuration of the fifth PC5 RLC channel between the first terminal and the relay terminal;
[0184] (3) The association between the configuration index value of the SL-DRB and the configuration of the fifth PC5 RLC channel.
[0185] 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.
[0186] In a possible implementation manner, 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:
[0187] 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.
[0188] In the 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 make the correspondence clear, the value of the BEARER ID is set to the configuration index value of the SL-DRB minus 1, or, after the value of the BEARER ID is set 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 configuration index value of SL-DRB is equal to 391, 9-bit binary encoding 0001 1000 0111 can be performed, and the encoding of the lower 5 bits (0 0111) is taken, and the value corresponds to 7. Then the value of BEARER ID is 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 when the first terminal and the second terminal actually use 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.
[0189] In a possible implementation, the first terminal determines the second PC5 RLC channel between the first terminal and the relay terminal according to the SRAP SDU received from the first layer and the dedicated configuration of the SL-DRB, including:
[0190] (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;
[0191] (2) The first terminal determines the second PC5 RLC channel between the first terminal and the relay terminal according to the configuration of the fifth PC5 RLC channel.
[0192] 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 shown in the above example), 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.
[0193] See also Figure 4 The embodiment of the present application provides a secondary link data transmission method, the execution subject is a relay terminal, and the method includes:
[0194] Step 401: The relay terminal determines a 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 a 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;
[0195] 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;
[0196] Among them, the SL-DRB is the SL-DRB between the first terminal and the second terminal.
[0197] In the embodiment of the present application, the relay terminal needs to determine the PC5 RLC channel used for subsequently transmitting the SRAP PDU to the second terminal according to the SRAP PDU received from the first terminal.
[0198] 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.
[0199] In a possible implementation manner, 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:
[0200] (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 SRAPPDU 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;
[0201] (2) The relay terminal determines a third PC5 RLC channel between the relay terminal and the second terminal according to the configuration of the PC5 RLC channel between the relay terminal and the second terminal;
[0202] 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, such as 0, 1, 2, and 3 in the above example.
[0203] In the embodiment of the present application, since the relay terminal cannot directly know whether the SL-SRB data or the SL-DRB data is transmitted when receiving the SRAP PDU from the first terminal, it is necessary to judge in combination with the value of the BEARER ID in the header format of the SRAP PDU and the PC5 RLC channel of the received SRAP PDU;
[0204] 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 BEARERID 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 agreed upon by the protocol or configured by default, 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.
[0205] In a possible implementation, in the case where the SRAP PDU transmits SL-SRB data, 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:
[0206] (1) When the value of 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;
[0207] (2) When the value of 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;
[0208] (3) When the value of 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;
[0209] (4) When the value of 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.
[0210] In a possible implementation manner, 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:
[0211] (1) RLC sequence number field length;
[0212] (2) RLC reorganization timer;
[0213] (3) RLC polling retransmission timer;
[0214] (4) RLC polls PDU;
[0215] (5) RLC polling byte;
[0216] (6) RLC maximum retransmission threshold
[0217] (7) RLC status prohibit timer;
[0218] (8) Logical channel identifier, which is used to uniquely identify the PC5 RLC channel;
[0219] (9) MAC logical channel priority;
[0220] (10) MAC priority bit rate;
[0221] (11) MAC logical channel group;
[0222] (12) MAC scheduling request identifier.
[0223] Optionally, the PC5 RLC channel configuration may be set as shown in Table 1 above:
[0224] In a possible implementation manner, the PC5 RLC channel configurations corresponding to the categories of data of different SL-SRBs are the same or different;
[0225] In the case of different PC5 RLC channel configurations, the logical channel identifiers in different PC5 RLC channel configurations have different values, 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 RLCchannel 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, such as 59, 60, 61, and 62 respectively.
[0226] In a possible implementation, the method further includes:
[0227] The relay terminal obtains the dedicated configuration of the SL-DRB, and the dedicated configuration of the SL-DRB includes at least one of the following:
[0228] (1) SL-DRB configuration index value;
[0229] (2) configuration of the sixth PC5 RLC channel between the relay terminal and the second terminal;
[0230] (3) The association between the configuration index value of the SL-DRB and the configuration of the sixth PC5 RLC channel.
[0231] In a possible implementation manner, 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, including:
[0232] (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 of the received SRAPPDU 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;
[0233] (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;
[0234] Among them, the first set is a set of BEARER ID values when transmitting SL-SRB data between the first terminal and the second terminal.
[0235] In the embodiment of the present application, since the relay terminal cannot directly know whether the SL-SRB data or the SL-DRB data is transmitted when receiving the SRAP PDU from the first terminal, it is necessary to judge in combination with the value of the BEARER ID in the header format of the SRAP PDU and the PC5 RLC channel of the received SRAP PDU;
[0236] 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 BEARERID 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 of the received SRAP PDU. If the PC5 RLC channel of the received 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 PC5 RLC channel configuration between the second terminal can be determined based on the value of the BEARER ID and the dedicated configuration of the SL-DRB. Specifically, the relay terminal determines the PC5 RLC channel configuration between 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.
[0237] In a possible implementation manner, 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, including:
[0238] (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;
[0239] (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;
[0240] Among them, the first set is a set of BEARER ID values when transmitting SL-SRB data between the first terminal and the second terminal.
[0241] In the embodiment of the present application, since 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 excluded that the BEARER ID value of the SL-SRB and the SL-DRB is shared, so it is directly determined that the SRAP PDU transmits the data of the SL-DRB, and accordingly, the PC5 RLC channel configuration between the relay terminal and the second terminal can be determined according to the value of the BEARER ID and the dedicated configuration of the SL-DRB. Specifically, the relay terminal determines the PC5RLC 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.
[0242] See also Figure 5 In an embodiment of the present application, a secondary link data transmission method is provided, and the execution subject is a second terminal. The method includes:
[0243] Step 501: The second terminal removes the header format of the SRAP PDU received from the relay terminal and submits it to the target entity;
[0244] Alternatively, the second terminal removes the header format of the SRAPPDU and delivers it to the target entity according to the dedicated configuration of the SRAP PDU and SL-DRB received from the relay terminal;
[0245] The SL-DRB is a 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.
[0246] In the embodiment of the present application, the second terminal needs to determine the target entity for subsequent delivery according to the SRAP PDU received from the relay terminal.
[0247] 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.
[0248] In a possible implementation manner, the second terminal removes the header format of the SRAPPDU and submits it to the target entity according to the SRAP PDU received from the relay terminal, including:
[0249] 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 SRAPPDU 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;
[0250] Among them, the first set is a set of BEARER ID values when transmitting SL-SRB data between the first terminal and the second terminal.
[0251] In the embodiment of the present application, since the second terminal cannot directly know whether the SL-SRB data or the SL-DRB data is transmitted when receiving the SRAP PDU from the relay terminal, it is necessary to judge in combination with the value of the BEARER ID in the header format of the SRAP PDU and the PC5 RLC channel of the received SRAP PDU;
[0252] 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 BEARERID 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 protocol-agreed or default-configured, 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.
[0253] In a possible implementation, the method further includes:
[0254] 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:
[0255] (1) SL-DRB configuration index value;
[0256] (2) The association between the configuration index value of the SL-DRB and the PDCP entity configuration of the second terminal.
[0257] In a possible implementation manner, 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, including:
[0258] (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 SRAPPDU 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;
[0259] or, (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 configuration index value of the SL-DRB equal to the value of the BEARER ID plus 1;
[0260] Among them, the first set is a set of BEARER ID values when transmitting SL-SRB data between the first terminal and the second terminal.
[0261] In the embodiment of the present application, since the second terminal cannot directly know whether the SL-SRB data or the SL-DRB data is transmitted when receiving the SRAP PDU from the relay terminal, it is necessary to judge in combination with the value of the BEARER ID in the header format of the SRAP PDU and the PC5 RLC channel of the received SRAP PDU;
[0262] 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 BEARERID 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 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 configuration index value of the SL-DRB equal to the value of the BEARER ID plus 1;
[0263] 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 the data of the SL-DRB. 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 configuration index value of the SL-DRB equal to the value of the BEARER ID plus 1.
[0264] 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 method executed by the secondary link data transmission device is taken as an example to illustrate the secondary link data transmission device provided in the embodiment of the present application.
[0265] See also Figure 6 The embodiment of the present application provides a secondary link data transmission device 600, which is applied to a first terminal and includes:
[0266] 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, the first terminal performing at least one of the following operations according to the SRAP SDU received from the first layer:
[0267] Determine the value of BEARER ID in the header format of the PC5 SRAP layer;
[0268] Determine the value of UE ID in the header format of the PC5 SRAP layer;
[0269] Determine a first PC5 RLC channel with the relay terminal;
[0270] The first layer is an upper layer of the PC5 SRAP layer of the first terminal.
[0271] Optionally, the device further comprises:
[0272] 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.
[0273] Optionally, the device further comprises:
[0274] 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.
[0275] Optionally, the device further comprises:
[0276] An establishing module, configured to establish a PC5 SRAP entity by the first terminal according to a PC5 SRAP configuration agreed upon in the protocol or by default when the PC5-S connection between the first terminal and the second terminal is established;
[0277] The PC5 SRAP configuration includes the value of the BEARER ID of the SL-SRB.
[0278] Optionally, the first execution module is used to:
[0279] 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;
[0280] The data category of each SL-SRB corresponds to different BEARER ID values.
[0281] Optionally, the first execution module is used for at least one of the following:
[0282] When the category 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;
[0283] When the category 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;
[0284] When the category 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;
[0285] 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;
[0286] Among them, the first value, the second value, the third value and the fourth value are different.
[0287] Optionally, the first execution module is used to:
[0288] 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;
[0289] 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.
[0290] Optionally, the first execution module is used for at least one of the following:
[0291] 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 the first PC5 RLC channel configuration;
[0292] In a case where the category of the SL-SRB data is SL-SRB1 data between the first terminal and the second terminal, the PC5 RLC channel configuration is determined as the second PC5 RLC channel configuration;
[0293] 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;
[0294] 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 the fourth PC5 RLC channel configuration.
[0295] 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:
[0296] RLC sequence number field length;
[0297] RLC reassembly timer;
[0298] RLC polling retransmission timer;
[0299] RLC polls PDU;
[0300] RLC polling byte;
[0301] RLC maximum retransmission threshold
[0302] RLC state prohibit timer;
[0303] Logical channel identifier, which is used to uniquely identify the PC5 RLC channel;
[0304] MAC logical channel priority;
[0305] MAC priority bit rate;
[0306] MAC logical channel group;
[0307] MAC scheduling request identifier.
[0308] Optionally,
[0309] The PC5 RLC channel configurations corresponding to the data categories of different SL-SRBs are the same or different;
[0310] When the PC5 RLC channel configurations are different, the values of the logical channel identifiers in different PC5 RLC channel configurations are different.
[0311] See also Figure 7 The embodiment of the present application provides a secondary link data transmission device 700, which is applied to a first terminal and includes:
[0312] 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, 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:
[0313] Determine the value of BEARER ID in the header format of the PC5 SRAP layer;
[0314] Determine the value of UE ID in the header format of the PC5 SRAP layer;
[0315] Determine a second PC5 RLC channel with the relay terminal;
[0316] The first layer is an upper layer of the PC5 SRAP layer of the first terminal.
[0317] Optionally, the device further comprises:
[0318] The second generating module is used for the first terminal to generate a SRAP PDU according to the value of the BEARER ID or the value of the UE ID.
[0319] Optionally, the device further comprises:
[0320] A second delivery module is used for the first terminal to deliver the SRAP PDU generated according to the SRAP SDU to the second PC5RLC channel for transmission;
[0321] The first layer is an upper layer of the PC5 SRAP layer of the first terminal.
[0322] Optionally, the device further comprises:
[0323] The first acquisition module is used for the first terminal to acquire the dedicated configuration of the SL-DRB, where the dedicated configuration of the SL-DRB includes at least one of the following:
[0324] Configuration index value of SL-DRB;
[0325] A fifth PC5 RLC channel configuration between the first terminal and the relay terminal;
[0326] The association between the configuration index value of SL-DRB and the configuration of the fifth PC5 RLC channel.
[0327] Optionally, the second execution module is used to:
[0328] 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.
[0329] Optionally, the second execution module is used to:
[0330] 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;
[0331] 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.
[0332] See also Figure 8 The embodiment of the present application provides a secondary link data transmission device 800, which is applied to a relay terminal and includes:
[0333] The third execution module 801 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;
[0334] The relay terminal delivers the SRAP PDU to the third PC5 RLC channel for transmission, or the relay terminal delivers the SRAPPDU to the fourth PC5 RLC channel for transmission;
[0335] Among them, the SL-DRB is the SL-DRB between the first terminal and the second terminal.
[0336] Optionally, the third execution module is used to:
[0337] 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 SRAPPDU 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;
[0338] 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;
[0339] Among them, the first set is a set of BEARER ID values when transmitting SL-SRB data between the first terminal and the second terminal.
[0340] Optionally, the third execution module is used to:
[0341] When the value of 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;
[0342] When the value of 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;
[0343] When the value of 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;
[0344] 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.
[0345] Optionally, any PC5 RLC channel configuration includes at least one of the following parameter values:
[0346] RLC sequence number field length;
[0347] RLC reassembly timer;
[0348] RLC polling retransmission timer;
[0349] RLC polls PDU;
[0350] RLC polling byte;
[0351] RLC maximum retransmission threshold
[0352] RLC state prohibit timer;
[0353] Logical channel identifier, which is used to uniquely identify the PC5 RLC channel;
[0354] MAC logical channel priority;
[0355] MAC priority bit rate;
[0356] MAC logical channel group;
[0357] MAC scheduling request identifier.
[0358] Optionally,
[0359] The PC5 RLC channel configurations corresponding to different BEARER ID values are the same or different;
[0360] 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.
[0361] Optionally, the device further comprises:
[0362] The second acquisition module is used for the relay terminal to acquire the dedicated configuration of the SL-DRB, where the dedicated configuration of the SL-DRB includes at least one of the following:
[0363] Configuration index value of SL-DRB;
[0364] a sixth PC5 RLC channel configuration between the relay terminal and the second terminal;
[0365] The association between the configuration index value of SL-DRB and the configuration of the sixth PC5 RLC channel.
[0366] Optionally, the third execution module is used to:
[0367] 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 of the received SRAPPDU 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;
[0368] 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;
[0369] Among them, the first set is a set of BEARER ID values when transmitting SL-SRB data between the first terminal and the second terminal.
[0370] Optionally, the third execution module is used to:
[0371] 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 BEARERID plus 1;
[0372] 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;
[0373] Among them, the first set is a set of BEARER ID values when transmitting SL-SRB data between the first terminal and the second terminal.
[0374] See also Fig. 9 The embodiment of the present application provides a secondary link data transmission device 900, which is applied to a second terminal and includes:
[0375] The fourth execution module 901 is used to:
[0376] The second terminal removes the header format of the SRAP PDU received from the relay terminal and then delivers it to the target entity;
[0377] Alternatively, the second terminal removes the header format of the SRAPPDU and delivers it to the target entity according to the dedicated configuration of the SRAP PDU and SL-DRB received from the relay terminal;
[0378] Among them, 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.
[0379] Optionally, the fourth execution module is used to:
[0380] 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 SRAPPDU 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;
[0381] Among them, the first set is a set of BEARER ID values when transmitting SL-SRB data between the first terminal and the second terminal.
[0382] Optionally, the device further comprises:
[0383] The third acquisition module is used for the second terminal to acquire the dedicated configuration of the SL-DRB, where the dedicated configuration of the SL-DRB includes at least one of the following:
[0384] Configuration index value of SL-DRB;
[0385] The association between the configuration index value of the SL-DRB and the PDCP entity configuration of the second terminal.
[0386] Optionally, the fourth execution module is used to:
[0387] 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 SRAPPDU 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;
[0388] or,
[0389] 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 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;
[0390] Among them, the first set is a set of BEARER ID values when transmitting SL-SRB data between the first terminal and the second terminal.
[0391] The side 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 a chip. The electronic device can be a terminal, or it can be other devices other than a terminal. Exemplarily, the terminal can include but is not limited to the types of terminals 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.
[0392] The secondary link data transmission device provided in the embodiment of the present application can achieve Figures 2 to 5 The various processes implemented by the method embodiment and achieving the same technical effect are not described here to avoid repetition.
[0393] like Fig.10 As shown, the embodiment of the present application also provides a communication device 1000, including a processor 1001 and a memory 1002, and 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.
[0394] The embodiment of 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 used to run a program or instruction to implement the following Figures 2 to 5 The steps in the method embodiment shown. This terminal embodiment corresponds to the above-mentioned terminal side method embodiment, and each implementation process and implementation method of the above-mentioned method embodiment can be applied to this terminal embodiment and can achieve the same technical effect. Specifically, Fig.11 A schematic diagram of the hardware structure of a terminal for implementing an embodiment of the present application.
[0395] 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 a processor 1110.
[0396] Those skilled in the art will appreciate that the terminal 1100 may also include a power source (such as a battery) for supplying power to each component, and the power source may be logically connected to the processor 1110 through a power management system, thereby implementing functions such as managing charging, discharging, and power consumption management through the power management system. Fig.11 The terminal structure shown in the figure does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently, which will not be described in detail here.
[0397] It should be understood that in the 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.
[0398] In the embodiment of the present application, after receiving downlink data from the network side device, the RF unit 1101 can transmit the data to the processor 1110 for processing; in addition, the RF unit 1101 can send uplink data to the network side device. Generally, the RF unit 1101 includes but is not limited to an antenna, an amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, etc.
[0399] 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, an application program or instruction required for at least one function (such as a sound playback function, an image playback function, etc.), 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 a random access memory (RAM), a static random access memory (SRAM), a dynamic random access memory (DRAM), a synchronous dynamic random access memory (SDRAM), a double data rate synchronous dynamic random access memory (DDRSDRAM), an enhanced synchronous dynamic random access memory (ESDRAM), a synchronous link dynamic random access memory (SLDRAM) and a direct memory 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.
[0400] The processor 1110 may include one or more processing units; optionally, the processor 1110 integrates an application processor and a modem processor, wherein the application processor mainly processes operations related to an operating system, a user interface, and application programs, and the modem processor mainly processes wireless communication signals, such as a baseband processor. It is understandable that the modem processor may not be integrated into the processor 1110.
[0401] When terminal 1100 is the first terminal:
[0402] The processor 1110 is configured to, when there is SL-SRB data to be transmitted between the first terminal and the second terminal, perform, according to the SRAP SDU received from the first layer, at least one of the following operations by the first terminal:
[0403] Determine the value of BEARER ID in the header format of the PC5 SRAP layer;
[0404] Determine the value of UE ID in the header format of the PC5 SRAP layer;
[0405] Determine a first PC5 RLC channel with the relay terminal;
[0406] The first layer is an upper layer of the PC5 SRAP layer of the first terminal.
[0407] Optionally, the processor 1110 is configured to, at the first terminal, generate a secondary link relay adaptation layer protocol data unit SRAP PDU according to a value of a BEARER ID or a value of a UE ID.
[0408] Optionally, the processor 1110 is configured for the first terminal to deliver the SRAP PDU generated according to the SRAP SDU to the first PC5 RLC channel for transmission.
[0409] Optionally, the processor 1110 is configured to, 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;
[0410] The PC5 SRAP configuration includes the value of the BEARER ID of the SL-SRB.
[0411] Optionally, the processor 1110 is configured to:
[0412] 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;
[0413] The data category of each SL-SRB corresponds to different BEARER ID values.
[0414] Optionally, the processor 1110 is configured to perform at least one of the following:
[0415] When the category 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;
[0416] When the category 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;
[0417] When the category 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;
[0418] 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;
[0419] Among them, the first value, the second value, the third value and the fourth value are different.
[0420] Optionally, the processor 1110 is configured to:
[0421] 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;
[0422] 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.
[0423] Optionally, the processor 1110 is configured to perform at least one of the following:
[0424] 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 the first PC5 RLC channel configuration;
[0425] In a case where the category of the SL-SRB data is SL-SRB1 data between the first terminal and the second terminal, the PC5 RLC channel configuration is determined as the second PC5 RLC channel configuration;
[0426] In a case where the category of the SL-SRB data is SL-SRB2 data between the first terminal and the second terminal, the PC5 RLC channel configuration is determined as a third PC5 RLC channel configuration;
[0427] 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 the fourth PC5 RLC channel configuration.
[0428] 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:
[0429] RLC sequence number field length;
[0430] RLC reassembly timer;
[0431] RLC polling retransmission timer;
[0432] RLC polls PDU;
[0433] RLC polling byte;
[0434] RLC maximum retransmission threshold
[0435] RLC state prohibit timer;
[0436] Logical channel identifier, which is used to uniquely identify the PC5 RLC channel;
[0437] MAC logical channel priority;
[0438] MAC priority bit rate;
[0439] MAC logical channel group;
[0440] MAC scheduling request identifier.
[0441] Optionally,
[0442] The PC5 RLC channel configurations corresponding to the data categories of different SL-SRBs are the same or different;
[0443] When the PC5 RLC channel configurations are different, the values of the logical channel identifiers in different PC5 RLC channel configurations are different.
[0444] When terminal 1100 is the first terminal:
[0445] The processor 1110 is configured to, when there is SL-DRB data to be transmitted between the first terminal and the second terminal, perform, by the first terminal, at least one of the following operations according to the SRAP SDU and the dedicated configuration of the SL-DRB received from the first layer:
[0446] Determine the value of BEARER ID in the header format of the PC5 SRAP layer;
[0447] Determine the value of UE ID in the header format of the PC5 SRAP layer;
[0448] Determine a second PC5 RLC channel with the relay terminal;
[0449] The first layer is an upper layer of the PC5 SRAP layer of the first terminal.
[0450] Optionally, the processor 1110 is configured for the first terminal to generate an SRAPPDU according to a value of a BEARER ID or a value of a UE ID.
[0451] 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;
[0452] The first layer is an upper layer of the PC5 SRAP layer of the first terminal.
[0453] Optionally, the processor 1110 is configured for 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:
[0454] Configuration index value of SL-DRB;
[0455] A fifth PC5 RLC channel configuration between the first terminal and the relay terminal;
[0456] The association between the configuration index value of SL-DRB and the configuration of the fifth PC5 RLC channel.
[0457] Optionally, the processor 1110 is configured to:
[0458] 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.
[0459] Optionally, the processor 1110 is configured to:
[0460] 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;
[0461] 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.
[0462] When terminal 1100 is a relay terminal:
[0463] Processor 1110, configured for the relay terminal to determine a 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 a 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;
[0464] The relay terminal delivers the SRAP PDU to the third PC5 RLC channel for transmission, or the relay terminal delivers the SRAPPDU to the fourth PC5 RLC channel for transmission;
[0465] Among them, the SL-DRB is the SL-DRB between the first terminal and the second terminal.
[0466] Optionally, the processor 1110 is configured to:
[0467] 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 SRAPPDU 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;
[0468] 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;
[0469] Among them, the first set is a set of BEARER ID values when transmitting SL-SRB data between the first terminal and the second terminal.
[0470] Optionally, the processor 1110 is configured to:
[0471] When the value of 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;
[0472] When the value of 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;
[0473] When the value of 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;
[0474] 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.
[0475] Optionally, any PC5 RLC channel configuration includes at least one of the following parameter values:
[0476] RLC sequence number field length;
[0477] RLC reassembly timer;
[0478] RLC polling retransmission timer;
[0479] RLC polls PDU;
[0480] RLC polling byte;
[0481] RLC maximum retransmission threshold
[0482] RLC state prohibit timer;
[0483] Logical channel identifier, which is used to uniquely identify the PC5 RLC channel;
[0484] MAC logical channel priority;
[0485] MAC priority bit rate;
[0486] MAC logical channel group;
[0487] MAC scheduling request identifier.
[0488] Optionally,
[0489] The PC5 RLC channel configurations corresponding to different BEARER ID values are the same or different;
[0490] 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.
[0491] 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:
[0492] Configuration index value of SL-DRB;
[0493] a sixth PC5 RLC channel configuration between the relay terminal and the second terminal;
[0494] The association between the configuration index value of SL-DRB and the configuration of the sixth PC5 RLC channel.
[0495] Optionally, the processor 1110 is configured to:
[0496] 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 of the received SRAPPDU 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;
[0497] 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;
[0498] Among them, the first set is a set of BEARER ID values when transmitting SL-SRB data between the first terminal and the second terminal.
[0499] Optionally, the processor 1110 is configured to:
[0500] 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 BEARERID plus 1;
[0501] 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;
[0502] Among them, the first set is a set of BEARER ID values when transmitting SL-SRB data between the first terminal and the second terminal.
[0503] When terminal 1100 is the second terminal:
[0504] The processor 1110 is configured to:
[0505] The second terminal removes the header format of the SRAP PDU received from the relay terminal and then delivers it to the target entity;
[0506] Alternatively, the second terminal removes the header format of the SRAPPDU and delivers it to the target entity according to the dedicated configuration of the SRAP PDU and SL-DRB received from the relay terminal;
[0507] Among them, 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.
[0508] Optionally, the processor 1110 is configured to:
[0509] 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 SRAPPDU 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;
[0510] Among them, the first set is a set of BEARER ID values when transmitting SL-SRB data between the first terminal and the second terminal.
[0511] Optionally, the processor 1110 is configured for 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:
[0512] Configuration index value of SL-DRB;
[0513] The association between the configuration index value of the SL-DRB and the PDCP entity configuration of the second terminal.
[0514] Optionally, the processor 1110 is configured to:
[0515] 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 SRAPPDU 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;
[0516] or,
[0517] 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 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;
[0518] Among them, the first set is a set of BEARER ID values when transmitting SL-SRB data between the first terminal and the second terminal.
[0519] 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 a processor, the various processes of the above-mentioned side-link data transmission method embodiment are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.
[0520] 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-transient readable storage medium.
[0521] 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 side-link data transmission method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.
[0522] 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.
[0523] 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.
[0524] 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.
[0525] It should be noted that, in this article, the terms "comprise", "include" or any other variant thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including 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 one..." does not exclude the presence of other identical elements in the process, method, article or device including the element. In addition, it should be pointed out that the scope of the method and device in the embodiment 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 reverse 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.
[0526] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment method can be implemented by means of a computer software product plus a hardware platform, and of course, it can also be implemented by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, disk, CD, etc.), including several instructions to enable the terminal or network side device to execute the methods described in each embodiment of the present application.
[0527] 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 the present application, ordinary technicians in this field can also make many forms of implementation methods without departing from the purpose of the present application and the scope of protection of the claims, and these implementation methods are all within the protection of the present application.
Claims
1. A secondary link data transmission method, characterized in that: The method comprises: 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, characterized in that 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, characterized in that 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, characterized in that: 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, characterized in that The first terminal determines the value of the BEARER ID in the header format of the PC5 SRAP layer according to the SRAPSDU received from the first layer, including: The first terminal determines a value of the BEARERID 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, characterized in that 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, characterized in that The first terminal determines, according to the SRAPSDU 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, characterized in that 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, characterized in that: 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, characterized in that 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, characterized in that: The method comprises: 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, characterized in that 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, characterized in that 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, characterized in that 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, characterized in that 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, characterized in that 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, characterized in that: The method comprises: 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, characterized in that 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, characterized in that 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, characterized in that 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, characterized in that 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, characterized in that 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, characterized in that 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, characterized in that 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, characterized in that: The method comprises: 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, characterized in that 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 receiving the SRAP PDU is a protocol agreement or a default configuration, the second terminal removes the header format of the SRAPPDU 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, characterized in that 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, characterized in that 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 BEARERID 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, characterized in that: The device is applied to a first terminal, and includes: 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, characterized in that: The device is applied to a first terminal, and includes: 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, characterized in that: The device is applied to a relay terminal, and comprises: 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, characterized in that: The device is applied to a second terminal, and the device includes: 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, characterized in that: It includes a processor and a memory, the memory stores a program or instruction that can be run on the processor, and the program or instruction, when executed by the processor, implements the steps of the side-link data transmission method as described in any one of claims 1 to 10, or, when executed, implements the steps of the side-link data transmission method as described in any one of claims 11 to 16, or, when executed, implements the steps of the side-link data transmission method as described in any one of claims 17 to 24, or, when executed, implements the steps of the side-link data transmission method as described in any one of claims 25 to 28.
34. A readable storage medium, characterized in that: The readable storage medium stores programs or instructions, 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.
