[go: up one dir, main page]
More Web Proxy on the site http://driver.im/

WO2024016173A1 - 中继承载配置的确定方法、装置、设备及存储介质 - Google Patents

中继承载配置的确定方法、装置、设备及存储介质 Download PDF

Info

Publication number
WO2024016173A1
WO2024016173A1 PCT/CN2022/106556 CN2022106556W WO2024016173A1 WO 2024016173 A1 WO2024016173 A1 WO 2024016173A1 CN 2022106556 W CN2022106556 W CN 2022106556W WO 2024016173 A1 WO2024016173 A1 WO 2024016173A1
Authority
WO
WIPO (PCT)
Prior art keywords
configuration
terminal
relay
candidate
bearer
Prior art date
Application number
PCT/CN2022/106556
Other languages
English (en)
French (fr)
Inventor
张博源
卢前溪
冷冰雪
Original Assignee
Oppo广东移动通信有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Oppo广东移动通信有限公司 filed Critical Oppo广东移动通信有限公司
Priority to PCT/CN2022/106556 priority Critical patent/WO2024016173A1/zh
Publication of WO2024016173A1 publication Critical patent/WO2024016173A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition

Definitions

  • the embodiments of the present application relate to the field of communication technology, and in particular to a method, device, equipment and storage medium for determining a relay transmission configuration.
  • End-to-end (UE-to-UE, U2U) communication is a sidelink communication technology, that is, near field communication where terminals (User Equipment, UE) directly connect information through the PC5 interface.
  • U2U relay (relay) relays data through a relay terminal (relay User Equipment, relay UE) for the source terminal (source UE) and the remote terminal (remote UE), thereby realizing the connection between the source terminal and the remote terminal. communication between.
  • mode A the base station allocates resources for data transmission on the sidelink.
  • mode B the source terminal/remote terminal selects a resource from the resource pool for data transmission on the sidelink.
  • the relay terminal cannot directly obtain the relay transmission configuration from the Sidelink Relay Adaptation Protocol (SRAP) message. How to determine the relay transmission configuration and then implement U2U relay is a problem that needs to be solved.
  • SRAP Sidelink Relay Adaptation Protocol
  • Embodiments of the present application provide a method, device, equipment and storage medium for determining relay transmission configuration.
  • the technical solutions are as follows:
  • a method for determining a relay transmission configuration is provided.
  • the method is executed by a first terminal, and the method includes:
  • a device for determining a relay transmission configuration includes: a receiving module and a determining module;
  • the receiving module is used to receive side row relay adaptation protocol SRAP messages
  • the determining module determines the target relay transfer configuration in the candidate relay transfer configuration list based on the SRAP message.
  • a terminal device includes a transceiver and a processor connected to the transceiver;
  • the transceiver is used to receive side row relay adaptation protocol SRAP messages
  • the processor is configured to determine a target relay transfer configuration in a candidate relay transfer configuration list based on the SRAP message.
  • a computer-readable storage medium is provided, and a computer program is stored in the storage medium, and the computer program is used for execution by a processor to implement the above method for determining the relay transmission configuration.
  • a chip is provided.
  • the chip includes a programmable logic circuit and/or program instructions. When the chip is running, it is used to implement the above method for determining the relay load configuration.
  • a computer program product or computer program includes computer instructions.
  • the computer instructions are stored in a computer-readable storage medium.
  • the processor obtains the instructions from the computer program.
  • the computer-readable storage medium reads and executes the computer instructions to implement the above method for determining the relay transmission configuration.
  • the first terminal determines the target intermediate bearer configuration for U2U relay transmission in the candidate intermediate bearer configuration list based on the information carried in the SRAP message, thereby realizing U2U relay transmission.
  • Figure 1 is a schematic diagram of a communication system provided by an embodiment of the present application.
  • Figure 2 is a flow chart of a method for determining intermediate transmission configuration provided by an embodiment of the present application
  • Figure 3 is a flow chart of a method for determining intermediate transmission configuration provided by an embodiment of the present application
  • Figure 4 is a flow chart of a method for determining intermediate transmission configuration provided by an embodiment of the present application.
  • Figure 5 is a schematic diagram of a serialization rule for generating a U2U bearer configuration sequence provided by an embodiment of the present application
  • Figure 6 is a structural block diagram of a device for relaying configuration provided by an embodiment of the present application.
  • Figure 7 is a schematic structural diagram of a terminal device provided by an embodiment of the present application.
  • FIG. 1 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 .
  • 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 relaying by the relay terminal 20 .
  • the two remote terminals 10 that perform sidelink communication via the relay terminal 20 may be respectively referred to as the source terminal and the remote terminal.
  • the source terminal transmits data to the remote terminal via the relay terminal 20, Or vice versa.
  • the number of remote terminals 10 is usually multiple, and one or more remote terminals 10 can be distributed in the cell managed by each network device 30 .
  • the remote terminal 10 may include various handheld devices with wireless communication functions, vehicle-mounted devices, wearable devices, computing devices or other processing devices connected to wireless modems, as well as various forms of user equipment, mobile stations (MS )etc. For convenience of description, the devices mentioned above are collectively called remote terminals.
  • the relay terminal 20 refers to a terminal device capable of performing side link communication with the remote terminal 10 .
  • the number of relay terminals 20 is usually multiple, and one or more relay terminals 20 may be distributed in the cell managed by each network device 30 .
  • the relay terminal 20 may include various handheld devices with wireless communication functions, vehicle-mounted devices, wearable devices, computing devices or other processing devices connected to wireless modems, as well as various forms of user equipment, mobile stations (Mobile Station, MS )etc. For convenience of description, the devices mentioned above are collectively called relay terminals.
  • 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 be different. For example, in a 5G NR system, it is called a 5G base station (5G Node B, gNodeB/gNB).
  • the remote terminal 10 and the relay terminal 20 establish a connection through a side link, and can communicate with each other through a direct communication interface (such as the PC5 interface).
  • the relay terminal 20 can broadcast the network to the remote terminal 10 through the side link. Device messages to achieve network relay. Communication data is directly transmitted between the remote terminal 10 and the relay terminal 20 through the side link. Unlike the traditional cellular system in which communication data is received or sent through network equipment, this transmission process has the characteristics of short delay and low overhead. , suitable for communication between two terminals that are geographically close (such as vehicle-mounted equipment and other peripheral devices that are geographically close).
  • the network device 30 and the relay terminal 20 communicate with each other through some air technology, such as the Uu interface.
  • terminal devices including remote terminal 10 and relay terminal 20
  • support broadcasting discovery messages so that other terminal devices can discover themselves by receiving discovery messages.
  • GSM Global System of Mobile Communication
  • CDMA Code Division Multiple Access
  • WCDMA broadband code division multiple access
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • FDD Frequency Division Duplex
  • TDD Time Division Duplex
  • LTE-A Advanced Long Term Evolution
  • NR New Radio
  • UMTS Universal Mobile Telecommunication System
  • WiMAX Worldwide Interoperability for Microwave Access
  • WLAN Wireless Local Area Networks
  • WiFi Wireless Fidelity
  • the relay terminal performs Quality of Service (QoS) segmentation for the remote terminal.
  • QoS Quality of Service
  • the relay terminal After the remote terminal transmits data to the relay terminal according to the segmented QoS, the relay terminal cannot directly determine the specific relay transmission configuration of the remote terminal through the information carried by the remote terminal in the subheader of the SRAP message. Therefore, the relay terminal The relay terminal cannot determine the relay transfer configuration required to perform relay transmission.
  • the technical solution of this application is to associate the information carried in the SRAP message with the relay bearer configuration used for U2U relay transmission, and the first terminal determines the relay transmission based on the received SRAP message.
  • the target relay carries the configuration to realize U2U relay transmission.
  • Layer 2 relay refers to a relay method that implements relay through the Access Stratum (AS) of the relay terminal.
  • AS Access Stratum
  • FIG. 2 shows a flow chart of a method for determining a relay transmission configuration provided by an embodiment of the present application.
  • the method is executed by the first terminal, which may be the relay terminal 20 or the remote terminal 10 in the communication system shown in FIG. 1 .
  • the method may include the following steps:
  • Step 220 Receive the SRAP message
  • the SRAP message carries a bearer IDitifier; or a QoS flow ID.
  • the information carried in the header of the SRAP message includes UE ID, bearer ID, QoS flow ID, data/control identification (D/C), etc. This application does not limit this.
  • bearers are used to transmit data.
  • a terminal can transmit data through multiple bearers, and different bearers are identified by bearer IDs.
  • the QoS flow ID or QoS flow ID list is carried in at least one of the following protocol layer sub-headers: SRAP layer; Radio Link Control (Radio Link Control, RLC) layer; Media Access Control (Media Access Control, MAC) layer.
  • SRAP layer Radio Link Control (Radio Link Control, RLC) layer
  • RLC Radio Link Control
  • MAC Media Access Control
  • Step 240 Determine the target intermediate transfer configuration in the candidate intermediate transfer configuration list based on the SRAP message.
  • the SRAP message carries the bearer ID, then the target intermediate bearer configuration is determined in the candidate intermediate bearer configuration list based on the bearer ID; in other embodiments, the SRAP message carries the QoS flow ID, then The target intermediate transfer configuration is determined in the candidate intermediate transfer configuration list based on the QoS flow ID.
  • the bearer ID is carried in the header of the SRAP message
  • the target intermediate bearer configuration is determined in the candidate intermediate bearer configuration list based on the bearer ID carried in the SRAP header.
  • the QoS flow ID is carried in the 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.
  • the list of candidate intermediate transfer configurations includes at least two candidate intermediate transfer configurations.
  • the candidate intermediate transmission configuration in the candidate intermediate transmission configuration list includes at least one of the following configurations: data transmission configuration of sidelink data radio bearer (SL-DRB); data transmission configuration The corresponding relationship between the corresponding bearer ID and the first information; the RLC bearer configuration of SL-DRB; the corresponding relationship between the bearer ID corresponding to the RLC bearer configuration and the first information; wherein the first information includes QoS flow, QoS flow list, RLC bearer At least one of a configuration index and an associated bearer configuration index.
  • SL-DRB sidelink data radio bearer
  • the aforementioned data bearing configuration includes at least one of the following: related configurations of the Service Data Adaptation Protocol (SDAP) layer; related configurations of the Packet Data Convergence Protocol (Packet Data Convergence Protocol, PDCP) layer ;Data bearer configuration index.
  • SDAP Service Data Adaptation Protocol
  • PDCP Packet Data Convergence Protocol
  • the aforementioned RLC bearer configuration includes at least one of the following: SRAP layer related configuration; RLC layer related configuration; MAC layer related configuration; RLC bearer configuration index; associated bearer configuration index.
  • the data bearer configuration of SL-DRB includes the relevant configuration of the SDAP layer/PDCP layer
  • the RLC bearer configuration includes the relevant configuration of the SRAP layer/MAC layer/RLC layer
  • the aforementioned associated bearer configuration index is the SDAP layer/PDCP layer
  • the bearer configuration index associated with the SRAP layer/MAC layer/RLC layer is to associate a set of bearer configurations of a complete protocol stack through the associated bearer configuration index.
  • a step is further included: obtaining a candidate midstream download configuration list.
  • obtaining the candidate midload configuration list includes at least one of the following methods: obtaining the candidate midload configuration list through preconfiguration; obtaining the candidate midload configuration list by receiving system broadcast messages; and obtaining the candidate midload configuration list by receiving radio resource control (Radio Resource Control, RRC) proprietary signaling to obtain the candidate midstream transmission configuration list; obtain the candidate midstream transmission configuration list by receiving a message sent by the second terminal.
  • RRC Radio Resource Control
  • obtaining the candidate mid-range load configuration list includes at least one of the following methods: when the first terminal is outside the network coverage, obtaining the candidate mid-range load configuration list through pre-configuration; when the first terminal is in the network When the first terminal is within network coverage and the RRC is in the idle state, the candidate successful bearer configuration list is obtained by receiving the system broadcast message; when the first terminal is within the network coverage and the RRC is in the inactive state, the candidate successful bearer is obtained by receiving the system broadcast message.
  • the second terminal is a peer terminal of the first terminal.
  • the second terminal device may 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 Figure 1, and will not be described in detail here.
  • the first terminal is a source terminal or a remote terminal
  • the second terminal is a relay terminal
  • the first terminal is a relay terminal
  • the second terminal is a source terminal or a remote terminal. That is, the relay transfer configuration may be performed from the source terminal/remote terminal to the relay terminal, or the relay transfer configuration may be performed from the relay terminal to the source terminal/remote terminal.
  • a first candidate relay bearer configuration list corresponding to the relay service of the first terminal and the candidate relay bearer configuration in the first candidate relay bearer configuration list includes a relay indication; and/or obtain the third relay bearer configuration list.
  • a second candidate relay bearer configuration list corresponding to a terminal's non-relay service, and the candidate relay bearer configuration in the second candidate relay bearer configuration list includes a non-relay indication. That is, for the relay service and the non-relay service of the first terminal, the candidate relay transmission configuration list can be obtained respectively.
  • the technical solution provided by the embodiments of this 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;
  • the association mechanism between the information carried and the target relay transmission configuration realizes U2U relay transmission.
  • the information carried in the SRAP message may be a bearer ID or a QoS flow ID.
  • the following is an exemplary description of the two kinds of information that may be carried in the foregoing SRAP message.
  • the SRAP message carries the bearer ID.
  • Figure 3 shows a flowchart of a method for determining a relay transmission configuration provided by an embodiment of the present application. This method can be applied to the communication system shown in Figure 1 and executed by the first terminal.
  • the first terminal can 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:
  • Step 320 Receive the SRAP message
  • the first terminal receives the SRAP message.
  • the SRAP message carries a bearer ID, and the bearer ID is used to indicate the bearer used by the second terminal to transmit data to the first terminal.
  • the bearer ID is carried in the header of the SRAP message.
  • the second terminal is a peer terminal of the first terminal.
  • the second terminal device may 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 Figure 1, and will not be described in detail here.
  • Step 322 Obtain the candidate relay download configuration list
  • the list of candidate intermediate transfer configurations includes at least two candidate intermediate transfer configurations.
  • the candidate intermediate transfer configurations in the candidate intermediate transfer configuration list include at least one of the following three configurations:
  • Configuration 1 SL-DRB data bearer configuration
  • the data bearing configuration includes at least one of the following:
  • the length of the data bearer configuration index is 512 bits.
  • the RLC bearer configuration includes at least one of the following:
  • the data bearer configuration of SL-DRB includes the relevant configuration of the SDAP layer/PDCP layer
  • the RLC bearer configuration includes the relevant configuration of the SRAP layer/MAC layer/RLC layer
  • the aforementioned associated bearer configuration index is the SDAP layer/PDCP layer
  • the bearer configuration index associated with the SRAP layer/MAC layer/RLC layer is to associate a set of bearer configurations of a complete protocol stack through the associated bearer configuration index.
  • Configuration 3 the correspondence between the bearer ID corresponding to the data bearer configuration and the first information; or the 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.
  • the bearer ID corresponding to the data bearer configuration is a signaling radio bearer (Signaling Radio Bearer, SRB) ID or a data radio bearer (Data Radio Bearer, DRB) ID.
  • SRB Signaling Radio Bearer
  • DRB Data Radio Bearer
  • the first terminal can obtain any one of the above three sets of configurations, or any combination of the above three sets of configurations. This application does not limit this.
  • obtaining the candidate midstream transfer configuration list includes at least one of the following methods: obtaining the candidate midstream load configuration list through preconfiguration; obtaining the candidate midstream load configuration list by receiving a system broadcast message; obtaining the candidate midstream load configuration list by receiving RRC proprietary Signaling obtains the candidate midload configuration list; and obtains the candidate midload configuration list by receiving a message sent by the second terminal.
  • obtaining the candidate intermediate download configuration list includes at least one of the following methods:
  • ⁇ Obtain the candidate relay transmission configuration list by receiving the PC5-RRC message or SL-MAC CE or SCI sent by the second terminal.
  • the second terminal is a peer terminal of the first terminal.
  • the second terminal device may be a remote terminal or a relay terminal.
  • the meaning of the remote terminal and the relay terminal can be referred to the embodiment shown in Figure 1, and will not be described again here.
  • 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. That is, the relay transfer configuration may be performed from the source terminal/remote terminal to the relay terminal, or the relay transfer configuration may be performed from the relay terminal to the source terminal/remote terminal.
  • the above three sets of candidate relay transmission configurations can be combined in any combination.
  • the source terminal transmits data to the remote terminal via the relay terminal
  • the source terminal uses the above configuration 1 when performing the relay transfer configuration to the relay terminal
  • the relay terminal performs the relay transfer configuration to the remote terminal.
  • the first terminal obtains the candidate transmission configuration list by receiving the PC5-RRC message/SL-MAC CE/SCI sent by the second terminal.
  • the candidate transmission configuration list can be obtained.
  • the candidate relay transfer configuration in the transfer configuration list is reported to the network side.
  • the network side may reject the candidate relay transfer configuration reported by the first terminal.
  • the second terminal may send the configuration rejection information to the first terminal, or send a reconfiguration request to the first terminal.
  • a first candidate relay bearer configuration list corresponding to the relay service of the first terminal and the candidate relay bearer configuration in the first candidate relay bearer configuration list includes a relay indication; and/or obtain the third relay bearer configuration list.
  • a second candidate relay bearer configuration list corresponding to a terminal's non-relay service, and the candidate relay bearer configuration in the second candidate relay bearer configuration list includes a non-relay indication. That is, for the relay service and the non-relay service of the first terminal, the candidate relay transmission configuration list can be obtained respectively.
  • steps 320 and 322 are executed in no particular order. Step 320 may be executed first and then step 322; or step 322 may be executed first and then step 320; or step 320 and step 322 may be executed at the same time. . This application does not limit this.
  • Step 340 Determine the target intermediate transfer configuration in the candidate intermediate transfer configuration list based on the bearer ID.
  • 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 the target intermediate bearer configuration in the candidate intermediate bearer configuration list, that is, the target intermediate bearer configuration is the intermediate bearer configuration corresponding to the bearer ID carried in the SRAP message. .
  • the first terminal performs U2U relay transmission based on the target relay transmission configuration.
  • the technical solution provided by this embodiment uses the bearer ID carried in the SRAP message to determine the target relay bearer configuration in the candidate relay bearer configuration list obtained by the first terminal, thereby realizing U2U relay. transmission.
  • the SRAP message carries the QoS flow ID.
  • Figure 4 shows a flowchart of a method for determining a relay transmission configuration provided by an embodiment of the present application. This method can be applied to the communication system shown in Figure 1 and executed by the first terminal.
  • the first terminal can 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:
  • Step 420 Receive the SRAP message
  • the first terminal receives the SRAP message.
  • the SRAP message carries a QoS flow ID, and the QoS flow ID corresponds to the bearer used by the second terminal to transmit data to the first terminal.
  • the QoS flow ID or QoS flow ID list is carried in the header of the SRAP message.
  • the QoS flow ID or QoS flow ID list is carried in at least one of the following protocol layer sub-headers: SRAP layer; RLC layer; MAC layer.
  • the second terminal is a peer terminal of the first terminal.
  • the second terminal device may 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 Figure 1, and will not be described in detail here.
  • Step 422 Obtain the candidate relay download configuration list
  • the list of candidate intermediate transfer configurations includes at least two candidate intermediate transfer configurations.
  • the candidate intermediate transfer configurations in the candidate intermediate transfer configuration list include at least one of the following three configurations:
  • Configuration 1 SL-DRB data bearer configuration
  • the data bearing configuration includes at least one of the following:
  • the length of the data bearer configuration index is 512 bits.
  • the RLC bearer configuration includes at least one of the following:
  • the data bearer configuration of SL-DRB includes the relevant configuration of the SDAP layer/PDCP layer
  • the RLC bearer configuration includes the relevant configuration of the SRAP layer/MAC layer/RLC layer
  • the aforementioned associated bearer configuration index is the SDAP layer/PDCP layer
  • the bearer configuration index associated with the SRAP layer/MAC layer/RLC layer means that a set of bearer configurations for a complete protocol stack are associated through the associated bearer configuration index.
  • Configuration 3 the corresponding relationship between the bearer ID corresponding to the data bearer configuration and the first information; or the corresponding relationship 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.
  • the bearer ID corresponding to the data bearer configuration is a signaling radio bearer (Signaling Radio Bearer, SRB) ID or a data radio bearer (Data Radio Bearer, DRB) ID.
  • SRB Signaling Radio Bearer
  • DRB Data Radio Bearer
  • the first terminal can obtain any one of the above three sets of configurations, or any combination of the above three sets of configurations. This application does not limit this.
  • obtaining the candidate midstream transfer configuration list includes at least one of the following methods: obtaining the candidate midstream load configuration list through preconfiguration; obtaining the candidate midstream load configuration list by receiving a system broadcast message; obtaining the candidate midstream load configuration list by receiving RRC proprietary Signaling obtains the candidate midload configuration list; and obtains the candidate midload configuration list by receiving a message sent by the second terminal.
  • obtaining the candidate intermediate download configuration list includes at least one of the following methods:
  • ⁇ Obtain the candidate relay transmission configuration list by receiving the PC5-RRC message or SL-MAC CE or SCI sent by the second terminal.
  • the second terminal is a peer terminal of the first terminal.
  • the second terminal device may 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 Figure 1, and will not be described in detail here.
  • 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. That is, the configuration can be relayed from the source terminal/remote terminal to the relay terminal, or the configuration can be relayed from the relay terminal to the source terminal/remote terminal.
  • the first terminal obtains the candidate transmission configuration list by receiving the PC5-RRC message/SL-MAC CE/SCI sent by the second terminal.
  • the candidate transmission configuration list can be obtained.
  • the candidate relay transfer configuration in the transfer configuration list is reported to the network side.
  • the network side may reject the candidate relay transfer configuration reported by the first terminal.
  • the second terminal may send the configuration rejection information to the first terminal, or send a reconfiguration request to the first terminal.
  • a first candidate relay bearer configuration list corresponding to the relay service of the first terminal and the candidate relay bearer configuration in the first candidate relay bearer configuration list includes a relay indication; and/or obtain the third relay bearer configuration list.
  • a second candidate relay bearer configuration list corresponding to a terminal's non-relay service, and the candidate relay bearer configuration in the second candidate relay bearer configuration list includes a non-relay indication. That is, for the relay service and the non-relay service of the first terminal, the candidate relay transmission configuration list can be obtained respectively.
  • the second terminal generates a U2U bearer configuration sequence based on the QoS flow ID and RLC bearer configuration. That is, 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.
  • 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, where the label of the U2U bearer configuration sequence corresponds to the QoS flow ID one-to-one.
  • Figure 5 shows a schematic diagram of a serialization rule for generating a U2U bearer configuration sequence.
  • 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;
  • QoS flow ID 8 corresponds to RLC bearer configuration 3. This application does not impose any restrictions on the corresponding method between QoS flow ID and RLC bearer configuration.
  • 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.
  • the above U2U bearer configuration sequence is carried in at least one of the following protocol layer sub-headers: SRAP layer; RLC layer; MAC layer.
  • steps 420 and 422 are executed in no particular order. 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 at the same time. . This application does not limit this.
  • Step 440 Determine the target intermediate transfer configuration in the candidate intermediate transfer configuration list based on the QoS flow ID.
  • the candidate midstream transfer configuration list includes the candidate midstream load and specific midstream load configuration information corresponding to the candidate midstream load.
  • the first terminal determines the target relay bearer configuration in the candidate relay bearer configuration list.
  • the first terminal performs U2U relay transmission based on the target relay transmission 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, it corresponds to U2U bearer configuration 5, and the first terminal determines RLC bearer configuration 2 corresponding to U2U bearer configuration 5 as the target intermediate bearer configuration.
  • the aforementioned candidate relay transmission configuration list can be generated by any combination.
  • the source terminal uses the above configuration 1 when performing the relay transfer configuration to the relay terminal, and the relay terminal performs the relay transfer configuration to the remote terminal.
  • Configuration sequence for another example, the above U2U bearer configuration sequence is used when the source terminal performs relay transfer configuration to the relay terminal and when the relay terminal performs relay transfer configuration to the remote terminal, and so on. This application does not limit this.
  • the technical solution provided by this embodiment uses the QoS flow ID carried in the SRAP message to determine the target relay bearer configuration in the candidate relay bearer configuration list obtained by the first terminal, thereby realizing U2U relay bearer configuration. relay transmission.
  • Figure 6 shows a structural block diagram of a device for determining a relay download configuration provided by an embodiment of the present application.
  • the device has the function of implementing the above method example of the first terminal, and the function can be implemented by hardware, or can also be implemented by hardware executing corresponding software.
  • the device may be the first terminal introduced above, or may be provided in the first terminal. As shown in Figure 6, the device may include the following modules:
  • the receiving module 520 is used to receive the side row relay adaptation protocol SRAP message
  • the determining module 540 is configured to determine the target relay transfer configuration in the candidate relay transfer configuration list based on the SRAP message.
  • the SRAP message carries: bearer identification ID; or quality of service QoS flow ID.
  • the target intermediate load configuration is determined in the candidate intermediate load configuration list based on the bearer ID.
  • the target intermediate load configuration is determined in the candidate intermediate load configuration list based on the QoS flow ID.
  • the receiving module 520 is also used to obtain a candidate midstream download configuration list.
  • the candidate midstream transmission configurations in the candidate midstream transmission configuration list include at least one of the following configurations: a data bearer configuration of a side-link data radio bearer SL-DRB; the data The corresponding relationship between the bearer ID corresponding to the bearer configuration and the first information; the wireless link control RLC bearer configuration of the SL-DRB; the corresponding relationship between the bearer ID corresponding to the RLC bearer configuration and the first information; wherein, the third One piece of information includes at least one of a QoS flow, a QoS flow list, an RLC bearer configuration index, and an associated bearer configuration index.
  • the data bearer configuration includes at least one of the following: related configurations of the Service Data Adaptation Protocol SDAP layer; related configurations of the Packet Data Aggregation Protocol PDCP layer; and data bearer configuration index.
  • the RLC bearer configuration includes at least one of the following: SRAP layer related configuration; RLC layer related configuration; media access control MAC layer related configuration; the RLC bearer configuration index ;The associated bearer configuration index.
  • the receiving module 520 is also configured to at least one of the following: obtain the candidate successful inheritance configuration list through pre-configuration; obtain the candidate successful inheritance by receiving a system broadcast message
  • the candidate relay bearer configuration list is obtained by receiving RRC proprietary signaling; the candidate relay bearer configuration list is obtained by receiving a message sent by the second terminal.
  • the receiving module 520 is also configured to at least one of the following: when the first terminal is outside network coverage, obtain the candidate successful load through a preconfigured manner. Configuration list; when the first terminal is within network coverage and the radio resource control RRC is in the idle state, obtain the candidate relay transmission configuration list by receiving a system broadcast message; when the first terminal is within network coverage and When the radio resource control RRC is in the inactive state, the candidate relay bearer configuration list is obtained by receiving a system broadcast message; when the first terminal is within network coverage and the radio resource control RRC is in the connected state, the candidate relay bearer configuration list is obtained by receiving the RRC Dedicated signaling obtains the candidate relay configuration list; by receiving the PC5-RRC message sent by the second terminal or the sidelink media access control control unit SL-MAC CE or the sidelink control information SCI, the candidate relay configuration list is obtained Continue to download the configuration list.
  • the first terminal is a source terminal or a remote terminal
  • the second terminal is a relay terminal
  • the first terminal is a relay terminal
  • the second terminal It is the source terminal or the remote terminal.
  • the receiving module 520 is also configured to obtain a first candidate midload configuration list corresponding to the relay service of the first terminal.
  • the first candidate midload configuration list Containing a relay indication; and/or obtaining a second candidate relay bearer configuration list corresponding to the non-relay service of the first terminal, where the second candidate relay bearer configuration list contains the non-relay indication.
  • the QoS flow ID is carried in at least one of the following protocol layer sub-headers: SRAP layer; RLC layer; MAC layer.
  • the target intermediate bearer configuration is determined based on the QoS flow ID and a terminal-to-terminal U2U bearer configuration sequence.
  • the U2U bearer configuration sequence is for the second terminal according to the QoS flow ID. and the end-to-end bearer configuration sequence generated by the RLC bearer configuration sequence.
  • the U2U bearer configuration sequence is carried in at least one of the following protocol layer subheaders: SRAP layer; RLC layer; MAC layer.
  • the device provided in the above embodiment implements its functions, only the division of the above functional modules is used as an example. In practical applications, the above functions can be allocated to different functional modules according to actual needs. That is, the content structure of the device is divided into different functional modules to complete all or part of the functions described above.
  • FIG. 7 shows a schematic structural diagram 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.
  • 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.
  • the receiver 802 and the transmitter 803 can be implemented as a transceiver 806, and the transceiver 806 can be a communication chip.
  • Memory 804 is connected to processor 801 through bus 805.
  • the memory 804 can be used to store a computer program, and the processor 801 is used to execute the computer program to implement various steps performed by the terminal device in the above method embodiment.
  • volatile or non-volatile storage devices include but are not limited to: RAM (Random-Access Memory, random access memory) And ROM (Read-Only Memory, read-only memory), EPROM (Erasable Programmable Read-Only Memory, erasable programmable read-only memory), EEPROM (Electrically Erasable Programmable Read-Only Memory, electrically erasable programmable read-only memory) memory), flash memory or other solid-state storage technology, CD-ROM (Compact Disc Read-Only Memory, read-only disc), DVD (Digital Video Disc, high-density digital video disc) or other optical storage, tape cassettes, tapes, disks storage or other magnetic storage device.
  • RAM Random-Access Memory, random access memory
  • ROM Read-Only Memory, read-only memory
  • EPROM Erasable Programmable Read-Only Memory, erasable programmable read-only memory
  • EEPROM Electrically Erasable Programmable Read-Only Memory, electrically erasable programmable read
  • the processor and transceiver involved in the embodiment of the present application can perform the steps performed by the first terminal in any of the methods shown in FIGS. 2 to 4 above. No further details will be given.
  • the terminal device when the terminal device is implemented as the first terminal device,
  • the receiver 802 is used to receive SRAP messages
  • the processor 801 is configured to determine a target relay transfer configuration in a candidate relay transfer configuration list based on the SRAP message.
  • Embodiments of the present application also provide a computer-readable storage medium.
  • a computer program is stored in the storage medium.
  • the computer program is used to be executed by a processor of the first terminal to implement the above-mentioned relay download of the first terminal. How to determine the configuration.
  • the computer-readable storage medium may include: ROM (Read-Only Memory), RAM (Random-Access Memory), SSD (Solid State Drives, solid state drive) or optical disk, etc.
  • random access memory can include ReRAM (Resistance Random Access Memory, resistive random access memory) and DRAM (Dynamic Random Access Memory, dynamic random access memory).
  • Embodiments of the present application also provide a chip, which includes programmable logic circuits and/or program instructions. When the chip is run on the first terminal, it is used to implement the above-mentioned intermediate load configuration of the first terminal. Determine the method.
  • Embodiments of the present application also provide a computer program product or computer program.
  • the computer program product or computer program includes computer instructions.
  • the computer instructions are stored in a computer-readable storage medium.
  • the processor of the first terminal obtains the information from the computer instructions.
  • the computer-readable storage medium reads and executes the computer instructions to implement the above-mentioned method for determining the relay transmission configuration of the first terminal.
  • the "instruction” mentioned in the embodiments of this application may be a direct instruction, an indirect instruction, or an association relationship.
  • a indicates B which 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. relation.
  • correlate can mean that there is a direct correspondence or indirect correspondence between the two, it can also mean that there is an associated relationship between the two, or it can mean indicating and being instructed, configuration and being. Configuration and other relationships.
  • the "plurality” mentioned in this article means two or more than two.
  • “And/or” describes the relationship between related objects, indicating that there can be three relationships.
  • a and/or B can mean: A exists alone, A and B exist simultaneously, and B exists alone.
  • the character “/” generally indicates that the related objects are in an "or” relationship.
  • step numbers described in this article only illustrate a possible execution sequence between the steps.
  • the above steps may not be executed in the numbering sequence, such as two different numbers.
  • the steps are executed simultaneously, or two steps with different numbers are executed in the reverse order as shown in the figure, which is not limited in the embodiments of the present application.
  • Computer-readable media includes computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
  • Storage media can be any available media that can be accessed by a general purpose or special purpose computer.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请公开了一种中继承载配置的确定方法、装置、设备及存储介质，涉及通信技术领域。该方法由第一终端执行，所述方法包括：接收侧行中继适配协议SRAP报文；基于所述SRAP报文在候选中继承载配置列表中确定目标中继承载配置。本申请实施例中，第一终端在接收到SRAP报文后，根据SRAP报文中携带的信息，在候选中继承载配置列表中确定目标中继承载配置，从而实现终端到终端的中继传输。

Description

中继承载配置的确定方法、装置、设备及存储介质 技术领域
本申请实施例涉及通信技术领域，特别涉及一种中继承载配置的确定方法、装置、设备及存储介质。
背景技术
终端到终端(UE-to-UE，U2U)通信是一种侧行链路(Sidelink)通信技术，即终端(User Equipment，UE)之间通过PC5接口进行信息直连的近场通信。U2U中继(relay)是通过一个中继终端(relay User Equipment，relay UE)为源端终端(source UE)和远端终端(remote UE)中继传输数据，从而实现源端终端与远端终端之间的通信。
3GPP中定义了U2U的两种传输模式。模式A中基站分配用于侧行链路上数据传输的资源，模式B中源端终端/远端终端在资源池中选取一个资源用于侧行链路上数据的传输。
然而U2U中继传输模式中，中继终端无法直接从侧行中继适配协议(Sidelink Relay Adaptation Protocol，SRAP)报文获取中继承载配置。如何确定中继承载配置，进而实现U2U中继，是需要解决的问题。
发明内容
本申请实施例提供了一种中继承载配置的确定方法、装置、设备及存储介质。所述技术方案如下：
根据本申请实施例的一个方面，提供了一种中继承载配置的确定方法，所述方法由第一终端执行，所述方法包括：
接收侧行中继适配协议SRAP报文；
基于所述SRAP报文在候选中继承载配置列表中确定目标中继承载配置。
根据本申请实施例的一个方面，提供了一种中继承载配置的确定装置，所述装置包括：接收模块和确定模块；
所述接收模块，用于接收侧行中继适配协议SRAP报文；
所述确定模块，基于所述SRAP报文在候选中继承载配置列表中确定目标中继承载配置。
根据本申请实施例的一个方面，提供了一种终端设备，所述终端设备包括收发器和与所述收发器相连的处理器；
所述收发器，用于接收侧行中继适配协议SRAP报文；
所述处理器，用于基于所述SRAP报文在候选中继承载配置列表中确定目标中继承载配置。
根据本申请实施例的一个方面，提供了一种计算机可读存储介质，所述存储介质中存储有计算机程序，所述计算机程序用于处理器执行，以实现上述中继承载配置的确定方法。
根据本申请实施例的一个方面，提供了一种芯片，所述芯片包括可编程逻辑电路和/或程序指令，当所述芯片运行时，用于实现上述中继承载配置的确定方法。
根据本申请实施例的一个方面，提供了一种计算机程序产品或计算机程序，所述计算机程序产品或计算机程序包括计算机指令，所述计算机指令存储在计算机可读存储介质中，处理器从所述计算机可读存储介质读取并执行所述计算机指令，以实现上述中继承载配置的确定方法。
本申请实施例提供的技术方案可以带来如下有益效果：
通过接收SRAP报文，第一终端基于SRAP报文中携带的信息在候选中继承载配置列表中确定用于U2U中继传输的目标中继承载配置，进而实现U2U中继传输。
附图说明
为了更清楚地说明本申请实施例中的技术方案，下面将对实施例描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1是本申请一个实施例提供的通信系统的示意图；
图2是本申请一个实施例提供的中继承载配置的确定方法的流程图；
图3是本申请一个实施例提供的中继承载配置的确定方法的流程图；
图4是本申请一个实施例提供的中继承载配置的确定方法的流程图；
图5是本申请一个实施例提供的生成U2U承载配置序列的序列化规则的示意图；
图6是本申请一个实施例提供的中继承载配置的装置的结构框图；
图7是本申请一个实施例提供的终端设备的结构示意图。
具体实施方式
为使本申请的目的、技术方案和优点更加清楚，下面将结合附图对本申请实施方式作进一步地详细描述。
本申请实施例描述的网络架构以及业务场景是为了更加清楚地说明本申请实施例的技术方案，并不构成对本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
请参考图1，其示出了本申请一个示例性实施例提供的通信系统的框图，该通信系统可以包括：远端终端10、中继终端20和网络设备30。
远端终端10是指与中继终端20进行侧行链路通信并且继而可以经由中继终端20的中继而与其他远端终端10或网络设备30通信的终端设备。其中，经由中继终端20进行侧行链路通信的两个远端终端10可以分别被称为源端终端和远端终端，例如，源端终端经由中继终端20向远端终端传输数据，或者反之。远端终端10的数量通常为多个，每一个网络设备30所管理的小区内可以分布一个或多个远端终端10。远端终端10可以包括各种具有无线通信功能的手持设备、车载设备、可穿戴设备、计算设备或连接到无线调制解调器的其他处理设备，以及各种形式的用户设备、移动台(Mobile Station，MS)等等。为方便描述，上面提到的设备统称为远端终端。
中继终端20是指能够与远端终端10进行侧行链路通信的终端设备。中继终端20的数量通常为多个，每一个网络设备30所管理的小区内可以分布一个或多个中继终端20。中继终端20可以包括各种具有无线通信功能的手持设备、车载设备、可穿戴设备、计算设备或连接到无线调制解调器的其他处理设备，以及各种形式的用户设备、移动台(Mobile Station，MS)等等。为方便描述，上面提到的设备统称为中继终端。
网络设备30是用于为远端终端10以及中继终端20提供无线通信功能的设备。网络设备30可以包括各种形式的宏基站，微基站，中继站，接入点等等。在采用不同的无线接入技术的系统中，网络设备30的名称可能会有所不同，例如在5G NR系统中，称为5G基站(5G Node B，gNodeB/gNB)。
远端终端10与中继终端20之间通过侧行链路建立连接，可以通过直连通信接口(如PC5接口)互相通信，中继终端20可以通过侧行链路向远端终端10广播网络设备的消息，从而实现网络中继。远端终端10与中继终端20之间通过侧行链路直接进行通信数据传输，不同于传统的蜂窝系统中通信数据通过网络设备接收或者发送，该传输过程具有时延短、开销小等特点，适合用于地理位置接近的两个终端(如车载设备和地理位置接近的其它周边设备)之间的通信。网络设备30与中继终端20之间通过某种空中技术互相通信，例如Uu接口。
在本申请实施例中，终端设备(包括远端终端10、中继终端20)支持广播发送发现消息，以使得其他终端设备通过接收发现消息来发现自己。
本申请实施例的技术方案可以应用于各种通信系统，例如：全球移动通讯(Global System of Mobile Communication，GSM)系统、码分多址(Code Division Multiple Access，CDMA)系统、宽带码分多址(Wideband Code Division Multiple Access，WCDMA)系统、通用分组无线业务(General Packet Radio Service，GPRS)、长期演进(Long Term Evolution，LTE)系统、LTE频分双工(Frequency Division Duplex，FDD)系统、LTE时分双工(Time Division Duplex，TDD)系统、先进的长期演进(Advanced Long Term Evolution，LTE-A)系统、新无线(New Radio，NR)系统、NR系统的演进系统、非授权频段上的LTE(LTE-based access to Unlicensed spectrum，LTE-U)系统、NR-U系统、通用移动通信系统(Universal Mobile Telecommunication System，UMTS)、全球互联微波接入(Worldwide Interoperability for Microwave Access，WiMAX)通信系统、无线局域网(Wireless Local Area Networks，WLAN)、无线保真(Wireless Fidelity，WiFi)、下一代通信系统或其他通信系统等。
通常来说，传统的通信系统支持的连接数有限，也易于实现，然而，随着通信技术的发展，移动通信系统将不仅支持传统的通信，还将支持例如，设备到设备(Device to Device，D2D)通信，机器到机器(Machine to Machine，M2M) 通信，机器类型通信(Machine Type Communication，MTC)，车辆间(Vehicle to Vehicle，V2V)通信以及车联网(Vehicle to Everything，V2X)系统等。本申请实施例也可以应用于这些通信系统。
在层二U2U中继中，中继终端为远端终端执行服务质量(Quality of Service，QoS)切分。在远端终端按照切分后的QoS传输数据至中继终端后，中继终端无法直接通过远端终端在SRAP报文子头上携带的信息确定远端终端具体的中继承载配置，因此，中继终端无法确定执行中继传输时所需要的中继承载配置。
为了解决如上问题，本申请技术方案，将SRAP报文中携带的信息和进行U2U中继传输所使用的中继承载配置进行关联，第一终端基于接收到的SRAP报文确定用于中继传输的目标中继承载配置，实现U2U中继传输。
在本申请实施例中，层二中继指的是一种通过中继终端的接入层(Access Stratum，AS)实现中继的中继方式。
下面，通过几个实施例对本申请技术方案进行介绍说明。
请参考图2，其示出了本申请一个实施例提供的中继承载配置的确定方法的流程图。该方法由第一终端执行，第一终端可以为图1所示的通信系统中的中继终端20或远端终端10。该方法可以包括如下步骤：
步骤220：接收SRAP报文；
可选地，SRAP报文携带有承载标识ID(bearer IDitifier)；或，QoS流ID。
可选地，SRAP报文的报头中携带的信息包括UE ID、承载ID、QoS流ID、数据/控制标识(D/C)，等等。本申请对此不加以限制。
可选地，承载用于传输数据。一个终端可以通过多个承载来传输数据，不同的承载通过承载ID来进行标识。
可选地，QoS流ID或QoS流ID列表携带在以下协议层子头中的至少一种：SRAP层；无线链路控制(Radio Link Control，RLC)层；媒体接入控制(Media Access Control，MAC)层。
步骤240：基于SRAP报文在候选中继承载配置列表中确定目标中继承载配置。
在一些实施例中，SRAP报文携带有承载ID，则目标中继承载配置基于承载ID在候选中继承载配置列表中确定；在另一些实施例中，SRAP报文携带有QoS流ID，则目标中继承载配置基于QoS流ID在候选中继承载配置列表中确 定。
可选地，承载ID携带在SRAP报文的报头中，则基于SRAP报头中携带的承载ID在候选中继承载配置列表中确定目标中继承载配置。
可选地，QoS流ID携带在SRAP报文的报头中，则基于SRAP报头中携带的QoS流ID在候选中继承载配置列表中确定目标中继承载配置。
示例性的，候选中继承载配置列表中包含至少两个候选中继承载配置。
示例性的，候选中继承载配置列表中的候选中继承载配置，包括以下配置中的至少一种：侧行数据无线承载(Sidelink Data Radio Bearer，SL-DRB)的数据承载配置；数据承载配置对应的承载ID与第一信息的对应关系；SL-DRB的RLC承载配置；RLC承载配置对应的承载ID与第一信息的对应关系；其中，第一信息包括QoS流、QoS流列表、RLC承载配置索引、关联的承载配置索引中的至少一种。
示例性的，前述数据承载配置包括以下中的至少一种：服务数据适配协议(Service Data Adaptation Protocol，SDAP)层的相关配置；分组数据聚合协议(Packet Data Convergence Protocol，PDCP)层的相关配置；数据承载配置索引。
示例性的，前述RLC承载配置包括以下中的至少一种：SRAP层的相关配置；RLC层的相关配置；MAC层的相关配置；RLC承载配置索引；关联的承载配置索引。
可选地，SL-DRB的数据承载配置包括SDAP层/PDCP层的相关配置，RLC承载配置包括SRAP层/MAC层/RLC层的相关配置；前述关联的承载配置索引为将SDAP层/PDCP层与SRAP层/MAC层/RLC层关联起来的承载配置索引，即通过关联的承载配置索引关联出一套完整协议栈的承载配置。
在一些实施例中，在步骤240之前还包括步骤：获取候选中继承载配置列表。
示例性的，获取候选中继承载配置列表包括以下方式中的至少一种：通过预配置方式获取候选中继承载配置列表；通过接收系统广播消息获取候选中继承载配置列表；通过接收无线资源控制(Radio Resource Control，RRC)专有信令获取候选中继承载配置列表；通过接收第二终端发送的消息获取候选中继承载配置列表。
示例性的，获取候选中继承载配置列表包括以下方式中的至少一种：在第 一终端处于网络覆盖外的情况下，通过预配置方式获取候选中继承载配置列表；在第一终端处于网络覆盖内且RRC空闲态的情况下，通过接收系统广播消息获取候选中继承载配置列表；在第一终端处于网络覆盖内且RRC非活跃态的情况下，通过接收系统广播消息获取候选中继承载配置列表；在第一终端处于网络覆盖内且RRC连接态的情况下，通过接收RRC专有信令获取候选中继承载配置列表；通过接收第二终端发送的PC5-RRC消息或侧行媒体接入控制控制单元(SideLink Media Access Control Control Element，SL-MAC CE)或侧行控制信息(Sidelink Control Information，SCI)，获取候选中继承载配置列表。
其中，第二终端是第一终端的一个对端终端。
在本申请实施例中，第二终端设备可以是远端终端，也可以是中继终端。远端终端和中继终端的含义可以参见图1所示实施例，在此不进行赘述。
可选地，第一终端为源端终端或远端终端，第二终端为中继终端；或，第一终端为中继终端，第二终端为源端终端或远端终端。即，可以为从源端终端/远端终端向中继终端进行中继承载配置，也可以为从中继终端向源端终端/远端终端进行中继承载配置。
可选地，获取第一终端的中继业务对应的第一候选中继承载配置列表，第一候选中继承载配置列表中的候选中继承载配置包含有中继指示；和/或，获取第一终端的非中继业务对应的第二候选中继承载配置列表，第二候选中继承载配置列表中的候选中继承载配置包含有非中继指示。即，针对第一终端的中继业务和非中继业务，可以分别获取候选中继承载配置列表。
综上所述，本申请实施例提供的技术方案，通过SRAP报文中携带的信息，在候选中继承载配置列表中确定用于中继传输的目标中继承载配置；通过建立SRAP报文中携带的信息与目标中继承载配置的关联机制，实现了U2U的中继传输。
在基于图2的可选实施例中，SRAP报文中携带的信息可能为承载ID或QoS流ID。以下对前述SRAP报文中可能携带的两种信息分别进行示例性的说明。
1)SRAP报文中携带有承载ID。
图3示出了本申请一个实施例提供的中继承载配置的确定方法的流程图。该方法可应用于图1所示的通信系统中，由第一终端执行，第一终端可以为图1 所示的通信系统中的中继终端20或远端终端10。该方法可以包括如下步骤：
步骤320：接收SRAP报文；
示例性的，第一终端接收SRAP报文。该SRAP报文中携带有承载ID，该承载ID用于指示第二终端向第一终端传输数据时使用的承载。
可选地，承载ID携带在SRAP报文的报头中。
其中，第二终端为第一终端的一个对端终端。
在本申请实施例中，第二终端设备可以是远端终端，也可以是中继终端。远端终端和中继终端的含义可以参见图1所示实施例，在此不进行赘述。
步骤322：获取候选中继承载配置列表；
示例性的，候选中继承载配置列表中包括至少两个候选中继承载配置。
候选中继承载配置列表中的候选中继承载配置包括以下三种配置中的至少一种：
(1)配置1：SL-DRB的数据承载配置；
示例性的，数据承载配置包括以下中的至少一种：
·SDAP层的相关配置；
·PDCP层的相关配置；
·数据承载配置索引。
可选地，数据承载配置索引的长度为512比特。
(2)配置2：SL-DRB的RLC承载配置；
示例性的，RLC承载配置包括以下中的至少一种：
·SRAP层的相关配置；
·RLC层的相关配置；
·MAC层的相关配置；
·RLC承载配置索引；
·关联的承载配置索引。
可选地，SL-DRB的数据承载配置包括SDAP层/PDCP层的相关配置，RLC承载配置包括SRAP层/MAC层/RLC层的相关配置；前述关联的承载配置索引为将SDAP层/PDCP层与SRAP层/MAC层/RLC层关联起来的承载配置索引，即通过关联的承载配置索引关联出一套完整协议栈的承载配置。
(3)配置3：数据承载配置对应的承载ID与第一信息的对应关系；或者， RLC承载配置对应的承载ID与第一信息的对应关系。
可选地，第一信息包括QoS流、QoS流列表、RLC承载配置索引、关联的承载配置索引中的至少一种。
可选地，数据承载配置对应的承载ID为信令无线承载(Signaling Radio Bearer，SRB)ID或数据无线承载(Data Radio Bearer，DRB)ID。
需要注意的是，第一终端可以获取上述三套配置中的任意一种，或者是上述三套配置的任意组合。本申请对此不加以限制。
可选地，获取候选中继承载配置列表包括以下方式中的至少一种：通过预配置方式获取候选中继承载配置列表；通过接收系统广播消息获取候选中继承载配置列表；通过接收RRC专有信令获取候选中继承载配置列表；通过接收第二终端发送的消息获取候选中继承载配置列表。
进一步的，获取候选中继承载配置列表包括以下方式中的至少一种：
·在第一终端处于网络覆盖外的情况下，通过预配置方式获取候选中继承载配置列表；
·在第一终端处于网络覆盖内且RRC空闲态的情况下，通过接收系统广播消息获取候选中继承载配置列表；
·在第一终端处于网络覆盖内且RRC非活跃态的情况下，通过接收系统广播消息获取候选中继承载配置列表；
·在第一终端处于网络覆盖内且RRC连接态的情况下，通过接收RRC专有信令获取候选中继承载配置列表；
·通过接收第二终端发送的PC5-RRC消息或SL-MAC CE或SCI，获取候选中继承载配置列表。
其中，第二终端是第一终端的一个对端终端。
在本申请实施例中，第二终端设备可以是远端终端，也可以是中继终端。远端终端和中继终端的含义可以参见图1所示实施例，在此不进行赘述。
即，第一终端为源端终端或远端终端，第二终端为中继终端；或，第一终端为中继终端，第二终端为源端终端或远端终端。也即，可以为从源端终端/远端终端向中继终端进行中继承载配置，也可以为从中继终端向源端终端/远端终端进行中继承载配置。
需要注意的是，在终端到终端的中继传输中，上述3套候选中继承载配置 可以任意组合。例如，在源端终端经由中继终端向远端终端传输数据的过程中，源端终端向中继终端进行中继承载配置时使用上述配置1，中继终端向远端终端进行中继承载配置使用上述配置1和配置3的组合，等等。本申请对此不加以限制。
可选地，第一终端通过接收第二终端发送的PC5-RRC消息/SL-MAC CE/SCI获取候选中继承载配置列表，在第一终端处于RRC连接态的情况下，可以将该候选中继承载配置列表中的候选中继承载配置上报给网络侧。网络侧可以拒绝第一终端上报的候选中继承载配置。在第二终端接收到网络侧的配置拒绝信息时，第二终端可以向第一终端发送配置拒绝信息，或者向第一终端发送重新配置请求。
可选地，获取第一终端的中继业务对应的第一候选中继承载配置列表，第一候选中继承载配置列表中的候选中继承载配置包含有中继指示；和/或，获取第一终端的非中继业务对应的第二候选中继承载配置列表，第二候选中继承载配置列表中的候选中继承载配置包含有非中继指示。即，针对第一终端的中继业务和非中继业务，可以分别获取候选中继承载配置列表。
需要说明的是，上述步骤320和步骤322的执行顺序不分先后，可以先执行步骤320，再执行步骤322；或者，先执行步骤322，再执行步骤320；或者，步骤320和步骤322同时执行。本申请对此不加以限制。
步骤340：基于承载ID在候选中继承载配置列表中确定目标中继承载配置。
示例性的，候选中继承载配置列表中包含有承载ID和与承载ID对应的具体的中继承载配置信息。第一终端基于SRAP报文中携带的承载ID，在候选中继承载配置列表中确定目标中继承载配置，即目标中继承载配置为与SRAP报文中携带的承载ID对应的中继承载配置。
进一步的，第一终端基于该目标中继承载配置进行U2U的中继传输。
综上所述，本实施例提供的技术方案，通过SRAP报文中携带的承载ID，在第一终端获取到的候选中继承载配置列表中确定目标中继承载配置，进而实现U2U的中继传输。
2)SRAP报文中携带有QoS流ID。
图4示出了本申请一个实施例提供的中继承载配置的确定方法的流程图。该方法可应用于图1所示的通信系统中，由第一终端执行，第一终端可以为图1 所示的通信系统中的中继终端20或远端终端10。该方法可以包括如下步骤：
步骤420：接收SRAP报文；
示例性的，第一终端接收SRAP报文。该SRAP报文中携带有QoS流ID，该QoS流ID与第二终端向第一终端传输数据时使用的承载相对应。
可选地，QoS流ID或QoS流ID列表携带在SRAP报文的报头中。
可选地，QoS流ID或QoS流ID列表携带在以下协议层子头中的至少一种：SRAP层；RLC层；MAC层。
其中，第二终端为第一终端的一个对端终端。
在本申请实施例中，第二终端设备可以是远端终端，也可以是中继终端。远端终端和中继终端的含义可以参见图1所示实施例，在此不进行赘述。
步骤422：获取候选中继承载配置列表；
示例性的，候选中继承载配置列表中包括至少两个候选中继承载配置。
在一些实施例中，候选中继承载配置列表中的候选中继承载配置包括以下三种配置中的至少一种：
(1)配置1：SL-DRB的数据承载配置；
示例性的，数据承载配置包括以下中的至少一种：
·SDAP层的相关配置；
·PDCP层的相关配置；
·数据承载配置索引。
可选地，数据承载配置索引的长度为512比特。
(2)配置2：SL-DRB的RLC承载配置；
示例性的，RLC承载配置包括以下中的至少一种：
·SRAP层的相关配置；
·RLC层的相关配置；
·MAC层的相关配置；
·RLC承载配置索引；
·关联的承载配置索引。
可选地，SL-DRB的数据承载配置包括SDAP层/PDCP层的相关配置，RLC承载配置包括SRAP层/MAC层/RLC层的相关配置；前述关联的承载配置索引为将SDAP层/PDCP层与SRAP层/MAC层/RLC层关联起来的承载配置索引， 即通过关联的承载配置索引关联出一套完整协议栈的承载配置。
(3)配置3：数据承载配置对应的承载ID与第一信息的对应关系；或者，RLC承载配置对应的承载ID与第一信息的对应关系；
可选地，第一信息包括QoS流、QoS流列表、RLC承载配置索引、关联的承载配置索引中的至少一种。
可选地，数据承载配置对应的承载ID为信令无线承载(Signaling Radio Bearer，SRB)ID或数据无线承载(Data Radio Bearer，DRB)ID。
需要注意的是，第一终端可以获取上述三套配置中的任意一种，或者是上述三套配置的任意组合。本申请对此不加以限制。
可选地，获取候选中继承载配置列表包括以下方式中的至少一种：通过预配置方式获取候选中继承载配置列表；通过接收系统广播消息获取候选中继承载配置列表；通过接收RRC专有信令获取候选中继承载配置列表；通过接收第二终端发送的消息获取候选中继承载配置列表。
示例性的，获取候选中继承载配置列表包括以下方式中的至少一种：
·在第一终端处于网络覆盖外的情况下，通过预配置方式获取候选中继承载配置列表；
·在第一终端处于网络覆盖内且RRC空闲态的情况下，通过接收系统广播消息获取候选中继承载配置列表；
·在第一终端处于网络覆盖内且RRC非活跃态的情况下，通过接收系统广播消息获取候选中继承载配置列表；
·在第一终端处于网络覆盖内且RRC连接态的情况下，通过接收RRC专有信令获取候选中继承载配置列表；
·通过接收第二终端发送的PC5-RRC消息或SL-MAC CE或SCI，获取候选中继承载配置列表。
其中，第二终端是第一终端的一个对端终端。
在本申请实施例中，第二终端设备可以是远端终端，也可以是中继终端。远端终端和中继终端的含义可以参见图1所示实施例，在此不进行赘述。
即，第一终端为源端终端或远端终端，第二终端为中继终端；或，第一终端为中继终端，第二终端为源端终端或远端终端。也即，可以为从源端终端/远端终端向中继终端进行中继承载配置，也可以为从中继终端向源端终端/远端终 端进行中继承载配置。
可选地，第一终端通过接收第二终端发送的PC5-RRC消息/SL-MAC CE/SCI获取候选中继承载配置列表，在第一终端处于RRC连接态的情况下，可以将该候选中继承载配置列表中的候选中继承载配置上报给网络侧。网络侧可以拒绝第一终端上报的候选中继承载配置。在第二终端接收到网络侧的配置拒绝信息时，第二终端可以向第一终端发送配置拒绝信息，或者向第一终端发送重新配置请求。
可选地，获取第一终端的中继业务对应的第一候选中继承载配置列表，第一候选中继承载配置列表中的候选中继承载配置包含有中继指示；和/或，获取第一终端的非中继业务对应的第二候选中继承载配置列表，第二候选中继承载配置列表中的候选中继承载配置包含有非中继指示。即，针对第一终端的中继业务和非中继业务，可以分别获取候选中继承载配置列表。
在一些实施例中，第二终端基于QoS流ID与RLC承载配置，生成U2U承载配置序列。即，该U2U承载配置序列为第二终端根据QoS流ID和RLC承载配置序列生成的终端到终端承载配置序列。
示例性的，第二终端将QoS流ID与RLC承载配置序列进一步序列化，生成U2U承载配置序列。序列化的规则为将QoS流ID与该QoS流ID对应的RLC承载配置相结合，生成U2U承载配置序列，其中，U2U承载配置序列的标号与QoS流ID一一对应。
图5示出了生成U2U承载配置序列的序列化规则的示意图。如图所示，QoS流ID 1、QoS流ID 2、QoS流ID 3与RLC承载配置1对应；QoS流ID 4、QoS流ID 5、QoS流ID 6与RLC承载配置2对应；QoS流ID 7、QoS流ID 8与RLC承载配置3对应。本申请对QoS流ID与RLC承载配置的对应方式不加以限制。
序列化的过程例如QoS流ID 1与对应的RLC承载配置1相结合，生成U2U承载配置1；再例如，QoS流ID 2与对应的RLC承载配置1相结合，生成U2U承载配置2；再例如，QoS流ID 4与对应的RLC承载配置2相结合，生成U2U承载配置4，以此类推。
可选地，上述U2U承载配置序列携带在以下协议层子头中的至少一种：SRAP层；RLC层；MAC层。
需要说明的是，上述步骤420和步骤422的执行顺序不分先后，可以先执 行步骤420，再执行步骤422；或者，先执行步骤422，再执行步骤420；或者，步骤420和步骤422同时执行。本申请对此不加以限制。
步骤440：基于QoS流ID在候选中继承载配置列表中确定目标中继承载配置。
示例性的，候选中继承载配置列表中包含有候选中继承载及候选中继承载对应的具体的中继承载配置信息。第一终端基于SRAP报文中携带的与当前中继传输所使用的中继承载相对应的QoS流ID，在候选中继承载配置列表中确定目标中继承载配置。
进一步的，第一终端基于该目标中继承载配置进行U2U的中继传输。
可选地，在第二终端基于QoS流ID与RLC承载配置生成U2U承载配置序列的情况下，目标中继承载配置是基于QoS流ID和U2U承载配置序列确定的。例如，参考图5，在QoS流ID指示QoS流ID5时，即对应为U2U承载配置5，第一终端将U2U承载配置5对应的RLC承载配置2确定为目标中继承载配置。
需要注意的是，在终端到终端的中继传输中，前述候选中继承载配置列表可以通过任意组合生成。例如，在源端终端经由中继终端向远端终端传输数据的过程中，源端终端向中继终端进行中继承载配置时使用上述配置1，中继终端向远端终端进行中继承载配置使用上述配置1、配置2和配置3的组合；再例如，源端终端向中继终端进行中继承载配置时使用上述配置2，中继终端向远端终端进行中继承载配置使用上述U2U承载配置序列；再例如，源端终端向中继终端进行中继承载配置和中继终端向远端终端进行中继承载配置时都使用上述U2U承载配置序列，等等。本申请对此不加以限制。
综上所述，本实施例提供的技术方案，通过SRAP报文中携带的QoS流ID，在第一终端获取到的候选中继承载配置列表中确定目标中继承载配置，进而实现U2U的中继传输。
下述为本申请装置实施例，可以用于执行本申请方法实施例。对于本申请装置实施例中未披露的细节，请参照本申请方法实施例。
图6示出了本申请一个实施例提供的中继承载配置的确定装置的结构框图。该装置具有实现上述第一终端的方法示例的功能，所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该装置可以是上文介绍的第一终端，也可以设置在第一终端中。如图6所示，该装置可以包括以下模块：
接收模块520，用于接收侧行中继适配协议SRAP报文；
确定模块540，用于基于所述SRAP报文在候选中继承载配置列表中确定目标中继承载配置。
在一个可选的实施例中，所述SRAP报文携带有：承载标识ID；或，服务质量QoS流ID。
在一个可选的实施例中，所述目标中继承载配置基于所述承载ID在所述候选中继承载配置列表中确定。
在一个可选的实施例中，所述目标中继承载配置基于所述QoS流ID在所述候选中继承载配置列表中确定。
在一个可选的实施例中，所述接收模块520，还用于获取候选中继承载配置列表。
在一个可选的实施例中，所述候选中继承载配置列表中的候选中继承载配置，包括以下配置中的至少一种：侧行数据无线承载SL-DRB的数据承载配置；所述数据承载配置对应的承载ID与第一信息的对应关系；所述SL-DRB的无线链路控制RLC承载配置；所述RLC承载配置对应的承载ID与第一信息的对应关系；其中，所述第一信息包括QoS流、QoS流列表、RLC承载配置索引、关联的承载配置索引中的至少一种。
在一个可选的实施例中，所述数据承载配置包括以下中的至少一种：服务数据适配协议SDAP层的相关配置；分组数据聚合协议PDCP层的相关配置；数据承载配置索引。
在一个可选的实施例中，所述RLC承载配置包括以下中的至少一种：SRAP层的相关配置；RLC层的相关配置；媒体接入控制MAC层的相关配置；所述RLC承载配置索引；所述关联的承载配置索引。
在一个可选的实施例中，所述接收模块520，还用于以下中的至少一种：通过预配置方式获取所述候选中继承载配置列表；通过接收系统广播消息获取所述候选中继承载配置列表；通过接收RRC专有信令获取所述候选中继承载配置列表；通过接收第二终端发送的消息获取所述候选中继承载配置列表。
在一个可选的实施例中，所述接收模块520，还用于以下中的至少一种：在所述第一终端处于网络覆盖外的情况下，通过预配置方式获取所述候选中继承载配置列表；在所述第一终端处于网络覆盖内且无线资源控制RRC空闲态的情 况下，通过接收系统广播消息获取所述候选中继承载配置列表；在所述第一终端处于网络覆盖内且无线资源控制RRC非活跃态的情况下，通过接收系统广播消息获取所述候选中继承载配置列表；在所述第一终端处于网络覆盖内且无线资源控制RRC连接态的情况下，通过接收RRC专有信令获取所述候选中继承载配置列表；通过接收第二终端发送的PC5-RRC消息或侧行媒体接入控制控制单元SL-MAC CE或侧行控制信息SCI，获取所述候选中继承载配置列表。
在一个可选的实施例中，所述第一终端为源端终端或远端终端，所述第二终端为中继终端；或，所述第一终端为中继终端，所述第二终端为源端终端或远端终端。
在一个可选的实施例中，所述接收模块520，还用于获取所述第一终端的中继业务对应的第一候选中继承载配置列表，所述第一候选中继承载配置列表中包含有中继指示；和/或，获取所述第一终端的非中继业务对应的第二候选中继承载配置列表，所述第二候选中继承载配置列表中包含有非中继指示。
在一个可选的实施例中，所述QoS流ID携带在以下协议层子头中的至少一种：SRAP层；RLC层；MAC层。
在一个可选的实施例中，所述目标中继承载配置是基于所述QoS流ID和终端到终端U2U承载配置序列确定的，所述U2U承载配置序列为第二终端根据所述QoS流ID和RLC承载配置序列生成的终端到终端承载配置序列。
在一个可选的实施例中，所述U2U承载配置序列携带在以下协议层子头中的至少一种：SRAP层；RLC层；MAC层。
需要说明的一点是，上述实施例提供的装置在实现其功能时，仅以上述各个功能模块的划分进行举例说明，实际应用中，可以根据实际需要而将上述功能分配由不同的功能模块完成，即将设备的内容结构划分成不同的功能模块，以完成以上描述的全部或者部分功能。
关于上述实施例中的装置，其中各个模块执行操作的具体方式已经在有关该方法的实施例中进行了详细描述，此处将不做详细阐述说明。
请参考图7，其示出了本申请一个实施例提供的终端设备的结构示意图。该终端设备可以包括：处理器801、接收器802、发射器803、存储器804和总线805。
处理器801包括一个或者一个以上处理核心，处理器801通过运行软件程 序以及模块，从而执行各种功能应用以及信息处理。
接收器802和发射器803可以实现为一个收发器806，该收发器806可以是一块通信芯片。
存储器804通过总线805与处理器801相连。
存储器804可用于存储计算机程序，处理器801用于执行该计算机程序，以实现上述方法实施例中终端设备执行的各个步骤。
此外，存储器804可以由任何类型的易失性或非易失性存储设备或者它们的组合实现，易失性或非易失性存储设备包括但不限于：RAM(Random-Access Memory，随机存储器)和ROM(Read-Only Memory，只读存储器)、EPROM(Erasable Programmable Read-Only Memory，可擦写可编程只读存储器)、EEPROM(Electrically Erasable Programmable Read-Only Memory，电可擦写可编程只读存储器)、闪存或其他固态存储其技术，CD-ROM(Compact Disc Read-Only Memory，只读光盘)、DVD(Digital Video Disc，高密度数字视频光盘)或其他光学存储、磁带盒、磁带、磁盘存储或其他磁性存储设备。
其中，当终端设备实现为第一终端设备时，本申请实施例涉及的处理器和收发器，可以执行上述图2至图4任一所示的方法中，由第一终端执行的步骤，此处不再赘述。
在一种可能的实现方式中，当终端设备实现为第一终端设备时，
所述接收器802，用于接收SRAP报文；
所述处理器801，用于基于所述SRAP报文在候选中继承载配置列表中确定目标中继承载配置。
本申请实施例还提供了一种计算机可读存储介质，所述存储介质中存储有计算机程序，所述计算机程序用于被第一终端的处理器执行，以实现上述第一终端的中继承载配置的确定方法。
可选地，该计算机可读存储介质可以包括：ROM(Read-Only Memory，只读存储器)、RAM(Random-Access Memory，随机存储器)、SSD(Solid State Drives，固态硬盘)或光盘等。其中，随机存取记忆体可以包括ReRAM(Resistance Random Access Memory，电阻式随机存取记忆体)和DRAM(Dynamic Random Access Memory，动态随机存取存储器)。
本申请实施例还提供了一种芯片，所述芯片包括可编程逻辑电路和/或程序 指令，当所述芯片在第一终端上运行时，用于实现上述第一终端的中继承载配置的确定方法。
本申请实施例还提供了一种计算机程序产品或计算机程序，所述计算机程序产品或计算机程序包括计算机指令，所述计算机指令存储在计算机可读存储介质中，第一终端的处理器从所述计算机可读存储介质读取并执行所述计算机指令，以实现上述第一终端的中继承载配置的确定方法。
应理解，在本申请的实施例中提到的“指示”可以是直接指示，也可以是间接指示，还可以是表示具有关联关系。举例说明，A指示B，可以表示A直接指示B，例如B可以通过A获取；也可以表示A间接指示B，例如A指示C，B可以通过C获取；还可以表示A和B之间具有关联关系。
在本申请实施例的描述中，术语“对应”可表示两者之间具有直接对应或间接对应的关系，也可以表示两者之间具有关联关系，也可以是指示与被指示、配置与被配置等关系。
在本文中提及的“多个”是指两个或两个以上。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。字符“/”一般表示前后关联对象是一种“或”的关系。
另外，本文中描述的步骤编号，仅示例性示出了步骤间的一种可能的执行先后顺序，在一些其它实施例中，上述步骤也可以不按照编号顺序来执行，如两个不同编号的步骤同时执行，或者两个不同编号的步骤按照与图示相反的顺序执行，本申请实施例对此不作限定。
本领域技术人员应该可以意识到，在上述一个或多个示例中，本申请实施例所描述的功能可以用硬件、软件、固件或它们的任意组合来实现。当使用软件实现时，可以将这些功能存储在计算机可读介质中或者作为计算机可读介质上的一个或多个指令或代码进行传输。计算机可读介质包括计算机存储介质和通信介质，其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是通用或专用计算机能够存取的任何可用介质。
以上所述仅为本申请的示例性实施例，并不用以限制本申请，凡在本申请的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本申请的保护范围之内。

Claims (20)

  1. 一种中继承载配置的确定方法，其特征在于，所述方法由第一终端执行，所述方法包括：
    接收侧行中继适配协议SRAP报文；
    基于所述SRAP报文在候选中继承载配置列表中确定目标中继承载配置。
  2. 根据权利要求1所述的方法，其特征在于，所述SRAP报文携带有：
    承载标识ID；
    或，
    服务质量QoS流标识ID。
  3. 根据权利要求2所述的方法，其特征在于，所述目标中继承载配置基于所述承载ID在所述候选中继承载配置列表中确定。
  4. 根据权利要求2所述的方法，其特征在于，所述目标中继承载配置基于所述QoS流ID在所述候选中继承载配置列表中确定。
  5. 根据权利要求1至4任一所述的方法，其特征在于，所述方法还包括：
    获取所述候选中继承载配置列表。
  6. 根据权利要求1至4任一所述的方法，其特征在于，所述候选中继承载配置列表中的候选中继承载配置，包括以下配置中的至少一种：
    侧行数据无线承载SL-DRB的数据承载配置；
    所述数据承载配置对应的承载ID与第一信息的对应关系；
    所述SL-DRB的无线链路控制RLC承载配置；
    所述RLC承载配置对应的承载ID与第一信息的对应关系；
    其中，所述第一信息包括QoS流、QoS流列表、RLC承载配置索引、关联的承载配置索引中的至少一种。
  7. 根据权利要求6所述的方法，其特征在于，所述数据承载配置包括以下中的至少一种：
    服务数据适配协议SDAP层的相关配置；
    分组数据聚合协议PDCP层的相关配置；
    数据承载配置索引。
  8. 根据权利要求6所述的方法，其特征在于，所述RLC承载配置包括以下中的至少一种：
    SRAP层的相关配置；
    RLC层的相关配置；
    媒体接入控制MAC层的相关配置；
    所述RLC承载配置索引；
    所述关联的承载配置索引。
  9. 根据权利要求5所述的方法，其特征在于，所述获取所述候选中继承载配置列表，包括以下方式中的至少一种：
    通过预配置方式获取所述候选中继承载配置列表；
    通过接收系统广播消息获取所述候选中继承载配置列表；
    通过接收RRC专有信令获取所述候选中继承载配置列表；
    通过接收第二终端发送的消息获取所述候选中继承载配置列表。
  10. 根据权利要求9所述的方法，其特征在于，所述获取所述候选中继承载配置列表，包括以下方式中的至少一种：
    在所述第一终端处于网络覆盖外的情况下，通过预配置方式获取所述候选中继承载配置列表；
    在所述第一终端处于网络覆盖内且无线资源控制RRC空闲态的情况下，通过接收系统广播消息获取所述候选中继承载配置列表；
    在所述第一终端处于网络覆盖内且RRC非活跃态的情况下，通过接收系统广播消息获取所述候选中继承载配置列表；
    在所述第一终端处于网络覆盖内且RRC连接态的情况下，通过接收RRC 专有信令获取所述候选中继承载配置列表；
    通过接收第二终端发送的PC5-RRC消息或侧行媒体接入控制控制单元SL-MAC CE或侧行控制信息SCI，获取所述候选中继承载配置列表。
  11. 根据权利要求9所述的方法，其特征在于，
    所述第一终端为源端终端或远端终端，所述第二终端为中继终端；
    或，
    所述第一终端为中继终端，所述第二终端为源端终端或远端终端。
  12. 根据权利要求5所述的方法，其特征在于，所述获取候选中继承载配置列表，还包括：
    获取所述第一终端的中继业务对应的第一候选中继承载配置列表，所述第一候选中继承载配置列表中的候选中继承载配置包含有中继指示；
    和/或，
    获取所述第一终端的非中继业务对应的第二候选中继承载配置列表，所述第二候选中继承载配置列表中的候选中继承载配置包含有非中继指示。
  13. 根据权利要求4所述的方法，其特征在于，所述QoS流ID携带在以下协议层子头中的至少一种：
    SRAP层；
    RLC层；
    MAC层。
  14. 根据权利要求4所述的方法，其特征在于，所述目标中继承载配置是基于所述QoS流ID和终端到终端U2U承载配置序列确定的，所述U2U承载配置序列为第二终端根据所述QoS流ID和RLC承载配置序列生成的终端到终端承载配置序列。
  15. 根据权利要求14所述的方法，其特征在于，所述U2U承载配置序列携带在以下协议层子头中的至少一种：
    SRAP层；
    RLC层；
    MAC层。
  16. 一种中继承载配置的确定装置，其特征在于，所述装置包括：接收模块和确定模块；
    所述接收模块，用于接收侧行中继适配协议SRAP报文；
    所述确定模块，用于基于所述SRAP报文在候选中继承载配置列表中确定目标中继承载配置。
  17. 一种终端设备，其特征在于，所述终端设备包括收发器和处理器；
    所述收发器，用于接收侧行中继适配协议SRAP报文；
    所述处理器，用于基于所述SRAP报文在候选中继承载配置列表中确定目标中继承载配置。
  18. 一种计算机可读存储介质，其特征在于，所述存储介质中存储有计算机程序，所述计算机程序用于被处理器执行，以实现如权利要求1至15任一项所述的中继承载配置的确定方法。
  19. 一种芯片，其特征在于，所述芯片包括可编程逻辑电路和/或程序指令，当所述芯片运行时，用于实现如权利要求1至15任一项所述的中继承载配置的确定方法。
  20. 一种计算机程序产品或计算机程序，其特征在于，所述计算机程序产品或计算机程序包括计算机指令，所述计算机指令存储在计算机可读存储介质中，处理器从所述计算机可读存储介质读取并执行所述计算机指令，以实现如权利要求1至15任一项所述的中继承载配置的确定方法。
PCT/CN2022/106556 2022-07-19 2022-07-19 中继承载配置的确定方法、装置、设备及存储介质 WO2024016173A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/106556 WO2024016173A1 (zh) 2022-07-19 2022-07-19 中继承载配置的确定方法、装置、设备及存储介质

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/106556 WO2024016173A1 (zh) 2022-07-19 2022-07-19 中继承载配置的确定方法、装置、设备及存储介质

Publications (1)

Publication Number Publication Date
WO2024016173A1 true WO2024016173A1 (zh) 2024-01-25

Family

ID=89616825

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/106556 WO2024016173A1 (zh) 2022-07-19 2022-07-19 中继承载配置的确定方法、装置、设备及存储介质

Country Status (1)

Country Link
WO (1) WO2024016173A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105611642A (zh) * 2016-01-08 2016-05-25 宇龙计算机通信科技(深圳)有限公司 一种数据传输的配置方法、基站和用户设备
CN109155949A (zh) * 2017-01-09 2019-01-04 Lg 电子株式会社 无线通信中在网络之间的互通方法及其装置
US20200022194A1 (en) * 2017-03-31 2020-01-16 Huawei Technologies Co., Ltd. Relay communication method and relay communications apparatus and system
CN113573327A (zh) * 2020-04-28 2021-10-29 维沃移动通信有限公司 远端ue的传输方法、配置方法、装置及电子设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105611642A (zh) * 2016-01-08 2016-05-25 宇龙计算机通信科技(深圳)有限公司 一种数据传输的配置方法、基站和用户设备
CN109155949A (zh) * 2017-01-09 2019-01-04 Lg 电子株式会社 无线通信中在网络之间的互通方法及其装置
US20200022194A1 (en) * 2017-03-31 2020-01-16 Huawei Technologies Co., Ltd. Relay communication method and relay communications apparatus and system
CN113573327A (zh) * 2020-04-28 2021-10-29 维沃移动通信有限公司 远端ue的传输方法、配置方法、装置及电子设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "TP for 38.331 on CHO", 3GPP DRAFT; R2-1912636 - TP FOR 38.331 ON CHO, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Chongqing, P.R. China; 20191014 - 20191018, 3 October 2019 (2019-10-03), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051790675 *

Similar Documents

Publication Publication Date Title
US11438941B2 (en) Communication method and communications apparatus
CN109716700B (zh) 一种指示方法及相关设备
JP7270766B2 (ja) 無線ベアラ構成方法、装置及びシステム
WO2022017348A1 (zh) 侧行链路信令无线承载配置的方法和通信装置
WO2022052851A1 (zh) 一种服务质量QoS的监测方法
CN113508639B (zh) 一种用于中继通信的方法和装置
WO2017024909A1 (zh) 一种进行数据传输的方法和设备
CN116530208A (zh) 一种通信方法、装置及系统
CN115707036A (zh) 传输数据的方法和装置
WO2020200043A1 (zh) 通信方法和通信装置
US10701591B2 (en) Data transmission method, apparatus, and system
WO2020015733A1 (zh) D2d通信的方法和终端设备
US20240155418A1 (en) Method and apparatus for connecting qos flow based terminal in wireless communication system
US20230107139A1 (en) Relay discovery method and terminal
KR102657514B1 (ko) 무선 통신 시스템에서 복제된 데이터를 송수신하기 위한 방법 및 장치
WO2024016173A1 (zh) 中继承载配置的确定方法、装置、设备及存储介质
WO2023015454A1 (zh) 路径建立方法、选择方法、装置、终端设备及存储介质
CN113747367B (zh) 一种通信方法及通信装置
JP2020529148A (ja) データ複製をサポートする方法、送信側デバイスおよび受信側デバイス
WO2023015413A1 (zh) 针对sl的复制传输方法、装置、设备及存储介质
WO2023137579A1 (zh) 紧急业务的提供方法、装置、设备及存储介质
WO2024027636A1 (zh) 一种通信方法、通信装置及通信系统
WO2022237763A1 (zh) 信道监听方法与装置、终端和网络设备
WO2023065865A1 (zh) 一种通信方法及设备
WO2024074148A1 (zh) 通信方法、装置及系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22951451

Country of ref document: EP

Kind code of ref document: A1