Transmission configuration method and apparatus, communication device, and storage medium

Abstract

The present application relates to the technical field of communications, and discloses a transmission configuration method and apparatus, a communication device, and a storage medium. The transmission configuration method of embodiments of the present application comprises: a first terminal reports, to a network side device, transmission requirement information of relay transmission from a terminal to a terminal; and the first terminal receives target information sent by the network side device, wherein the target information is used for determining configuration information of relay transmission from the terminal to the terminal.

Description

Transmission configuration method, device, communication equipment and storage medium

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to the Chinese patent application filed with the China Patent Office on September 26, 2023, with application number 202311254045.7 and invention name “A transmission configuration method, device, communication equipment and storage medium”, the entire contents of which are incorporated by reference into this application. Technical Field

[0003] The present application belongs to the field of communication technology, and specifically relates to a transmission configuration method, apparatus, communication equipment and storage medium. Background Art

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

[0005] On this basis, to further expand network and sidelink coverage, improve power efficiency, and support a wider range of applications and services, User Equipment to User Equipment Relay (U2U Relay) technology has gradually emerged. That is, when the link quality between a remote UE and a directly connected peer UE deteriorates or the direct communication link quality between the two terminals does not meet the requirements, the remote UE can select an appropriate relay UE and use U2U relay technology to ensure service continuity and reachability.

[0006] Figure 1 shows an example of a UE-to-UE (U2U) relay transmission network structure, including remote UE1, remote UE2, and a relay UE. Communication information from remote UE1 to remote UE2 must first be sent to the relay UE, which then forwards it to remote UE2. Similarly, communication information from remote UE2 to remote UE1 must first be sent to the relay UE, which then forwards it to remote UE1.

[0007] In addition, transmission between terminals requires relevant configuration. However, currently, this configuration can only be implemented when terminals communicate directly through the PC5 interface, and the transmission configuration method for terminal-to-terminal relay transmission is not given.

[0008] Summary of the Invention

[0009] The embodiments of the present application provide a transmission configuration method, apparatus, communication equipment, and storage medium, and provide a transmission configuration method for terminal-to-terminal relay transmission.

[0010] In a first aspect, a transmission configuration method is provided, the method comprising:

[0011] The first terminal reports transmission requirement information of terminal-to-terminal relay transmission to the network side device;

[0012] The first terminal receives target information sent by the network-side device, wherein the target information is used to determine configuration information of the terminal-to-terminal relay transmission.

[0013] In a second aspect, a transmission configuration method is provided, the method comprising:

[0014] The network-side device receives transmission requirement information of terminal-to-terminal relay transmission reported by the first terminal;

[0015] The network-side device sends target information to the first terminal, wherein the target information is used to determine configuration information of the terminal-to-terminal relay transmission.

[0016] According to a third aspect, a transmission configuration device is provided, which is applied to a first terminal, and the device includes:

[0017] A first sending module, configured to report transmission requirement information of terminal-to-terminal relay transmission to a network-side device;

[0018] The first receiving module is configured to receive target information sent by the network-side device, wherein the target information is used to determine configuration information of the terminal-to-terminal relay transmission.

[0019] In a fourth aspect, a transmission configuration apparatus is provided, which is applied to a network-side device, and the apparatus includes:

[0020] A second receiving module is configured to receive transmission requirement information of terminal-to-terminal relay transmission reported by the first terminal;

[0021] The second sending module is configured to send target information to the first terminal, wherein the target information is used to determine configuration information of the terminal-to-terminal relay transmission.

[0022] In a fifth aspect, a communication device is provided, which includes a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the steps of the method described in the first aspect or the second aspect are implemented.

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

[0024] Reporting terminal-to-terminal relay transmission requirements to network devices;

[0025] Receive target information sent by the network-side device, wherein the target information is used to determine configuration information of the terminal-to-terminal relay transmission.

[0026] A seventh aspect provides a network-side device, including a processor and a communication interface, wherein the communication interface is configured to:

[0027] receiving transmission requirement information of terminal-to-terminal relay transmission reported by the first terminal;

[0028] Sending target information to the first terminal, wherein the target information is used to determine configuration information of the terminal-to-terminal relay transmission.

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

[0030] In the ninth aspect, a transmission configuration system is provided, comprising: a terminal and a network side device, wherein the terminal can be used to execute the steps of the method described in the first aspect, and the network side device can be used to execute the steps of the method described in the second aspect.

[0031] In the tenth aspect, a chip is provided, which includes a processor and a communication interface, the communication interface and the processor are coupled, and the processor is used to run programs or instructions to implement the method as described in the first aspect, or to implement the method as described in the second aspect.

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

[0033] In an embodiment of the present application, a first terminal can report transmission requirement information for terminal-to-terminal relay transmission to a network-side device, thereby receiving target information sent by the network-side device, and the target information is used to determine configuration information for the terminal-to-terminal relay transmission. 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 can report the transmission requirement for the terminal-to-terminal relay transmission to the network-side device, so that the network-side device can configure corresponding configuration information for the terminal-to-terminal transmission based on the transmission requirement. Therefore, an embodiment of the present application provides a transmission configuration method for terminal-to-terminal relay transmission. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] FIG1 is a schematic diagram of terminal-to-terminal relay transmission in an embodiment of the present application;

[0035] FIG2 is a block diagram of a wireless communication system to which embodiments of the present application may be applied;

[0036] FIG3 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;

[0037] FIG4 is a schematic diagram of an example of a layer 2 UE to UE relay control plane protocol stack according to an embodiment of the present application;

[0038] FIG5 is a flow chart of a transmission configuration method according to an embodiment of the present application;

[0039] FIG6 is a flowchart of another transmission configuration method in an embodiment of the present application;

[0040] FIG7 is a structural block diagram of a transmission configuration device according to an embodiment of the present application;

[0041] FIG8 is a structural block diagram of another transmission configuration device in an embodiment of the present application;

[0042] FIG9 is a structural block diagram of a communication device in an embodiment of the present application;

[0043] FIG10 is a block diagram of a terminal in an embodiment of the present application;

[0044] FIG11 is a structural block diagram of a network-side device in an embodiment of the present application. DETAILED DESCRIPTION

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

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

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

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

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

[0050] To facilitate understanding of the transmission configuration method of the embodiment of the present application, the following related technologies are now introduced:

[0051] There are two types of U2U relays: one that forwards data at Layer 2, called Layer 2 U2U relay, and the other that forwards data at Layer 3, called Layer 3 U2U relay. The following briefly describes each.

[0052] 1. Layer 2 U2U relay

[0053] The user plane protocol stack and control plane protocol stack of the Layer 2 U2U relay are shown in Figures 3 and 4, respectively. For both the user plane protocol stack and the control plane protocol stack, the remote UE adds an adaptation protocol layer between the PC5-PDCP layer and the PC5-RLC layer. The adaptation protocol layer is used to generate, receive, and forward data packets.

[0054] In Figures 3 and 4, IP represents Internet Protocol, SDAP represents Service Data Adaptation Protocol, PDCP represents Packet Data Convergence Protocol, ADAPT represents Adaptation Layer Protocol, RLC represents Radio Link Control Protocol, MAC represents Media Access Control, PHY represents Physical Layer, and RRC represents Radio Resource Control.

[0055] The following describes the process of generating and receiving the adaptation data packet.

[0056] (1) Generate an adaptation layer data packet: The remote UE as the transmitting end determines the adaptation protocol header based on the U2U relay routing configuration and adds it to the PDCP protocol data unit (PDU) from the upper layer to generate an adaptation layer data packet. The adaptation protocol header contains 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.

[0057] (2) Receiving an Adaptation Layer Data Packet: Upon receiving an Adaptation Layer Data Packet, the receiving remote UE determines whether it is the intended receiving terminal based on 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 layer data packet exactly matches its own identification information, it determines that it is the intended remote UE for the data packet. It then determines the corresponding upper-layer protocol entity based on the radio bearer identification information carried in the data packet. Finally, it removes the adaptation layer protocol header and sends the data packet to the corresponding upper-layer protocol entity.

[0058] 2. Layer 3 U2U relay

[0059] Data forwarding in Layer 3 relaying occurs above Layer 2. The relay UE's radio access layer protocol does not handle the routing of forwarded data packets. One possible implementation involves a relay UE receiving a forwarded data packet from a remote UE and submitting it to an upper layer, such as the IP layer. The IP layer then determines the destination remote UE based on the destination IP address carried in the packet's IP header and sends the data packet to that destination UE.

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

[0061] The transmission configuration method provided in the embodiment of the present application is described in detail below through some embodiments and their application scenarios in combination with the accompanying drawings.

[0062] In a first aspect, as shown in FIG5 , an embodiment of the present application provides a transmission configuration method, which may include the following steps 501 to 502:

[0063] Step 501: A first terminal reports transmission requirement information of terminal-to-terminal relay transmission to a network-side device.

[0064] The first terminal is one of the terminals in the terminal-to-terminal relay transmission, and the terminal-to-terminal relay transmission includes terminals with different roles, such as a source remote terminal (Source Remote UE), a relay terminal (Relay UE), and a target remote terminal (Target Remote UE). Here, the first terminal can be a source remote terminal or a relay terminal. It should be noted that when the first terminal is a source remote terminal and when the first terminal is a relay terminal, the specific content of the transmission requirement information for the terminal-to-terminal relay transmission reported by the first terminal may be different.

[0065] Exemplarily, when the first terminal is a source remote terminal, the transmission requirement information of the terminal-to-terminal relay transmission reported by the first terminal to the network side device (e.g., the service cell / base station of the source remote terminal) may include: the service requirement information in the transmission; when the first terminal is a relay terminal, the transmission requirement information of the terminal-to-terminal relay transmission reported by the first terminal to the network side device (e.g., the service cell / base station of the relay terminal) may include: the service requirement information in the transmission, and the information that the previous hop terminal of the relay terminal has been configured.

[0066] It should be noted that the source remote terminal is one of the two remote terminals in a communication. If a service flow is sent from the source remote terminal to the destination remote terminal, then from the perspective of the service flow, the source remote terminal is the transmitter of the service and is therefore the source side, while the destination remote terminal is the receiver of the service and is therefore the destination side. If it is another service, the source and destination remote terminals may exchange identities depending on the service flow direction. In short, the source and destination are distinguished by the flow direction of a service. Different services can have different or the same source and destination, and each service is established and maintained separately.

[0067] Step 502: The first terminal receives target information sent by the network-side device.

[0068] The target information is used to determine configuration information of the terminal-to-terminal relay transmission.

[0069] Similarly, when the first terminal is a source remote terminal and when the first terminal is a relay terminal, the configuration information of the terminal-to-terminal relay transmission determined by the above target information may be different.

[0070] Exemplarily, when the first terminal is a source remote terminal, the target information can be used to determine the configuration information of the first hop, the configuration information of the end-to-end bearer, and the mapping relationship between the configuration of the first hop and the end-to-end bearer; when the first terminal is a relay terminal, the target information can be used to determine the configuration information of the next hop of the relay terminal, and the mapping relationship between the configuration of the next hop of the relay terminal (i.e., PC5 RL Channel) and the end-to-end bearer.

[0071] It is understandable that when the first terminal is a source remote terminal, and when the first terminal is a relay terminal, the above-mentioned transmission requirement information and target information may also include other content, which will be described in detail later.

[0072] As can be seen from the above steps 501 to 502, in an embodiment of the present application, the first terminal can report the transmission requirement information of the terminal-to-terminal relay transmission to the network-side device, thereby receiving the target information sent by the network-side device, and the target information is used to determine the configuration information of the terminal-to-terminal relay transmission. 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 can report the transmission requirement of the terminal-to-terminal relay transmission to the network-side device, so that the network-side device can configure the corresponding configuration information for the terminal-to-terminal transmission based on the transmission requirement. Therefore, an embodiment of the present application provides a transmission configuration method during terminal-to-terminal relay transmission.

[0073] The following describes the first terminal from different perspectives of serving as a relay terminal and a source remote terminal.

[0074] 1.1 When the first terminal acts as a relay terminal, the first terminal interacts with the network-side device to implement terminal-to-terminal relay transmission configuration, which can be specifically configured in Mode 1 or Mode 2 as described below:

[0075] Method 1: The network-side device is configured according to the information reported by the first terminal.

[0076] Optionally, when the first terminal is a relay terminal (Relay UE), the transmission requirement information includes at least one of the following items A-1 to A-7:

[0077] Item A-1: ​​End-to-end bearer configuration information. It should be noted that the end-to-end bearer in this text may be an end-to-end SL data bearer. The end-to-end bearer configuration information may include at least one of a bearer (Radio Bearer (RB)) ID, RB configuration parameters, Quality of Service flow (QoS flow) information contained in the RB, and a corresponding QoS parameter set (profile). Alternatively, the end-to-end bearer configuration information may include Service Data Adaptation Protocol (SDAP) and Packet Data Convergence Protocol (PDCP) configuration, wherein the SDAP configuration indicates the E2E QoS flow ID and QoS parameter set information contained in the SL RB.

[0078] Item A-2: Service demand information for transmission between the relay terminal and the second terminal, where the second terminal is the next-hop terminal of the relay terminal; here, the second terminal may be a target remote terminal or a relay terminal of the next hop of the relay terminal; for example, in a single-hop U2U architecture, the first terminal is a Relay UE, and the second terminal is a Target Remote UE; in a multi-hop U2U architecture, the first terminal is one of the Relay UEs, and the second terminal may be the next Relay UE or the Target Remote UE of the Relay UE; wherein, the service demand information may include at least one of QoS flow information and a corresponding QoS profile; wherein, the service demand information may be the portion after being split by the Relay UE, for example, in a U2U Relay link, the E2E packet delay budget (PDB) may be 100ms, which is split into 50ms for the first-hop PDB and 50ms for the second-hop PDB;

[0079] Item A-3: Identification information of the source remote terminal; here, the identification information of the Source Remote UE may be, for example, the PC5 layer 2 (Layer-2) ID of the Source Remote UE or its local UE ID information;

[0080] Item A-4: identification information of the target remote terminal; here, the identification information of the Target Remote UE may be, for example, the PC5 layer 2 (Layer-2) ID of the Target Remote UE or its local UE ID information;

[0081] Item A-5: identification information of the second terminal; here, the identification information of the second terminal may be, for example, a PC5 layer 2 (Layer-2) ID of the second terminal or its local UE ID information;

[0082] Item A-6: configuration information of a first channel, where the first channel includes a radio link control (RLC) channel of a communication interface PC5 between a previous hop terminal of the relay terminal and the relay terminal;

[0083] Item A-7: A first mapping relationship, wherein the first mapping relationship includes a mapping relationship between an end-to-end bearer and the first channel.

[0084] The contents of items A-6 and A-7 may be sent from the previous hop terminal of the first terminal to the first terminal. For example, when the first terminal is a relay terminal, the contents may be sent from the Source Remote UE to the relay terminal, or from the previous hop relay terminal of the relay terminal to the relay terminal.

[0085] From this, it can be seen that the relay terminal can report at least one item of information from A-1 to A-7 to the network side device (for example, the service cell / base station of the relay terminal), so that the network side device configures the next hop of the relay terminal for the relay terminal based on at least one item of information from A-1 to A-7, that is, the reporting of at least one item of information from A-1 to A-7 provides a data basis for the network side device to configure the relevant configuration of the next hop of the relay terminal.

[0086] Optionally, when the first terminal is a relay terminal (Relay UE), the target information includes at least one item of the following B-1 to B-5:

[0087] Item B-1: configuration information of a second channel, the second channel including a PC5 RLC channel between the relay terminal and a second terminal, the second terminal being a next-hop terminal of the relay terminal; the configuration information of the second channel may include configuration information of at least one of an RLC layer, a media access control (MAC), and a physical layer (PHY);

[0088] Item B-2: identification information of the second terminal; here, the identification information of the second terminal may be, for example, the PC5 layer 2 (Layer-2) ID of the second terminal or its local UE ID information;

[0089] Item B-3: Identification information of the target remote terminal corresponding to the second channel; wherein, because the Relay UE may communicate with multiple Target Remote UEs due to the needs of multiple Source Remote UEs, the PC5 RLC channel needs to indicate the corresponding Target Remote UE ID information;

[0090] Item B-4: A second mapping relationship, wherein the second mapping relationship includes a mapping relationship between an end-to-end bearer and the second channel; the mapping relationship between the end-to-end bearer and the second channel is generally N to 1, that is, a many-to-one relationship; wherein, a configuration method for the mapping relationship may be, for example: including a corresponding PC5 RLC channel ID or index information in each end-to-end bearer (wherein it is necessary to indicate which Target Remote UE's PC5 RLC channel it is, and therefore it is necessary to additionally carry the Target Remote UE ID), or including a corresponding end-to-end bearer ID or index list information in each PC5 RLC channel (wherein it is necessary to indicate which Source Remote UE and Target Remote UE it is an end-to-end bearer between, and therefore it is necessary to additionally carry the Target Remote UE ID and the Source Remote UE ID);

[0091] Item B-5: Logical channel group identification information corresponding to the second channel. This facilitates the Relay UE to subsequently perform the PC5 BSR reporting process based on the cache size of the logical channel group (Logic Channel Group Identity, LCG ID) corresponding to different PC5 RLC channels, thereby facilitating the allocation of appropriate transmission resources. Optionally, when the Relay UE is configured in resource scheduling mode 1, the network-side device (e.g., the serving cell / base station of the Relay UE) can allocate LCG IDs for different PC5 RLC channels between the Relay UE and the second terminal.

[0092] From the above, it can be seen that the network side device sends at least one of the above B-1 to B-5 to the relay terminal, realizing the relevant configuration of the next hop of the relay device, thereby facilitating the establishment of the transmission channel of the next hop of the relay terminal.

[0093] Method 2: The network device confirms or rejects the configuration information of the first terminal

[0094] Optionally, when the first terminal is a relay terminal (Relay UE), the transmission requirement information includes at least one of the following items C-1 to C-9:

[0095] Item C-1: End-to-end bearer configuration information; the end-to-end bearer configuration information may include at least one of an RB ID, RB configuration parameters, Quality of Service flow (QoS flow) information contained in the RB, and a corresponding QoS parameter set (profile); alternatively, the end-to-end bearer configuration information may include SDAP and PDCP configuration, wherein the SDAP configuration indicates the E2E QoS flow ID and QoS parameter set information contained in the SL RB;

[0096] Item C-2: Service requirement information for transmission between the relay terminal and a second terminal, where the second terminal is the next-hop terminal of the relay terminal. Here, the second terminal may be a target remote terminal or a next-hop relay terminal of the relay terminal. The service requirement information may include at least one of QoS flow information and a corresponding QoS profile. The service requirement information may be the portion after being segmented by the Relay UE. For example, in a U2U Relay link, the E2E packet delay budget (PDB) may be 100 ms, which is segmented to 50 ms for the first-hop PDB and 50 ms for the second-hop PDB.

[0097] Item C-3: identification information of the second terminal; here, the identification information of the second terminal may be, for example, the PC5 layer 2 (Layer-2) ID of the second terminal or its local UE ID information;

[0098] Item C-4: Identification information of the source remote terminal; here, the identification information of the Source Remote UE may be, for example, the Layer 2 ID of the Source Remote UE or its local UE ID information;

[0099] Item C-5: identification information of the target remote terminal; here, the identification information of the Target Remote UE may be, for example, the PC5 layer 2 (Layer-2) ID of the Target Remote UE or its local UE ID information;

[0100] Item C-6: configuration information of a second channel, where the second channel includes a PC5 RLC channel between the relay terminal and the second terminal; the configuration information of the second channel may include configuration information of at least one of the RLC, MAC, and PHY layers;

[0101] Item C-7: Quality of Service (QoS) information; the QoS information may include at least one of QoS flow information and corresponding QoS profile information;

[0102] Item C-8: Target configuration information, the target configuration information includes the association between any two of the second channel, the end-to-end bearer, and the QoS information; for example, in the SL U2U relay architecture, the Relay UE can report to its serving cell / base station: the PC5 RLC channel configuration information between the Relay UE and the Target Remote UE, the E2E SL RB information mapped to the PC5 RLC channel, and the QoS flow and / or QoS profile information mapped to the E2E SL RB.

[0103] Item C-9: Configuration suggestion information, the configuration suggestion information including identification information of the logical channel group allocated by the first terminal to the second channel; optionally, when the Relay UE is configured in resource scheduling mode 1, the Relay UE may allocate LCG IDs for different PC5 RLC channels between the Relay UE and the second terminal. That is, if the Relay UE wishes to be configured in resource scheduling mode 1, it may negotiate with the serving cell / base station for the configuration of the LCG ID, that is, the Relay UE may carry its own LCG ID allocation suggestion and wait for network confirmation; it is understandable that the Relay UE may also wait for the network to directly configure the LCG ID for the PC5 RLC channel between the Relay UE and the second terminal.

[0104] It can be seen from this that the relay terminal can report at least one of the above information C-1 to C-9 to the network side device (such as the service cell / base station of the relay terminal), so that the network side device can confirm or reject the next hop configuration of the relay terminal based on at least one of the information C-1 to C-7. That is, here, the relay terminal can report the configuration information of the next hop of the relay terminal to the network side device, and then wait for the network side device to confirm. In addition, the relay terminal and the network side device can also negotiate about the configuration of mode 1, such as LCG ID. It can be seen that the reporting of at least one of the above information C-1 to C-7 provides a data basis for the network side device to confirm the relevant configuration of the next hop of the relay terminal.

[0105] Optionally, the target information includes at least one of a confirmation message, a rejection message, and a logical channel group corresponding to the second channel configured by the network side device;

[0106] The following describes the different situations of confirming and rejecting messages:

[0107] Confirmation messages can be divided into the following two cases:

[0108] In case 1, the confirmation message includes at least one of the following items D-1 to D-7:

[0109] Item D-1: configuration information of at least part of the second channel confirmed by the network-side device;

[0110] Item D-2: at least part of the end-to-end bearer confirmed by the network-side device;

[0111] Item D-3: at least part of the QoS flow information confirmed by the network side device;

[0112] Item D-4: an index of at least part of the configuration information of the second channel confirmed by the network-side device;

[0113] Item D-5: index of at least part of the end-to-end bearer confirmed by the network-side device;

[0114] Item D-6: an index of at least part of the QoS flow information confirmed by the network-side device;

[0115] Item D-7: Identification information of the logical channel group corresponding to at least part of the second channel confirmed by the network side device.

[0116] Therefore, it can be seen that the network-side device can confirm or accept at least one of the configuration information, end-to-end bearer, and QoS flow information of the second channel reported by the relay terminal to the network-side device. The acceptance status of different channels can be listed separately, such as the confirmation or acceptance status of the RLC channel granularity, the confirmation or acceptance status of the E2E SL RB granularity, the confirmation or acceptance status of the QoS flow granularity, etc. In addition, for the LCG ID allocated by the relay terminal for the second channel, the network-side device can also confirm at least part of the LCG ID.

[0117] Case 2: The confirmation message includes an indication for confirming all the configuration information in the transmission requirement information reported by the first terminal; here, all the configuration information in the transmission requirement information reported by the first terminal may include at least one of the configuration information of the second channel in the above-mentioned item C-6, the target configuration information in the item C-8, and the configuration recommendation information in the item C-9. For example, all the configuration information in the transmission requirement information reported by the first terminal includes items C-6, C-8, and C-9, then the confirmation message can be used to indicate the confirmation of all these configuration information. Exemplarily, there may be a bit in the confirmation message, and when the value of the bit is 1, it indicates confirmation of all the configuration information in the transmission requirement information reported by the first terminal. Or the name of the confirmation message is Confirm Message, and receipt of the Confirm Message indicates confirmation of all the configuration information in the transmission requirement information reported by the first terminal.

[0118] It can be seen from this that the network-side device can directly confirm all the configuration information in the transmission requirement information reported by the first terminal through a confirmation message.

[0119] Rejection messages can be divided into the following three and four cases:

[0120] Case 3: The rejection information includes at least one of the following items E-1 to E-7:

[0121] Item E-1: configuration information of at least part of the second channel rejected by the network-side device;

[0122] Item E-2: at least some end-to-end bearers rejected by the network-side device;

[0123] Item E-3: information about at least some QoS flows rejected by the network-side device;

[0124] Item E-4: index of at least part of the configuration information of the second channel rejected by the network-side device;

[0125] Item E-5: index of RBs of at least some end-to-end bearers rejected by the network-side device;

[0126] Item E-6: index of at least part of the QoS flow information rejected by the network side device;

[0127] Item E-7: Identification information of the logical channel group corresponding to at least part of the second channel rejected by the network side device.

[0128] Therefore, it can be seen that the network-side device can reject at least one of the configuration information, end-to-end bearer, and QoS flow information of the second channel reported by the relay terminal to the network-side device. The rejection situations of different channels can be listed separately, such as rejection at the RLC channel granularity, rejection at the E2E SL RB granularity, rejection at the QoS flow granularity, etc. In addition, for the LCG IDs allocated by the relay terminal for the second channel, the network-side device can also reject at least some of the LCG IDs.

[0129] Case four, the rejection message includes an indication for indicating the rejection of all configuration information in the transmission requirement information reported by the first terminal; similarly, all configuration information in the transmission requirement information reported by the first terminal may include at least one of the configuration information of the second channel in the above-mentioned item C-6, the target configuration information in the item C-8, and the configuration recommendation information in the item C-9. For example, all configuration information in the transmission requirement information reported by the first terminal includes items C-6, C-8, and C-9, then the rejection message can be used to indicate the rejection of all these configuration information. Exemplarily, there may be a bit in the rejection message, and when the value of the bit is 0, it indicates the rejection of all configuration information in the transmission requirement information reported by the first terminal. Or the name of the rejection message is Reject Message, and receipt of the Reject Message indicates the rejection of all configuration information in the transmission requirement information reported by the first terminal.

[0130] It can be seen from this that the network-side device can directly reject all configuration information in the transmission requirement information reported by the first terminal through a confirmation message.

[0131] It can be seen that in the embodiment of the present application, for the configuration information reported by the relay device to the network side device, the network side device can confirm or reject it in the form of multiple granularities, so that the configuration information of the terminal-to-terminal relay transmission can be configured more flexibly.

[0132] In addition, from the above, it can be seen that the network side device can directly configure the logical channel group corresponding to the second channel, or the relay terminal can report the logical channel group corresponding to the second channel configured by it to the network side device, so that the network side device can confirm or reject at least part of the logical channel group of the second channel.

[0133] It should also be noted that the network side device can send the confirmation message in the above situation 1 to the relay terminal to inform the relay terminal of the content confirmed by the network side device;

[0134] Alternatively, the network side device may also send a confirmation message in the above-mentioned second situation to the relay terminal to inform the relay terminal that the network side device confirms all the configuration information reported by it;

[0135] Alternatively, the network side device may also send a rejection message in the above-mentioned case 3 to the relay terminal, informing the relay terminal of the content rejected by the network side device, so that the relay terminal can use the content other than the rejected content in the configuration information reported by it;

[0136] Alternatively, the network side device may also send a rejection message in the above fourth situation to the relay terminal to inform the relay terminal that the network side device rejects all configuration information reported by the relay terminal;

[0137] Alternatively, the network side device may send a confirmation message in the above case 1 to the relay terminal to inform the relay terminal of the content of the network side device's confirmation, and a rejection message in the above case 3 to inform the relay terminal of the content of the network side device's rejection.

[0138] Optionally, the method further includes:

[0139] The first terminal sends at least one of the following to the second terminal:

[0140] End-to-end bearer configuration information;

[0141] configuration information of the second channel;

[0142] A second mapping relationship, where the second mapping relationship includes a mapping relationship between an end-to-end bearer and the second channel.

[0143] It can be seen from this that the first terminal can also send at least one of the configuration information of the end-to-end bearer, the configuration information of the second channel, and the second association relationship to the second terminal, thereby establishing a transmission channel between the first terminal and the second terminal.

[0144] It should be noted that, based on the above-mentioned method 1 or method 2, the first terminal can send at least one of the configuration information of the end-to-end bearer, the configuration information of the second channel, and the second association relationship to the second terminal.

[0145] 1.2 When the first terminal serves as a source remote terminal, the first terminal interacts with the network-side device to implement transmission configuration for terminal-to-terminal relay transmission. Optionally, when the first terminal is a source remote terminal, the transmission requirement information includes at least one of the following items F-1 to F-4:

[0146] Item F-1: End-to-end service demand information. Here, the end-to-end service demand information may include E2E QoS flow ID information, corresponding QoS parameter set (profile) and rate information;

[0147] Item F-2: Service requirement information for transmission between a source remote terminal and a third terminal, where the third terminal is the next-hop terminal of the source remote terminal; that is, the third terminal is the first relay UE after the source remote terminal. This requirement information may include at least one of split QoS flow ID information, a corresponding QoS profile, and rate information. The service requirement for transmission on the first hop is the service requirement after being split from the E2E service requirement. For example, if the PDB for the E2E link is 100ms, the first-hop split may be 50ms.

[0148] Item F-3: identification information of the target remote terminal corresponding to the end-to-end service; here, the identification information of the target remote terminal may be, for example, the PC5 layer 2 (Layer-2) ID of the Target Remote UE, or other ID information (used to identify and distinguish the Target Remote UE);

[0149] Item F-4: identification information of the third terminal; here, the identification information of the second terminal may be, for example, the PC5 layer 2 (Layer-2) ID of the second terminal, or its local UE ID information.

[0150] Therefore, it can be seen that the source remote terminal can report at least one of the above information F-1 to F-4 to the network-side device (e.g., the serving cell / base station of the source remote terminal), so that the network-side device configures at least one of the relevant configurations of the first hop and the relevant configurations of the end-to-end bearer based on the at least one of the information F-1 to F-4. That is, the reporting of at least one of the above information F-1 to F-4 provides a data basis for the network-side device to configure at least one of the relevant configuration information of the first hop and the relevant configuration of the end-to-end bearer.

[0151] Optionally, when the first terminal is a source remote terminal, the target information includes at least one of the following items J-1 to J-6:

[0152] Item J-1: End-to-end bearer configuration information; the end-to-end bearer configuration information may include at least one of an RB ID, RB configuration parameters, QoS flow information contained in the RB, and a corresponding QoS profile; or, alternatively, the end-to-end bearer configuration information may include SDAP and PDCP configuration, wherein the SDAP configuration may indicate the E2E QoS flow ID information contained in the SL RB;

[0153] Item J-2: configuration information of a third channel, the third channel comprising a PC5 RLC channel between the source remote terminal and a third terminal, the third terminal being a next-hop terminal of the source remote terminal; the configuration information of the third channel may include configuration information of at least one of the RLC, MAC, and PHY layers;

[0154] Item J-3: Identification information of the target remote terminal corresponding to the third channel; because the Source Remote UE may communicate with multiple Target Remote UEs, the E2E SL RB needs to indicate the corresponding Target Remote UE ID information;

[0155] Item J-4: Identification information of the third terminal. Because the Source Remote UE may communicate with multiple Target Remote UEs through multiple Relay UEs, the PC5 RLC channel (i.e., the third channel) needs to indicate the identification information of the corresponding third terminal. Here, the identification information of the third terminal may be, for example, the PC5 Layer 2 ID of the third terminal or its local UE ID information.

[0156] Item J-5: A third mapping relationship, the third mapping relationship including a mapping relationship between an end-to-end bearer and the third channel; here, the mapping relationship is generally an N-to-1, i.e., a many-to-one relationship; wherein, a configuration method for the mapping relationship may be, for example: including a corresponding PC5 RLC channel ID or index information in each end-to-end bearer (where it is necessary to indicate which Relay UE's PC5 RLC channel it is, and therefore, the Relay UE ID needs to be additionally carried); or, including a corresponding end-to-end bearer ID or index list (index list information) in each PC5 RLC channel (where it is necessary to indicate which Target UE's E2E SL RB it is, and therefore, the Target Remote UE ID needs to be additionally carried);

[0157] Item J-6: Logical channel group identification information corresponding to the third channel; optionally, when the Source Remote UE is configured as resource scheduling mode mode 1 (i.e., the mode in which the network schedules PC5 resources), the network side device (such as the service cell / base station of the Source Remote UE) can be the ID corresponding to different PC5RLC channels between the Source Remote UE and the Relay UE, which can facilitate the Source Remote UE to subsequently perform a PC5 buffer state report (BSR) reporting process based on the cache size of the LCG ID, thereby facilitating the allocation of appropriate transmission resources.

[0158] As can be seen from the above, the network side device sends at least one of the above J-1 to J-6 to the source remote terminal, thereby implementing relevant configurations for the first hop, thereby facilitating the establishment of the transmission channel for the first hop.

[0159] Optionally, the method further comprises at least one of the following H-1 to H-3:

[0160] The first terminal sends configuration information of the end-to-end bearer to a target remote terminal;

[0161] The first terminal sends at least one of the following to the third terminal;

[0162] Item H-1: End-to-end bearer configuration information;

[0163] Item H-2: configuration information of the third channel;

[0164] Item H-3: the third mapping relationship.

[0165] From this, it can be seen that the first terminal can also send the configuration information of the end-to-end bearer to the target remote terminal, thereby establishing an end-to-end SL RB transmission pipeline; the first terminal can also send at least one of the above H-1 to H-3 to the next-hop terminal when the first terminal is the source remote terminal, thereby establishing the first-hop RLC channel transmission pipeline, so that the first-hop transmission from the source remote terminal to the target remote terminal can be opened.

[0166] Optionally, the first terminal reports transmission requirement information of terminal-to-terminal relay transmission to the network side device, including:

[0167] The first terminal reports the transmission requirement information to the network-side device using at least one of a target data format and a target message, wherein the target data format is different from an existing data format (i.e., the target data format is a new data format), and the target message is different from an existing message (i.e., the target message is a new message);

[0168] or,

[0169] The first terminal reports the transmission requirement information and target indication information to the network-side device, wherein the target indication information is used to indicate that the transmission requirement information is associated with terminal-to-terminal relay transmission.

[0170] It can be seen from this that the above-mentioned transmission requirement information reported by the first terminal to the network-side device can be reported in a new data format and a new message (such as a new RRC message); it can also be reported by reusing an existing message (such as sidelink terminal information (SidelinkUEInformation)), but it needs to be clearly distinguished by the above-mentioned target indication information. This is the reporting of the U2U Relay link. For example, the above-mentioned transmission requirement information can adopt a new message, but use an existing data format; or, it can also adopt an existing message, but use a new data format; or, it can also use a new data format and a new message. That is, the above-mentioned transmission requirement information can adopt different reporting domains or reuse the original QoS information domain but carry a special U2U Relay link indication, etc. In short, the network side needs to be made aware that this is different from the requirements of direct communication between two UEs.

[0171] It can be seen that in the embodiment of the present application, the above-mentioned transmission requirement information reported by the first terminal to the network side device can be explicitly or implicitly indicated to be associated with the terminal-to-terminal relay transmission, and the indication form of the content is more flexible.

[0172] Optionally, the first terminal reports transmission requirement information of terminal-to-terminal relay transmission to the network side device, including:

[0173] When the first terminal is in a connected state, the first terminal reports the transmission requirement information to the network side device.

[0174] It can be seen from this that in an embodiment of the present application, the first terminal can report the transmission requirement information to the network side device when it is in a connected state, thereby receiving the above-mentioned target information sent by the network side device to determine the configuration information of the terminal-to-terminal relay transmission, so as to realize the transmission configuration of the terminal-to-terminal relay transmission when the first terminal is in a connected state.

[0175] In a second aspect, as shown in FIG6 , an embodiment of the present application provides a transmission configuration method, which may include the following steps 601 to 602:

[0176] Step 601: A network-side device receives transmission requirement information of terminal-to-terminal relay transmission reported by a first terminal.

[0177] Here, the network side device may be a serving cell or a base station of the first terminal.

[0178] The first terminal is one of the terminals in the terminal-to-terminal relay transmission. The terminal-to-terminal relay transmission includes terminals with different roles, such as a source remote terminal (Source Remote UE), a relay terminal (Relay UE), and a target remote terminal (Target Remote UE). Here, the first terminal can be a source remote terminal or a relay terminal. It should be noted that when the first terminal is a source remote terminal and when the first terminal is a relay terminal, the specific content of the transmission requirement information for the terminal-to-terminal relay transmission reported by the first terminal may be different.

[0179] Exemplarily, when the first terminal is a source remote terminal, the transmission requirement information of the terminal-to-terminal relay transmission reported by the first terminal to the network side device (e.g., the service cell / base station of the source remote terminal) may include: the service requirement information in the transmission; when the first terminal is a relay terminal, the transmission requirement information of the terminal-to-terminal relay transmission reported by the first terminal to the network side device (e.g., the service cell / base station of the relay terminal) may include: the service requirement information in the transmission, and the information that the previous hop terminal of the relay terminal has been configured.

[0180] Step 602: The network-side device sends target information to the first terminal.

[0181] The target information is used to determine configuration information of the terminal-to-terminal relay transmission.

[0182] The target information is used to determine configuration information of the terminal-to-terminal relay transmission.

[0183] Similarly, when the first terminal is a source remote terminal and when the first terminal is a relay terminal, the configuration information of the terminal-to-terminal relay transmission determined by the above target information may be different.

[0184] Exemplarily, when the first terminal is a source remote terminal, the target information can be used to determine the configuration information of the first hop, the configuration information of the end-to-end bearer, and the mapping relationship between the configuration of the first hop and the end-to-end bearer; when the first terminal is a relay terminal, the target information can be used to determine the configuration information of the next hop of the relay terminal, and the mapping relationship between the configuration of the next hop of the relay terminal (i.e., PC5 RL Channel) and the end-to-end bearer.

[0185] It is understandable that when the first terminal is a source remote terminal, and when the first terminal is a relay terminal, the above-mentioned transmission requirement information and target information may also include other content, which will be described in detail later.

[0186] As can be seen from the above steps 501 to 502, in an embodiment of the present application, the first terminal can report the transmission requirement information of the terminal-to-terminal relay transmission to the network-side device, thereby receiving the target information sent by the network-side device, and the target information is used to determine the configuration information of the terminal-to-terminal relay transmission. 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 can report the transmission requirement of the terminal-to-terminal relay transmission to the network-side device, so that the network-side device can configure the corresponding configuration information for the terminal-to-terminal transmission based on the transmission requirement. Therefore, an embodiment of the present application provides a transmission configuration method during terminal-to-terminal relay transmission.

[0187] Optionally, when the first terminal is a relay terminal, the transmission requirement information includes at least one of the following items A-1 to A-7:

[0188] Item A-1: ​​End-to-end bearer configuration information;

[0189] Item A-2: demand information for services transmitted between the relay terminal and a second terminal, where the second terminal is a next-hop terminal of the relay terminal;

[0190] Item A-3: identification information of the source remote terminal;

[0191] Item A-4: identification information of the target remote terminal;

[0192] Item A-5: identification information of the second terminal;

[0193] Item A-6: configuration information of a first channel, where the first channel includes a radio link control (RLC) channel of a communication interface PC5 between a previous hop terminal of the relay terminal and the relay terminal;

[0194] Item A-7: A first mapping relationship, wherein the first mapping relationship includes a mapping relationship between an end-to-end bearer and the first channel.

[0195] Here, the relevant explanations of items A-1 to A-7 can be found in the previous text and will not be repeated here.

[0196] Optionally, when the first terminal is a relay terminal, the target information includes at least one of the following items B-1 to B-5:

[0197] Item B-1: configuration information of a second channel, where the second channel includes a PC5 RLC channel between the relay terminal and a second terminal, where the second terminal is a next-hop terminal of the relay terminal;

[0198] Item B-2: identification information of the second terminal;

[0199] Item B-3: identification information of the target remote terminal corresponding to the second channel;

[0200] Item B-4: a second mapping relationship, the second mapping relationship including a mapping relationship between an end-to-end bearer and the second channel;

[0201] Item B-5: Logical channel group identification information corresponding to the second channel.

[0202] Here, the relevant explanations of items B-1 to B-5 can be found in the previous text and will not be repeated here.

[0203] Optionally, when the first terminal is a relay terminal, the transmission requirement information includes at least one of the following items C-1 to C-9:

[0204] Item C-1: End-to-end bearer configuration information;

[0205] Item C-2: demand information for services transmitted between the relay terminal and a second terminal, where the second terminal is a next-hop terminal of the relay terminal;

[0206] Item C-3: identification information of the second terminal;

[0207] Item C-4: identification information of the source remote terminal;

[0208] Item C-5: identification information of the target remote terminal;

[0209] Item C-6: configuration information of a second channel, where the second channel includes a PC5 RLC channel between the relay terminal and the second terminal;

[0210] Item C-7: Quality of service (Qos) information;

[0211] Item C-8: target configuration information, the target configuration information including an association between any two of the second channel, the end-to-end bearer, and the QoS information;

[0212] Item C-9: Configuration recommendation information, the configuration recommendation information including identification information of the logical channel group allocated by the first terminal to the second channel.

[0213] Here, the relevant explanations of items C-1 to C-9 can be found in the previous article and will not be repeated here.

[0214] Optionally, the target information includes at least one of a confirmation message, a rejection message, and a logical channel group corresponding to the second channel configured by the network side device;

[0215] The following describes the different situations of confirming and rejecting messages:

[0216] Confirmation messages can be divided into the following two cases:

[0217] In case 1, the confirmation message includes at least one of the following items D-1 to D-7:

[0218] Item D-1: configuration information of at least part of the second channel confirmed by the network-side device;

[0219] Item D-2: at least part of the end-to-end bearer confirmed by the network-side device;

[0220] Item D-3: at least part of the QoS flow information confirmed by the network side device;

[0221] Item D-4: an index of at least part of the configuration information of the second channel confirmed by the network-side device;

[0222] Item D-5: index of at least part of the end-to-end bearer confirmed by the network-side device;

[0223] Item D-6: an index of at least part of the QoS flow information confirmed by the network-side device;

[0224] Item D-7: identification information of the logical channel group corresponding to at least part of the second channel confirmed by the network-side device;

[0225] Here, the relevant explanations of items D-1 to D-7 can be found in the previous article and will not be repeated here.

[0226] In case 2, the confirmation message includes an indication for confirming all configuration information in the transmission requirement information reported by the first terminal; from this, it can be seen that the network side device can directly confirm all configuration information in the transmission requirement information reported by the first terminal through the confirmation message.

[0227] Rejection messages can be divided into the following three and four cases:

[0228] Case 3: The rejection information includes at least one of the following items E-1 to E-7:

[0229] Item E-1: configuration information of at least part of the second channel rejected by the network-side device;

[0230] Item E-2: at least some end-to-end bearers rejected by the network-side device;

[0231] Item E-3: information about at least some QoS flows rejected by the network-side device;

[0232] Item E-4: index of at least part of the configuration information of the second channel rejected by the network-side device;

[0233] Item E-5: index of RBs of at least some end-to-end bearers rejected by the network-side device;

[0234] Item E-6: index of at least part of the QoS flow information rejected by the network side device;

[0235] Item E-7: Identification information of the logical channel group corresponding to at least part of the second channel rejected by the network side device.

[0236] Here, the relevant explanations of items E-1 to E-7 can be found in the previous article and will not be repeated here.

[0237] In case 4, the rejection message includes an instruction for rejecting all configuration information in the transmission requirement information reported by the first terminal. Therefore, the network side device can directly reject all configuration information in the transmission requirement information reported by the first terminal through a confirmation message.

[0238] Optionally, when the first terminal is a source remote terminal, the transmission requirement information includes at least one of the following items F-1 to F-4:

[0239] Item F-1: End-to-end business demand information;

[0240] Item F-2: demand information for services transmitted between a source remote terminal and a third terminal, where the third terminal is a next-hop terminal of the source remote terminal;

[0241] Item F-3: identification information of the target remote terminal corresponding to the end-to-end service;

[0242] Item F-4: identification information of the third terminal.

[0243] Here, the relevant explanations of items F-1 to F-4 can be found in the previous article and will not be repeated here.

[0244] Optionally, when the first terminal is a source remote terminal, the target information includes at least one of the following items J-1 to J-6:

[0245] Item J-1: End-to-end bearer configuration information;

[0246] Item J-2: configuration information of a third channel, where the third channel includes a PC5 RLC channel between the source remote terminal and a third terminal, where the third terminal is a next-hop terminal of the source remote terminal;

[0247] Item J-3: identification information of the target remote terminal corresponding to the third channel;

[0248] Item J-4: identification information of the third terminal;

[0249] Item J-5: a third mapping relationship, the third mapping relationship including a mapping relationship between an end-to-end bearer and the third channel;

[0250] Item J-6: Logical channel group identification information corresponding to the third channel.

[0251] Here, the relevant explanations of items J-1 to J-6 can be found in the previous article and will not be repeated here.

[0252] Optionally, the network-side device receives transmission requirement information of terminal-to-terminal relay transmission reported by the first terminal, including:

[0253] The network-side device receives the transmission requirement information sent by the first terminal using at least one of a target data format and a target message, wherein the target data format is different from an existing data format, and the target message is different from an existing message;

[0254] or,

[0255] The network-side device receives the transmission requirement information and target indication information sent by the terminal, wherein the target indication information is used to indicate that the transmission requirement information is associated with terminal-to-terminal relay transmission.

[0256] It can be seen from this that the above-mentioned transmission requirement information reported by the first terminal to the network-side device can be reported in a new data format and a new message (such as a new RRC message); it can also be reported by reusing an existing message (such as sidelink terminal information (SidelinkUEInformation)), but it needs to be clearly distinguished by the above-mentioned target indication information. This is the reporting of the U2U Relay link. For example, the above-mentioned transmission requirement information can adopt a new message, but use an existing data format; or, it can also adopt an existing message, but use a new data format; or, it can also use a new data format and a new message. That is, the above-mentioned transmission requirement information can adopt different reporting domains or reuse the original QoS information domain but carry a special U2U Relay link indication, etc. In short, the network side needs to be made aware that this is different from the requirements of direct communication between two UEs.

[0257] In summary, taking a single-hop U2U architecture as an example, the specific implementation methods of the transmission configuration method of an embodiment of the present application are introduced, as described in the following implementation methods one to three.

[0258] Implementation Method 1

[0259] In this embodiment, the source remote UE is in the Radio Resource Control (RRC) connected state. It needs to report its terminal-to-terminal relay (U2U Relay) service requirements to the network side, and then obtain relevant configuration from the network side to complete the end-to-end (E2E) and first-hop configuration process before it can transmit data through the U2U Relay link.

[0260] It should be noted that although the reporting process of the Source Remote UE can also reuse the reporting process of the existing PC5 link (i.e., direct PC5 communication between two UEs), some clear distinctions must be made. The network side needs to be aware that this is a U2U Relay link, which is communication between two UEs, rather than traditional single-hop communication between UEs. This allows for a better understanding of the service's Quality of Service (QoS) requirements and provides configuration suitable for the U2U relay link.

[0261] Specifically, the information reported by the Source Remote UE to its serving cell / base station includes at least one of the following:

[0262] E2E service requirements of the U2U Relay link, including E2E QoS flow ID information, corresponding QoS parameter set (profile) and rate information;

[0263] The service requirements of the first-hop transmission of the U2U Relay link between the Source Remote UE and the Relay UE include at least one of the split QoS flow ID information, the corresponding QoS profile, and the rate information. The service requirements of the first-hop transmission are the requirements after being split from the E2E service requirements. For example, if the packet delay budget (PDB) for the E2E link is 100ms, it may be 50ms after the first-hop split.

[0264] ID information of the Target Remote UE corresponding to each E2E service or a group of E2E services of the Source Remote UE, for example, the PC5 layer 2 (Layer-2) ID of the Target Remote UE, or other ID information (used to identify and distinguish the Target Remote UE);

[0265] The ID information of the Relay UE with which the Source Remote UE directly communicates may be, for example, the PC5 layer 2 (Layer-2) ID of the Relay UE, or other ID information (used to identify and distinguish the Relay UE).

[0266] Here, the above-mentioned reporting information can be reported in a new data format or a new RRC message (Msg), or it can be reported by reusing the existing sidelink terminal information (SidelinkUEInformation). However, it needs to be clearly distinguished that this is a report of the U2U Relay link, so a different reporting domain can be adopted or the original QoS information domain can be reused but with a special U2U Relay link indication, etc. In short, the network side needs to be aware that this is different from the requirements of direct communication between two UEs.

[0267] After receiving the information reported by the Source Remote UE, the serving cell / base station needs to send configuration information for the U2U Relay link to the Source Remote UE. The configuration information includes at least one of the following:

[0268] Configuration information of the end-to-end bearer (E2E SL RB) between the Source Remote UE and the Target Remote UE, which may include Service Data Adaptation Protocol (SDAP) and Packet Data Convergence Protocol (PDCP) configuration. The SDAP configuration will indicate the E2E QoS flow ID information contained in the SL RB;

[0269] Target Remote UE ID information corresponding to the E2E SL RB. Because the Source Remote UE may communicate with multiple Target Remote UEs, the E2E SL RB needs to indicate its corresponding Target Remote UE ID information;

[0270] PC5 Radio Link Control (RLC) channel configuration information between the Source Remote UE and the Relay UE, which may include configuration information of at least one of the RLC, MAC, and PHY layers;

[0271] The Relay UE ID information corresponding to the PC5 RLC channel between the Source Remote UE and the Relay UE. Since the Source Remote UE may communicate with multiple Target Remote UEs through multiple Relay UEs, the PC5 RLC channel needs to indicate the corresponding Relay UE ID information;

[0272] The mapping relationship between the E2E SL RB between the Source Remote UE and the Target Remote UE and the PC5 RLC channel between the Source Remote UE and the Relay UE, where the mapping relationship is generally N to 1, that is, a many-to-one relationship. The mapping relationship may be configured, for example, by including the corresponding PC5 RLC channel ID or index information in each E2E SL RB (which needs to indicate which Relay UE's PC5 RLC channel it is, and therefore needs to additionally carry the Relay UE ID); or, by including the corresponding E2E SL RB ID or index list (index list information) in each PC5 RLC channel (which needs to indicate which Target UE's E2E SL RB it is, and therefore needs to additionally carry the Target Remote UE ID).

[0273] The logical channel group (LCG) ID corresponding to the different PC5 RLC channels between the Source Remote UE and the Relay UE; optionally, when the Source Remote UE is configured as resource scheduling mode mode 1 (i.e., the mode in which the network schedules PC5 resources), the network side device (such as the serving cell / base station of the Source Remote UE) can be the ID corresponding to the different PC5 RLC channels between the Source Remote UE and the Relay UE, which can facilitate the Source Remote UE to subsequently perform the PC5 buffer status report (BSR) reporting process according to the cache size of the LCG ID, thereby facilitating the allocation of appropriate transmission resources.

[0274] In addition, after obtaining the configuration information of the U2U Relay link, the Source Remote UE sends the E2E SL RB information to the Target Remote UE to establish an end-to-end SL RB transmission pipeline, and sends the PC5 RLC channel configuration between the Source Remote UE and the Relay UE, as well as the mapping information relationship between the E2E SL RB and the PC5 RLC channel between the Source Remote UE and the Relay UE, to the Relay UE to establish the first-hop RLC channel transmission pipeline. In this way, the first-hop transmission from the Source Remote UE to the Target Remote UE can be opened.

[0275] Implementation Method 2

[0276] In this embodiment, the Relay UE is in the RRC Connected state. It needs to report the service requirements of the U2U Relay in which it participates and the transmission requirements of the second hop (i.e., between the Relay UE and the Target Remote UE) to the network side, and then obtain relevant configurations from the network side. After completing the configuration of the second hop and the E2E bearer mapping configuration process, it can then transmit data through the U2U Relay link.

[0277] It should be noted that although the reporting process of the Relay UE can also reuse the reporting signaling of the existing PC5 link (i.e. direct PC5 communication between two UEs), there needs to be some obvious distinction. The network side needs to know that this is a request and report from the Relay UE in a U2U Relay link. The focus needs to be on the configuration of the second hop, rather than the traditional one-hop communication between UEs. This allows for a better understanding of the QoS requirements of the service and the already configured E2E SL RB configuration, thereby providing a second-hop configuration from the Relay UE to the Target Remote UE suitable for the U2U Relay link.

[0278] Specifically, the information reported by the Relay UE to its serving cell / base station includes at least one of the following:

[0279] In the SL U2U Relay architecture, the configuration information of the E2E SL RB between the Source Remote UE and the Target Remote UE may include at least one of the RB ID, RB configuration parameters, QoS flow information contained in the RB, and the corresponding QoS profile; here, the configuration information of the E2E SL RB may be the one sent by the Source Remote UE to the Relay UE in the aforementioned embodiment 1.

[0280] In the SL U2U Relay architecture, the service demand information transmitted between the Relay UE and the Target Remote UE (i.e., the second hop) may include at least one of QoS flow information and corresponding QoS profile information. The demand information may be the portion after being split by the Relay UE. For example, the E2E PDB may be 100ms, which is then split into 50ms for the first-hop PDB and 50ms for the second-hop PDB.

[0281] In the SL U2U Relay architecture, the data source of the Relay UE is the ID information of the Source Remote UE, which can be, for example, the PC5 layer 2 (Layer-2) ID of the Source Remote UE or its local UE ID information;

[0282] In the SL U2U Relay architecture, the ID information of the Target Remote UE, the data receiving end of the Relay UE, may be, for example, the PC5 layer 2 (Layer-2) ID of the Target Remote UE or its local UE ID information;

[0283] Configuration information of the PC5 RLC channel between the Source Remote UE and the Relay UE;

[0284] The mapping relationship between E2E SL RB and the PC5 RLC channel between Source Remote UE and Relay UE.

[0285] Here, the above-mentioned reporting information can be reported in a new data format or a new RRC Msg, or it can be reported by reusing the existing SidelinkUEInformation. However, it needs to be clearly distinguished that this is the report of the Relay UE in the U2U Relay link. Therefore, a different reporting domain can be adopted or the original QoS information domain can be reused but carrying a special U2U Relay link or Relay UE identity indication, etc. Moreover, the report of the Relay UE not only carries QoS information (i.e., the service requirement information of the second hop), but also needs to carry the configured E2E SL RB configuration information, and optionally, it can also carry the mapping relationship between the PC5 RLC channel configuration between the Source Remote UE and the Relay UE and the E2E SL RB configuration information, etc. In short, the network needs to be aware that this is the reporting requirement of the Relay UE in the U2U Relay link.

[0286] After receiving the information reported by the Relay UE, the serving cell / base station needs to send configuration information for the U2U Relay link to the Relay UE, which may include at least one of the following:

[0287] The PC5 RLC channel configuration information between the Relay UE and the Target Remote UE may include configuration information of at least one of the RLC, MAC, and PHY layers;

[0288] The Target Remote UE ID information corresponding to the PC5 RLC channel between the Relay UE and the Target Remote UE. Since the Relay UE may communicate with multiple Target Remote UEs due to the needs of multiple Source Remote UEs, the PC5 RLC channel needs to indicate the corresponding Target Remote UE ID information;

[0289] The mapping relationship between the E2E SL RB between the Source Remote UE and the Target Remote UE and the PC5 RLC channel between the Relay UE and the Target Remote UE is generally N to 1, that is, a many-to-one relationship. The mapping relationship may be configured, for example, by including the corresponding PC5 RLC channel ID or index information in each E2E SL RB (where it is necessary to indicate which Target Remote UE's PC5 RLC channel it is, and therefore it is necessary to additionally carry the Target Remote UE ID), or by including the corresponding E2E SL RB ID or index list information in each PC5 RLC channel (where it is necessary to indicate which E2E SL RB between the Source Remote UE and the Target Remote UE it is, and therefore it is necessary to additionally carry the Target Remote UE ID and the Source Remote UE ID).

[0290] The LCG IDs corresponding to the different PC5 RLC channels between the Relay UE and the Target Remote UE are used. This allows the Relay UE to subsequently perform a PC5 BSR reporting process based on the cache size of the LCG IDs corresponding to the different PC5 RLC channels, thereby facilitating the allocation of appropriate transmission resources. Optionally, when the Relay UE is configured in resource scheduling mode 1, the network-side device (e.g., the serving cell / base station of the Relay UE) can allocate LCG IDs for the different PC5 RLC channels between the Relay UE and the Target Remote UE.

[0291] In addition, after obtaining the above configuration information of the U2U Relay link, the Relay UE sends the PC5 RLC channel configuration between the Relay UE and the Target Remote UE, as well as the mapping relationship between the E2E SL RB and the PC5 RLC channel between the Relay UE and the Target Remote UE, to the Target Remote UE, and establishes the second-hop RLC channel transmission pipeline, so that the second-hop transmission from the Relay UE to the Target Remote UE can be opened.

[0292] Implementation Method 3

[0293] In this embodiment, the Relay UE is in the RRC Connected state. It needs to report the service requirements of the U2U Relay in which it participates and the transmission configuration of the second hop (i.e., between the Relay UE and the Target Remote UE) to the network side, and then obtain relevant configuration confirmation from the network side, and synchronize the content and configuration of the LCG, completing the configuration of the second hop and the E2E bearer mapping configuration process before it can transmit data through the U2U Relay link.

[0294] It should be noted that although the reporting process of the Relay UE can also reuse the reporting signaling of the existing PC5 link (i.e. direct PC5 communication between two UEs), there needs to be some obvious distinction. The network needs to be informed that this is a Relay request and report in a U2U Relay link. The focus needs to be on reporting the second-hop configuration and obtaining synchronous understanding with the network, rather than the traditional PC5 communication requirements. This allows for a better understanding of the service QoS requirements and the already configured E2E SL RB configuration and RLC channel configuration and mapping, so that more appropriate scheduling control and resources can be provided in the subsequent second-hop communication from the Relay UE to the Target Remote UE.

[0295] Specifically, the information reported by the Relay UE to its serving cell / base station includes at least one of the following:

[0296] In the SL U2U Relay architecture, the configuration information of the E2E SL RB between the Source Remote UE and the Target Remote UE may include at least one of the RB ID, RB configuration parameters, QoS flow information contained in the RB, and the corresponding QoS profile; here, the configuration information of the E2E SL RB may be the one sent by the Source Remote UE to the Relay UE in the aforementioned embodiment 1.

[0297] In the SL U2U Relay architecture, the service demand information transmitted between the Relay UE and the Target Remote UE (i.e., the second hop) may include at least one of QoS flow information and corresponding QoS profile information. The demand information may be the portion after being split by the Relay UE. For example, the E2E PDB may be 100ms, which is then split into 50ms for the first-hop PDB and 50ms for the second-hop PDB.

[0298] In the SL U2U relay architecture, the transmission channel information between the Relay UE and the Target Remote UE may include at least one of the following: PC5 RLC channel configuration information between the Relay UE and the Target Remote UE, E2E SL RB information mapped to the PC5 RLC channel, QoS flow mapped to the E2E SL RB, and QoS profile information;

[0299] In the SL U2U Relay architecture, the data source of the Relay UE is the ID information of the Source Remote UE, which can be, for example, the PC5 layer 2 (Layer-2) ID of the Source Remote UE or its local UE ID information;

[0300] In the SL U2U Relay architecture, the ID information of the Target Remote UE, the data receiving end of the Relay UE, may be, for example, the PC5 layer 2 (Layer-2) ID of the Target Remote UE or its local UE ID information;

[0301] The allocation suggestion includes the LCG IDs allocated by the Relay UE to different PC5 RLC channels between the Relay UE and the Target Remote UE. Optionally, when the Relay UE is configured in resource scheduling mode 1, the Relay UE can allocate LCG IDs to different PC5 RLC channels between the Relay UE and the Target Remote UE. That is, if the Relay UE wishes to be configured in resource scheduling mode 1, it can negotiate the configuration of the LCG ID with the serving cell / base station. In other words, the Relay UE can carry its own LCG ID allocation suggestion and wait for network confirmation. It is understandable that the Relay UE can also wait for the network to directly configure the LCG ID for the PC5 RLC channel between the Relay UE and the Target Remote UE.

[0302] After receiving the information reported by the Relay UE, the serving cell / base station needs to send a confirmation of the U2U Relay link configuration and mapping information to the Relay UE, including at least one of the following:

[0303] Regarding the confirmation and acceptance of the configuration content reported by the Relay UE, you can confirm it as a whole or list the acceptance status of different channels separately, such as the acceptance / rejection status of the RLC channel granularity, the acceptance / rejection status of the E2E SL RB granularity, and the acceptance / rejection status of the QoS flow granularity.

[0304] The LCG ID corresponding to the different PC5 RLC channels between the Relay UE and the Target Remote UE, where the LCG ID may be allocated by the serving cell / base station, or the serving cell / base station may accept or confirm at least part of the LCG ID in the above allocation suggestion. Optionally, when the Relay UE is configured in resource scheduling mode 1, the serving cell / base station of the Relay UE may allocate LCG IDs for the different PC5 RLC channels between the Relay UE and the Target Remote UE, or accept or confirm at least part of the LCG ID in the above allocation suggestion, so that the Relay UE can subsequently perform the PC5 BSR reporting process according to the cache size of the LCG ID, thereby facilitating the allocation of appropriate transmission resources.

[0305] In addition, after obtaining the second-hop configuration confirmation of the U2U Relay link, the Relay UE sends the PC5 RLC channel configuration between the Relay UE and the Target Remote UE, as well as the mapping relationship between the E2E SL RB and the PC5 RLC channel between the Relay UE and the Target Remote UE, to the Target Remote UE to establish the second-hop RLC channel transmission pipeline, so that the second-hop transmission from the Source Remote UE to the Target Remote UE can be opened.

[0306] It should also be noted that the above-mentioned embodiment 1 occurs before embodiment 2 or 3, and embodiment 2 and embodiment 3 are parallel technical solutions.

[0307] As can be seen from the above, the embodiments of the present application can enable the Relay UE in the RRC Connected state to obtain an RLC channel and mapping configuration (i.e., the mapping relationship between the end-to-end bearer and the RLC channel) that is consistent with the understanding of the network side, and can work well in the resource scheduling Mode 1 mode, ensuring the efficiency of communication between UEs, thereby reducing the complexity of the UE and improving the system efficiency while ensuring transmission.

[0308] The transmission configuration method provided in the embodiment of the present application can be executed by a transmission configuration device. In the embodiment of the present application, the transmission configuration device provided in the embodiment of the present application is described by taking the transmission configuration device executing the transmission configuration method as an example.

[0309] In a third aspect, an embodiment of the present application provides a transmission configuration device, which is applied to a first terminal. As shown in FIG7 , the transmission configuration device 70 may include the following modules:

[0310] The first sending module 701 is configured to report transmission requirement information of terminal-to-terminal relay transmission to a network-side device;

[0311] The first receiving module 702 is configured to receive target information sent by the network-side device, wherein the target information is used to determine configuration information of the terminal-to-terminal relay transmission.

[0312] Optionally, when the first terminal is a relay terminal, the transmission requirement information includes at least one of the following:

[0313] End-to-end bearer configuration information;

[0314] demand information of a service transmitted between the relay terminal and a second terminal, where the second terminal is a next-hop terminal of the relay terminal;

[0315] Identification information of the source remote terminal;

[0316] identification information of the target remote terminal;

[0317] identification information of the second terminal;

[0318] Configuration information of a first channel, where the first channel includes a radio link control (RLC) channel of a communication interface PC5 between a previous hop terminal of the relay terminal and the relay terminal;

[0319] A first mapping relationship includes a mapping relationship between an end-to-end bearer and the first channel.

[0320] Optionally, when the first terminal is a relay terminal, the target information includes at least one of the following:

[0321] Configuration information of a second channel, where the second channel includes a PC5 RLC channel between the relay terminal and a second terminal, where the second terminal is a next-hop terminal of the relay terminal;

[0322] identification information of the second terminal;

[0323] identification information of the target remote terminal corresponding to the second channel;

[0324] a second mapping relationship, where the second mapping relationship includes a mapping relationship between an end-to-end bearer and the second channel;

[0325] The logical channel group identification information corresponding to the second channel.

[0326] Optionally, when the first terminal is a relay terminal, the transmission requirement information includes at least one of the following:

[0327] End-to-end bearer configuration information;

[0328] demand information of a service transmitted between the relay terminal and a second terminal, where the second terminal is a next-hop terminal of the relay terminal;

[0329] identification information of the second terminal;

[0330] Identification information of the source remote terminal;

[0331] identification information of the target remote terminal;

[0332] configuration information of a second channel, where the second channel includes a PC5 RLC channel between the relay terminal and the second terminal;

[0333] Quality of service (Qos) information;

[0334] Target configuration information, the target configuration information including an association relationship between any two of the second channel, the end-to-end bearer, and the QoS information;

[0335] Configuration suggestion information, where the configuration suggestion information includes identification information of a logical channel group allocated by the first terminal to the second channel.

[0336] Optionally, the target information includes at least one of a confirmation message, a rejection message, and a logical channel group corresponding to the second channel configured by the network side device;

[0337] The confirmation message includes at least one of the following:

[0338] Configuration information of at least part of the second channel confirmed by the network-side device;

[0339] At least part of the end-to-end bearer confirmed by the network side device;

[0340] At least part of the QoS flow information confirmed by the network side device;

[0341] an index of at least part of the configuration information of the second channel confirmed by the network-side device;

[0342] An index of at least part of the end-to-end bearer confirmed by the network-side device;

[0343] An index of at least part of the QoS flow information confirmed by the network side device;

[0344] identification information of the logical channel group corresponding to at least part of the second channel confirmed by the network side device;

[0345] Alternatively, the confirmation message includes an instruction for confirming all configuration information in the transmission requirement information reported by the first terminal;

[0346] The rejection information includes at least one of the following:

[0347] at least part of the configuration information of the second channel rejected by the network-side device;

[0348] At least part of the end-to-end bearer rejected by the network side device;

[0349] At least part of the QoS flow information rejected by the network side device;

[0350] an index of at least part of the configuration information of the second channel rejected by the network-side device;

[0351] An index of an RB of at least part of the end-to-end bearer rejected by the network-side device;

[0352] An index of at least part of the QoS flow information rejected by the network side device;

[0353] identification information of a logical channel group corresponding to at least part of the second channels rejected by the network side device;

[0354] Alternatively, the rejection message includes an instruction for rejecting all configuration information in the transmission requirement information reported by the first terminal.

[0355] Optionally, the device further comprises:

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

[0357] End-to-end bearer configuration information;

[0358] configuration information of the second channel;

[0359] A second mapping relationship, where the second mapping relationship includes a mapping relationship between an end-to-end bearer and the second channel.

[0360] Optionally, when the first terminal is a source remote terminal, the transmission requirement information includes at least one of the following:

[0361] End-to-end business demand information;

[0362] Demand information for services transmitted between a source remote terminal and a third terminal, the third terminal being a next-hop terminal of the source remote terminal;

[0363] Identification information of the target remote terminal corresponding to the end-to-end service;

[0364] Identification information of the third terminal.

[0365] Optionally, when the first terminal is a source remote terminal, the target information includes at least one of the following:

[0366] End-to-end bearer configuration information;

[0367] Configuration information of a third channel, the third channel comprising a PC5 RLC channel between the source remote terminal and a third terminal, the third terminal being a next-hop terminal of the source remote terminal;

[0368] identification information of the target remote terminal corresponding to the third channel;

[0369] identification information of the third terminal;

[0370] a third mapping relationship, the third mapping relationship including a mapping relationship between an end-to-end bearer and the third channel;

[0371] The logical channel group identification information corresponding to the third channel.

[0372] Optionally, the device further includes at least one of the following modules:

[0373] A fourth sending module, configured to send the configuration information of the end-to-end bearer to a target remote terminal;

[0374] A fifth sending module, configured to send at least one of the following items to the third terminal;

[0375] End-to-end bearer configuration information;

[0376] Configuration information of the third channel;

[0377] The third mapping relationship.

[0378] Optionally, the first sending module 701 is specifically configured to:

[0379] Reporting the transmission requirement information to the network-side device by using at least one of a target data format and a target message, wherein the target data format is different from an existing data format, and the target message is different from an existing message;

[0380] or,

[0381] The transmission requirement information and target indication information are reported to the network side device, wherein the target indication information is used to indicate that the transmission requirement information is associated with terminal-to-terminal relay transmission.

[0382] Optionally, the first sending module 701 is specifically configured to:

[0383] When the first terminal is in a connected state, the transmission requirement information is reported to the network side device.

[0384] The transmission configuration device in the embodiments of the present application can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or chip. The electronic device can be a terminal. For example, the terminal can include but is not limited to the types of terminal 11 listed above, and the embodiments of the present application do not specifically limit this.

[0385] The transmission configuration device provided in the embodiment of the present application can implement the various processes implemented in the method embodiment of Figure 5 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0386] In a fourth aspect, an embodiment of the present application provides a transmission configuration device. As shown in FIG8 , the transmission configuration device 80 may include the following modules:

[0387] The second receiving module 801 is configured to receive transmission requirement information of terminal-to-terminal relay transmission reported by a first terminal;

[0388] The second sending module 802 is configured to send target information to the first terminal, wherein the target information is used to determine configuration information of the terminal-to-terminal relay transmission.

[0389] Optionally, when the first terminal is a relay terminal, the transmission requirement information includes at least one of the following:

[0390] End-to-end bearer configuration information;

[0391] demand information of a service transmitted between the relay terminal and a second terminal, where the second terminal is a next-hop terminal of the relay terminal;

[0392] Identification information of the source remote terminal;

[0393] identification information of the target remote terminal;

[0394] identification information of the second terminal;

[0395] Configuration information of a first channel, where the first channel includes a radio link control (RLC) channel of a communication interface PC5 between a previous hop terminal of the relay terminal and the relay terminal;

[0396] A first mapping relationship includes a mapping relationship between an end-to-end bearer and the first channel.

[0397] Optionally, when the first terminal is a relay terminal, the target information includes at least one of the following:

[0398] Configuration information of a second channel, where the second channel includes a PC5 RLC channel between the relay terminal and a second terminal, where the second terminal is a next-hop terminal of the relay terminal;

[0399] identification information of the second terminal;

[0400] identification information of the target remote terminal corresponding to the second channel;

[0401] a second mapping relationship, where the second mapping relationship includes a mapping relationship between an end-to-end bearer and the second channel;

[0402] The logical channel group identification information corresponding to the second channel.

[0403] Optionally, when the first terminal is a relay terminal, the transmission requirement information includes at least one of the following:

[0404] End-to-end bearer configuration information;

[0405] demand information of a service transmitted between the relay terminal and a second terminal, where the second terminal is a next-hop terminal of the relay terminal;

[0406] identification information of the second terminal;

[0407] Identification information of the source remote terminal;

[0408] identification information of the target remote terminal;

[0409] configuration information of a second channel, where the second channel includes a PC5 RLC channel between the relay terminal and the second terminal;

[0410] Quality of service (Qos) information;

[0411] Target configuration information, the target configuration information including an association relationship between any two of the second channel, the end-to-end bearer, and the QoS information;

[0412] Configuration suggestion information, where the configuration suggestion information includes identification information of a logical channel group allocated by the first terminal to the second channel.

[0413] Optionally, the target information includes at least one of a confirmation message, a rejection message, and a logical channel group corresponding to the second channel configured by the network side device;

[0414] The confirmation message includes at least one of the following:

[0415] Configuration information of at least part of the second channel confirmed by the network-side device;

[0416] At least part of the end-to-end bearer confirmed by the network side device;

[0417] At least part of the QoS flow information confirmed by the network side device;

[0418] an index of at least part of the configuration information of the second channel confirmed by the network-side device;

[0419] An index of at least part of the end-to-end bearer confirmed by the network-side device;

[0420] An index of at least part of the QoS flow information confirmed by the network side device;

[0421] identification information of the logical channel group corresponding to at least part of the second channel confirmed by the network side device;

[0422] Alternatively, the confirmation message includes an instruction for confirming all configuration information in the transmission requirement information reported by the first terminal;

[0423] The rejection information includes at least one of the following:

[0424] at least part of the configuration information of the second channel rejected by the network-side device;

[0425] At least part of the end-to-end bearer rejected by the network side device;

[0426] At least part of the QoS flow information rejected by the network side device;

[0427] an index of at least part of the configuration information of the second channel rejected by the network-side device;

[0428] An index of an RB of at least part of the end-to-end bearer rejected by the network-side device;

[0429] An index of at least part of the QoS flow information rejected by the network side device;

[0430] identification information of a logical channel group corresponding to at least part of the second channels rejected by the network side device;

[0431] Alternatively, the rejection message includes an instruction for rejecting all configuration information in the transmission requirement information reported by the first terminal.

[0432] Optionally, when the first terminal is a source remote terminal, the transmission requirement information includes at least one of the following:

[0433] End-to-end business demand information;

[0434] Demand information for services transmitted between a source remote terminal and a third terminal, the third terminal being a next-hop terminal of the source remote terminal;

[0435] Identification information of the target remote terminal corresponding to the end-to-end service;

[0436] Identification information of the third terminal.

[0437] Optionally, when the first terminal is a source remote terminal, the target information includes at least one of the following:

[0438] End-to-end bearer configuration information;

[0439] Configuration information of a third channel, the third channel comprising a PC5 RLC channel between the source remote terminal and a third terminal, the third terminal being a next-hop terminal of the source remote terminal;

[0440] identification information of the target remote terminal corresponding to the third channel;

[0441] identification information of the third terminal;

[0442] a third mapping relationship, the third mapping relationship including a mapping relationship between an end-to-end bearer and the third channel;

[0443] The logical channel group identification information corresponding to the third channel.

[0444] Optionally, the second receiving module 801 is specifically configured to:

[0445] receiving the transmission requirement information sent by the first terminal in at least one of a target data format and a target message, wherein the target data format is different from an existing data format, and the target message is different from an existing message;

[0446] or,

[0447] The transmission requirement information and target indication information sent by the terminal are received, wherein the target indication information is used to indicate that the transmission requirement information is associated with terminal-to-terminal relay transmission.

[0448] The transmission configuration device in the embodiments of the present application can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or chip. The electronic device can be a terminal. For example, the terminal can include but is not limited to the types of terminal 11 listed above, and the embodiments of the present application do not specifically limit this.

[0449] The transmission configuration device provided in the embodiment of the present application can implement the various processes implemented in the method embodiment of Figure 6 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0450] As shown in Figure 9, an embodiment of the present application further provides a communication device 900, including a processor 901 and a memory 902, wherein the memory 902 stores a program or instruction that can be run on the processor 901. For example, when the communication device 900 is a first terminal, the program or instruction, when executed by the processor 901, implements the various steps of the embodiment of the transmission configuration method described in the first aspect above, and can achieve the same technical effect. When the communication device 900 is a network-side device, the program or instruction, when executed by the processor 901, implements the various steps of the embodiment of the transmission configuration method described in the second aspect above, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

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

[0452] The terminal 1000 includes but is not limited to: a radio frequency unit 1001, a network module 1002, an audio output unit 1003, an input unit 1004, a sensor 1005, a display unit 1006, a user input unit 1007, an interface unit 1008, a memory 1009 and at least some of the components of the processor 1010.

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

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

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

[0456] The memory 1009 can be used to store software programs or instructions and various data. The memory 1009 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, applications or instructions required for at least one function (such as a sound playback function, an image playback function, etc.). In addition, the memory 1009 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 1009 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.

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

[0458] When the terminal 1000 serves as the first terminal, the radio frequency unit 1001 is configured to:

[0459] Reporting terminal-to-terminal relay transmission requirements to network devices;

[0460] Receive target information sent by the network-side device, wherein the target information is used to determine configuration information of the terminal-to-terminal relay transmission.

[0461] Optionally, when the first terminal is a relay terminal, the transmission requirement information includes at least one of the following:

[0462] End-to-end bearer configuration information;

[0463] demand information of a service transmitted between the relay terminal and a second terminal, where the second terminal is a next-hop terminal of the relay terminal;

[0464] Identification information of the source remote terminal;

[0465] identification information of the target remote terminal;

[0466] identification information of the second terminal;

[0467] Configuration information of a first channel, where the first channel includes a radio link control (RLC) channel of a communication interface PC5 between a previous hop terminal of the relay terminal and the relay terminal;

[0468] A first mapping relationship includes a mapping relationship between an end-to-end bearer and the first channel.

[0469] Optionally, when the first terminal is a relay terminal, the target information includes at least one of the following:

[0470] Configuration information of a second channel, where the second channel includes a PC5 RLC channel between the relay terminal and a second terminal, where the second terminal is a next-hop terminal of the relay terminal;

[0471] identification information of the second terminal;

[0472] identification information of the target remote terminal corresponding to the second channel;

[0473] a second mapping relationship, where the second mapping relationship includes a mapping relationship between an end-to-end bearer and the second channel;

[0474] The logical channel group identification information corresponding to the second channel.

[0475] Optionally, when the first terminal is a relay terminal, the transmission requirement information includes at least one of the following:

[0476] End-to-end bearer configuration information;

[0477] demand information of a service transmitted between the relay terminal and a second terminal, where the second terminal is a next-hop terminal of the relay terminal;

[0478] identification information of the second terminal;

[0479] Identification information of the source remote terminal;

[0480] identification information of the target remote terminal;

[0481] configuration information of a second channel, where the second channel includes a PC5 RLC channel between the relay terminal and the second terminal;

[0482] Quality of service (Qos) information;

[0483] Target configuration information, the target configuration information including an association relationship between any two of the second channel, the end-to-end bearer, and the QoS information;

[0484] Configuration suggestion information, where the configuration suggestion information includes identification information of a logical channel group allocated by the first terminal to the second channel.

[0485] Optionally, the target information includes at least one of a confirmation message, a rejection message, and a logical channel group corresponding to the second channel configured by the network side device;

[0486] The confirmation message includes at least one of the following:

[0487] Configuration information of at least part of the second channel confirmed by the network-side device;

[0488] At least part of the end-to-end bearer confirmed by the network side device;

[0489] At least part of the QoS flow information confirmed by the network side device;

[0490] an index of at least part of the configuration information of the second channel confirmed by the network-side device;

[0491] An index of at least part of the end-to-end bearer confirmed by the network-side device;

[0492] An index of at least part of the QoS flow information confirmed by the network side device;

[0493] identification information of the logical channel group corresponding to at least part of the second channel confirmed by the network side device;

[0494] Alternatively, the confirmation message includes an instruction for confirming all configuration information in the transmission requirement information reported by the first terminal;

[0495] The rejection information includes at least one of the following:

[0496] at least part of the configuration information of the second channel rejected by the network-side device;

[0497] At least part of the end-to-end bearer rejected by the network side device;

[0498] At least part of the QoS flow information rejected by the network side device;

[0499] an index of at least part of the configuration information of the second channel rejected by the network-side device;

[0500] An index of an RB of at least part of the end-to-end bearer rejected by the network-side device;

[0501] An index of at least part of the QoS flow information rejected by the network side device;

[0502] identification information of a logical channel group corresponding to at least part of the second channels rejected by the network side device;

[0503] Alternatively, the rejection message includes an instruction for rejecting all configuration information in the transmission requirement information reported by the first terminal.

[0504] Optionally, the radio frequency unit 1001 is further configured to:

[0505] Sending at least one of the following to the second terminal:

[0506] End-to-end bearer configuration information;

[0507] configuration information of the second channel;

[0508] A second mapping relationship, where the second mapping relationship includes a mapping relationship between an end-to-end bearer and the second channel.

[0509] Optionally, when the first terminal is a source remote terminal, the transmission requirement information includes at least one of the following:

[0510] End-to-end business demand information;

[0511] Demand information for services transmitted between a source remote terminal and a third terminal, the third terminal being a next-hop terminal of the source remote terminal;

[0512] Identification information of the target remote terminal corresponding to the end-to-end service;

[0513] Identification information of the third terminal.

[0514] Optionally, when the first terminal is a source remote terminal, the target information includes at least one of the following:

[0515] End-to-end bearer configuration information;

[0516] Configuration information of a third channel, the third channel comprising a PC5 RLC channel between the source remote terminal and a third terminal, the third terminal being a next-hop terminal of the source remote terminal;

[0517] identification information of the target remote terminal corresponding to the third channel;

[0518] identification information of the third terminal;

[0519] a third mapping relationship, the third mapping relationship including a mapping relationship between an end-to-end bearer and the third channel;

[0520] The logical channel group identification information corresponding to the third channel.

[0521] Optionally, the radio frequency unit 1001 is further configured to perform at least one of the following:

[0522] Sending the end-to-end bearer configuration information to the target remote terminal;

[0523] Sending at least one of the following to the third terminal;

[0524] End-to-end bearer configuration information;

[0525] Configuration information of the third channel;

[0526] The third mapping relationship.

[0527] Optionally, the radio frequency unit 1001 reports transmission requirement information of terminal-to-terminal relay transmission to the network side device, including:

[0528] Reporting the transmission requirement information to the network-side device by using at least one of a target data format and a target message, wherein the target data format is different from an existing data format, and the target message is different from an existing message;

[0529] or,

[0530] The transmission requirement information and target indication information are reported to the network side device, wherein the target indication information is used to indicate that the transmission requirement information is associated with terminal-to-terminal relay transmission.

[0531] Optionally, the radio frequency unit 1001 reports transmission requirement information of terminal-to-terminal relay transmission to the network-side device, including:

[0532] When the first terminal is in a connected state, the transmission requirement information is reported to the network side device.

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

[0534] The present application also provides a network-side device, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to execute a program or instruction to implement the steps of the method embodiment shown in FIG10 . This network-side device embodiment corresponds to the aforementioned network-side device method embodiment, and each implementation process and implementation method of the aforementioned method embodiment are applicable to this network-side device embodiment and can achieve the same technical effects.

[0535] Specifically, embodiments of the present application also provide a network-side device. As shown in Figure 11, the network-side device 1100 includes an antenna 111, a radio frequency device 112, a baseband device 113, a processor 114, and a memory 115. Antenna 111 is connected to radio frequency device 112. In the uplink direction, radio frequency device 112 receives information via antenna 111 and sends the received information to baseband device 113 for processing. In the downlink direction, baseband device 113 processes the information to be transmitted and sends it to radio frequency device 112. Radio frequency device 112 processes the received information and then sends it through antenna 111.

[0536] The method executed by the network-side device in the above embodiment may be implemented in the baseband device 113 , which includes a baseband processor.

[0537] The baseband device 113 may include, for example, at least one baseband board, on which multiple chips are arranged, as shown in Figure 11, one of the chips is, for example, a baseband processor, which is connected to the memory 115 through a bus interface to call the program in the memory 115 to execute the network device operations shown in the above method embodiment.

[0538] The network side device may further include a network interface 116, which is, for example, a Common Public Radio Interface (CPRI).

[0539] Specifically, the network side device 1100 of an embodiment of the present invention also includes: instructions or programs stored in the memory 115 and executable on the processor 114. The processor 114 calls the instructions or programs in the memory 115 to execute the methods executed by the modules shown in FIG8 and achieve the same technical effect. To avoid repetition, they will not be elaborated here.

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

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

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

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

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

[0545] An embodiment of the present application also provides a transmission configuration system, including: a first terminal and a network side device, wherein the first terminal can be used to execute the steps of the transmission configuration method described in the first aspect above, and the network side device can be used to execute the steps of the transmission configuration method described in the second aspect above.

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

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

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

Claims

1. A transmission configuration method, wherein: The method comprises: The first terminal reports transmission requirement information of terminal-to-terminal relay transmission to the network side device; The first terminal receives target information sent by the network side device, wherein the target information is used to determine configuration information of the terminal-to-terminal relay transmission.

2. The method according to claim 1, wherein: In the case where the first terminal is a relay terminal, the transmission requirement information includes at least one of the following: End-to-end bearer configuration information; demand information of a service transmitted between the relay terminal and a second terminal, the second terminal being a next-hop terminal of the relay terminal; Identification information of the source remote terminal; identification information of the target remote terminal; identification information of the second terminal; Configuration information of a first channel, wherein the first channel includes a radio link control RLC channel of a communication interface PC5 between a previous hop terminal of the relay terminal and the relay terminal; A first mapping relationship, where the first mapping relationship includes a mapping relationship between an end-to-end bearer and the first channel.

3. The method according to claim 1 or 2, wherein: In the case where the first terminal is a relay terminal, the target information includes at least one of the following: Configuration information of a second channel, where the second channel includes a PC5 RLC channel between the relay terminal and a second terminal, where the second terminal is a next-hop terminal of the relay terminal; identification information of the second terminal; identification information of a target remote terminal corresponding to the second channel; a second mapping relationship, wherein the second mapping relationship includes a mapping relationship between an end-to-end bearer and the second channel; The logical channel group identification information corresponding to the second channel.

4. The method according to claim 1, wherein: In the case where the first terminal is a relay terminal, the transmission requirement information includes at least one of the following: End-to-end bearer configuration information; demand information of a service transmitted between the relay terminal and a second terminal, the second terminal being a next-hop terminal of the relay terminal; identification information of the second terminal; Identification information of the source remote terminal; identification information of the target remote terminal; Configuration information of a second channel, wherein the second channel includes a PC5RLC channel between the relay terminal and the second terminal; Quality of service (Qos) information; target configuration information, the target configuration information including the second channel, the end-to-end bearer, the Qos information The relationship between any two items in the information; Configuration suggestion information, where the configuration suggestion information includes identification information of a logical channel group allocated by the first terminal to the second channel.

5. The method according to claim 4, wherein: The target information includes at least one of a confirmation message, a rejection message, and a logical channel group corresponding to the second channel configured by the network side device; The confirmation message includes at least one of the following: Configuration information of at least part of the second channel confirmed by the network side device; At least part of the end-to-end bearer confirmed by the network side device; At least part of the QoS flow information confirmed by the network side device; An index of at least part of the configuration information of the second channel confirmed by the network side device; An index of at least part of the end-to-end bearer confirmed by the network side device; An index of at least part of the QoS flow information confirmed by the network side device; identification information of a logical channel group corresponding to at least part of the second channel confirmed by the network side device; Alternatively, the confirmation message includes an indication for indicating confirmation of all configuration information in the transmission requirement information reported by the first terminal; The rejection information includes at least one of the following: configuration information of at least part of the second channel rejected by the network side device; At least part of the end-to-end bearer rejected by the network side device; At least part of the QoS flow information rejected by the network side device; An index of at least part of the configuration information of the second channel rejected by the network side device; An index of an RB of at least part of the end-to-end bearer rejected by the network side device; An index of at least part of the QoS flow information rejected by the network side device; identification information of a logical channel group corresponding to at least part of the second channels rejected by the network side device; Alternatively, the rejection message includes an indication for indicating rejection of all configuration information in the transmission requirement information reported by the first terminal.

6. The method according to claim 3 or 4, wherein: The method further comprises: The first terminal sends at least one of the following to the second terminal: End-to-end bearer configuration information; configuration information of the second channel; A second mapping relationship, where the second mapping relationship includes a mapping relationship between an end-to-end bearer and the second channel.

7. The method according to claim 1, wherein: In the case where the first terminal is a source remote terminal, the transmission requirement information includes at least one of the following: End-to-end business demand information; Demand information for services transmitted between a source remote terminal and a third terminal, the third terminal being a next-hop terminal of the source remote terminal; Identification information of the target remote terminal corresponding to the end-to-end service; The identification information of the third terminal.

8. The method according to claim 1 or 7, wherein: In the case where the first terminal is a source remote terminal, the target information includes at least one of the following: End-to-end bearer configuration information; Configuration information of a third channel, wherein the third channel includes a PC5 RLC channel between the source remote terminal and a third terminal, and the third terminal is a next-hop terminal of the source remote terminal; identification information of the target remote terminal corresponding to the third channel; identification information of the third terminal; a third mapping relationship, the third mapping relationship comprising a mapping relationship between an end-to-end bearer and the third channel; The logical channel group identification information corresponding to the third channel.

9. The method according to claim 8, wherein: The method further comprises at least one of the following: The first terminal sends configuration information of the end-to-end bearer to a target remote terminal; The first terminal sends at least one of the following to the third terminal; End-to-end bearer configuration information; Configuration information of the third channel; The third mapping relationship.

10. The method according to any one of claims 1 to 9, wherein: The first terminal reports transmission requirement information of terminal-to-terminal relay transmission to the network side device, including: The first terminal reports the transmission requirement information to the network side device through at least one of a target data format and a target message, wherein the target data format is different from an existing data format, and the target message is different from an existing message; or, The first terminal reports the transmission requirement information and target indication information to the network side device, wherein the target indication information is used to indicate that the transmission requirement information is associated with terminal-to-terminal relay transmission.

11. The method according to any one of claims 1 to 10, wherein: The first terminal reports transmission requirement information of terminal-to-terminal relay transmission to the network side device, including: When the first terminal is in a connected state, the first terminal reports the transmission requirement information to the network side device.

12. A transmission configuration method, wherein: The method comprises: The network side device receives the transmission requirement information of the terminal-to-terminal relay transmission reported by the first terminal; The network side device sends target information to the first terminal, wherein the target information is used to determine configuration information of the terminal-to-terminal relay transmission.

13. The method according to claim 12, wherein: In the case where the first terminal is a relay terminal, the transmission requirement information includes at least one of the following: End-to-end bearer configuration information; The service demand information transmitted between the relay terminal and the second terminal, the second terminal being the relay terminal The next hop terminal; Identification information of the source remote terminal; identification information of the target remote terminal; identification information of the second terminal; Configuration information of a first channel, wherein the first channel includes a radio link control RLC channel of a communication interface PC5 between a previous hop terminal of the relay terminal and the relay terminal; A first mapping relationship, where the first mapping relationship includes a mapping relationship between an end-to-end bearer and the first channel.

14. The method according to claim 12 or 13, wherein: In the case where the first terminal is a relay terminal, the target information includes at least one of the following: Configuration information of a second channel, where the second channel includes a PC5 RLC channel between the relay terminal and a second terminal, where the second terminal is a next-hop terminal of the relay terminal; identification information of the second terminal; identification information of a target remote terminal corresponding to the second channel; a second mapping relationship, wherein the second mapping relationship includes a mapping relationship between an end-to-end bearer and the second channel; The logical channel group identification information corresponding to the second channel.

15. The method according to claim 12, wherein: In the case where the first terminal is a relay terminal, the transmission requirement information includes at least one of the following: End-to-end bearer configuration information; demand information of a service transmitted between the relay terminal and a second terminal, the second terminal being a next-hop terminal of the relay terminal; identification information of the second terminal; Identification information of the source remote terminal; identification information of the target remote terminal; Configuration information of a second channel, wherein the second channel includes a PC5RLC channel between the relay terminal and the second terminal; Quality of service (Qos) information; Target configuration information, the target configuration information including an association relationship between any two of the second channel, the end-to-end bearer, and the QoS information; Configuration suggestion information, where the configuration suggestion information includes identification information of a logical channel group allocated by the first terminal to the second channel.

16. The method according to claim 15, wherein: The target information includes at least one of a confirmation message, a rejection message, and a logical channel group corresponding to the second channel configured by the network side device; The confirmation message includes at least one of the following: Configuration information of at least part of the second channel confirmed by the network side device; At least part of the end-to-end bearer confirmed by the network side device; At least part of the QoS flow information confirmed by the network side device; An index of at least part of the configuration information of the second channel confirmed by the network side device; An index of at least part of the end-to-end bearer confirmed by the network side device; An index of at least part of the QoS flow information confirmed by the network side device; identification information of a logical channel group corresponding to at least part of the second channel confirmed by the network side device; Alternatively, the confirmation message includes an indication for indicating confirmation of all configuration information in the transmission requirement information reported by the first terminal; The rejection information includes at least one of the following: configuration information of at least part of the second channel rejected by the network side device; At least part of the end-to-end bearer rejected by the network side device; At least part of the QoS flow information rejected by the network side device; An index of at least part of the configuration information of the second channel rejected by the network side device; An index of an RB of at least part of the end-to-end bearer rejected by the network side device; An index of at least part of the QoS flow information rejected by the network side device; identification information of a logical channel group corresponding to at least part of the second channels rejected by the network side device; Alternatively, the rejection message includes an indication for indicating rejection of all configuration information in the transmission requirement information reported by the first terminal.

17. The method according to claim 12, wherein: In the case where the first terminal is a source remote terminal, the transmission requirement information includes at least one of the following: End-to-end business demand information; Demand information for services transmitted between a source remote terminal and a third terminal, the third terminal being a next-hop terminal of the source remote terminal; Identification information of the target remote terminal corresponding to the end-to-end service; The identification information of the third terminal.

18. The method according to claim 12 or 17, wherein: In the case where the first terminal is a source remote terminal, the target information includes at least one of the following: End-to-end bearer configuration information; Configuration information of a third channel, wherein the third channel includes a PC5 RLC channel between the source remote terminal and a third terminal, and the third terminal is a next-hop terminal of the source remote terminal; identification information of the target remote terminal corresponding to the third channel; identification information of the third terminal; a third mapping relationship, the third mapping relationship comprising a mapping relationship between an end-to-end bearer and the third channel; The logical channel group identification information corresponding to the third channel.

19. The method according to any one of claims 12 to 18, wherein: The network side device receives transmission requirement information of terminal-to-terminal relay transmission reported by the first terminal, including: The network side device receives the transmission requirement information sent by the first terminal using at least one of a target data format and a target message, wherein the target data format is different from an existing data format, and the target message is different from an existing message format. The interest is different; or, The network side device receives the transmission requirement information and target indication information sent by the terminal, wherein the target indication information is used to indicate that the transmission requirement information is associated with terminal-to-terminal relay transmission.

20. A transmission configuration device, wherein: Applied to a first terminal, the device includes: A first sending module, used to report transmission requirement information of terminal-to-terminal relay transmission to a network side device; The first receiving module is used to receive target information sent by the network side device, wherein the target information is used to determine the configuration information of the terminal-to-terminal relay transmission.

21. A transmission configuration device, wherein: Applied to a network side device, the device comprises: A second receiving module, configured to receive transmission requirement information of terminal-to-terminal relay transmission reported by the first terminal; The second sending module is used to send target information to the first terminal, wherein the target information is used to determine configuration information of the terminal-to-terminal relay transmission.

22. A communication device, wherein: 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, it implements the steps of the transmission configuration method as described in any one of claims 1 to 11, or implements the steps of the transmission configuration method as described in any one of claims 12 to 19.

23. A readable storage medium, wherein: The readable storage medium stores a program or instruction, and when the program or instruction is executed by the processor, it implements the steps of the transmission configuration method as described in any one of claims 1 to 11, or implements the steps of the transmission configuration method as described in any one of claims 12 to 19.

24. A chip, wherein: The chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the steps of the transmission configuration method as described in any one of claims 1 to 11, or to implement the steps of the transmission configuration method as described in any one of claims 12 to 19.

Images