Transmission configuration determination method and device, terminal and storage medium

Abstract

The invention discloses a transmission configuration determination method and device, a terminal and a storage medium, and belongs to the technical field of communication, and the transmission configuration determination method comprises the steps that a first terminal determines transmission configuration information of terminal-to-terminal relay transmission according to end-to-end quality of service (QoS) flow information and a target message; wherein the target message comprises a system broadcast message or a direct link SL pre-configuration message.

Description

Technical Field

[0001] The present application belongs to the field of communication technology, and specifically relates to a transmission configuration determination method, device, terminal and storage medium. Background Art

[0002] With the development of technology, New Radio (NR) sidelink (SL) technology has emerged, which mainly focuses on road safety services related to vehicle to everything (V2X) and realizes broadcast, multicast and unicast communications between terminals in scenarios within and outside network coverage.

[0003] On this basis, in order to further expand the coverage of the network and sidelink, improve power efficiency, and support a wider range of applications and services, end-to-end relay (UE-to-UE Relay, U2U Relay) technology has gradually emerged. That is, when the quality of the direct link between the remote UE and its opposite UE deteriorates or does not meet the link quality requirements for direct communication through the PC5 interface, the remote UE can select a suitable relay UE to ensure service continuity and reachability through U2U relay technology.

[0004] Among them, the single-hop relay transmission network structure between end-to-end (UE to UE, U2U) is as follows: Figure 1 As shown, it includes remote UE1, remote UE2 and relay UE. Among them, the communication information sent from remote UE1 to remote UE2 must first be sent to the relay UE, and then forwarded to remote UE2 by the relay UE. Similarly, the communication information sent from remote UE2 to remote UE1 must first be sent to the relay UE, and then forwarded to remote UE1 by the relay UE. For the expansion of multi-hop scenarios (more than one relay UE), the communication information sent from remote UE1 to remote UE2 must first be sent to the relay UE1, and then forwarded to the next-hop relay UE by the relay UE1, until the last-hop relay UE forwards it to remote UE2. Similarly, the communication information sent from remote UE2 to remote UE1 must first be sent to the relay UE2, and then forwarded to the next-hop relay UE by the relay UE2, until the last-hop relay UE forwards it to remote UE1.

[0005] In addition, transmission between terminals requires relevant configuration. However, currently only the configuration when the terminals communicate directly through the PC5 interface can be realized, and the transmission configuration method for end-to-end relay transmission is not given. Summary of the invention

[0006] Embodiments of the present application provide a method, device, terminal, and storage medium for determining a transmission configuration, and provide a method for determining a transmission configuration for terminal-to-terminal relay transmission.

[0007] In a first aspect, a method for determining a transmission configuration is provided, the method comprising:

[0008] The first terminal determines transmission configuration information of terminal-to-terminal relay transmission according to the end-to-end quality of service QoS flow information and the target message;

[0009] The target message includes a system broadcast message or a direct link SL pre-configuration message.

[0010] In a second aspect, a transmission configuration determination device is provided, which is applied to a first terminal, and the device includes:

[0011] A configuration determination module, used to determine transmission configuration information of terminal-to-terminal relay transmission according to end-to-end quality of service QoS flow information and a target message;

[0012] The target message includes a system broadcast message or a direct link SL pre-configuration message.

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

[0014] In a fourth aspect, a terminal is provided, including a processor and a communication interface, wherein the processor is configured to:

[0015] Determine transmission configuration information of terminal-to-terminal relay transmission according to end-to-end quality of service QoS flow information and target message;

[0016] The target message includes a system broadcast message or a direct link SL pre-configuration message.

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

[0018] In a sixth 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 instruction to implement the method described in the first aspect.

[0019] In a seventh 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.

[0020] In an embodiment of the present application, the first terminal can determine the transmission configuration information of the terminal-to-terminal relay transmission according to the end-to-end quality of service QoS flow information and the target message, wherein the target message includes a system broadcast message or an SL pre-configuration message. It can be seen that in an embodiment of the present application, when performing terminal-to-terminal relay transmission, the first terminal in the transmission determines the transmission configuration information of the terminal-to-terminal relay transmission according to the end-to-end QoS flow information and the system broadcast message, or, it can also determine the transmission configuration information of the terminal-to-terminal relay transmission according to the end-to-end QoS flow information and the SL pre-configuration message. Therefore, an embodiment of the present application provides a method for determining the transmission configuration during terminal-to-terminal relay transmission. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] Figure 1 It is a schematic diagram of terminal-to-terminal relay transmission in an embodiment of the present application;

[0022] Figure 2 It is a schematic diagram of an example of a layer 2 UE to UE relay user plane protocol stack in an embodiment of the present application;

[0023] Figure 3 It is a schematic diagram of an example of a layer 2 UE to UE relay control plane protocol stack in an embodiment of the present application;

[0024] Figure 4 is a flow chart of a method for determining a transmission configuration in an embodiment of the present application;

[0025] Figure 5 is a schematic diagram of the signaling structure of the target message in an embodiment of the present application;

[0026] Figure 6 is a structural block diagram of a transmission configuration determination device in an embodiment of the present application;

[0027] Figure 7 is a structural block diagram of a communication device in an embodiment of the present application;

[0028] Figure 8 It is a structural block diagram of a terminal in an embodiment of the present application. DETAILED DESCRIPTION

[0029] 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.

[0030] 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.

[0031] 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.

[0032] 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 thGeneration, 6G) communication system.

[0033] In order to facilitate understanding of the transmission configuration determination method of the embodiment of the present application, the following related technologies are now introduced:

[0034] There are two types of U2U relays: one is to forward data at layer 2, called layer 2 U2U relay, and the other is to forward data at layer 3, called layer 3 U2U relay. The following is a brief introduction to each.

[0035] 1. Layer 2 U2U relay

[0036] The protocol stack of the user plane and the protocol stack of the control plane of the layer 2 U2U relay are respectively as follows: Figure 2 and Figure 3 As shown, whether for the protocol stack of the user plane or the protocol stack of the control plane, the remote UE adds an adaptation protocol layer between the PC5-PDCP layer and the PC5-RLC layer, and the adaptation protocol layer is used to generate, receive and forward data packets.

[0037] in, Figures 2 to 3 IP stands for Internet Protocol, SDAP stands for Service Data Adaptation Protocol, PDCP stands for Packet Data Convergence Protocol, RLC stands for Radio Link Control Protocol, MAC stands for Media Access Control, PHY stands for Physical Layer, and RRC stands for Radio Resource Control. The ADAPT layer is the Sidelink Relay Adaptation Protocol (SRAP).

[0038] The process of generating and receiving the adaptation data packet is described below.

[0039] (1) Generate an adaptation layer data packet: The remote UE as the transmitting end determines the adaptation protocol header according to the U2U relay routing configuration, adds the adaptation protocol header to the PDCP protocol data unit (PDU) from the upper layer, and generates an adaptation layer data packet. The adaptation protocol header includes at least the identification information of the remote UE as the receiving end (such as address information or ID information) and the radio bearer identification information (such as radio bearer ID information) used to identify the data information carried.

[0040] (2) Receiving an adaptation layer data packet: After receiving an adaptation layer data packet, the remote UE as the receiving end determines whether it is the destination receiving terminal according to the U2U relay adaptation layer configuration, including its own identification information and the radio bearer identification configuration between it and the transmitting UE. If the identification information of the received adaptation data packet completely matches its own identification information, it determines that it is the destination remote UE of the data packet, and then determines the corresponding upper layer protocol entity according to the radio bearer identification information carried by the data packet. Finally, the adaptation layer protocol header is removed and the data packet is sent to the corresponding upper layer protocol body.

[0041] 2. Layer 3 U2U relay

[0042] The data forwarding of layer 3 relay occurs on layer 2, and the radio access layer protocol of the relay UE does not handle the routing of the data packet to be forwarded. One possible implementation method is that when the relay UE receives a data packet to be forwarded sent by a remote UE, it submits the data packet to be forwarded to the upper layer, such as the IP layer, and then the IP layer can determine the destination remote UE of the data packet to be forwarded based on the destination IP address carried in the IP header of the data packet, and send the data packet to be forwarded to the destination remote UE.

[0043] In addition, a multi-hop U2U network refers to an architecture in which Remote UEs at both ends communicate with each other by transferring data through two or more Relay UEs.

[0044] The following is a detailed description of the transmission configuration determination method provided in the embodiment of the present application through some embodiments and their application scenarios in combination with the accompanying drawings.

[0045] In a first aspect, an embodiment of the present application provides a method for determining a transmission configuration, such as Figure 4 As shown, the method may include the following step 401:

[0046] Step 401: The first terminal determines transmission configuration information of terminal-to-terminal relay transmission according to terminal-to-terminal quality of service QoS flow information and a target message.

[0047] The target message includes a system broadcast message or a direct link SL preconfiguration message. Optionally, the system broadcast message is a system information block (SIB) 12 broadcast message. In addition, the first terminal is one of the terminals in the terminal-to-terminal relay transmission, and in the terminal-to-terminal relay transmission, terminals with different roles are included, such as a source remote terminal (Source Remote UE), a relay terminal (Relay UE), and a target remote terminal (TargetRemote UE). Here, the first terminal can be a source remote terminal or a relay terminal.

[0048] Exemplarily, when the transmission configuration determination method of an embodiment of the present application is applied to a single-hop U2U architecture, the first terminal can be a Source Remote UE or a Relay UE; when the transmission configuration determination method of an embodiment of the present application is applied to a multi-hop U2U architecture, the first terminal can be a Source Remote UE or a Relay UE that communicates directly with the SourceRemote UE, or other Relay UEs after the Relay UE that communicates with the Source Remote UE.

[0049] Here, it should be noted that the Source Remote UE may also be referred to as a transmitting remote terminal (TX Remote UE), and the Target Remote UE may also be referred to as a receiving remote terminal (RX Remote UE).

[0050] It should also be noted that the source remote terminal is one of the two remote terminals of the communication. If a service flow is sent from the source remote terminal to the target remote terminal, then from the perspective of the service flow, the source remote terminal is the sender of the service, so it is the source side, and the target remote terminal is the receiver of the service, so it is the target side. If it is another service, the source remote terminal and the target remote terminal may exchange identities depending on the different service flows. In short, the source and the target are distinguished by the flow of a service. Different services can have different or the same sources and targets, and each service is established and maintained separately.

[0051] Optionally, the end-to-end quality of service (QoS) flow information includes at least one of the following items A-1 to A-3:

[0052] Item A-1: ​​End-to-end QoS flow identification QoS-FlowIdentity;

[0053] Item A-2: QoS parameter set QoS-Profile of end-to-end QoS flow;

[0054] Item A-3: Hop-by-hop QoS parameters corresponding to the QoS parameter set of the end-to-end QoS flow.

[0055] For item A-1, for SL end-to-end relay transmission, a maximum of 2048 different QoS flow identifiers (values ​​are any integers from 1 to 2048) are supported between the end-to-end. Among them, the end-to-end relay transmission corresponding to each destination address (destination ID) supports a maximum of 64 different QoS flow identifiers (values ​​are any integers from 1 to 64).

[0056] For item A-2, for SL terminal-to-terminal relay transmission, the QoS parameters between terminals support 256 standard PC5 QoS identifier (PQI) values ​​(any integer from 0 to 255). Each standard PQI can represent the specific QoS requirements corresponding to the value combination of at least one of the following QoS parameter dimensions:

[0057] The priority value of the QoS flow (PriorityLevel);

[0058] Packet Delay Budget (PDB) of the QoS flow;

[0059] Packet Error Rate (PER) of the QoS flow;

[0060] AveragingWindow of QoS flow;

[0061] The maximum data burst volume (MaxDataBurstVolume) of the QoS flow.

[0062] In addition, SL end-to-end communication also supports non-standard PQI. For non-standard PQI, its value is not defined at present. Instead, the value combination of at least one of the above QoS parameter dimensions is directly used to represent the specific QoS requirements.

[0063] For the above item A-3, the QoS parameters of the end-to-end QoS flow, that is, the end-to-end QoS parameters (E2E QoS profile), can be divided into all hops included in the terminal-to-terminal relay transmission. Therefore, the above hop-by-hop QoS parameters include the QoS parameters of each hop in the terminal-to-destination relay transmission. For example, in the U2U Relay link, it can be divided into the first hop and the second hop. Exemplarily, the E2E PDB can be 100ms. After the division, 50ms PDB is given to the first hop and 50ms is given to the second hop.

[0064] As can be seen from the above, in an embodiment of the present application, the first terminal can determine the transmission configuration information of the terminal-to-terminal relay transmission according to the end-to-end quality of service QoS flow information and the target message, wherein the target message includes a system broadcast message or an SL pre-configuration message. It can be seen that in an embodiment of the present application, when performing terminal-to-terminal relay transmission, the first terminal in the transmission determines the transmission configuration information of the terminal-to-terminal relay transmission according to the end-to-end QoS flow information and the system broadcast message, or, it can also determine the transmission configuration information of the terminal-to-terminal relay transmission according to the end-to-end QoS flow information and the SL pre-configuration message. Therefore, an embodiment of the present application provides a method for determining the transmission configuration during terminal-to-terminal relay transmission.

[0065] Optionally, the transmission configuration information includes at least one of the following items B-1 to B-2:

[0066] Item B-1: First configuration information, the first configuration includes configuration information of a target channel, the target channel includes a direct communication interface PC5 wireless link control RLC channel between the first terminal and the second terminal, and the second terminal is the next hop terminal of the first terminal.

[0067] For example, when the first terminal is a Source Remote UE, the first configuration information includes the configuration information of the PC5 RLC Channel between the Source Remote UE and the Relay UE (i.e., the first hop); or, when the first terminal is a Relay UE, the first configuration information includes the configuration information of the PC5 RLC Channel between the Relay UE and the next hop terminal of the Relay UE (which can be a Relay UE or a Target Remote UE).

[0068] Item B-2: A first mapping relationship, wherein the first mapping relationship includes a mapping relationship between an end-to-end SL data bearer and the target channel.

[0069] For example, when the first terminal is the Source Remote UE, the first mapping relationship includes the end-to-end SL data bearer and the mapping relationship between the Source Remote UE and the Relay UE and the PC5 RLC Channel; or, for example, when the first terminal is the Relay UE, the first configuration information includes the end-to-end SL data bearer and the mapping relationship between the PC5 RLC Channel between the Relay UE and the next hop terminal of the Relay UE (which can be the Relay UE or the Target Remote UE).

[0070] It should be noted that the end-to-end bearer may include: an end-to-end Uu bearer (a wireless bearer between a remote UE and a network-side device (such as a base station)), and an end-to-end SL bearer (a wireless bearer between a remote UE and a remote UE). The end-to-end SL bearer may also include an SL data bearer and an SL signaling bearer according to the type of the SL bearer.

[0071] Optionally, when the transmission configuration information includes at least the first configuration information, the first terminal determines the transmission configuration information of the terminal-to-terminal relay transmission according to the terminal-to-terminal QoS flow information and the target message, including the following steps C-1 to C-2:

[0072] Step C-1: the first terminal searches the target message for direct link radio link control bearer configuration information SL-RLCBearerconfig corresponding to a first parameter, wherein the first parameter includes a QoS parameter of a hop corresponding to the first terminal and the second terminal;

[0073] Step C-2: The first terminal determines the first configuration information according to the SL-RLC Bearer config.

[0074] For example, in a single-hop U2U architecture:

[0075] When the first terminal is a Source Remote UE, the first parameter includes a QoS parameter between the Source Remote UE and the Relay UE (i.e., a first-hop QoS parameter (1 st Per-hop QoS profile)), in this case, the Source RemoteUE can search for the same QoS profile as 1 in the target message (such as system broadcast message or SL pre-configuration message). st The SL-RLCBearerconfig corresponding to the Per-hop QoS profile determines the configuration information of the first-hop PC5 RLCChannel based on the SL-RLCBearerconfig.

[0076] When the first terminal is a Relay UE, the first parameter includes a QoS parameter between the Relay UE and the Target Remote UE (i.e., a second-hop QoS parameter (2 nd Per-hop QoS profile)). In this case, the Relay UE can search for the same QoS profile in the target message (such as a system broadcast message or a SL pre-configuration message). nd The SL-RLCBearerconfig corresponding to the Per-hop QoS profile is used to determine the configuration information of the PC5 RLC Channel of the second hop based on the SL-RLCBearerconfig.

[0077] Exemplarily, in a multi-hop U2U architecture;

[0078] When the first terminal is a Source Remote UE, the first parameter includes a QoS parameter between the Source Remote UE and the Relay UE (i.e., a first-hop QoS parameter (1 stPer-hop QoS profile)), in this case, the Source RemoteUE can search for the same QoS profile as 1 in the target message (such as system broadcast message or SL pre-configuration message). st The SL-RLCBearerconfig corresponding to the Per-hop QoS profile determines the configuration information of the first-hop PC5 RLCChannel based on the SL-RLCBearerconfig.

[0079] When the first terminal is a Relay UE that directly communicates with the Source Remote, the first parameter includes a QoS parameter between the Relay UE and the next-hop Relay UE (i.e., a second-hop QoS parameter (2 nd Per-hop QoS profile)), in this case, the Relay UE can search for the same QoS profile as 2 in the target message (such as system broadcast message or SL pre-configuration message). nd The SL-RLCBearerconfig corresponding to the Per-hop QoS profile, and then the configuration information of the PC5RLC Channel of the second hop is determined according to the SL-RLCBearerconfig;

[0080] When the first terminal is the next-hop Relay UE of the Relay UE that communicates directly with the Source Remote, the first parameter includes the QoS parameter between the Relay UE and the next-hop UE (i.e., the third-hop QoS parameter). In this case, the Relay UE can search for the SL-RLCBearerconfig corresponding to the third-hop QoS parameter in the target message (such as a system broadcast message or an SL pre-configuration message), and then determine the configuration information of the PC5 RLC Channel of the third hop according to the SL-RLCBearerconfig.

[0081] Optionally, the above step C-1 "the first terminal searches the target message for the SL-RLC Bearer config corresponding to the first parameter" includes the following steps D-1 to D-4:

[0082] Step D-1: the first terminal searches the target message for a through link service quality parameter set SL-QoS-Profile corresponding to the first parameter;

[0083] Step D-2: when the first terminal finds the SL-QoS-Profile corresponding to the first parameter, the first terminal obtains the direct link service data adaptation protocol configuration information SL-SDAP-Config including the SL-QoS-Profile corresponding to the first parameter;

[0084] Step D-3: the first terminal obtains SL-RadioBearerConfig including the SL-SDAP-Config;

[0085] Step D-4: The first terminal determines the SL-RLCBearerconfig corresponding to the SL-RadioBearerConfig as the SL-RLCBearerconfig corresponding to the first parameter.

[0086] The signaling structure of the target message (i.e., system broadcast message or SL pre-configuration message) is as follows: Figure 5 As shown, the target message includes multiple SL-RadioBearerConfigs and multiple SL-RLCBearerconfigs, and each SL-RadioBearerConfig corresponds to a SL-RLCBearerconfig (the one-to-one correspondence is determined by whether they include the same SLRB-Uu-ConfigIndex). Furthermore, a SL-RadioBearerConfig includes a SL-SDAP-Config, and the SL-SDAP-Config includes multiple SL-QoS-Profiles. Therefore, the SL-QoS-Profile corresponding to the first parameter can be searched in the target message. If the SL-QoS-Profile corresponding to the first parameter can be found, the SL-SDAP-Config including the SL-QoS-Profile can be obtained, and then the SL-RadioBearerConfig including the SL-SDAP-Config can be obtained, and then the SL-RLCBearerconfig corresponding to the SL-RadioBearerConfig can be obtained. In this way, the SL-RLCBearerconfig corresponding to the first parameter is obtained.

[0087] It is understood that the target message may also include Figure 5 Other content shown, Figure 5 Only part of the content is shown.

[0088] It should be noted that the SL-QoS-Profile corresponding to the first parameter here refers to an SL-QoS-Profile having at least one QoS attribute identical to that of the first parameter.

[0089] Optionally, the above step C-1 "the first terminal searches the target message for the SL-RLC Bearer config corresponding to the first parameter" further includes the following step D-5:

[0090] Step D-5: If the first terminal fails to find the SL-QoS-Profile corresponding to the first parameter, perform any one of the following steps E-1 to E-2:

[0091] Item E-1: The first terminal determines default radio bearer configuration information, and searches for the SL-RLCBearerconfig according to the default radio bearer configuration information;

[0092] Item E-2: The first terminal determines a matching parameter that is closest to at least one QoS attribute of the first parameter, and searches for the SL-RLCBearerconfig based on the matching parameter.

[0093] Among them, in item E-1, the default wireless bearer configuration information includes the default bearer SL-DefaultRB of the direct link, and SL-DefaultRB is included in SL-SDAP-Config. Therefore, based on the default wireless bearer configuration information, SL-SDAP-Config including SL-DefaultRB can be obtained, and then SL-RadioBearerConfig including SL-SDAP-Config can be obtained. In this way, the SL-RLCBearerconfig corresponding to the obtained SL-RadioBearerConfig is the SL-RLCBearerconfig corresponding to the first parameter.

[0094] In addition, in item E-2, the matching parameter closest to at least one QoS attribute of the first parameter includes the SL-QoS-Profile closest to at least one QoS attribute of the first parameter. Therefore, after searching the matching parameter, the SL-SDAP-Config including the SL-QoS-Profile can be obtained, and then the SL-RadioBearerConfig including the SL-SDAP-Config can be obtained. In this way, the SL-RLCBearerconfig corresponding to the obtained SL-RadioBearerConfig is the SL-RLCBearerconfig corresponding to the first parameter.

[0095] Optionally, the first terminal determines a matching parameter closest to the QoS attribute of the first parameter according to at least one of the following F-1 to F-3 (that is, the matching parameter closest to the QoS attribute of the first parameter satisfies at least one of the following F-1 to F-3):

[0096] Item F-1: the priority value in the matching parameter is the same as the priority value in the first parameter;

[0097] Item F-2: The packet delay budget PDB value in the matching parameter is the same as or closest to the PDB value in the first parameter; here, the PDB in the matching parameter is closest to the PDB in the first parameter, that is, the SL-QoS-Profile corresponding to the matching parameter has the PDB closest to the first parameter, which means that: among the multiple SL-QoS-Profiles included in the SL-SDAP-Config, the absolute value of the difference between the PDB of the SL-QoS-Profile corresponding to the matching parameter and the PDB in the first parameter is the smallest.

[0098] Item F-3: The packet error rate PER value in the matching parameter is the same as or closest to the packet error rate PER value in the matching parameter; here, the PER in the matching parameter is closest to the PER in the first parameter, that is, the SL-QoS-Profile corresponding to the matching parameter has a PER closest to the first parameter, which means that: among the multiple SL-QoS-Profiles included in the SL-SDAP-Config, the absolute value of the difference between the PER of the SL-QoS-Profile corresponding to the matching parameter and the PER in the first parameter is the smallest.

[0099] It can be seen that SL-SDAP-Config includes multiple SL-QoS-Profiles, and each SL-QoS-Profile has QoS attributes in multiple dimensions. Here, the SL-QoS-Profile that meets at least one of the conditions F-1 to F-3 above can be found based on at least one dimension of priority, PDB, and PER.

[0100] For example, if SL-SDAP-Config includes N SL-QoS-Profiles, the QoS attributes of each dimension of these N SL-QoS-Profiles can be compared with the QoS data of the above-mentioned first parameter. For example, the priority values ​​can be compared respectively, and the SL-QoS-Profile with the same priority value as the first parameter can be obtained; or, the PDB values ​​can be compared, and the SL-QoS-Profile that is the same as or closest to the PDB value of the first parameter can be obtained; or, the PER values ​​can be compared, and the SL-QoS-Profile that is the same as or closest to the PER value of the first parameter can be obtained, and N is an integer greater than zero.

[0101] Optionally, the above step C-2 "the first terminal determines the first configuration information according to the SL-RLC Bearer config" includes the following steps H-1 to H-2:

[0102] Step H-1: the first terminal searches for at least one of the direct link radio link control configuration information SL-RLC-Config and the direct link logical channel configuration information SL-LogicalChannelConfig in the SL-RLC Bearerconfig;

[0103] Step H-2: The first terminal uses at least one of the found SL-RLC-Config and the SL-LogicalChannelConfig as information included in the first configuration information.

[0104] Among them, SL-RLCBearerconfig includes SL-RLC-Config and SL-LogicalChannelConfig. Therefore, through the above process, after finding the SL-RLCBearerconfig corresponding to the first parameter, SL-RLC-Config and SL-LogicalChannelConfig can be found from the SL-RLCBearerconfig, and then based on at least one item of SL-RLC-Config and SL-LogicalChannelConfig, the above-mentioned first configuration information can be determined.

[0105] In order to facilitate understanding of the determination process of the first configuration information, an implementation method of determining the first configuration information by the first terminal according to the end-to-end QoS flow information and the target message is now introduced based on the above content:

[0106] Execute the search process: first parameter + target message: SL-SDAP-Config:{SL-QoS-Profile}→SL-RadioBearerConfig→SL-RLCBearerconfig→SL-RLC-Config,SL-LogicalChannelConfig→PC5 RLC channel config;

[0107] That is, in the target message, the SL-QoS-Profile corresponding to the first parameter is searched, wherein if the SL-QoS-Profile corresponding to the first parameter is found, the SL-SDAP-Config including the SL-QoS-Profile can be obtained, and then the SL-RadioBearerConfig including the SL-SDAP-Config can be obtained, and then the SL-RLCBearerconfig corresponding to the SL-RadioBearerConfig can be obtained; and then at least one of the SL-RLC-Config and the SL-LogicalChannelConfig is searched in the SL-RLCBearerconfig, and then the first configuration information is determined according to the found SL-RLC-Config and SL-LogicalChannelConfig;

[0108] If the SL-QoS-Profile corresponding to the first parameter cannot be found, the following L-1 or L-2 is executed:

[0109] Item L-1: search for the corresponding SL-RadioBearerConfig according to the default radio bearer configuration information, and then find the corresponding SL-RLCBearerconfig, thereby searching for at least one of SL-RLC-Config and SL-LogicalChannelConfig in the found SL-RLCBearerconfig, and then determine the first configuration information according to the found SL-RLC-Config and SL-LogicalChannelConfig;

[0110] Item L-2: According to the SL-QoS-Profile corresponding to the matching parameter, search for the SL-RLCBearerconfig corresponding to the SL-QoS-Profile, and then search for at least one of SL-RLC-Config and SL-LogicalChannelConfig in the found SL-RLCBearerconfig, and then determine the first configuration information based on the found SL-RLC-Config and SL-LogicalChannelConfig; wherein the matching parameter closest to at least one QoS attribute of the first parameter satisfies at least one of the conditions F-1 to F-3 above.

[0111] It should be noted that, no matter the first terminal is a Source Remote UE or a Relay UE, the process of determining the first configuration information according to the end-to-end QoS flow information and the target message can be as described above.

[0112] Optionally, the first configuration information further includes identification information of the target channel;

[0113] The identification information of the target channel is determined according to the value of at least one of the following items:

[0114] The RLC sequence number SN in the SL-RLC-Config (for example, the value of the RLC SN or the field length of the RLC SN, where the field length of the RLC SN may indicate the maximum value of the RLC SN);

[0115] The RLC mode in the SL-RLC-Config (e.g., RLC acknowledgement mode AM, unacknowledgement mode UM, transparent transmission mode TM);

[0116] The RLC retransmission number threshold value in the SL-RLC-Config (e.g., the maximum upper limit value of the RLC retransmission number);

[0117] The logical channel priority (Logical Channel Priority, LCH Priority) in the SL-LogicalChannelConfig (for example, the value of the logical channel priority).

[0118] Among them, there can be at least one of the values ​​of RLC mode, RLC SN, RLC retransmission number threshold value, and LCH Priority, wherein a combination of an RLC mode, an RLC SN value, a maximum upper limit value of the number of RLC retransmissions, and an LCH Priority value constitutes a set of configuration information of the target channel. Therefore, according to the number of RLC mode, RLC SN, RLC retransmission number threshold value, and LCH Priority values, it can be determined that there are several sets of configuration information of the target channel, so that the identification information of several target channels can be allocated. Therefore, the identification information of the above-mentioned target channel can be determined according to at least one of the RLC mode, RLC SN, RLC retransmission number threshold value, and LCH Priority.

[0119] Optionally, when the transmission configuration information includes at least the first mapping relationship, the first terminal determines the transmission configuration information of the terminal-to-terminal relay transmission according to the terminal-to-terminal QoS flow information and the target message, including:

[0120] The first terminal determines the first mapping relationship based on the mapping relationship between the end-to-end QoS flow information and the end-to-end SL data bearer determined based on the end-to-end QoS flow information and the target message, and the end-to-end QoS flow information corresponding to the target channel.

[0121] From this, it can be seen that if the mapping relationship between end-to-end QoS flow information and end-to-end SL data bearer, as well as the end-to-end QoS flow information corresponding to the target channel are known, then the end-to-end SL data bearer and the target channel can be associated with a unique end-to-end QoS flow respectively, and therefore the first mapping relationship between the target channel and the end-to-end SL data bearer can be determined.

[0122] Optionally, the method further comprises:

[0123] The first terminal sends at least one of the following V-1 to V-3 to the second terminal:

[0124] Item V-1: at least one set of first target information, wherein the set of first target information includes a set of configuration information of a PC5 RLC channel between the first terminal and the second terminal;

[0125] Item V-2: a mapping relationship between an end-to-end SL data bearer and one of the at least one set of first target information;

[0126] Item V-3: a second mapping relationship, wherein the second mapping relationship includes a mapping relationship between end-to-end QoS flow information and end-to-end SL data bearer;

[0127] The second terminal is a next-hop terminal of the first terminal.

[0128] It should be noted that, as mentioned above, the first terminal can determine the identification information of the above-mentioned target channel based on at least one of the RLC mode, RLC SN, RLC retransmission number threshold value, and LCH Priority. Among them, the first terminal determines how many identification information to allocate to the target channel based on at least one of the RLC mode, RLC SN, RLC retransmission number threshold value, and LCH Priority, which indicates that there are several sets of configuration information for the target channel (i.e., the PC5 RLC channel between the first terminal and the second terminal).

[0129] In addition, when the first terminal is a Source Remote UE, the first terminal may send at least one of the above V-1 to V-3 to the second terminal; when the first terminal is a Relay UE, the first terminal may send at least one of the above V-1 to V-2 to the second terminal.

[0130] Optionally, in the case where the first terminal is a source remote terminal, the transmission configuration information further includes: a second mapping relationship, the second mapping relationship including a mapping relationship between end-to-end QoS flow information and end-to-end SL data bearer;

[0131] The first terminal determines, according to the end-to-end QoS flow information and the target message, transmission configuration information for the end-to-end relay transmission, including:

[0132] The first terminal searches the target message for the SL-RadioBearerConfig corresponding to the QoS parameters of the end-to-end QoS flow;

[0133] When the SL-RadioBearerConfig corresponding to the QoS parameters of the end-to-end QoS flow is found, the first terminal determines the identification information of the end-to-end SL data bearer based on the index value of the SL-RadioBearerConfig corresponding to the QoS parameters of the end-to-end QoS flow, and establishes the second mapping relationship between the end-to-end QoS flow information and the identification information of the end-to-end SL data bearer.

[0134] It can be seen that the specific method for the first terminal to determine the second mapping relationship based on the end-to-end QoS flow information and the target message is: E2E QoS flow info->E2E QoS profile+target message: SL-SDAP-Config:{SL-QoS-Profile}→SL-RadioBearerConfig; that is, search for the SL-QoS-Profile corresponding to the E2E QoS profile in the target message, so as to obtain the SL-SDAP-Config including the SL-QoS-Profile, and then obtain the SL-RadioBearerConfig including the SL-SDAP-Config. Among them, the found SL-RadioBearerConfig has several index values, which determines how many SL bearer identifiers need to be allocated to distinguish different end-to-end SL data bearers.

[0135] Optionally, when the first terminal is a relay terminal, the method further includes:

[0136] The first terminal receives second target information sent by a third terminal, where the third terminal is a previous hop terminal of the relay terminal;

[0137] The second target information includes at least one of the following:

[0138] at least one set of third target information, wherein the set of third target information includes a set of configuration information of a PC5 RLC channel between the third terminal and the first terminal;

[0139] a mapping relationship between an end-to-end SL data bearer and one of the sets of third target information in the at least one set of third target information;

[0140] The second mapping relationship includes a mapping relationship between end-to-end QoS flow information and end-to-end SL data bearer.

[0141] When the first terminal is a relay terminal, the previous hop terminal of the relay terminal may be a Source Remote UE or another Relay UE.

[0142] In addition, the process of determining the at least one set of third target information is the same as the process of determining the at least one set of first target information described above, and will not be repeated here.

[0143] Optionally, when the first terminal is a relay terminal, the method further includes:

[0144] The first terminal determines target QoS flow information mapped to the same end-to-end SL data bearer;

[0145] In a case where the target QoS flow information corresponds to multiple sets of configuration information of target channels, the first terminal selects one set of configuration information of the multiple sets of target channels to be mapped to the target QoS flow information;

[0146] The target channel includes a PC5 RLC channel between the first terminal and a second terminal, and the second terminal is a next-hop terminal of the first terminal.

[0147] For example, in a single-hop U2U architecture, in the first hop, QoS flows 1 and 2 are mapped to PC5 RLC channel 1, and the SDAP header format is E2E SL-DRB1. However, the results of splitting end-to-end QoS parameters for different QoS flows may vary greatly. For example, after QoS flow 1 is split, it is 20ms+80ms, and after QoS flow 2 is split, it is 50ms+50ms.

[0148] In the second hop, QoS flow 1 is mapped on PC5 RLC channel 2, and the SDAP header format is E2E SL-DRB1, and QoS flow 2 is mapped on PC5 RLC channel 3 and the SDAP header format is SL-DRB1.

[0149] It should be noted that the results of splitting the end-to-end QoS parameters of QoS flows 1 and 2 to the first hop and the second hop are different. Therefore, even if QoS flows 1 and 2 can be mapped to the same PC5 RLC Channel at the first hop, the configuration information of the PC5 RLC Channel obtained based on different QoS parameters of the second hop may be different at the second hop. In this way, the data of QoS flows 1 and 2 received by the RelayUE will no longer be mapped to the same channel. In this case, the Relay UE needs to distinguish which E2E QoS flow the received data belongs to.

[0150] However, the SRAP header format cannot distinguish different E2E QoS flows, unless the UE additionally reads the SDAP header format on this basis to know which E2E QoS flow the SRAP PDU data corresponds to, but this will bring additional UE complexity.

[0151] Based on this problem, in an embodiment of the present application, for different QoS flow information mapped to the same end-to-end SL data bearer, if there are multiple sets of target channel configuration information corresponding to these QoS flow information, one set of configuration information is selected so that these QoS flow information are mapped to the same target channel. In this way, the Relay UE does not need to read the SDAP header format across layers, but determines the unique target channel at this layer through the end-to-end bearer identification information contained in the SRAP header format.

[0152] That is, to solve this problem, after the Relay UE determines that there are several sets of configuration information for the PC5 RLC channel between the first terminal and the second terminal, at least one of the following conditions needs to be met:

[0153] (1) Relay UE cannot allocate different PC5RLC Channel configuration information to different E2E QoS flows on the same end-to-end bearer;

[0154] (2) Relay UE can be allocated different PC5 RLC Channel configuration information or the same PC5 RLC channel configuration information for different E2E QoS flows on different end-to-end bearers.

[0155] Optionally, the first terminal determines, according to the end-to-end quality of service QoS flow information and the target message, transmission configuration information of the terminal-to-terminal relay transmission, including:

[0156] When the first terminal is in a state of network coverage (IC), the first terminal determines transmission configuration information of terminal-to-terminal relay transmission according to end-to-end quality of service QoS flow information and a system broadcast message;

[0157] When the first terminal is in an out-of-coverage (OOC) state, the first terminal determines transmission configuration information of terminal-to-terminal relay transmission according to end-to-end quality of service QoS flow information and SL pre-configuration message.

[0158] From this, it can be seen that if the first terminal is in the IC state, the transmission configuration information of the terminal-to-terminal relay transmission can be determined based on the end-to-end QoS flow information and the system broadcast message; if the first terminal is in the OOC state, the transmission configuration information of the terminal-to-terminal relay transmission can be determined based on the end-to-end QoS flow information and the SL pre-configuration message.

[0159] It should be noted that, among the various information included in the transmission configuration information for determining terminal-to-terminal relay transmission mentioned above, if the first terminal is in the IC state, the target message mentioned above is the system broadcast message; if the first terminal is in the OCC state, the target message mentioned above is the SL pre-configuration message.

[0160] Optionally, when the first terminal is in a state where there is network coverage IC, the first terminal determines the transmission configuration information of the terminal-to-terminal relay transmission according to the end-to-end quality of service QoS flow information and the system broadcast message, including:

[0161] When the first terminal is in a state with network coverage IC and satisfies any of the following states I-1 to I-3, the first terminal determines the transmission configuration information of the terminal-to-terminal relay transmission according to the end-to-end quality of service QoS flow information and the target message:

[0162] Item I-1: Radio Resource Control RRC Idle State;

[0163] Item I-2: RRC inactive state;

[0164] Item I-3: RRC connected state and working in SL resource scheduling mode 2.

[0165] It can be seen from this that if the first terminal is in the IC state, it can determine the transmission configuration information of the terminal-to-terminal relay transmission according to the end-to-end service quality QoS flow information and the target message in any of the states I-1 to I-3 above.

[0166] In summary, the specific implementation of the transmission configuration determination method in the embodiment of the present application can be described in the following implementation mode 1 or 2:

[0167] Implementation method 1: The Source Remote UE determines transmission configuration information of terminal-to-terminal relay transmission;

[0168] Case 1: The Source Remote UE is within the network coverage, for example, it can be in RRC_IDLE state, or RRC_INCATIVE state, or RRC_CONNECTED state and works in SL resource scheduling mode 2 (mode-2). The specific implementation process is as described in steps 1.1 to 1.3 below:

[0169] Step 1.1: The Source Remote UE determines the QoS parameters of the first hop (i.e., between the Source Remote UE and the Relay UE) (i.e., 1 stPer-hop QoS profile) and the content of SIB12 message determine the "first hop PC5 RLC channel configuration information":

[0170] Here, the specific search method is: 1 st Per-hop QoS profile+SIB12→SL-SDAP-Config:{SL-QoS-Profile}→SL-RadioBearerConfig→SL-RLCBearerconfig→SL-RLC-Config,SL-LogicalChannelConfig→PC5 RLC channel config;

[0171] That is, search for the SL-QoS-Profile corresponding to the first-hop QoS parameters in SIB12. If it can be found, obtain the SL-SDAP-Config including the SL-QoS-Profile, and then obtain the SL-RadioBearerConfig including the SL-SDAP-Config, and then search for SL-RLC-Config and SL-LogicalChannelConfig in the SL-RLCBearerconfig corresponding to the SL-RadioBearerConfig; and then determine the first-hop PC5 RLC channel configuration information according to the found SL-RLC-Config and SL-LogicalChannelConfig;

[0172] If the SL-QoS-Profile corresponding to the first-hop QoS parameters cannot be found, execute the following 1.1-1 or 1.1-2:

[0173] Item 1.1-1: Search for the corresponding SL-RadioBearerConfig according to the default radio bearer configuration information, and then find the corresponding SL-RLCBearerconfig, thereby searching for at least one of SL-RLC-Config and SL-LogicalChannelConfig in the found SL-RLCBearerconfig, and then determine the first configuration information according to the found SL-RLC-Config and SL-LogicalChannelConfig;

[0174] 1.1-2: Find the SL-QoS-Profile that meets the first target condition, thereby finding the SL-RLCBearerconfig corresponding to the SL-QoS-Profile, and then find at least one of SL-RLC-Config and SL-LogicalChannelConfig in the found SL-RLCBearerconfig, and then determine the first hop PC5 RLC channel configuration information according to the found SL-RLC-Config and SL-LogicalChannelConfig; wherein the first target condition includes at least one of the following:

[0175] SL-QoS-Profile and 1 st The priority values ​​included in the per-hop QoS profile are the same;

[0176] SL-QoS-Profile and 1 st The PDB values ​​in the Per-hop QoS profile are the same or closest (having the closest PDB);

[0177] SL-QoS-Profile and 1 st The PER values ​​in the per-hop QoS profile are the same or closest (having the closest PER).

[0178] That is, SL-SDAP-Config includes multiple SL-QoS-Profiles, and each SL-QoS-Profile has parameters of multiple dimensions. Here, the SL-QoS-Profile that meets the above target conditions can be found based on at least one of priority, PDB, and PER.

[0179] Wherein: According to the obtained SL-RLC-Config and SL-LogicalChannelConfig, the first-hop PC5RLC Channel configuration information obtained includes at least one of the following:

[0180] RLC mode;

[0181] RLC SN (e.g., the value of the SN, or the length of the SN field, where the length of the SN field may indicate the maximum value of the SN);

[0182] RLC retransmission number threshold;

[0183] Logical channel priority (LCH Priority).

[0184] In addition: according to the number of parameter values ​​in the finally obtained first-hop PC5 RLC channel configuration information, it is determined that several LCG IDs need to be allocated to distinguish different PC5 RLC channels.

[0185] Here, it should be noted that there can be at least one of the values ​​of RLC mode, RLC SN, RLC retransmission number threshold, and LCH Priority, wherein at least one of the values ​​of an RLC mode, an RLC SN, a maximum upper limit value of the number of RLC retransmissions, and a LCH Priority constitutes a set of PC5 RLC channel configuration information. Therefore, according to the number of RLC mode, RLC SN, the maximum upper limit value of the number of RLC retransmissions, and LCH Priority values, it can be determined how many sets of PC5 RLC channel configuration information exist, and thus how many PC5 RLC channel identification information can be allocated.

[0186] Step 1.2: The Source Remote UE determines the mapping relationship between the end-to-end QoS flow information and the end-to-end SL data bearer according to the content of the end-to-end QoS flow information (E2E QoS flow info) and the SIB12 message:

[0187] The specific determination method is: E2E QoS flow info->E2E QoS profile+SIB12→SL-SDAP-Config:{SL-QoS-Profile}→SL-RadioBearerConfig; that is, search the SIB12 message for the SL-QoS-Profile corresponding to the E2E QoS profile in the E2E QoS flowinfo, and then search for the SL-RadioBearerConfig corresponding to the SL-QoS-Profile (that is, search for the SL-SDAP-Config including the SL-QoS-Profile, and then obtain the SL-RadioBearerConfig including the SL-SDAP-Config).

[0188] Among them, the found SL-RadioBearerConfig has several index values, which determines how many SL bearer identifiers need to be allocated to distinguish different end-to-end SL data bearers, and establishes a mapping relationship between the SL bearer identifier and the end-to-end QoS flow information.

[0189] In addition, the end-to-end QoS flow information (E2E QoS flow info) is composed of the end-to-end QoS flow identity (E2E QoS flow identity) and the end-to-end QoS parameters (E2E QoS profile). Here, the E2E QoS profile can be divided into all hops included in the end-to-end relay transmission. For example, in the U2U Relay link, it can be divided into the first hop and the second hop. Then the parameter divided into the first hop can be called 1 st Per-hop QoS profile, the parameters for splitting into the second hop can be called 2 nd Per-hop QoS profile.

[0190] In addition, it should be noted that the execution order of the above steps 1.1 and 1.2 can be any order.

[0191] Step 1.3: Send at least one of the following content configuration information to the Relay UE via PC5 RRC message:

[0192] At least one set of first-hop PC5 RLC Channel configuration information;

[0193] A mapping relationship between an end-to-end SL data bearer and a set of PC5 RLC Channel configuration information in the at least one set of first-hop PC5 RLC Channel configuration information;

[0194] The mapping relationship between end-to-end QoS flow information and end-to-end SL data bearer.

[0195] It should be noted that step 1.1 can be based on 1 st Per-hop QoS profile obtains the corresponding first-hop PC5 RLC Channel configuration information, and 1 st Per-hop QoS profile is obtained by splitting the end-to-end QoS profile in the end-to-end QoS flow information. Therefore, the mapping relationship between the end-to-end QoS flow information and the first-hop PC5 RLC Channel configuration information can be obtained; through the above step 1.2, the mapping relationship between the end-to-end QoS flow information and the end-to-end SL data bearer can be obtained. Therefore, based on the above two mapping relationships, the mapping relationship between the end-to-end SL data bearer and the first-hop PC5 RLC Channel configuration information can be obtained.

[0196] Case 2: The Source Remote UE is out of network coverage, and the Source Remote UE determines the transmission configuration information of the terminal-to-terminal relay transmission according to the content of the SL pre-configuration message. In this case, the content of the SIB12 message in the above case 1 in this implementation is replaced with the SL pre-configuration message, and the other execution steps are the same.

[0197] Implementation method 2: Relay UE determines transmission configuration information of terminal-to-terminal relay transmission;

[0198] Case 1: The Relay UE is within the network coverage, for example, it may be in RRC_IDLE state, or RRC_INCATIVE state, or RRC_CONNECTED state and works in SL resource scheduling mode 2 (mode-2). The specific implementation process is as described in steps 2.1 to 2.4 below:

[0199] Step 2.1: The Relay UE receives at least one of the following configuration information sent by the Source Remote UE via a PC5 RRC message:

[0200] At least one set of first-hop PC5 RLC Channel configuration information;

[0201] A mapping relationship between an end-to-end SL data bearer and a set of PC5 RLC Channel configuration information in the at least one set of first-hop PC5 RLC Channel configuration information;

[0202] The mapping relationship between end-to-end QoS flow information and end-to-end SL data bearer.

[0203] Step 2.2: The Relay Remote UE determines the QoS parameters of the second hop (i.e., between the Relay UE and the Target Remote UE) (i.e., 2 nd Per-hop QoS profile) and the content of SIB12 message determine the "second hop PC5 RLC channel configuration information":

[0204] Here, the specific search method is: 2 nd Per-hop QoS profile+SIB12→SL-SDAP-Config:{SL-QoS-Profile}→SL-RadioBearerConfig→SL-RLCBearerconfig→SL-RLC-Config,SL-LogicalChannelConfig→PC5 RLC channel config;

[0205] That is, search for the SL-QoS-Profile corresponding to the second-hop QoS parameters in SIB12. If it can be found, obtain the SL-SDAP-Config including the SL-QoS-Profile, and then obtain the SL-RadioBearerConfig including the SL-SDAP-Config, and then search for SL-RLC-Config and SL-LogicalChannelConfig in the SL-RLCBearerconfig corresponding to the SL-RadioBearerConfig, and then determine the second-hop PC5 RLC channel configuration information according to the found SL-RLC-Config and SL-LogicalChannelConfig;

[0206] If the SL-QoS-Profile corresponding to the second-hop QoS parameters cannot be found, execute the following 2.2-1 or 2.2-2:

[0207] Item 2.2-1: Find the corresponding SL-RadioBearerConfig according to the default radio bearer configuration information, and then find the corresponding SL-RLCBearerconfig, and then find at least one of SL-RLC-Config and SL-LogicalChannelConfig in the found SL-RLCBearerconfig, and then determine the second-hop PC5 RLC channel configuration information according to the found SL-RLC-Config and SL-LogicalChannelConfig;

[0208] Item 2.2-2: Find the SL-QoS-Profile that meets the second target condition, thereby finding the SL-RLCBearerconfig corresponding to the SL-QoS-Profile, and then find at least one of SL-RLC-Config and SL-LogicalChannelConfig in the found SL-RLCBearerconfig, and then determine the second hop PC5 RLC channel configuration information according to the found SL-RLC-Config and SL-LogicalChannelConfig; wherein the second target condition includes at least one of the following:

[0209] SL-QoS-Profile and 2 nd The priority values ​​included in the per-hop QoS profile are the same;

[0210] SL-QoS-Profile and 2 nd The PDB values ​​in the Per-hop QoS profile are the same or closest (having the closest PDB);

[0211] SL-QoS-Profile and 2 nd The PER values ​​in the per-hop QoS profile are the same or closest (having the closest PER).

[0212] That is, SL-SDAP-Config includes multiple SL-QoS-Profiles, and each SL-QoS-Profile has parameters of multiple dimensions. Here, the SL-QoS-Profile that meets the above target conditions can be found based on at least one of priority, PDB, and PER.

[0213] Wherein: according to the obtained SL-RLC-Config and SL-LogicalChannelConfig, the second-hop PC5RLC Channel configuration information obtained includes at least one of the following:

[0214] RLC mode;

[0215] RLC SN (e.g., the value of the SN, or the length of the SN field, where the length of the SN field may indicate the maximum value of the SN);

[0216] RLC retransmission number threshold;

[0217] Logical channel priority (LCH Priority).

[0218] In addition, according to the number of parameter values ​​in the finally obtained second-hop PC5 RLC channel configuration information, it is determined that several Channel ID identifiers (ie, LCID values) need to be allocated to distinguish different PC5 RLC channels.

[0219] Here, it should be noted that there can be at least one of the values ​​of RLC mode, RLC SN, RLC retransmission number threshold, and LCH Priority, wherein at least one of the values ​​of an RLC mode, an RLC SN, a maximum upper limit of the number of RLC retransmissions, and an LCH Priority constitutes a set of PC5 RLC channel configuration information. Therefore, according to the number of RLC mode, RLC SN, RLC retransmission number threshold, and LCH Priority values, it can be determined how many sets of PC5 RLC channel configuration information exist, and thus how many PC5 RLC channel identification information can be allocated.

[0220] After the Relay UE executes the above search method (i.e., after finding SL-RLC-Config and SL-LogicalChannelConfig), in addition to distinguishing different PC5 RLC channels according to the parameter values ​​in the PC5 RLC channel configuration information, it also needs to meet at least one of the following conditions:

[0221] (1) Relay UE cannot allocate different PC5RLC Channel configuration information to different E2E QoS flows on the same end-to-end bearer;

[0222] (2) Relay UE can be allocated different PC5 RLC Channel configuration information or the same PC5 RLC channel configuration information for different E2E QoS flows on different end-to-end bearers.

[0223] That is, if there are multiple sets of configuration information for the PC5 RLC Channel corresponding to different E2E QoS flows on the same bearer, one set of configuration information can be selected to be mapped with these E2E QoS flows.

[0224] Step 2.3: The Relay UE determines the mapping relationship between the second-hop RLC channel and the end-to-end SL data bearer based on the end-to-end QoS flow information (E2E QoS flow info) and the PC5 RRC content received in step 2.1:

[0225] That is, in the above step 2.2, based on 2 nd Per-hop QoS profile determines the second hop PC5 RLC channel configuration information, and 2 ndPer-hop QoS profile is split based on the E2E QoS profile included in the end-to-end QoS flow channel. Therefore, on this basis, the end-to-end QoS flow information and the second-hop PC5 RLC channel can be obtained;

[0226] In the above step 2.1, the Relay UE receives the mapping relationship between the end-to-end QoS flow information and the end-to-end SL data bearer sent by the Source Remote UE;

[0227] Therefore, based on the combination of the above two points, since the configuration information source is associated with a unique end-to-end QoS flow, the "mapping relationship between the second-hop RLC channel and the end-to-end SL data bearer" can be determined.

[0228] It should be noted that the execution order of the above steps 2.2 and 2.3 can be any order.

[0229] Step 2.4: Send at least one of the following configuration information to the Target Remote UE via PC5 RRC message:

[0230] At least one set of second-hop PC5 RLC Channel configuration information;

[0231] End-to-end SL data is carried to a set of PC5 RLC in the at least one set of second-hop PC5 RLC Channel configuration information.

[0232] The mapping relationship of Channel configuration information.

[0233] Case 2: The Relay UE is out of network coverage, and the Relay UE determines the transmission configuration information of the terminal-to-terminal relay transmission according to the content of the SL pre-configuration information message. In this case, the content of the SIB12 message in the above case 1 in this implementation is replaced with the SL pre-configuration information message, and the other execution steps are the same.

[0234] It can be seen from the above-mentioned embodiments one and two that in the embodiments of the present application, based on terminal-to-terminal relay transmission, a configuration information method that does not require the participation of a base station is proposed, that is, it mainly relies on the Relay UE and the Remote UE to deduce the required sets of PC5 RLC Channel configuration information and specific mapping based on the content of the existing SIB12 broadcast message or SL pre-configuration information message. It is a solution that is more suitable for non-connected UEs.

[0235] Moreover, in the embodiments of the present application, the base station only needs to support the existing SL function (i.e., SIB12 and SL pre-configuration information messages of the R16 version) to be expanded to support the SL-based U2U relay scenario, which greatly reduces the signaling overhead of dedicated configuration information and the complexity of development and upgrade.

[0236] The transmission configuration determination method provided in the embodiment of the present application may be executed by a transmission configuration determination device. In the embodiment of the present application, the transmission configuration determination device executing the transmission configuration determination method is taken as an example to illustrate the transmission configuration determination device provided in the embodiment of the present application.

[0237] In a second aspect, an embodiment of the present application provides a transmission configuration determination device, such as Figure 6 As shown, the transmission configuration determination device 50 includes the following modules:

[0238] Configuration determination module 501, used to determine transmission configuration information of terminal-to-terminal relay transmission according to end-to-end quality of service QoS flow information and target message;

[0239] The target message includes a system broadcast message or a direct link SL pre-configuration message.

[0240] Optionally, the end-to-end quality of service (QoS) flow information includes at least one of the following:

[0241] End-to-end QoS flow identification QoS-FlowIdentity;

[0242] QoS parameter set QoS-Profile for end-to-end QoS flow;

[0243] The hop-by-hop QoS parameters corresponding to the QoS parameter set of the end-to-end QoS flow.

[0244] Optionally, the transmission configuration information includes at least one of the following:

[0245] First configuration information, the first configuration includes configuration information of a target channel, the target channel includes a direct communication interface PC5 radio link control RLC channel between the first terminal and the second terminal, the second terminal being a next hop terminal of the first terminal;

[0246] A first mapping relationship, wherein the first mapping relationship includes a mapping relationship between an end-to-end SL data bearer and the target channel.

[0247] Optionally, when the transmission configuration information includes at least the first configuration information, the configuration determination module 501 includes:

[0248] A first search submodule is used to search for direct link radio link control bearer configuration information SL-RLCBearerconfig corresponding to a first parameter in the target message, wherein the first parameter includes a QoS parameter of a hop corresponding to the first terminal and the second terminal;

[0249] The first determination submodule is used to determine the first configuration information according to the SL-RLCBearerconfig.

[0250] Optionally, the first search submodule is specifically used for:

[0251] Searching the target message for a through link service quality parameter set SL-QoS-Profile corresponding to the first parameter;

[0252] When the first terminal finds the SL-QoS-Profile corresponding to the first parameter, obtain direct link service data adaptation protocol configuration information SL-SDAP-Config including the SL-QoS-Profile corresponding to the first parameter;

[0253] Obtain SL-RadioBearerConfig including the SL-SDAP-Config;

[0254] The SL-RLCBearerconfig corresponding to the SL-RadioBearerConfig is determined as the SL-RLCBearerconfig corresponding to the first parameter.

[0255] Optionally, the first search submodule is further used for:

[0256] If the first terminal fails to find the SL-QoS-Profile corresponding to the first parameter, perform any of the following:

[0257] Determine default radio bearer configuration information, and search for the SL-RLCBearerconfig according to the default radio bearer configuration information;

[0258] Determine a matching parameter that is closest to at least one QoS attribute of the first parameter, and search for the SL-RLCBearerconfig according to the matching parameter.

[0259] Optionally, the first search submodule determines a matching parameter closest to the QoS attribute of the first parameter according to at least one of the following:

[0260] The priority value in the matching parameter is the same as the priority value in the first parameter;

[0261] The packet delay budget PDB value in the matching parameter is the same as or closest to the PDB value in the first parameter;

[0262] The packet error rate PER value in the matching parameter is the same as or closest to the packet error rate PER value in the matching parameter.

[0263] Optionally, the first determining submodule is specifically used to:

[0264] Searching at least one of the direct link radio link control configuration information SL-RLC-Config and the direct link logical channel configuration information SL-LogicalChannelConfig in the SL-RLCBearerconfig;

[0265] At least one of the found SL-RLC-Config and the SL-LogicalChannelConfig is used as information included in the first configuration information.

[0266] Optionally, the first configuration information further includes identification information of the target channel;

[0267] The identification information of the target channel is determined according to the value of at least one of the following items:

[0268] The RLC sequence number SN in the SL-RLC-Config;

[0269] RLC mode in the SL-RLC-Config;

[0270] The RLC retransmission number threshold in the SL-RLC-Config;

[0271] The logical channel priority in the SL-LogicalChannelConfig.

[0272] Optionally, when the transmission configuration information includes at least the first mapping relationship, the configuration determination module 501 further includes:

[0273] The second determination submodule is used to determine the first mapping relationship based on the mapping relationship between the end-to-end QoS flow information and the end-to-end SL data bearer determined based on the end-to-end QoS flow information and the target message, and the end-to-end QoS flow information corresponding to the target channel.

[0274] Optionally, the device further comprises:

[0275] The first sending module is configured to send at least one of the following items to the second terminal:

[0276] at least one set of first target information, wherein the set of first target information includes a set of configuration information of a PC5 RLC channel between the first terminal and the second terminal;

[0277] a mapping relationship between an end-to-end SL data bearer and one of the at least one set of first target information;

[0278] A second mapping relationship, wherein the second mapping relationship includes a mapping relationship between end-to-end QoS flow information and end-to-end SL data bearer;

[0279] The second terminal is a next-hop terminal of the first terminal.

[0280] Optionally, in the case where the first terminal is a source remote terminal, the transmission configuration information further includes: a second mapping relationship, the second mapping relationship including a mapping relationship between end-to-end QoS flow information and end-to-end SL data bearer;

[0281] The configuration determination module 501 further includes:

[0282] A second search submodule, configured to search, in the target message, for an SL-RadioBearerConfig corresponding to the QoS parameters of the end-to-end QoS flow;

[0283] The third determination submodule is used to determine the identification information of the end-to-end SL data bearer according to the index value of the SL-RadioBearerConfig corresponding to the QoS parameters of the end-to-end QoS flow when the SL-RadioBearerConfig corresponding to the QoS parameters of the end-to-end QoS flow is found, and establish the second mapping relationship between the end-to-end QoS flow information and the identification information of the end-to-end SL data bearer.

[0284] Optionally, when the first terminal is a relay terminal, the apparatus further includes:

[0285] A receiving module, configured to receive second target information sent by a third terminal, where the third terminal is a previous hop terminal of the relay terminal;

[0286] The second target information includes at least one of the following:

[0287] at least one set of third target information, wherein the set of third target information includes a set of configuration information of a PC5 RLC channel between the third terminal and the first terminal;

[0288] a mapping relationship between an end-to-end SL data bearer and one of the sets of third target information in the at least one set of third target information;

[0289] The second mapping relationship includes a mapping relationship between end-to-end QoS flow information and end-to-end SL data bearer.

[0290] Optionally, when the first terminal is a relay terminal, the apparatus further includes:

[0291] A flow information determination module, used to determine target QoS flow information mapped to the same end-to-end SL data bearer;

[0292] A selection module, configured to select, when the target QoS flow information corresponds to multiple sets of configuration information of target channels, one set of configuration information of the target channels from the multiple sets of configuration information of the target channels, and map it to the target QoS flow information;

[0293] The target channel includes a PC5 RLC channel between the first terminal and a second terminal, and the second terminal is a next-hop terminal of the first terminal.

[0294] Optionally, the configuration determination module 501 includes:

[0295] A fourth determination submodule, configured to determine, when the first terminal is in a state where there is network coverage IC, transmission configuration information of terminal-to-terminal relay transmission according to end-to-end quality of service QoS flow information and system broadcast messages;

[0296] The fifth determination submodule is used to determine the transmission configuration information of the terminal-to-terminal relay transmission according to the end-to-end service quality QoS flow information and the SL pre-configuration message when the first terminal is in the state of being out of network coverage OOC.

[0297] Optionally, the fourth determining submodule is specifically used to:

[0298] When the first terminal is in a state where there is network coverage IC and any of the following states is met, the first terminal determines the transmission configuration information of the terminal-to-terminal relay transmission according to the end-to-end quality of service QoS flow information and the target message:

[0299] Radio resource control RRC idle state;

[0300] RRC inactive state;

[0301] RRC is in connected state and works in SL resource scheduling mode 2.

[0302] The transmission configuration determination device in the embodiment of the present application may 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 may be a terminal, or may be other devices other than a terminal. Exemplarily, the terminal may include but is not limited to the types of terminals 11 listed above, and other devices may be servers, network attached storage (NAS), etc., which are not specifically limited in the embodiment of the present application.

[0303] The transmission configuration determination device provided in the embodiment of the present application can achieve Figure 4 The various processes implemented by the method embodiment and achieving the same technical effect are not described here to avoid repetition.

[0304] like Figure 7 As shown, the embodiment of the present application further provides a communication device 600, including a processor 601 and a memory 602, and the memory 602 stores a program or instruction that can be run on the processor 601. For example, when the communication device 600 is a terminal, the program or instruction is executed by the processor 601 to implement the various steps of the above-mentioned transmission configuration determination method embodiment, and can achieve the same technical effect. When the communication device 600 is a network side device, the program or instruction is executed by the processor 601 to implement the various steps of the above-mentioned transmission configuration determination method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0305] 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 Figure 4 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, Figure 8 A schematic diagram of the hardware structure of a terminal for implementing an embodiment of the present application.

[0306] The terminal 700 includes but is not limited to: a radio frequency unit 701, a network module 702, an audio output unit 703, an input unit 704, a sensor 705, a display unit 706, a user input unit 707, an interface unit 708, a memory 709 and at least some of the components of a processor 710.

[0307] Those skilled in the art will appreciate that the terminal 700 may also include a power source (such as a battery) for supplying power to various components, and the power source may be logically connected to the processor 710 through a power management system, thereby implementing functions such as managing charging, discharging, and power consumption management through the power management system. Figure 8The 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.

[0308] It should be understood that in the embodiment of the present application, the input unit 704 may include a graphics processing unit (GPU) 7041 and a microphone 7042, and the graphics processor 7041 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 706 may include a display panel 7061, and the display panel 7061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 707 includes a touch panel 7071 and at least one of other input devices 7072. The touch panel 7071 is also called a touch screen. The touch panel 7071 may include two parts: a touch detection device and a touch controller. Other input devices 7072 may include, but are not limited to, a physical keyboard, function keys (such as a volume control button, a switch button, etc.), a trackball, a mouse, and a joystick, which will not be repeated here.

[0309] In the embodiment of the present application, after receiving downlink data from the network side device, the RF unit 701 can transmit the data to the processor 710 for processing; in addition, the RF unit 701 can send uplink data to the network side device. Generally, the RF unit 701 includes but is not limited to an antenna, an amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, etc.

[0310] The memory 709 can be used to store software programs or instructions and various data. The memory 709 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 709 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 709 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.

[0311] The processor 710 may include one or more processing units; optionally, the processor 710 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 710.

[0312] The terminal 700 is used as a first terminal, and the processor 710 is used to:

[0313] Determine transmission configuration information of terminal-to-terminal relay transmission according to end-to-end quality of service QoS flow information and target message;

[0314] The target message includes a system broadcast message or a direct link SL pre-configuration message.

[0315] Optionally, the end-to-end quality of service (QoS) flow information includes at least one of the following:

[0316] End-to-end QoS flow identification QoS-FlowIdentity;

[0317] QoS parameter set QoS-Profile for end-to-end QoS flow;

[0318] The hop-by-hop QoS parameters corresponding to the QoS parameter set of the end-to-end QoS flow.

[0319] Optionally, the transmission configuration information includes at least one of the following:

[0320] First configuration information, the first configuration includes configuration information of a target channel, the target channel includes a direct communication interface PC5 radio link control RLC channel between the first terminal and the second terminal, the second terminal being a next hop terminal of the first terminal;

[0321] A first mapping relationship, wherein the first mapping relationship includes a mapping relationship between an end-to-end SL data bearer and the target channel.

[0322] Optionally, when the transmission configuration information includes at least the first configuration information, the processor 710 determines the transmission configuration information of the terminal-to-terminal relay transmission according to the terminal-to-terminal QoS flow information and the target message, including:

[0323] Searching for direct link radio link control bearer configuration information SL-RLCBearerconfig corresponding to a first parameter in the target message, wherein the first parameter includes a QoS parameter of a hop corresponding to the first terminal and the second terminal;

[0324] Determine the first configuration information according to the SL-RLCBearerconfig.

[0325] Optionally, the processor 710 searches the target message for an SL-RLCBearerconfig corresponding to the first parameter, including:

[0326] Searching the target message for a through link quality of service parameter set SL-QoS-Profile corresponding to the first parameter;

[0327] When the SL-QoS-Profile corresponding to the first parameter is found, obtaining direct link service data adaptation protocol configuration information SL-SDAP-Config including the SL-QoS-Profile corresponding to the first parameter;

[0328] Obtain SL-RadioBearerConfig including the SL-SDAP-Config;

[0329] The SL-RLCBearerconfig corresponding to the SL-RadioBearerConfig is determined as the SL-RLCBearerconfig corresponding to the first parameter.

[0330] Optionally, the processor 710 searches the target message for a SL-RLCBearerconfig corresponding to the first parameter, further comprising:

[0331] If the SL-QoS-Profile corresponding to the first parameter is not found, perform any of the following:

[0332] Determine default radio bearer configuration information, and search for the SL-RLCBearerconfig according to the default radio bearer configuration information;

[0333] Determine a matching parameter that is closest to at least one QoS attribute of the first parameter, and search for the SL-RLCBearerconfig according to the matching parameter.

[0334] Optionally, the processor 710 determines a matching parameter that is closest to the QoS attribute of the first parameter according to at least one of the following:

[0335] The priority value in the matching parameter is the same as the priority value in the first parameter;

[0336] The packet delay budget PDB value in the matching parameter is the same as or closest to the PDB value in the first parameter;

[0337] The packet error rate PER value in the matching parameter is the same as or closest to the packet error rate PER value in the matching parameter.

[0338] Optionally, the processor 710 determines, according to the SL-RLC Bearer config, the first configuration information, including:

[0339] Searching at least one of the direct link radio link control configuration information SL-RLC-Config and the direct link logical channel configuration information SL-LogicalChannelConfig in the SL-RLCBearerconfig;

[0340] At least one of the found SL-RLC-Config and the SL-LogicalChannelConfig is used as information included in the first configuration information.

[0341] Optionally, the first configuration information further includes identification information of the target channel;

[0342] The identification information of the target channel is determined according to the value of at least one of the following items:

[0343] The RLC sequence number SN in the SL-RLC-Config;

[0344] RLC mode in the SL-RLC-Config;

[0345] The RLC retransmission number threshold in the SL-RLC-Config;

[0346] The logical channel priority in the SL-LogicalChannelConfig.

[0347] Optionally, when the transmission configuration information includes at least the first mapping relationship, the processor 710 determines the transmission configuration information of the terminal-to-terminal relay transmission according to the terminal-to-terminal QoS flow information and the target message, including:

[0348] The first mapping relationship is determined according to the mapping relationship between the end-to-end QoS flow information and the end-to-end SL data bearer determined based on the end-to-end QoS flow information and the target message, and the end-to-end QoS flow information corresponding to the target channel.

[0349] Optionally, the radio frequency unit 701 is used for:

[0350] Send at least one of the following to the second terminal:

[0351] at least one set of first target information, wherein the set of first target information includes a set of configuration information of a PC5 RLC channel between the first terminal and the second terminal;

[0352] a mapping relationship between an end-to-end SL data bearer and one of the at least one set of first target information;

[0353] A second mapping relationship, wherein the second mapping relationship includes a mapping relationship between end-to-end QoS flow information and end-to-end SL data bearer;

[0354] The second terminal is a next-hop terminal of the first terminal.

[0355] Optionally, in the case where the first terminal is a source remote terminal, the transmission configuration information further includes: a second mapping relationship, the second mapping relationship including a mapping relationship between end-to-end QoS flow information and end-to-end SL data bearer;

[0356] The processor 710 determines transmission configuration information of terminal-to-terminal relay transmission according to the terminal-to-terminal QoS flow information and the target message, including:

[0357] In the target message, searching for the SL-RadioBearerConfig corresponding to the QoS parameters of the end-to-end QoS flow;

[0358] When the SL-RadioBearerConfig corresponding to the QoS parameters of the end-to-end QoS flow is found, the identification information of the end-to-end SL data bearer is determined according to the index value of the SL-RadioBearerConfig corresponding to the QoS parameters of the end-to-end QoS flow, and the second mapping relationship between the end-to-end QoS flow information and the identification information of the end-to-end SL data bearer is established.

[0359] Optionally, when the first terminal is a relay terminal, the radio frequency unit 701 is further configured to:

[0360] Receiving second target information sent by a third terminal, where the third terminal is a previous hop terminal of the relay terminal;

[0361] The second target information includes at least one of the following:

[0362] at least one set of third target information, wherein the set of third target information includes a set of configuration information of a PC5 RLC channel between the third terminal and the first terminal;

[0363] a mapping relationship between an end-to-end SL data bearer and one of the sets of third target information in the at least one set of third target information;

[0364] The second mapping relationship includes a mapping relationship between end-to-end QoS flow information and end-to-end SL data bearer.

[0365] Optionally, when the first terminal is a relay terminal, the processor 710 is further configured to:

[0366] Determine target QoS flow information mapped to the same end-to-end SL data bearer;

[0367] In a case where the target QoS flow information corresponds to multiple sets of configuration information of the target channel, the first terminal selects one set of configuration information of the multiple sets of target channels to be mapped to the target QoS flow information;

[0368] The target channel includes a PC5 RLC channel between the first terminal and a second terminal, and the second terminal is a next-hop terminal of the first terminal.

[0369] Optionally, the processor 710 determines transmission configuration information of terminal-to-terminal relay transmission according to the end-to-end quality of service QoS flow information and the target message, including:

[0370] When the first terminal is in a state where there is network coverage IC, determine the transmission configuration information of the terminal-to-terminal relay transmission according to the end-to-end quality of service QoS flow information and the system broadcast message;

[0371] When the first terminal is in a state of out-of-network coverage (OOC), transmission configuration information of terminal-to-terminal relay transmission is determined according to end-to-end quality of service QoS flow information and SL pre-configuration message.

[0372] Optionally, when the first terminal is in a state where there is network coverage IC, the processor 701 determines the transmission configuration information of the terminal-to-terminal relay transmission according to the end-to-end quality of service QoS flow information and the system broadcast message, including:

[0373] When the first terminal is in a state with network coverage IC and any of the following states is met, the processor 710 determines the transmission configuration information of the terminal-to-terminal relay transmission according to the end-to-end quality of service QoS flow information and the target message:

[0374] Radio resource control RRC idle state;

[0375] RRC inactive state;

[0376] RRC is in connected state and works in SL resource scheduling mode 2.

[0377] It can be understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the aforementioned transmission configuration determination method embodiment, and achieve the same or corresponding technical effect. To avoid repetition, it will not be repeated here.

[0378] 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, each process of the above-mentioned transmission configuration determination method embodiment is implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0379] 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.

[0380] 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 transmission configuration determination method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0381] 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.

[0382] 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 transmission configuration determination method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0383] 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.

[0384] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of a computer software product plus a necessary general hardware platform, and of course, 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 a terminal or a network-side device to execute the methods described in each embodiment of the present application.

[0385] 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 method for determining a transmission configuration, characterized in that: The method comprises: The first terminal determines transmission configuration information of terminal-to-terminal relay transmission according to the end-to-end quality of service QoS flow information and the target message; The target message includes a system broadcast message or a direct link SL pre-configuration message.

2. The method according to claim 1, characterized in that The end-to-end quality of service (QoS) flow information includes at least one of the following: End-to-end QoS flow identification QoS-FlowIdentity; QoS parameter set QoS-Profile for end-to-end QoS flow; The hop-by-hop QoS parameters corresponding to the QoS parameter set of the end-to-end QoS flow.

3. The method according to claim 1 or 2, characterized in that: The transmission configuration information includes at least one of the following: first configuration information, wherein the first configuration includes configuration information of a target channel; a first mapping relationship, wherein the first mapping relationship includes a mapping relationship between an end-to-end SL data bearer and the target channel; The target channel includes a direct communication interface PC5 radio link control RLC channel between the first terminal and the second terminal, and the second terminal is a next-hop terminal of the first terminal.

4. The method according to claim 3, characterized in that In a case where the transmission configuration information includes at least the first configuration information, the first terminal determines the transmission configuration information of the terminal-to-terminal relay transmission according to the terminal-to-terminal QoS flow information and the target message, including: The first terminal searches for direct link radio link control bearer configuration information SL-RLCBearerconfig corresponding to a first parameter in the target message, wherein the first parameter includes a QoS parameter of a hop corresponding to the first terminal and the second terminal; The first terminal determines the first configuration information according to the SL-RLC Bearer config.

5. The method according to claim 4, characterized in that The first terminal searches the target message for an SL-RLCBearerconfig corresponding to the first parameter, including: The first terminal searches the target message for a through link service quality parameter set SL-QoS-Profile corresponding to the first parameter; In a case where the first terminal finds the SL-QoS-Profile corresponding to the first parameter, the first terminal obtains direct link service data adaptation protocol configuration information SL-SDAP-Config including the SL-QoS-Profile corresponding to the first parameter; The first terminal obtains SL-RadioBearerConfig including the SL-SDAP-Config; The first terminal determines the SL-RLCBearerconfig corresponding to the SL-RadioBearerConfig as the SL-RLCBearerconfig corresponding to the first parameter.

6. The method according to claim 5, characterized in that The first terminal searches the target message for a SL-RLCBearerconfig corresponding to the first parameter, further comprising: If the first terminal fails to find the SL-QoS-Profile corresponding to the first parameter, perform any of the following: The first terminal determines default radio bearer configuration information, and searches for the SL-RLCBearerconfig according to the default radio bearer configuration information; The first terminal determines a matching parameter that is closest to at least one QoS attribute of the first parameter, and searches for the SL-RLCBearerconfig according to the matching parameter.

7. The method according to claim 6, characterized in that The first terminal determines a matching parameter that is closest to the QoS attribute of the first parameter according to at least one of the following: The priority value in the matching parameter is the same as the priority value in the first parameter; The packet delay budget PDB value in the matching parameter is the same as or closest to the PDB value in the first parameter; The packet error rate PER value in the matching parameter is the same as or closest to the packet error rate PER value in the matching parameter.

8. The method according to any one of claims 4 to 7, characterized in that: The first terminal determines the first configuration information according to the SL-RLC Bearer config, including: The first terminal searches for at least one of the direct link radio link control configuration information SL-RLC-Config and the direct link logical channel configuration information SL-LogicalChannelConfig in the SL-RLC Bearerconfig; The first terminal uses at least one of the found SL-RLC-Config and the SL-LogicalChannelConfig as information included in the first configuration information.

9. The method according to claim 8, characterized in that The first configuration information also includes identification information of the target channel; The identification information of the target channel is determined according to the value of at least one of the following items: The RLC sequence number SN in the SL-RLC-Config; RLC mode in the SL-RLC-Config; The RLC retransmission number threshold in the SL-RLC-Config; The logical channel priority in the SL-LogicalChannelConfig.

10. The method according to any one of claims 3 to 9, characterized in that: In a case where the transmission configuration information includes at least the first mapping relationship, the first terminal determines the transmission configuration information of the terminal-to-terminal relay transmission according to the terminal-to-terminal QoS flow information and the target message, including: The first terminal determines the first mapping relationship based on the mapping relationship between the end-to-end QoS flow information and the end-to-end SL data bearer determined based on the end-to-end QoS flow information and the target message, and the end-to-end QoS flow information corresponding to the target channel.

11. The method according to any one of claims 1 to 10, characterized in that: The method further comprises: The first terminal sends at least one of the following to the second terminal: at least one set of first target information, wherein the set of first target information includes a set of configuration information of a PC5 RLC channel between the first terminal and the second terminal; a mapping relationship between an end-to-end SL data bearer and one of the at least one set of first target information; A second mapping relationship, wherein the second mapping relationship includes a mapping relationship between end-to-end QoS flow information and end-to-end SL data bearer; The second terminal is a next-hop terminal of the first terminal.

12. The method according to any one of claims 1 to 11, characterized in that In the case where the first terminal is a source remote terminal, the transmission configuration information further includes: a second mapping relationship, the second mapping relationship including a mapping relationship between end-to-end QoS flow information and end-to-end SL data bearer; The first terminal determines, according to the end-to-end QoS flow information and the target message, transmission configuration information for the end-to-end relay transmission, including: The first terminal searches the target message for the SL-RadioBearerConfig corresponding to the QoS parameters of the end-to-end QoS flow; When the SL-RadioBearerConfig corresponding to the QoS parameters of the end-to-end QoS flow is found, the first terminal determines the identification information of the end-to-end SL data bearer based on the index value of the SL-RadioBearerConfig corresponding to the QoS parameters of the end-to-end QoS flow, and establishes the second mapping relationship between the end-to-end QoS flow information and the identification information of the end-to-end SL data bearer.

13. The method according to any one of claims 1 to 12, characterized in that In the case where the first terminal is a relay terminal, the method further includes: The first terminal receives second target information sent by a third terminal, where the third terminal is a previous hop terminal of the relay terminal; The second target information includes at least one of the following: at least one set of third target information, wherein the set of third target information includes a set of configuration information of a PC5 RLC channel between the third terminal and the first terminal; a mapping relationship between an end-to-end SL data bearer and one of the sets of third target information in the at least one set of third target information; The second mapping relationship includes a mapping relationship between end-to-end QoS flow information and end-to-end SL data bearer.

14. The method according to any one of claims 1 to 13, characterized in that: In the case where the first terminal is a relay terminal, the method further includes: The first terminal determines target QoS flow information mapped to the same end-to-end SL data bearer; In a case where the target QoS flow information corresponds to multiple sets of configuration information of target channels, the first terminal selects one set of configuration information of the multiple sets of target channels to be mapped to the target QoS flow information; The target channel includes a PC5 RLC channel between the first terminal and a second terminal, and the second terminal is a next-hop terminal of the first terminal.

15. The method according to any one of claims 1 to 14, characterized in that The first terminal determines transmission configuration information of terminal-to-terminal relay transmission according to the end-to-end quality of service QoS flow information and the target message, including: When the first terminal is in a state where there is network coverage IC, the first terminal determines transmission configuration information of terminal-to-terminal relay transmission according to end-to-end quality of service QoS flow information and system broadcast messages; When the first terminal is in a state of out-of-network coverage (OOC), the first terminal determines transmission configuration information of terminal-to-terminal relay transmission according to end-to-end quality of service QoS flow information and SL pre-configuration message.

16. The method according to claim 15, characterized in that When the first terminal is in a state where there is network coverage IC, the first terminal determines transmission configuration information of terminal-to-terminal relay transmission according to end-to-end quality of service QoS flow information and a system broadcast message, including: When the first terminal is in a state where there is network coverage IC and any of the following states is met, the first terminal determines the transmission configuration information of the terminal-to-terminal relay transmission according to the end-to-end quality of service QoS flow information and the target message: Radio resource control RRC idle state; RRC inactive state; RRC is in connected state and works in SL resource scheduling mode 2.

17. A transmission configuration determination device, characterized in that: Applied to a first terminal, the device includes: A configuration determination module, used to determine transmission configuration information of terminal-to-terminal relay transmission according to end-to-end quality of service QoS flow information and a target message; The target message includes a system broadcast message or a direct link SL pre-configuration message.

18. 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 when the program or instruction is executed by the processor, the steps of the transmission configuration determination method according to any one of claims 1 to 16 are implemented.

19. A readable storage medium, characterized in that: The readable storage medium stores a program or instruction, and when the program or instruction is executed by the processor, the transmission configuration determination method according to any one of claims 1 to 16 is implemented.

Images