Communication method and device, communication equipment, communication system and storage medium

Abstract

The invention provides a communication method and device, equipment and a storage medium. The method comprises the steps that first equipment sends sidelink SL data associated with a first target address based on at least one of a mapping relation between the first target address and a carrier and a first attribute corresponding to the first target address; wherein the first attribute is used for indicating at least one of the following: a version number of the first target address, whether the first target address supports carrier aggregation, whether the first target address supports data distribution, and whether the first target address is backward compatible; wherein the first target address is a target address associated with the broadcast service and / or the multicast service, and the first target address is a target address which the first device is interested in sending and / or receiving. According to the method disclosed by the invention, backward compatibility of the receiving terminal of the first target address can be successfully realized, and the stability of SL communication is ensured.

Description

Communication method and device, communication equipment, communication system, and storage medium

[0001] The present disclosure relates to the field of communication technology, and in particular to communication methods and devices, communication equipment, communication systems, and storage media.

[0002] In the communication system, the uplink and downlink transmission rates are improved by introducing the carrier aggregation (CA) technology. Optionally, in the new version (such as R18 version), the SL carrier aggregation technology is also introduced in the sidelink (SL) communication.

[0003]

[0004] The present disclosure provides a communication method and apparatus, a communication device, a communication system, and a storage medium.

[0005] According to a first aspect of an embodiment of the present disclosure, a communication method is proposed, including:

[0006] The first device sends side link SL data associated with the first target address based on the mapping relationship between the first target address and the carrier and at least one of the first attributes corresponding to the first target address; wherein the first attribute corresponding to the first target address is used to indicate at least one of the following: the version number of the first target address, whether the first target address supports carrier aggregation, whether the first target address supports data offloading, and whether the first target address is backward compatible; wherein the first target address is a target address associated with a broadcast service and / or a multicast service, and the first target address is a target address that the first device is interested in sending and / or receiving.

[0007] According to a second aspect of an embodiment of the present disclosure, a communication method is proposed, including:

[0008] The second device receives SL data on one or more carriers based on the mapping relationship between the second target address and the carrier and at least one of the first attributes corresponding to the second target address; wherein the first attribute corresponding to the second target address is used to indicate at least one of the following: the version number of the second target address, whether the second target address supports carrier aggregation, whether the second target address supports data offloading, and whether the second target address is backward compatible; the second target address is a target address associated with a broadcast service and / or a multicast service, and the second target address is a target address that the second device is interested in sending and / or receiving.

[0009] According to a third aspect of an embodiment of the present disclosure, a communication method is provided for use in a communication system, wherein the communication system includes a first device and a second device, and the method includes at least one of the following:

[0010] The first device sends SL data associated with the first target address based on a mapping relationship between the first target address and the carrier and at least one of the first attributes corresponding to the first target address; wherein the first attribute corresponding to the first target address is used to indicate at least one of the following: a version number of the first target address, whether the first target address supports carrier aggregation, whether the first target address supports data offloading, and whether the first target address is backward compatible; wherein the first target address is a target address associated with a broadcast service and / or a multicast service, and the first target address is a target address that the first device is interested in sending and / or receiving;

[0011] The second device receives SL data on one or more carriers based on the mapping relationship between the second target address and the carrier and at least one of the first attributes corresponding to the second target address; wherein the first attribute corresponding to the second target address is used to indicate at least one of the following: the version number of the second target address, whether the second target address supports carrier aggregation, whether the second target address supports data offloading, and whether the second target address is backward compatible; the second target address is a target address associated with a broadcast service and / or a multicast service, the second target address is a target address that the second device is interested in sending and / or receiving, and the at least one second target address is part or all of the at least one first target address.

[0012] According to a fourth aspect of an embodiment of the present disclosure, a first device is provided, including:

[0013] A sending module, used to send SL data associated with the first target address based on the mapping relationship between the first target address and the carrier and at least one of the first attributes corresponding to the first target address; wherein the first attribute corresponding to the first target address is used to indicate at least one of the following: the version number of the first target address, whether the first target address supports carrier aggregation, whether the first target address supports data diversion, and whether the first target address is backward compatible; wherein the first target address is a target address associated with a broadcast service and / or a multicast service, and the first target address is a target address that the first device is interested in sending and / or receiving.

[0014] According to a fifth aspect of an embodiment of the present disclosure, a second device is provided, including:

[0015] A receiving module, used to receive SL data on one or more carriers based on the mapping relationship between the second target address and the carrier and at least one of the first attributes corresponding to the second target address; wherein the first attribute corresponding to the second target address is used to indicate at least one of the following: the version number of the second target address, whether the second target address supports carrier aggregation, whether the second target address supports data offloading, and whether the second target address is backward compatible; the second target address is a target address associated with a broadcast service and / or a multicast service, and the second target address is a target address that the second device is interested in sending and / or receiving.

[0016] According to a sixth aspect of an embodiment of the present disclosure, a communication device is provided, including:

[0017] One or more processors; wherein the processor is used to call instructions so that the communication device executes the communication method described in any one of the first aspect and the second aspect.

[0018] According to the seventh aspect of an embodiment of the present disclosure, a communication system is proposed, characterized in that it includes a first device and a second device, wherein the first device is configured to implement the communication method described in the first aspect, and the second device is configured to implement the communication method described in the second aspect.

[0019] According to an eighth aspect of an embodiment of the present disclosure, a storage medium is proposed, wherein the storage medium stores instructions, and is characterized in that when the instructions are executed on a communication device, the communication device executes the communication method as described in any one of the first aspect and the second aspect.

[0020] The above and / or additional aspects and advantages of the present disclosure will become apparent and easily understood from the following description of the embodiments in conjunction with the accompanying drawings, in which:

[0021] FIG1 is a schematic diagram of the architecture of some communication systems provided by embodiments of the present disclosure;

[0022] 2A-2D are interactive schematic diagrams of a communication method provided by an embodiment of the present disclosure;

[0023] 3A-3E are flowchart diagrams of a communication method provided in yet another embodiment of the present disclosure;

[0024] 4A-4C are flowchart diagrams of a communication method provided in yet another embodiment of the present disclosure;

[0025] FIG5 is a flow chart of a communication method provided by yet another embodiment of the present disclosure;

[0026] FIG6A is a schematic diagram of the structure of a first device provided by an embodiment of the present disclosure;

[0027] FIG6B is a schematic diagram of the structure of a second device provided by an embodiment of the present disclosure;

[0028] FIG7A is a schematic diagram of the structure of a communication device provided by an embodiment of the present disclosure;

[0029] FIG. 7B is a schematic diagram of the structure of a chip provided by an embodiment of the present disclosure.

[0030] The embodiments of the present disclosure provide a communication method and apparatus, a communication device, a communication system, and a storage medium.

[0031] In a first aspect, an embodiment of the present disclosure provides a communication method, which is performed by a first device, and the method includes:

[0032] The first device sends side link SL data associated with the first target address based on the mapping relationship between the first target address and the carrier and at least one of the first attributes corresponding to the first target address; wherein the first attribute corresponding to the first target address is used to indicate at least one of the following: the version number of the first target address, whether the first target address supports carrier aggregation, whether the first target address supports data offloading, and whether the first target address is backward compatible; wherein the first target address is a target address associated with a broadcast service and / or a multicast service, and the first target address is a target address that the first device is interested in sending and / or receiving.

[0033] In the above embodiment, when the first device sends the SL data associated with the first target address, it is based on at least one of the mapping relationship between the first target address and the carrier and the first attribute corresponding to the first target address. Among them, the first attribute corresponding to the first target address is used to indicate at least one of the following: the version number of the first target address, whether the first target address supports carrier aggregation, whether the first target address supports data diversion, and whether the first target address is backward compatible, that is, the first attribute corresponding to the first target address can reflect whether the first target address is backward compatible. It can be seen that in the embodiment of the present disclosure, when the first device sends the SL data associated with the first target address, it will send the SL data associated with the first target address from the two dimensions of "mapping relationship between target address and carrier" and "whether the first target address is backward compatible", so that it can be ensured that the first device finally sends the SL data associated with the first target address. The sending mode is matched with the receiving capability of the second device (i.e., the receiving terminal of the first target address). When the second device is a terminal with limited capability (such as: an old version terminal, for example: an R16 / 17 terminal), it can be ensured that the second device is successfully backward compatible, thereby ensuring the stability of SL communication.

[0034] In combination with some embodiments of the first aspect, in some embodiments, the method further includes:

[0035] The first device determines a first attribute corresponding to at least one first target address.

[0036] In combination with some embodiments of the first aspect, in some embodiments, the first attribute is configured according to a service granularity; wherein one first service corresponds to one first attribute, and the first target address is associated with at least one first service; the first service includes a broadcast service and / or a multicast service; or

[0037] The first attribute is configured according to the target address granularity; wherein the first target address corresponds to one first attribute.

[0038] In the above embodiment, a method for configuring a first attribute is provided, which is used to configure a first attribute corresponding to a first target address, so that the first device can subsequently successfully achieve backward compatibility with a second device based on the first attribute corresponding to the first target address, thereby ensuring the stability of SL communication.

[0039] In conjunction with some embodiments of the first aspect, in some embodiments, determining the first attribute corresponding to at least one first target address includes:

[0040] The first attribute is configured according to a service granularity, and the first attribute corresponding to the first target address is determined based on a first attribute corresponding to at least one first service associated with the first target address.

[0041] In combination with some embodiments of the first aspect, in some embodiments, determining the first attribute corresponding to the first target address based on the first attribute corresponding to at least one first service associated with the first target address includes:

[0042] The first attributes corresponding to all first services associated with the first target address indicate at least one of the following: the version number is the target version number, carrier aggregation is supported, data diversion is supported, and there is no backward compatibility. It is determined that the first attribute corresponding to the first target address is at least one of the following: the version number of the first target address is the target version number, the first target address supports carrier aggregation, the first target address supports data diversion, and the first target address is not backward compatible.

[0043] In the above embodiment, a method for determining a first attribute is provided, for determining the first attribute corresponding to the first target address, so that the first device can subsequently successfully achieve backward compatibility with the second device based on the first attribute corresponding to the first target address, thereby ensuring the stability of SL communication.

[0044] In combination with some embodiments of the first aspect, in some embodiments, the method further includes:

[0045] There is no corresponding first attribute for the first target address, and at least one of the following is determined: the version number of the first target address is not the target version number, the first target address does not support carrier aggregation, the first target address does not support data diversion, and the first target address is backward compatible.

[0046] In the above embodiment, a method is provided for determining whether the first target address is backward compatible when the first target address does not have a corresponding first attribute, so that the first device sends the SL data associated with the first target address based on whether the first target address is backward compatible. This ensures that the first device ultimately sends the SL data associated with the first target address in a manner that matches the receiving capability of the second device (i.e., the receiving terminal of the first target address). When the second device is a terminal with limited capabilities (such as an old version terminal, for example, an R16 / 17 terminal), it ensures that backward compatibility is successfully achieved with the second device, thereby ensuring the stability of SL communication.

[0047] In combination with some embodiments of the first aspect, in some embodiments, the sending the SL data associated with the first target address based on at least one of a mapping relationship between the first target address and the carrier and a first attribute corresponding to the first target address includes:

[0048] The mapping relationship between the first target address and the carrier is: the first target address is mapped to multiple carriers; and / or the first attribute corresponding to the first target address indicates at least one of the following: the version number of the first target address is the target version number, the first target address supports carrier aggregation, the first target address supports data diversion, and the first target address is not backward compatible; the SL data associated with the first target address is sent through multi-carrier diversion and / or packet data convergence protocol PDCP duplication.

[0049] In combination with some embodiments of the first aspect, in some embodiments, the sending the SL data associated with the first target address based on at least one of a mapping relationship between the first target address and the carrier and a first attribute corresponding to the first target address includes:

[0050] The mapping relationship between the first target address and the carrier is: the first target address is mapped to multiple carriers; and / or the first attribute corresponding to the first target address indicates at least one of the following: the version number of the first target address is not the target version number, the first target address does not support carrier aggregation, the first target address does not support data offloading, and the first target address is backward compatible; the SL data associated with the first target address is sent via a single carrier and / or PDCP multiplexing.

[0051] In combination with some embodiments of the first aspect, in some embodiments, the sending the SL data associated with the first target address based on at least one of a mapping relationship between the first target address and the carrier and a first attribute corresponding to the first target address includes:

[0052] The mapping relationship between the first target address and the carrier is: the first target address is mapped to one carrier; and / or the first attribute corresponding to the first target address indicates at least one of the following: the version number of the first target address is the target version number, the first target address supports carrier aggregation, the first target address supports data diversion, and the first target address is not backward compatible; the SL data associated with the first target address is sent via a single carrier.

[0053] In combination with some embodiments of the first aspect, in some embodiments, the sending the SL data associated with the first target address based on at least one of a mapping relationship between the first target address and the carrier and a first attribute corresponding to the first target address includes:

[0054] The mapping relationship between the first target address and the carrier is: the first target address is mapped to one carrier; and / or the first attribute corresponding to the first target address indicates at least one of the following: the version number of the first target address is not the target version number, the first target address does not support carrier aggregation, the first target address does not support data diversion, and the first target address is backward compatible; the SL data associated with the first target address is sent via a single carrier.

[0055] In the above embodiment, a method is provided for how the first device specifically sends the SL data associated with the first target address based on the mapping relationship between the first target address and the carrier and / or the first attribute corresponding to the first target address, so that the sending method when the first device finally sends the SL data associated with the first target address is matched with the receiving capability of the second device (i.e., the receiving terminal of the first target address). In this case, when the second device is a terminal with limited capabilities (such as an old version terminal, for example, an R16 / 17 terminal), backward compatibility with the second device can be successfully achieved, thereby ensuring the stability of SL communication.

[0056] In combination with some embodiments of the first aspect, in some embodiments, sending the SL data associated with the first target address through PDCP multiplexing includes:

[0057] The SL data associated with the first SLRB is sent through PDCP multiplexing; wherein the first SLRB is an SLRB associated with the first target address and with PDCP multiplexing activated, and the first SLRB is one or more.

[0058] In combination with some embodiments of the first aspect, in some embodiments, sending the SL data associated with the first SLRB through PDCP multiplexing includes:

[0059] Select two carriers from among the multiple carriers mapped to the first target address to respectively send the same SL data associated with the first SLRB.

[0060] In combination with some embodiments of the first aspect, in some embodiments, the selecting two carriers from the multiple carriers mapped to the first target address to respectively send the same SL data associated with the first SLRB includes:

[0061] Randomly select two carriers from the multiple carriers mapped to the first target address to respectively send the same SL data associated with the first SLRB.

[0062] In combination with some embodiments of the first aspect, in some embodiments, sending the SL data associated with the first target address through multi-carrier offloading includes:

[0063] The SL data associated with the second SLRB is sent through the multiple carriers mapped to the first target address; wherein the second SLRB is the SLRB associated with the first target address and deactivated PDCP multiplexing, and the second SLRB is one or more.

[0064] In combination with some embodiments of the first aspect, in some embodiments, sending SL data associated with the second SLRB through multi-carrier splitting includes:

[0065] Different SL data associated with the second SLRB are sent on multiple carriers mapped to the first target address.

[0066] In combination with some embodiments of the first aspect, in some embodiments, sending the SL data associated with the first target address through PDCP multiplexing includes:

[0067] The SL data associated with the first SLRB is sent through PDCP multiplexing; wherein the first SLRB is an SLRB associated with the first target address and with PDCP multiplexing activated, and the first SLRB is one or more.

[0068] In combination with some embodiments of the first aspect, in some embodiments, sending the SL data associated with the first SLRB through PDCP multiplexing includes:

[0069] Select two carriers from among the multiple carriers mapped to the first target address to respectively send the same SL data associated with the first SLRB.

[0070] In combination with some embodiments of the first aspect, in some embodiments, the selecting two carriers from the multiple carriers mapped to the first target address to respectively send the same SL data associated with the first SLRB includes:

[0071] An existing carrier that can achieve backward compatibility and any other carrier are selected from multiple carriers mapped to the first target address to respectively send the same SL data associated with the first SLRB.

[0072] In combination with some embodiments of the first aspect, in some embodiments, sending the SL data associated with the first target address through a single carrier includes:

[0073] The SL data associated with the second SLRB is sent via an existing carrier that can achieve backward compatibility; wherein the second SLRB is an SLRB associated with the first target address and with PDCP multiplexing deactivated, and the second SLRB is one or more.

[0074] In combination with some embodiments of the first aspect, in some embodiments, sending the SL data associated with the first target address through a single carrier includes:

[0075] The SL data associated with the first target address is sent via an existing carrier that can achieve backward compatibility.

[0076] In the above embodiment, a method is provided for how the first device specifically sends SL data, which is used for the first device to successfully send SL data to the second device, thereby ensuring the successful transmission of SL data and ensuring the stability of SL transmission. In addition, in some embodiments, when certain SLRBs (such as the first SLRB mentioned above) activate PDCP multiplexing, the first device will also send the SL data associated with the SLRB through PDCP multiplexing, thereby improving the reliability of SL data, reducing the delay of repeated transmission, and meeting the requirements of Ultra Reliable and Low Latency Communication (URLLC).

[0077] In combination with some embodiments of the first aspect, in some embodiments, the method further includes:

[0078] Determine the SLRB configurations respectively corresponding to at least one first SLRB and / or at least one second SLRB, where the SLRB configurations respectively corresponding to the at least one first SLRB and / or at least one second SLRB are used to configure whether to activate PDCP multiplexing for the at least one first SLRB and / or at least one second SLRB;

[0079] Determine whether PDCP multiplexing is activated for the at least one first SLRB and / or the at least one second SLRB associated with the first target address according to the SLRB configurations respectively corresponding to the at least one first SLRB and / or the at least one second SLRB.

[0080] In combination with some embodiments of the first aspect, in some embodiments, determining the SLRB configurations corresponding to at least one first SLRB and / or at least one second SLRB respectively includes at least one of the following:

[0081] Obtaining SLRB configurations respectively corresponding to the at least one first SLRB and / or the at least one second SLRB sent through dedicated signaling;

[0082] Obtaining SLRB configurations respectively corresponding to the at least one first SLRB and / or the at least one second SLRB sent through a system information block SIB;

[0083] Obtain the SLRB configurations corresponding to the at least one first SLRB and / or at least one second SLRB pre-configured respectively.

[0084] In the above embodiment, a method is provided for a first device to determine which SLRB configurations activate PDCP multiplexing, which is used for the first device to determine the above-mentioned first SLRB and second SLRB, and adopt corresponding sending methods to respectively send the SL data associated with the first SLRB and the SL data associated with the second SLRB, thereby ensuring the successful transmission of the SL data and ensuring the stability of the SL transmission.

[0085] In combination with some embodiments of the first aspect, in some embodiments, the method further includes:

[0086] A mapping relationship between the first target address and the carrier is determined based on a high-level configuration.

[0087] In the above embodiment, a method is provided for how a first device determines a mapping relationship between a first target address and a carrier, and is used for the first device to successfully determine the mapping relationship between the first target address and the carrier. Then, when the first device subsequently sends SL data associated with the first target address, the SL data associated with the first target address can be sent based on the determined mapping relationship between the first target address and the carrier in combination with the first attribute corresponding to the first target address, so as to ensure that the sending method of the SL data associated with the first target address finally sent by the first device matches the receiving capability of the second device (i.e., the receiving terminal of the first target address). Then, when the second device is a terminal with limited capability (such as a terminal that does not support carrier aggregation in the old version, for example, an R16 / 17 terminal), backward compatibility with the second device can be ensured to be successfully achieved, thereby ensuring the stability of SL communication.

[0088] In combination with some embodiments of the first aspect, in some embodiments, for a first target address, the first device and the second device are configured with the same first attribute; wherein the first device is a sending terminal of the first target address, and the second device is a receiving terminal of the first target address.

[0089] In the above embodiment, the first device (i.e., the sending terminal of the first target address) and the second device (i.e., the receiving terminal of the first target address) will configure the same first attribute for the first target address, thereby unifying the understanding of the first attribute of the first target address by the first device and the second device, thereby ensuring that the SL data associated with the first target address can be successfully transmitted between the first device and the second device based on the unified understanding of the first attribute of the first target address, thereby ensuring the stability of SL communication.

[0090] In combination with some embodiments of the first aspect, in some embodiments, the target version number is R18.

[0091] In a second aspect, an embodiment of the present disclosure provides a communication method, which is performed by a second device and includes:

[0092] The second device receives SL data on one or more carriers based on the mapping relationship between the second target address and the carrier and at least one of the first attributes corresponding to the second target address; wherein the first attribute corresponding to the second target address is used to indicate at least one of the following: the version number of the second target address, whether the second target address supports carrier aggregation, whether the second target address supports data offloading, and whether the second target address is backward compatible; the second target address is a target address associated with a broadcast service and / or a multicast service, and the second target address is a target address that the second device is interested in sending and / or receiving.

[0093] In the above embodiment, when the second device receives the SL data associated with the second target address, it is based on the mapping relationship between the second target address and the carrier, and at least one of the first attributes corresponding to the second target address. Among them, the first attribute corresponding to the second target address is used to indicate at least one of the following: the version number of the second target address, whether the second target address supports carrier aggregation, whether the second target address supports data diversion, and whether the second target address is backward compatible, that is, the first attribute corresponding to the second target address can reflect whether the second target address is backward compatible. It can be seen that in the embodiment of the present disclosure, when the second device receives the SL data associated with the second target address, it will receive the SL data associated with the second target address from the two dimensions of "mapping relationship between target address and carrier" and "whether the second target address is backward compatible", so that it can be ensured that the receiving mode when the second device finally receives the SL data associated with the second target address is matched with the receiving capability of the second device, then when the second device is a terminal with limited capability (such as: old version terminal, for example: R16 / 17 terminal), it can be ensured that the second device is successfully backward compatible, thereby ensuring the stability of SL communication.

[0094] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes:

[0095] The second device determines a first attribute corresponding to at least one second target address.

[0096] In combination with some embodiments of the second aspect, in some embodiments, the first attribute is configured according to the service granularity; wherein one second service corresponds to one first attribute, and the second target address is associated with at least one second service; the second service includes a broadcast service and / or a multicast service; or

[0097] The first attribute is configured according to the target address granularity; wherein the second target address corresponds to one first attribute.

[0098] In conjunction with some embodiments of the second aspect, in some embodiments, determining the first attribute corresponding to at least one second target address includes:

[0099] The first attribute is configured according to a service granularity, and the first attribute corresponding to the second target address is determined based on a first attribute corresponding to at least one second service associated with the second target address.

[0100] In combination with some embodiments of the second aspect, in some embodiments, determining the first attribute corresponding to the second target address based on the first attribute corresponding to at least one second service associated with the second target address includes:

[0101] The first attributes corresponding to all second services associated with the second target address indicate at least one of the following: the version number is the target version number, carrier aggregation is supported, data offloading is supported, and there is no backward compatibility. It is determined that the first attribute corresponding to the second target address is at least one of the following: the version number of the second target address is the target version number, the second target address supports carrier aggregation, the second target address supports data offloading, and the second target address is not backward compatible.

[0102] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes:

[0103] There is no corresponding first attribute for the second target address, and at least one of the following is determined: the version number of the second target address is not the target version number, the second target address does not support carrier aggregation, the second target address does not support data diversion, and the second target address is backward compatible.

[0104] In combination with some embodiments of the second aspect, in some embodiments, the receiving SL data on one or more carriers based on at least one of the mapping relationship between the second target address and the carrier and the first attribute corresponding to the second target address includes:

[0105] At least one second target address satisfies a first preset condition, and SL data associated with the at least one second target address is received through multiple carriers; wherein the first preset condition includes: a mapping relationship between the second target address and the carrier is: the second target address is mapped to multiple carriers; and / or, a first attribute corresponding to the second target address indicates at least one of the following: the version number of the second target address is the target version number, the second target address supports carrier aggregation, the second target address supports data diversion, and the second target address is not backward compatible.

[0106] In combination with some embodiments of the second aspect, in some embodiments, the receiving SL data on one or more carriers based on at least one of the mapping relationship between the second target address and the carrier and the first attribute corresponding to the second target address includes:

[0107] All second target addresses meet the second preset condition, and the SL data associated with at least one second target address is received through an existing carrier that can achieve backward compatibility; wherein, the second preset condition includes: the mapping relationship between the second target address and the carrier is: the second target address is mapped to one carrier; and / or, the first attribute corresponding to the second target address indicates at least one of the following: the version number of the second target address is not the target version number, the second target address does not support carrier aggregation, the second target address does not support data diversion, and the second target address is backward compatible; and / or, the second preset condition includes: the mapping relationship between the second target address and the carrier is: the second target address is mapped to multiple carriers; and / or, the first attribute corresponding to the second target address indicates at least one of the following: the version number of the second target address is not the target version number, the second target address does not support carrier aggregation, the second target address does not support data diversion, and the second target address is backward compatible.

[0108] In combination with some embodiments of the second aspect, in some embodiments, for the second target address, the first device and the second device are configured with the same first attribute; wherein the first device is a sending terminal of the second target address, and the second device is a receiving terminal of the second target address.

[0109] In a third aspect, an embodiment of the present disclosure provides a communication method for a communication system, wherein the communication system includes a first device and a second device, and the method includes at least one of the following:

[0110] The first device sends the SL data associated with the first target address based on the mapping relationship between the first target address and the carrier and at least one of the first attributes corresponding to the first target address; wherein the first attribute corresponding to the first target address is used to indicate at least one of the following: the version number of the first target address, whether the first target address supports carrier aggregation, whether the first target address supports data offloading, and whether the first target address is backward compatible; wherein the first target address is a target address associated with a broadcast service and / or a multicast service, and the first target address is a target address that the first device is interested in sending and / or receiving;

[0111] The second device receives SL data on one or more carriers based on the mapping relationship between the second target address and the carrier and at least one of the first attributes corresponding to the second target address; wherein the first attribute corresponding to the second target address is used to indicate at least one of the following: the version number of the second target address, whether the second target address supports carrier aggregation, whether the second target address supports data offloading, and whether the second target address is backward compatible; the second target address is a target address associated with a broadcast service and / or a multicast service, the second target address is a target address that the second device is interested in sending and / or receiving, and the at least one second target address is part or all of the at least one first target address.

[0112] In a fourth aspect, an embodiment of the present disclosure provides a first device, including:

[0113] A sending module, used to send SL data associated with the first target address based on the mapping relationship between the first target address and the carrier and at least one of the first attributes corresponding to the first target address; wherein the first attribute corresponding to the first target address is used to indicate at least one of the following: the version number of the first target address, whether the first target address supports carrier aggregation, whether the first target address supports data diversion, and whether the first target address is backward compatible; wherein the first target address is a target address associated with a broadcast service and / or a multicast service, and the first target address is a target address that the first device is interested in sending and / or receiving.

[0114] In conjunction with some embodiments of the fourth aspect, in some embodiments, the first device is further used for:

[0115] A first attribute corresponding to at least one first target address is determined.

[0116] In combination with some embodiments of the fourth aspect, in some embodiments, the first attribute is configured according to the service granularity; wherein one first service corresponds to one first attribute, and the first target address is associated with at least one first service; the first service includes a broadcast service and / or a multicast service; or

[0117] The first attribute is configured according to the target address granularity; wherein the first target address corresponds to one first attribute.

[0118] In conjunction with some embodiments of the fourth aspect, in some embodiments, the first device is further used for:

[0119] The first attribute is configured according to a service granularity, and the first attribute corresponding to the first target address is determined based on a first attribute corresponding to at least one first service associated with the first target address.

[0120] In conjunction with some embodiments of the fourth aspect, in some embodiments, the first device is further used for:

[0121] The first attributes corresponding to all first services associated with the first target address indicate at least one of the following: the version number is the target version number, carrier aggregation is supported, data diversion is supported, and there is no backward compatibility. It is determined that the first attribute corresponding to the first target address is at least one of the following: the version number of the first target address is the target version number, the first target address supports carrier aggregation, the first target address supports data diversion, and the first target address is not backward compatible.

[0122] In conjunction with some embodiments of the fourth aspect, in some embodiments, the first device is further used for:

[0123] There is no corresponding first attribute for the first target address, and at least one of the following is determined: the version number of the first target address is not the target version number, the first target address does not support carrier aggregation, the first target address does not support data diversion, and the first target address is backward compatible.

[0124] In conjunction with some embodiments of the fourth aspect, in some embodiments, the sending module is further used to:

[0125] The mapping relationship between the first target address and the carrier is: the first target address is mapped to multiple carriers; and / or the first attribute corresponding to the first target address indicates at least one of the following: the version number of the first target address is the target version number, the first target address supports carrier aggregation, the first target address supports data diversion, and the first target address is not backward compatible; the SL data associated with the first target address is sent through multi-carrier diversion and / or packet data convergence protocol PDCP duplication.

[0126] In conjunction with some embodiments of the fourth aspect, in some embodiments, the sending module is further used to:

[0127] The mapping relationship between the first target address and the carrier is: the first target address is mapped to multiple carriers; and / or the first attribute corresponding to the first target address indicates at least one of the following: the version number of the first target address is not the target version number, the first target address does not support carrier aggregation, the first target address does not support data offloading, and the first target address is backward compatible; the SL data associated with the first target address is sent via a single carrier and / or PDCP multiplexing.

[0128] In conjunction with some embodiments of the fourth aspect, in some embodiments, the sending module is further used to:

[0129] The mapping relationship between the first target address and the carrier is: the first target address is mapped to one carrier; and / or the first attribute corresponding to the first target address indicates at least one of the following: the version number of the first target address is the target version number, the first target address supports carrier aggregation, the first target address supports data diversion, and the first target address is not backward compatible; the SL data associated with the first target address is sent via a single carrier.

[0130] In conjunction with some embodiments of the fourth aspect, in some embodiments, the sending module is further used to:

[0131] The mapping relationship between the first target address and the carrier is: the first target address is mapped to one carrier; and / or the first attribute corresponding to the first target address indicates at least one of the following: the version number of the first target address is not the target version number, the first target address does not support carrier aggregation, the first target address does not support data diversion, and the first target address is backward compatible; the SL data associated with the first target address is sent via a single carrier.

[0132] In conjunction with some embodiments of the fourth aspect, in some embodiments, the sending module is further used to:

[0133] The SL data associated with the first SLRB is sent through PDCP multiplexing; wherein the first SLRB is an SLRB associated with the first target address and with PDCP multiplexing activated, and the first SLRB is one or more.

[0134] In conjunction with some embodiments of the fourth aspect, in some embodiments, the sending module is further used to:

[0135] Select two carriers from among the multiple carriers mapped to the first target address to respectively send the same SL data associated with the first SLRB.

[0136] In conjunction with some embodiments of the fourth aspect, in some embodiments, the sending module is further used to:

[0137] Randomly select two carriers from the multiple carriers mapped to the first target address to respectively send the same SL data associated with the first SLRB.

[0138] In conjunction with some embodiments of the fourth aspect, in some embodiments, the sending module is further used to:

[0139] The SL data associated with the second SLRB is sent through the multiple carriers mapped to the first target address; wherein the second SLRB is the SLRB associated with the first target address and deactivated PDCP multiplexing, and the second SLRB is one or more.

[0140] In conjunction with some embodiments of the fourth aspect, in some embodiments, the sending module is further used to:

[0141] Different SL data associated with the second SLRB are sent on multiple carriers mapped to the first target address.

[0142] In conjunction with some embodiments of the fourth aspect, in some embodiments, the sending module is further used to:

[0143] The SL data associated with the first SLRB is sent through PDCP multiplexing; wherein the first SLRB is an SLRB associated with the first target address and with PDCP multiplexing activated, and the first SLRB is one or more.

[0144] In conjunction with some embodiments of the fourth aspect, in some embodiments, the sending module is further used to:

[0145] Select two carriers from among the multiple carriers mapped to the first target address to respectively send the same SL data associated with the first SLRB.

[0146] In conjunction with some embodiments of the fourth aspect, in some embodiments, the sending module is further used to:

[0147] An existing carrier that can achieve backward compatibility and any other carrier are selected from multiple carriers mapped to the first target address to respectively send the same SL data associated with the first SLRB.

[0148] In conjunction with some embodiments of the fourth aspect, in some embodiments, the sending module is further used to:

[0149] The SL data associated with the second SLRB is sent via an existing carrier that can achieve backward compatibility; wherein the second SLRB is an SLRB associated with the first target address and with PDCP multiplexing deactivated, and the second SLRB is one or more.

[0150] In conjunction with some embodiments of the fourth aspect, in some embodiments, the sending module is further used to:

[0151] The SL data associated with the first target address is sent via an existing carrier that can achieve backward compatibility.

[0152] In conjunction with some embodiments of the fourth aspect, in some embodiments, the device is further used for:

[0153] Determine the SLRB configurations respectively corresponding to at least one first SLRB and / or at least one second SLRB, where the SLRB configurations respectively corresponding to the at least one first SLRB and / or at least one second SLRB are used to configure whether to activate PDCP multiplexing for the at least one first SLRB and / or at least one second SLRB;

[0154] Determine whether PDCP multiplexing is activated for the at least one first SLRB and / or the at least one second SLRB associated with the first target address according to the SLRB configurations respectively corresponding to the at least one first SLRB and / or the at least one second SLRB.

[0155] In conjunction with some embodiments of the fourth aspect, in some embodiments, the device is further used for:

[0156] Obtaining SLRB configurations respectively corresponding to the at least one first SLRB and / or the at least one second SLRB sent through dedicated signaling;

[0157] Obtaining SLRB configurations respectively corresponding to the at least one first SLRB and / or the at least one second SLRB sent through a system information block SIB;

[0158] Obtain the SLRB configurations corresponding to the at least one first SLRB and / or at least one second SLRB pre-configured respectively.

[0159] In conjunction with some embodiments of the fourth aspect, in some embodiments, the device is further used for:

[0160] A mapping relationship between the first target address and the carrier is determined based on a high-level configuration.

[0161] In combination with some embodiments of the fourth aspect, in some embodiments, for the first target address, the first device and the second device are configured with the same first attribute; wherein the first device is a sending terminal of the first target address, and the second device is a receiving terminal of the first target address.

[0162] In combination with some embodiments of the fourth aspect, in some embodiments, the target version number is R18.

[0163] In a fifth aspect, the present disclosure provides a second device, including:

[0164] A receiving module, used to receive SL data on one or more carriers based on the mapping relationship between the second target address and the carrier and at least one of the first attributes corresponding to the second target address; wherein the first attribute corresponding to the second target address is used to indicate at least one of the following: the version number of the second target address, whether the second target address supports carrier aggregation, whether the second target address supports data offloading, and whether the second target address is backward compatible; the second target address is a target address associated with a broadcast service and / or a multicast service, and the second target address is a target address that the second device is interested in sending and / or receiving.

[0165] In conjunction with some embodiments of the fifth aspect, in some embodiments, the second device is further used for:

[0166] A first attribute corresponding to each of the at least one second target address is determined.

[0167] In combination with some embodiments of the fifth aspect, in some embodiments, the first attribute is configured according to the service granularity; wherein one second service corresponds to one first attribute, and the second target address is associated with at least one second service; the second service includes a broadcast service and / or a multicast service; or

[0168] The first attribute is configured according to the target address granularity; wherein the second target address corresponds to one first attribute.

[0169] In conjunction with some embodiments of the fifth aspect, in some embodiments, the second device is further used for:

[0170] The first attribute is configured according to a service granularity, and the first attribute corresponding to the second target address is determined based on a first attribute corresponding to at least one second service associated with the second target address.

[0171] In conjunction with some embodiments of the fifth aspect, in some embodiments, the second device is further used for:

[0172] The first attributes corresponding to all second services associated with the second target address indicate at least one of the following: the version number is the target version number, carrier aggregation is supported, data offloading is supported, and there is no backward compatibility. It is determined that the first attribute corresponding to the second target address is at least one of the following: the version number of the second target address is the target version number, the second target address supports carrier aggregation, the second target address supports data offloading, and the second target address is not backward compatible.

[0173] In conjunction with some embodiments of the fifth aspect, in some embodiments, the second device is further used for:

[0174] There is no corresponding first attribute for the second target address, and at least one of the following is determined: the version number of the second target address is not the target version number, the second target address does not support carrier aggregation, the second target address does not support data diversion, and the second target address is backward compatible.

[0175] In conjunction with some embodiments of the fifth aspect, in some embodiments, the receiving module is further used for:

[0176] At least one second target address satisfies a first preset condition, and SL data associated with the at least one second target address is received through multiple carriers; wherein the first preset condition includes: a mapping relationship between the second target address and the carrier is: the second target address is mapped to multiple carriers; and / or, a first attribute corresponding to the second target address indicates at least one of the following: the version number of the second target address is the target version number, the second target address supports carrier aggregation, the second target address supports data diversion, and the second target address is not backward compatible.

[0177] In conjunction with some embodiments of the fifth aspect, in some embodiments, the receiving module is further used for:

[0178] All second target addresses meet the second preset condition, and the SL data associated with at least one second target address is received through an existing carrier that can achieve backward compatibility; wherein, the second preset condition includes: the mapping relationship between the second target address and the carrier is: the second target address is mapped to one carrier; and / or, the first attribute corresponding to the second target address indicates at least one of the following: the version number of the second target address is not the target version number, the second target address does not support carrier aggregation, the second target address does not support data diversion, and the second target address is backward compatible; and / or, the second preset condition includes: the mapping relationship between the second target address and the carrier is: the second target address is mapped to multiple carriers; and / or, the first attribute corresponding to the second target address indicates at least one of the following: the version number of the second target address is not the target version number, the second target address does not support carrier aggregation, the second target address does not support data diversion, and the second target address is backward compatible.

[0179] In combination with some embodiments of the fifth aspect, in some embodiments, for the second target address, the first device and the second device are configured with the same first attribute; wherein the first device is a sending terminal of the second target address, and the second device is a receiving terminal of the second target address.

[0180] In a sixth aspect, an embodiment of the present disclosure proposes a communication device, wherein the communication device includes: one or more processors; one or more memories for storing instructions; wherein the processor is used to call the instructions so that the communication device executes the communication method described in the first and second aspects, and the optional implementation methods of the first and second aspects.

[0181] In the seventh aspect, an embodiment of the present disclosure proposes a communication system, which includes: a first device and a second device; wherein the first device is configured to execute the method described in the first aspect and the optional implementation of the first aspect, and the second device is configured to execute the method described in the second aspect and the optional implementation of the second aspect.

[0182] In an eighth aspect, an embodiment of the present disclosure proposes a storage medium, wherein the storage medium stores instructions. When the instructions are executed on a communication device, the communication device executes the method described in the first aspect, the optional implementation of the first aspect, the second aspect, and the optional implementation of the second aspect.

[0183] In a ninth aspect, an embodiment of the present disclosure proposes a program product. When the program product is executed by a communication device, the communication device executes the method described in the first aspect, the optional implementation of the first aspect, the second aspect, and the optional implementation of the second aspect.

[0184] In a tenth aspect, an embodiment of the present disclosure proposes a computer program, which, when executed on a computer, enables the computer to execute the method described in the first aspect, the optional implementation of the first aspect, the second aspect, and the optional implementation of the second aspect.

[0185] It is understandable that the first device, the second device, the communication device, the communication system, the storage medium, the program product, and the computer program are all used to execute the method proposed in the embodiment of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding method, which will not be repeated here.

[0186] The present disclosure proposes the title of the invention. In some embodiments, the terms such as communication method and information processing method, information sending method, information receiving method, etc. can be replaced with each other, the terms such as communication device and information processing device, information sending device, information receiving device, etc. can be replaced with each other, and the terms such as information processing system, communication system, information sending system, information receiving system, etc. can be replaced with each other.

[0187] The embodiments of the present disclosure are not exhaustive, but are only illustrative of some embodiments, and are not intended to be a specific limitation on the scope of protection of the present disclosure. In the absence of contradiction, each step in a certain embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a certain embodiment can also be implemented as an independent embodiment, and the order of the steps in a certain embodiment can be arbitrarily exchanged. In addition, the optional implementation methods in a certain embodiment can be arbitrarily combined; in addition, the embodiments can be arbitrarily combined, for example, some or all of the steps of different embodiments can be arbitrarily combined, and a certain embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0188] In each embodiment of the present disclosure, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between the embodiments are consistent and can be referenced to each other, and the technical features in different embodiments can be combined to form a new embodiment based on their internal logical relationships.

[0189] The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments and are not intended to limit the present disclosure.

[0190] In the embodiments of the present disclosure, unless otherwise specified, elements expressed in the singular form, such as "a", "an", "the", "above", "said", "aforementioned", "this", etc., may mean "one and only one", or "one or more", "at least one", etc. For example, when using articles such as "a", "an", "the" in English in translation, the noun after the article may be understood as a singular expression or a plural expression.

[0191] In the embodiments of the present disclosure, “plurality” refers to two or more.

[0192] In some embodiments, the terms “at least one of,” “at least one of,” “at least one of,” “one or more,” “a plurality of,” “multiple,” etc. may be used interchangeably.

[0193] In the embodiments of the present disclosure, descriptions such as “at least one of A, B, C…”, “A and / or B and / or C…”, etc. include the situation where any one of A, B, C… exists alone, and also include the situation where any multiple of A, B, C… exist in any combination, and each situation can exist alone; for example, “at least one of A, B, C” includes the situation where A exists alone, B exists alone, C exists alone, the combination of A and B, the combination of A and C, the combination of B and C, and the combination of A, B and C; for example, A and / or B includes the situation where A exists alone, B exists alone, and the combination of A and B.

[0194] In some embodiments, the description methods such as "in one case A, in another case B", "in response to one case A, in response to another case B", etc. may include the following technical solutions according to the situation: A is executed independently of B, that is, in some embodiments A; B is executed independently of A, that is, in some embodiments B; A and B are selectively executed, that is, selected from A and B in some embodiments; A and B are both executed, that is, A and B in some embodiments. When there are more branches such as A, B, C, etc., it is similar to the above.

[0195] The prefixes such as "first" and "second" in the embodiments of the present disclosure are only used to distinguish different description objects, and do not constitute restrictions on the position, order, priority, quantity or content of the description objects. The statement of the description object refers to the description in the context of the claims or embodiments, and should not constitute unnecessary restrictions due to the use of prefixes. For example, if the description object is a "field", the ordinal number before the "field" in the "first field" and the "second field" does not limit the position or order between the "fields", and the "first" and "second" do not limit whether the "fields" they modify are in the same message, nor do they limit the order of the "first field" and the "second field". For another example, if the description object is a "level", the ordinal number before the "level" in the "first level" and the "second level" does not limit the priority between the "levels". For another example, the number of description objects is not limited by the ordinal number, and can be one or more. Taking the "first device" as an example, the number of "devices" can be one or more. In addition, the objects modified by different prefixes may be the same or different. For example, if the description object is "device", then the "first device" and the "second device" may be the same device or different devices, and their types may be the same or different. For another example, if the description object is "information", then the "first information" and the "second information" may be the same information or different information, and their contents may be the same or different.

[0196] In some embodiments, “including A”, “comprising A”, “used to indicate A”, and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0197] In some embodiments, terms such as "in response to ...", "in response to determining ...", "in the case of ...", "at the time of ...", "when ...", "if ...", "if ...", etc. can be used interchangeably.

[0198] In some embodiments, terms such as "greater than", "greater than or equal to", "not less than", "more than", "more than or equal to", "not less than", "higher than", "higher than or equal to", "not lower than", and "above" can be replaced with each other, and terms such as "less than", "less than or equal to", "not greater than", "less than", "less than or equal to", "no more than", "lower than", "lower than or equal to", "not higher than", and "below" can be replaced with each other.

[0199] In some embodiments, devices, etc. can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. Terms such as "device", "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", and "subject" can be used interchangeably.

[0200] In some embodiments, "network" may be interpreted as devices included in the network (eg, access network equipment, core network equipment, etc.).

[0201] In some embodiments, the terms "access network device (AN device)", "radio access network device (RAN device)", "base station (BS)", "radio base station (radio base station)", "fixed station (fixed station)", "node (node)", "access point (access point)", "transmission point (TP)", "reception point (reception point, RP)", "transmission / reception point (transmission / reception point, TRP)", "panel (panel)", "antenna panel (antenna panel)", "antenna array (antenna array)", "cell (cell)", "macro cell (macro cell)", "small cell (small cell)", "femto cell (femto cell)", "pico cell (pico cell)", "sector (sector)", "cell group (cell)", "carrier (carrier)", "component carrier (component carrier)", "bandwidth part (bandwidth part, BWP)" and the like can be used interchangeably.

[0202] In some embodiments, the terms "terminal", "terminal device", "user equipment (UE)", "user terminal" "mobile station (MS)", "mobile terminal (MT)", subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client and the like may be used interchangeably.

[0203] In some embodiments, the access network device, the core network device, or the network device can be replaced by a terminal. For example, the various embodiments of the present disclosure can also be applied to a structure in which the access network device, the core network device, or the network device and the communication between the terminals is replaced by the communication between multiple terminals (for example, it can also be referred to as device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, it can also be set as a structure in which the terminal has all or part of the functions of the access network device. In addition, the language such as "uplink" and "downlink" can also be replaced by the language corresponding to the communication between the terminals (for example, "side"). For example, the uplink channel, the downlink channel, etc. can be replaced by the side channel, and the uplink, the downlink, etc. can be replaced by the side link.

[0204] In some embodiments, the terminal may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, the core network device, or the network device may also be configured to have a structure that has all or part of the functions of the terminal.

[0205] In some embodiments, acquisition of data, information, etc. may comply with the laws and regulations of the country where the data is obtained.

[0206] In some embodiments, data, information, etc. may be obtained with the user's consent.

[0207] In addition, each element, each row, or each column in the table of the embodiments of the present disclosure may be implemented as an independent embodiment, and the combination of any elements, any rows, and any columns may also be implemented as an independent embodiment.

[0208] The corresponding relationships shown in the tables in the present disclosure can be configured or predefined. The values ​​of the information in each table are only examples and can be configured as other values, which are not limited by the present disclosure. When configuring the corresponding relationship between the information and each parameter, it is not necessarily required to configure all the corresponding relationships illustrated in each table. For example, in the table in the present disclosure, the corresponding relationships shown in some rows may not be configured. For another example, appropriate deformation adjustments can be made based on the above table, such as splitting, merging, etc. The names of the parameters shown in the titles of the above tables can also use other names that can be understood by the communication device, and the values ​​or representations of the parameters can also be other values ​​or representations that can be understood by the communication device. When implementing the above tables, other data structures can also be used, such as arrays, queues, containers, stacks, linear lists, pointers, linked lists, trees, graphs, structures, classes, heaps, hash tables or hash tables.

[0209] The predefined in the present disclosure may be understood as defined, predefined, stored, pre-stored, pre-negotiated, pre-configured, solidified, or pre-burned.

[0210] For ease of understanding, the terms involved in the present disclosure are first introduced.

[0211] 1. Packet Data Convergence Protocol (PDCP) duplication

[0212] PDCP multiplexing can also be called Packet duplication, which can be understood as: sending a PDCP data packet repeatedly. This has two purposes: repeated transmission to improve the reliability of data packet transmission; reducing the delay of repeated transmission to meet URLLC (high reliability and low latency) requirements. Optionally, if PDCP multiplexing is not triggered, the terminal will transmit a PDCP data packet to a radio link control (Radio Link Control, RLC) entity of the terminal. After processing, the RLC entity will send it to the terminal's media access control (Medium Access Control, MAC) layer. The MAC layer completes the data scheduling to send the PDCP data packet to another terminal. If PDCP multiplexing is turned on, the terminal will transmit a PDCP data packet to two RLC entities of the terminal, namely the Primary RLC entity and the Secondary RLC entity. The two RLC entities will process the PDCP data packet independently and transmit the processed data packet to the terminal's MAC layer. From the perspective of the MAC layer, the data packets sent by the two RLC entities are two independent data packets. The MAC cannot identify whether these are packets multiplexed by PDCP. The MAC layer only needs to complete data scheduling according to the algorithm to send the PDCP data packet to the other terminal.

[0213] FIG1 is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure. As shown in FIG1 , a communication system 100 may include at least one of a first device 101 and a second device 102. The first device and the second device may be at least one of a terminal and a network device, respectively. Optionally, when both the first device and the second device are terminals, SL communication may be performed between the first device and the second device. Optionally, the network device may include at least one of an access network device and a core network device.

[0214] In some embodiments, the terminal includes, for example, a mobile phone, a wearable device, an Internet of Things device, a car with communication function, a smart car, a tablet computer (Pad), a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, and at least one of a wireless terminal device in a smart home, but is not limited to these.

[0215] In some embodiments, the access network device is, for example, a node or device that accesses a terminal to a wireless network. The access network device may include an evolved NodeB (eNB), a next generation evolved NodeB (ng-eNB), a next generation NodeB (gNB), a node B (NB), a home node B (HNB), a home evolved nodeB (HeNB), a wireless backhaul device, a radio network controller (RNC), a base station controller (BSC), a base transceiver station (BTS), a base band unit (BBU), a mobile switching center, a base station in a 6G communication system, an open base station (Open RAN), a cloud base station (Cloud RAN), a base station in other communication systems, and at least one of an access node in a wireless fidelity (WiFi) system, but is not limited thereto.

[0216] In some embodiments, the technical solution of the present disclosure may be applicable to the Open RAN architecture. In this case, the interfaces between or within the access network devices involved in the embodiments of the present disclosure may become internal interfaces of the Open RAN, and the processes and information interactions between these internal interfaces may be implemented through software or programs.

[0217] In some embodiments, the access network device may be composed of a centralized unit (central unit, CU) and a distributed unit (distributed unit, DU), wherein the CU may also be referred to as a control unit (control unit). The CU-DU structure may be used to split the protocol layer of the access network device, with some functions of the protocol layer being centrally controlled by the CU, and the remaining part or all of the functions of the protocol layer being distributed in the DU, and the DU being centrally controlled by the CU, but not limited to this.

[0218] In some embodiments, the core network device may be a device including one or more network elements, or may be a plurality of devices or a group of devices, each including all or part of one or more network elements. The network element may be virtual or physical. The core network may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), and a Next Generation Core (NGC). Alternatively, the core network device may also be a location management function network element. Exemplarily, the location management function network element includes a location server (location server), which may be implemented as any one of the following: Location Management Function (LMF), Enhanced Serving Mobile Location Centre (E-SMLC), Secure User Plane Location (SUPL), and Secure User Plane Location Platform (SUPLLP).

[0219] It can be understood that the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution proposed in the embodiment of the present disclosure. A person of ordinary skill in the art can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution proposed in the embodiment of the present disclosure is also applicable to similar technical problems.

[0220] The following embodiments of the present disclosure may be applied to the communication system 100 shown in FIG1 , or part of the subject, but are not limited thereto. The subjects shown in FIG1 are examples, and the communication system may include all or part of the subjects in FIG1 , or may include other subjects other than FIG1 , and the number and form of the subjects are arbitrary, and the connection relationship between the subjects is an example, and the subjects may be connected or disconnected, and the connection may be in any manner, which may be a direct connection or an indirect connection, and may be a wired connection or a wireless connection.

[0221] The embodiments of the present disclosure may be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), future radio access (FRA), new radio access technology (RAT), new radio (NR), new radio access (NX), future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), Public Land Mobile Network (PLMN) network, Device-to-Device (D2D) system, Machine-to-Machine (M2M) system, Internet of Things (IoT) system, Vehicle-to-Everything (V2X), systems using other communication methods, next-generation systems based on them, etc. In addition, multiple systems can also be combined (for example, a combination of LTE or LTE-A and 5G, etc.) for application.

[0222] Optionally, in a communication system, a capability-limited terminal (e.g., an old version terminal, such as an R16 / 17 terminal) may only be able to send or receive SL service data on one or several carriers due to limited sending and receiving capabilities, which results in the capability-limited terminal not supporting sending and / or receiving on multiple carriers, that is, not supporting carrier aggregation. Therefore, when performing SL carrier aggregation, backward compatibility needs to be considered for capability-limited terminals, that is, when using SL carrier aggregation technology, it is necessary to ensure that the capability-limited terminal can successfully receive SL service data. Among them, an optional method is: the sending terminal achieves backward compatibility based on the mapping of high-level configured services to carriers / frequency bands. Optionally, if the target terminal of a service (such as broadcast and / or multicast services) (i.e., the receiving terminal of a service) is a terminal that does not support carrier aggregation (or is called a capability-limited terminal), only the service data of this service is mapped to a single carrier / frequency band (R16 / 17 carrier / frequency band) for sending. If the target terminal of a service is a terminal that supports carrier aggregation (such as an R18 / 19 terminal), the service data of this service is mapped to multiple carriers / frequency bands for sending.

[0223] However, the above method is unreasonable. Specifically, in some embodiments, the capability-limited terminal may also need to receive service data mapped to multiple carriers / frequency bands, and when the capability-limited terminal receives service data mapped to multiple carriers / frequency bands, since the capability-limited terminal does not support carrier aggregation, it can only receive service data on the carrier / frequency band (i.e., the carrier / frequency band of R16 / 17) that supports the reception of the capability-limited terminal among the multiple carriers / frequency bands transmitting the service data, and cannot receive the service data on multiple carriers / frequency bands transmitting the service. However, at this time, the sending terminal may not know that the capability-limited terminal is receiving the service data, and the sending terminal may directly perform data diversion on multiple carriers / frequency bands, that is, different parts of the service data are sent on multiple carriers / frequency bands respectively. At this time, since the capability-limited terminal cannot receive the service data on multiple carriers / frequency bands transmitting the service data, the capability-limited terminal may lose part of the data of this service, resulting in the inability to achieve backward compatibility with the capability-limited terminal, thereby affecting the stability of SL communication.

[0224] FIG2A is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in FIG2A , the present disclosure embodiment relates to a communication method, which is used in a communication system 100, and the method includes:

[0225] Step 2101: The first device determines a first attribute corresponding to at least one first target address.

[0226] Optionally, the first target address may be, for example, a first target layer 2 address. Also, the first target address may be a target address associated with a first service, and the first service may be a broadcast service and / or a multicast service. The first target address may be associated with at least one first service, and the first target address may also be associated with SL data, wherein the SL data associated with the first target address may be SL data of at least one first service associated with the first target address.

[0227] Optionally, in some embodiments, the first destination address may be a destination address that the first device is interested in sending. When the first destination address is a destination address that the first device is interested in sending, the first device may be a sending terminal of the first destination address, and a receiving terminal that is interested in receiving the first destination address may be referred to as a second device. The first device may broadcast and / or multicast SL data associated with the first destination address. Specifically, the first device may generate a data packet based on the SL data associated with the first destination address, and set the destination address of the data packet to the first destination address, after which the first device may broadcast and / or multicast the data packet, and when the second device receives the data packet, by determining that the destination address of the data packet is the first destination address, the second device determines that the data packet is of interest to receive, and thus may receive and parse the data packet, thereby achieving successful transmission of the SL data associated with the first destination address.

[0228] Optionally, in some other embodiments, the first destination address may also be a destination address that the first device is interested in receiving. When the first destination address is a destination address that the first device is interested in receiving, the first device may be a receiving terminal of the first destination address, and the sending terminal of the first destination address may be referred to as a second device, and the second device may broadcast and / or multicast the SL data associated with the first destination address. Specifically, the second device generates a data packet based on the SL data associated with the first destination address, and sets the destination address of the data packet to the first destination address, after which the second device may broadcast and / or multicast the data packet, and when the first device receives the data packet, by determining that the destination address of the data packet is the first destination address, the first device determines that the data packet is of interest to receive, and thus may receive and parse the data packet, thereby achieving successful transmission of the SL data associated with the first destination address.

[0229] Optionally, in some embodiments, the above-mentioned first attribute may be a transmission attribute (Tx profile), and the first attribute may be used to indicate at least one of the following: the version number of the first target address, whether the first target address supports carrier aggregation, whether the first target address supports data splitting, and whether the first target address is backward compatible. It can be seen that the first attribute corresponding to the first target address is essentially used to indicate whether the first target address is compatible with the existing R16 / 17 terminal device, that is, to indicate whether the existing R16 / 17 terminal device is the receiving terminal of the first target address. Optionally, when the first attribute corresponding to the first target address indicates at least one of the following: the version number of the first target address is the target version number (the target version number is, for example, version R18 and / or R19), the first target address supports carrier aggregation, the first target address supports data splitting, and the first target address is not backward compatible, it means that the first target address is not compatible with the existing R16 / 17 terminal device, that is, the existing R16 / 17 terminal device is not the receiving terminal of the first target address. At this time, it is considered that the receiving terminal of the first target address is a terminal that supports carrier aggregation (for example, an R18 or R19 terminal). When the first attribute corresponding to the first target address indicates at least one of the following: the version number of the first target address is not the target version number (for example, the version number of the first target address is not R18 or R19), the first target address does not support carrier aggregation, the first target address does not support data diversion, and the first target address is backward compatible, then it means that the first target address is compatible with existing R16 / 17 terminal devices, that is, the existing R16 / 17 terminal devices are the receiving terminal of the first target address. At this time, the receiving terminal of the first target address is considered to be a terminal that does not support carrier aggregation (for example, an R16 or R17 terminal).

[0230] Optionally, the content indicated by the first attribute may have other naming forms, which are not specifically limited in the present disclosure. Optionally, the above-mentioned "carrier" may also be called "frequency band" or other names, which are not specifically limited in the present disclosure.

[0231] Optionally, in some embodiments, after the first device determines whether the receiving terminal of the first target address is a terminal that supports carrier aggregation through the first attribute corresponding to the first target address, the first device may subsequently use a sending method that matches the capability of the receiving terminal of the first target address (i.e., whether the receiving terminal of the first target address supports the capability of carrier aggregation) to send the SL data associated with the first target address, so as to ensure that the subsequent receiving terminal of the first target address can successfully receive the SL data associated with the first target address. Thus, when the receiving terminal of the first target address is a terminal that does not support carrier aggregation, backward compatibility with the receiving terminal of the first target address can be achieved, thereby ensuring the successful sending of the SL data and ensuring the stability of SL communication.

[0232] Optionally, in some embodiments, the first attribute may be configured by a high-level layer of the first device, for example, a vehicle-to-everything (V2X) layer of the first device. In some embodiments, the high-level layer of the first device indicates the configured first attribute to the access stratum (AS) layer.

[0233] Optionally, in some embodiments, the first attribute may be configured according to the service granularity; exemplarily, the high layer of the first terminal configures the first attribute according to the service granularity, and the high layer of the first terminal indicates the first attribute of one or more services to the AS layer. Among them, one first service corresponds to one first attribute, the first attributes corresponding to different first services may be the same or different, and one first target address may be associated with at least one first service. Among them, when the first attribute is configured according to the service granularity, the first device may determine the first attribute corresponding to the first target address based on the first attribute corresponding to at least one first service associated with the first target address. Specifically, when the first attributes corresponding to all first services associated with the first target address indicate at least one of the following: the version number is the target version number, carrier aggregation is supported, data diversion is supported, and backward compatibility is not supported, the first device determines that the first attribute corresponding to the first target address is at least one of the following: the version number of the first target address is the target version number, the first target address supports carrier aggregation, the first target address supports data diversion, and the first target address is not backward compatible. When the first attribute corresponding to at least one first service associated with the first target address indicates at least one of the following: the version number is not the target version number, carrier aggregation is not supported, data diversion is not supported, and backward compatibility, the first device determines that the first attribute corresponding to the first target address is at least one of the following: the version number of the first target address is not the target version number, the first target address does not support carrier aggregation, the first target address does not support data diversion, and the first target address is backward compatible.

[0234] Optionally, in some other embodiments, the first attribute may be configured according to the granularity of the target address; illustratively, the upper layer of the first terminal configures the first attribute according to the granularity of the target address, and the upper layer of the first terminal indicates the first attribute of one or more target addresses to the AS layer. Among them, the first target address may correspond to one first attribute. Optionally, when the first attribute is configured according to the granularity of the target address, it can be considered that the first attributes associated with all first services corresponding to the first target address are the same, and are all the first attributes corresponding to the first target address.

[0235] Optionally, in some embodiments, the first attribute may not be configured for the first target address. In this case, the first target address has no associated first attribute, and at least one of the following is determined: the version number of the first target address is not the target version number, the first target address does not support carrier aggregation, the first target address does not support data diversion, and the first target address is backward compatible.

[0236] Optionally, in some embodiments, for the first target address, the first device and the second device are configured with the same first attribute; that is, the first attribute of the first target address configured by the high-level configuration of the first device should be the same as the first attribute of the first target address configured by the high-level configuration of the second device, thereby unifying the understanding of the first attribute of the first target address by the first device and the second device, thereby ensuring that the first device and the second device can subsequently successfully transmit SL data associated with the first target address between the first device and the second device based on the unified understanding of the first attribute of the first target address, thereby ensuring the stability of SL communication.

[0237] Step 2102: The first device determines a mapping relationship between a first target address and a carrier based on a high-level configuration.

[0238] Optionally, in some embodiments, the high layer may configure the relationship between the service and the target address and / or the relationship between the service and the carrier, and the first device may determine the mapping relationship between the target address and the carrier based on the relationship between the service and the target address and / or the relationship between the service and the carrier. Specifically, the first device may determine the mapping relationship between the first target address and the carrier based on the relationship between the first service and the first target address and / or the relationship between the first service and the carrier configured by the high layer. The first service may be a broadcast service and / or a multicast service.

[0239] Optionally, in some embodiments, when the mapping relationship between the first target address and the carrier is: the first target address is mapped to one carrier, it indicates that the first target address supports single-carrier mapping.

[0240] Optionally, in some other embodiments, when the mapping relationship between the first target address and the carrier is: the first target address is mapped to multiple carriers, it indicates that the first target address supports multi-carrier mapping.

[0241] Step 2103, the mapping relationship between the first target address and the carrier is: the first target address is mapped to multiple carriers; and / or the first attribute corresponding to the first target address indicates at least one of the following: the version number of the first target address is the target version number, the first target address supports carrier aggregation, the first target address supports data diversion, and the first target address is not backward compatible; the SL data associated with the first target address is sent through multi-carrier diversion and / or Packet Data Convergence Protocol (PDCP) multiplexing (duplication).

[0242] Optionally, in some embodiments, when the mapping relationship between the first target address and the carrier is: the first target address is mapped to multiple carriers; and / or the first attribute corresponding to the first target address indicates at least one of the following: the version number of the first target address is the target version number, the first target address supports carrier aggregation, the first target address supports data offloading, and the first target address is not backward compatible, then it means that the first target address supports multi-carrier mapping, and the first target address is not compatible with the existing R16 / 17 terminal device, that is, the existing R16 / 17 terminal device is not the receiving terminal of the first target address, and the second device (that is, the receiving terminal of the first target address) supports carrier aggregation (that is, supports multi-carrier reception), then the first device can send the SL data associated with the first target address through multi-carrier offloading and / or PDCP multiplexing.

[0243] Optionally, the following introduces a method of how the first device sends SL data associated with the first target address through multi-carrier splitting and / or PDCP multiplexing.

[0244] Optionally, the first target address may be associated with at least one sidelink radio bearer (SLRB), and the SLRB is associated with one or more first services, and the first service may be a broadcast service and / or a multicast service. The SLRB may also be associated with SL data, and the SL data associated with the SLRB may be: data corresponding to one or more first services of the SLRB in the SL data associated with the first target address. Optionally, the SLRB may be used to transmit the SL data associated with the SLRB.

[0245] In some embodiments, at least one SLRB associated with the first target address corresponds to a SLRB configuration, and the SLRB configuration can indicate whether the corresponding SLRB activates PDCP multiplexing, specifically, the PDCP configuration in the SLRB configuration indicates whether the corresponding SLRB activates PDCP multiplexing. The SLRB configuration may be sent by a network device to the first device through dedicated signaling; or, the SLRB configuration may be sent by a network device to the first device through a system information block (SIB), or, the SLRB configuration may be pre-configured. The first device in a Radio Resource Control (RRC) connected state can obtain the SLRB configuration through dedicated signaling, the first device in an RRC idle state (IDLE) or a deactivated state (INACTIVE) can obtain the SLRB configuration through SIB, and the first device out of coverage (OOC) can obtain the SLRB configuration through pre-configuration. Optionally, the SLRB associated with the first target address and configured to activate PDCP multiplexing may be a first SLRB, which may be one or more, and the SLRB associated with the first target address and configured to deactivate PDCP multiplexing may be a second SLRB, which may be one or more.

[0246] Optionally, for the first SLRB, the first device may send the SL data associated with the first SLRB through PDCP multiplexing. Optionally, the first device may select 2 carriers from the multiple carriers mapped to the first target address to respectively send the same SL data associated with the first SLRB. For example, the first device may select 2 carriers from the multiple carriers mapped to the first target address to respectively send the same SL data associated with the first SLRB. Exemplarily, the first device may select 2 carriers from the multiple carriers to respectively send the same SL data associated with the first SLRB according to implementation; or, select the 2 carriers with the highest quality from the multiple carriers mapped to the first target address to respectively send the same SL data associated with the first SLRB. Exemplarily, the first device may arbitrarily select 2 carriers with the lowest channel busy ratio (CBR) from the multiple carriers to respectively send the same SL data associated with the first SLRB. Exemplarily, the first device may send SL data A associated with the first SLRB on both carriers 1 and 2.

[0247] Optionally, for the second SLRB, the first device may send the SL data associated with the second SLRB through multi-carrier splitting. Optionally, the first device may send different SL data associated with the second SLRB on multiple carriers mapped to the first target address, for example, sending SL data A associated with the second SLRB, SL data B associated with the second SLRB, and SL data C associated with the second SLRB on carriers 1, 2, and 3, respectively.

[0248] The communication method involved in the embodiment of the present disclosure may include at least one of steps S2101 to S2103. For example, step S2101 may be implemented as an independent embodiment, step S2102 may be implemented as an independent embodiment, step S2103 may be implemented as an independent embodiment, and steps S2101+S2102 may be implemented as an independent embodiment, but are not limited thereto.

[0249] In this implementation mode or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other implementation modes or other examples.

[0250] FIG2B is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in FIG2B , the present disclosure embodiment relates to a communication method, which is used in a communication system 100, and the method includes:

[0251] Step 2201: The first device determines a first attribute corresponding to at least one first target address.

[0252] Step 2202: The first device determines a mapping relationship between a first target address and a carrier based on a high-level configuration.

[0253] For a detailed description of steps 2201 - 2202 , please refer to the above embodiment description.

[0254] Step 2203, the mapping relationship between the first target address and the carrier is: the first target address is mapped to multiple carriers; and / or the first attribute corresponding to the first target address indicates at least one of the following: the version number of the first target address is not the target version number, the first target address does not support carrier aggregation, the first target address does not support data offloading, and the first target address is backward compatible; the SL data associated with the first target address is sent via a single carrier and / or PDCP multiplexing.

[0255] Optionally, in some embodiments, when the mapping relationship between the first target address and the carrier is: the first target address is mapped to multiple carriers; and / or the first attribute corresponding to the first target address indicates at least one of the following: the version number of the first target address is not the target version number, the first target address does not support carrier aggregation, the first target address does not support data offloading, and the first target address is backward compatible, it means that the first target address supports multi-carrier mapping, and the first target address is compatible with existing R16 / 17 terminal devices, that is, the existing R16 / 17 terminal device is the receiving terminal of the first target address, and the second device (that is, the receiving terminal of the first target address) includes an R16 / 17 terminal that does not support carrier aggregation (that is, does not support multi-carrier reception), then the first device can send SL data associated with the first target address through a single carrier and / or PDCP multiplexing.

[0256] Optionally, in some embodiments, for the first SLRB, the first device may send the SL data associated with the first SLRB through PDCP multiplexing. Optionally, the first device may select 2 carriers from the multiple carriers mapped to the first target address to respectively send the same SL data associated with the first SLRB. For example, the first device may select an existing carrier (such as a legacy carrier, that is, a legacy carrier supported by R16 / 17 terminals) and one other carrier from the multiple carriers mapped to the first target address to respectively send the same SL data associated with the first SLRB. Optionally, the other carrier may be a carrier other than the existing carrier that may be backward compatible. Exemplarily, the first device may select a carrier from the multiple carriers other than the existing carrier according to implementation; or, it may be the carrier with the highest quality other than the existing carrier that may be backward compatible. Exemplarily, the first device may select a carrier with the lowest CBR from the multiple carriers other than the existing carrier.

[0257] It should be noted that, in some embodiments, it can be known from the aforementioned explanation of "PDCP multiplexing" that during PDCP multiplexing, a PDCP data packet will be transmitted to two RLC entities of the terminal, namely the Primary RLC entity and the Secondary RLC entity. The two RLC entities will process the PDCP data packets independently and transmit the processed data packets to the MAC layer of the terminal. Among them, the two PDCP data packets obtained by the two RLC entities independently can be associated with different logical channel identifiers (logical channel IDentity, LCID) respectively, so as to send the PDCP data packet through the logical channel corresponding to the LCID associated with the PDCP data packet. Optionally, in some embodiments, one of the PDCP data packets can be associated with an existing LCID (for example, 4-19) to be sent through the logical channel corresponding to the existing LCID, and the other PDCP data packet can be associated with a reserved LCID to be sent through the reserved logical channel.

[0258] Based on this, in some embodiments, when the first device sends the SL data associated with the first SLRB through PDCP multiplexing, the first device can send the data packet associated with the existing LCID corresponding to the SL data associated with the first SLRB on an existing carrier (such as a legacy carrier, that is, a legacy carrier supported by R16 / 17 terminals) that can achieve backward compatibility, and send the data packet associated with the reserved LCID corresponding to the SL data associated with the first SLRB on the other carriers mentioned above.

[0259] Optionally, for the second SLRB, the first device may send SL data associated with the second SLRB through an existing carrier that can achieve backward compatibility.

[0260] For further detailed description of steps 2202 - 2203 , please refer to the above embodiment description.

[0261] The communication method involved in the embodiment of the present disclosure may include at least one of steps S2201 to S2203. For example, step S2201 may be implemented as an independent embodiment, step S2202 may be implemented as an independent embodiment, step S2203 may be implemented as an independent embodiment, and steps S2201+S2202 may be implemented as an independent embodiment, but are not limited thereto.

[0262] In this implementation mode or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other implementation modes or other examples.

[0263] FIG2C is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in FIG2C , the present disclosure embodiment relates to a communication method, which is used in a communication system 100, and the method includes:

[0264] Step 2301: The first device determines a first attribute corresponding to at least one first target address.

[0265] Step 2302: The first device determines a mapping relationship between a first target address and a carrier based on a high-level configuration.

[0266] Step 2303, the mapping relationship between the first target address and the carrier is: the first target address is mapped to one carrier; and / or the first attribute corresponding to the first target address indicates at least one of the following: the version number of the first target address is the target version number, the first target address supports carrier aggregation, the first target address supports data diversion, and the first target address is not backward compatible; the SL data associated with the first target address is sent via a single carrier.

[0267] Optionally, in some embodiments, when the mapping relationship between the first target address and the carrier is: the first target address is mapped to one carrier; and / or the first attribute corresponding to the first target address indicates at least one of the following: the version number of the first target address is the target version number, the first target address supports carrier aggregation, the first target address supports data diversion, and the first target address is not backward compatible, then it means that the first target address supports single carrier mapping, and the first target address is not compatible with existing R16 / 17 terminal devices, that is, the existing R16 / 17 terminal devices are not the receiving terminal of the first target address, and the second device (that is, the receiving terminal of the first target address) is a terminal that supports carrier aggregation (that is, supports multi-carrier reception). Among them, although the first target address is not backward compatible, since the first target address supports single-carrier mapping but does not support multi-carrier mapping, at this time, the first device cannot send the SL data associated with the first target address through multiple carriers, but needs to send the SL data associated with the first target address through a single carrier. For example, the SL data associated with the first target address can be sent through an existing carrier that can achieve backward compatibility (such as a legacy carrier, that is, a legacy carrier supported by R16 / 17 terminals).

[0268] For other detailed descriptions of steps 2301 - 2303 , please refer to the above embodiment description.

[0269] The communication method involved in the embodiment of the present disclosure may include at least one of steps S2301 to S2303. For example, step S2301 may be implemented as an independent embodiment, step S2302 may be implemented as an independent embodiment, step S2303 may be implemented as an independent embodiment, and steps S2301+S2302 may be implemented as an independent embodiment, but are not limited thereto.

[0270] In this implementation mode or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other implementation modes or other examples.

[0271] FIG2D is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in FIG2D , the embodiment of the present disclosure relates to a communication method, which is used in a communication system 100, and the method includes:

[0272] Step 2401: The first device determines a first attribute corresponding to at least one first target address.

[0273] Step 2402: The first device determines a mapping relationship between a first target address and a carrier based on a high-level configuration.

[0274] Step 2403, the mapping relationship between the first target address and the carrier is: the first target address is mapped to one carrier; and / or the first attribute corresponding to the first target address indicates at least one of the following: the version number of the first target address is not the target version number, the first target address does not support carrier aggregation, the first target address does not support data diversion, and the first target address is backward compatible; the SL data associated with the first target address is sent via a single carrier.

[0275] Optionally, in some embodiments, when the mapping relationship between the first target address and the carrier is: the first target address is mapped to one carrier; and / or the first attribute corresponding to the first target address indicates at least one of the following: the version number of the first target address is the target version number, the first target address supports carrier aggregation, the first target address supports data diversion, and the first target address is backward compatible, then it means that the first target address supports single carrier mapping, and the first target address is compatible with existing R16 / 17 terminal devices, that is, the existing R16 / 17 terminal devices are the receiving terminals of the first target address, and the second device (i.e., the receiving terminal of the first target address) includes an R16 / 17 terminal that does not support carrier aggregation (i.e., does not support multi-carrier reception). At this time, the first device can send the SL data associated with the first target address through a single carrier. For example, the SL data associated with the first target address can be sent through an existing carrier that can achieve backward compatibility (such as a legacy carrier, that is, a legacy carrier supported by the R16 / 17 terminal).

[0276] For further detailed description of steps 2401 - 2403 , please refer to the above embodiment description.

[0277] The communication method involved in the embodiment of the present disclosure may include at least one of steps S2401 to S2403. For example, step S2401 may be implemented as an independent embodiment, step S2402 may be implemented as an independent embodiment, step S2403 may be implemented as an independent embodiment, and steps S2401+S2402 may be implemented as an independent embodiment, but are not limited thereto.

[0278] In this implementation mode or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other implementation modes or other examples.

[0279] FIG3A is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in FIG3A , the present disclosure embodiment relates to a communication method, which is used for a first device 101, and the method includes:

[0280] Step 3101: The first device determines a first attribute corresponding to at least one first target address.

[0281] Step 3102: The first device determines a mapping relationship between a first target address and a carrier based on a high-level configuration.

[0282] Step 3103, the mapping relationship between the first target address and the carrier is: the first target address is mapped to multiple carriers; and / or the first attribute corresponding to the first target address indicates at least one of the following: the version number of the first target address is the target version number, the first target address supports carrier aggregation, the first target address supports data offloading, and the first target address is not backward compatible; the SL data associated with the first target address is sent through multi-carrier offloading and / or PDCP multiplexing.

[0283] For a detailed description of steps 3101 - 3103 , please refer to the above embodiment description.

[0284] The communication method involved in the embodiment of the present disclosure may include at least one of steps S3101 to S3103. For example, step S3101 may be implemented as an independent embodiment, step S3102 may be implemented as an independent embodiment, and step S3101+S3102 may be implemented as an independent embodiment, but is not limited thereto.

[0285] In this implementation mode or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other implementation modes or other examples.

[0286] FIG3B is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in FIG3B , the present disclosure embodiment relates to a communication method, which is used for a first device 101, and the method includes:

[0287] Step 3201: The first device determines a first attribute corresponding to at least one first target address.

[0288] Step 3202: The first device determines a mapping relationship between a first target address and a carrier based on a high-level configuration.

[0289] Step 3203, the mapping relationship between the first target address and the carrier is: the first target address is mapped to multiple carriers; and / or the first attribute corresponding to the first target address indicates at least one of the following: the version number of the first target address is not the target version number, the first target address does not support carrier aggregation, the first target address does not support data offloading, and the first target address is backward compatible; the first device sends the SL data associated with the first target address via a single carrier and / or PDCP multiplexing.

[0290] For a detailed description of steps 3201 - 3203 , please refer to the above embodiment description.

[0291] The communication method involved in the embodiment of the present disclosure may include at least one of step S3201 to step S3203. For example, step S3201 may be implemented as an independent embodiment, and step S3202 may be implemented as an independent embodiment, but is not limited thereto.

[0292] In this implementation mode or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other implementation modes or other examples.

[0293] FIG3C is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in FIG3C , the present disclosure embodiment relates to a communication method, which is used for a first device 101, and the method includes:

[0294] Step 3301: The first device determines a first attribute corresponding to at least one first target address.

[0295] Step 3302: The first device determines a mapping relationship between a first target address and a carrier based on a high-level configuration.

[0296] Step 3303, the mapping relationship between the first target address and the carrier is: the first target address is mapped to one carrier; and / or the first attribute corresponding to the first target address indicates at least one of the following: the version number of the first target address is the target version number, the first target address supports carrier aggregation, the first target address supports data diversion, and the first target address is not backward compatible; the first device sends the SL data associated with the first target address through a single carrier.

[0297] For a detailed description of steps 3301 - 3303 , please refer to the above embodiment description.

[0298] The communication method involved in the embodiment of the present disclosure may include at least one of steps S3301 to S3303. For example, step S3301 may be implemented as an independent embodiment, step S3302 may be implemented as an independent embodiment, and step S3301+S3302 may be implemented as an independent embodiment, but is not limited thereto.

[0299] In this implementation mode or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other implementation modes or other examples.

[0300] FIG3D is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in FIG3D , the present disclosure embodiment relates to a communication method, which is used for a first device 101, and the method includes:

[0301] Step 3401: The first device determines a first attribute corresponding to at least one first target address.

[0302] Step 3402: The first device determines a mapping relationship between a first target address and a carrier based on a high-level configuration.

[0303] Step 3403, the mapping relationship between the first target address and the carrier is: the first target address is mapped to one carrier; and / or the first attribute corresponding to the first target address indicates at least one of the following: the version number of the first target address is not the target version number, the first target address does not support carrier aggregation, the first target address does not support data diversion, and the first target address is backward compatible; the first device sends the SL data associated with the first target address through a single carrier.

[0304] For a detailed description of steps 3401 - 3403 , please refer to the above embodiment description.

[0305] The communication method involved in the embodiment of the present disclosure may include at least one of step S3401 to step S3403. For example, step S3401 may be implemented as an independent embodiment, and step S3402 may be implemented as an independent embodiment, but is not limited thereto.

[0306] In this implementation mode or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other implementation modes or other examples.

[0307] FIG3E is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in FIG3E , the present disclosure embodiment relates to a communication method, which is used for a first device 101, and the method includes:

[0308] Step 3501: The first device sends SL data associated with the first target address based on a mapping relationship between the first target address and the carrier and at least one of a first attribute corresponding to the first target address.

[0309] Optionally, the first attribute corresponding to the first target address is used to indicate at least one of the following: a version number of the first target address, whether the first target address supports carrier aggregation, whether the first target address supports data offloading, and whether the first target address is backward compatible; wherein, the first target address is a target address associated with a broadcast service and / or a multicast service, and the first target address is a target address that the first device is interested in sending and / or receiving.

[0310] Optionally, the method further comprises:

[0311] The first device determines a first attribute corresponding to at least one first target address.

[0312] Optionally, the first attribute is configured according to a service granularity; wherein one first service corresponds to one first attribute, the first target address is associated with at least one first service; the first service includes a broadcast service and / or a multicast service; or

[0313] The first attribute is configured according to the target address granularity; wherein the first target address corresponds to one first attribute.

[0314] Optionally, determining the first attribute corresponding to at least one first target address includes:

[0315] The first attribute is configured according to a service granularity, and the first attribute corresponding to the first target address is determined based on a first attribute corresponding to at least one first service associated with the first target address.

[0316] Optionally, the determining the first attribute corresponding to the first target address based on the first attribute corresponding to at least one first service associated with the first target address includes:

[0317] The first attributes corresponding to all first services associated with the first target address indicate at least one of the following: the version number is the target version number, carrier aggregation is supported, data diversion is supported, and there is no backward compatibility. It is determined that the first attribute corresponding to the first target address is at least one of the following: the version number of the first target address is the target version number, the first target address supports carrier aggregation, the first target address supports data diversion, and the first target address is not backward compatible.

[0318] Optionally, the method further comprises:

[0319] There is no corresponding first attribute for the first target address, and at least one of the following is determined: the version number of the first target address is not the target version number, the first target address does not support carrier aggregation, the first target address does not support data diversion, and the first target address is backward compatible.

[0320] Optionally, the sending the SL data associated with the first target address based on at least one of a mapping relationship between the first target address and the carrier and a first attribute corresponding to the first target address includes:

[0321] The mapping relationship between the first target address and the carrier is: the first target address is mapped to multiple carriers; and / or the first attribute corresponding to the first target address indicates at least one of the following: the version number of the first target address is the target version number, the first target address supports carrier aggregation, the first target address supports data diversion, and the first target address is not backward compatible; the SL data associated with the first target address is sent through multi-carrier diversion and / or packet data convergence protocol PDCP duplication.

[0322] Optionally, the sending the SL data associated with the first target address based on at least one of a mapping relationship between the first target address and the carrier and a first attribute corresponding to the first target address includes:

[0323] The mapping relationship between the first target address and the carrier is: the first target address is mapped to multiple carriers; and / or the first attribute corresponding to the first target address indicates at least one of the following: the version number of the first target address is not the target version number, the first target address does not support carrier aggregation, the first target address does not support data offloading, and the first target address is backward compatible; the SL data associated with the first target address is sent via a single carrier and / or PDCP multiplexing.

[0324] Optionally, the sending the SL data associated with the first target address based on at least one of a mapping relationship between the first target address and the carrier and a first attribute corresponding to the first target address includes:

[0325] The mapping relationship between the first target address and the carrier is: the first target address is mapped to one carrier; and / or the first attribute corresponding to the first target address indicates at least one of the following: the version number of the first target address is the target version number, the first target address supports carrier aggregation, the first target address supports data diversion, and the first target address is not backward compatible; the SL data associated with the first target address is sent via a single carrier.

[0326] Optionally, the sending the SL data associated with the first target address based on at least one of a mapping relationship between the first target address and the carrier and a first attribute corresponding to the first target address includes:

[0327] The mapping relationship between the first target address and the carrier is: the first target address is mapped to one carrier; and / or the first attribute corresponding to the first target address indicates at least one of the following: the version number of the first target address is not the target version number, the first target address does not support carrier aggregation, the first target address does not support data diversion, and the first target address is backward compatible; the SL data associated with the first target address is sent via a single carrier.

[0328] Optionally, the sending the SL data associated with the first target address through PDCP multiplexing includes:

[0329] The SL data associated with the first SLRB is sent through PDCP multiplexing; wherein the first SLRB is an SLRB associated with the first target address and with PDCP multiplexing activated, and the first SLRB is one or more.

[0330] Optionally, sending the SL data associated with the first SLRB through PDCP multiplexing includes:

[0331] Select two carriers from among the multiple carriers mapped to the first target address to respectively send the same SL data associated with the first SLRB.

[0332] Optionally, the selecting two carriers from the multiple carriers mapped to the first target address to respectively send the same SL data associated with the first SLRB includes:

[0333] Randomly select two carriers from the multiple carriers mapped to the first target address to respectively send the same SL data associated with the first SLRB.

[0334] Optionally, the sending of SL data associated with the first target address by using multi-carrier offload includes:

[0335] The SL data associated with the second SLRB is sent through the multiple carriers mapped to the first target address; wherein the second SLRB is the SLRB associated with the first target address and deactivated PDCP multiplexing, and the second SLRB is one or more.

[0336] Optionally, the sending of SL data associated with the second SLRB through multi-carrier splitting includes:

[0337] Different SL data associated with the second SLRB are sent on multiple carriers mapped to the first target address.

[0338] Optionally, the sending the SL data associated with the first target address through PDCP multiplexing includes:

[0339] The SL data associated with the first SLRB is sent through PDCP multiplexing; wherein the first SLRB is an SLRB associated with the first target address and with PDCP multiplexing activated, and the first SLRB is one or more.

[0340] Optionally, sending the SL data associated with the first SLRB through PDCP multiplexing includes:

[0341] Select two carriers from among the multiple carriers mapped to the first target address to respectively send the same SL data associated with the first SLRB.

[0342] Optionally, the selecting two carriers from the multiple carriers mapped to the first target address to respectively send the same SL data associated with the first SLRB includes:

[0343] An existing carrier that can achieve backward compatibility and any other carrier are selected from multiple carriers mapped to the first target address to respectively send the same SL data associated with the first SLRB.

[0344] Optionally, the sending the SL data associated with the first target address through a single carrier includes:

[0345] The SL data associated with the second SLRB is sent via an existing carrier that can achieve backward compatibility; wherein the second SLRB is an SLRB associated with the first target address and with PDCP multiplexing deactivated, and the second SLRB is one or more.

[0346] Optionally, the sending the SL data associated with the first target address through a single carrier includes:

[0347] The SL data associated with the first target address is sent via an existing carrier that can achieve backward compatibility.

[0348] Optionally, the method further comprises:

[0349] Determine the SLRB configurations respectively corresponding to at least one first SLRB and / or at least one second SLRB, where the SLRB configurations respectively corresponding to the at least one first SLRB and / or at least one second SLRB are used to configure whether to activate PDCP multiplexing for the at least one first SLRB and / or at least one second SLRB;

[0350] Determine whether PDCP multiplexing is activated for the at least one first SLRB and / or the at least one second SLRB associated with the first target address according to the SLRB configurations respectively corresponding to the at least one first SLRB and / or the at least one second SLRB.

[0351] Optionally, the determining of the SLRB configurations corresponding to the at least one first SLRB and / or the at least one second SLRB respectively includes at least one of the following:

[0352] Obtaining SLRB configurations respectively corresponding to the at least one first SLRB and / or the at least one second SLRB sent through dedicated signaling;

[0353] Obtaining SLRB configurations respectively corresponding to the at least one first SLRB and / or the at least one second SLRB sent through a system information block SIB;

[0354] Obtain the SLRB configurations corresponding to the at least one first SLRB and / or at least one second SLRB pre-configured respectively.

[0355] Optionally, the method further comprises:

[0356] A mapping relationship between the first target address and the carrier is determined based on a high-level configuration.

[0357] Optionally, for the first target address, the first device and the second device are configured with the same first attribute; wherein the first device is a sending terminal of the first target address, and the second device is a receiving terminal of the first target address.

[0358] Optionally, the target version number is R18.

[0359] For a detailed introduction to step 3501, please refer to the contents of the above embodiment.

[0360] In this implementation mode or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other implementation modes or other examples.

[0361] FIG4A is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in FIG4A , the present disclosure embodiment relates to a communication method, which is used for a second device 102, and the method includes:

[0362] Step 4101: The second device determines a first attribute corresponding to at least one second target address.

[0363] Optionally, the second target address may be, for example, a second target layer 2 address. Also, the second target address may be a target address associated with a second service, and the second service may be a broadcast service and / or a multicast service. The second target address may be associated with at least one second service, and the second target address may also be associated with SL data, wherein the SL data associated with the second target address may be SL data of at least one second service associated with the second target address.

[0364] Optionally, in some embodiments, the second target address may be a target address that the second device is interested in sending and / or interested in receiving. When the second target address is a target address that the second device is interested in sending, or when the second target address is a target address that the second device is interested in receiving, the principle is the same as the aforementioned "the first target address is a target address that the first device is interested in sending, or the first target address is a target address that the first device is interested in receiving", and will not be repeated here.

[0365] Furthermore, the above-mentioned introduction about the first target address is also applicable to the introduction about the second target address, which will not be repeated here.

[0366] Step 4102: The second device determines a mapping relationship between a second target address and a carrier based on a high-level configuration.

[0367] For a detailed introduction to step 4102, please refer to the above description of step 2102.

[0368] Step 4103: At least one second target address satisfies a first preset condition, and the second device receives SL data associated with the at least one second target address through a multi-carrier.

[0369] Optionally, the first preset condition may include: the mapping relationship between the second target address and the carrier is: the second target address is mapped to multiple carriers; and / or, the first attribute corresponding to the second target address indicates at least one of the following: the version number of the second target address is the target version number, the second target address supports carrier aggregation, the second target address supports data diversion, and the second target address is not backward compatible.

[0370] Optionally, in some embodiments, when the second device receives SL data associated with at least one second target address, if at least one second target address satisfies the first preset condition, it means that the SL data associated with at least one second target address is sent through multiple carriers. At this time, the second device should also correspondingly receive the SL data associated with at least one second target address through multiple carriers.

[0371] For a detailed description of steps 4101-4103, please refer to the contents of the above embodiment.

[0372] The communication method involved in the embodiment of the present disclosure may include at least one of step S4101 to step S4103. For example, step S4101 may be implemented as an independent embodiment, and step S4102 may be implemented as an independent embodiment, but is not limited thereto.

[0373] In this implementation mode or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other implementation modes or other examples.

[0374] FIG4B is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in FIG4B , the present disclosure embodiment relates to a communication method, which is used for a second device 102, and the method includes:

[0375] Step 4201: The second device determines a first attribute corresponding to at least one second target address.

[0376] Step 4102: The second device determines a mapping relationship between a second target address and a carrier based on a high-level configuration.

[0377] Step 4203: All second target addresses satisfy a second preset condition, and SL data associated with at least one second target address is received via an existing carrier that can achieve backward compatibility.

[0378] Among them, the second preset condition includes: the mapping relationship between the second target address and the carrier is: the second target address is mapped to one carrier; and / or, the first attribute corresponding to the second target address indicates at least one of the following: the version number of the first target address is not the target version number, the second target address does not support carrier aggregation, the second target address does not support data splitting, and the second target address is backward compatible. And / or, the second preset condition includes: the mapping relationship between the second target address and the carrier is: the second target address is mapped to multiple carriers; and / or, the first attribute corresponding to the second target address indicates at least one of the following: the version number of the second target address is not the target version number, the second target address does not support carrier aggregation, the second target address does not support data splitting, and the second target address is backward compatible.

[0379] Optionally, when the second device receives SL data associated with at least one second target address, if all the second target addresses meet the second preset condition, it means that the SL data associated with all the second target addresses are sent through an existing carrier that can achieve backward compatibility. At this time, the second device should also correspondingly receive SL data associated with at least one second target address through an existing carrier that can achieve backward compatibility.

[0380] For a detailed description of steps 4201-4203, please refer to the contents of the above embodiment.

[0381] The communication method involved in the embodiment of the present disclosure may include at least one of step S4201 to step S4203. For example, step S4201 may be implemented as an independent embodiment, and step S4202 may be implemented as an independent embodiment, but is not limited thereto.

[0382] In this implementation mode or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other implementation modes or other examples.

[0383] FIG4C is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in FIG4C , the present disclosure embodiment relates to a communication method, which is used for a second device 102, and the method includes:

[0384] Step 4301: The second device receives SL data on one or more carriers based on a mapping relationship between a second target address and a carrier and at least one of the first attributes corresponding to the second target address.

[0385] Optionally, the first attribute corresponding to the second target address is used to indicate at least one of the following: a version number of the second target address, whether the second target address supports carrier aggregation, whether the second target address supports data offloading, and whether the second target address is backward compatible; the second target address is a target address associated with a broadcast service and / or a multicast service, and the second target address is a target address that the second device is interested in sending and / or receiving.

[0386] Optionally, the method further comprises:

[0387] The second device determines a first attribute corresponding to each of the at least one second target address.

[0388] Optionally, the first attribute is configured according to the service granularity; wherein one second service corresponds to one first attribute, and the second target address is associated with at least one second service; the second service includes a broadcast service and / or a multicast service; or

[0389] The first attribute is configured according to the target address granularity; wherein the second target address corresponds to one first attribute.

[0390] Optionally, determining the first attribute corresponding to the at least one second target address includes:

[0391] The first attribute is configured according to a service granularity, and the first attribute corresponding to the second target address is determined based on a first attribute corresponding to at least one second service associated with the second target address.

[0392] Optionally, the determining the first attribute corresponding to the second target address based on the first attribute corresponding to at least one second service associated with the second target address includes:

[0393] The first attributes corresponding to all second services associated with the second target address indicate at least one of the following: the version number is the target version number, carrier aggregation is supported, data offloading is supported, and there is no backward compatibility. It is determined that the first attribute corresponding to the second target address is at least one of the following: the version number of the second target address is the target version number, the second target address supports carrier aggregation, the second target address supports data offloading, and the second target address is not backward compatible.

[0394] Optionally, the method further comprises:

[0395] There is no corresponding first attribute for the second target address, and at least one of the following is determined: the version number of the second target address is not the target version number, the second target address does not support carrier aggregation, the second target address does not support data diversion, and the second target address is backward compatible.

[0396] Optionally, the receiving SL data on one or more carriers based on a mapping relationship between the second target address and the carrier and at least one of the first attributes corresponding to the second target address includes:

[0397] At least one second target address satisfies a first preset condition, and SL data associated with the at least one second target address is received through multiple carriers; wherein the first preset condition includes: a mapping relationship between the second target address and the carrier is: the second target address is mapped to multiple carriers; and / or, a first attribute corresponding to the second target address indicates at least one of the following: the version number of the second target address is the target version number, the second target address supports carrier aggregation, the second target address supports data diversion, and the second target address is not backward compatible.

[0398] Optionally, the receiving SL data on one or more carriers based on a mapping relationship between the second target address and the carrier and at least one of the first attributes corresponding to the second target address includes:

[0399] All second target addresses meet the second preset condition, and the SL data associated with at least one second target address is received through an existing carrier that can achieve backward compatibility; wherein, the second preset condition includes: the mapping relationship between the second target address and the carrier is: the second target address is mapped to one carrier; and / or, the first attribute corresponding to the second target address indicates at least one of the following: the version number of the second target address is not the target version number, the second target address does not support carrier aggregation, the second target address does not support data diversion, and the second target address is backward compatible; and / or, the second preset condition includes: the mapping relationship between the second target address and the carrier is: the second target address is mapped to multiple carriers; and / or, the first attribute corresponding to the second target address indicates at least one of the following: the version number of the second target address is not the target version number, the second target address does not support carrier aggregation, the second target address does not support data diversion, and the second target address is backward compatible.

[0400] Optionally, for the second target address, the first device and the second device are configured with the same first attribute; wherein the first device is a sending terminal of the second target address, and the second device is a receiving terminal of the second target address.

[0401] For a detailed introduction to step 4301, please refer to the contents of the above embodiment.

[0402] In this implementation mode or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other implementation modes or other examples.

[0403] FIG5 is a flow chart of a communication method according to an embodiment of the present disclosure. As shown in FIG5, the present disclosure embodiment relates to a communication method, which is used in a communication system, the communication system including a first device and a second device, and the method includes at least one of the following:

[0404] Step 5101: The first device sends SL data associated with the first target address based on a mapping relationship between the first target address and the carrier and at least one of a first attribute corresponding to the first target address.

[0405] Step 5102: The second device receives SL data on one or more carriers based on a mapping relationship between the second target address and the carrier and at least one of the first attributes corresponding to the second target address.

[0406] The optional implementation methods of step 5101-step 5102 can refer to the introduction of the above embodiment.

[0407] In some embodiments, the above method may include the method described in the above embodiments of the communication system side, the first device side, the second device side, etc., which will not be repeated here.

[0408] The communication method involved in the embodiment of the present disclosure may include at least one of step S5101 to step S5104. For example, step S5101 may be implemented as an independent embodiment, and step S5102 may be implemented as an independent embodiment, but is not limited thereto.

[0409] In this implementation mode or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other implementation modes or other examples.

[0410] The following is an exemplary introduction to the above method.

[0411] Optional example: Define a Tx profile with service type granularity or target address granularity for broadcast / multicast services, indicating whether the broadcast / multicast services support carrier aggregation / data offloading / backward compatibility.

[0412] Optional Example 1: Define a Tx profile at the service type granularity or the destination address granularity for broadcast / multicast services

[0413] Embodiment: If the Tx profile is defined at the service type granularity, different service types are associated with different Tx profiles. If a target address can be associated with multiple different service types, a target address may be associated with multiple Tx profiles.

[0414] Embodiment: If the Tx profile is defined based on the target address granularity, there is only one Tx profile associated with one target address, and the high-level layer needs to ensure that the Tx profiles associated with all service types associated with one target address are the same. Embodiment: The Tx profile is indicated to the AS layer by the high-level layer.

[0415] Optional Example 2: Tx profile is used to indicate whether broadcast / multicast services support carrier aggregation / data offload / backward compatibility

[0416] Embodiment: The Tx profile may indicate a version, such as Rel-18, and may also be used to indicate whether carrier aggregation / data splitting is supported. Exemplarily, the content specifically indicated by the Tx profile may have other naming forms, which are not specifically limited in the present disclosure. Exemplarily, the Tx profile may indicate whether the service is backward compatible with R16 / 17legacy terminals. Exemplarily, the terminal determines whether the R16 / 17legacy terminal is the receiving terminal of the service / target address based on the Tx profile.

[0417] Embodiment: If the Tx profile is defined at the service type granularity, and all Tx profiles associated with a target address indicate support for carrier aggregation / data splitting, the terminal device considers that the target address supports carrier aggregation / data splitting. If a service is mapped to only one carrier / frequency band, the Tx profile associated with this service does not support carrier aggregation / data splitting. If a service is mapped to multiple carriers / frequency bands, the Tx profile associated with this service may or may not support carrier aggregation / data splitting. If a target address has no associated Tx profile, the terminal device considers that the target address does not support carrier aggregation / data splitting.

[0418] Embodiment: If the Tx profile is defined at the target address granularity, and if the target address is mapped to only one carrier / frequency band, the Tx profile associated with the target address does not support carrier aggregation / data splitting. If the target address is mapped to multiple carriers / frequency bands, the Tx profile associated with the target address may support carrier aggregation / data splitting or may not support carrier aggregation / data splitting.

[0419] Optional Example 3: For a destination address of a broadcast / multicast service, all sending terminals and receiving terminals need to be configured with the same Tx profile(s).

[0420] Optional example 4: The terminal device determines that a broadcast / multicast service target address supports carrier aggregation / data offloading / does not support backward compatibility, and the terminal device can offload data on multiple carriers / frequency bands.

[0421] Embodiment: The terminal device is a transmitting terminal. Exemplarily, the terminal splitting data on multiple carriers / frequency bands means that the terminal device splits data on multiple carriers / frequency bands (data split), and the data transmitted on different carriers / frequency bands belong to the target address, and the data transmitted on different carriers / frequency bands are different. For example, packets A, B, and C are sent on carriers 1, 2, and 3 respectively. The terminal device may also enable PDCP multiplexing, specifically, enable PDCP multiplexing according to the configuration of the network device, for example, for certain SL radio bearers (SLRB radio bearers) associated with the broadcast / multicast service target address, if the network device configuration enables PDCP multiplexing, the terminal device enables PDCP multiplexing to transmit these SLRBs (the terminal device transmits the same data of this SLRB on two different carriers), wherein the terminal device can arbitrarily select two carriers from multiple carriers that support aggregation to do PDCP multiplexing.

[0422] For example, for some SLRB radio bearers associated with the target address of this broadcast / multicast service, if the network device is configured to enable PDCP multiplexing, the terminal device transmits these SLRBs through data splitting (the terminal device transmits different data of this SLRB on two or more different carriers)

[0423] Embodiment: The terminal device can determine whether the broadcast / multicast target address supports carrier aggregation / data splitting in combination with the mapping of the broadcast / multicast service to the carrier / frequency band configured by the high-level configuration and / or the Tx profile associated with the target broadcast / multicast target address. Exemplarily, case a: If a broadcast / multicast target address is mapped to multiple carriers / frequency bands, and the Tx profile associated with the target address supports carrier aggregation / data splitting, the terminal device determines that the target address supports carrier aggregation / data splitting. Exemplarily, case b: If a broadcast / multicast target address is mapped to multiple carriers / frequency bands, and the Tx profile associated with the target address does not support carrier aggregation / data splitting, the terminal device determines that the target address does not support carrier aggregation / data splitting. Exemplarily, case c: If a broadcast / multicast target address is mapped to one carrier / frequency band, and the Tx profile associated with the target address supports carrier aggregation / data splitting, the terminal device determines that the target address does not support carrier aggregation / data splitting. Exemplarily, case d: if a broadcast / multicast target address is mapped to a carrier / frequency band, and the Tx profile associated with the target address does not support carrier aggregation / data offloading, the terminal device determines that the target address does not support carrier aggregation / data offloading.

[0424] Optional example 5: The terminal device determines that a broadcast / multicast service target address does not support carrier aggregation / data offloading / supports backward compatibility, and the terminal device sends data on a single carrier / frequency band.

[0425] Embodiment: The terminal device is a transmitting terminal. Exemplarily, the single carrier / frequency band is a carrier / frequency band supported by the R16 / 17 terminal. The above cases bcd are applicable. Exemplarily, for case b, a broadcast / multicast target address is mapped to multiple carriers / frequency bands, and the Tx profile associated with the target address does not support carrier aggregation / data splitting, that is, the broadcast / multicast target address is backward compatible with R16 / 17 terminal devices (R16 / 17 terminal devices need to receive the broadcast / multicast services associated with the broadcast / multicast address). For this broadcast / multicast target address, the terminal device can also enable PDCP multiplexing or send it on a single carrier / frequency band. Specifically, the terminal device enables PDCP multiplexing according to the configuration of the network device. For example, for certain SL radio bearers (SLRB radio bearers) associated with the broadcast / multicast service target address, if the network device configuration enables PDCP multiplexing, the terminal device enables PDCP multiplexing to transmit these SLRBs (the terminal device transmits the same data of this SLRB on two different carriers), where the terminal device needs to select the legacy carrier / frequency band supported by the R16 / 17 terminal as one of the carriers, and arbitrarily select one carrier from the multiple carriers that support aggregation as another carrier for PDCP multiplexing.

[0426] For example, for some SLRB radio bearers associated with the target address of this broadcast / multicast service, if the network equipment is configured to enable PDCP multiplexing, the terminal equipment transmits the data of these SLRBs through a single carrier / frequency band.

[0427] Optional Example 6: The terminal device determines that a broadcast / multicast service target address does not support carrier aggregation / data splitting, and the terminal device performs PDCP duplication on multiple carriers / frequency bands.

[0428] Embodiment: The terminal device is a transmitting terminal. Exemplarily, the above case b applies. Exemplarily, the PDCP duplication of the terminal on multiple carriers / frequency bands means that the terminal device multiplexes data (data duplication) on multiple carriers / frequency bands, and the data transmitted on different carriers / frequency bands belong to the target address, and the data transmitted on different carriers / frequency bands are the same. For example, packet A is sent on both carriers 1 and 2.

[0429] Embodiment: The terminal device sends a data packet associated with an existing LCID (eg, 4-19) via a carrier / frequency band supported by the R16 / 17 terminal.

[0430] Optional example 7: The terminal device determines that a broadcast / multicast service target address supports carrier aggregation / data splitting, and the terminal device receives data on multiple carriers / frequency bands.

[0431] Embodiment: The terminal device is a receiving terminal. Exemplarily, the terminal device supports carrier aggregation (R18 / 19 terminal). The terminal device determines that the target address of any broadcast / multicast service supports carrier aggregation / data splitting, and the terminal device receives data on multiple carriers / frequency bands. Exemplarily, the target address of the broadcast / multicast service is the target address of the broadcast / multicast service that the terminal device is interested in receiving;

[0432] The present disclosure provides a method for SL carrier aggregation backward compatibility, which solves the problem that an old version terminal of R16 / 17 can receive broadcast / multicast services sent by an R18 terminal supporting carrier aggregation in an NR sidelink carrier aggregation scenario, thereby ensuring backward compatibility.

[0433] The embodiments of the present disclosure also propose a device for implementing any of the above methods, for example, a device is proposed, the above device includes a unit or module for implementing each step performed by the first device in any of the above methods. For another example, another device is also proposed, including a unit or module for implementing each step performed by the second device (such as an access network device, a core network function node, a core network device, etc.) in any of the above methods.

[0434] It should be understood that the division of the units or modules in the above device is only a division of logical functions, and in actual implementation, they can be fully or partially integrated into one physical entity, or they can be physically separated. In addition, the units or modules in the device can be implemented in the form of a processor calling software: for example, the device includes a processor, the processor is connected to a memory, and instructions are stored in the memory. The processor calls the instructions stored in the memory to implement any of the above methods or implement the functions of the units or modules of the above device, wherein the processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory inside the device or a memory outside the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits, and the functions of some or all of the units or modules can be realized by designing the hardware circuits. The above hardware circuits can be understood as one or more processors; for example, in one implementation, the above hardware circuit is an application-specific integrated circuit (ASIC), and the functions of some or all of the above units or modules are realized by designing the logical relationship of the components in the circuit; for example, in another implementation, the above hardware circuit can be realized by a programmable logic device (PLD), taking a field programmable gate array (FPGA) as an example, which can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by a configuration file, so as to realize the functions of some or all of the above units or modules. All units or modules of the above devices can be realized in the form of a processor calling software, or in the form of a hardware circuit, or in part by a processor calling software, and the rest by a hardware circuit.

[0435] In the disclosed embodiment, the processor is a circuit with signal processing capability. In one implementation, the processor may be a circuit with instruction reading and running capability, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which may be understood as a microprocessor), or a digital signal processor (DSP), etc.; in another implementation, the processor may realize certain functions through the logical relationship of the hardware circuit, and the logical relationship of the above hardware circuit is fixed or reconfigurable, such as a hardware circuit implemented by a processor as an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the processor loads a configuration document to implement the process of hardware circuit configuration, which may be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. In addition, it may also be a hardware circuit designed for artificial intelligence, which may be understood as an ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), etc.

[0436] FIG6A is a schematic diagram of the structure of the first device proposed in an embodiment of the present disclosure. As shown in FIG6A , the device comprises:

[0437] A sending module, used to send SL data associated with the first target address based on the mapping relationship between the first target address and the carrier and at least one of the first attributes corresponding to the first target address; wherein the first attribute corresponding to the first target address is used to indicate at least one of the following: the version number of the first target address, whether the first target address supports carrier aggregation, whether the first target address supports data diversion, and whether the first target address is backward compatible; wherein the first target address is a target address associated with a broadcast service and / or a multicast service, and the first target address is a target address that the first device is interested in sending and / or receiving.

[0438] Optionally, the sending module is used to execute the steps related to sending executed by the first device 101 in any of the above methods, which are not described in detail here. Optionally, the second device also includes at least one of a receiving module and a processing module, and the receiving module is used to execute the steps related to receiving executed by the first device 101 in any of the above methods, and the processing module is used to execute the steps related to "processing" executed by the first device 101 in any of the above methods, which are not described in detail here.

[0439] FIG6B is a schematic diagram of the structure of the second device proposed in the embodiment of the present disclosure. As shown in FIG6B , it includes:

[0440] A receiving module, used to receive SL data on one or more carriers based on the mapping relationship between the second target address and the carrier and at least one of the first attributes corresponding to the second target address; wherein the first attribute corresponding to the second target address is used to indicate at least one of the following: the version number of the second target address, whether the second target address supports carrier aggregation, whether the second target address supports data offloading, and whether the second target address is backward compatible; the second target address is a target address associated with a broadcast service and / or a multicast service, and the second target address is a target address that the second device is interested in sending and / or receiving.

[0441] Optionally, the receiving module is used to execute the steps related to receiving performed by the second device 102 in any of the above methods, which will not be repeated here. Optionally, the second device also includes at least one of a sending module and a processing module, and the sending module is used to execute the steps related to sending performed by the second device 102 in any of the above methods, and the processing module is used to execute the steps related to "processing" performed by the second device 102 in any of the above methods, which will not be repeated here.

[0442] FIG7A is a schematic diagram of the structure of a communication device 7100 proposed in an embodiment of the present disclosure. The communication device 7100 may be a network device (e.g., an access network device, a core network device, etc.), or a terminal (e.g., a user device, etc.), or a chip, a chip system, or a processor that supports a network device to implement any of the above methods, or a chip, a chip system, or a processor that supports a terminal to implement any of the above methods. The communication device 7100 may be used to implement the method described in the above method embodiment, and the details may refer to the description in the above method embodiment.

[0443] As shown in FIG. 7A , the communication device 7100 includes one or more processors 7101. The processor 7101 may be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit. The baseband processor may be used to process the communication protocol and the communication data, and the central processing unit may be used to control the communication device (such as a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute a program, and process the data of the program. The processor 7101 is used to call instructions so that the communication device 7100 executes any of the above methods.

[0444] In some embodiments, the communication device 7100 further includes one or more memories 7102 for storing instructions. Optionally, all or part of the memory 7102 may also be outside the communication device 7100.

[0445] In some embodiments, the communication device 7100 further includes one or more transceivers 7103. When the communication device 7100 includes one or more transceivers 7103, the communication steps such as sending and receiving in the above method are executed by the transceiver 7103, and the other steps are executed by the processor 7101.

[0446] In some embodiments, the transceiver may include a receiver and a transmitter, and the receiver and the transmitter may be separate or integrated. Optionally, the terms such as transceiver, transceiver unit, transceiver, transceiver circuit, etc. may be replaced with each other, the terms such as transmitter, transmission unit, transmitter, transmission circuit, etc. may be replaced with each other, and the terms such as receiver, receiving unit, receiver, receiving circuit, etc. may be replaced with each other.

[0447] Optionally, the communication device 7100 further includes one or more interface circuits 7104, which are connected to the memory 7102. The interface circuit 7104 can be used to receive signals from the memory 7102 or other devices, and can be used to send signals to the memory 7102 or other devices. For example, the interface circuit 7104 can read instructions stored in the memory 7102 and send the instructions to the processor 7101.

[0448] The communication device 7100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 7100 described in the present disclosure is not limited thereto, and the structure of the communication device 7100 may not be limited by FIG. 7a. The communication device may be an independent device or may be part of a larger device. For example, the communication device may be: 1) an independent integrated circuit IC, or a chip, or a chip system or subsystem; (2) a collection of one or more ICs, optionally, the above IC collection may also include a storage component for storing data and programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, a terminal device, an intelligent terminal device, a cellular phone, a wireless device, a handheld device, a mobile unit, a vehicle-mounted device, a network device, a cloud device, an artificial intelligence device, etc.; (6) others, etc.

[0449] 7B is a schematic diagram of the structure of a chip 7200 provided in an embodiment of the present disclosure. In the case where the communication device 7100 may be a chip or a chip system, reference may be made to the schematic diagram of the structure of the chip 7200 shown in FIG. 7B , but the present disclosure is not limited thereto.

[0450] The chip 7200 includes one or more processors 7201, and the processor 7201 is used to call instructions so that the chip 7200 executes any of the above methods.

[0451] In some embodiments, the chip 7200 further includes one or more interface circuits 7202, which are connected to the memory 7203. The interface circuit 7202 can be used to receive signals from the memory 7203 or other devices, and the interface circuit 7202 can be used to send signals to the memory 7203 or other devices. For example, the interface circuit 7202 can read instructions stored in the memory 7203 and send the instructions to the processor 7201. Optionally, the terms such as interface circuit, interface, transceiver pin, and transceiver can be replaced with each other.

[0452] In some embodiments, the chip 7200 further includes one or more memories 7203 for storing instructions. Optionally, all or part of the memory 7203 may be outside the chip 7200.

[0453] The present disclosure also proposes a storage medium, on which instructions are stored, and when the instructions are executed on the communication device 7100, the communication device 7100 executes any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but is not limited to this, and it can also be a storage medium readable by other devices. Optionally, the storage medium can be a non-transitory storage medium, but is not limited to this, and it can also be a temporary storage medium.

[0454] The present disclosure also proposes a program product, which, when executed by the communication device 7100, enables the communication device 7100 to execute any of the above methods. Optionally, the program product is a computer program product.

[0455] The present disclosure also proposes a computer program, which, when executed on a computer, causes the computer to execute any one of the above methods.

[0456] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented by software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer programs. When the computer program is loaded and executed on a computer, the process or function described in the embodiment of the present disclosure is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer program can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer program can be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a high-density digital video disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

[0457] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this disclosure.

[0458] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0459] The above is only a specific embodiment of the present disclosure, but the protection scope of the present disclosure is not limited thereto. Any person skilled in the art who is familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present disclosure, which should be included in the protection scope of the present disclosure. Therefore, the protection scope of the present disclosure should be based on the protection scope of the claims.

Claims

A communication method, characterized in that: The method includes: the first device sends the side link SL data associated with the first target address based on the mapping relationship between the first target address and the carrier and at least one of the first attributes corresponding to the first target address; wherein the first attribute corresponding to the first target address is used to indicate at least one of the following: the version number of the first target address, whether the first target address supports carrier aggregation, whether the first target address supports data offloading, and whether the first target address is backward compatible; wherein the first target address is a target address associated with a broadcast service and / or a multicast service, and the first target address is a target address that the first device is interested in sending and / or receiving. The method according to claim 1, characterized in that The method further includes: the first device determining a first attribute corresponding to at least one first target address. The method according to claim 1 or 2, characterized in that The first attribute is configured according to the service granularity; wherein, one first service corresponds to one first attribute, and the first target address is associated with at least one first service; the first service includes a broadcast service and / or a multicast service; or the first attribute is configured according to the target address granularity; wherein, the first target address corresponds to one first attribute. The method according to claim 2 or 3, characterized in that The determining of the first attribute corresponding to at least one first target address includes: configuring the first attribute according to the service granularity, and determining the first attribute corresponding to the first target address based on the first attribute corresponding to at least one first service associated with the first target address. The method according to claim 4, characterized in that The first attribute corresponding to the first target address is determined based on the first attribute corresponding to at least one first service associated with the first target address, including: the first attributes corresponding to all first services associated with the first target address indicate at least one of the following: the version number is the target version number, carrier aggregation is supported, data diversion is supported, and there is no backward compatibility; the first attribute corresponding to the first target address is determined to be at least one of the following: the version number of the first target address is the target version number, the first target address supports carrier aggregation, the first target address supports data diversion, and the first target address is not backward compatible. The method according to any one of claims 1 to 5, characterized in that: The method also includes: the first target address does not have a corresponding first attribute, and determining at least one of the following: the version number of the first target address is not the target version number, the first target address does not support carrier aggregation, the first target address does not support data diversion, and the first target address is backward compatible. The method according to any one of claims 1 to 6, characterized in that: The method of sending the SL data associated with the first target address based on the mapping relationship between the first target address and the carrier and at least one of the first attributes corresponding to the first target address includes: the mapping relationship between the first target address and the carrier is: the first target address is mapped to multiple carriers; and / or the first attribute corresponding to the first target address indicates at least one of the following: the version number of the first target address is the target version number, the first target address supports carrier aggregation, the first target address supports data diversion, and the first target address is not backward compatible; and the SL data associated with the first target address is sent through multi-carrier diversion and / or packet data convergence protocol PDCP multiplexing duplication. The method according to any one of claims 1 to 6, characterized in that: The SL data associated with the first target address is sent based on the mapping relationship between the first target address and the carrier and at least one of the first attributes corresponding to the first target address, including: the mapping relationship between the first target address and the carrier is: the first target address is mapped to multiple carriers; and / or the first attribute corresponding to the first target address indicates at least one of the following: the version number of the first target address is not the target version number, the first target address does not support carrier aggregation, the first target address does not support data offloading, and the first target address is backward compatible; and the SL data associated with the first target address is sent via a single carrier and / or PDCP multiplexing. The method according to any one of claims 1 to 6, characterized in that: The sending of SL data associated with the first target address based on the mapping relationship between the first target address and the carrier and at least one of the first attributes corresponding to the first target address includes: the mapping relationship between the first target address and the carrier is: the first target address is mapped to one carrier; and / or the first attribute corresponding to the first target address indicates at least one of the following: the version number of the first target address is the target version number, the first target address supports carrier aggregation, the first target address supports data diversion, and the first target address is not backward compatible; and the sending of SL data associated with the first target address via a single carrier. The method according to any one of claims 1 to 6, characterized in that: The sending of SL data associated with the first target address based on the mapping relationship between the first target address and the carrier and at least one of the first attributes corresponding to the first target address includes: the mapping relationship between the first target address and the carrier is: the first target address is mapped to one carrier; and / or the first attribute corresponding to the first target address indicates at least one of the following: the version number of the first target address is not the target version number, the first target address does not support carrier aggregation, the first target address does not support data diversion, and the first target address is backward compatible; and the sending of SL data associated with the first target address via a single carrier. The method according to claim 7, characterized in that The sending of SL data associated with the first target address through PDCP multiplexing includes: sending SL data associated with a first SLRB through PDCP multiplexing; wherein, the first SLRB is an SLRB associated with the first target address and with PDCP multiplexing activated, and the first SLRB is one or more. The method according to claim 11, characterized in that The sending of the SL data associated with the first SLRB through PDCP multiplexing includes: selecting two carriers from the multiple carriers mapped to the first target address to respectively send the same SL data associated with the first SLRB. The method according to claim 12, characterized in that The selecting two carriers from the multiple carriers mapped to the first target address to respectively send the same SL data associated with the first SLRB includes: arbitrarily selecting two carriers from the multiple carriers mapped to the first target address to respectively send the same SL data associated with the first SLRB. The method according to claim 7, characterized in that The sending of SL data associated with the first target address through multi-carrier splitting includes: sending SL data associated with the second SLRB through the multiple carrier splitting mapped to the first target address; wherein, the second SLRB is the SLRB associated with the first target address and deactivated PDCP multiplexing, and the second SLRB is one or more. The method according to claim 14, characterized in that The sending of SL data associated with the second SLRB through multi-carrier splitting includes: sending different SL data associated with the second SLRB on multiple carriers mapped to the first target address. The method according to claim 8, characterized in that The sending of SL data associated with the first target address through PDCP multiplexing includes: sending SL data associated with a first SLRB through PDCP multiplexing; wherein, the first SLRB is an SLRB associated with the first target address and with PDCP multiplexing activated, and the first SLRB is one or more. The method according to claim 16, characterized in that The sending of the SL data associated with the first SLRB through PDCP multiplexing includes: selecting two carriers from the multiple carriers mapped to the first target address to respectively send the same SL data associated with the first SLRB. The method according to claim 17, characterized in that The selecting two carriers from the multiple carriers mapped to the first target address to respectively send the same SL data associated with the first SLRB includes: selecting an existing carrier that can achieve backward compatibility and any other carrier from the multiple carriers mapped to the first target address to respectively send the same SL data associated with the first SLRB. The method according to claim 8, characterized in that The sending of SL data associated with the first target address through a single carrier includes: sending SL data associated with a second SLRB through an existing carrier that can achieve backward compatibility; wherein, the second SLRB is an SLRB associated with the first target address and with deactivated PDCP multiplexing, and the second SLRB is one or more. The method according to claim 9 or 10, characterized in that The sending the SL data associated with the first target address through a single carrier includes: sending the SL data associated with the first target address through an existing carrier that can achieve backward compatibility. The method according to any one of claims 11 to 19, characterized in that: The method also includes: determining the SLRB configurations corresponding to at least one first SLRB and / or at least one second SLRB respectively, the SLRB configurations corresponding to the at least one first SLRB and / or at least one second SLRB respectively being used to configure whether PDCP multiplexing is activated for the at least one first SLRB and / or at least one second SLRB; and determining whether PDCP multiplexing is activated for the at least one first SLRB and / or at least one second SLRB associated with the first target address according to the SLRB configurations corresponding to the at least one first SLRB and / or at least one second SLRB respectively. The method according to claim 21, characterized in that The determination of the SLRB configurations corresponding to at least one first SLRB and / or at least one second SLRB respectively includes at least one of the following: obtaining the SLRB configurations corresponding to the at least one first SLRB and / or at least one second SLRB respectively sent through dedicated signaling; obtaining the SLRB configurations corresponding to the at least one first SLRB and / or at least one second SLRB respectively sent through the system information block SIB; obtaining the pre-configured SLRB configurations corresponding to the at least one first SLRB and / or at least one second SLRB respectively. The method according to any one of claims 1 to 22, characterized in that: The method further includes: determining a mapping relationship between the first target address and the carrier based on a high-level configuration. The method according to any one of claims 1 to 23, characterized in that: For the first target address, the first device and the second device are configured with the same first attribute; wherein the first device is a sending terminal of the first target address, and the second device is a receiving terminal of the first target address. The method according to any one of claims 7 to 24, characterized in that: The target version number is R18. A communication method, characterized in that: The method includes: the second device receives SL data on one or more carriers based on the mapping relationship between the second target address and the carrier and at least one of the first attributes corresponding to the second target address; wherein the first attribute corresponding to the second target address is used to indicate at least one of the following: the version number of the second target address, whether the second target address supports carrier aggregation, whether the second target address supports data offloading, and whether the second target address is backward compatible; the second target address is a target address associated with a broadcast service and / or a multicast service, and the second target address is a target address that the second device is interested in sending and / or receiving. The method according to claim 26, characterized in that The method further includes: the second device determining a first attribute corresponding to at least one second target address. The method according to claim 26 or 27, characterized in that The first attribute is configured according to the service granularity; wherein, one second service corresponds to one first attribute, and the second target address is associated with at least one second service; the second service includes a broadcast service and / or a multicast service; or the first attribute is configured according to the target address granularity; wherein, the second target address corresponds to one first attribute. The method according to claim 27 or 28, characterized in that The determining of the first attribute corresponding to at least one second target address includes: configuring the first attribute according to the service granularity, and determining the first attribute corresponding to the second target address based on the first attribute corresponding to at least one second service associated with the second target address. The method of claim 29, wherein: The method of determining the first attribute corresponding to the second target address based on the first attribute corresponding to at least one second service associated with the second target address includes: the first attributes corresponding to all second services associated with the second target address indicate at least one of the following: the version number is the target version number, carrier aggregation is supported, data offloading is supported, and there is no backward compatibility; determining that the first attribute corresponding to the second target address is at least one of the following: the version number of the second target address is the target version number, the second target address supports carrier aggregation, the second target address supports data offloading, and the second target address is not backward compatible. The method according to any one of claims 26 to 30, characterized in that: The method also includes: the second target address does not have a corresponding first attribute, and determining at least one of the following: the version number of the second target address is not the target version number, the second target address does not support carrier aggregation, the second target address does not support data diversion, and the second target address is backward compatible. The method according to any one of claims 26 to 31, characterized in that: The receiving of SL data on one or more carriers based on the mapping relationship between the second target address and the carrier and at least one of the first attributes corresponding to the second target address includes: at least one second target address satisfies a first preset condition, and the SL data associated with the at least one second target address is received through multiple carriers; wherein the first preset condition includes: the mapping relationship between the second target address and the carrier is: the second target address is mapped to multiple carriers; and / or the first attribute corresponding to the second target address indicates at least one of the following: the version number of the second target address is the target version number, the second target address supports carrier aggregation, the second target address supports data diversion, and the second target address is not backward compatible. The method according to any one of claims 26 to 31, characterized in that: The receiving of SL data on one or more carriers based on the mapping relationship between the second target address and the carrier and at least one of the first attributes corresponding to the second target address includes: all second target addresses satisfy the second preset condition, and the SL data associated with the at least one second target address is received through an existing carrier that can achieve backward compatibility; wherein the second preset condition includes: the mapping relationship between the second target address and the carrier is: the second target address is mapped to one carrier; and / or, the first attribute corresponding to the second target address indicates at least one of the following: the version number of the second target address is not the target version number, the second target address does not support carrier aggregation, the second target address does not support data diversion, and the second target address is backward compatible; and / or, the second preset condition includes: the mapping relationship between the second target address and the carrier is: the second target address is mapped to multiple carriers; and / or, the first attribute corresponding to the second target address indicates at least one of the following: the version number of the second target address is not the target version number, the second target address does not support carrier aggregation, the second target address does not support data diversion, and the second target address is backward compatible. The method according to any one of claims 26 to 33, characterized in that: For the second target address, the first device and the second device are configured with the same first attribute; wherein the first device is a sending terminal of the second target address, and the second device is a receiving terminal of the second target address. A communication method, characterized in that: Used in a communication system, the communication system includes a first device and a second device, the method includes at least one of the following: the first device sends SL data associated with the first target address based on a mapping relationship between the first target address and the carrier and at least one of the first attributes corresponding to the first target address; wherein the first attribute corresponding to the first target address is used to indicate at least one of the following: the version number of the first target address, whether the first target address supports carrier aggregation, whether the first target address supports data offloading, and whether the first target address is backward compatible; wherein the first target address is a target address associated with a broadcast service and / or a multicast service, and the first target address is a target address that the first device is interested in sending and / or receiving address; the second device receives SL data on one or more carriers based on the mapping relationship between the second target address and the carrier and at least one of the first attributes corresponding to the second target address; wherein the first attribute corresponding to the second target address is used to indicate at least one of the following: the version number of the second target address, whether the second target address supports carrier aggregation, whether the second target address supports data offloading, and whether the second target address is backward compatible; the second target address is a target address associated with a broadcast service and / or a multicast service, the second target address is a target address that the second device is interested in sending and / or receiving, and the at least one second target address is part or all of the target addresses in the at least one first target address. A first device includes: A sending module, used to send SL data associated with the first target address based on the mapping relationship between the first target address and the carrier and at least one of the first attributes corresponding to the first target address; wherein the first attribute corresponding to the first target address is used to indicate at least one of the following: the version number of the first target address, whether the first target address supports carrier aggregation, whether the first target address supports data diversion, and whether the first target address is backward compatible; wherein the first target address is a target address associated with a broadcast service and / or a multicast service, and the first target address is a target address that the first device is interested in sending and / or receiving. A second device, comprising: A receiving module, used to receive SL data on one or more carriers based on the mapping relationship between the second target address and the carrier and at least one of the first attributes corresponding to the second target address; wherein the first attribute corresponding to the second target address is used to indicate at least one of the following: the version number of the second target address, whether the second target address supports carrier aggregation, whether the second target address supports data offloading, and whether the second target address is backward compatible; the second target address is a target address associated with a broadcast service and / or a multicast service, and the second target address is a target address that the second device is interested in sending and / or receiving. A communication device, characterized in that: include: One or more processors; wherein the processor is used to call instructions so that the communication device executes the communication method described in any one of claims 1-25 and 26-34. A communication system, characterized in that: The invention comprises a first device and a second device, wherein the first device is configured to implement the communication method according to any one of claims 1 to 25, and the second device is configured to implement the communication method according to any one of claims 26 to 34. A storage medium stores instructions, characterized in that: When the instruction is executed on a communication device, the communication device is caused to execute the communication method according to any one of claims 1-25 and 26-34.

Images