A communication method and apparatus

Abstract

The application provides a communication method and device. The method comprises: a first terminal device obtaining a first configuration from a network device, the first configuration comprising a first radio link control bearer configuration, the first radio link control bearer configuration having an association relationship with a first carrier, the first radio link control bearer configuration being one of a plurality of radio link control bearer configurations corresponding to a packet data convergence layer protocol entity configuration, the first carrier being a carrier corresponding to a terminal device performing single-carrier communication, and multicasting or broadcasting data corresponding to a first radio link control bearer entity established by the first radio link control bearer configuration on the first carrier. According to the association relationship between the first radio link control bearer configuration and the first carrier, the first terminal device can multicast or broadcast data to receiving terminal devices that do not support sidelink carrier aggregation through the first radio link control bearer entity and using the first carrier, thereby improving the quality of sidelink communication.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a communication method and apparatus. Background Technology

[0002] In wireless communication systems, terminal devices (or user equipment) can communicate directly with each other via sidelink (SL) technology. A typical application scenario for SL communication is vehicle-to-everything (V2X) technology. In V2X, each vehicle is a terminal device, and data can be transmitted directly between them using SL technology without going through a network, effectively reducing communication latency.

[0003] To further improve the reliability of SL communication, researchers in the industry began to study terminal devices supporting SL carrier aggregation (CA) in later versions of the 5th generation (5G) (or new radio (NR)) communication protocol (such as Rel-18 or Rel-18+). However, in Rel-16 and Rel-17 versions of the 5G communication protocol, terminal devices do not support SL CA. Terminal devices that do not support SL CA can only perform SL communication on a single carrier. Therefore, when a terminal device supporting SL CA needs to communicate with a terminal device that does not support SL CA, if the terminal device supporting SL CA chooses to transmit SL data on multiple carriers, the terminal device that does not support SL CA may not be able to receive the SL transmission from the terminal device that supports SL CA, thus degrading the quality of SL communication. Summary of the Invention

[0004] This application provides a communication method and apparatus for improving the quality of sidelink communication.

[0005] Firstly, this application provides a communication method that can be implemented through data interaction between multiple communication devices (such as a first communication device and a second communication device). Optionally, the first communication device may be a first terminal device or a component (such as a chip, chip system, or circuit) capable of supporting the functions required for the first terminal device to implement the method. The second communication device may be a network device or a component (such as a chip, chip system, or circuit) capable of supporting the functions required for the network device to implement the method. For example, taking the data interaction between the first terminal device and the network device as an example, in this method, the first terminal device obtains a first configuration from the network device. The first configuration includes a first radio link control bearer configuration, which is associated with a first carrier. The first radio link control bearer configuration is one of multiple radio link control bearer configurations corresponding to a packet data aggregation layer protocol entity configuration. The first radio link control bearer configuration is used to establish a first radio link control bearer entity. The first carrier is the carrier corresponding to the terminal device performing single-carrier communication. Subsequently, the first terminal device can multicast or broadcast data corresponding to the first radio link control bearer entity on the first carrier. Optionally, sidelink carrier aggregation may include sidelink packet data aggregation layer protocol repetition.

[0006] In this method, when one or more first radio link control bearer configurations are associated with the first carrier, the first terminal device can, when it needs to transmit data, use the first radio link control bearer entity and the first carrier to multicast or broadcast the data to be transmitted to a receiving terminal device that does not support sidelink carrier aggregation. This can effectively ensure normal data transmission between terminal devices that support sidelink carrier aggregation and terminal devices that do not support sidelink carrier aggregation, thereby ensuring the reliability of sidelink communication and effectively improving the quality of sidelink communication.

[0007] In one possible design, if the first terminal device does not support sidelink carrier aggregation or the destination address corresponding to the receiving terminal device does not support sidelink carrier aggregation, in order to ensure normal data transmission between terminal devices that support sidelink carrier aggregation and terminal devices that do not support sidelink carrier aggregation, thereby improving the quality of sidelink communication, multiple radio link control bearer configurations can be configured to establish radio link control bearer entities for transmitting the same data.

[0008] In one possible design, the method further includes:

[0009] When the packet data aggregation layer protocol entity configuration obtained by the first terminal device includes a packet data aggregation layer protocol splitting configuration, in order to ensure normal data transmission between terminal devices that do not support sidelink carrier aggregation and terminal devices that do support sidelink carrier aggregation, the first terminal device can transmit multiple data items in the first terminal device through a first radio link control bearer entity. The packet data aggregation layer protocol splitting configuration is used to instruct multiple data items in the first terminal device to be transmitted through multiple radio link control bearer entities. Optionally, sidelink carrier aggregation may include sidelink packet data aggregation layer protocol splitting.

[0010] In the above design, if the first terminal device does not support sidelink carrier aggregation or the destination address corresponding to the receiving terminal device does not support sidelink carrier aggregation, the first terminal device can choose not to apply (or not use or ignore) the packet data aggregation layer protocol split configuration. Multiple data in the first terminal device can be transmitted through the first radio link control bearer entity corresponding to the first carrier, which effectively ensures normal data transmission between terminal devices that support sidelink carrier aggregation and terminal devices that do not support sidelink carrier aggregation. This ensures the reliability of sidelink communication and effectively improves the quality of sidelink communication.

[0011] In one possible design, when the first terminal device does not support sidelink carrier aggregation and / or the destination address does not support sidelink carrier aggregation, even if the first terminal device obtains the packet data aggregation layer protocol split configuration, it can choose not to apply the packet data aggregation layer protocol split configuration. In this case, after establishing the sidelink radio bearer (including the packet data aggregation layer protocol entity and one or more radio link control bearer entities) according to the obtained configuration, it can select the first radio link control bearer entity corresponding to the first carrier in one or more radio link control bearer entities to transmit multiple data in the first terminal device. The destination address is used to indicate the receiving terminal device for the first terminal device to perform sidelink communication.

[0012] In one possible design, the first terminal device can send a first message to the network device, the first message being used to instruct the first terminal device not to apply the Packet Data Convergence Layer Protocol split configuration.

[0013] For example, after the first terminal device selects not to apply the Packet Data Convergence Layer Protocol (PDLP) split configuration, it can send the first information to the network device. In this way, when the network device configures the sidelink radio bearer configuration for establishing the sidelink radio bearer for the first terminal device or the destination address requested by the first terminal device, it does not need to configure the PLP split configuration. This makes the sidelink radio bearer configuration more targeted and can meet the different needs of the terminal device.

[0014] In one possible design, the first terminal device may send second information to the network device, wherein the second information is used to indicate that the first terminal device supports sidelink carrier aggregation and / or to indicate that the destination address supports sidelink carrier aggregation, and the destination address is used to indicate the receiving terminal device for sidelink communication of the first terminal device.

[0015] For example, when the first terminal device needs the sidelink radio bearer configuration required to establish the sidelink radio bearer, the first terminal device can actively send the second information to the network device. This allows the network device to determine the corresponding sidelink radio bearer configuration for the first terminal device based on the first information, while ensuring the reliability of sidelink communication.

[0016] In one possible design, when the first terminal device is in a radio resource control (RRC) connection state, it can send the second information to the network device in a terminal device capability information message or a sidelink terminal device information message. This allows the network device to determine a corresponding first configuration for the first terminal device, where the sidelink terminal device information message is used to request the first configuration. Optionally, after sending the terminal device capability information message to the network device, the first terminal device may also send a sidelink terminal device information message to the network device.

[0017] In one possible design, the first terminal device (e.g., the access layer of the first terminal device) can obtain third information from the upper layer of the first terminal device, wherein the third information is used to indicate that the destination address supports sidelink carrier aggregation.

[0018] For example, the access layer of the first terminal device can promptly obtain information from the upper layer of the first terminal device regarding whether the destination address corresponding to the receiving terminal device supports sidelink carrier aggregation. In one example, when the destination address corresponding to the receiving terminal device supports sidelink carrier aggregation, if the first terminal device also supports sidelink carrier aggregation, then sidelink communication between the first terminal device and the receiving terminal device can be performed on multiple carriers. If the first terminal device does not support sidelink carrier aggregation, then normal data transmission between the first terminal device and the receiving terminal device can also be achieved by applying a first configuration. In another example, when the destination address corresponding to the receiving terminal device does not support sidelink carrier aggregation, if the first terminal device supports sidelink carrier aggregation, then normal data transmission between the first terminal device and the receiving terminal device can also be achieved by applying a first configuration. If the first terminal device also does not support sidelink carrier aggregation, then data transmission between the first terminal device and the receiving terminal device can be performed using a first carrier.

[0019] In one possible design, the association between the first radio link control bearer configuration and the first carrier can be determined by the network device when transmitting the first configuration to the first terminal device, or it can be determined by the first terminal device, not the network device. For example, after obtaining the first configuration from the network device, the first terminal device can select the first radio link control bearer configuration from multiple radio link control bearer configurations to establish an association with the first carrier based on the information of the carriers it supports.

[0020] Secondly, this application provides a communication method that can be implemented through data interaction between multiple communication devices (such as a first communication device and a second communication device). Optionally, the first communication device can be a second terminal device or a component (such as a chip, chip system, or circuit) capable of supporting the functions required for the second terminal device to implement the method. The second communication device can be a third terminal device or a component (such as a chip, chip system, or circuit) capable of supporting the functions required for the third terminal device to implement the method. For example, taking the data interaction between the second terminal device and the third terminal device as an example, in this method, after determining that the second terminal device supports sidelink carrier aggregation, it can send fourth information to the third terminal device on the second carrier. The third terminal device can be a receiving terminal device for sidelink communication between the second terminal device and the third terminal device. The fourth information can be used to instruct the second terminal device and the third terminal device to perform sidelink transmission on the third carrier. The second carrier and / or the third carrier do not include the first carrier. The first carrier is the carrier corresponding to the terminal device performing single-carrier communication, and the second and third carriers are different. Optionally, sidelink carrier aggregation can include sidelink cross-carrier scheduling and / or sidelink cross-carrier feedback.

[0021] In this method, when the destination address corresponding to the receiving terminal device does not support sidelink carrier aggregation, by restricting the second and / or third carriers to exclude the first carrier, it can be ensured that the receiving terminal device that does not support sidelink carrier aggregation can normally receive sidelink data from the second terminal device on the first carrier. This enables normal data transmission between the terminal device that supports sidelink carrier aggregation and the terminal device that does not support sidelink carrier aggregation, thereby ensuring the reliability of sidelink communication and effectively improving the quality of sidelink communication.

[0022] In one possible design, the second terminal device may receive a hybrid automatic repeat request feedback from the third terminal device on a second or third carrier, wherein the hybrid automatic repeat request feedback is used to indicate the reception status of the side link transmission on the third carrier by the third terminal device.

[0023] For example, when the destination address corresponding to the third terminal device supports sidelink carrier aggregation, the third terminal device can provide feedback to the second terminal device on the second carrier or the third carrier regarding the reception status of the data transmitted by the second terminal device on the third carrier. This allows the second terminal device to understand the data reception status of the third terminal device in a timely manner, thereby facilitating the second terminal device to make corresponding adjustments to the data transmission in a timely manner.

[0024] In one possible design, the second terminal device (e.g., the access layer of the second terminal device) can obtain the fifth information from the upper layer of the second terminal device, wherein the fifth information is used to indicate that the destination address corresponding to the third terminal device supports sidelink carrier aggregation.

[0025] For example, the access layer of the second terminal device can promptly obtain information from the upper layer of the second terminal device regarding whether the destination address corresponding to the third terminal device supports sidelink carrier aggregation. In one example, when the destination address corresponding to the third terminal device supports sidelink carrier aggregation, the second and / or third carriers can be restricted to include the first carrier. This ensures that the third terminal device can receive signaling or data transmitted by the second terminal device on any carrier. In another example, when the destination address corresponding to the third terminal device does not support sidelink carrier aggregation, the second and / or third carriers can be restricted to exclude the first carrier. This ensures that the third terminal device can receive signaling or data transmitted by the second terminal device on the first carrier.

[0026] In one possible design, sidelink aggregation may include sidelink cross-carrier scheduling and / or sidelink cross-carrier feedback. This allows the communication method to be applied to a wider range of scenarios, meeting the needs of different application scenarios, while taking into account the characteristics of cross-carrier scheduling / cross-carrier feedback.

[0027] Thirdly, this application provides a possible communication device. Optionally, the communication device may be a communication equipment (such as a first communication device or a second communication device) or a component (such as a chip, chip system, or circuit) capable of supporting the communication equipment to implement the communication method. For example, the first communication device may be a first terminal device or a second terminal device, and the second communication device may be a network device or a third terminal device. When the communication device is a chip disposed in the first (or second) communication device, the communication device includes a transceiver and a processor, but does not include a memory. The transceiver exists as an input / output interface, which is used by the chip to implement the transmission and reception of the communication device. The input / output interface may include an input interface and / or an output interface; the input interface can enable the communication device to receive data, and the output interface can be used to enable the communication device to transmit data. The processor is used to read and execute corresponding computer programs or instructions, so that the corresponding functions of the first (or second) communication device are implemented. Optionally, when the chip implements the corresponding functions of the first communication device (or the second communication device) in the communication method embodiment provided in this application, the input / output interface can implement the transmit / receive operations performed by the first communication device (or the second communication device) in the communication method embodiment provided in this application; the processor can implement other operations besides transmit / receive operations performed by the first communication device (or the second communication device) in the communication method embodiment provided in this application.

[0028] In one example, when the communication device is used to implement the function of the first terminal device in the communication method embodiment provided in this application, the beneficial effects can be found in the description of the first terminal device in the first aspect, and will not be repeated here. The communication device has the function of implementing the behavior of the first terminal device in the method example of the first aspect described above. The function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions. In one possible design, the communication device includes: a communication module (or may be called a communication unit, transceiver module, or transceiver unit, used for sending and receiving data) and a processing module (or may be called a processing unit). The communication module is used to obtain a first configuration from a network device. The first configuration includes a first radio link control bearer configuration, which is associated with a first carrier. The first radio link control bearer configuration is one of multiple radio link control bearer configurations corresponding to a packet data aggregation layer protocol entity configuration. The first radio link control bearer configuration is used to establish a first radio link control bearer entity, and the first carrier is the carrier corresponding to the terminal device performing single-carrier communication. The processing module is used to multicast or broadcast data corresponding to the first radio link control bearer entity on the first carrier. In another possible design, the communication device includes a communication module (or transceiver module, used for sending and receiving data) and a processing module. The communication module is used to acquire the Packet Data Convergence Layer Protocol (PDCP) entity configuration from the network device. Exemplarily, the PDCP entity configuration may or may not include a PDCP split configuration. The PDCP split configuration is used to instruct multiple data items in the first terminal device to be transmitted through multiple Radio Link Control Bearer (RLC) entities. These RLC entities are established by the first terminal device according to multiple RLC bearer configurations. Optionally, in the PDCP split configuration, the multiple RLC bearer configurations are associated with different carriers. Optionally, the different carriers may include a first carrier. The processing module is used to transmit multiple data items in the first terminal device through the first RLC bearer entity. These modules can perform the corresponding functions of the first terminal device in the method examples of the first aspect described above; see the detailed description of the corresponding functions of the first terminal device in the method examples for details, which will not be repeated here.

[0029] In another example, when the communication device is used to implement the function of the second terminal device in the communication method embodiment provided in this application, the beneficial effects can be found in the description of the second terminal device in the second aspect, which will not be repeated here. The communication device has the function of implementing the behavior of the first terminal device in the method example of the first aspect described above. The function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions. In one possible design, the communication device includes: a communication module (or transceiver module, used for sending and receiving data) and a processing module. The processing module is used to determine that the second terminal device supports sidelink carrier aggregation. The communication module is used to send fourth information to the third terminal device on the second carrier. The third terminal device is the receiving terminal device for sidelink communication between the second terminal device and the third terminal device, and the fourth information can be used to instruct the second terminal device and the third terminal device to perform sidelink transmission on the third carrier. The second carrier and / or the third carrier do not include the first carrier; the first carrier generally refers to the carrier corresponding to the terminal device performing single-carrier communication, and the second carrier and the third carrier are different. These modules can perform the corresponding functions of the second terminal device in the method example of the second aspect above. For details, please refer to the detailed description of the corresponding functions of the second terminal device in the method example, which will not be repeated here.

[0030] Fourthly, this application provides a possible communication device, which may be a communication device required for executing the communication method provided in this application (such as a first communication device or a second communication device), or it may be a device including the communication device required for executing the communication method provided in this application, or it may be a device having the functions required to implement the communication method. The communication device may include a transceiver and a processor. Optionally, the communication device may further include a memory. The memory is used to store computer programs or instructions, and the processor is coupled to the memory and the transceiver. When the processor executes the computer program or instructions, it causes the communication device to execute the method in any of the possible designs of the first aspect or the method in any of the possible designs of the second aspect.

[0031] Fifthly, this application provides a possible communication system, which may include the first communication device and the second communication device mentioned in the first or second aspect above. The functional implementation of the first or second communication device can be found in the relevant descriptions mentioned in the first or second aspect above, and will not be repeated here.

[0032] For example, the communication system may include one or more first communication devices and one or more second communication devices.

[0033] In a sixth aspect, this application provides a computer program product comprising a computer program or instructions that, when executed on a computer, cause the computer to perform any of the possible designs in the first aspect or any of the possible designs in the second aspect described above.

[0034] In a seventh aspect, this application provides a computer-readable storage medium storing a computer program or instructions that, when executed by a computer, cause the computer to perform any of the possible designs of the first aspect or any of the possible designs of the second aspect described above.

[0035] Eighthly, this application provides a computer program including program code that, when a computer runs the computer program, performs the method in any possible design of the first aspect or any possible design of the second aspect described above.

[0036] Ninthly, this application also provides a chip that may include a processor and may also include a memory (or the chip may be coupled to the memory), the chip executing program instructions in the memory to perform the method in any possible design of the first aspect or the method in any possible design of the second aspect. Here, "coupling" means that two components are directly or indirectly connected to each other, such as coupling can refer to an electrical connection between two components.

[0037] In a tenth aspect, this application also provides a chip system including a processor for supporting a computer device in implementing any of the possible designs of the first aspect or any of the possible designs of the second aspect described above. In one possible design, the chip system further includes a memory for storing programs and data necessary for the computer device. The chip system may be composed of chips or may include chips and other discrete devices.

[0038] Based on the implementation methods provided in the above aspects, this application can be further combined to provide more implementation methods. Attached Figure Description

[0039] Figure 1a An exemplary schematic diagram of a possible communication system architecture provided in an embodiment of this application is shown;

[0040] Figure 1b This illustration shows another possible communication system architecture provided by an embodiment of this application;

[0041] Figure 2This illustration shows a schematic diagram of data transmission between protocol layers according to an embodiment of this application.

[0042] Figure 3 An exemplary flowchart of a communication method provided in an embodiment of this application is shown;

[0043] Figure 4 An exemplary flowchart of another communication method provided in an embodiment of this application is shown;

[0044] Figure 5 An exemplary flowchart of another communication method provided in an embodiment of this application is shown;

[0045] Figure 6 An exemplary schematic diagram of a possible communication device provided in an embodiment of this application is shown;

[0046] Figure 7 An exemplary schematic diagram of another possible communication device provided in an embodiment of this application is shown. Detailed Implementation

[0047] Before introducing the technical solutions provided in this application, some of the terms used in this application will be explained in order to facilitate understanding by those skilled in the art.

[0048] (1) Sidelink Radio Bearer (SLRB): This is the bearer used in Layer 2 for transmitting and receiving data on the sidelink. SLRBs include Packet Data Convergence Protocol (PDCP) entities, Radio Link Control (RLC) entities, or Logical Channel (LCH) entities. Optionally, an SLRB is uniquely associated with a set of address information, which may include a source address identifier (e.g., source L2 ID) and a destination address identifier (e.g., destination L2 ID).

[0049] (2) Sidelink (SL) Carrier Aggregation (CA): Terminal devices can communicate with each other via one or more carriers (or SL carriers) on the sidelink. For example, a terminal device can use multiple SL carriers to send broadcast or multicast messages, or it can use multiple SL carriers to unicast with another terminal device. Different data can be sent on different SL carriers, thereby increasing the data rate on the SL. For example, a splitting mechanism can be used. Here, data rate generally refers to data transmission rate, or simply data rate. Optionally, the same data can also be sent on different carriers. For example, a duplication mechanism can be used, where duplicate data can be transmitted on different carriers to improve the reliability of data transmission.

[0050] (3) Terminal equipment: is a device on the user side that has the function of sending and receiving signals and can provide users with services such as video, voice and data connectivity.

[0051] Optionally, the terminal device may also be referred to as a terminal, user equipment (UE), access terminal device, vehicle-mounted terminal, industrial control terminal, UE unit, UE station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal device, mobile device, UE terminal device, terminal device, wireless communication device, UE agent, or UE apparatus, etc. In the embodiments of this application, the terminal device may be fixed in location or mobile, and this application does not limit it in this respect.

[0052] For example, terminal devices can be mobile phones, tablets, subscriber units, cellular phones, smartphones, wireless data cards, personal digital assistant (PDA) computers, wireless modems, handsets, laptop computers, computers with wireless transceiver capabilities, virtual reality (VR) terminal devices, augmented reality (AR) terminal devices, wireless terminals in industrial control, terminal devices capable of sidelink communication (such as vehicle-mounted terminal devices or handheld terminals for V2X communication), wireless terminals in self-driving vehicles, wireless terminals in remote medical care, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, wearable terminal devices, vehicles, drones, helicopters, aircraft, factory machines / equipment, and machine-type communication devices. Communication (MTC) terminals, ships, or robots, etc. This application does not limit the specific technology or form of the terminal device used in its embodiments.

[0053] (4) Network equipment: This can refer to any device with wireless transceiver capabilities. For example, network equipment can be a radio access network (RAN) device that connects terminal devices to a wireless network. For example, RAN equipment can include, but is not limited to: next-generation NodeB (gNB) in 5th generation (5G) communication systems, next-generation base stations in 6th generation (6G) communication systems, base stations in future communication systems, transmission reception points (TRP), evolved Node B (eNB), radio network controllers (RNC), Node B (NB), base station controllers (BSC), base transceiver stations (BTS), home base stations (e.g., home evolved Node B, or home Node B (HNB)), base band units (BBU), or wireless fidelity (Wi-Fi) access points (AP), etc.

[0054] Optionally, in a network architecture, the RAN device may further include a centralized unit (CU) or a distributed unit (DU). This architecture can separate the protocol layers of the network device, with some protocol layer functions centrally controlled by the CU, and the remaining part or all protocol layer functions distributed in the DU, which is centrally controlled by the CU. For example, the PDCP layer and above protocol layer functions can be located in the CU, while the functions of protocol layers below PDCP (such as the RLC layer and medium access control (MAC) layer) can be located in the DU. It should be noted that this division of protocol layers is merely an example, and it can also be done in other protocol layers. The radio frequency device can be remote and not placed in the DU, or it can be integrated into the DU, or partially remote and partially integrated into the DU; this application embodiment does not impose any limitations. In addition, in some embodiments, the control plane (CP) and user plane (UP) of the CU can be separated and implemented as different entities, namely the control plane CU entity (CU-CP entity) and the user plane CU entity (CU-UP entity).

[0055] For example, taking a network device as a base station, the base station can communicate with the terminal device, or it can communicate with the terminal device through a relay station. The terminal device can communicate with multiple base stations using different access technologies.

[0056] In this application embodiment, the RAN device can be a macro base station, a micro base station, an indoor station, a relay node, or a donor node, etc. This application embodiment does not limit the specific technology or device form used in the wireless access network equipment.

[0057] (5) Sidelink (SL): Also known as a side link, side-link, direct link, edge link, or auxiliary link, etc. In the embodiments of this application, the above terms all refer to links established between devices of the same type, and have the same meaning. The so-called devices of the same type can be links between terminal devices, etc. Among them, the links between terminal devices can be D2D links defined in 3GPP versions (Rel)-12 / 13 / 14 / 15, or V2X links defined by 3GPP for vehicle-to-vehicle, vehicle-to-mobile, or vehicle-to-any entity, or V2X links based on NR systems in other versions (such as Rel-16 or later versions), etc.

[0058] The embodiments of this application will now be described in detail with reference to the accompanying drawings.

[0059] The following describes possible communication system architectures to which the communication method provided in this application is applicable. It should be noted that this description is for the convenience of those skilled in the art and is not intended to limit the scope of protection claimed in this application.

[0060] Figure 1a This illustration shows a possible communication system architecture applicable to embodiments of this application. Figure 1a As shown, the communication system architecture includes RAN 100 and core network 200. Optionally, the communication system architecture may also include Internet 300. RAN 100 may include at least one RAN device (e.g., Figure 1a RAN devices 110a and RAN devices 110b, and including at least one terminal device (e.g., Figure 1aThe terminal devices 120a-120j are included in the network architecture. Optionally, the terminal devices can be connected to the RAN devices wirelessly, and the RAN devices can be connected to the core network 200 wirelessly or via a wired connection. The core network devices and RAN devices can be independent physical devices, or the functions of the core network devices and the logical functions of the RAN devices can be integrated into the same physical device, or a single physical device can integrate some of the functions of the core network devices and some of the functions of the radio access network devices. Terminal devices and RAN devices can be interconnected via wired or wireless connections. For example, this communication system architecture may also include other network devices (such as wireless relay devices or wireless backhaul devices).

[0061] RAN devices (such as RAN devices 110a and RAN devices 110b), sometimes also referred to as access network devices, RAN entities, RAN nodes, or access nodes, constitute part of a communication system and are used to help terminal devices achieve wireless access. Multiple RAN devices in a communication system can be nodes of the same type or different types. The network devices involved in the embodiments of this application include, for example, RAN devices. RAN devices can be base stations, evolved NodeBs (eNodeBs), transmission reception points (TRPs), transmission points (TPs), next-generation NodeBs (gNBs) in 5G mobile communication systems, next-generation base stations in 6G mobile communication systems, base stations in future mobile communication systems, or access nodes in WiFi systems, etc.

[0062] In some scenarios, the roles of RAN devices (such as RAN devices 110a and RAN devices 110b) and terminal devices (such as terminal devices 120a-120j) are relative. For example, Figure 1a The network element 120i can be a helicopter or a drone, and it can be configured as a mobile base station. For terminals 120j that access RAN 100 via network element 120i, network element 120i is a base station; however, for RAN equipment 110a, network element 120i is a terminal. RAN equipment and terminal equipment are sometimes referred to as communication devices, for example... Figure 1a Network elements 110a and 110b can be understood as communication devices with base station functions, while network elements 120a-120j can be understood as communication devices with terminal functions.

[0063] In another possible scenario, multiple RAN devices collaborate to assist the terminal in achieving wireless access, with each RAN device performing a portion of the base station's functions. For example, RAN devices can be CUs, DUs, CU-CPs, CU-UPs, or radio units (RUs). CUs and DUs can be configured separately or included in the same network element, such as a baseband unit (BBU). RUs can be included in radio equipment or radio units, such as remote radio units (RRUs), active antenna units (AAUs), or remote radio heads (RRHs).

[0064] The CU and DU can be configured separately or included in the same network element, such as the baseband unit (BBU). Here, the CU performs the functions of the radio resource control protocol and PDCP of the base station, and can also perform the functions of the service data adaptation protocol (SDAP). The DU performs the functions of the RLC layer and MAC layer (or media access control layer) of the base station, and can also perform some or all of the physical layer functions. For specific descriptions of the above-mentioned protocol layers, please refer to the relevant technical specifications of the 3rd Generation Partnership Project (3GPP). The RU can be included in radio frequency equipment or radio frequency units, such as in a remote radio unit (RRU), active antenna unit (AAU), or remote radio head (RRH). In the embodiments of this application, when the network equipment includes CU and / or DU, in one possible implementation, the PDCP / SLRB related configuration is generated by the CU, and the RLC bearer / RLC entity / LCH, etc., are generated by the DC. For example, taking PDCP entity configuration as an example, the PDCP entity configuration can be generated by the CU and sent by the CU to the DU (e.g., via Radio Resource Control (RRC) messages). The DU can then send the PDCP entity configuration to the first terminal device. As another example, taking Radio Link Control (RLC) bearer configuration as an example, the RLC bearer configuration can be generated by the DU. The DU can first send the RLC bearer configuration to the CU, then the CU processes it and sends it back to the DU, which then sends it to the first terminal device.

[0065] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an open radio access network (ORAN) system, CU can also be called open CU (open-CU, O-CU), DU can also be called open DU (open-DU, O-DU), CU-CP can also be called open CU-CP (open-CU-CP, O-CU-CP), CU-UP can also be called O-CU-UP, and RU can also be called open RU (open-RU, O-RU). For ease of description, this application uses CU, CU-CP, CU-UP, DU, and RU as examples. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software modules and hardware modules.

[0066] In this embodiment, the functions of the RAN device (such as a base station) can also be executed by modules (such as chips) within the base station, or by a control subsystem containing base station functions. This control subsystem containing base station functions can be a control center in the aforementioned application scenarios such as smart grids, industrial control, intelligent transportation, and smart cities. Similarly, the functions of the terminal device can be executed by modules (such as chips or modems) within the terminal device, or by a device containing terminal functions.

[0067] based on Figure 1a The communication system architecture shown is as follows: Figure 1b An exemplary schematic diagram of a possible communication system architecture applicable to embodiments of this application is shown. For example... Figure 1bAs shown, the communication system architecture includes a terminal device 400, at least one receiving terminal device corresponding to the terminal device 400 (such as terminal device 501, terminal device 502, etc.), and a RAN device 600. The terminal device 400 and at least one receiving terminal device can communicate via one or more SL carriers. For example, taking terminal device 501 as an example, terminal device 400 can send SL information to terminal device 501 via one or more SL carriers. The communication interface between terminal device 400 and terminal device 501 is called a Prose Communication 5 (PC5) interface, and a PC5 connection can be established between terminal device 400 and terminal device 501. For example, taking terminal device 400 as UE1 and terminal device 501 as UE2, UE1 can be in coverage (IC) or out of coverage (OOC) state. When UE1 is in RRC connected state, UE1 can communicate with network devices (such as...) Figure 1b The RAN device 600 (as shown) requests SL resources for transmitting SL information, such as SL signaling or SL data. This mode is called the resource allocation mode of Mode 1 (base station scheduling mode). In Mode 1, the RAN device 600 can schedule SL resources for UE1 via downlink control information (DCI) or configure SL grants for UE1 via RRC messages. Optionally, UE1 can also operate in Mode 2 (autonomous contention mode). When UE1 operates in Mode 2, UE1 can be in RRC connected state, RRC inactive state, RRC idle state, or OOC state. In Mode 2, UE1 can receive SL resource pool configuration from the RAN device 600 or obtain SL resource pool configuration from pre-configuration. Then, UE1 can select SL resources from the SL resource pool to transmit SL information, such as SL signaling or SL data. For example, UE1 can select SL resources from the SL resource pool in a random manner, or it can select SL resources from the SL resource pool based on the results of sensing or partial sensing.

[0068] It should be noted that the communication method provided in this application embodiment can be applied to various radio access technology (RAT) communication systems, such as Long Term Evolution (LTE) systems, or 5G (or New Radio, NR) communication systems, and of course, future communication systems (such as 6G communication systems) or other similar communication systems. This application embodiment does not impose any limitations on this. The communication system architecture illustrated in this application embodiment is for the purpose of more clearly illustrating the technical solutions of this application embodiment and does not constitute a limitation on the technical solutions provided in this application embodiment. As those skilled in the art will understand, with the evolution of communication system architecture and the emergence of new service scenarios, the technical solutions provided in this application embodiment are also applicable to similar technical problems.

[0069] Optionally, the communication method provided in this application embodiment can be applied to device-to-device (D2D) scenarios, such as NR-D2D scenarios, or to vehicle-to-everything (V2X) scenarios, such as NR-V2X scenarios (e.g., scenarios in the fields of drivable vehicles, assisted driving, or intelligent connected vehicles). For example, V2X scenarios may include, but are not limited to, vehicle-to-vehicle (V2V), vehicle-to-pedestrian (V2P), vehicle-to-network (V2N) services, or vehicle-to-infrastructure (V2I) communication. For example, device-to-device scenarios may also include, but are not limited to: communication scenarios between remote UE and relay user equipment (relay UE) in a sidelink user equipment-to-network relay communication system architecture; communication scenarios between source UE and relay user equipment in a sidelink user equipment-to-user equipment relay communication system architecture; or communication scenarios between relay user equipment and target UE, etc.

[0070] Optionally, in the above Figure 1a or Figure 1bIn the illustrated communication system architecture, communication between a terminal device (e.g., terminal device 400) and at least one receiving terminal device (or communication between the terminal device and the RAN device) can follow a certain protocol layer structure. For example, the control plane protocol layer structure may include the functions of protocol layers such as RRC, PDCP (or packet data aggregation protocol layer), RLC, MAC, and physical layer (PHY); the user plane protocol layer structure may include the functions of protocol layers such as PDCP, RLC, MAC, and PHY; in one possible implementation, an SDAP layer may also be included above the PDCP layer. Exemplarily, the RAN device may have one node implementing the functions of protocol layers such as RRC, PDCP, RLC, and MAC, or it may have multiple nodes implementing these protocol layer functions.

[0071] For example, with Figure 1b Taking the data transmission between terminal device 400 and terminal device 501 as an example, data transmission needs to pass through user plane protocol layers, such as the SDAP layer, PDCP layer, RLC layer, MAC layer, and PHY layer. The SDAP layer, PDCP layer, RLC layer, MAC layer, and PHY layer can also be collectively referred to as the access layer. Based on the direction of data transmission, it is divided into sending or receiving; each of the above layers is further divided into a sending part and a receiving part. Taking the data transmission from terminal device 400 to terminal device 501 as an example, see... Figure 2 The diagram shows the data transmission between different protocol layers. Figure 2 Downward arrows indicate data transmission, and upward arrows indicate data reception. Optionally, the communication method between terminal device 400 and terminal device 501 can be multicast or broadcast communication. After the PDCP layer obtains data from the upper layer, it transmits the data to the RLC and MAC layers. The MAC layer then generates a transport block (TB), which is then wirelessly transmitted through the physical layer. Data is encapsulated in each layer. Data received by a layer from the upper layer is considered as the service data unit (SDU) of that layer. After layer encapsulation, it becomes a protocol data unit (PDU) and is then passed to the next layer. Optionally, through... Figure 2 It can also be seen that the terminal device may have an application layer and a non-access layer; the application layer can be used to provide services to applications installed on the terminal device. Optionally, the non-access layer can be used to forward user data, for example, it can forward data received from the application layer to the SDAP layer or forward data received from the SDAP layer to the application layer.

[0072] For example, taking the SDAP layer above the PDCP layer as an example, when terminal device 400 sends a data packet corresponding to multicast communication (or broadcast communication) to terminal device 501, the SDAP entity of terminal device 400 can, according to the correspondence, deliver the SDAP PDU containing the data packet to the PDCP entity corresponding to a certain SLRB of the multicast communication for processing. After receiving the SDAP PDU, the PDCP entity corresponding to that SLRB processes the SDAP SDU included in the SDAP PDU to generate a PDCPPDU, and can deliver the PDCP PDU to the RLC entity in that SLRB. After receiving the PDCP PDU, the RLC entity processes the PDCP SDU included in the PDCPPDU to generate an RLC PDU, and can deliver the RLC PDU to the MAC entity of terminal device 400 via the LCH corresponding to that SLRB. After receiving the RLC PDU, the MAC entity processes the RLC SDU included in the RLC PDU to obtain a MAC PDU, and can send the MAC PDU to the MAC entity of terminal device 501 through the PC5 port. After receiving a MAC PDU, the MAC entity of terminal device 501 hands it over to the SLRB corresponding to the multicast communication in terminal device 501 for processing. Each SLRB corresponds to a PDCP entity, one or more RLC entities, one or more LCHs, etc. The configuration of each SLRB may include SLRB identifier, PDCP entity configuration, RLC entity configuration, LCH configuration, etc.

[0073] The following is based on Figure 1a , Figure 1b The schematic diagram of the communication system architecture is shown, and the specific implementation of the communication method in the embodiments of this application is described in detail.

[0074] Figure 3 This illustration shows a flowchart of a communication method provided in an embodiment of this application. The method is applicable to... Figure 1a , Figure 1b The illustrated communication system architecture. This method can be implemented through data interaction between multiple communication devices (such as a first communication device and a second communication device). Optionally, the first communication device can be a first terminal device or a component (such as a chip, chip system, or circuit) capable of supporting the functions required for the first terminal device to implement the method. The second communication device can be a network device or a component (such as a chip, chip system, or circuit) capable of supporting the functions required for the network device to implement the method. For example, the first terminal device can be... Figure 1a The terminal device shown is 120f or 120g, etc., and the network device can be... Figure 1a The RAN device 110b shown, or the first terminal device, can be Figure 1a The terminal device shown is 120a or 120i, etc., and the network device can be... Figure 1a The RAN device 110a shown, or the first terminal device, can be Figure 1b The terminal device 400 shown; the network device can be Figure 1b The illustrated RAN device is 600. Optionally, the network device can also be a core network device, such as... Figure 1a The core network 200 is shown in the diagram. To facilitate the introduction of the technical solutions provided in the embodiments of this application, the following uses a first communication device as a first terminal device and a second communication device as a network device as an example to describe the flow of the communication method achieved through data interaction between the first communication device and the second communication device. For example... Figure 3 As shown, the method includes:

[0075] Step 301: The first terminal device obtains the first configuration from the network device.

[0076] The first configuration may include (or be understood as associated with or correspond to) a first radio link control bearer configuration. This first radio link control bearer configuration is associated with (or mapped to) a first carrier. The first radio link control bearer configuration is one of multiple radio link control bearer configurations corresponding to the packet data aggregation layer protocol entity configuration. The first carrier is the carrier corresponding to the terminal device performing single-carrier communication. For example, the terminal device performing single-carrier communication can refer to a terminal device that only supports single-carrier communication (understood as a terminal device that does not support SL CA), or it can refer to a terminal device that supports single-carrier communication (understood as a terminal device that supports SL CA also supports SL communication on a single carrier). Exemplarily, the first carrier can be one of the following: a carrier predefined by the communication protocol, a default carrier, a carrier supported by the terminal device under Rel-16 and Rel-17 versions, or a specific carrier in the sidelink carrier list included in the System Information Block (SIB) 12 message. Exemplarily, the specific carrier in the sidelink carrier list included in the SIB 12 message can be the first carrier in the sidelink carrier list included in the SIB 12 message. Optionally, the SIB12 message can be replaced with other SIB messages. Optionally, the first configuration may include multiple radio link control bearer configurations. In one example, a packet data aggregation layer protocol entity configuration may be included in the first configuration. In another example, the packet data aggregation layer protocol entity configuration may not be included in the first configuration. For example, the first configuration is an SLRB configuration. Optionally, the first radio link control bearer configuration is associated with the first carrier; that is, the first radio link control bearer configuration is only associated with the first carrier, meaning it is not associated with any carriers other than the first carrier.

[0077] In one possible implementation, the network device may specify that a first radio link control bearer configuration is associated with a first carrier, and transmit this association relationship to the first terminal device in the first configuration or the first radio link control bearer configuration. Alternatively, it may transmit this association relationship to the first terminal device in other ways, such as transmitting the association relationship separately or in other messages. This application embodiment does not limit this approach. In another possible implementation, the network device only transmits the packet data aggregation layer protocol entity configuration, multiple radio link control bearer configurations, etc., to the first terminal device, without specifying which carriers each of the multiple radio link control bearer configurations is associated with, and therefore does not specify that the first radio link control bearer configuration is associated with the first carrier. When the first terminal device receives the packet data aggregation layer protocol entity configuration, multiple radio link control bearer configurations, etc., it can select one radio link control bearer configuration (such as the first radio link control bearer configuration) from the multiple radio link control bearer configurations to establish an association relationship with the first carrier.

[0078] Optionally, a radio link control (NRDC) bearer configuration may include a NRDC entity configuration and a logical channel configuration, wherein the logical channel configuration may be associated with one or more carriers. Specifically, the NRDC entity established by the NRDC entity configuration may correspond to the logical channel established by the logical channel configuration. For example, taking a certain NRDC bearer configuration (such as NRDC bearer configuration 1) as an example, the logical channel configuration included in NRDC bearer configuration 1 is associated with carrier A. When the first terminal device transmits data on the logical channel established by the logical channel configuration, it can use carrier A. In other words, the association between the NRDC bearer configuration and the carrier can mean that the logical channel configuration included in the NRDC bearer configuration is associated with the carrier.

[0079] For example, the following describes the implementation process of the first terminal device obtaining the first configuration from the network device through several possible implementation methods.

[0080] Method 1: The first terminal device sends second information to the network device. The network device receives the second information. In one example, the second information may be used to indicate that the first terminal device supports sidelink SL carrier aggregation (CA) and / or may be used to indicate that the destination address supports SL CA. The destination address may be used to indicate the receiving terminal device for sidelink communication performed by the first terminal device. In another example, the second information may also be used to indicate that the first terminal device does not support SL CA and / or may be used to indicate that the destination address does not support SL CA. Optionally, SL CA may include a sidelink SL packet data aggregation layer protocol entity (PDCP) duplication.

[0081] For example, the second information can be carried in a UE capability information message or a side link UE information message. When the first UE is in a radio resource control (RRR) connected state, it can send a UE capability information message or a side link UE information (SUI) message to the network device. The side link UE information message can be used to request a first configuration, or it can be used to request a side link radio bearer configuration, which includes the first configuration. Optionally, when the second information is carried in the UE capability information message, the first UE will also send a side link UE information message to the network device after sending the UE capability information message to the network device.

[0082] In one possible approach, the first terminal device, during the process of obtaining the first configuration, also obtains third information. Optionally, before the first terminal device sends the second information to the network device, the access layer of the first terminal device can obtain the third information from the upper layer of the first terminal device. In one possible implementation, the third information can be used to indicate whether the destination address supports SL CA, or it can also be used to indicate whether the destination address does not support SL CA. In another possible implementation, the third information can also be used to indicate whether the first terminal device supports SL CA, or it can also be used to indicate whether the first terminal device does not support SL CA. It should be understood that the first terminal device may also be configured to support SL CA without needing to know from the upper layer. Optionally, the first terminal device can also obtain information about whether it supports SL CA from the network device where the cell it is camped, or it can also obtain information about whether it supports SL CA from the receiving terminal device. In yet another possible implementation, the third information can also be used to indicate whether the destination address supports Rel-18 or Rel-18+ services, or it can also be used to indicate whether the destination address does not support Rel-18 or Rel-18+ services. When the destination address supports Rel-18 or Rel-18+ services, the destination address supports SL CA.

[0083] Optionally, the third information may also include the association between the service type and the destination address and / or information about the carriers supported by the service type (such as the carrier's name, index, or identifier). For example, the service type may include, but is not limited to, a provider service identifier (PSID), an intelligent transport systems application identifier (ITS-AID), or an application identifier (AID).

[0084] For example, the "upper layer" here can refer to a layer above the access layer of the terminal device (e.g., the first terminal device), such as the V2X layer, the application layer, or a layer between the V2X layer and the application layer. Exemplarily, the access layer of the terminal device (e.g., the first terminal device) may include one or more of the following: RRC layer, SDAP layer, PDCP layer, RLC layer, and MAC layer. Optionally, the access layer of the terminal device may also include the PHY layer. Optionally, the V2X layer may also be replaced by the Prose layer or the PC5-S layer.

[0085] After receiving the sidelink terminal device information message from the first terminal device, the network device can determine the first configuration based on the second information. Then, the network device can transmit the first configuration to the first terminal device. The following examples illustrate the implementation process of the network device determining the first configuration in Method 1.

[0086] Example 1: When the second information is used to indicate that the first terminal device supports SL CA, in order to ensure that data transmission between the first terminal device and a receiving terminal device that does not support SL CA can proceed normally, the network device can select one radio link control bearer configuration (such as the first radio link control bearer configuration) from among multiple radio link control bearer configurations corresponding to the packet data aggregation layer protocol entity configuration to establish an association relationship (or correspondence or mapping relationship) with the first carrier. Then, the network device can generate a first configuration based on the first radio link control bearer configuration and the association relationship between the first radio link control bearer configuration and the first carrier.

[0087] For example, SL PDCP duplication can be cross-carrier SL PDCP duplication (duplication occurs on different carriers) or intra-carrier SL PDCP duplication (duplication occurs on the same carrier). Thus, this method allows the first terminal device, after applying (or using) the first configuration, to multicast or broadcast data corresponding to the first radio link control bearer entity on the first carrier. The first radio link control bearer entity is established by the first terminal device according to the first radio link control bearer configuration.

[0088] Example 2: When the second information is used to indicate that the first terminal device supports SL CA, in order to ensure that data transmission between the first terminal device and a receiving terminal device that does not support SL CA can proceed normally, the network device can also associate multiple radio link control bearer configurations corresponding to the packet data aggregation layer protocol entity configuration with the first carrier. Then, the network device can generate the first configuration based on the multiple radio link control bearer configurations and the association relationships between the multiple radio link control bearer configurations and the first carrier.

[0089] Example 3: When the second information indicates that the destination address supports SL CA and the first terminal device supports SL CA, in order to ensure that the multicast or broadcast data of the first terminal device can be received by other receiving terminal devices that do not support SL CA, thereby enabling normal data transmission between terminal devices that do not support SL CA and terminal devices that support SL CA, the network device can select one of the multiple radio link control bearer configurations (such as the first radio link control bearer configuration) from the multiple radio link control bearer configurations corresponding to the packet data aggregation layer protocol entity configuration to establish an association with the first carrier. Then, the network device can generate a first configuration based on the first radio link control bearer configuration and the association between the first radio link control bearer configuration and the first carrier.

[0090] Example 4: When the second information indicates that the destination address supports SL CA and the first terminal device supports SL CA, in order to ensure that the multicast or broadcast data of the first terminal device can be received by other receiving terminal devices that do not support SL CA, thereby enabling normal data transmission between terminal devices that do not support SL CA and terminal devices that support SL CA, the network device can also establish association relationships between multiple radio link control bearer configurations corresponding to the packet data aggregation layer protocol entity configuration and the first carrier. Then, the network device can generate a first configuration based on the multiple radio link control bearer configurations and the association relationships between the multiple radio link control bearer configurations and the first carrier.

[0091] Optionally, the network device may also select multiple radio link control bearer configurations (such as multiple first radio link control bearer configurations) from multiple radio link control bearer configurations to establish an association with the first carrier, and generate a first configuration based on the multiple first radio link control bearer configurations and the association between the multiple first radio link control bearer configurations and the first carrier respectively.

[0092] Optionally, the first configuration in Examples 1, 2, 3, or 4 above can be generated by the DU. In this case, the first configuration does not include the packet data aggregation layer protocol entity configuration. After generating the first configuration, the DU can send the first configuration to the CU. After receiving the first configuration, the CU can process the first configuration accordingly. For example, the CU can encapsulate the first configuration with other configurations (such as the packet data aggregation layer protocol entity configuration) in a message, or it can encapsulate the first configuration in the sidelink radio bearer configuration. This application embodiment does not limit this. Then, the CU can send the processed first configuration to the DU, and the DU will send the processed first configuration to the first terminal device. In one possible implementation, the DU and CU can be different network devices. For example, when the DU and CU are different network devices, the DU and CU can be two different network devices belonging to the same communication architecture (such as 3GPP architecture or ORAN architecture), or they can be two network devices belonging to different communication architectures (such as one network device of 3GPP architecture and the other network device of ORAN architecture). In another possible implementation, the DU and CU can be configured separately, each as an independent unit located in different network devices. For example, the network devices containing the DU as an independent unit and the network devices containing the CU as an independent unit can be two different network devices belonging to the same communication architecture (e.g., 3GPP or ORAN architecture), or they can be two network devices belonging to different communication architectures (e.g., one is a 3GPP architecture network device, and the other is an ORAN architecture network device). In yet another possible implementation, the DU and CU can be combined into a single network device, which can be a 3GPP architecture network device or an ORAN architecture network device. In yet another possible implementation, the DU and CU can also be integrated as two independent units within the same network element, which is located in a network device, which can be a 3GPP architecture network device or an ORAN architecture network device.

[0093] Method 2: When the first terminal device is stationed in or connected to one of the multiple cells in the coverage area of ​​the network device, it can obtain the first configuration from the network device via multicast or broadcast.

[0094] Network devices generate a first configuration in advance or beforehand, and can multicast or broadcast the first configuration to the outside world according to the communication method of multicast or broadcast communication.

[0095] Optionally, the network device may also unicast the first configuration to the first terminal device.

[0096] In one possible implementation, the network device can select one radio link control bearer configuration (e.g., a first radio link control bearer configuration) from among multiple radio link control bearer configurations corresponding to the packet data aggregation layer protocol entity configuration to establish an association with the first carrier. Then, the network device can generate a first configuration based on the first radio link control bearer configuration and the association between the first radio link control bearer configuration and the first carrier.

[0097] In another possible implementation, the network device can associate multiple radio link control bearer configurations corresponding to the packet data aggregation layer protocol entity configuration with the first carrier. Then, the network device can generate a first configuration based on the multiple radio link control bearer configurations and their associations with the first carrier. This method allows the first terminal device, after applying (or using) the first configuration, to multicast or broadcast data corresponding to multiple radio link control bearer entities on the first carrier. This enables receiving terminal devices that do not support SLCA to receive data from the first terminal device, achieving normal data transmission between SLCA-supporting and non-SLCA-supporting terminal devices and ensuring the reliability of sidelink communication. The multiple radio link control bearer entities are established by the first terminal device according to the multiple radio link control bearer configurations, and these multiple radio link control bearer entities are used to transmit the same data. Each radio link control bearer entity includes a radio link control entity and a logical channel.

[0098] For example, the following are some possible examples illustrating the implementation process of the network device transmitting the first configuration to the first terminal device in the above-mentioned method two.

[0099] Example 1: After determining the first configuration, the network device can encapsulate the first configuration in a sidelink radio bearer configuration. Then, the network device can transmit the sidelink radio bearer configuration to the first terminal device using communication methods such as unicast, broadcast, or multicast.

[0100] In one example, when the first configuration includes a packet data aggregation layer protocol entity configuration, the sidelink radio bearer configuration may include (or be associated with or correspond to) other radio link control bearer configurations besides the first radio link control bearer configuration.

[0101] In another example, when the first configuration does not include the Packet Data Convergence Layer Protocol (PDLP) entity configuration, the sidelink radio bearer configuration may include (or be associated with or correspond to) the PDLP entity configuration and other radio link control bearer configurations besides the first radio link control bearer configuration.

[0102] Optionally, the sidelink radio bearer configuration may also include (or be associated with or correspond to) carrier information (such as carrier name, carrier index, or carrier identifier) ​​corresponding to multiple radio link control bearer configurations. For example, address information may include, but is not limited to, source address identifier (such as source L2 ID), source address name, destination address identifier (such as destination L2 ID or destination ID), or destination address name. Optionally, address information may also include communication type. The communication type may include unicast, multicast, or broadcast. Optionally, for unicast, the destination address identifier is the identifier of the receiving terminal device. For multicast, the destination address identifier is the group identifier (group destination L2 ID). For broadcast, the destination address identifier is the destination address identifier corresponding to the service type.

[0103] Optionally, the packet data aggregation layer protocol entity configuration can be generated by the CU. After generating the packet data aggregation layer protocol entity configuration, the CU can send it to the DU. For example, the CU can encapsulate the packet data aggregation layer protocol entity configuration in an RRC message and send it to the DU. After receiving the RRC message, the DU can send the RRC message to the first terminal device, or it can encapsulate the packet data aggregation layer protocol entity configuration parsed from the RRC message in another message and send it to the first terminal device. In one possible implementation, the DU and CU can be different network devices. For example, when the DU and CU are different network devices, they can be two different network devices belonging to the same communication architecture (such as 3GPP architecture or ORAN architecture), or they can be two network devices belonging to different communication architectures (such as one network device of 3GPP architecture and the other network device of ORAN architecture). In another possible implementation, the DU and CU can also be set up separately, as independent units, located in different network devices. For example, the network device containing the DU as an independent unit and the network device containing the CU as an independent unit can be two different network devices belonging to the same communication architecture (such as 3GPP architecture or ORAN architecture), or they can be two network devices belonging to different communication architectures (such as one network device of 3GPP architecture and the other network device of ORAN architecture). In another possible implementation, the DU and CU can also be combined into a single network device, which can be a network device of 3GPP architecture or a network device of ORAN architecture. In yet another possible implementation, the DU and CU can also be integrated as two independent units into the same network element, which is located in a network device, which can be a network device of 3GPP architecture or a network device of ORAN architecture.

[0104] Optionally, the radio link control bearer configuration can be generated by the DU. The implementation process of the DU generating and sending the radio link control bearer configuration can be found in the implementation process of the DU generating and sending the first configuration in Method 1 above, and will not be repeated here.

[0105] Example 2: After determining the first configuration, the network device can transmit the first configuration to the first terminal device according to communication methods such as unicast communication, broadcast communication or multicast communication.

[0106] In one example, when the first configuration includes a packet data aggregation layer protocol entity configuration, the network device can also transmit other radio link control bearer configurations associated with or corresponding to the first configuration, excluding the first radio link control bearer configuration, to the first terminal device in accordance with communication methods such as unicast communication, broadcast communication, or multicast communication.

[0107] In another example, when the first configuration does not include the packet data aggregation layer protocol entity configuration, the network device may also transmit the packet data aggregation layer protocol entity configuration associated with or corresponding to the first configuration, as well as other radio link control bearer configurations other than the first radio link control bearer configuration, to the first terminal device in accordance with communication methods such as unicast communication, broadcast communication, or multicast communication.

[0108] Optionally, the first configuration may include at least one of the following: address information or carrier information corresponding to other radio link control bearer configurations, or it may not include address information and carrier information corresponding to other radio link control bearer configurations. When the first configuration does not include address information and carrier information corresponding to other radio link control bearer configurations, the network device may transmit at least one of the following associated with the first configuration: address information or carrier information corresponding to other radio link control bearer configurations, to the first terminal device according to communication methods such as unicast communication, broadcast communication, or multicast communication.

[0109] Example 3: After determining the sidelink radio bearer configuration, the network device can transmit the sidelink radio bearer configuration as the first configuration to the first terminal device according to communication methods such as unicast communication, broadcast communication or multicast communication.

[0110] For example, the sidelink radio bearer configuration may include, but is not limited to, packet data aggregation layer protocol entity configuration, multiple radio link control bearer configurations, or the association between a first radio link control bearer configuration and a first carrier among multiple radio link control bearer configurations. In one example, the sidelink radio bearer configuration may also include at least one of the following: address information or carrier information corresponding to other radio link control bearer configurations besides the first radio link control bearer configuration among multiple radio link control bearer configurations. In another example, the sidelink radio bearer configuration may not include address information and carrier information corresponding to other radio link control bearer configurations besides the first radio link control bearer configuration among multiple radio link control bearer configurations; however, the sidelink radio bearer configuration may be associated with or correspond to address information or carrier information corresponding to other radio link control bearer configurations besides the first radio link control bearer configuration among multiple radio link control bearer configurations.

[0111] Method 3: The first terminal device obtains the first configuration through pre-configuration.

[0112] Optionally, when the first terminal device is in an OOC state, it can obtain the first configuration through pre-configuration. In one example, the first terminal device obtains the pre-configured first configuration through a network device, for example, the core network. In another example, when the first terminal device needs the first configuration, it can obtain it through a locally pre-saved configuration. This first configuration can be pre-determined by the network device and sent to the first terminal device for storage, or it can be pre-configured in the chip at the factory. Optionally, the implementation process of the network device determining the first configuration can refer to the implementation process of Method 1 or Method 2 above, and will not be repeated here.

[0113] It should be noted that the network devices in Method 1, Method 2, or Method 3 described above can also determine the first configuration using the following implementation process. Optionally, the network device may not specify which radio link control bearer configuration the first carrier is associated with, and may generate the first configuration based on the packet data aggregation layer protocol entity configuration and multiple radio link control bearer configurations, or it may generate the first configuration based on multiple radio link control bearer configurations. This first configuration does not include which radio link control bearer configuration the first carrier is associated with. It should be understood that the network device may specify which carriers each of the multiple radio link control bearer configurations is associated with, or it may not specify which carriers each of the multiple radio link control bearer configurations is associated with. It should be noted that when the network device does not specify which radio link control bearer configuration the first carrier is associated with, the terminal device can determine which radio link control bearer configuration the first carrier is associated with. Thus, this method enables the first terminal device to broadcast or multicast data corresponding to the wireless link control bearer entity established by the first wireless link control bearer configuration on the first carrier, thereby enabling normal data transmission between terminal devices that support SL CA and terminal devices that do not support SL CA, ensuring the reliability of sidelink communication.

[0114] Step 302: The first terminal device multicasts or broadcasts the data corresponding to the first radio link control bearer entity on the first carrier.

[0115] Optionally, the first terminal device may multicast or broadcast data transmitted through the first radio link control bearer entity on the first carrier. Alternatively, the first terminal device may multicast or broadcast the data carried by the first radio link control bearer entity on the first carrier. Or, the first terminal device may multicast or broadcast data on the first carrier according to the configuration of the first radio link control bearer.

[0116] Considering PDCP duplication, if the first terminal device uses the PDCP duplication mechanism, one PDCP entity will correspond to two or more radio link control bearer entities. The PDCP duplication mechanism generally refers to the PDCP entity copying the PDCP PDU and submitting it to the associated two or more radio link control bearer entities for processing and transmission. Based on this, when the first terminal device obtains multiple radio link control bearer configurations from the network device, it can establish corresponding radio link control bearer entities according to these configurations and transmit the same data through each of these multiple radio link control bearer entities.

[0117] In one possible implementation, when the first configuration includes a Packet Data Convergence Layer Protocol (PDLP) entity configuration and multiple Radio Link Control (RLC) bearer configurations, if the first terminal device supports SL CA, it can establish or reconfigure a Sidelink Radio Bearer (SLRB) based on the PDLP entity configuration, the first RLC bearer configuration, and other RLC bearer configurations. Then, the first terminal device can perform sidelink communication on the established SLRB; for example, it can multicast or broadcast data (such as SL signaling or SL data) on the established SLRB. The SLRB includes a PDLP entity and multiple RLC bearer entities. These multiple RLC bearer entities may include the first RLC bearer entity, and all multiple RLC bearer entities can be used to transmit the same data.

[0118] In another possible implementation, when the first configuration includes multiple radio link control bearer configurations, and the first terminal device obtains the packet data aggregation layer protocol entity configuration through other means, if the first terminal device supports SL CA, then the first terminal device can establish or reconfigure a sidelink radio bearer (SLRB) based on the packet data aggregation layer protocol entity configuration and the multiple radio link control bearer configurations. Then, the first terminal device can perform sidelink communication on the established SLRB.

[0119] In another possible implementation, when the first configuration is included in the sidelink radio bearer configuration, or when the sidelink radio bearer configuration is the first configuration, if the first terminal device supports SL CA, the first terminal device can establish or reconfigure the sidelink radio bearer SLRB according to the sidelink radio bearer configuration. Then, the first terminal device can perform sidelink communication on the established SLRB.

[0120] The following describes the implementation process of the first terminal device multicasting or broadcasting the data corresponding to the first radio link control bearer entity on the first carrier after obtaining the first configuration from the network device, through the following possible implementation methods.

[0121] Method 1: When the first configuration includes the association between the first radio link control bearer configuration and the first carrier, the first terminal device, if it supports SL CA, can establish a first radio link control bearer entity based on the first radio link control bearer configuration included in the first configuration. The carrier used for data transmission corresponding to the logical channel included in the first radio link control bearer entity is the first carrier. Subsequently, the first terminal device can multicast or broadcast the data corresponding to the first radio link control bearer entity (such as RLC data or RLC PDUs) on the first carrier.

[0122] Method 2: When the first terminal device receives indication information from the network device, and this indication information indicates that the first radio link control bearer configuration is associated with the first carrier, the first terminal device, if it supports SLCA, can establish a first radio link control bearer entity according to the first radio link control bearer configuration included in the first configuration. Subsequently, the first terminal device can multicast or broadcast the data corresponding to the first radio link control bearer entity established by the first radio link control bearer configuration on the first carrier.

[0123] Method 3: When the first configuration does not include the association between the first radio link control bearer configuration and the first carrier, and no indication information is obtained from the network device, the first terminal device, if it supports SL CA, can select one radio link control bearer configuration (such as the first radio link control bearer configuration) from among multiple radio link control bearer configurations to establish an association with the first carrier, or it can select multiple first radio link control bearer configurations from among multiple radio link control bearer configurations to establish an association with the first carrier. Afterwards, after establishing the first radio link control bearer entity corresponding to the first radio link control bearer configuration, the first terminal device can multicast or broadcast the data corresponding to the first radio link control bearer entity established by the first radio link control bearer configuration on the first carrier.

[0124] As can be seen from steps 301 to 302 above, when one or more first radio link control bearer configurations are associated with the first carrier, when the first terminal device needs to transmit data (such as sidelink data), it can use the first radio link control bearer entity and the first carrier to multicast or broadcast the data to be transmitted. This can effectively ensure that receiving terminal devices that do not support SL CA can receive data from the first terminal device normally on the first carrier, thereby enabling normal data transmission between terminal devices that support SL CA and terminal devices that do not support SL CA, thus ensuring the reliability of sidelink communication and effectively improving the quality of sidelink communication.

[0125] Figure 4 A flowchart illustrating another communication method provided in an embodiment of this application is shown as an example. This method is applicable to... Figure 1a , Figure 1b The illustrated communication system architecture. This method can be implemented through data interaction between multiple communication devices (such as a first communication device and a second communication device). To facilitate the introduction of the technical solutions provided in the embodiments of this application, the following uses the first communication device as a first terminal device and the second communication device as a network device as an example to describe the flow of the communication method implemented through data interaction between the first and second communication devices. Figure 4 As shown, the method includes:

[0126] Step 401: The first terminal device obtains the second configuration from the network device.

[0127] In one possible implementation, the second configuration may include a Packet Data Convergence Layer Protocol (PDCP) split configuration (e.g., the Data Split Threshold configuration in the More Than One RLC configuration). The PDCP split configuration instructs multiple data items (e.g., multiple data items to be transmitted, which may be the same or different data, as not limited in this embodiment) in the first terminal device to be transmitted through multiple Radio Link Control (RLC) bearer entities. These multiple RLC bearer entities are established by the first terminal device according to the multiple RLC bearer configurations. Optionally, in the PDCP split configuration, the multiple RLC bearer configurations are associated with different carriers. In other words, the RLC entities established by the multiple RLC bearer configurations are associated with different carriers. Each RLC bearer configuration may include a RLC entity configuration and a logical channel configuration, and the logical channel configuration may be associated with the carrier corresponding to that RLC bearer configuration. Optionally, the different carriers may include a first carrier. In one example, the second configuration may be included in the Packet Data Convergence Layer Protocol (PDCP) entity configuration. In another example, the packet data aggregation layer protocol entity configuration can be used as a second configuration, which includes the PDCP split configuration.

[0128] In another possible implementation, the second configuration may not include the PDCP split configuration. For example, this second configuration may include, but is not limited to, packet data aggregation layer protocol entity configuration, radio link control bearer configuration, address information, or carrier information. Optionally, the number of packet data aggregation layer protocol entity configuration, radio link control bearer configuration, address information, or carrier information may be one or more.

[0129] The following is an exemplary description of PDCP split configuration. For example, consider a first terminal device that needs to transmit 10 data items, and the first terminal device corresponds to two Radio Link Control Bearer Entities (RCBs) (e.g., RCB 1 and RCB 2). Optionally, RCB 1 can be associated with one or more carriers, and RCB 2 can be associated with one or more carriers. The carriers associated with RCB 1 and RCB 2 can be the same or different. For example, if RCB 1 is associated with carrier 1 and RCB 2 is associated with carrier 2, when the first terminal device applies the PDCP split configuration, the first terminal device can transmit a portion of the 10 data items using carrier 1 on RCB 1, and transmit another portion of the 10 data items using carrier 2 on RCB 2.

[0130] For example, the following describes the implementation process of the first terminal device obtaining the second configuration from the network device through several possible implementation methods.

[0131] Implementation Method 1: The first terminal device sends sixth information to the network device. The network device receives the sixth information. In one example, the sixth information can be used to indicate that the first terminal device supports SL CA and / or can be used to indicate that the destination address supports SL CA. The destination address can be used to indicate the receiving terminal device for sidelink communication performed by the first terminal device. In another example, the sixth information can also be used to indicate that the first terminal device does not support SL CA and / or can be used to indicate that the destination address does not support SL CA. Optionally, SL CA may include a sidelink SL packet data aggregation layer protocol entity PDCP split.

[0132] For example, the sixth information can be carried in a terminal device capability information message or a sidelink terminal device information message. When the first terminal device is in a radio resource control (RFC) connection state, it can send a terminal device capability information message or a sidelink terminal device information message to the network device. The sidelink terminal device information message is used to request the second configuration, or it can also be used to request a sidelink radio bearer configuration, which includes the second configuration. Optionally, when the sixth information is carried in a terminal device capability information message, the first terminal device, after sending the terminal device capability information message to the network device, will also send a sidelink terminal device information message to the network device.

[0133] In one possible approach, the first terminal device, during the process of obtaining the second configuration, also obtains the seventh information. Optionally, before the first terminal device sends the sixth information to the network device, the access layer of the first terminal device can obtain the seventh information from the upper layer of the first terminal device. In one possible implementation, the seventh information can be used to indicate whether the destination address supports SL CA, or it can also be used to indicate whether the destination address does not support SL CA. In another possible implementation, the seventh information can also be used to indicate whether the first terminal device supports SL CA, or it can also be used to indicate whether the first terminal device does not support SL CA. It should be understood that the first terminal device may also be configured to support SL CA without needing to know from the upper layer. Optionally, the first terminal device can also obtain information on whether it supports SL CA from the network device where the cell it is camped, or it can obtain information on whether it supports SL CA from the receiving terminal device. Optionally, the seventh information may also include the association between the service type and the destination address and / or information on the carriers supported by the service type (such as the carrier name, index, or identifier).

[0134] After the network device receives the sidelink terminal device information message from the first terminal device, it can determine the second configuration based on the sixth information. Then, the network device can transmit the second configuration to the first terminal device. The following examples illustrate the implementation process of the network device determining the second configuration in Method 1.

[0135] Example 1: When the sixth information indicates that the first terminal device supports SL CA and the destination address supports SL CA, in order to enable multiple data in the first terminal device to be transmitted through multiple radio link control bearer entities, the network device can configure multiple corresponding radio link control bearer configurations to map (or associate) different carriers for the Packet Data Convergence Layer Protocol entity. Optionally, the different carriers may include the first carrier. Then, the network device can generate a PDCP split configuration based on the different carriers mapped by the multiple radio link control bearer configurations and the information indicating that the first terminal device should split and transmit multiple data through multiple radio link control bearer entities, and can generate a second configuration based on the PDCP split configuration. This second configuration may also include the association between the first carrier and the first radio link control bearer configuration.

[0136] Example 2: When the sixth information indicates that the first terminal device supports SL CA but the destination address does not support SL CA, in order to enable normal data transmission between the first terminal device (which does not support SL CA) and the receiving terminal device (which supports SL CA), the network device can select one of the multiple radio link control bearer configurations (e.g., the first radio link control bearer configuration) from the packet data aggregation layer protocol entity configuration to establish an association with the first carrier. Then, the network device can generate a second configuration based on the packet data aggregation layer protocol entity configuration, the first radio link control bearer configuration, and the association between the first radio link control bearer configuration and the first carrier. This second configuration does not include the PDCP split configuration, but it does include the packet data aggregation layer protocol entity configuration, the first radio link control bearer configuration, and the association between the first carrier and the first radio link control bearer configuration. In other words, this second configuration can be used to instruct the first terminal device to use the first carrier to transmit multiple data items from the first terminal device on the first radio link control bearer entity. Thus, the first terminal device can transmit multiple data items from its own data to the receiving terminal device (which does not support SL CA).

[0137] Example 3: When the sixth piece of information indicates that the first terminal device does not support SL CA, the network device can map (or associate) a certain radio link control bearer configuration (such as the first radio link control bearer configuration) corresponding to the packet data aggregation layer protocol entity configuration to the first carrier. Then, the network device can generate a second configuration based on the packet data aggregation layer protocol entity configuration, the first radio link control bearer configuration, and the association between the first radio link control bearer configuration and the first carrier. This second configuration does not include the PDCP split configuration, but it does include the packet data aggregation layer protocol entity configuration, the first radio link control bearer configuration, and the association between the first carrier and the first radio link control bearer configuration.

[0138] Implementation Method 2: When the first terminal device is stationed in or connected to one of the multiple cells in the coverage area of ​​the network device, it can obtain the second configuration from the network device via multicast or broadcast.

[0139] In one possible implementation, after the network device generates the second configuration in advance or beforehand, it can multicast or broadcast the second configuration to the outside world in accordance with the communication methods of multicast or broadcast communication.

[0140] In another possible implementation, after the network device generates the second configuration in advance or beforehand, it can also encapsulate the second configuration within the sidelink radio bearer configuration. Subsequently, the network device can multicast or broadcast the sidelink radio bearer configuration externally according to multicast or broadcast communication methods.

[0141] Optionally, the network device may also unicast the second configuration to the first terminal device.

[0142] For example, the sidelink radio bearer configuration may include, but is not limited to, packet data aggregation layer protocol entity configuration, one or more radio link control bearer configurations, and carrier information corresponding to one or more radio link control bearer configurations.

[0143] For example, the following examples illustrate the implementation process of generating a second configuration in advance or beforehand for network devices.

[0144] Example 1: A network device can configure multiple Radio Link Control Bearer (RLC) configurations corresponding to a Packet Data Convergence Layer (PDCP) entity, each mapping (or associating) different carriers. Then, the network device can generate a PDCP split configuration based on the different carriers mapped by the multiple RLC configurations and information instructing the first terminal device to split and transmit multiple data streams through the multiple RLC entities. Furthermore, based on the PDCP split configuration, a second configuration can be generated, which includes the PDCP split configuration.

[0145] Example 2: A network device can multicast or broadcast two (or two sets of) sidelink radio bearer configurations to terminal devices for the same Quality of Service (QoS) flow. One sidelink radio bearer configuration includes a PDCP split configuration in its Packet Data Convergence Layer (PDCL) entity configuration, which serves as a second configuration. The other sidelink radio bearer configuration does not include a PDCP split configuration, but one of its radio link control (NRC) bearer configurations may be associated with a first carrier. Optionally, the network device may not specify which NRC bearer configuration the first carrier is associated with in the sidelink radio bearer configuration, or it may not specify which carriers each NRC bearer configuration is associated with. It should be understood that the network device may specify which carriers each NRC bearer configuration is associated with in the sidelink radio bearer configuration. Thus, this method allows terminal devices receiving two sidelink radio bearer configurations to choose which sidelink radio bearer configuration to apply based on their actual needs, offering high flexibility and effectively meeting the diverse requirements of terminal devices. Optionally, the network device in the above implementation method one can also adopt the implementation process of Example 2 when determining the second configuration.

[0146] Implementation method 3: The first terminal device obtains the second configuration through pre-configuration.

[0147] Optionally, when the first terminal device is in an OOC state, it can obtain the second configuration through pre-configuration. In one example, the first terminal device obtains the pre-configured second configuration through a network device, for example, the core network. In another example, when the first terminal device needs the second configuration, it can obtain it through a locally pre-saved configuration. This second configuration can be pre-determined by the network device and sent to the first terminal device for storage, or it can be pre-configured in the chip at the factory. Optionally, the implementation process of the network device determining the second configuration can refer to the implementation process of implementation method one or implementation method two above, and will not be repeated here.

[0148] It should be noted that the network devices in implementation methods one, two, or three above can also determine the second configuration using the following implementation process. Optionally, the network device may not specify which radio link control bearer configuration the first carrier is associated with, and generate the second configuration based on the packet data aggregation layer protocol entity configuration and multiple radio link control bearer configurations, or it may generate the second configuration based on multiple radio link control bearer configurations. This second configuration does not include the PDCP split configuration, nor does it include the association between the first carrier and which radio link control bearer configuration. It should be noted that when the network device does not specify which radio link control bearer configuration the first carrier is associated with, the terminal device can determine which radio link control bearer configuration the first carrier is associated with.

[0149] Optionally, the radio link control bearer configuration in implementation method one, implementation method two, or implementation method three above can be generated by the DU. The implementation process of the DU generating and sending the radio link control bearer configuration can refer to the implementation process of the DU generating and sending the first configuration in implementation method one of step 301 above, and will not be repeated here. Optionally, the packet data aggregation layer protocol entity configuration in implementation method one, implementation method two, or implementation method three above can be generated by the CU. The implementation process of the CU generating and sending the radio link control bearer configuration can refer to the implementation process of the CU generating and sending the packet data aggregation layer protocol entity configuration in implementation method two of step 301 above, and will not be repeated here.

[0150] Step 402: The first terminal device controls the transmission of multiple data through the first wireless link to control the bearer entity.

[0151] The following describes the process by which the first terminal device multicasts or broadcasts multiple data from the first terminal device after obtaining the second configuration or sidelink radio bearer configuration (which includes the second configuration) from the network device, through several possible implementation methods.

[0152] Implementation Method 1: When the first terminal device does not support SL CA or the destination address does not support SL CA. In one example, when the second configuration is not included in the sidelink radio bearer configuration, if the second configuration includes a PDCP split configuration, the first terminal device may not apply the PDCP split configuration, but may apply other received configurations (such as one or more radio link control bearer configurations, packet data aggregation layer protocol entity configurations, etc.). When the second configuration includes the association between the first carrier and the first radio link control bearer configuration, after the first terminal device establishes or reconfigures the sidelink radio bearer SLRB (which may include packet data aggregation layer protocol entities, one or more radio link control bearer entities, etc.) using other configurations, if the first terminal device needs to transmit multiple data, the first terminal device can transmit the multiple data through the first radio link control bearer entity and using the first carrier. Here, the SLRB includes the first radio link control bearer entity corresponding to the first radio link control bearer configuration. When the second configuration does not include the association between the first carrier and the first radio link control bearer configuration, and the association between the first carrier and the first radio link control bearer configuration is not obtained from the network device, the first terminal device can select one of the one or more radio link control bearer configurations (such as the first radio link control bearer configuration) to establish an association with the first carrier. Afterwards, after the first terminal device establishes or reconfigures the SLRB according to other configurations, if the first terminal device needs to transmit multiple data, it can transmit these multiple data through the first radio link control bearer entity and using the first carrier. In this way, the first terminal device can use the first carrier to transmit these multiple data on the first radio link control bearer entity, enabling normal data transmission between terminal devices that do not support SLCA and terminal devices that support SLCA, ensuring the reliability of sidelink communication.

[0153] If the second configuration does not include a PDCP split configuration, the first terminal device can apply the second configuration and other received configurations. When the second configuration includes the association between the first carrier and the first radio link control bearer configuration, after the first terminal device establishes or reconfigures the SLRB using the second configuration and other received configurations, if the first terminal device needs to transmit multiple data, it can transmit the multiple data through the first radio link control bearer entity and using the first carrier. When the second configuration does not include the association between the first carrier and the first radio link control bearer configuration, and the association between the first carrier and the first radio link control bearer configuration is not obtained from the network device, the first terminal device can select one radio link control bearer configuration (such as the first radio link control bearer configuration) from one or more radio link control bearer configurations to establish an association with the first carrier. Subsequently, after the first terminal device establishes or reconfigures the SLRB according to the second configuration and other received configurations, if the first terminal device needs to transmit multiple data, it can transmit the multiple data through the first radio link control bearer entity and using the first carrier.

[0154] In another example, when the second configuration is included in the sidelink radio bearer configuration, if the second configuration includes a PDCP split configuration, the first terminal device may not apply the PDCP split configuration, but may apply other configurations in the sidelink radio bearer configuration besides the PDCP split configuration (such as packet data aggregation layer protocol entity configuration, one or more radio link control bearer configurations, etc.). When the second configuration includes the association between the first carrier and the first radio link control bearer configuration, after the first terminal device establishes or reconfigures the SLRB using other configurations in the sidelink radio bearer configuration besides the PDCP split configuration, if the first terminal device needs to transmit multiple data, it can transmit the multiple data through the first radio link control bearer entity and using the first carrier. When the second configuration does not include the association between the first carrier and the first radio link control bearer configuration, and the association between the first carrier and the first radio link control bearer configuration is not obtained from the network device, the first terminal device may select one radio link control bearer configuration (such as the first radio link control bearer configuration) from one or more radio link control bearer configurations to establish an association with the first carrier. Subsequently, after the first terminal device establishes or reconfigures the SLRB according to the configuration other than the PDCP split configuration in the side link radio bearer configuration, if the first terminal device needs to transmit multiple data, the first terminal device can control the bearer entity through the first radio link and use the first carrier to transmit the multiple data.

[0155] If the second configuration does not include a PDCP split configuration, the first terminal device can apply a sidelink radio bearer configuration. When the second configuration includes an association between the first carrier and the first radio link control bearer configuration, after the first terminal device establishes or reconfigures an SLRB using the sidelink radio bearer configuration, if the first terminal device needs to transmit multiple data, it can transmit the multiple data through the first radio link control bearer entity and using the first carrier. When the second configuration does not include an association between the first carrier and the first radio link control bearer configuration, and the association between the first carrier and the first radio link control bearer configuration is not obtained from the network device, the first terminal device can select one radio link control bearer configuration (such as the first radio link control bearer configuration) from one or more radio link control bearer configurations to establish an association with the first carrier. Subsequently, after the first terminal device establishes or reconfigures an SLRB according to the sidelink radio bearer configuration, if the first terminal device needs to transmit multiple data, it can transmit the multiple data through the first radio link control bearer entity and using the first carrier.

[0156] Optionally, if the first terminal device supports SL CA and the destination address supports SL CA, and if the second configuration obtained by the first terminal device from the network device includes a PDCP split configuration, then the first terminal device can apply the PDCP split configuration. In one example, when the second configuration includes the association relationships between multiple radio link control bearer configurations and different carriers, or when the first terminal device obtains the association relationships between multiple radio link control bearer configurations and different carriers from the network device, after establishing or reconfiguring the SLRB according to the PDCP split configuration, other configurations in the packet data aggregation layer protocol entity configuration besides the PDCP split configuration, and multiple radio link control bearer configurations, the first terminal device can multicast or broadcast the multiple data (such as SL signaling or SL data) through the multiple radio link control bearer entities included in the SLRB. The SLRB includes a packet data aggregation layer protocol entity and multiple radio link control bearer entities. In another example, when the second configuration does not include the association relationships between multiple radio link control bearer configurations and different carriers, and the network device does not obtain information on which carriers each radio link control bearer configuration is associated with, the first terminal device can allocate corresponding carriers to each radio link control bearer configuration based on the information of the carriers it supports, thus establishing the association relationships between the multiple radio link control bearer configurations and different carriers. Subsequently, after the first terminal device establishes or reconfigures the SLRB according to the side-link radio bearer configuration, if the first terminal device needs to transmit multiple data, it can multicast or broadcast these multiple data through the multiple radio link control bearer entities included in the SLRB.

[0157] Implementation Method Two: When the first terminal device does not support SL CA or the destination address does not support SL CA, when the first terminal device obtains two sidelink radio bearer configurations from the network device, it can identify these two sidelink radio bearer configurations. If one of the identified sidelink radio bearer configurations does not include a PDCP split configuration, the first terminal device can apply that sidelink radio bearer configuration. It can be understood that these two sidelink radio bearer configurations are the sidelink radio bearer configurations corresponding to the multiple data sets. When the sidelink radio bearer configuration includes the association between the first carrier and the first radio link control bearer configuration, or when the association between the first radio link control bearer configuration and the first carrier is obtained from the network device, after the first terminal device establishes or reconfigures the SLRB using the sidelink radio bearer configuration, if the first terminal device needs to transmit multiple data sets, it can transmit these multiple data sets through the first radio link control bearer entity and using the first carrier. The SLRB includes the first radio link control bearer entity corresponding to the first radio link control bearer configuration. When the sidelink radio bearer configuration does not include the association between the first carrier and the first radio link control bearer configuration, and the association between the first carrier and the first radio link control bearer configuration is not obtained from the network device, the first terminal device may select one of the one or more radio link control bearer configurations (such as the first radio link control bearer configuration) to establish an association with the first carrier. Subsequently, after the first terminal device establishes or reconfigures the SLRB according to the sidelink radio bearer configuration, if the first terminal device needs to transmit multiple data, it can transmit these multiple data through the first radio link control bearer entity and using the first carrier.

[0158] Optionally, if the first terminal device supports SL CA and the destination address supports SL CA, when the first terminal device obtains two sidelink radio bearer configurations from the network device, the first terminal device can identify these two sidelink radio bearer configurations. When it is identified that a sidelink radio bearer configuration includes a PDCP split configuration, the first terminal device can apply that sidelink radio bearer configuration. In one example, when the sidelink radio bearer configuration includes the association relationships between multiple radio link control bearer configurations and different carriers, or when the association relationships between multiple radio link control bearer configurations and different carriers are obtained from the network device, after the first terminal device establishes or reconfigures the SLRB using the sidelink radio bearer configuration, if the first terminal device needs to transmit multiple data, the first terminal device can multicast or broadcast these multiple data through the multiple radio link control bearer entities included in the SLRB. In another example, when the sidelink radio bearer configuration does not include the association relationships between multiple radio link control bearer configurations and different carriers, and the network device does not obtain information on which carriers each radio link control bearer configuration is associated with, the first terminal device can allocate corresponding carriers to each radio link control bearer configuration based on the information of the carriers it supports, thus establishing the association relationships between the multiple radio link control bearer configurations and different carriers. Subsequently, after the first terminal device establishes or reconfigures the SLRB according to the sidelink radio bearer configuration, if the first terminal device needs to transmit multiple data, it can multicast or broadcast these multiple data through the multiple radio link control bearer entities included in the SLRB.

[0159] Furthermore, when the first terminal device chooses not to apply the PDCP split configuration, it can send a first message to the network device. This first message can be used to instruct the first terminal device not to apply the PDCP split configuration. In one example, when the first terminal device does not support SL CA, the first message can carry (or associate) information indicating that the first terminal device does not support SL CA. In another example, when the destination address does not support SL CA, the first message can carry (or associate) the destination address, and the destination address is a destination address that does not support SL CA. Thus, this method allows the network device to configure the sidelink radio bearer configuration for establishing SLRB for the first terminal device or the destination address requested by the first terminal device without configuring the PDCP split configuration, making the sidelink radio bearer configuration more targeted and able to meet the different needs of the terminal device.

[0160] As can be seen from steps 401 to 402 above, when the first terminal device does not support SL CA or the destination address corresponding to the receiving terminal device does not support SL CA, the first terminal device can choose not to apply PDCPsplit configuration. It can transmit multiple data in the first terminal device through the first radio link control bearer entity corresponding to the first carrier. This can ensure that the receiving terminal device that does not support SL CA can normally receive multiple data from the first terminal device on the first carrier, realize normal data transmission between the terminal device that supports SL CA and the terminal device that does not support SL CA, thereby ensuring the reliability of the sidelink communication and effectively improving the quality of the sidelink communication.

[0161] Figure 5 This illustration shows a flowchart of yet another communication method provided in an embodiment of this application. This method is applicable to... Figure 1a , Figure 1b The illustrated communication system architecture. This method can be implemented through data interaction between multiple communication devices (such as a first communication device and a second communication device). Optionally, the first communication device can be a second terminal device or a component (such as a chip, chip system, or circuit) capable of supporting the functions required for the second terminal device to implement the method. The second communication device can be a third terminal device or a component (such as a chip, chip system, or circuit) capable of supporting the functions required for the third terminal device to implement the method. For example, the second terminal device can be... Figure 1a The terminal device 120i shown can be a third terminal device. Figure 1a The terminal device 120j shown; or the second terminal device can be Figure 1a The terminal device 120f shown can be a third terminal device. Figure 1a The intended terminal device weighs 120g; or the second terminal device may be... Figure 1a The terminal device 120a shown can be a third terminal device. Figure 1a The terminal device 120b shown; or the second terminal device may be Figure 1b The terminal device 400 shown can be a third terminal device. Figure 1b The terminal device 501 or terminal device 502 are shown. To facilitate the introduction of the technical solutions provided in the embodiments of this application, the following uses a first communication device as the second terminal device and a second communication device as the third terminal device as an example to describe the flow of the communication method achieved through data interaction between the first communication device and the second communication device. Figure 5 As shown, the method includes:

[0162] Step 501: The second terminal device determines that it supports sidelink carrier aggregation.

[0163] Optionally, the sidelink SL carrier aggregation (CA) may include sidelink cross-carrier scheduling and / or sidelink cross-carrier feedback.

[0164] The following describes the process of determining whether a second terminal device supports SLCA through several possible implementation methods.

[0165] Method 1: The access layer of the second terminal device obtains the eighth information from the upper layer of the second terminal device. Based on the eighth information, the second terminal device can determine that it supports SL CA. The eighth information is used to indicate that the second terminal device supports SL CA.

[0166] Method 2: The second terminal device obtains capability information from the network device. Based on the capability information, the second terminal device can determine whether it supports side-link carrier aggregation. Optionally, the capability information is used to indicate that the second terminal device supports side-link carrier aggregation.

[0167] Method 3: The capability to support sidelink carrier aggregation is configured in the second terminal device, and the second terminal device itself can be aware of this capability.

[0168] Optionally, any combination of methods one, two, and three above can be used.

[0169] Step 502: The second terminal device sends fourth information to the third terminal device on the second carrier. The third terminal device receives the fourth information.

[0170] In this method, the third terminal device is the receiving terminal device for sidelink communication with the second terminal device. The fourth information (such as Sidelink Control Information (SCI)) can be used to instruct the second and third terminal devices to perform sidelink transmission on the third carrier. The second and / or third carriers do not include the first carrier. The first carrier generally refers to the carrier corresponding to the terminal device performing single-carrier communication, and the second and third carriers are different. It should be understood that the second and / or third carriers not including the first carrier can mean that the second and / or third carriers are different from the first carrier. Optionally, the second and / or third carriers can be carriers associated (or mapped or corresponded) with the destination address of the third terminal device. Thus, by restricting the second and / or third carriers from including the first carrier, this method not only ensures that receiving terminal devices supporting SL CA can normally receive sidelink data from the second terminal device on the third carrier, but also ensures that receiving terminal devices not supporting SL CA can normally receive sidelink data from the second terminal device on the first carrier, thereby guaranteeing the reliability of sidelink communication.

[0171] Optionally, the access layer of the second terminal device can obtain the fifth information from the upper layer of the second terminal device. In one possible implementation, when the fifth information is used to indicate that the destination address corresponding to the third terminal device supports SL CA, the second carrier and / or the third carrier may include the first carrier. It should be understood that the second carrier and / or the third carrier including the first carrier may mean that the second carrier and / or the third carrier is the same as the first carrier, and the destination address corresponding to the third terminal device supporting SL CA may mean that the destination address corresponding to the third terminal device supports the second carrier and / or the third carrier. In this way, when the destination address corresponding to the third terminal device supports SL CA, regardless of which carrier the second terminal device sends scheduling information (such as SCI information) on, or regardless of which carrier the second terminal device transmits sidelink data on, the third terminal device can receive it normally on the corresponding carrier. In another possible implementation, when the fifth information is used to indicate that the destination address corresponding to the third terminal device does not support SL CA, the second carrier and / or the third carrier does not include the first carrier. Thus, even if the destination address corresponding to the third terminal device does not support SL CA, although the third terminal device cannot receive the scheduling information or sidelink data sent by the second terminal device on the second or third carrier, it can still be guaranteed that the third terminal device can normally receive the sidelink data transmitted by the second terminal device on the first carrier.

[0172] It should be understood that the destination address corresponding to the third terminal device not supporting SL CA can mean that the destination address corresponding to the third terminal device does not support the second carrier and / or the third carrier. Therefore, if the second carrier and / or the third carrier includes the first carrier, the third terminal device will not receive the fourth information from the second terminal device, nor will it receive the sidelink data transmitted by the second terminal device on the second or third carrier. Furthermore, if the destination address corresponding to the third terminal device does not support the second carrier and / or the third carrier, but the second carrier and / or the third carrier does not include the first carrier, the third terminal device, although unable to receive the fourth information from the second terminal device, can normally receive the sidelink data transmitted by the second terminal device on the first carrier.

[0173] Optionally, when the destination address corresponding to the third terminal device supports SL CA, the third terminal device can provide feedback to the second terminal device on the second carrier or the third carrier regarding the reception status of the sidelink data transmitted by the second terminal device on the third carrier. For example, the third terminal device can send a Hybrid Automatic Repeat Request (HARQ) feedback to the second terminal device on the second carrier or the third carrier. The HARQ feedback can be used to indicate the reception status of the sidelink transmission on the third carrier, such as indicating successful reception (ACK) or unsuccessful reception (NACK).

[0174] For example, the following describes the implementation process of a third terminal device sending HARQ feedback to another second terminal device on a second carrier or a third carrier through several possible implementation methods.

[0175] Implementation Method 1: When the fourth information indicates that the side link transmission on the third carrier is multicast communication, the third terminal device can send HARQ feedback to the second terminal device on the second carrier or the third carrier.

[0176] Implementation Method 2: When the fourth information indicates that the side link transmission on the third carrier is HARQ feedback enabled communication, the third terminal device can send HARQ feedback to the second terminal device on the second carrier or the third carrier.

[0177] It should be understood that the above implementation method one and the above implementation method two can be used in combination.

[0178] As can be seen from steps 501 to 502 above, when the destination address corresponding to the receiving terminal device does not support SL CA, by restricting the second carrier and / or the third carrier to exclude the first carrier, it can be ensured that the receiving terminal device that does not support SL CA can normally receive sidelink data from the second terminal device on the first carrier, thereby realizing normal data transmission between the terminal device that supports SL CA and the terminal device that does not support SL CA, thus ensuring the reliability of sidelink communication and effectively improving the quality of sidelink communication.

[0179] It should be noted that in the description of this application, "at least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, "at least one of A, B, and C" includes A, B, C, AB, AC, BC, or ABC. Furthermore, unless otherwise specified, the ordinal numbers "first," "second," "third," etc., mentioned in the embodiments of this application are used to distinguish multiple objects and are not used to limit the order, sequence, priority, or importance of multiple objects. In addition, the terms "including," "comprising," "having," and their variations appearing in this application all mean "including but not limited to," unless otherwise specifically emphasized.

[0180] Furthermore, it should be noted that each step in the above embodiments can be executed by the corresponding device, or by components such as chips, processors, or chip systems within that device. This application does not limit the scope of these steps. The above embodiments are only illustrated by examples of execution by the corresponding device.

[0181] It should be noted that in the above embodiments, some steps may be selected for implementation, and the order of the steps in the figures may be adjusted. This application does not limit this. It should be understood that performing some of the steps in the figures, adjusting the order of the steps, or combining them in a specific implementation all fall within the protection scope of this application.

[0182] It is understood that, in order to achieve the functions described in the above embodiments, each device involved in the above embodiments includes a hardware structure and / or software module corresponding to perform each function. Those skilled in the art should readily recognize that, based on the units and method steps of the various examples described in conjunction with the embodiments disclosed in this application, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed by hardware or by computer software driving hardware depends on the specific application scenario and design constraints of the technical solution.

[0183] It should be noted that the "steps" in the embodiments of this application are merely illustrative and are intended to better understand one method of presentation used in the embodiments. They do not constitute a substantial limitation on the execution of the solution of this application. For example, the "step" can also be understood as a "feature". Furthermore, the steps do not constitute any limitation on the execution order of the solution of this application. Any changes to the order of steps, or the merging or splitting of steps made on this basis without affecting the overall solution implementation, resulting in a new technical solution, are also within the scope of disclosure of this application.

[0184] Based on the same concept, embodiments of this application also provide a possible communication device, which is suitable for... Figure 1a , Figure 1b The diagram illustrates a communication system architecture. Optionally, the communication device can be a communication equipment (such as a first communication device or a second communication device) or a component (such as a chip, chip system, or circuit) capable of supporting the communication equipment in implementing the functions required for the communication method. In one example, when the communication device is a first communication device (such as a first terminal device or a second terminal device), the communication device is used to implement the technical solutions involved in the first communication device in the above embodiments, or the module (such as a chip) of the communication device is used to implement the technical solutions involved in the first communication device in the above embodiments, thus also achieving the beneficial effects of the first communication device in the above embodiments. For example, the first communication device can be as follows: Figure 1a The terminal device shown (e.g., terminal device 120f, terminal device 120g, terminal device 120a, terminal device 120b, or terminal device 120i, etc.), or it could be as follows: Figure 1b The terminal device shown is an example (e.g., terminal device 400, etc.). For instance, taking a chip within a first communication device as an example, when the communication device is a chip, it includes a transceiver and a processor, but does not include a memory. The transceiver exists as an input / output interface, which is used by the chip to implement the transmission and reception of the first communication device. This input / output interface may include an input interface and / or an output interface. The input interface enables the first communication device to receive data, and the output interface enables the first communication device to transmit data. The processor is used to read and execute corresponding computer programs or instructions, thereby enabling the corresponding functions of the first communication device to be implemented. Optionally, when the chip implements the corresponding functions of the first communication device in the above embodiments, the input / output interface can implement the transmission and reception operations performed by the first communication device in the above embodiments; the processor can implement other operations performed by the first communication device in the above embodiments besides the transmission and reception operations. For specific details, please refer to the above description. Figures 3 to 5 The description of the first communication device in the method embodiment shown will not be detailed here.

[0185] In another example, when the communication device is a second communication device (such as a network device or a third terminal device), the communication device is used to implement the technical solutions involved in the second communication device in the above embodiments, or the module (such as a chip) of the communication device is used to implement the technical solutions involved in the second communication device in the above embodiments, thus also achieving the beneficial effects of the second communication device in the above embodiments. For example, when the first terminal device is... Figure 1a When the terminal device 120f or terminal device 120g is as shown, the second communication device can be as follows: Figure 1a The RAN device 110b shown, or when the first terminal device is Figure 1a When the terminal device 120a or terminal device 120b is shown, the second communication device can be as follows: Figure 1a The illustrated RAN device 110a. For example, when the first communication device is... Figure 1b When the terminal device 400 is as shown, the second communication device can be as follows: Figure 1b The terminal device shown (e.g., terminal device 501 or terminal device 502, etc.), or it could be as follows: Figure 1b The illustrated RAN device 600. For example, taking a chip within a second communication device as an example, when the communication device is a chip, it includes a transceiver and a processor, but does not include a memory. The transceiver exists as an input / output interface, which is used by the chip to implement the transmission and reception of the second communication device. This input / output interface may include an input interface and / or an output interface. The input interface enables the second communication device to receive data, and the output interface enables the second communication device to transmit data. The processor is used to read and execute corresponding computer programs or instructions, thereby enabling the corresponding functions of the second communication device to be implemented. Optionally, when the chip implements the corresponding functions of the second communication device in the above embodiments, the input / output interface can implement the transmission and reception operations performed by the second communication device in the above embodiments; the processor can implement other operations performed by the second communication device in the above embodiments besides the transmission and reception operations. For more detailed descriptions, please refer to the above. Figures 3 to 5 The description of the second communication device in the method embodiment shown will not be detailed here.

[0186] See Figure 6 The communication device 600 includes a communication module 601 (or transceiver module, used for sending and receiving data) and a processing module 602. The communication device 600 is used to implement the above-mentioned... Figures 3 to 5 The method embodiments shown illustrate the functions of the first communication device (e.g., a first terminal device or a second terminal device) or the second communication device (e.g., a network device or a third terminal device).

[0187] Optionally, the communication module 601 may include a receiving module and / or a transmitting module. The receiving module can be used by the communication device 600 to receive signals (information or data, etc.); the transmitting module can be used by the communication device 600 to transmit signals (information or data, etc.). The transmitting module can transmit signals (information or data, etc.) under the control of the processing module 602, and the receiving module can receive signals (information or data, etc.) under the control of the processing module 602.

[0188] When the communication device 600 is used to achieve the above Figure 3 In the illustrated method embodiment, the first communication device functions as follows: Communication module 601 is used to acquire a first configuration from a network device. The first configuration includes a first radio link control bearer configuration, which is associated with a first carrier. The first radio link control bearer configuration is one of multiple radio link control bearer configurations corresponding to a packet data aggregation layer protocol entity configuration. This first radio link control bearer configuration is used to establish a first radio link control bearer entity. The first carrier is the carrier corresponding to the terminal device performing single-carrier communication. Processing module 602 is used to multicast or broadcast data corresponding to the first radio link control bearer entity on the first carrier.

[0189] When the communication device 600 is used to achieve the above Figure 3 In the method embodiment shown, the second communication device functions as follows: a processing module 602, used to determine a first configuration; and a communication module 601, used to send (or broadcast, etc.) the first configuration to the first communication device (e.g., a first terminal device).

[0190] When the communication device 600 is used to achieve the above Figure 4 In the illustrated method embodiment, the first communication device functions as follows: a communication module 601 is used to obtain a second configuration from a network device. Exemplarily, the second configuration may or may not include a PDCP split configuration. The PDCP split configuration instructs multiple data items in the first terminal device to be transmitted through multiple radio link control bearer entities. These multiple radio link control bearer entities are established by the first terminal device according to multiple radio link control bearer configurations. Optionally, in the PDCP split configuration, the multiple radio link control bearer configurations are associated with different carriers. Optionally, the different carriers may include a first carrier. In one example, the second configuration may be included in a packet data aggregation layer protocol entity configuration. In another example, the packet data aggregation layer protocol entity configuration may serve as the second configuration, which includes the PDCP split configuration. A processing module 602 is used to transmit multiple data items in the first terminal device through the first radio link control bearer entity.

[0191] When the communication device 600 is used to achieve the above Figure 4 In the method embodiment shown, the second communication device functions as follows: a processing module 602, used to determine a second configuration; and a communication module 601, used to send (or broadcast, etc.) the second configuration to the first communication device (e.g., a first terminal device).

[0192] When the communication device 600 is used to achieve the above Figure 5 In the illustrated method embodiment, the first communication device functions as follows: Processing module 602 is used to determine that the second terminal device supports sidelink carrier aggregation. Communication module 601 is used to send fourth information to the third terminal device on the second carrier. The third terminal device is the receiving terminal device for sidelink communication between the second terminal device and the third terminal device. The fourth information can be used to instruct the second and third terminal devices to perform sidelink transmission on the third carrier. The second and / or third carriers do not include the first carrier. The first carrier can refer to the carrier corresponding to the terminal device performing single-carrier communication, and the second and third carriers are different.

[0193] When the communication device 600 is used to achieve the above Figure 5 In the illustrated method embodiment, the second communication device functions as follows: Communication module 601 is used to receive fourth information from the second terminal device on the second carrier. Communication module 601 is also used to receive sidelink data from the second terminal device on the third carrier. Communication module 601 is also used to send HARQ feedback to the second terminal device on the second or third carrier.

[0194] Among them, when the communication device 600 is used to achieve Figures 3 to 5 For a more detailed description of the communication module 601 and the processing module 602 regarding the functions of the first or second communication device in the method embodiments shown, please refer to the above. Figures 3 to 5 The descriptions of the first or second communication device in the method embodiments shown will not be repeated here.

[0195] It should be understood that the communication module 601 in the embodiments of this application can be implemented by a transceiver or transceiver-related circuit components, and the processing module 602 can be implemented by a processor or processor-related circuit components.

[0196] It should be noted that the module division in the embodiments of this application is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods. Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, exist as separate physical entities, or have two or more units integrated into one unit. The integrated units described above can be implemented in hardware or as software functional units.

[0197] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, or a server, etc.) or processor to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as a USB flash drive, a portable hard drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0198] Based on the same concept, embodiments of this application also provide a possible communication device, which is suitable for... Figure 1a or Figure 1bThe illustrated communication system architecture. Exemplarily, the communication device may be an apparatus required for executing the communication method provided in the embodiments of this application (such as a first communication device or a second communication device), or it may be a device containing an apparatus required for executing the communication method provided in the embodiments of this application. Optionally, the communication device may also be a chip disposed within a first communication device (or a second communication device). When the communication device is a chip disposed within a first communication device (or a second communication device), the communication device includes a transceiver and a processor, but does not include a memory. The transceiver exists as an input / output interface, which is used by the chip to implement the transmission and reception of the communication device. The input / output interface may include an input interface and / or an output interface. The input interface can enable the communication device to receive data, and the output interface can be used to enable the communication device to transmit data. The processor is used to read and execute corresponding computer programs or instructions, so that the corresponding functions of the first communication device (or the second communication device) are implemented. Optionally, when the chip implements the corresponding functions of the first communication device (or the second communication device) in the above embodiments, the input / output interface can implement the transmit / receive operations performed by the first communication device (or the second communication device) in the above embodiments; the processor can implement other operations performed by the first communication device (or the second communication device) in the above embodiments besides the transmit / receive operations. Specific details can be found in the relevant descriptions in the above embodiments, and will not be elaborated here. For example, taking the communication device as a first communication device (e.g., a first terminal device or a second terminal device) or a second communication device (e.g., a network device or a third terminal device), when the communication device is used to implement the technical solutions involved in the first communication device in the above embodiments, it can also achieve the beneficial effects of the first communication device in the above method embodiments; similarly, when the communication device is used to implement the technical solutions involved in the second communication device in the above embodiments, it can also achieve the beneficial effects of the second communication device in the above method embodiments.

[0199] See Figure 7The communication device 700 includes a transceiver 701 and a processor 702. Optionally, the communication device 700 also includes a memory 703. The transceiver 701, processor 702, and memory 703 are interconnected. When the communication device 700 is used to implement the technical solution of the first communication device provided in the above embodiments, the transceiver 701 can be used to implement the function of the communication module 601 when executing the technical solution of the first communication device, and the processor 702 is used to implement the function of the processing module 602 when executing the technical solution of the first communication device. When the communication device 700 is used to implement the technical solution of the second communication device provided in the above embodiments, the transceiver 701 can be used to implement the function of the communication module 601 when executing the technical solution of the second communication device, and the processor 702 is used to implement the function of the processing module 602 when executing the technical solution of the second communication device.

[0200] Optionally, the transceiver 701, processor 702, and memory 703 are interconnected via bus 704. Bus 704 can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The bus can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 7 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0201] Transceiver 701 is used to receive and send data. For example, when communication device 700 is as follows... Figure 1a When the terminal device 120i is as shown, the transceiver 701 realizes communication with, for example, the terminal device 120i. Figure 1a It can communicate with the RAN device 110a or terminal device 120j as shown, or it can also achieve communication with... Figure 1a This allows communication with devices outside the illustrated communication system architecture (such as in-vehicle equipment or servers). For example, when communication device 700 is as follows... Figure 1a When the terminal device 120f is as shown, the transceiver 701 realizes communication with such a terminal device 120f. Figure 1a It can communicate with the RAN device 110b, terminal device 120g, or terminal device 120h as shown, or it can also achieve communication with... Figure 1a This allows communication with devices outside the illustrated communication system architecture (such as vehicle-mounted equipment or servers). For example, when communication device 700 is as follows... Figure 1b When the terminal device 400 is as shown, the transceiver 701 realizes communication with such a terminal device 400. Figure 1bIt can communicate with the RAN device 600, terminal device 501, or terminal device 502 as shown, or it can also achieve communication with... Figure 1b This allows communication with devices outside the illustrated communication system architecture (such as in-vehicle equipment or servers). In one example, the transceiver can be a transceiver device with integrated data transmission and reception capabilities. In another example, the transceiver can also consist of a transmitter and a receiver, where the transmitter sends data and the receiver receives data.

[0202] Optionally, transceiver 701 may include a transmitter and / or a receiver. The transmitter is used to send signals, messages, information, or data, etc. The receiver is used to receive signals, messages, information, or data, etc. Exemplarily, the transmitter sends signals, messages, information, or data, etc., under the control of processor 702. The receiver receives signals, messages, information, or data, etc., under the control of processor 702.

[0203] The functions of processor 702 can be referred to the descriptions of the corresponding functions involved in the first or second communication device in the above embodiments, and will not be repeated here. Processor 702 can be a central processing unit (CPU), a network processor (NP), or a combination of CPU and NP, etc. Processor 702 may further include a hardware chip. The aforementioned hardware chip can be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof. The aforementioned PLD can be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), or any combination thereof. When implementing the above functions, processor 702 can be implemented through hardware, or it can be implemented by hardware executing corresponding software.

[0204] Memory 703 is used to store program instructions, etc. Specifically, program instructions may include program code, which includes computer operation instructions. Memory 703 may include random access memory (RAM) and may also include non-volatile memory, such as at least one disk storage device. Processor 702 executes the program instructions stored in memory 703 to implement the above-mentioned functions, thereby implementing the method steps required by the first communication device or the second communication device in the above embodiments.

[0205] Based on the same concept, embodiments of this application also provide a possible communication system, which includes a first communication device (such as a first terminal device or a second terminal device) and a second communication device (such as a network device or a third terminal device). The first communication device can be used to implement the technical solutions involved in the first communication device in the above embodiments, and the second communication device can be used to implement the technical solutions involved in the second communication device in the above embodiments.

[0206] Based on the same concept, this application also provides a computer program product, which includes a computer program or instructions that, when run on a computer, cause the computer to perform the methods provided in the above embodiments.

[0207] Based on the same concept, embodiments of this application also provide a computer-readable storage medium storing a computer program or instructions, which, when executed by a computer, causes the computer to perform the methods provided in the above embodiments.

[0208] The storage medium can be any available medium that a computer can access. For example, but not limited to, a computer-readable medium can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer.

[0209] Based on the same concept, this application also provides a computer program, which includes program code. When the computer runs the computer program, the program code executes the method provided in the above embodiments.

[0210] Based on the same concept, embodiments of this application also provide a chip, which may include a processor and may also include a memory (or the chip is coupled to the memory). The chip executes program instructions in the memory to perform the method in any possible design of the first aspect or the method in any possible design of the second aspect described above. Here, "coupling" refers to two components being directly or indirectly connected to each other, such as coupling referring to an electrical connection between two components.

[0211] Based on the same concept, embodiments of this application also provide a chip system, which includes a processor for supporting a computer device in implementing the functions involved in the first communication device (such as a first terminal device or a second terminal device) or the second communication device (such as a network device or a third terminal device) in the above embodiments. In one possible design, the chip system also includes a memory for storing necessary programs and data of the computer device. The chip system may be composed of chips or may include chips and other discrete components.

[0212] The methods provided in this application can be implemented entirely or partially through software, hardware, firmware, or any combination thereof. When implemented in software, they can be implemented entirely or partially in the form of a computer program product. This computer program product includes one or more computer instructions. When these computer instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., high-density digital video discs (DVDs)), or semiconductor media (e.g., solid-state drives (SSDs)).

[0213] The steps of the methods described in the embodiments of this application can be directly embedded in hardware, a software unit executed by a processor, or a combination of both. The software unit can be stored in RAM, ROM, EEPROM, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium in the art. Exemplarily, the storage medium can be connected to the processor so that the processor can read information from the storage medium and write information to the storage medium. Optionally, the storage medium can also be integrated into the processor. The processor and the storage medium can be housed in an ASIC.

[0214] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in one or more blocks of the flowchart illustrations and / or one or more blocks of the block diagrams.

[0215] These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process, such that the instructions, which execute on the computer or other programmable apparatus, provide steps for implementing the functions specified in one or more flowcharts and / or one or more block diagrams.

[0216] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the spirit and scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A communication method, characterized in that, Applied to a first terminal device, the method includes: A first configuration is obtained from a network device. The first configuration includes a first radio link control bearer configuration. The first radio link control bearer configuration is associated with a first carrier. The first radio link control bearer configuration is one of multiple radio link control bearer configurations corresponding to a packet data aggregation layer protocol entity configuration. The first radio link control bearer configuration is used to establish a first radio link control bearer entity. The first carrier is a carrier corresponding to a terminal device performing single-carrier communication. The radio link control bearer entities established by the multiple radio link control bearer configurations are used to transmit the same data. The data corresponding to the first radio link control bearer entity is multicast or broadcast on the first carrier.

2. The method as described in claim 1, characterized in that, The method further includes: The packet data convergence layer protocol entity configuration includes a packet data convergence layer protocol splitting configuration, which is used to instruct multiple data in the first terminal device to be transmitted through multiple radio link control bearer entities. The multiple data are transmitted through the first wireless link control bearer entity.

3. The method as described in claim 2, characterized in that, The first terminal device does not support sidelink carrier aggregation and / or the destination address does not support the sidelink carrier aggregation. The destination address is used to indicate the receiving terminal device for the first terminal device to perform sidelink communication.

4. The method as described in claim 2 or 3, characterized in that, The method further includes: Send a first message to the network device, the first message being used to instruct the first terminal device not to apply the packet data aggregation layer protocol split configuration.

5. The method as described in claim 1 or 2, characterized in that, The method further includes: Send a second message to the network device, the second message being used to indicate that the first terminal device supports sidelink carrier aggregation and / or to indicate that the destination address supports the sidelink carrier aggregation, the destination address being used to indicate the receiving terminal device for the first terminal device to perform sidelink communication.

6. The method as described in claim 5, characterized in that, Sending second information to the network device includes: When the first terminal device is in the radio resource control connection state, it sends a terminal device capability information message or a sidelink terminal device information message to the network device. The terminal device capability information message or the sidelink terminal device information message includes the second information. The sidelink terminal device information message is used to request the first configuration.

7. The method as described in claim 5 or 6, characterized in that, The method further includes: The third information is obtained from the upper layer of the first terminal device, and the third information is used to indicate that the destination address supports the sidelink carrier aggregation.

8. The method according to any one of claims 1-7, characterized in that, The association is determined by the network device, or the association is determined by the first terminal device.

9. A communication device, characterized in that, Includes modules or units for performing the method as described in any one of claims 1-8.

10. A communication device, characterized in that, include: A transceiver is used to receive and send data; Memory is used to store computer program instructions and data; A processor for executing computer program instructions and data that call the memory to cause the communication device to perform the method as described in any one of claims 1-8.

11. A communication system, characterized in that, Includes a first terminal device for performing the method as described in any one of claims 1-8.

12. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program or instructions that, when executed by a computer, cause the computer to perform the method as described in any one of claims 1-8.

13. A computer program product, characterized in that, The computer program product includes a computer program or instructions that, when run on a computer, cause the computer to perform the method as described in any one of claims 1-8.

14. A chip, characterized in that, The chip includes a processor for executing program instructions in a memory to perform the method as described in any one of claims 1-8.

Images