RELAY BEARER ESTABLISHING METHOD AND COMMUNICATION APPARATUS
20230098258 · 2023-03-30
Assignee
Inventors
Cpc classification
H04W88/04
ELECTRICITY
H04W28/0268
ELECTRICITY
International classification
Abstract
A method includes receiving a first parameter set that is for establishing a relay radio link control RLC bearer and that is sent by a first terminal; and further receiving a first configuration message sent by a network device, where the first configuration message includes a second parameter set corresponding to the relay RLC bearer. The relay device establishes, based on the first parameter set received from the first terminal and the second parameter set obtained from the network device, a relay RLC bearer corresponding to a first link, where the first link is a link between the relay device and a second terminal.
Claims
1. A relay bearer establishing method, comprising: receiving an indication message sent by a first terminal, wherein the indication message comprises a first parameter set for establishing a relay radio link control (RLC) bearer; receiving a first configuration message sent by a network device, wherein the first configuration message comprises a second parameter set corresponding to the relay RLC bearer; and establishing, based on the first parameter set and the second parameter set, a relay RLC bearer corresponding to a first link, wherein the first link is a link between a relay device and a second terminal, and the first link is for data transmission between the first terminal and the second terminal.
2. The relay bearer establishing method according to claim 1, wherein the indication message further comprises a first quality of service (QoS) information set; and before receiving the first configuration message sent by the network device, the method further comprises: sending a first request message to the network device, to request the first configuration message of the relay RLC bearer, wherein the first request message comprises a target QoS information set, there is an association relationship between the target QoS information set and the first QoS information set, and there is a correspondence between the target QoS information set and the relay RLC bearer corresponding to the first link.
3. The relay bearer establishing method according to claim 1, wherein the first parameter set comprises a first configuration parameter set corresponding to the first link and a second configuration parameter set corresponding to a second link, and the second link is a link between the first terminal and the relay device; and establishing, based on the first parameter set and the second parameter set, the relay RLC bearer corresponding to the first link further comprises: establishing, based on the first configuration parameter set and the second parameter set, the relay RLC bearer corresponding to the first link, and establishing, based on the second configuration parameter set, a relay RLC bearer corresponding to the second link.
4. The relay bearer establishing method according to claim 3, wherein the first configuration parameter set and the second configuration parameter set are a same configuration parameter set.
5. The relay bearer establishing method according to claim 1, further comprising: receiving a configuration message that is for establishing a data radio bearer (DRB) and that is sent by the first terminal, wherein the configuration message for establishing the DRB comprises an identifier of the DRB, configuration information of a service data adaptation protocol (SDAP) layer, configuration information of a packet data convergence protocol (PDCP) layer, and configuration information of an RLC layer, and the relay RLC bearer comprises a correspondence between a relay RLC entity and the DRB; and forwarding, to the second terminal, the configuration message for establishing the data radio bearer (DRB).
6. The relay bearer establishing method according to claim 1, further comprising: receiving a second configuration message sent by the network device, wherein the second configuration message comprises a second transmit only parameter set corresponding to a relay RLC bearer corresponding to a second link, and the second link is a link between the first terminal and the relay device; and establishing, based on the first parameter set and the second transmit only parameter set, the relay RLC bearer corresponding to the second link, wherein the relay RLC bearer is a bi-directional RLC bearer.
7. The relay bearer establishing method according to claim 6, wherein before receiving the second configuration message sent by the network device, the method further comprises: sending a second request message to the network device, to request the second transmit only parameter set corresponding to the relay RLC bearer corresponding to the second link, wherein the second request message comprises a target QoS information set, and there is a correspondence between the target QoS information set and the relay RLC bearer corresponding to the second link.
8. An apparatus, comprising: at least one processor, and a memory storing instructions for execution by the at least one processor; wherein, when executed, the instructions cause the apparatus to perform operations comprising: receiving an indication message sent by a first terminal, wherein the indication message comprises a first parameter set for establishing a relay radio link control (RLC) bearer; receiving a first configuration message sent by a network device, wherein the first configuration message comprises a second parameter set corresponding to the relay RLC bearer; and establishing, based on the first parameter set and the second parameter set, a relay RLC bearer corresponding to a first link, wherein the first link is a link between a relay device and a second terminal, and the first link is for data transmission between the first terminal and the second terminal.
9. The apparatus according to claim 8, wherein the indication message further comprises a first quality of service (QoS) information set; and before receiving the first configuration message sent by the network device, when executed, the instructions further cause the apparatus to perform operations comprising: sending a first request message to the network device, to request the first configuration message of the relay RLC bearer, wherein the first request message comprises a target QoS information set, there is an association relationship between the target QoS information set and the first QoS information set, and there is a correspondence between the target QoS information set and the relay RLC bearer corresponding to the first link.
10. The apparatus according to claim 8, wherein the first parameter set comprises a first configuration parameter set corresponding to the first link and a second configuration parameter set corresponding to a second link, and the second link is a link between the first terminal and the relay device; and establishing, based on the first parameter set and the second parameter set, the relay RLC bearer corresponding to the first link further comprises: establishing, based on the first configuration parameter set and the second parameter set, the relay RLC bearer corresponding to the first link, and establishing, based on the second configuration parameter set, a relay RLC bearer corresponding to the second link.
11. The apparatus according to claim 10, wherein the first configuration parameter set and the second configuration parameter set are a same configuration parameter set.
12. The apparatus according to claim 8, wherein, when executed, the instructions further cause the apparatus to perform operations comprising: receiving a configuration message that is for establishing a data radio bearer (DRB) and that is sent by the first terminal, wherein the configuration message for establishing the DRB comprises an identifier of the DRB, configuration information of a service data adaptation protocol (SDAP) layer, configuration information of a packet data convergence protocol (PDCP) layer, and configuration information of an RLC layer, and the relay RLC bearer comprises a correspondence between a relay RLC entity and the DRB; and forwarding, to the second terminal, the configuration message for establishing the data radio bearer (DRB).
13. The apparatus according to claim 8, wherein, when executed, the instructions further cause the apparatus to perform operations comprising: receiving a second configuration message sent by the network device, wherein the second configuration message comprises a second transmit only parameter set corresponding to a relay RLC bearer corresponding to a second link, and the second link is a link between the first terminal and the relay device; and establishing, based on the first parameter set and the second transmit only parameter set, the relay RLC bearer corresponding to the second link, wherein the relay RLC bearer is a bi-directional RLC bearer.
14. The apparatus according to claim 13, wherein before receiving the second configuration message sent by the network device, when executed, the instructions further cause the apparatus to perform operations comprising: sending a second request message to the network device, to request the second transmit only parameter set corresponding to the relay RLC bearer corresponding to the second link, wherein the second request message comprises a target QoS information set, and there is a correspondence between the target QoS information set and the relay RLC bearer corresponding to the second link.
15. An apparatus,. comprising: at least one processor, and a memory storing instructions for execution by the at least one processor; wherein, when executed, the instructions cause the apparatus to perform operations comprising: determining configuration information for establishing a relay radio link control (RLC) bearer, wherein the configuration information of the relay RLC bearer comprises an identifier of the relay RLC bearer and a first parameter set; and sending the configuration information of the relay RLC bearer to a relay device.
16. The apparatus according to claim 15, wherein the first parameter set comprises a first configuration parameter set corresponding to a first link and a second configuration parameter set corresponding to a second link, the first link is a link between the relay device and a second terminal, and the second link is a link between a first terminal and the relay device.
17. The apparatus according to claim 16, wherein the first configuration parameter set and the second configuration parameter set are a same configuration parameter set.
18. The apparatus according to claim 17, wherein the first parameter set corresponds to a second link, and the second link is a link between a first terminal and the relay device.
19. The apparatus according to claim 15, wherein the configuration information further comprises a first QoS information set, and the first QoS information set is a QoS information set that corresponds when the first terminal transmits data to the second terminal.
20. The apparatus according to claim 19, wherein the first QoS information set comprises a first information set and a second information set, the first information set is a QoS information set that corresponds when the relay device transmits data through the first link, and the second information set is a QoS information set that corresponds when the first terminal transmits data through the second link.
Description
BRIEF DESCRIPTION OF THE DRAWINGS
[0037]
[0038]
[0039]
[0040]
[0041]
[0042]
[0043]
DETAILED DESCRIPTION OF THE EMBODIMENTS
[0044] The following describes the embodiments with reference to the accompanying drawings.
[0045] The term “and/or” may describe an association relationship between associated objects and may represent that there may be three relationships. For example, A and/or B may represent the following three cases: only A exists, both A and B exist, and only B exists. In addition, the character “/” may indicates an “or” relationship between the associated objects.
[0046] In the embodiments and the accompanying drawings, the terms “first”, “second”, and the like are intended to distinguish between similar objects but are not necessarily for describing an order or sequence. It should be understood that the data termed in such a way is interchangeable in appropriate circumstances, so that embodiments described herein can be implemented in orders other than the order illustrated or described herein. In addition, the terms “include”, “have”, and any variant thereof mean to cover the non-exclusive inclusion, for example, a process, method, system, product, or device that includes a list of steps or modules is not necessarily limited to those expressly listed steps or modules, but may include other steps or modules not expressly listed or inherent to such a process, method, product, or device.
[0047] For ease of understanding, terms are first described.
[0048] Radio link control (RLC) bearer: A network device (for example, a base station) may configure an RLC entity and a corresponding logical channel that are associated with a radio bearer (RB). The radio bearer may be a data radio bearer (DRB) or a signaling radio bearer (SRB). The RLC entity and the corresponding logical channel that are associated with the radio bearer are usually referred to as an RLC bearer. Configuration parameters of the RLC bearer include an RLC entity configuration, a logical channel identifier (LCID), a logical channel configuration, and an identifier of the associated radio bearer. For a sidelink interface, the network device may configure an RLC entity associated with the DRB and a logical channel, and the RLC entity and the logical channel that are associated with the sidelink radio bearer are referred to as a sidelink RLC bearer.
[0049] First link: a link between a relay device and a second terminal (a receiving side terminal).
[0050] Second link: a link between a first terminal (a transmitting side terminal) and the relay device.
[0051] (Tx&Rx common) Configuration parameter applicable to both a transmitting side and a receiving side: a parameter that the receiving side and the transmitting side need to understand consistently to ensure communication between the receiving side and the transmitting side. For example, Tx&Rx common RLC configuration parameters include an RLC mode (mode), an RLC sequence number (SN) length, and the like. The transmitting side and the receiving side are relative concepts. For example, for the second link, the first terminal is the transmitting side, and the relay device is the receiving side. The parameter that the transmitting side and the receiving side need to understand consistently is a parameter that the first terminal and the relay device understand consistently. For the first link, the relay device is the transmitting side, and the second terminal is the receiving side. The Tx&Rx common configuration parameter is a parameter that the relay device and the second terminal need to understand consistently. For an entire link between the first terminal and the second terminal, the Tx&Rx common configuration parameter is a parameter that the first terminal, the relay device, and the second terminal all need to keep understanding consistently. If the first terminal forwards data to the second terminal via the relay device, the Tx&Rx common configuration parameter is a parameter that the first terminal and the second terminal need to understand consistently. For example, the Tx&Rx common configuration parameter is a Tx&Rx common packet data convergence protocol (PDCP)-related configuration parameter and may include a PDCP SN length, a robust header compression (RoHC) configuration, and the like. It should be noted that “Tx&Rx common” is also abbreviated as “common”.
[0052] Bi-directional RLC bearer: Data can be sent and received over the bi-directional RLC bearer. For example, for the second link, if an RLC bearer corresponding to the second link is a bi-directional RLC bearer, the first terminal may send data to the relay device and may also receive data sent by the relay device (or the relay device may send data to the first terminal).
[0053] Unidirectional RLC bearer: A data flow direction is a direction from a transmitting end device to a receiving end device. For a transmitting end, data can only be sent over the unidirectional RLC bearer. For a receiving end, data can only be received over the unidirectional RLC bearer. If an RLC bearer corresponding to the second link is a unidirectional RLC bearer, the first terminal may send data to the relay device, but the relay device cannot send data to the first terminal over the unidirectional RLC bearer.
[0054] Transmit only (Tx only) parameter: a parameter related only to the transmitting side. For example, for the first link, when the relay device sends data to the second terminal, the relay device is the transmitting side, and the Tx only parameter corresponds to a parameter configured for the relay device. For example, a Tx only parameter of the RLC bearer includes, but is not limited to, T-PollRetransmit for controlling duration of a polling retransmission timer, a parameter pollPDU for controlling triggering of polling, pollByte, a maximum allowed quantity of times of automatic repeat request (ARQ) retransmission in RLC AM mode, and the like.
[0055] Quality of service (QoS) information: The QoS information may include at least one of a PC5 quality of service identifier (PQI), a PC5 QoS flow identifier (PFI), a logical channel priority, or other QoS parameters, for example, a delay, reliability, a throughput rate, and a packet loss rate, of service data transmitted over the RLC bearer.
[0056] Identifier of a relay RLC bearer: The identifier of the relay RLC bearer is for distinguishing RLC bearers. The identifier of the relay RLC bearer may be an index number of the relay RLC bearer. For example, index numbers may be 1, 3, 5, 7, and the like. Alternatively, the identifier may be an LCID corresponding to the relay RLC bearer. Alternatively, the identifier is an implicit representation of an index determined in order based on a quantity of relay RLC bearers. For example, if the first terminal indicates five relay RLC bearers in total, index numbers corresponding to the five relay RLC bearers are 0, 1, 2, 3, and 4.
[0057] Identifier of a terminal: The identifier of the terminal may be a destination layer-2 ID and identifies a unicast receiving side terminal. Alternatively, the identifier may be an identifier, for example, a local ID, allocated by the relay device for relay communication between the first terminal and the second terminal.
[0058] The embodiments may provide a relay bearer establishing method and a communication apparatus. The method is applied to a communication system. The communication system includes, but is not limited to, a 4.sup.th generation (4G) communication system, a 5G communication system, a 6G communication system, a system integrating a plurality of communication systems, or a future evolved communication system, for example, a long term evolution (LTE) system, a new radio (NR) system, a communication system related to the 3.sup.rd generation partnership project (3GPP), and another such communication system.
[0059] Refer to
[0060] the network device may include, but is not limited to: an evolved NodeB (eNB) in LTE, a gNodeB (gNB) or a transmission reception point (TRP) in NR, a base station that subsequently evolves in 3GPP. The base station may be a macro base station, a micro base station, a picocell base station, a small cell, a relay station, a balloon station, or the like. A plurality of base stations may support the foregoing networks using a same technology or may support the foregoing networks using different technologies. The base station may include one or more co-site or non-co-site TRPs. The network device may alternatively be a radio controller, a central unit (CU), and/or a distributed unit (DU) in a cloud radio access network (CRAN) scenario. That the network device is a base station is used as an example for description below.
[0061] A terminal is a device having a wireless transceiver function. The terminal sometimes may also be referred to as a terminal device, user equipment (UE), an access terminal device, a mobile station (MS), a mobile terminal (MT), a UE unit, a UE station, a mobile device, a UE terminal device, a wireless communication device, a machine terminal, a UE agent, a UE apparatus, or the like. The terminal may be a device that can perform sidelink communication, for example, a vehicle-mounted terminal, a terminal in self driving, a terminal in assisted driving, or a handheld terminal or a mobile phone that can perform V2X communication. The terminal may be an in-vehicle module, an onboard component, an automotive chip, or an on board unit that is built in a vehicle as one or more components or units.
[0062] A relay device may be a terminal, may be a drive test unit, or may be a wireless relay node (or a relay station). The terminal may be a mobile phone (mobile phone), a tablet computer (Pad), a handheld terminal, a wearable device, a vehicle-mounted terminal, a terminal in self driving, or a terminal in assisted driving. The terminal sometimes may also be referred to as a terminal device, UE, an access terminal device, an MS, an MT, a UE unit, a UE station, a mobile station, a mobile device, a UE terminal device, a wireless communication device, a machine terminal, a UE agent, a UE apparatus, or the like.
[0063] In the embodiments, a step performed by a relay device may be performed by the relay device, or a processor, a chip, or a chip system in the relay device, and a step performed by a first terminal may be performed by the first terminal, or a processor, a chip, or a chip system in the first terminal.
[0064] As shown in
[0065] Step 301: The first terminal sends, to the second terminal, configuration information for establishing an SL-DRB (also referred “o a” a “DRB”), where the configuration information for establishing the DRB includes an identifier of the DRB, configuration information of a service data adaptation protocol SDAP layer, configuration information of a packet data convergence protocol PDCP layer, and configuration information of an RLC layer. The relay RLC bearer includes a correspondence between a relay RLC entity and the DRB. The relay device receives the configuration information that is for establishing the DRB and that is sent by the first terminal, and forwards, to the second terminal, the configuration information for establishing the DRB, so that the second terminal can establish the DRB based on the configuration information of the DRB.
[0066] In this step, the configuration information that is for establishing the DRB and that is determined by the first terminal is used by the second terminal to establish the DRB. The first terminal may notify, by using a radio resource control (RRC) message, the second terminal of the configuration information of the SL-DRB that needs to be established. The message may be a sidelink RRC connection reconfiguration message (RRC Reconfiguration Sidelink). The identifier of the DRB may be an index of the DRB. The configuration information of SDAP may include a mapping relationship from a QoS flow to the DRB. The configuration information of PDCP includes Tx&Rx Common PDCP configuration information (for example, a PDCP SN length and a RoHC configuration). The configuration information of RLC includes a Tx&Rx Common RLC configuration (for example, an RLC mode and an RLC SN length), an LCID, and the like. The message is forwarded to the second terminal via the relay device. Configuration information of a relay RLC bearer for forwarding the message may be predefined in a protocol or preconfigured.
[0067] For example, in this step, a purpose of sending, by the first terminal to the second terminal, the configuration information for establishing the DRB is to establish the DRB by the second terminal. This step is not directly associated with step 302. Therefore, a time sequence of step 301 is not limited, and step 301 may be performed at any location after step 302.
[0068] Step 302: The first terminal determines the configuration information for establishing the relay RLC bearer, where the configuration information of the relay RLC bearer includes a first parameter set.
[0069] Optionally, the configuration information of the relay RLC bearer includes an identifier of the relay RLC bearer.
[0070] The first parameter set may include a common RLC configuration parameter (for example, including the RLC mode and the RLC SN length). In this embodiment, the first terminal determines a common RLC configuration parameter corresponding to the first link and a common RLC configuration parameter corresponding to the second link. It may alternatively be understood as that the first terminal determines a (Tx&Rx common) RLC configuration parameter applicable to both the relay device and the second terminal.
[0071] In a possible implementation, the first parameter set is one set. The first parameter set includes a configuration parameter and a parameter value corresponding to the configuration parameter, and the configuration parameter and the corresponding parameter value in the first parameter set are applicable to both the first link and the second link. For example, an example in which the configuration parameter is the RLC SN length is used. If the RLC SN length is 12 bits, it indicates that an RLC SN length corresponding to the second link is 12 bits, and an RLC SN length corresponding to the first link is also 12 bits.
[0072] In another possible implementation, the first parameter set may include two configuration parameter sets. The first parameter set includes a first configuration parameter set corresponding to the first link and a second configuration parameter set corresponding to the second link. A configuration parameter included in the first configuration parameter set is the same as a configuration parameter included in the second configuration parameter set, and parameter values corresponding to all configuration parameters may be the same or may be different. For example, the first configuration parameter set and the second configuration parameter set each include the RLC mode and the RLC SN length, an RLC SN length in the first configuration parameter set is 12 bits, and an RLC SN length in the second configuration parameter set is 15 bits. Alternatively, a configuration parameter in the first configuration parameter set and a parameter value of the configuration parameter are the same as a configuration parameter in the second configuration parameter set and a parameter value of the configuration parameter. That is, the first configuration parameter set and the second configuration parameter set are a same configuration parameter set. For example, RLC SN lengths in both of the first configuration parameter set and the second configuration parameter set are 12 bits.
[0073] Step 303: The relay device receives an indication message that is for indicating to establish the relay RLC bearer and that is sent by the first terminal, where the indication message includes configuration information of each to-be-transmitted relay RLC bearer, and the configuration information of the relay RLC bearer includes the first parameter set.
[0074] For understanding of the first parameter set, refer to the descriptions in step 302. Details are not described herein.
[0075] There is at least one relay RLC bearer. A quantity is not limited and is determined based on to-be-transmitted service data.
[0076] Optionally, the configuration information of the relay RLC bearer may include the identifier of the relay RLC bearer.
[0077] Optionally, the configuration information of the relay RLC bearer may further include a first QoS information set corresponding to the relay RLC bearer. In a possible implementation, the first QoS information set may be one set. In this implementation, the first QoS information set may be a corresponding QoS information set mapped by the first terminal to the relay RLC bearer for data transmission. The first QoS information set corresponds to the second link and the first link. For example, a delay parameter in the first QoS information set is used as an example. If a delay is 10 ms, it indicates that a delay of transmitting, to the second terminal through the second link and the first link, data sent by the first terminal is 10 ms. In another possible implementation, the first QoS information set may include two information sets, namely, a first information set and a second information set. The first information set corresponds to the first link. The first information set may be a QoS information set that corresponds when the relay device transmits data through the first link. The second information set corresponds to the second link. The second information set is a QoS information set that corresponds when the first terminal transmits data through the second link. A delay parameter in the QoS information set is used as an example. A delay in the first information set is 5 ms and a delay in the second information set is 5 ms.
[0078] Optionally, the configuration information of the relay RLC bearer may further include an LCID corresponding to the relay RLC bearer.
[0079] Optionally, the indication message may further include at least one of the following information:
[0080] (1) an identifier of the second terminal, where the identifier of the second terminal is used by the relay device to identify that the corresponding relay RLC bearer needs to be established for data transmission between the first terminal and the second terminal; and
[0081] (2) an indication field (for example, relay_config_indication), where the indication field is for notifying the relay device that the configuration information carried in the indication message is information for establishing the relay RLC bearer.
[0082] After receiving the indication message sent by the first terminal, the relay device determines, based on the indication message, the configuration information carried in the indication message, or the indication field carried in the indication message, that the relay RLC bearer needs to be established.
[0083] Step 304: The relay device sends a first request message to the network device, where the first request message requests the network device to configure a corresponding second parameter set (namely, a first transmit only parameter set) for a relay RLC bearer corresponding to the first link. The first request message includes information associated with the relay RLC bearer.
[0084] Optionally, the first request message includes an identifier of the relay RLC bearer and/or an identifier of the second terminal. The identifier of the second terminal notifies the network device that the requested second parameter set is the parameter set corresponding to the second link.
[0085] Optionally, the information associated with the relay RLC bearer includes a target QoS information set. There is an association relationship between the target QoS information set and the first QoS information set. There is a correspondence between the target QoS information set and the relay RLC bearer.
[0086] There may be the following several implementations of the target QoS information set: 1. If the first QoS information set is the set: (1) The target QoS information set may be the first QoS information set. (2) The target QoS information set may be an information set determined based on the first QoS information set. For example, if the delay in the first QoS information set is 10 ms (where the delay from the first terminal to the second terminal is 10 ms), the relay device may determine that a delay of the first link is 5 ms, a delay in the target QoS information set is 5 ms, and the target QoS information set corresponds to QoS information corresponding to the first link. 2. If the first QoS information set includes the two sets (namely, the first information set and the second information set), the target QoS information set may be the first information set (namely, QoS information corresponding to the first link).
[0087] For example, there is a correspondence between the target QoS information set and the Tx only parameter corresponding to the relay RLC bearer. The network device may configure, for the relay device based on the target QoS information set, the first transmit only parameter set (a Tx only parameter set) corresponding to the relay RLC bearer.
[0088] Optionally, the information associated with the relay RLC bearer may further include an RLC mode (mode).
[0089] Optionally, the information associated with the relay RLC bearer may further include an LCID corresponding to the relay RLC bearer.
[0090] Optionally, the content in the indication message in step 303 is directly reported to the network device by using the first request message, or the configuration information of the relay RLC bearer may be directly reported to the network device by using the first request message.
[0091] Optionally, the first request message includes a transmit only parameter configuration indication field (for example, relay_TxConfig_Request), and the indication field indicates to request the first transmit only parameter set (the Tx only parameter set) corresponding to the relay RLC bearer corresponding to the first link.
[0092] The network device receives the first request message sent by the relay device, and determines, based on the first request message, the information carried in the first request message, or the indication field carried in the first request message, that the Tx only parameter corresponding to the relay RLC bearer needs to be configured for the relay device.
[0093] It should be noted that step 304 is an optional step, and may not be performed, but step 305 is directly performed. The relay device may not need to send a request to the network device and the relay device may directly receive a first configuration message that is preconfigured by the network device for the relay device and that is for establishing the relay RLC bearer.
[0094] Step 305: The relay device receives the first configuration message sent by the network device, where the first configuration message includes the second parameter set corresponding to the relay RLC bearer.
[0095] The second parameter set includes the first transmit only parameter set (the Tx only parameter set). The first transmit only parameter set includes, but is not limited to, T-PollRetransmit for controlling duration of a polling retransmission timer, a parameter pollPDU for controlling triggering of polling, pollByte, a maximum allowed quantity of times of ARQ retransmission in RLC AM mode, and the like.
[0096] Optionally, the first configuration message includes an identifier of the relay RLC bearer.
[0097] The relay device may associate, based on the identifier of the relay RLC bearer in this step and the identifier of the relay RLC bearer in step 304, the first transmit only parameter set (the Tx only parameter) configured by the network device with the relay RLC bearer corresponding to the first link, where the first transmit only parameter set corresponds to the first link.
[0098] Optionally, the first configuration message may further include configuration information of a logical channel (LCH). The configuration information of the LCH includes at least one of an LCH priority, a parameter related to control execution of (LCP) (for example, the logical channel priority, a prioritized bit rate (PBR), and bucket size duration (BSD)), whether to enable a hybrid automatic repeat request (HARQ) feedback, a scheduling request (SR) resource associated with the LCH, and a logical channel group (LCG) to which the LCH belongs.
[0099] Step 306: The relay device establishes, based on the first parameter set and the second parameter set, the relay RLC bearer corresponding to the first link.
[0100] If the first parameter set is the set, the relay device establishes, based on a receive only parameter corresponding to the first parameter set (the Tx&Rx common RLC configuration parameter), a unidirectional RLC bearer corresponding to the second link, and establishes, based on the first parameter set and the first transmit only parameter set (the Tx only parameter) corresponding to the relay RLC bearer and received from the network device, the relay RLC bearer corresponding to the first link.
[0101] If the first parameter set includes the two sets, the first parameter set includes the first configuration parameter set and the second configuration parameter set, the relay device establishes, based on the first configuration parameter set received from the first terminal and the second parameter set received from the network device, the relay RLC bearer corresponding to the first link, and establishes, based on the second configuration parameter set, the unidirectional RLC bearer corresponding to the second link, so that the relay device can transfer, to the second terminal, data sent by the first terminal.
[0102] Step 307: The relay device feeds back a response message to the first terminal, where the response message notifies the first terminal that the relay RLC bearer has been established.
[0103] The response message may include an identifier of the relay RLC bearer, and the identifier is used by the terminal to identify which relay RLC bearers have been established.
[0104] Optionally, the unidirectional RLC bearer corresponding to the second link is established in step 306. When A relay RLC bearer corresponding to the second link is a bi-directional RLC bearer for receiving data and sending data, the first terminal may send data to the relay device through the second link, or the relay device may send data to the first terminal through the second link, step 30a (not shown in the figure) and step 30b (not shown in the figure) may be further included before step 306.
[0105] Step 30a: The relay device sends a second request message to the network device, where the second request message requests a second transmit only parameter set (a Tx only parameter set) corresponding to the relay RLC bearer corresponding to the second link. The second transmit only parameter set corresponds to the second link, and the second request message includes an identifier of the first terminal and information associated with the bi-directional RLC bearer. The identifier of the first terminal notifies the network device that a requested second transmitter side parameter corresponds to the second link. The information associated with the bi-directional RLC bearer includes target QoS information set, and there is a correspondence between the target QoS information set and the relay RLC bearer.
[0106] There may be the following several implementations of the target QoS information set: 1. If the first QoS information set is the set: (1) The target QoS information set may be the first QoS information set. (2) The target QoS information set may be an information set determined based on the first QoS information set. 2. If the first QoS information set includes the two sets (namely, the first information set and the second information set), the target QoS information set is the second information set (namely, QoS information corresponding to the second link).
[0107] Optionally, the information associated with the bi-directional RLC bearer includes an identifier of the relay RLC bearer.
[0108] Optionally, the information associated with the bi-directional RLC bearer may further include an RLC mode and/or an LCID corresponding to the bi-directional relay RLC bearer.
[0109] Optionally, the second request message includes a transmit only parameter configuration indication field (for example, relay_TxConfig_Request), and the indication field indicates that the relay device requests, from the network device, the second transmit only parameter set (a Tx only parameter) corresponding to the relay RLC bearer corresponding to the second link.
[0110] The network device receives the second request message sent by the relay device, and the network device determines, based on the second request message, the information carried in the second request message, or the indication field carried in the second request message, that Tx only parameters corresponding to these relay RLC bearers need to be configured for the relay device.
[0111] The relay device reports the target QoS information set to the network device, and the network device may configure, for the relay device based on the target QoS information set, the second transmit only parameter set corresponding to the second link.
[0112] Step 30b: The relay device receives a second configuration message sent by the network device, where the second configuration message includes the second transmit only parameter set corresponding to the relay RLC bearer corresponding to the second link.
[0113] Optionally, the second configuration message may further include an identifier of the relay RLC bearer, and the relay device may associate the second transmit only parameter set with the relay RLC bearer based on the identifier of the relay RLC bearer.
[0114] Optionally, the second configuration message further includes configuration information of an LCH. The configuration information of the LCH includes an LCH priority, a parameter related to LCP (for example, the logical channel priority, a PBR, and BSD), whether to enable a HARQ feedback, an SR resource associated with the LCH, an LCG to which the LCH belongs, and the like.
[0115] The second transmitter side parameter set includes, but is not limited to, T-PollRetransmit, pollPDU, pollByte, a maximum allowed quantity of times of ARQ retransmission in RLC AM mode, and the like.
[0116] When the relay RLC bearer corresponding to the second link is the bi-directional bearer, in step 306, the relay device establishes, based on the first parameter set and the second transmit only parameter set, the relay RLC bearer corresponding to the second link.
[0117] If the first parameter set is one set, the relay device establishes, based on the receive only parameter corresponding to the first parameter set (the RLC configuration parameter of Tx&Rx common) and the second transmit only parameter set, the bi-directional relay RLC bearer corresponding to the second link.
[0118] If the first parameter set includes the two sets, the first parameter set includes the first configuration parameter set and the second configuration parameter set, the relay device establishes, based on the second configuration parameter set and the second transmit only parameter set, the bi-directional RLC bearer corresponding to the second link, so that the relay device can send data to the first terminal over the bi-directional RLC bearer corresponding to the second link.
[0119] It should be noted that the foregoing process is described by using an example in which the first terminal sends data to the second terminal via the relay device. Actually, when the second terminal sends data to the first terminal via the relay device, a corresponding relay RLC bearer may also be established. The foregoing steps may also be used, but execution entities of the steps need to be correspondingly adjusted. For example, in step 302, the second terminal determines configuration information for establishing an RLC bearer. In step 303, the second terminal sends an indication message to the relay device. In step 304, the relay device feeds back a response message to the second terminal. In step 301, the second terminal sends, to the first terminal, the configuration information for establishing the DRB.
[0120] A time sequence of the foregoing steps may be adjusted based on an actual situation. For example, the time sequence of step 301 is not limited. Step 30a and step 304 may be in one message, for example, the first request message. The first request message includes the identifier of the first terminal and the identifier of the second terminal, and the first request message requests the first transmit only parameter set corresponding to the first link and the second transmit only parameter set corresponding to the second link. Step 30b and step 305 may be in one configuration message. For example, the first configuration message includes the first transmit only parameter set corresponding to the first link and the second transmit only parameter set corresponding to the second link. Step 307 is an optional step and may not be performed. Step 30a and step 30b are also optional steps and may not be performed. For example, when the first terminal needs to establish only the unidirectional RLC bearer, step 30a and step 30b may not be performed.
[0121] In this embodiment, the relay device receives the indication message sent by the first terminal, where the indication message includes configuration information for establishing the relay radio link control RLC bearer, and the configuration information of the relay RLC bearer includes the identifier of the relay RLC bearer and the first parameter set. The first parameter set is the (Tx&Rx common) configuration parameter applicable to both the transmitting side and the receiving side, the first parameter set corresponds to the first link and the second link, and the Tx&Rx common configuration parameter is the parameter that the relay device and the second terminal need to understood consistently. The relay device receives the first configuration message sent by the network device, where the first configuration message includes the identifier of the relay RLC bearer and the second parameter set corresponding to the relay RLC bearer. The second parameter set includes the first transmit only parameter set corresponding to the first link. The relay device may establish, based on the first parameter set and the second parameter set, the relay RLC bearer corresponding to the first link, so that the relay device can forward the data sent by the first terminal to the second terminal. In this embodiment, the first terminal determines the Tx&Rx common configuration parameter of the relay RLC bearer applicable to both the relay device and the second terminal. Both the configuration parameter of the relay RLC bearer corresponding to the first link and the configuration parameter of the relay RLC bearer corresponding to the second link are determined. The configuration parameters corresponding to the first link and the second link are well adapted to better ensure, over the relay RLC bearer, forwarding of service data.
[0122] As shown in
[0123] Step 401: The first terminal sends, to the second terminal, the configuration information for establishing the DRB, where the configuration information for establishing the DRB is forwarded by the relay device to the second terminal. The relay device may receive the configuration information that is for establishing the DRB and that is sent by the first terminal, and may forward the configuration information to the second terminal.
[0124] The configuration information for establishing the DRB includes an identifier of the DRB, configuration information of a service data adaptation protocol SDAP layer, and configuration information of a packet data convergence protocol PDCP layer but does not include the configuration information of the RLC layer and configuration information of an LCH. The identifier of the DRB may be an index number of the DRB.
[0125] A configuration of a relay RLC bearer used by the relay device to forward the message may be predefined in a protocol or preconfigured.
[0126] A difference between this step and step 301 in the embodiment corresponding to
[0127] For understanding of this step, refer to step 301 in the embodiment corresponding to
[0128] For example, in this step, a purpose of sending, by the first terminal to the second terminal, the configuration information for establishing the DRB is to establish the DRB by the second terminal. This step is not directly associated with step 402. Therefore, a time sequence of step 401 is not limited, and step 401 may be performed at any location after step 402.
[0129] Step 402: The first terminal determines configuration information for establishing a relay radio link control RLC bearer, where the configuration information of the relay RLC bearer includes the second configuration parameter set corresponding to the second link.
[0130] A difference between this step and step 302 in the embodiment corresponding to
[0131] Optionally, the configuration information of the relay RLC bearer may further include an identifier of the relay RLC bearer.
[0132] Step 403: The relay device receives an indication message sent by the first terminal, where the indication message includes the configuration information for establishing the relay RLC bearer, and the configuration information of the relay RLC bearer includes the identifier of the relay RLC bearer, an identifier of a DRB associated with the relay RLC bearer, and the second configuration parameter set corresponding to the second link.
[0133] A difference between this step and step 303 in the embodiment corresponding to
[0134] In step 401, the configuration information that is for establishing the DRB and that is sent by the first terminal to the second terminal does not include the configuration information of the RLC layer. Therefore, a correspondence between the DRB and an RLC entity is not included. Therefore, a function of the identifier of the DRB associated with the relay RLC bearer is as follows: When sending, to the second terminal, configuration information of an RLC bearer corresponding to the DRB, the relay device needs to send the identifier of the DRB to the second terminal, so that the second terminal can associate, based on the identifier of the DRB, the configuration information that is of the RLC bearer and that is indicated by the relay device with the corresponding DRB.
[0135] The configuration information of the relay RLC bearer may further include a first QoS information set corresponding to the relay RLC bearer.
[0136] Optionally, the configuration information of the relay RLC bearer may further include an LCID corresponding to the relay RLC bearer.
[0137] Optionally, the indication message may further include an identifier of the second terminal and/or an indication field.
[0138] For understanding of the first QoS information set, the identifier of the relay RLC bearer, the identifier of the second terminal, and the indication field (relay_config_indication) in this step, refer to step 303 in the embodiment corresponding to
[0139] Step 404: The relay device sends a first request message to the network device, to request a target parameter set of a relay RLC bearer corresponding to the first link. The first request message includes the identifier of the second terminal and information associated with the relay RLC bearer. The identifier of the second terminal notifies the network device that the target parameter set corresponds to the first link. The information associated with the relay RLC bearer may include a target QoS information set. There is an association relationship between the target QoS information set and the first QoS information set. There is a correspondence between the target QoS information set and the relay RLC bearer. For understanding of the target QoS information set, refer to step 304 in the embodiment corresponding to
[0140] The target parameter set includes a first configuration parameter set corresponding to the first link and a first transmit only parameter set (a Tx only parameter) corresponding to the first link.
[0141] In this embodiment, the first terminal determines the second configuration parameter set (namely, the Tx&Rx common RLC configuration parameter) corresponding to the second link, and the first configuration parameter set (namely, a Tx&Rx common RLC configuration parameter) corresponding to the first link needs to be obtained from the network device.
[0142] Optionally, the first request message may further include an identifier of the relay RLC bearer.
[0143] Optionally, the information associated with the relay RLC bearer may further include an RLC mode (mode).
[0144] Optionally, the information associated with the relay RLC bearer may further include an LCID corresponding to the relay RLC bearer.
[0145] Optionally, the first request message may include a transmit only parameter configuration indication field (for example, relay_TxALLConfig_Request), and the indication field indicates that the relay device requests the first configuration parameter set and the first transmit only parameter set (the Tx only parameter) that are of the relay RLC bearer corresponding to the first link. The network device receives the first request message sent by the relay device, and determines, based on the first request message, the information carried in the first request message, or the indication field carried in the first request message, that the first configuration parameter set and the first transmit only parameter set that correspond to the relay RLC bearer need to be configured for the relay device.
[0146] A difference between this step and step 304 in the embodiment corresponding to
[0147] Step 405: The relay device receives a first configuration message sent by the network device, where the first configuration message includes the target parameter set of the relay RLC bearer corresponding to the first link.
[0148] The target parameter set includes the first configuration parameter set and the first transmit only parameter set that correspond to the first link.
[0149] Optionally, the first configuration message includes an identifier of the relay RLC bearer. The relay device associates, based on the identifier of the relay RLC bearer in this step and the identifier of the relay RLC bearer in step 404, the first configuration parameter set and the first transmit only parameter set that are configured by the network device with the relay RLC bearer corresponding to the first link.
[0150] Optionally, the first configuration message may further include an identifier of the second terminal. In this case, the relay device may determine, based on the identifier of the second terminal and the identifier of the relay RLC bearer, that the target parameter set configured by the network device is the relay RLC bearer corresponding to the first link.
[0151] Optionally, the first configuration message may further include configuration information of the LCH. For understanding of the configuration information of the LCH, refer to step 305 in the embodiment corresponding to
[0152] For understanding of the first transmit only parameter set in this step, refer to step 305 in the embodiment corresponding to
[0153] Step 406: Establish, based on the target parameter set, the relay RLC bearer corresponding to the first link.
[0154] The relay device establishes, based on the target parameter set received from the network device, a unidirectional RLC bearer corresponding to the first link, and establishes, based on the second configuration parameter set received from the first terminal, a unidirectional RLC bearer corresponding to the second link, so that the relay device can transfer, to the second terminal, data sent by the first terminal.
[0155] Step 407: The relay device feeds back a response message to the first terminal, where the response message notifies the first terminal that the relay RLC bearer has been established.
[0156] Optionally, the response message includes an identifier of the relay RLC bearer and/or an identifier of the DRB. The identifier of the relay RLC bearer and/or the identifier of the DRB notify/notifies the first terminal which relay RLC bearers have been established.
[0157] Step 408: The relay device sends a third configuration message to the second terminal, where the third configuration message includes the first configuration parameter set, an identifier of the DRB, and an identifier of the RLC bearer.
[0158] Optionally, configuration information of the RLC bearer corresponding to the DRB may further include an LCID.
[0159] A purpose of sending, by the relay device to the second terminal, the configuration information of the RLC bearer corresponding to the DRB is to indicate the second terminal to establish the DRB. The second terminal associates, with the corresponding DRB based on the identifier of the DRB (for example, may be the index number of the DRB), the configuration information that is of the RLC bearer and that is indicated by the relay device. The second terminal may establish the corresponding DRB based on the configuration information of SDAP and the configuration information of PDCP that are indicated by the first terminal, and the configuration information that is of the RLC bearer and that is indicated by the relay device.
[0160] It may be understood that, in the embodiment corresponding to
[0161] Step 40a: The relay device sends a second request message to the network device, where the second request message requests a second transmit only parameter set corresponding to the bi-directional RLC bearer corresponding to the second link, the second request message may include an identifier of the first terminal, an identifier of the relay RLC bearer, and target QoS information set, and there is a correspondence between the target QoS information set and the relay RLC bearer.
[0162] For understanding of this step, refer to step 30a in the embodiment corresponding to
[0163] Step 40b: The relay device receives a second configuration message sent by the network device, where the second configuration message includes the second transmit only parameter set corresponding to the bi-directional RLC bearer corresponding to the second link.
[0164] For understanding of this step, refer to step 30b in the embodiment corresponding to FIG. 3. Details are not described herein.
[0165] In step 406, the relay device establishes, based on the second configuration parameter set received from the first terminal and the second transmit only parameter set, a bi-directional relay RLC bearer corresponding to the first link, so that the relay device can feed back data to the first terminal through the second link.
[0166] It should be noted that the foregoing process is described by using an example in which the first terminal sends data to the second terminal via the relay device. Actually, when the second terminal sends data to the first terminal via the relay device, a corresponding relay RLC bearer may also be established. The foregoing steps may also be used, but execution entities of the steps need to be correspondingly adjusted. For example, in step 402, the second terminal determines configuration information for establishing an RLC bearer. In step 403, the second terminal sends an indication message to the relay device. In step 404, the relay device feeds back a response message to the second terminal. In step 401, the second terminal sends, to the first terminal, the configuration information for establishing the DRB.
[0167] A time sequence of the foregoing steps may be adjusted based on an actual situation. For example, a time sequence of step 401 is not limited. Step 40a and step 404 may be in one request. Step 40b and step 405 may be in one configuration message. Step 407 is an optional step and may not be performed. Step 408 may be performed at any location after step 405. Step 40a and step 40b are also optional steps and may not be performed. For example, when the first terminal needs to establish only a unidirectional RLC bearer, step 40a and step 40b may not be performed.
[0168] In an optional implementation, refer to
[0169] In this embodiment, the first terminal determines only the Tx&Rx common RLC configuration parameter (the second configuration parameter set) corresponding to the second link. The relay device receives the second configuration parameter set from the first terminal. The relay device obtains the target parameter set from the network device. The target parameter set includes the Tx&Rx common RLC configuration parameter and the first transmit only parameter set that correspond to the first link. Because the network device (for example, a base station) connected to the relay device needs to allocate a resource for transmission between the relay device and the second terminal, it is appropriate for the network device to determine the common RLC configuration parameter corresponding to the first link. This can avoid additional complexity caused by determining the common RLC configuration parameter by the first terminal to base station scheduling. The relay device establishes the relay RLC bearer of the second link based on the second configuration parameter set received from the first terminal, and the relay device establishes, based on the target parameter set, the relay RLC bearer corresponding to the first link, so that the relay device can forward, by using the relay RLC bearer, data sent by the first terminal to the second terminal.
[0170] For example, in the embodiments, in step 303 and step 301 in the embodiment corresponding to
[0171] For example, in the embodiments, for a same relay RLC bearer, the identifier of the relay RLC bearer carried in the indication message received by the relay device and the identifier of the relay RLC bearer reported by the relay device to the network device indicate the same relay RLC bearer, but representation manners may be different. For example, the identifier of the relay RLC bearer is an index number. For example, in step 303 (or step 403) and step 304 (or step 404), for a relay RLC bearer corresponding to an SL-DRB, an index number of the relay RLC bearer carried in the indication message in step 304 (or step 404) may be different from an index number of the RLC bearer carried in the request in step 304 (or step 404). For example, for the relay RLC bearer corresponding to the SL-DRB, the index number of the RLC bearer carried in the indication message in step 303 (or step “0”) is “1”, and the index number of the RLC bearer reported by the relay device to the network device in the request message in step 304 (or step “0”) is “2”. The relay device only needs to determine a correspondence between the index number of the relay RLC bearer indicated by the first terminal and the index number of the RLC bearer reported to the network device.
[0172] It should be noted that, in the embodiments of, a sequence of the steps may be adjusted for implementation. This is not limited. It should be understood that performing some steps in the figure or adjusting a sequence of the steps for implementation shall fall within the scope of the embodiments.
[0173] Corresponding to the methods provided in the foregoing method embodiments, the embodiments may further provide corresponding apparatuses. The apparatuses include corresponding modules configured to perform the foregoing embodiments. The module may be software, hardware, or a combination of the software and the hardware.
[0174] As shown in
[0175] The apparatus 600 may include one or more processors 601. The processor 601 may also be referred to as a processing unit and may implement a control function. The processor 601 may be a general-purpose processor, a dedicated processor, or the like. For example, the processor 601 may be a baseband processor or a central processing unit. The baseband processor may be configured to process a communication protocol and communication data. The central processing unit may be configured to control the communication apparatus (for example, a base station, a baseband chip, a terminal, a terminal chip, a DU, or a CU), execute a software program, and process data of the software program.
[0176] The processor 601 may alternatively store instructions and/or data 603, and the instructions and/or data 603 may be run by the processor, to enable the apparatus 600 to perform the methods in the foregoing method embodiments.
[0177] The processor 601 may include a transceiver unit configured to implement receiving and sending functions. For example, the transceiver unit may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, the interface, or the interface circuit configured to implement the receiving and sending functions may be separated or may be integrated together. The transceiver circuit, the interface, or the interface circuit may be configured to read and write code/data, or the transceiver circuit, the interface, or the interface circuit may be configured to transmit or transfer a signal.
[0178] The apparatus 600 may include a circuit, and the circuit may implement the sending, receiving, or communication function in the foregoing method embodiments.
[0179] Optionally, the apparatus 600 may include one or more memories 602. The memory may store instructions 604. The instructions may be run on the processor, so that the apparatus 600 performs the methods in the foregoing method embodiments. Optionally, the memory may further store data. Optionally, the processor may also store instructions and/or data. The processor and the memory may be separately disposed or may be integrated together.
[0180] Optionally, the apparatus 600 may further include a transceiver 605 and/or an antenna 606. The processor 601 may be referred to as a processing unit and may control the apparatus 600. The transceiver 605 may be referred to as a transceiver unit, a transceiver, a transceiver circuit, a transceiver apparatus, a transceiver module, or the like, and is configured to implement a transceiver function.
[0181] Optionally, the apparatus 600 in this embodiment may be configured to perform the methods performed by the relay device in
[0182] As shown in
[0183] One or more modules in
[0184] The apparatus has a function of implementing the relay device in the embodiments. For example, the apparatus includes a corresponding module, unit, or means used by the relay device to perform the steps related to the relay device in embodiments. The function, the unit, or the means may be implemented by software or hardware, may be implemented by hardware executing corresponding software, or may be implemented by a combination of software and hardware. For details, further refer to the corresponding descriptions in the foregoing corresponding method embodiments. Alternatively, the apparatus has a function of implementing the first terminal in the embodiments. For example, the apparatus includes a corresponding module, unit, or means used by the first terminal to perform the steps related to the terminal in the embodiments. The function, the unit, or the means may be implemented by software or hardware, may be implemented by hardware executing corresponding software, or may be implemented by a combination of software and hardware. For details, further refer to the corresponding descriptions in the foregoing corresponding method embodiments.
[0185] In an optional implementation, the modules in the communication apparatus 700 in this embodiment may be configured to perform the methods performed by the relay device in
[0186] In a possible embodiment, the apparatus 700 may include the processing module 702 and the transceiver module 701.
[0187] The transceiver module 701 is configured to receive an indication message sent by a first terminal, where the indication message includes configuration information for establishing a relay radio link control RLC bearer, and the configuration information of the relay RLC bearer includes a first parameter set.
[0188] The transceiver module 701 is further configured to receive a first configuration message sent by a network device, where the first configuration message includes a second parameter set corresponding to the relay RLC bearer.
[0189] The processing module 702 is configured to establish, based on the first parameter set and the second parameter set, a relay RLC bearer corresponding to a first link, where the first link is a link between a relay device and a second terminal, and the first link is for data transmission between the first terminal and the second terminal.
[0190] Further, the transceiver module 701 is configured to perform step 303, step 304, step 305, step 307, step 30a, and step 30b that correspond to
[0191] The transceiver module 701 may be configured to receive a first configuration message sent by a network device, where the first configuration message includes a target parameter set of a relay RLC bearer corresponding to a first link; and the processing module 702 is configured to establish, based on the target parameter set, the relay RLC bearer corresponding to the first link, where the first link is a link between a relay device and a second terminal, and the first link is for data transmission between a first terminal and the second terminal.
[0192] Further, the transceiver module 701 is configured to perform step 403, step 404, step 405, step 407, step 408, step 40a, step 40b, and step 409 that correspond to
[0193] In an optional implementation, the modules in the apparatus 700 in this embodiment may be configured to perform the methods performed by the first terminal in
[0194] The communication apparatus 700 may include the processing module 702 and the transceiver module 701.
[0195] The processing module 702 is configured to determine configuration information for establishing a relay RLC bearer, where the configuration information of the relay RLC bearer includes a first parameter set.
[0196] The transceiver module 701 is configured to send, to a relay device, the configuration information for establishing the relay RLC bearer.
[0197] Further, the processing module 702 is configured to perform step 302 in the method embodiment corresponding to
[0198] The embodiments may further provide a non-transitory computer-readable medium. The non-transitory computer-readable medium stores a computer program. When the computer program is executed by a computer, the function in any one of the foregoing method embodiments is implemented.
[0199] The embodiments may further provide a computer program product. When the computer program product is executed by a computer, the function in any one of the foregoing method embodiments is implemented.
[0200] An element represented in a singular form is intended to represent “one or more”, but does not represent “only one”, unless otherwise specified. “Unless otherwise specified, “at least one” is intended to represent “one or more”, and “a plurality of” is intended to represent “two or more”.
[0201] It may be understood that, in the embodiments, “when” and “if” both mean that the apparatus performs corresponding processing in an objective situation, are not intended to limit time, do not require the apparatus to necessarily have a determining action during implementation, and do not mean other limitation.
[0202] It may be understood that, in the embodiments, “B corresponding to A” indicates that B is associated with A, and B may be determined based on A. However, it should be further understood that determining B based on A does not mean that B is determined based only on A. That is, B may alternatively be determined based on A and/or other information.
[0203] For example, in the embodiments, the “parameter set” may be understood as a group of parameters or may be understood as one or more parameters.
[0204] When the apparatus is a chip in a terminal, the chip includes a processing unit and a communication unit. The processing unit may be, for example, a processor. The communication unit may be, for example, an input/output interface, a pin, or a circuit. The processing unit may execute computer-executable instructions stored in a storage unit, so that the chip in the terminal performs the wireless communication method in any implementation of the first aspect. Optionally, the storage unit is a storage unit in the chip, for example, a register or a buffer, or the storage unit may be a storage unit in the terminal but outside the chip, for example, a read-only memory (ROM), another type of static storage device capable of storing static information and instructions, or a random access memory (RAM).
[0205] The processor mentioned anywhere above may be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling program execution of the wireless communication method according to the first aspect.
[0206] It may be clearly understood by a person skilled in the art that, for the purpose of convenient and brief description, for a detailed working process of the foregoing system, apparatus, and unit, refer to a corresponding process in the foregoing method embodiments. Details are not described herein again.
[0207] In the several embodiments, it should be understood that the system, apparatus, and method may be implemented in other manners. For example, the foregoing apparatus embodiments are merely examples. For example, division into the units is merely logical function division and may be other division during actual implementation. For example, a plurality of units or components may be combined or integrated into another system, or some features may be ignored or not performed. In addition, the displayed or discussed mutual couplings or direct couplings or communication connections may be implemented through some interfaces. The indirect couplings or communication connections between the apparatuses or units may be implemented in electrical, mechanical, or other forms.
[0208] The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, that is, may be located in one position, or may be distributed on a plurality of network units. Some or all of the units may be selected based on actual requirements to achieve the objectives of the solutions in embodiments.
[0209] In addition, functional units in the embodiments may be integrated into one processing unit, each of the units may exist alone physically, or two or more units may be integrated into one unit. The integrated unit may be implemented in a form of hardware or may be implemented in a form of a software functional unit.
[0210] When the integrated unit is implemented in the form of the software functional unit and sold or used as an independent product, the integrated unit may be stored in a non-transitory computer-readable storage medium. Based on such an understanding, the embodiments essentially, or the part contributing to the prior art, may be implemented in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for instructing a computer device (which may be a personal computer, a server, a network device, or the like) to perform all or some of the steps of the methods in embodiments. The foregoing storage medium includes: any medium that can store program code, such as a USB flash drive, a removable hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disc.
[0211] The foregoing descriptions are merely implementations, but the scope of the embodiments is not limited thereto. Any variation or replacement readily figured out by a person skilled in the art shall fall within the scope of the embodiments.