Method and device for determining relay load configuration, equipment and storage medium

CN119014032APending Publication Date: 2024-11-22GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202280094509.X
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2022-07-19
Publication Date
2024-11-22

AI Technical Summary

Technical Problem

The relay terminal cannot obtain the relay bearer configuration directly from the Sidelink Relay Adaptation Protocol (SRAP) message, resulting in the inability to determine the relay bearer configuration for U2U relay transmission.

Method used

By receiving the SRAP message, the first terminal determines the target relay transfer configuration in the candidate relay transfer configuration list based on the information in the message, thereby realizing U2U relay transmission.

Benefits of technology

The relay transmission configuration determination of U2U relay transmission is realized, which solves the problem that the relay terminal cannot directly determine the configuration required for relay transmission, and improves the efficiency and reliability of U2U communication.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119014032A_ABST
    Figure CN119014032A_ABST
Patent Text Reader

Abstract

The invention discloses a relay bearer configuration determination method and device, equipment and a storage medium, and relates to the technical field of communication. The method is executed by a first terminal, and the method comprises the following steps: receiving a sideline relay adaptation protocol (SRAP) message; and determining a target relay bearer configuration in a candidate relay bearer configuration list based on the SRAP message. In the embodiment of the invention, after the first terminal receives the SRAP message, the target relay bearer configuration is determined in the candidate relay bearer configuration list according to the information carried in the SRAP message, so that the terminal-to-terminal relay transmission is realized.
Need to check novelty before this filing date? Find Prior Art

Description

Method, device, equipment and storage medium for determining intermediate load configuration Technical Field

[0001] The embodiments of the present application relate to the field of communication technology, and in particular to a method, apparatus, device, and storage medium for determining relay bearer configuration. Background Art

[0002] U2U (UE-to-UE) communication is a sidelink technology that allows near-field communication between user equipment (UE) devices via a PC5 interface. U2U relaying uses a relay UE (relay user equipment) to relay data between a source UE and a remote UE, enabling communication between the source and remote UEs.

[0003] 3GPP defines two U2U transmission modes. In Mode A, the base station allocates resources for data transmission on the sidelink, while in Mode B, the source terminal / remote terminal selects a resource from the resource pool for data transmission on the sidelink.

[0004] However, in the U2U relay transmission mode, the relay terminal cannot directly obtain the relay bearer configuration from the Sidelink Relay Adaptation Protocol (SRAP) message. How to determine the relay bearer configuration and thus implement U2U relay is a problem that needs to be solved.

[0005] Summary of the Invention

[0006] The present invention provides a method, apparatus, device, and storage medium for determining a relay bearer configuration. The technical solution is as follows:

[0007] According to one aspect of an embodiment of the present application, a method for determining a relay bearer configuration is provided, the method being performed by a first terminal, the method including:

[0008] Receive Sideline Relay Adaptation Protocol (SRAP) messages;

[0009] A target intermediate bearer configuration is determined in a candidate intermediate bearer configuration list based on the SRAP message.

[0010] According to one aspect of an embodiment of the present application, a device for determining a relay bearer configuration is provided, the device comprising: a receiving module and a determining module;

[0011] The receiving module is used to receive the Sidelink Relay Adaptation Protocol (SRAP) message;

[0012] The determining module determines the target intermediate bearer configuration in the candidate intermediate bearer configuration list based on the SRAP message.

[0013] According to one aspect of an embodiment of the present application, a terminal device is provided, the terminal device including a transceiver and a processor connected to the transceiver;

[0014] The transceiver is used to receive Sidelink Relay Adaptation Protocol (SRAP) messages;

[0015] The processor is configured to determine a target intermediate bearer configuration in a candidate intermediate bearer configuration list based on the SRAP message.

[0016] According to one aspect of an embodiment of the present application, a computer-readable storage medium is provided, in which a computer program is stored. The computer program is used for execution by a processor to implement the above-mentioned method for determining the intermediate load configuration.

[0017] According to one aspect of an embodiment of the present application, a chip is provided, which includes a programmable logic circuit and / or program instructions. When the chip is running, it is used to implement the above-mentioned method for determining the intermediate load configuration.

[0018] According to one aspect of an embodiment of the present application, a computer program product or computer program is provided, wherein the computer program product or computer program includes computer instructions, the computer instructions are stored in a computer-readable storage medium, and a processor reads and executes the computer instructions from the computer-readable storage medium to implement the above-mentioned method for determining the intermediate load configuration.

[0019] The technical solutions provided in the embodiments of the present application can bring the following beneficial effects:

[0020] By receiving the SRAP message, the first terminal determines the target relay bearer configuration for U2U relay transmission in the candidate relay bearer configuration list based on the information carried in the SRAP message, thereby realizing U2U relay transmission. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0022] FIG1 is a schematic diagram of a communication system provided by an embodiment of the present application;

[0023] FIG2 is a flowchart of a method for determining a relay load configuration according to an embodiment of the present application;

[0024] FIG3 is a flowchart of a method for determining a relay load configuration according to an embodiment of the present application;

[0025] FIG4 is a flowchart of a method for determining a relay load configuration according to an embodiment of the present application;

[0026] FIG5 is a schematic diagram of a serialization rule for generating a U2U bearer configuration sequence provided by one embodiment of the present application;

[0027] FIG6 is a structural block diagram of an apparatus for intermediate load configuration provided by an embodiment of the present application;

[0028] FIG7 is a schematic diagram of the structure of a terminal device provided in one embodiment of the present application. DETAILED DESCRIPTION

[0029] In order to make the objectives, technical solutions and advantages of this application clearer, the implementation methods of this application will be further described in detail below with reference to the accompanying drawings.

[0030] The network architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application. A person skilled in the art will appreciate that, with the evolution of the network architecture and the emergence of new business scenarios, the technical solutions provided by the embodiments of the present application are equally applicable to similar technical problems.

[0031] Please refer to FIG. 1 , which shows a block diagram of a communication system provided by an exemplary embodiment of the present application. The communication system may include: a remote terminal 10 , a relay terminal 20 and a network device 30 .

[0032] The remote terminal 10 refers to a terminal device that performs sidelink communication with the relay terminal 20 and can then communicate with other remote terminals 10 or network devices 30 via the relay of the relay terminal 20. The two remote terminals 10 that perform sidelink communication via the relay terminal 20 can be respectively referred to as the source terminal and the remote terminal. For example, the source terminal transmits data to the remote terminal via the relay terminal 20, or vice versa. There are usually multiple remote terminals 10, and one or more remote terminals 10 can be distributed in the cell managed by each network device 30. The remote terminal 10 can include various handheld devices with wireless communication functions, vehicle-mounted devices, wearable devices, computing devices or other processing devices connected to a wireless modem, as well as various forms of user equipment, mobile stations (MS), etc. For the convenience of description, the above-mentioned devices are collectively referred to as remote terminals.

[0033] The relay terminal 20 is a terminal device capable of sidelink communication with the remote terminal 10. There are typically multiple relay terminals 20, with one or more relay terminals 20 distributed within each cell managed by the network device 30. Relay terminals 20 can include various wireless communication-capable handheld devices, vehicle-mounted devices, wearable devices, computing devices, or other processing devices connected to a wireless modem, as well as various user equipment and mobile stations (MSs). For ease of description, the aforementioned devices are collectively referred to as relay terminals.

[0034] The network device 30 is a device used to provide wireless communication functions for the remote terminal 10 and the relay terminal 20. The network device 30 may include various forms of macro base stations, micro base stations, relay stations, access points, etc. In systems using different wireless access technologies, the name of the network device 30 may vary. For example, in the 5G NR system, it is called a 5G base station (5G Node B, gNodeB / gNB).

[0035] The remote terminal 10 and relay terminal 20 establish a connection via a sidelink, enabling communication via a direct communication interface (such as a PC5 interface). The relay terminal 20 can broadcast network device messages to the remote terminal 10 via the sidelink, thus implementing network relay. Direct communication and data transmission between the remote terminal 10 and relay terminal 20 via the sidelink differs from traditional cellular systems, where communication data is received or sent via network devices. This transmission process offers low latency and minimal overhead, making it suitable for communication between geographically close terminals (such as an in-vehicle device and other nearby peripheral devices). Network device 30 and relay terminal 20 communicate via an over-the-air technology, such as the Uu interface.

[0036] In an embodiment of the present application, the terminal device (including the remote terminal 10 and the relay terminal 20) supports broadcasting discovery messages so that other terminal devices can discover themselves by receiving the discovery messages.

[0037] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Global System of Mobile Communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (TDD) system, Advanced Long Term Evolution (LTE-A) system, New Radio (NR) system, NR system evolution system, LTE-based access to Unlicensed spectrum (LTE-U) system, NR-U system, Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication system, Wireless Local Area Network (WLAN) system, Networks, WLAN), Wireless Fidelity (WiFi), next generation communication systems or other communication systems, etc.

[0038] Generally speaking, traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communications, but will also support, for example, device-to-device (D2D) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), vehicle-to-vehicle (V2V) communication, and vehicle-to-everything (V2X) systems. The embodiments of the present application can also be applied to these communication systems.

[0039] In Layer 2 U2U relay, the relay terminal performs Quality of Service (QoS) segmentation for the remote terminal. After the remote terminal transmits data to the relay terminal according to the segmented QoS, the relay terminal cannot directly determine the remote terminal's specific relay bearer configuration based on the information carried in the SRAP message subheader. Therefore, the relay terminal cannot determine the relay bearer configuration required for relay transmission.

[0040] In order to solve the above problems, the technical solution of the present application associates the information carried in the SRAP message with the relay bearer configuration used for U2U relay transmission. The first terminal determines the target relay bearer configuration for relay transmission based on the received SRAP message to realize U2U relay transmission.

[0041] In the embodiment of the present application, layer 2 relay refers to a relay method that implements relay through the access stratum (AS) of the relay terminal.

[0042] The technical solution of this application is introduced and explained through several embodiments below.

[0043] Please refer to Figure 2, which shows a flow chart of a method for determining a relay bearer configuration according to one embodiment of the present application. The method is executed by a first terminal, which may be the relay terminal 20 or the remote terminal 10 in the communication system shown in Figure 1. The method may include the following steps:

[0044] Step 220: Receive SRAP message;

[0045] Optionally, the SRAP message carries a bearer identifier ID (bearer IDitifier); or a QoS flow ID.

[0046] Optionally, the information carried in the header of the SRAP message includes UE ID, bearer ID, QoS flow ID, data / control identifier (D / C), etc. This application does not impose any limitation on this.

[0047] Optionally, a bearer is used to transmit data. A terminal can transmit data through multiple bearers, and different bearers are identified by bearer IDs.

[0048] Optionally, the QoS flow ID or the QoS flow ID list is carried in at least one of the following protocol layer subheaders: SRAP layer; Radio Link Control (RLC) layer; Media Access Control (MAC) layer.

[0049] Step 240: Determine the target intermediate bearer configuration in the candidate intermediate bearer configuration list based on the SRAP message.

[0050] In some embodiments, the SRAP message carries a bearer ID, and the target intermediate bearer configuration is determined based on the bearer ID in the candidate intermediate bearer configuration list; in other embodiments, the SRAP message carries a QoS flow ID, and the target intermediate bearer configuration is determined based on the QoS flow ID in the candidate intermediate bearer configuration list.

[0051] Optionally, the bearer ID is carried in a header of the SRAP message, and the target intermediate bearer configuration is determined in the candidate intermediate bearer configuration list based on the bearer ID carried in the SRAP header.

[0052] Optionally, the QoS flow ID is carried in a header of the SRAP message, and the target relay bearer configuration is determined in the candidate relay bearer configuration list based on the QoS flow ID carried in the SRAP header.

[0053] Exemplarily, the candidate successor bearer configuration list includes at least two candidate successor bearer configurations.

[0054] Exemplarily, the candidate successor bearer configurations in the candidate successor bearer configuration list include at least one of the following configurations: data bearer configuration of sidelink data radio bearer (SL-DRB); the correspondence between the bearer ID corresponding to the data bearer configuration and the first information; RLC bearer configuration of SL-DRB; the correspondence between the bearer ID corresponding to the RLC bearer configuration and the first information; wherein the first information includes at least one of QoS flow, QoS flow list, RLC bearer configuration index, and associated bearer configuration index.

[0055] Exemplarily, the aforementioned data bearer configuration includes at least one of the following: relevant configuration of the Service Data Adaptation Protocol (SDAP) layer; relevant configuration of the Packet Data Convergence Protocol (PDCP) layer; and a data bearer configuration index.

[0056] Exemplarily, the aforementioned RLC bearer configuration includes at least one of the following: relevant configuration of the SRAP layer; relevant configuration of the RLC layer; relevant configuration of the MAC layer; RLC bearer configuration index; associated bearer configuration index.

[0057] Optionally, the data bearer configuration of SL-DRB includes relevant configurations of the SDAP layer / PDCP layer, and the RLC bearer configuration includes relevant configurations of the SRAP layer / MAC layer / RLC layer; the aforementioned associated bearer configuration index is a bearer configuration index that associates the SDAP layer / PDCP layer with the SRAP layer / MAC layer / RLC layer, that is, a complete set of bearer configurations of the protocol stack is associated through the associated bearer configuration index.

[0058] In some embodiments, before step 240 , the method further includes the step of obtaining a candidate successor load configuration list.

[0059] Exemplarily, obtaining the candidate successor bearer configuration list includes at least one of the following methods: obtaining the candidate successor bearer configuration list through pre-configuration; obtaining the candidate successor bearer configuration list by receiving system broadcast messages; obtaining the candidate successor bearer configuration list by receiving Radio Resource Control (RRC) dedicated signaling; obtaining the candidate successor bearer configuration list by receiving a message sent by the second terminal.

[0060] Exemplarily, obtaining the candidate successor bearer configuration list includes at least one of the following methods: when the first terminal is outside the network coverage, obtaining the candidate successor bearer configuration list through pre-configuration; when the first terminal is within the network coverage and the RRC is in an idle state, obtaining the candidate successor bearer configuration list by receiving a system broadcast message; when the first terminal is within the network coverage and the RRC is in an inactive state, obtaining the candidate successor bearer configuration list by receiving a system broadcast message; when the first terminal is within the network coverage and the RRC is in a connected state, obtaining the candidate successor bearer configuration list by receiving RRC-specific signaling; obtaining the candidate successor bearer configuration list by receiving a PC5-RRC message or a sidelink media access control control element (SideLink Media Access Control Control Element, SL-MAC CE) or sidelink control information (Sidelink Control Information, SCI) sent by the second terminal.

[0061] The second terminal is a counterpart terminal of the first terminal.

[0062] In the embodiment of the present application, the second terminal device can be a remote terminal or a relay terminal. The meanings of the remote terminal and the relay terminal can be referred to the embodiment shown in FIG1 and will not be described in detail here.

[0063] Optionally, the first terminal is a source terminal or a remote terminal, and the second terminal is a relay terminal; or the first terminal is a relay terminal, and the second terminal is a source terminal or a remote terminal. That is, relay bearer configuration can be performed from the source terminal / remote terminal to the relay terminal, or from the relay terminal to the source terminal / remote terminal.

[0064] Optionally, a first candidate relay bearer configuration list corresponding to the relay service of the first terminal is obtained, where the candidate relay bearer configurations in the first candidate relay bearer configuration list include a relay indication; and / or a second candidate relay bearer configuration list corresponding to the non-relay service of the first terminal is obtained, where the candidate relay bearer configurations in the second candidate relay bearer configuration list include a non-relay indication. That is, candidate relay bearer configuration lists can be obtained separately for the relay service and non-relay service of the first terminal.

[0065] To sum up, the technical solution provided in the embodiment of the present application determines the target relay bearer configuration for relay transmission in the candidate relay bearer configuration list through the information carried in the SRAP message; and realizes U2U relay transmission by establishing an association mechanism between the information carried in the SRAP message and the target relay bearer configuration.

[0066] In an optional embodiment based on Figure 2, the information carried in the SRAP message may be a bearer ID or a QoS flow ID. The following provides exemplary descriptions of the two types of information that may be carried in the aforementioned SRAP message.

[0067] 1) The SRAP message carries a bearer ID.

[0068] Figure 3 shows a flowchart of a method for determining a relay bearer configuration according to one embodiment of the present application. This method can be applied to the communication system shown in Figure 1 and executed by a first terminal, which can be relay terminal 20 or remote terminal 10 in the communication system shown in Figure 1. The method may include the following steps:

[0069] Step 320: Receive SRAP message;

[0070] Exemplarily, the first terminal receives an SRAP message, wherein the SRAP message carries a bearer ID, and the bearer ID is used to indicate a bearer used when the second terminal transmits data to the first terminal.

[0071] Optionally, the bearer ID is carried in a header of the SRAP message.

[0072] The second terminal is a counterpart terminal of the first terminal.

[0073] In the embodiment of the present application, the second terminal device can be a remote terminal or a relay terminal. The meanings of the remote terminal and the relay terminal can be referred to the embodiment shown in FIG1 and will not be described in detail here.

[0074] Step 322: Obtain a candidate successor load configuration list;

[0075] Exemplarily, the candidate successor bearer configuration list includes at least two candidate successor bearer configurations.

[0076] The candidate successor load configuration in the candidate successor load configuration list includes at least one of the following three configurations:

[0077] (1) Configuration 1: SL-DRB data bearer configuration;

[0078] Exemplarily, the data bearer configuration includes at least one of the following:

[0079] SDAP layer configuration;

[0080] PDCP layer configuration;

[0081] Data bearer configuration index.

[0082] Optionally, the length of the data bearer configuration index is 512 bits.

[0083] (2) Configuration 2: RLC bearer configuration for SL-DRB;

[0084] Exemplarily, the RLC bearer configuration includes at least one of the following:

[0085] SRAP layer configuration;

[0086] RLC layer configuration;

[0087] MAC layer configuration;

[0088] RLC bearer configuration index;

[0089] The associated bearer configuration index.

[0090] Optionally, the data bearer configuration of SL-DRB includes relevant configurations of the SDAP layer / PDCP layer, and the RLC bearer configuration includes relevant configurations of the SRAP layer / MAC layer / RLC layer; the aforementioned associated bearer configuration index is a bearer configuration index that associates the SDAP layer / PDCP layer with the SRAP layer / MAC layer / RLC layer, that is, a complete set of bearer configurations of the protocol stack is associated through the associated bearer configuration index.

[0091] (3) Configuration 3: a correspondence between a bearer ID corresponding to a data bearer configuration and the first information; or a correspondence between a bearer ID corresponding to an RLC bearer configuration and the first information.

[0092] Optionally, the first information includes at least one of a QoS flow, a QoS flow list, an RLC bearer configuration index, and an associated bearer configuration index.

[0093] Optionally, the bearer ID corresponding to the data bearer configuration is a signaling radio bearer (SRB) ID or a data radio bearer (DRB) ID.

[0094] It should be noted that the first terminal may obtain any one of the above three configurations, or any combination of the above three configurations, which is not limited in this application.

[0095] Optionally, obtaining the candidate successor bearer configuration list includes at least one of the following methods: obtaining the candidate successor bearer configuration list through pre-configuration; obtaining the candidate successor bearer configuration list by receiving system broadcast messages; obtaining the candidate successor bearer configuration list by receiving RRC proprietary signaling; obtaining the candidate successor bearer configuration list by receiving a message sent by the second terminal.

[0096] Furthermore, obtaining the candidate successor load configuration list includes at least one of the following methods:

[0097] When the first terminal is out of network coverage, a candidate inheritor bearer configuration list is obtained through pre-configuration;

[0098] When the first terminal is within network coverage and in RRC idle state, obtain a candidate inheritor bearer configuration list by receiving a system broadcast message;

[0099] When the first terminal is within network coverage and RRC is in an inactive state, obtaining a candidate inheritor bearer configuration list by receiving a system broadcast message;

[0100] When the first terminal is within network coverage and in an RRC connected state, obtaining a candidate inheritor bearer configuration list by receiving RRC dedicated signaling;

[0101] Obtain a candidate inheritor bearer configuration list by receiving a PC5-RRC message, SL-MAC CE, or SCI sent by the second terminal.

[0102] The second terminal is a counterpart terminal of the first terminal.

[0103] In the embodiment of the present application, the second terminal device can be a remote terminal or a relay terminal. The meanings of the remote terminal and the relay terminal can be referred to the embodiment shown in FIG1 and will not be described in detail here.

[0104] That is, the first terminal is the source terminal or the remote terminal, and the second terminal is the relay terminal; or the first terminal is the relay terminal, and the second terminal is the source terminal or the remote terminal. In other words, relay bearer configuration can be performed from the source terminal / remote terminal to the relay terminal, or from the relay terminal to the source terminal / remote terminal.

[0105] It should be noted that in terminal-to-terminal relay transmission, the three candidate relay bearer configurations described above can be combined in any combination. For example, when a source terminal transmits data to a remote terminal via a relay terminal, the source terminal may use Configuration 1 when performing relay bearer configuration on the relay terminal, and a combination of Configuration 1 and Configuration 3 when performing relay bearer configuration on the remote terminal, and so on. This application does not impose any restrictions on this.

[0106] Optionally, the first terminal obtains a candidate intermediate carrier configuration list by receiving a PC5-RRC message / SL-MAC CE / SCI sent by the second terminal. When the first terminal is in an RRC connected state, the candidate intermediate carrier configuration in the candidate intermediate carrier configuration list can be reported to the network side. The network side can reject the candidate intermediate carrier configuration reported by the first terminal. When the second terminal receives the configuration rejection information from the network side, the second terminal can send a configuration rejection information to the first terminal, or send a reconfiguration request to the first terminal.

[0107] Optionally, a first candidate relay bearer configuration list corresponding to the relay service of the first terminal is obtained, where the candidate relay bearer configurations in the first candidate relay bearer configuration list include a relay indication; and / or a second candidate relay bearer configuration list corresponding to the non-relay service of the first terminal is obtained, where the candidate relay bearer configurations in the second candidate relay bearer configuration list include a non-relay indication. That is, candidate relay bearer configuration lists can be obtained separately for the relay service and non-relay service of the first terminal.

[0108] It should be noted that the execution order of the above steps 320 and 322 is not specific, and step 320 can be executed first and then step 322; or step 322 can be executed first and then step 320; or step 320 and step 322 can be executed simultaneously. This application does not impose any restrictions on this.

[0109] Step 340: Determine the target intermediate bearer configuration in the candidate intermediate bearer configuration list based on the bearer ID.

[0110] Exemplarily, the candidate intermediate bearer configuration list includes a bearer ID and specific intermediate bearer configuration information corresponding to the bearer ID. The first terminal determines a target intermediate bearer configuration from the candidate intermediate bearer configuration list based on the bearer ID carried in the SRAP message. That is, the target intermediate bearer configuration is the intermediate bearer configuration corresponding to the bearer ID carried in the SRAP message.

[0111] Furthermore, the first terminal performs U2U relay transmission based on the target relay bearer configuration.

[0112] In summary, the technical solution provided in this embodiment determines the target relay bearer configuration in the candidate relay bearer configuration list obtained by the first terminal through the bearer ID carried in the SRAP message, thereby realizing U2U relay transmission.

[0113] 2) The SRAP message carries the QoS flow ID.

[0114] Figure 4 shows a flowchart of a method for determining a relay bearer configuration according to one embodiment of the present application. This method can be applied to the communication system shown in Figure 1 and executed by a first terminal, which can be a relay terminal 20 or a remote terminal 10 in the communication system shown in Figure 1. The method may include the following steps:

[0115] Step 420: Receive SRAP message;

[0116] Exemplarily, the first terminal receives an SRAP message, wherein the SRAP message carries a QoS flow ID corresponding to a bearer used when the second terminal transmits data to the first terminal.

[0117] Optionally, the QoS flow ID or the QoS flow ID list is carried in a header of the SRAP message.

[0118] Optionally, the QoS flow ID or the QoS flow ID list is carried in at least one of the following protocol layer subheaders: SRAP layer; RLC layer; MAC layer.

[0119] The second terminal is a counterpart terminal of the first terminal.

[0120] In the embodiment of the present application, the second terminal device can be a remote terminal or a relay terminal. The meanings of the remote terminal and the relay terminal can be referred to the embodiment shown in FIG1 and will not be described in detail here.

[0121] Step 422: Obtain a candidate successor load configuration list;

[0122] Exemplarily, the candidate successor bearer configuration list includes at least two candidate successor bearer configurations.

[0123] In some embodiments, the candidate intermediate bearer configuration in the candidate intermediate bearer configuration list includes at least one of the following three configurations:

[0124] (1) Configuration 1: SL-DRB data bearer configuration;

[0125] Exemplarily, the data bearer configuration includes at least one of the following:

[0126] SDAP layer configuration;

[0127] PDCP layer configuration;

[0128] Data bearer configuration index.

[0129] Optionally, the length of the data bearer configuration index is 512 bits.

[0130] (2) Configuration 2: RLC bearer configuration for SL-DRB;

[0131] Exemplarily, the RLC bearer configuration includes at least one of the following:

[0132] SRAP layer configuration;

[0133] RLC layer configuration;

[0134] MAC layer configuration;

[0135] RLC bearer configuration index;

[0136] The associated bearer configuration index.

[0137] Optionally, the data bearer configuration of SL-DRB includes relevant configurations of the SDAP layer / PDCP layer, and the RLC bearer configuration includes relevant configurations of the SRAP layer / MAC layer / RLC layer; the aforementioned associated bearer configuration index is a bearer configuration index that associates the SDAP layer / PDCP layer with the SRAP layer / MAC layer / RLC layer, that is, a complete set of bearer configurations of the protocol stack is associated through the associated bearer configuration index.

[0138] (3) Configuration 3: a correspondence between a bearer ID corresponding to a data bearer configuration and the first information; or a correspondence between a bearer ID corresponding to an RLC bearer configuration and the first information;

[0139] Optionally, the first information includes at least one of a QoS flow, a QoS flow list, an RLC bearer configuration index, and an associated bearer configuration index.

[0140] Optionally, the bearer ID corresponding to the data bearer configuration is a signaling radio bearer (SRB) ID or a data radio bearer (DRB) ID.

[0141] It should be noted that the first terminal may obtain any one of the above three configurations, or any combination of the above three configurations, which is not limited in this application.

[0142] Optionally, obtaining the candidate successor bearer configuration list includes at least one of the following methods: obtaining the candidate successor bearer configuration list through pre-configuration; obtaining the candidate successor bearer configuration list by receiving system broadcast messages; obtaining the candidate successor bearer configuration list by receiving RRC proprietary signaling; obtaining the candidate successor bearer configuration list by receiving a message sent by the second terminal.

[0143] Exemplarily, obtaining the candidate successor load configuration list includes at least one of the following methods:

[0144] When the first terminal is out of network coverage, a candidate inheritor bearer configuration list is obtained through pre-configuration;

[0145] When the first terminal is within network coverage and in RRC idle state, obtain a candidate inheritor bearer configuration list by receiving a system broadcast message;

[0146] When the first terminal is within network coverage and RRC is in an inactive state, obtaining a candidate inheritor bearer configuration list by receiving a system broadcast message;

[0147] When the first terminal is within network coverage and in an RRC connected state, obtaining a candidate inheritor bearer configuration list by receiving RRC dedicated signaling;

[0148] Obtain a candidate inheritor bearer configuration list by receiving a PC5-RRC message, SL-MAC CE, or SCI sent by the second terminal.

[0149] The second terminal is a counterpart terminal of the first terminal.

[0150] In the embodiment of the present application, the second terminal device can be a remote terminal or a relay terminal. The meanings of the remote terminal and the relay terminal can be referred to the embodiment shown in FIG1 and will not be described in detail here.

[0151] That is, the first terminal is the source terminal or the remote terminal, and the second terminal is the relay terminal; or the first terminal is the relay terminal, and the second terminal is the source terminal or the remote terminal. In other words, relay bearer configuration can be performed from the source terminal / remote terminal to the relay terminal, or from the relay terminal to the source terminal / remote terminal.

[0152] Optionally, the first terminal obtains a candidate intermediate carrier configuration list by receiving a PC5-RRC message / SL-MAC CE / SCI sent by the second terminal. When the first terminal is in an RRC connected state, the candidate intermediate carrier configuration in the candidate intermediate carrier configuration list can be reported to the network side. The network side can reject the candidate intermediate carrier configuration reported by the first terminal. When the second terminal receives the configuration rejection information from the network side, the second terminal can send a configuration rejection information to the first terminal, or send a reconfiguration request to the first terminal.

[0153] Optionally, a first candidate relay bearer configuration list corresponding to the relay service of the first terminal is obtained, where the candidate relay bearer configurations in the first candidate relay bearer configuration list include a relay indication; and / or a second candidate relay bearer configuration list corresponding to the non-relay service of the first terminal is obtained, where the candidate relay bearer configurations in the second candidate relay bearer configuration list include a non-relay indication. That is, candidate relay bearer configuration lists can be obtained separately for the relay service and non-relay service of the first terminal.

[0154] In some embodiments, the second terminal generates a U2U bearer configuration sequence based on the QoS flow ID and the RLC bearer configuration. That is, the U2U bearer configuration sequence is a terminal-to-terminal bearer configuration sequence generated by the second terminal based on the QoS flow ID and the RLC bearer configuration sequence.

[0155] Exemplarily, the second terminal further serializes the QoS flow ID and the RLC bearer configuration sequence to generate a U2U bearer configuration sequence. The serialization rule is to combine the QoS flow ID with the RLC bearer configuration corresponding to the QoS flow ID to generate a U2U bearer configuration sequence, wherein the number of the U2U bearer configuration sequence corresponds to the QoS flow ID one-to-one.

[0156] Figure 5 shows a schematic diagram of the serialization rules for generating a U2U bearer configuration sequence. As shown, QoS flow ID 1, QoS flow ID 2, and QoS flow ID 3 correspond to RLC bearer configuration 1; QoS flow ID 4, QoS flow ID 5, and QoS flow ID 6 correspond to RLC bearer configuration 2; and QoS flow ID 7 and QoS flow ID 8 correspond to RLC bearer configuration 3. This application does not limit the manner in which QoS flow IDs correspond to RLC bearer configurations.

[0157] The serialization process is such that, for example, QoS flow ID 1 is combined with the corresponding RLC bearer configuration 1 to generate U2U bearer configuration 1; for another example, QoS flow ID 2 is combined with the corresponding RLC bearer configuration 1 to generate U2U bearer configuration 2; for another example, QoS flow ID 4 is combined with the corresponding RLC bearer configuration 2 to generate U2U bearer configuration 4, and so on.

[0158] Optionally, the U2U bearer configuration sequence is carried in at least one of the following protocol layer subheaders: SRAP layer; RLC layer; MAC layer.

[0159] It should be noted that the execution order of the above steps 420 and 422 is not specific, and step 420 may be executed first and then step 422; or step 422 may be executed first and then step 420; or step 420 and step 422 may be executed simultaneously. This application does not impose any limitation on this.

[0160] Step 440: Determine the target intermediate bearer configuration in the candidate intermediate bearer configuration list based on the QoS flow ID.

[0161] Exemplarily, the candidate relay bearer configuration list includes candidate relay bearers and specific relay bearer configuration information corresponding to the candidate relay bearers. The first terminal determines the target relay bearer configuration in the candidate relay bearer configuration list based on the QoS flow ID corresponding to the relay bearer used for the current relay transmission and carried in the SRAP message.

[0162] Furthermore, the first terminal performs U2U relay transmission based on the target relay bearer configuration.

[0163] Optionally, when the second terminal generates a U2U bearer configuration sequence based on the QoS flow ID and the RLC bearer configuration, the target intermediate bearer configuration is determined based on the QoS flow ID and the U2U bearer configuration sequence. For example, referring to Figure 5 , when the QoS flow ID indicates QoS flow ID 5, i.e., corresponding to U2U bearer configuration 5, the first terminal determines RLC bearer configuration 2 corresponding to U2U bearer configuration 5 as the target intermediate bearer configuration.

[0164] It should be noted that in terminal-to-terminal relay transmission, the aforementioned candidate relay bearer configuration list can be generated through any combination. For example, in the process of transmitting data from the source terminal to the remote terminal via the relay terminal, the source terminal uses the above configuration 1 when performing relay bearer configuration to the relay terminal, and the relay terminal uses the combination of the above configuration 1, configuration 2 and configuration 3 when performing relay bearer configuration to the remote terminal; for another example, the source terminal uses the above configuration 2 when performing relay bearer configuration to the relay terminal, and the relay terminal uses the above U2U bearer configuration sequence when performing relay bearer configuration to the remote terminal; for another example, the source terminal uses the above U2U bearer configuration sequence when performing relay bearer configuration to the relay terminal and when the relay terminal performs relay bearer configuration to the remote terminal, and so on. This application does not impose any restrictions on this.

[0165] In summary, the technical solution provided in this embodiment determines the target relay bearer configuration in the candidate relay bearer configuration list obtained by the first terminal through the QoS flow ID carried in the SRAP message, thereby realizing U2U relay transmission.

[0166] The following are device embodiments of the present application, which can be used to implement the method embodiments of the present application. For details not disclosed in the device embodiments of the present application, please refer to the method embodiments of the present application.

[0167] Figure 6 shows a block diagram of a device for determining a relay bearer configuration according to one embodiment of the present application. The device has the function of implementing the method example of the first terminal described above. The function can be implemented by hardware or by hardware executing corresponding software. The device can be the first terminal described above or can be set in the first terminal. As shown in Figure 6, the device can include the following modules:

[0168] The receiving module 520 is configured to receive a Sidelink Relay Adaptation Protocol (SRAP) message;

[0169] The determination module 540 is configured to determine a target intermediate bearer configuration in the candidate intermediate bearer configuration list based on the SRAP message.

[0170] In an optional embodiment, the SRAP message carries: a bearer identifier ID; or a quality of service QoS flow ID.

[0171] In an optional embodiment, the target intermediate bearer configuration is determined in the candidate intermediate bearer configuration list based on the bearer ID.

[0172] In an optional embodiment, the target relay bearer configuration is determined in the candidate relay bearer configuration list based on the QoS flow ID.

[0173] In an optional embodiment, the receiving module 520 is further configured to obtain a candidate successor bearer configuration list.

[0174] In an optional embodiment, the candidate successor bearer configuration in the candidate successor bearer configuration list includes at least one of the following configurations: data bearer configuration of the sidelink data radio bearer SL-DRB; the correspondence between the bearer ID corresponding to the data bearer configuration and the first information; the radio link control RLC bearer configuration of the SL-DRB; the correspondence between the bearer ID corresponding to the RLC bearer configuration and the first information; wherein the first information includes at least one of QoS flow, QoS flow list, RLC bearer configuration index, and associated bearer configuration index.

[0175] In an optional embodiment, the data bearer configuration includes at least one of the following: relevant configuration of the Service Data Adaptation Protocol (SDAP) layer; relevant configuration of the Packet Data Convergence Protocol (PDCP) layer; and a data bearer configuration index.

[0176] In an optional embodiment, the RLC bearer configuration includes at least one of the following: relevant configuration of the SRAP layer; relevant configuration of the RLC layer; relevant configuration of the media access control MAC layer; the RLC bearer configuration index; the associated bearer configuration index.

[0177] In an optional embodiment, the receiving module 520 is also used for at least one of the following: obtaining the candidate successor bearer configuration list through pre-configuration; obtaining the candidate successor bearer configuration list by receiving a system broadcast message; obtaining the candidate successor bearer configuration list by receiving RRC dedicated signaling; obtaining the candidate successor bearer configuration list by receiving a message sent by the second terminal.

[0178] In an optional embodiment, the receiving module 520 is also used for at least one of the following: when the first terminal is outside the network coverage, obtaining the candidate successor bearer configuration list through pre-configuration; when the first terminal is within the network coverage and the wireless resource control RRC is in an idle state, obtaining the candidate successor bearer configuration list by receiving a system broadcast message; when the first terminal is within the network coverage and the wireless resource control RRC is in an inactive state, obtaining the candidate successor bearer configuration list by receiving a system broadcast message; when the first terminal is within the network coverage and the wireless resource control RRC is in a connected state, obtaining the candidate successor bearer configuration list by receiving RRC-specific signaling; obtaining the candidate successor bearer configuration list by receiving a PC5-RRC message or a sidelink media access control control unit SL-MAC CE or a sidelink control information SCI sent by the second terminal.

[0179] In an optional embodiment, the first terminal is a source terminal or a remote terminal, and the second terminal is a relay terminal; or, the first terminal is a relay terminal, and the second terminal is a source terminal or a remote terminal.

[0180] In an optional embodiment, the receiving module 520 is further used to obtain a first candidate relay bearer configuration list corresponding to the relay service of the first terminal, the first candidate relay bearer configuration list including a relay indication; and / or, to obtain a second candidate relay bearer configuration list corresponding to the non-relay service of the first terminal, the second candidate relay bearer configuration list including a non-relay indication.

[0181] In an optional embodiment, the QoS flow ID is carried in at least one of the following protocol layer subheaders: SRAP layer; RLC layer; MAC layer.

[0182] In an optional embodiment, the target intermediate carrier configuration is determined based on the QoS flow ID and the terminal-to-terminal U2U bearer configuration sequence, and the U2U bearer configuration sequence is a terminal-to-terminal bearer configuration sequence generated by the second terminal based on the QoS flow ID and the RLC bearer configuration sequence.

[0183] In an optional embodiment, the U2U bearer configuration sequence is carried in at least one of the following protocol layer subheaders: SRAP layer; RLC layer; MAC layer.

[0184] It should be noted that the device provided in the above embodiment only uses the division of the above-mentioned functional modules as an example to implement its functions. In actual applications, the above-mentioned functions can be assigned to different functional modules according to actual needs, that is, the content structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0185] Regarding the apparatus in the above embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be elaborated here.

[0186] Please refer to Figure 7, which shows a schematic diagram of the structure of a terminal device provided by an embodiment of the present application. The terminal device may include: a processor 801, a receiver 802, a transmitter 803, a memory 804 and a bus 805.

[0187] The processor 801 includes one or more processing cores. The processor 801 executes various functional applications and information processing by running software programs and modules.

[0188] The receiver 802 and the transmitter 803 may be implemented as a transceiver 806 , which may be a communication chip.

[0189] The memory 804 is connected to the processor 801 via a bus 805 .

[0190] The memory 804 may be used to store a computer program, and the processor 801 may be used to execute the computer program to implement the various steps performed by the terminal device in the above method embodiment.

[0191] In addition, the memory 804 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, including but not limited to: RAM (Random-Access Memory) and ROM (Read-Only Memory), EPROM (Erasable Programmable Read-Only Memory), EEPROM (Electrically Erasable Programmable Read-Only Memory), flash memory or other solid-state storage technology, CD-ROM (Compact Disc Read-Only Memory), DVD (Digital Video Disc) or other optical storage, tape cassettes, magnetic tape, disk storage or other magnetic storage devices.

[0192] Among them, when the terminal device is implemented as a first terminal device, the processor and transceiver involved in the embodiment of the present application can execute the steps performed by the first terminal in any of the methods shown in Figures 2 to 4 above, which will not be repeated here.

[0193] In a possible implementation, when the terminal device is implemented as a first terminal device,

[0194] The receiver 802 is configured to receive SRAP messages;

[0195] The processor 801 is configured to determine a target intermediate bearer configuration in a candidate intermediate bearer configuration list based on the SRAP message.

[0196] An embodiment of the present application further provides a computer-readable storage medium, wherein the storage medium stores a computer program, and the computer program is configured to be executed by a processor of a first terminal to implement the above-mentioned method for determining the relay load configuration of the first terminal.

[0197] Optionally, the computer-readable storage medium may include: ROM (Read-Only Memory), RAM (Random-Access Memory), SSD (Solid State Drives), or an optical disk, etc. Among them, the random access memory may include ReRAM (Resistance Random Access Memory) and DRAM (Dynamic Random Access Memory).

[0198] An embodiment of the present application further provides a chip, which includes a programmable logic circuit and / or program instructions. When the chip runs on a first terminal, it is used to implement the method for determining the relay load configuration of the first terminal.

[0199] An embodiment of the present application also provides a computer program product or computer program, which includes computer instructions, and the computer instructions are stored in a computer-readable storage medium. The processor of the first terminal reads and executes the computer instructions from the computer-readable storage medium to implement the above-mentioned method for determining the intermediate load configuration of the first terminal.

[0200] It should be understood that the "indication" mentioned in the embodiments of this application can be a direct indication, an indirect indication, or an indication of an association. For example, "A indicates B" can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association between A and B.

[0201] In the description of the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between the two, or an association relationship between the two, or a relationship between indication and being indicated, configuration and being configured, etc.

[0202] In this document, "plurality" refers to two or more. "And / or" describes a relationship between associated objects, indicating that three possible relationships exist. For example, "A and / or B" can mean: A exists alone, A and B exist simultaneously, or B exists alone. The character " / " generally indicates an "or" relationship between the associated objects.

[0203] In addition, the step numbers described in this document only illustrate a possible execution order between the steps. In some other embodiments, the above steps may not be executed in the order of the numbers, such as two steps with different numbers are executed at the same time, or two steps with different numbers are executed in the opposite order of the diagram. The embodiments of the present application are not limited to this.

[0204] Those skilled in the art will appreciate that in one or more of the above examples, the functions described in the embodiments of the present application can be implemented using hardware, software, firmware, or any combination thereof. When implemented using software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein communication media include any media that facilitates the transmission of computer programs from one place to another. The storage medium can be any available medium that can be accessed by a general-purpose or special-purpose computer.

[0205] The above description is merely an exemplary embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application shall be included in the scope of protection of the present application.

Claims

1. A method for determining a relay bearer configuration, characterized in that: The method is performed by a first terminal, and includes: Receive Sideline Relay Adaptation Protocol (SRAP) messages; A target intermediate bearer configuration is determined in a candidate intermediate bearer configuration list based on the SRAP message.

2. The method according to claim 1, characterized in that The SRAP message carries: Bearer identification ID; or, Quality of Service (QoS) flow identification ID.

3. The method according to claim 2, characterized in that The target intermediate bearer configuration is determined in the candidate intermediate bearer configuration list based on the bearer ID.

4. The method according to claim 2, characterized in that The target intermediate bearer configuration is determined in the candidate intermediate bearer configuration list based on the QoS flow ID.

5. The method according to any one of claims 1 to 4, characterized in that: The method further comprises: Obtain the candidate successor load configuration list.

6. The method according to any one of claims 1 to 4, characterized in that: The candidate successor bearer configuration in the candidate successor bearer configuration list includes at least one of the following configurations: Data bearer configuration of sidelink data radio bearer SL-DRB; A correspondence between the bearer ID corresponding to the data bearer configuration and the first information; Radio link control RLC bearer configuration of the SL-DRB; A correspondence between the bearer ID corresponding to the RLC bearer configuration and the first information; The first information includes at least one of a QoS flow, a QoS flow list, an RLC bearer configuration index, and an associated bearer configuration index.

7. The method according to claim 6, characterized in that The data bearer configuration includes at least one of the following: Related configuration of the Service Data Adaptation Protocol (SDAP) layer; Packet Data Convergence Protocol (PDCP) layer configuration; Data bearer configuration index.

8. The method according to claim 6, characterized in that The RLC bearer configuration includes at least one of the following: SRAP layer related configuration; Related configuration of RLC layer; Media Access Control (MAC) layer configuration; The RLC bearer configuration index; The associated bearer configuration index.

9. The method according to claim 5, characterized in that The obtaining of the candidate successor load configuration list includes at least one of the following methods: Obtain the candidate successor load configuration list in a preconfigured manner; Obtain the candidate successor bearer configuration list by receiving a system broadcast message; Obtaining the candidate inheritor bearer configuration list by receiving RRC dedicated signaling; The candidate successor bearer configuration list is obtained by receiving a message sent by the second terminal.

10. The method according to claim 9, characterized in that The obtaining of the candidate successor load configuration list includes at least one of the following methods: When the first terminal is out of network coverage, obtaining the candidate inheritor bearer configuration list in a pre-configured manner; When the first terminal is within network coverage and in a radio resource control (RRC) idle state, obtaining the candidate inherit bearer configuration list by receiving a system broadcast message; When the first terminal is within network coverage and the RRC is in an inactive state, obtaining the candidate inheritor bearer configuration list by receiving a system broadcast message; When the first terminal is within network coverage and in an RRC connected state, obtaining the candidate inheritor bearer configuration list by receiving RRC dedicated signaling; The candidate inherit bearer configuration list is obtained by receiving a PC5-RRC message or a sidelink media access control control element SL-MAC CE or sidelink control information SCI sent by the second terminal.

11. The method according to claim 9, characterized in that The first terminal is a source terminal or a remote terminal, and the second terminal is a relay terminal; or, The first terminal is a relay terminal, and the second terminal is a source terminal or a remote terminal.

12. The method according to claim 5, characterized in that The obtaining of the candidate successor load configuration list further includes: Obtaining a first candidate relay bearer configuration list corresponding to the relay service of the first terminal, where the candidate relay bearer configurations in the first candidate relay bearer configuration list include a relay indication; and / or, A second candidate relay bearer configuration list corresponding to the non-relay service of the first terminal is obtained, where the candidate relay bearer configurations in the second candidate relay bearer configuration list include a non-relay indication.

13. The method according to claim 4, characterized in that The QoS flow ID is carried in at least one of the following protocol layer subheaders: SRAP layer; RLC layer; MAC layer.

14. The method according to claim 4, characterized in that The target intermediate bearer configuration is determined based on the QoS flow ID and the terminal-to-terminal U2U bearer configuration sequence, and the U2U bearer configuration sequence is a terminal-to-terminal bearer configuration sequence generated by the second terminal according to the QoS flow ID and the RLC bearer configuration sequence.

15. The method according to claim 14, characterized in that The U2U bearer configuration sequence is carried in at least one of the following protocol layer subheaders: SRAP layer; RLC layer; MAC layer.

16. A device for determining a relay bearer configuration, characterized in that: The device includes: a receiving module and a determining module; The receiving module is used to receive the Sidelink Relay Adaptation Protocol (SRAP) message; The determining module is configured to determine a target intermediate bearer configuration in a candidate intermediate bearer configuration list based on the SRAP message.

17. A terminal device, characterized in that: The terminal device includes a transceiver and a processor; The transceiver is used to receive Sidelink Relay Adaptation Protocol (SRAP) messages; The processor is configured to determine a target intermediate bearer configuration in a candidate intermediate bearer configuration list based on the SRAP message.

18. A computer-readable storage medium, characterized in that The storage medium stores a computer program, and the computer program is used to be executed by a processor to implement the method for determining the relay load configuration according to any one of claims 1 to 15.

19. A chip, characterized in that: The chip includes a programmable logic circuit and / or program instructions, and when the chip is running, is used to implement the method for determining the relay load configuration according to any one of claims 1 to 15.

20. A computer program product or a computer program, characterized in that The computer program product or computer program includes computer instructions, which are stored in a computer-readable storage medium. The processor reads and executes the computer instructions from the computer-readable storage medium to implement the method for determining the relay load configuration according to any one of claims 1 to 15.