[go: up one dir, main page]

WO2025035230A1 - 通信方法及装置、通信设备、通信系统、存储介质 - Google Patents

通信方法及装置、通信设备、通信系统、存储介质 Download PDF

Info

Publication number
WO2025035230A1
WO2025035230A1 PCT/CN2023/112426 CN2023112426W WO2025035230A1 WO 2025035230 A1 WO2025035230 A1 WO 2025035230A1 CN 2023112426 W CN2023112426 W CN 2023112426W WO 2025035230 A1 WO2025035230 A1 WO 2025035230A1
Authority
WO
WIPO (PCT)
Prior art keywords
target address
slrb
carrier
target
data
Prior art date
Application number
PCT/CN2023/112426
Other languages
English (en)
French (fr)
Inventor
赵力
Original Assignee
北京小米移动软件有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 北京小米移动软件有限公司 filed Critical 北京小米移动软件有限公司
Priority to PCT/CN2023/112426 priority Critical patent/WO2025035230A1/zh
Publication of WO2025035230A1 publication Critical patent/WO2025035230A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/40—Resource management for direct mode communication, e.g. D2D or sidelink

Definitions

  • 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.
  • the uplink and downlink transmission rates are improved by introducing carrier aggregation (CA) technology.
  • CA carrier aggregation
  • SL carrier aggregation technology is also introduced in the sidelink (SL) communication.
  • the present disclosure provides a communication method and apparatus, a communication device, a communication system, and a storage medium.
  • a communication method including:
  • 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.
  • a communication method including:
  • 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.
  • a communication method 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:
  • 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;
  • 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.
  • a first device including:
  • 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 including:
  • 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 including:
  • 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.
  • a communication system 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.
  • a storage medium stores instructions, and wherein 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.
  • FIG1 is a schematic diagram of the architecture of some communication systems provided by embodiments of the present disclosure.
  • 2A-2D are interactive schematic diagrams of a communication method provided by an embodiment of the present disclosure.
  • 3A-3E are flowchart diagrams of a communication method provided in yet another embodiment of the present disclosure.
  • 4A-4C are flowchart diagrams of a communication method provided in yet another embodiment of the present disclosure.
  • FIG5 is a flow chart of a communication method provided by yet another embodiment of the present disclosure.
  • FIG6A is a schematic diagram of the structure of a first device provided by an embodiment of the present disclosure.
  • FIG6B is a schematic diagram of the structure of a second device provided by an embodiment of the present disclosure.
  • FIG7A is a schematic diagram of the structure of a communication device provided by an embodiment of the present disclosure.
  • FIG. 7B is a schematic diagram of the structure of a chip provided by an embodiment of the present disclosure.
  • the embodiments of the present disclosure provide a communication method and apparatus, a communication device, a communication system, and a storage medium.
  • an embodiment of the present disclosure provides a communication method, which is performed by a first device, and the method includes:
  • 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.
  • the first device 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.
  • 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.
  • the first device 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).
  • 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.
  • the method further includes:
  • the first device determines a first attribute corresponding to at least one first target address.
  • 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
  • the first attribute is configured according to the target address granularity; wherein the first target address corresponds to one first attribute.
  • 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.
  • the determining of the first attribute corresponding to the at least one first target address respectively comprises: include:
  • 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.
  • 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:
  • 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.
  • 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.
  • the method further includes:
  • 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
  • the first target address is backward compatible.
  • a method 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).
  • 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.
  • 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:
  • 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.
  • 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:
  • 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.
  • 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:
  • 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.
  • 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:
  • 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.
  • a first device provides a method for determining a mapping relationship between a first target address and a carrier and/or a first target address.
  • 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 backward compatibility is successfully achieved for the second device, thereby ensuring the stability of SL communication.
  • sending the SL data associated with the first target address through PDCP multiplexing includes:
  • 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.
  • sending the SL data associated with the first SLRB through PDCP multiplexing includes:
  • 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:
  • sending the SL data associated with the first target address through multi-carrier offloading includes:
  • 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.
  • sending SL data associated with the second SLRB through multi-carrier splitting includes:
  • Different SL data associated with the second SLRB are sent on multiple carriers mapped to the first target address.
  • sending the SL data associated with the first target address through PDCP multiplexing includes:
  • 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.
  • sending the SL data associated with the first SLRB through PDCP multiplexing includes:
  • 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:
  • 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.
  • sending the SL data associated with the first target address through a single carrier includes:
  • the SL data associated with the second SLRB is sent 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.
  • sending the SL data associated with the first target address through a single carrier includes:
  • the SL data associated with the first target address is sent via an existing carrier that can achieve backward compatibility.
  • a method for how the first device specifically sends SL data is provided, which is used for the first device to successfully send SL data to the second device, ensure the successful transmission of SL data, and ensure the stability of SL transmission.
  • some SLRBs such as the first SLRB mentioned above
  • the first device will also send the SL data associated with the SLRB through PDCP multiplexing, thereby improving the reliability of SL data and reducing the delay of repeated transmission, meeting the requirements of ultra-reliable and low-latency communication.
  • Low Latency Communication, URLLC Low Latency Communication
  • the method further includes:
  • 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;
  • 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:
  • 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.
  • the method further includes:
  • a mapping relationship between the first target address and the carrier is determined based on a high-level configuration.
  • a method 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).
  • 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.
  • 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 first device i.e., the sending terminal of the first target address
  • the second device i.e., the receiving terminal of the first target address
  • the first device and the second device 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.
  • the target version number is R18.
  • an embodiment of the present disclosure provides a communication method, which is performed by a second device and 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 second device when the second device receives the SL data associated with the second target address, it receives it 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.
  • 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.
  • the second device 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 "the mapping relationship between the target address and the carrier" and "whether the second target address is backward compatible". This can ensure that the second device finally receives the SL data associated with the second target address in a manner that matches the second. If the receiving capability of the device is sufficient, when the second device is a terminal with limited capability (such as an old version terminal, for example, an R16/17 terminal), backward compatibility with the second device can be ensured, thereby ensuring the stability of SL communication.
  • the method further includes:
  • the second device determines a first attribute corresponding to at least one second target address.
  • 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.
  • determining the first attribute corresponding to at least one second target address includes:
  • 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.
  • 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. 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.
  • the method further includes:
  • 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
  • the second target address is backward compatible.
  • 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:
  • 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.
  • 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:
  • 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 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.
  • 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:
  • the first device sends 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; 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 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.
  • an embodiment of the present disclosure provides a first device, including:
  • 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.
  • the first device is further used for:
  • a first attribute corresponding to at least one first target address is determined.
  • 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 first device is further used for:
  • 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.
  • the first device is further used for:
  • 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.
  • the first device is further used for:
  • 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
  • the first target address is backward compatible.
  • the sending module is further used to:
  • 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.
  • the sending module is further used to:
  • 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.
  • the sending module is further used to:
  • 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 Supporting carrier aggregation, the first target address supports data diversion, and the first target address is not backward compatible; and sending SL data associated with the first target address through a single carrier.
  • the sending module is further used to:
  • 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.
  • the sending module is further used to:
  • 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.
  • the sending module is further used to:
  • the sending module is further used to:
  • the sending module is further used to:
  • 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.
  • the sending module is further used to:
  • Different SL data associated with the second SLRB are sent on multiple carriers mapped to the first target address.
  • the sending module is further used to:
  • 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.
  • the sending module is further used to:
  • the sending module is further used to:
  • 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.
  • the sending module is further used to:
  • 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.
  • the sending module is further used to:
  • the SL data associated with the first target address is sent via an existing carrier that can achieve backward compatibility.
  • the device is further used for:
  • 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;
  • the device is further used for:
  • the device is further used for:
  • a mapping relationship between the first target address and the carrier is determined based on a high-level configuration.
  • 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 target version number is R18.
  • the present disclosure provides a second device, including:
  • 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.
  • the second device is further used for:
  • a first attribute corresponding to each of the at least one second target address is determined.
  • 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 second device is further used for:
  • 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.
  • the second device is further used for:
  • 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.
  • the second device is further used for:
  • 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
  • the second target address is backward compatible.
  • the receiving module is further used for:
  • 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.
  • the receiving module is further used for:
  • 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 first device and the second device are configured similarly.
  • the same first attribute wherein the first device is the sending terminal of the second target address, and the second device is the receiving terminal of the second target address.
  • 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.
  • 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.
  • an embodiment of the present disclosure proposes a storage medium, wherein the storage medium stores instructions.
  • 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.
  • an embodiment of the present disclosure proposes a program product.
  • 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.
  • 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.
  • 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.
  • the present disclosure proposes the title of the invention.
  • 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.
  • each step in a certain embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined.
  • 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.
  • 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.
  • 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.
  • the noun after the article may be understood as a singular expression or a plural expression.
  • plurality refers to two or more.
  • the terms “at least one of”, “at least one of”, “at least one of”, “one or more”, “a plurality of”, “multiple”, etc. can be used interchangeably.
  • 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.
  • 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.
  • branches such as A, B, C, etc., it is similar to the above.
  • prefixes such as “first” and “second” in the embodiments of the present disclosure are only used to distinguish different description objects, and do not limit the position, order, priority, quantity or content of the description objects.
  • the description objects please refer to the description in the context of the claims or embodiments.
  • the use of prefixes constitutes redundant restrictions. For example, if the description object is "field”, the ordinal number before “field” in “first field” and “second field” does not limit the position or order between "fields”, “first” and “second” do not limit whether the "fields” they modify are in the same message, nor do they limit the order of "first field” and "second field”.
  • the description object is "level”
  • the ordinal number before “level” in “first level” and “second level” does not limit the priority between “levels”.
  • the number of description objects is not limited by ordinal numbers and can be one or more. Take “first device” as an example, where the number of "devices" can be one or more.
  • the objects modified by different prefixes can be the same or different. For example, if the description object is “device”, “first device” and “second device” can be the same device or different devices, and their types can be the same or different; for another example, if the description object is "information”, “first information” and “second information” can be the same information or different information, and their contents can be the same or different.
  • “including A”, “comprising A”, “used to indicate A”, and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.
  • 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.
  • 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.
  • network may be interpreted as devices included in the network (eg, access network equipment, core network equipment, etc.).
  • terminal 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 can be used interchangeably.
  • the access network device, the core network device, or the network device can be replaced by a terminal.
  • 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.).
  • D2D device-to-device
  • V2X vehicle-to-everything
  • the language such as "uplink” and "downlink” can also be replaced by the language corresponding to the communication between the terminals (for example, "side”).
  • the uplink channel, the downlink channel, etc. can be replaced by the side channel
  • the uplink, the downlink, etc. can be replaced by the side link.
  • the terminal may be replaced by an access network device, a core network device, or a network device.
  • 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.
  • acquisition of data, information, etc. may comply with the laws and regulations of the country where the data is obtained.
  • data, information, etc. may be obtained with the user's consent.
  • each element, each row, or each column in the table of the embodiment of the present disclosure can be implemented as an independent embodiment. Any combination of pixels, any rows, and any columns can also be implemented as independent embodiments.
  • 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.
  • the corresponding relationships shown in some rows may not be configured.
  • 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.
  • 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.
  • the predefined in the present disclosure may be understood as defined, predefined, stored, pre-stored, pre-negotiated, pre-configured, solidified, or pre-burned.
  • 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 the URLLC (high reliability and low latency) requirements.
  • the terminal will transmit a PDCP data packet to a radio link control (Radio Link Control, RLC) entity of the terminal, and the RLC entity will process it and then send it to the terminal's media access control (Medium Access Control, MAC) layer.
  • RLC Radio Link Control
  • MAC Media Access Control
  • the MAC layer completes the data scheduling to send the PDCP data packet to another terminal.
  • the terminal will transmit a PDCP data packet to the 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.
  • FIG1 is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure.
  • 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.
  • SL communication may be performed between the first device and the second device.
  • the network device may include at least one of an access network device and a core network device.
  • 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 (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 (smart grid), a wireless terminal device in transportation safety (transportation safety), a wireless terminal device in a smart city (smart city), and at least one of a wireless terminal device in a smart home (smart home), but is not limited to these.
  • 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
  • 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 Node B (eNB), a next generation evolved Node B (ng-eNB), a next generation Node B (gNB), a node B (NB), a home node B (HNB), a home evolved node B (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.
  • eNB evolved Node B
  • ng-eNB next generation evolved Node B
  • gNB next generation Node B
  • the technical solution of the present disclosure may be applicable to the Open RAN architecture.
  • the interfaces between access network devices or within access network devices involved in the embodiments of the present disclosure may become internal interfaces of Open RAN, and the processes and information interactions between these internal interfaces may be implemented through software or programs.
  • the access network device may be composed of a centralized unit (CU) and a distributed unit (DU), wherein the CU may also be referred to as a control unit.
  • the CU-DU structure may be used to separate the protocol layer of the access network device, with some functions of the protocol layer being centrally controlled by the CU, and the remaining functions of some or all of the protocol layers being distributed in the DU, which is centrally controlled by the CU. Control DU, but not limited to it.
  • 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).
  • EPC Evolved Packet Core
  • 5GCN 5G Core Network
  • NGC Next Generation Core
  • the core network device may also be a location management function network element.
  • the location management function network element includes a location server (location server), which may be implemented as any one of the following: a location management function (LMF), an Enhanced Serving Mobile Location Centre (E-SMLC), a Secure User Plane Location (SUPL), and a Secure User Plane Location Platform (SUPLLP).
  • LMF location management function
  • E-SMLC Enhanced Serving Mobile Location Centre
  • SUPL Secure User Plane Location
  • SUPLLP Secure User Plane Location Platform
  • 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.
  • 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.
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • LTE-B LTE-Beyond
  • SUPER 3G IMT-Advanced
  • 4G 4th generation mobile communication system
  • 5G 5th generation mobile communication system
  • 5G new radio NR
  • Future Radio Access FX
  • RAT New-Radio Access Technology
  • NR New Radio
  • NX New radio access
  • FX Future generation radio access
  • GSM Global System for Mobile communications
  • CDMA2000 Code Division Multiple Access 2000
  • UMB Ultra Mobile Broadband
  • IEEE 802.11 Wi-Fi (registered trademark)
  • IEEE 802.16 WiMAX (registered trademark)
  • IEEE 802.20 Ultra-WideBand (UWB)
  • Bluetooth registered trademark
  • PLMN Public Land Mobile Network
  • D2D Device to Device
  • M2M Machine to Machine to Machine
  • IoT Internet of Things
  • V2X Vehicle to-Everything
  • system using other communication methods for example, combination of LTE or LTE-A and 5G, etc.
  • a capability-limited terminal e.g., an old version terminal, such as an R16/17 terminal
  • a capability-limited 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.
  • an optional method is: the sending terminal achieves backward compatibility based on the mapping of high-level configured services to carriers/frequency bands.
  • 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.
  • 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.
  • 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.
  • the carrier/frequency band i.e., the carrier/frequency band of R16/1
  • 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.
  • the capability-limited terminal 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.
  • 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:
  • Step 2101 The first device determines a first attribute corresponding to at least one first target address.
  • the first target address may be, for example, a first target layer 2 address.
  • 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.
  • the first destination address may be 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.
  • 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.
  • the first destination address may also be 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.
  • 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.
  • the first attribute may be a transmission attribute (Tx profile), which 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.
  • Tx profile transmission attribute
  • the first attribute corresponding to the first target address is essentially used to indicate whether the first target address is compatible with an existing R16/17 terminal device, that is, to indicate whether the existing R16/17 terminal device is a receiving terminal of the first target address.
  • 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 a 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 an existing R16/17 terminal device, that is, the existing R16/17 terminal device is not a receiving terminal of the first target address.
  • the receiving terminal of the first target address is considered to be a terminal that supports carrier aggregation (for example, an R18 or R19 terminal).
  • 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.
  • 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).
  • the content indicated by the first attribute may have other naming forms, which are not specifically limited in the present disclosure.
  • the above-mentioned “carrier” may also be called “frequency band” or other names, which are not specifically limited in the present disclosure.
  • 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.
  • 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.
  • 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.
  • V2X vehicle-to-everything
  • the high-level layer of the first device indicates the configured first attribute to the access stratum (AS) layer.
  • 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.
  • one first service corresponds to one first attribute
  • the first attributes corresponding to different first services may be the same or different
  • one first target address may be associated with at least one first service.
  • 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.
  • 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.
  • 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.
  • 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.
  • the first target address may correspond to one first attribute.
  • the first attribute 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.
  • the first attribute may not be configured for the first target address.
  • 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.
  • 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.
  • Step 2102 The first device determines a mapping relationship between a first target address and a carrier based on a high-level configuration.
  • the high layer may configure the relationship between the service and the target address and/or the relationship between the service and the carrier
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • PDCP Packet Data Convergence Protocol
  • the first target address 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.
  • 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.
  • the first target address may be associated with at least one sidelink radio bearer (SLRB).
  • SLRB sidelink radio bearer
  • 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.
  • the SLRB may be used to transmit the SL data associated with the SLRB.
  • At least one SLRB associated with the first target address corresponds to an SLRB configuration
  • 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 can be sent to the first device by a network device through dedicated signaling; or, the SLRB configuration can be sent to the first device by a network device through a system information block (System Information Blocks, SIB), or, the SLRB configuration can be pre-configured.
  • SIB System Information Blocks
  • the first device in a Radio Resource Control (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
  • the first device in out of coverage (out of coverage, OOC) can obtain the SLRB configuration through pre-configuration.
  • 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
  • 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.
  • the first device may send the SL data associated with the first SLRB through PDCP multiplexing.
  • 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.
  • 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.
  • 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.
  • 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.
  • CBR channel busy ratio
  • the first device may send SL data A associated with the first SLRB on both carriers 1 and 2.
  • the first device may send the SL data associated with the second SLRB through multi-carrier splitting.
  • 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.
  • the communication method involved in the embodiment of the present disclosure may include at least one of steps S2101 to S2103.
  • 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
  • steps S2101+S2102 may be implemented as an independent embodiment, but are not limited thereto.
  • 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.
  • 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:
  • Step 2201 The first device determines a first attribute corresponding to at least one first target address.
  • Step 2202 The first device determines a mapping relationship between a first target address and a carrier based on a high-level configuration.
  • steps 2201 - 2202 please refer to the above embodiment description.
  • 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.
  • the first target address 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.
  • the first device may send the first SLRB associated with the first SLRB through PDCP multiplexing. SL data.
  • 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.
  • the first device may select an existing carrier (such as a legacy carrier, that is, a legacy carrier supported by the R16/17 terminal) 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.
  • the other carrier may be a carrier other than the existing carrier that may be backward compatible.
  • 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.
  • the first device may select a carrier with the lowest CBR from the multiple carriers other than the existing carrier.
  • 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.
  • 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.
  • 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.
  • an existing LCID for example, 4-19
  • the other PDCP data packet can be associated with a reserved LCID to be sent through the reserved logical channel.
  • the first device 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.
  • an existing carrier such as a legacy carrier, that is, a legacy carrier supported by R16/17 terminals
  • the first device may send SL data associated with the second SLRB through an existing carrier that can achieve backward compatibility.
  • steps 2202 - 2203 please refer to the above embodiment description.
  • the communication method involved in the embodiment of the present disclosure may include at least one of steps S2201 to S2203.
  • 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
  • steps S2201+S2202 may be implemented as an independent embodiment, but are not limited thereto.
  • 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.
  • 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:
  • Step 2301 The first device determines a first attribute corresponding to at least one first target address.
  • Step 2302 The first device determines a mapping relationship between a first target address and a carrier based on a high-level configuration.
  • 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.
  • 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).
  • the first target address is not backward compatible
  • 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).
  • steps 2301 - 2303 please refer to the above embodiment description.
  • the communication method involved in the embodiment of the present disclosure may include at least one of step S2301 to step S2303.
  • 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.
  • steps S2301+S2302 can be implemented as independent embodiments, but are not limited thereto.
  • 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.
  • FIG2D is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure.
  • the embodiment of the present disclosure relates to a communication method, which is used in a communication system 100, and the method includes:
  • Step 2401 The first device determines a first attribute corresponding to at least one first target address.
  • Step 2402 The first device determines a mapping relationship between a first target address and a carrier based on a high-level configuration.
  • 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.
  • 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).
  • the first device can send the SL data associated with the first target address through a single carrier.
  • 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).
  • steps 2401 - 2403 please refer to the above embodiment description.
  • the communication method involved in the embodiment of the present disclosure may include at least one of steps S2401 to S2403.
  • 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
  • steps S2401+S2402 may be implemented as an independent embodiment, but are not limited thereto.
  • 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.
  • 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:
  • Step 3101 The first device determines a first attribute corresponding to at least one first target address.
  • Step 3102 The first device determines a mapping relationship between a first target address and a carrier based on a high-level configuration.
  • 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.
  • steps 3101 - 3103 please refer to the above embodiment description.
  • the communication method involved in the embodiment of the present disclosure may include at least one of steps S3101 to S3103.
  • step S3101 may be implemented as an independent embodiment
  • step S3102 may be implemented as an independent embodiment
  • step S3101+S3102 may be implemented as an independent embodiment, but is not limited thereto.
  • 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.
  • 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:
  • Step 3201 The first device determines a first attribute corresponding to at least one first target address.
  • Step 3202 The first device determines a mapping relationship between a first target address and a carrier based on a high-level configuration.
  • 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 splitting, and the first target address is backward compatible; the first device uses a single carrier and/or PDCP multiplexing Send the SL data associated with the first target address.
  • steps 3201 - 3203 please refer to the above embodiment description.
  • step S3201 may be implemented as an independent embodiment
  • step S3202 may be implemented as an independent embodiment, but is not limited thereto.
  • 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.
  • 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:
  • Step 3301 The first device determines a first attribute corresponding to at least one first target address.
  • Step 3302 The first device determines a mapping relationship between a first target address and a carrier based on a high-level configuration.
  • 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.
  • steps 3301 - 3303 please refer to the above embodiment description.
  • the communication method involved in the embodiment of the present disclosure may include at least one of steps S3301 to S3303.
  • step S3301 may be implemented as an independent embodiment
  • step S3302 may be implemented as an independent embodiment
  • step S3301+S3302 may be implemented as an independent embodiment, but is not limited thereto.
  • 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.
  • 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:
  • Step 3401 The first device determines a first attribute corresponding to at least one first target address.
  • Step 3402 The first device determines a mapping relationship between a first target address and a carrier based on a high-level configuration.
  • 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.
  • steps 3401 - 3403 please refer to the above embodiment description.
  • step S3401 may be implemented as an independent embodiment
  • step S3402 may be implemented as an independent embodiment, but is not limited thereto.
  • 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.
  • 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:
  • 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.
  • 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.
  • the method further comprises:
  • the first device determines a first attribute corresponding to at least one first target address.
  • 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
  • the first attribute is configured according to the target address granularity; wherein the first target address corresponds to one first attribute.
  • determining the first attribute corresponding to at least one first target address includes:
  • 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.
  • 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:
  • 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.
  • the method further comprises:
  • 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
  • the first target address is backward compatible.
  • 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:
  • 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.
  • 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:
  • 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.
  • 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:
  • 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.
  • 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:
  • 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.
  • the sending the SL data associated with the first target address through PDCP multiplexing includes:
  • 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.
  • sending the SL data associated with the first SLRB through PDCP multiplexing includes:
  • 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:
  • the sending of SL data associated with the first target address by using multi-carrier offload includes:
  • 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.
  • the sending of SL data associated with the second SLRB through multi-carrier splitting includes:
  • Different SL data associated with the second SLRB are sent on multiple carriers mapped to the first target address.
  • the sending the SL data associated with the first target address through PDCP multiplexing includes:
  • 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.
  • sending the SL data associated with the first SLRB through PDCP multiplexing includes:
  • 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:
  • 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.
  • the sending the SL data associated with the first target address through a single carrier includes:
  • 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.
  • the sending the SL data associated with the first target address through a single carrier includes:
  • the SL data associated with the first target address is sent via an existing carrier that can achieve backward compatibility.
  • the method further comprises:
  • 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;
  • 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:
  • the method further comprises:
  • a mapping relationship between the first target address and the carrier is determined based on a high-level configuration.
  • 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 target version number is R18.
  • step 3501 For a detailed introduction to step 3501, please refer to the contents of the above embodiment.
  • 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.
  • 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:
  • Step 4101 The second device determines a first attribute corresponding to at least one second target address.
  • the second target address may be, for example, a second target layer 2 address.
  • 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
  • the second target address is also 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.
  • the second target address may be a target address that the second device is interested in sending and/or 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.
  • Step 4102 The second device determines a mapping relationship between a second target address and a carrier based on a high-level configuration.
  • step 4102 For a detailed introduction to step 4102, please refer to the above description of step 2102.
  • 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.
  • 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.
  • the second device 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.
  • steps 4101-4103 please refer to the contents of the above embodiment.
  • step S4101 may be implemented as an independent embodiment
  • step S4102 may be implemented as an independent embodiment, but is not limited thereto.
  • 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.
  • 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:
  • Step 4201 The second device determines a first attribute corresponding to at least one second target address.
  • Step 4102 The second device determines a mapping relationship between a second target address and a carrier based on a high-level configuration.
  • 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.
  • 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.
  • 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.
  • the second device 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.
  • steps 4201-4203 please refer to the contents of the above embodiment.
  • step S4201 may be implemented as an independent embodiment
  • step S4202 may be implemented as an independent embodiment, but is not limited thereto.
  • 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.
  • 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:
  • 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.
  • 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.
  • the method further comprises:
  • the second device determines a first attribute corresponding to each of the at least one second target address.
  • 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.
  • determining the first attribute corresponding to the at least one second target address includes:
  • 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.
  • 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:
  • 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.
  • the method further comprises:
  • 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
  • the second target address is backward compatible.
  • 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:
  • 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.
  • 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:
  • 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 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.
  • step 4301 For a detailed introduction to step 4301, please refer to the contents of the above embodiment.
  • 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.
  • FIG5 is a flow chart of a communication method according to an embodiment of the present disclosure.
  • 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:
  • Step 5101 The first device determines the mapping relationship between the first target address and the carrier, and the first attribute corresponding to the first target address. At least one of them sends the SL data associated with the first target address.
  • 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.
  • step 5101-step 5102 can refer to the introduction of the above embodiment.
  • 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.
  • step S5101 may be implemented as an independent embodiment
  • step S5102 may be implemented as an independent embodiment, but is not limited thereto.
  • 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.
  • Optional example Define a Tx profile with service type granularity or target address granularity for broadcast/multicast services to indicate whether the broadcast/multicast services support carrier aggregation/data offloading/backward compatibility.
  • Optional Example 1 Define a Tx profile at the service type granularity or the destination address granularity for broadcast/multicast services
  • Tx profile is defined based on the granularity of service type, 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.
  • Tx profile is defined at 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.
  • Tx profile is indicated to the AS layer by the high-level layer.
  • Tx profile is used to indicate whether the broadcast/multicast service supports carrier aggregation/data offload/backward compatibility
  • 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.
  • the content specifically indicated by the Tx profile may have other naming forms, which are not specifically limited in the present disclosure.
  • the Tx profile may indicate whether the service is backward compatible with R16/17legacy terminals.
  • the terminal determines whether the R16/17legacy terminal is the receiving terminal of the service/target address based on the Tx profile.
  • 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.
  • the Tx profile is defined at the target address granularity, 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.
  • Optional Example 3 For a destination address of a broadcast/multicast service, all sending and receiving terminals need to be configured with the same Tx profile(s).
  • 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.
  • the terminal device is a transmitting terminal.
  • the terminal splitting data on multiple carriers/frequency bands means that the terminal device splits data (data split) on multiple carriers/frequency bands, and the data transmitted on different carriers/frequency bands belong to this target address, and the data transmitted on different carriers/frequency bands are different.
  • packet A, B, and C are sent on carriers 1, 2, and 3 respectively.
  • the terminal device can also enable PDCP multiplexing. Specifically, PDCP multiplexing is enabled according to the configuration of the network device.
  • SLRB radio bearer For example, for certain SL radio bearers (SLRB radio bearer) associated with the target address of this broadcast/multicast service, 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.
  • the terminal device transmits these SLRBs through data splitting (the terminal device transmits these SLRBs on two or more different carriers). Transmit different data of this SLRB)
  • the terminal device may 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 layer 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the terminal device is a transmitting terminal.
  • the single carrier/frequency band is a carrier/frequency band supported by the R16/17 terminal.
  • the above case bcd are applicable.
  • 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 service associated with the broadcast/multicast address).
  • the terminal device can also enable PDCP multiplexing or send it on a single carrier/frequency band.
  • the terminal device enables PDCP multiplexing according to the configuration of the network device. For example, for certain SL radio bearers (SLRB radio bearer) 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 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.
  • SLRB radio bearer SL radio bearer
  • the terminal device transmits the data of these SLRBs through a single carrier/frequency band.
  • 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.
  • the terminal device is a transmitting terminal.
  • 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.
  • packet A is sent on both carriers 1 and 2.
  • 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.
  • an existing LCID eg, 4-19
  • 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.
  • the terminal device is a receiving terminal.
  • 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.
  • 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;
  • the present invention provides a method for SL carrier aggregation backward compatibility, which solves the problem that old version terminals of R16/17 can receive broadcast/multicast services sent by R18 terminals that support carrier aggregation in the NR sidelink carrier aggregation scenario, thereby ensuring backward compatibility.
  • 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.
  • a 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.
  • the division of the units or modules in the above devices is only a division of logical functions, which can be fully or partially integrated into one physical entity or physically separated in actual implementation.
  • 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 devices, 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.
  • CPU central processing unit
  • microprocessor a microprocessor
  • the device can be implemented in the form of hardware circuits, and the functions of some or all units or modules can be realized by designing the hardware circuits.
  • the hardware circuits can be understood as one or more processors; for example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC), and the functions of some or all units or modules are realized by designing the logical relationship of components in the circuit; for another example, in another implementation, the hardware circuit can be implemented 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 units or modules. All units or modules of the above devices can be implemented in the form of software called by the processor, or in the form of hardware circuits, or in part by software called by the processor, and the rest by hardware circuits.
  • PLD programmable logic device
  • FPGA field programmable gate array
  • the processor is a circuit with signal processing capability.
  • 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); in another implementation, the processor may implement certain functions through the logical relationship of a hardware circuit, and the logical relationship of the above hardware circuit may be fixed or reconfigurable, such as a hardware circuit implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA.
  • ASIC application-specific integrated circuit
  • PLD programmable logic device
  • the process of the processor loading a configuration document to implement the hardware circuit configuration 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.
  • it can also be a hardware circuit designed for artificial intelligence, which can be understood as ASIC, such as Neural Network Processing Unit (NPU), Tensor Processing Unit (TPU), Deep Learning Processing Unit (DPU), etc.
  • ASIC Neural Network Processing Unit
  • NPU Neural Network Processing Unit
  • TPU Tensor Processing Unit
  • DPU Deep Learning Processing Unit
  • 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:
  • 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.
  • 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.
  • 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.
  • 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:
  • 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.
  • 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.
  • 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.
  • 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.
  • 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
  • the central processing unit may be used to process the communication device (such as a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.). Control, execute programs, and process program data.
  • the processor 7101 is used to call instructions to enable the communication device 7100 to execute any of the above methods.
  • the communication device 7100 further includes one or more memories 7102 for storing instructions.
  • the memory 7102 may also be outside the communication device 7100.
  • the communication device 7100 further 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.
  • the transceiver may include a receiver and a transmitter, and the receiver and the transmitter may be separate or integrated.
  • 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.
  • 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.
  • the interface circuit 7104 can read instructions stored in the memory 7102 and send the instructions to the processor 7101.
  • 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.
  • 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.
  • FIG. 7B is a schematic diagram of the structure of a chip 7200 provided in an embodiment of the present disclosure.
  • the communication device 7100 may be a chip or a chip system
  • 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.
  • 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.
  • the interface circuit 7202 can read instructions stored in the memory 7203 and send the instructions to the processor 7201.
  • the terms such as interface circuit, interface, transceiver pin, and transceiver can be replaced with each other.
  • the chip 7200 further includes one or more memories 7203 for storing instructions.
  • the memory 7203 may be outside the chip 7200.
  • 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.
  • the storage medium is an electronic storage medium.
  • 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.
  • 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.
  • 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.
  • the program product is a computer program product.
  • 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.
  • the computer program product includes one or more computer programs.
  • 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.
  • 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)).
  • a magnetic medium eg, a floppy disk, a hard disk, a magnetic tape
  • an optical medium eg, a high-density digital video disc (DVD)
  • DVD high-density digital video disc
  • SSD solid state disk

Landscapes

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

Abstract

本公开提出一种通信方法、装置、设备及存储介质，方法包括：第一设备基于第一目标地址与载波之间的映射关系、第一目标地址对应的第一属性中的至少之一发送第一目标地址关联的侧行链路SL数据；其中，第一属性用于指示以下至少之一：第一目标地址的版本号、第一目标地址是否支持载波聚合、第一目标地址是否支持数据分流、第一目标地址是否后向兼容；其中，第一目标地址为广播业务和/或组播业务关联的目标地址，第一目标地址为第一设备感兴趣发送和/或接收的目标地址。本公开的方法可以确保对该第一目标地址的接收终端成功实现后向兼容，保证了SL通信的稳定性。

Description

通信方法及装置、通信设备、通信系统、存储介质 技术领域
本公开涉及通信技术领域，尤其涉及通信方法及装置、通信设备、通信系统、存储介质。
背景技术
通信系统中，通过引入载波聚合(Carrier Aggregation，CA)技术来提高上下行传输速率，可选地，在新版本(如R18版本)中，侧行链路(Sidelink，SL)通信中也引入了SL载波聚合技术。
发明内容
本公开提出通信方法及装置、通信设备、通信系统、存储介质。
根据本公开实施例的第一方面，提出了一种通信方法，包括：
第一设备基于第一目标地址与载波之间的映射关系、第一目标地址对应的第一属性中的至少之一发送所述第一目标地址关联的侧行链路SL数据；其中，所述第一目标地址对应的第一属性用于指示以下至少之一：所述第一目标地址的版本号、所述第一目标地址是否支持载波聚合、所述第一目标地址是否支持数据分流、所述第一目标地址是否后向兼容；其中，所述第一目标地址为广播业务和/或组播业务关联的目标地址，所述第一目标地址为所述第一设备感兴趣发送和/或接收的目标地址。
根据本公开实施例的第二方面，提出了一种通信方法，包括：
第二设备基于第二目标地址与载波之间的映射关系、第二目标地址对应的第一属性中的至少之一在一个或多个载波上接收SL数据；其中，所述第二目标地址对应的第一属性用于指示以下至少之一：所述第二目标地址的版本号、所述第二目标地址是否支持载波聚合、所述第二目标地址是否支持数据分流、所述第二目标地址是否后向兼容；所述第二目标地址为广播业务和/或组播业务关联的目标地址，所述第二目标地址为所述第二设备感兴趣发送和/或接收的目标地址。
根据本公开实施例的第三方面，提出了一种通信方法，用于通信系统，所述通信系统包括第一设备、第二设备，所述方法包括以下至少之一：
所述第一设备基于第一目标地址与载波之间的映射关系、第一目标地址对应的第一属性中的至少之一发送所述第一目标地址关联的SL数据；其中，所述第一目标地址对应的第一属性用于指示以下至少之一：所述第一目标地址的版本号、所述第一目标地址是否支持载波聚合、所述第一目标地址是否支持数据分流、所述第一目标地址是否后向兼容；其中，所述第一目标地址为广播业务和/或组播业务关联的目标地址，所述第一目标地址为所述第一设备感兴趣发送和/或接收的目标地址；
所述第二设备基于第二目标地址与载波之间的映射关系、第二目标地址对应的第一属性中的至少之一在一个或多个载波上接收SL数据；其中，所述第二目标地址对应的第一属性用于指示以下至少之一：所述第二目标地址的版本号、所述第二目标地址是否支持载波聚合、所述第二目标地址是否支持数据分流、所述第二目标地址是否后向兼容；所述第二目标地址为广播业务和/或组播业务关联的目标地址，所述第二目标地址为所述第二设备感兴趣发送和/或接收的目标地址，所述至少一个第二目标地址为所述至少一个第一目标地址中的部分或全部目标地址。
根据本公开实施例的第四方面，提出了一种第一设备，包括：
发送模块，用于基于第一目标地址与载波之间的映射关系、第一目标地址对应的第一属性中的至少之一发送所述第一目标地址关联的SL数据；其中，所述第一目标地址对应的第一属性用于指示以下至少之一：所述第一目标地址的版本号、所述第一目标地址是否支持载波聚合、所述第一目标地址是否支持数据分流、所述第一目标地址是否后向兼容；其中，所述第一目标地址为广播业务和/或组播业务关联的目标地址，所述第一目标地址为所述第一设备感兴趣发送和/或接收的目标地址。
根据本公开实施例的第五方面，提出了一种第二设备，包括：
接收模块，用于基于所述第二目标地址与载波之间的映射关系、所述第二目标地址对应的第一属性中的至少之一在一个或多个载波上接收SL数据；其中，所述第二目标地址对应的第一属性用于指示以下至少之一：所述第二目标地址的版本号、所述第二目标地址是否支持载波聚合、所述第二目标地址是否支持数据分流、所述第二目标地址是否后向兼容；所述第二目标地址为广播业务和/或组播业务关联的目标地址，所述第二目标地址为所述第二设备感兴趣发送和/或接收的目标地址。
根据本公开实施例的第六方面，提出了一种通信设备，包括：
一个或多处理器；其中，所述处理器用于调用指令以使得所述通信设备执行第一方面、第二方面中任一方面所述的通信方法。
根据本公开实施例的第七方面，提出了一种通信系统，其特征在于，包括第一设备、第二设备，其中，所述第一设备被配置为实现第一方面所述的通信方法，所述第二设备被配置为实现第二方面所述的通信方法。
根据本公开实施例的第八方面，提出了一种存储介质，所述存储介质存储有指令，其特征在于，当所述指令在通信设备上运行时，使得所述通信设备执行如第一方面、第二方面中任一方面所述的通信方法。
附图说明
本公开上述的和/或附加的方面和优点从下面结合附图对实施例的描述中将变得明显和容易理解，其中：
图1为本公开实施例提供的一些通信系统的架构示意图；
图2A-2D为本公开一个实施例所提供的通信方法的交互示意图；
图3A-3E为本公开再一个实施例所提供的通信方法的流程示意图；
图4A-4C为本公开再一个实施例所提供的通信方法的流程示意图；
图5为本公开再一个实施例所提供的通信方法的流程示意图；
图6A为本公开一个实施例所提供的第一设备的结构示意图；
图6B为本公开一个实施例所提供的第二设备的结构示意图；
图7A是本公开一个实施例所提供的一种通信设备的结构示意图；
图7B为本公开一个实施例所提供的一种芯片的结构示意图。
具体实施方式
本公开实施例提出了通信方法及装置、通信设备、通信系统、存储介质。
第一方面，本公开实施例提出了一种通信方法，由第一设备执行，所述方法包括：
第一设备基于第一目标地址与载波之间的映射关系、第一目标地址对应的第一属性中的至少之一发送所述第一目标地址关联的侧行链路SL数据；其中，所述第一目标地址对应的第一属性用于指示以下至少之一：所述第一目标地址的版本号、所述第一目标地址是否支持载波聚合、所述第一目标地址是否支持数据分流、所述第一目标地址是否后向兼容；其中，所述第一目标地址为广播业务和/或组播业务关联的目标地址，所述第一目标地址为所述第一设备感兴趣发送和/或接收的目标地址。
在上述实施例中，第一设备在发送第一目标地址关联的SL数据时是基于第一目标地址与载波之间的映射关系、第一目标地址对应的第一属性中的至少之一发送的。其中，该第一目标地址对应的第一属性用于指示以下至少之一：第一目标地址的版本号、第一目标地址是否支持载波聚合、第一目标地址是否支持数据分流、第一目标地址是否后向兼容，也即是，该第一目标地址对应的第一属性可以体现出该第一目标地址是否后向兼容。由此可知，在本公开实施例之中，当第一设备在发送第一目标地址关联的SL数据时，会从“目标地址与载波之间的映射关系”、“第一目标地址是否后向兼容”这两个维度来发送第一目标地址关联的SL数据，则可以确保第一设备最终发送第一目标地址关联的SL数据时的发送方式是匹配于第二设备(即第一目标地址的接收终端)的接收能力的，则当第二设备为能力受限终端(如：旧版本终端，例如：R16/17的终端)时，可以确保对该第二设备成功实现后向兼容，从而保证了SL通信的稳定性。
结合第一方面的一些实施例，在一些实施例中，所述方法还包括：
所述第一设备确定至少一个第一目标地址分别对应的第一属性。
结合第一方面的一些实施例，在一些实施例中，所述第一属性按照业务粒度配置；其中，一个第一业务对应一个第一属性，所述第一目标地址关联至少一个第一业务；所述第一业务包括广播业务和/或组播业务；或者
所述第一属性按照目标地址粒度配置；其中，所述第一目标地址对应一个第一属性。
在上述实施例中，提供了一种第一属性的配置方法，用于为第一目标地址配置对应的第一属性，以便第一设备后续可以基于第一目标地址对应的第一属性对第二设备成功实现后向兼容，从而保证了SL通信的稳定性。
结合第一方面的一些实施例，在一些实施例中，所述确定至少一个第一目标地址分别对应的第一属性， 包括：
所述第一属性按照业务粒度配置，基于所述第一目标地址关联的至少一个第一业务对应的第一属性确定所述第一目标地址对应的第一属性。
结合第一方面的一些实施例，在一些实施例中，所述基于所述第一目标地址关联的至少一个第一业务对应的第一属性确定所述第一目标地址对应的第一属性，包括：
所述第一目标地址关联的所有第一业务对应的第一属性均指示以下至少之一：版本号为目标版本号、支持载波聚合、支持数据分流、不后向兼容，确定所述第一目标地址对应的第一属性为以下至少之一：所述第一目标地址的版本号为所述目标版本号、所述第一目标地址支持载波聚合、所述第一目标地址支持数据分流、所述第一目标地址不后向兼容。
在上述实施例中，提供了一种第一属性的确定方法，用于确定出第一目标地址对应的第一属性，以便第一设备后续可以基于第一目标地址对应的第一属性对第二设备成功实现后向兼容，从而保证了SL通信的稳定性。
结合第一方面的一些实施例，在一些实施例中，所述方法还包括：
所述第一目标地址不存在对应的第一属性，确定以下至少之一：所述第一目标地址的版本号不为目标版本号、所述第一目标地址不支持载波聚合、所述第一目标地址不支持数据分流、所述第一目标地址后向兼容。
在上述实施例中，提供了一种当第一目标地址不存在对应的第一属性时，如何确定第一目标地址是否后向兼容的方法，以便第一设备基于第一目标地址是否后向兼容来发送第一目标地址关联的SL数据，则可以确保第一设备最终发送第一目标地址关联的SL数据时的发送方式是匹配于第二设备(即第一目标地址的接收终端)的接收能力的，则当第二设备为能力受限终端(如：旧版本终端，例如：R16/17的终端)时，可以确保对该第二设备成功实现后向兼容，从而保证了SL通信的稳定性。
结合第一方面的一些实施例，在一些实施例中，所述基于所述第一目标地址与载波之间的映射关系、所述第一目标地址对应的第一属性中的至少之一发送所述第一目标地址关联的SL数据，包括：
所述第一目标地址与载波之间的映射关系为：所述第一目标地址映射到多个载波；和/或，所述第一目标地址对应的第一属性指示以下至少之一：所述第一目标地址的版本号为目标版本号、所述第一目标地址支持载波聚合、所述第一目标地址支持数据分流、所述第一目标地址不后向兼容；通过多载波分流和/或包数据汇聚协议PDCP复用duplication发送所述第一目标地址关联的SL数据。
结合第一方面的一些实施例，在一些实施例中，所述基于所述第一目标地址与载波之间的映射关系、所述第一目标地址对应的第一属性中的至少之一发送所述第一目标地址关联的SL数据，包括：
所述第一目标地址与载波之间的映射关系为：所述第一目标地址映射到多个载波；和/或，所述第一目标地址对应的第一属性指示以下至少之一：所述第一目标地址的版本号不为目标版本号、所述第一目标地址不支持载波聚合、所述第一目标地址不支持数据分流、所述第一目标地址后向兼容；通过单载波和/或PDCP复用发送所述第一目标地址关联的SL数据。
结合第一方面的一些实施例，在一些实施例中，所述基于所述第一目标地址与载波之间的映射关系、所述第一目标地址对应的第一属性中的至少之一发送所述第一目标地址关联的SL数据，包括：
所述第一目标地址与载波之间的映射关系为：所述第一目标地址映射到一个载波；和/或，所述第一目标地址对应的第一属性指示以下至少之一：所述第一目标地址的版本号为目标版本号、所述第一目标地址支持载波聚合、所述第一目标地址支持数据分流、所述第一目标地址不后向兼容；通过单载波发送所述第一目标地址关联的SL数据。
结合第一方面的一些实施例，在一些实施例中，所述基于所述第一目标地址与载波之间的映射关系、所述第一目标地址对应的第一属性中的至少之一发送所述第一目标地址关联的SL数据，包括：
所述第一目标地址与载波之间的映射关系为：所述第一目标地址映射到一个载波；和/或，所述第一目标地址对应的第一属性指示以下至少之一：所述第一目标地址的版本号不为目标版本号、所述第一目标地址不支持载波聚合、所述第一目标地址不支持数据分流、所述第一目标地址后向兼容；通过单载波发送所述第一目标地址关联的SL数据。
在上述实施例中，提供了一种第一设备具体如何基于第一目标地址与载波之间的映射关系和/或第一目 标地址对应的第一属性来发送第一目标地址关联的SL数据的方法，以使得第一设备最终发送第一目标地址关联的SL数据时的发送方式是匹配于第二设备(即第一目标地址的接收终端)的接收能力的，则当第二设备为能力受限终端(如：旧版本终端，例如：R16/17的终端)时，可以确保对该第二设备成功实现后向兼容，从而保证了SL通信的稳定性。
结合第一方面的一些实施例，在一些实施例中，所述通过PDCP复用发送所述第一目标地址关联的SL数据，包括：
通过PDCP复用发送第一SLRB关联的SL数据；其中，所述第一SLRB为第一目标地址关联的且激活了PDCP复用的SLRB，所述第一SLRB为一个或者多个。
结合第一方面的一些实施例，在一些实施例中，所述通过PDCP复用发送第一SLRB关联的SL数据，包括：
在所述第一目标地址映射的所述多个载波中选择2个载波分别发送所述第一SLRB关联的相同的SL数据。
结合第一方面的一些实施例，在一些实施例中，所述在所述第一目标地址映射的所述多个载波中选择2个载波分别发送所述第一SLRB关联的相同的SL数据，包括：
在所述第一目标地址映射的多个载波中任意选择2个载波分别发送所述第一SLRB关联的相同的SL数据。
结合第一方面的一些实施例，在一些实施例中，所述通过多载波分流发送所述第一目标地址关联的SL数据，包括：
通过所述第一目标地址映射的所述多个载波分流发送第二SLRB关联的SL数据；其中，所述第二SLRB为第一目标地址关联的且去激活PDCP复用的SLRB，所述第二SLRB为一个或者多个。
结合第一方面的一些实施例，在一些实施例中，所述通过多载波分流发送第二SLRB关联的SL数据，包括：
在所述第一目标地址映射的多个载波上发送所述第二SLRB关联的不同的SL数据。
结合第一方面的一些实施例，在一些实施例中，所述通过PDCP复用发送所述第一目标地址关联的SL数据，包括：
通过PDCP复用发送第一SLRB关联的SL数据；其中，所述第一SLRB为第一目标地址关联的且激活了PDCP复用的SLRB，所述第一SLRB为一个或者多个。
结合第一方面的一些实施例，在一些实施例中，所述通过PDCP复用发送第一SLRB关联的SL数据，包括：
在所述第一目标地址映射的所述多个载波中选择2个载波分别发送所述第一SLRB关联的相同的SL数据。
结合第一方面的一些实施例，在一些实施例中，所述在所述第一目标地址映射的所述多个载波中选择2个载波分别发送所述第一SLRB关联的相同的SL数据，包括：
在所述第一目标地址映射的多个载波中选择可实现后向兼容的现有载波和任意一个其他载波分别发送所述第一SLRB关联的相同的SL数据。
结合第一方面的一些实施例，在一些实施例中，所述通过单载波发送所述第一目标地址关联的SL数据，包括：
通过可实现后向兼容的现有载波发送第二SLRB关联的SL数据；其中，所述第二SLRB为第一目标地址关联的且去激活PDCP复用的SLRB，所述第二SLRB为一个或者多个。
结合第一方面的一些实施例，在一些实施例中，所述通过单载波发送所述第一目标地址关联的SL数据，包括：
通过可实现后向兼容的现有载波发送所述第一目标地址关联的SL数据。
在上述实施例中，提供了一种第一设备具体如何发送SL数据的方法，用于第一设备成功向第二设备发送SL数据，确保SL数据的成功传输，保证了SL传输的稳定性。并且，在一些实施例之中，当某些SLRB(如上述的第一SLRB)激活了PDCP复用时，第一设备还会通过PDCP复用发送该SLRB关联的SL数据，从而可以提高SL数据的可靠性、降低重复发送的时延，满足超高可靠低时延通信(Ultra Reliable and  Low Latency Communication，URLLC)要求。
结合第一方面的一些实施例，在一些实施例中，所述方法还包括：
确定至少一个第一SLRB和/或至少一个第二SLRB分别对应的SLRB配置，所述至少一个第一SLRB和/或至少一个第二SLRB分别对应的SLRB配置用于配置所述至少一个第一SLRB和/或至少一个第二SLRB是否激活PDCP复用；
根据所述至少一个第一SLRB和/或至少一个第二SLRB分别对应的SLRB配置确定所述第一目标地址关联的所述至少一个第一SLRB和/或至少一个第二SLRB是否激活PDCP复用。
结合第一方面的一些实施例，在一些实施例中，所述确定至少一个第一SLRB和/或至少一个第二SLRB分别对应的SLRB配置，包括以下至少之一：
获取通过专用信令发送的所述至少一个第一SLRB和/或至少一个第二SLRB分别对应的SLRB配置；
获取通过系统信息块SIB发送的所述至少一个第一SLRB和/或至少一个第二SLRB分别对应的SLRB配置；
获取预配置的所述至少一个第一SLRB和/或至少一个第二SLRB分别对应的SLRB配置。
在上述实施例中，提供了一种第一设备具体如何确定哪些SLRB配置激活了PDCP复用的方法，用于第一设备确定出上述的第一SLRB和第二SLRB，并采用对应的发送方式来分别发送第一SLRB关联的SL数据和第二SLRB关联的SL数据，从而确保SL数据的成功传输，保证了SL传输的稳定性。
结合第一方面的一些实施例，在一些实施例中，所述方法还包括：
基于高层配置确定所述第一目标地址与载波之间的映射关系。
在上述实施例中，提供了一种第一设备如何确定第一目标地址与载波之间的映射关系的方法，用于第一设备成功确定出第一目标地址与载波之间的映射关系，则当第一设备后续在发送第一目标地址关联的SL数据时，可以基于所确定的第一目标地址与载波之间的映射关系结合第一目标地址对应的第一属性来发送第一目标地址关联的SL数据，以确保第一设备最终发送第一目标地址关联的SL数据时的发送方式是匹配于第二设备(即第一目标地址的接收终端)的接收能力的，则当第二设备为能力受限终端(如：旧版本中不支持载波聚合的终端，例如：R16/17的终端)时，可以确保对该第二设备成功实现后向兼容，从而保证了SL通信的稳定性。
结合第一方面的一些实施例，在一些实施例中，对于第一目标地址，所述第一设备与第二设备配置相同的第一属性；其中，所述第一设备为所述第一目标地址的发送终端，所述第二设备所述第一目标地址的接收终端。
在上述实施例中，第一设备(即第一目标地址的发送终端)与第二设备(即第一目标地址的接收终端)对于第一目标地址会配置相同的第一属性，由此统一了第一设备和第二设备对于第一目标地址的第一属性的理解，从而可以确保第一设备与第二设备之间可以基于统一理解的第一目标地址的第一属性来实现第一目标地址关联的SL数据的成功传输，确保SL通信的稳定性。
结合第一方面的一些实施例，在一些实施例中，所述目标版本号为R18。
第二方面，本公开实施例提出了一种通信方法，由第二设备执行，包括：
第二设备基于第二目标地址与载波之间的映射关系、第二目标地址对应的第一属性中的至少之一在一个或多个载波上接收SL数据；其中，所述第二目标地址对应的第一属性用于指示以下至少之一：所述第二目标地址的版本号、所述第二目标地址是否支持载波聚合、所述第二目标地址是否支持数据分流、所述第二目标地址是否后向兼容；所述第二目标地址为广播业务和/或组播业务关联的目标地址，所述第二目标地址为所述第二设备感兴趣发送和/或接收的目标地址。
在上述实施例中，第二设备在接收第二目标地址关联的SL数据时是基于第二目标地址与载波之间的映射关系、第二目标地址对应的第一属性中的至少之一接收的。其中，该第二目标地址对应的第一属性用于指示以下至少之一：第二目标地址的版本号、第二目标地址是否支持载波聚合、第二目标地址是否支持数据分流、第二目标地址是否后向兼容，也即是，该第二目标地址对应的第一属性可以体现出该第二目标地址是否后向兼容。由此可知，在本公开实施例之中，当第二设备在接收第二目标地址关联的SL数据时，会从“目标地址与载波之间的映射关系”、“第二目标地址是否后向兼容”这两个维度来接收第二目标地址关联的SL数据，则可以确保第二设备最终接收第二目标地址关联的SL数据时的接收方式是匹配于第二 设备的接收能力的，则当第二设备为能力受限终端(如：旧版本终端，例如：R16/17的终端)时，可以确保对该第二设备成功实现后向兼容，从而保证了SL通信的稳定性。
结合第二方面的一些实施例，在一些实施例中，所述方法还包括：
所述第二设备确定至少一个第二目标地址分别对应的第一属性。
结合第二方面的一些实施例，在一些实施例中，所述第一属性按照业务粒度配置；其中，一个第二业务对应一个第一属性，所述第二目标地址关联至少一个第二业务；所述第二业务包括广播业务和/或组播业务；或者
所述第一属性按照目标地址粒度配置；其中，所述第二目标地址对应一个第一属性。
结合第二方面的一些实施例，在一些实施例中，所述确定至少一个第二目标地址分别对应的第一属性，包括：
所述第一属性按照业务粒度配置，基于所述第二目标地址关联的至少一个第二业务对应的第一属性确定所述第二目标地址对应的第一属性。
结合第二方面的一些实施例，在一些实施例中，所述基于所述第二目标地址关联的至少一个第二业务对应的第一属性确定所述第二目标地址对应的第一属性，包括：
所述第二目标地址关联的所有第二业务对应的第一属性均指示以下至少之一：版本号为目标版本号、支持载波聚合、支持数据分流、不后向兼容，确定所述第二目标地址对应的第一属性为以下至少之一：所述第二目标地址的版本号为所述目标版本号、所述第二目标地址支持载波聚合、所述第二目标地址支持数据分流、所述第二目标地址不后向兼容。
结合第二方面的一些实施例，在一些实施例中，所述方法还包括：
所述第二目标地址不存在对应的第一属性，确定以下至少之一：所述第二目标地址的版本号不为目标版本号、所述第二目标地址不支持载波聚合、所述第二目标地址不支持数据分流、所述第二目标地址后向兼容。
结合第二方面的一些实施例，在一些实施例中，所述基于所述第二目标地址与载波之间的映射关系、所述第二目标地址对应的第一属性中的至少之一在一个或多个载波上接收SL数据，包括：
至少一个第二目标地址满足第一预设条件，通过多载波接收所述至少一个第二目标地址关联的SL数据；其中，所述第一预设条件包括：所述第二目标地址与载波之间的映射关系为：所述第二目标地址映射到多个载波；和/或，所述第二目标地址对应的第一属性指示以下至少之一：所述第二目标地址的版本号为目标版本号、所述第二目标地址支持载波聚合、所述第二目标地址支持数据分流、所述第二目标地址不后向兼容。
结合第二方面的一些实施例，在一些实施例中，所述基于所述第二目标地址与载波之间的映射关系、所述第二目标地址对应的第一属性中的至少之一在一个或多个载波上接收SL数据，包括：
全部第二目标地址满足第二预设条件，通过可实现后向兼容的现有载波接收所述至少一个第二目标地址关联的SL数据；其中，所述第二预设条件包括：所述第二目标地址与载波之间的映射关系为：所述第二目标地址映射到一个载波；和/或，所述第二目标地址对应的第一属性指示以下至少之一：所述第二目标地址的版本号不为目标版本号、所述第二目标地址不支持载波聚合、所述第二目标地址不支持数据分流、所述第二目标地址后向兼容；和/或，所述第二预设条件包括：所述第二目标地址与载波之间的映射关系为：所述第二目标地址映射到多个载波；和/或，所述第二目标地址对应的第一属性指示以下至少之一：所述第二目标地址的版本号不为目标版本号、所述第二目标地址不支持载波聚合、所述第二目标地址不支持数据分流、所述第二目标地址后向兼容。
结合第二方面的一些实施例，在一些实施例中，对于第二目标地址，所述第一设备与第二设备配置相同的第一属性；其中，所述第一设备为所述第二目标地址的发送终端，所述第二设备为所述第二目标地址的接收终端。
第三方面，本公开实施例提出了一种通信方法，用于通信系统，所述通信系统包括第一设备、第二设备，所述方法包括以下至少之一：
所述第一设备基于第一目标地址与载波之间的映射关系、第一目标地址对应的第一属性中的至少之一发送所述第一目标地址关联的SL数据；其中，所述第一目标地址对应的第一属性用于指示以下至少之一： 所述第一目标地址的版本号、所述第一目标地址是否支持载波聚合、所述第一目标地址是否支持数据分流、所述第一目标地址是否后向兼容；其中，所述第一目标地址为广播业务和/或组播业务关联的目标地址，所述第一目标地址为所述第一设备感兴趣发送和/或接收的目标地址；
所述第二设备基于第二目标地址与载波之间的映射关系、第二目标地址对应的第一属性中的至少之一在一个或多个载波上接收SL数据；其中，所述第二目标地址对应的第一属性用于指示以下至少之一：所述第二目标地址的版本号、所述第二目标地址是否支持载波聚合、所述第二目标地址是否支持数据分流、所述第二目标地址是否后向兼容；所述第二目标地址为广播业务和/或组播业务关联的目标地址，所述第二目标地址为所述第二设备感兴趣发送和/或接收的目标地址，所述至少一个第二目标地址为所述至少一个第一目标地址中的部分或全部目标地址。
第四方面，本公开实施例提出了第一设备，包括：
发送模块，用于基于第一目标地址与载波之间的映射关系、第一目标地址对应的第一属性中的至少之一发送所述第一目标地址关联的SL数据；其中，所述第一目标地址对应的第一属性用于指示以下至少之一：所述第一目标地址的版本号、所述第一目标地址是否支持载波聚合、所述第一目标地址是否支持数据分流、所述第一目标地址是否后向兼容；其中，所述第一目标地址为广播业务和/或组播业务关联的目标地址，所述第一目标地址为所述第一设备感兴趣发送和/或接收的目标地址。
结合第四方面的一些实施例，在一些实施例中，所述第一设备还用于：
确定至少一个第一目标地址分别对应的第一属性。
结合第四方面的一些实施例，在一些实施例中，所述第一属性按照业务粒度配置；其中，一个第一业务对应一个第一属性，所述第一目标地址关联至少一个第一业务；所述第一业务包括广播业务和/或组播业务；或者
所述第一属性按照目标地址粒度配置；其中，所述第一目标地址对应一个第一属性。
结合第四方面的一些实施例，在一些实施例中，所述第一设备还用于：
所述第一属性按照业务粒度配置，基于所述第一目标地址关联的至少一个第一业务对应的第一属性确定所述第一目标地址对应的第一属性。
结合第四方面的一些实施例，在一些实施例中，所述第一设备还用于：
所述第一目标地址关联的所有第一业务对应的第一属性均指示以下至少之一：版本号为目标版本号、支持载波聚合、支持数据分流、不后向兼容，确定所述第一目标地址对应的第一属性为以下至少之一：所述第一目标地址的版本号为所述目标版本号、所述第一目标地址支持载波聚合、所述第一目标地址支持数据分流、所述第一目标地址不后向兼容。
结合第四方面的一些实施例，在一些实施例中，所述第一设备还用于：
所述第一目标地址不存在对应的第一属性，确定以下至少之一：所述第一目标地址的版本号不为目标版本号、所述第一目标地址不支持载波聚合、所述第一目标地址不支持数据分流、所述第一目标地址后向兼容。
结合第四方面的一些实施例，在一些实施例中，所述发送模块还用于：
所述第一目标地址与载波之间的映射关系为：所述第一目标地址映射到多个载波；和/或，所述第一目标地址对应的第一属性指示以下至少之一：所述第一目标地址的版本号为目标版本号、所述第一目标地址支持载波聚合、所述第一目标地址支持数据分流、所述第一目标地址不后向兼容；通过多载波分流和/或包数据汇聚协议PDCP复用duplication发送所述第一目标地址关联的SL数据。
结合第四方面的一些实施例，在一些实施例中，所述发送模块还用于：
所述第一目标地址与载波之间的映射关系为：所述第一目标地址映射到多个载波；和/或，所述第一目标地址对应的第一属性指示以下至少之一：所述第一目标地址的版本号不为目标版本号、所述第一目标地址不支持载波聚合、所述第一目标地址不支持数据分流、所述第一目标地址后向兼容；通过单载波和/或PDCP复用发送所述第一目标地址关联的SL数据。
结合第四方面的一些实施例，在一些实施例中，所述发送模块还用于：
所述第一目标地址与载波之间的映射关系为：所述第一目标地址映射到一个载波；和/或，所述第一目标地址对应的第一属性指示以下至少之一：所述第一目标地址的版本号为目标版本号、所述第一目标地址 支持载波聚合、所述第一目标地址支持数据分流、所述第一目标地址不后向兼容；通过单载波发送所述第一目标地址关联的SL数据。
结合第四方面的一些实施例，在一些实施例中，所述发送模块还用于：
所述第一目标地址与载波之间的映射关系为：所述第一目标地址映射到一个载波；和/或，所述第一目标地址对应的第一属性指示以下至少之一：所述第一目标地址的版本号不为目标版本号、所述第一目标地址不支持载波聚合、所述第一目标地址不支持数据分流、所述第一目标地址后向兼容；通过单载波发送所述第一目标地址关联的SL数据。
结合第四方面的一些实施例，在一些实施例中，所述发送模块还用于：
通过PDCP复用发送第一SLRB关联的SL数据；其中，所述第一SLRB为第一目标地址关联的且激活了PDCP复用的SLRB，所述第一SLRB为一个或者多个。
结合第四方面的一些实施例，在一些实施例中，所述发送模块还用于：
在所述第一目标地址映射的所述多个载波中选择2个载波分别发送所述第一SLRB关联的相同的SL数据。
结合第四方面的一些实施例，在一些实施例中，所述发送模块还用于：
在所述第一目标地址映射的多个载波中任意选择2个载波分别发送所述第一SLRB关联的相同的SL数据。
结合第四方面的一些实施例，在一些实施例中，所述发送模块还用于：
通过所述第一目标地址映射的所述多个载波分流发送第二SLRB关联的SL数据；其中，所述第二SLRB为第一目标地址关联的且去激活PDCP复用的SLRB，所述第二SLRB为一个或者多个。
结合第四方面的一些实施例，在一些实施例中，所述发送模块还用于：
在所述第一目标地址映射的多个载波上发送所述第二SLRB关联的不同的SL数据。
结合第四方面的一些实施例，在一些实施例中，所述发送模块还用于：
通过PDCP复用发送第一SLRB关联的SL数据；其中，所述第一SLRB为第一目标地址关联的且激活了PDCP复用的SLRB，所述第一SLRB为一个或者多个。
结合第四方面的一些实施例，在一些实施例中，所述发送模块还用于：
在所述第一目标地址映射的所述多个载波中选择2个载波分别发送所述第一SLRB关联的相同的SL数据。
结合第四方面的一些实施例，在一些实施例中，所述发送模块还用于：
在所述第一目标地址映射的多个载波中选择可实现后向兼容的现有载波和任意一个其他载波分别发送所述第一SLRB关联的相同的SL数据。
结合第四方面的一些实施例，在一些实施例中，所述发送模块还用于：
通过可实现后向兼容的现有载波发送第二SLRB关联的SL数据；其中，所述第二SLRB为第一目标地址关联的且去激活PDCP复用的SLRB，所述第二SLRB为一个或者多个。
结合第四方面的一些实施例，在一些实施例中，所述发送模块还用于：
通过可实现后向兼容的现有载波发送所述第一目标地址关联的SL数据。
结合第四方面的一些实施例，在一些实施例中，所述装置还用于：
确定至少一个第一SLRB和/或至少一个第二SLRB分别对应的SLRB配置，所述至少一个第一SLRB和/或至少一个第二SLRB分别对应的SLRB配置用于配置所述至少一个第一SLRB和/或至少一个第二SLRB是否激活PDCP复用；
根据所述至少一个第一SLRB和/或至少一个第二SLRB分别对应的SLRB配置确定所述第一目标地址关联的所述至少一个第一SLRB和/或至少一个第二SLRB是否激活PDCP复用。
结合第四方面的一些实施例，在一些实施例中，所述装置还用于：
获取通过专用信令发送的所述至少一个第一SLRB和/或至少一个第二SLRB分别对应的SLRB配置；
获取通过系统信息块SIB发送的所述至少一个第一SLRB和/或至少一个第二SLRB分别对应的SLRB配置；
获取预配置的所述至少一个第一SLRB和/或至少一个第二SLRB分别对应的SLRB配置。
结合第四方面的一些实施例，在一些实施例中，所述装置还用于：
基于高层配置确定所述第一目标地址与载波之间的映射关系。
结合第四方面的一些实施例，在一些实施例中，对于第一目标地址，所述第一设备与第二设备配置相同的第一属性；其中，所述第一设备为所述第一目标地址的发送终端，所述第二设备所述第一目标地址的接收终端。
结合第四方面的一些实施例，在一些实施例中，所述目标版本号为R18。
第五方面，本公开实施例提出了第二设备，包括：
接收模块，用于基于所述第二目标地址与载波之间的映射关系、所述第二目标地址对应的第一属性中的至少之一在一个或多个载波上接收SL数据；其中，所述第二目标地址对应的第一属性用于指示以下至少之一：所述第二目标地址的版本号、所述第二目标地址是否支持载波聚合、所述第二目标地址是否支持数据分流、所述第二目标地址是否后向兼容；所述第二目标地址为广播业务和/或组播业务关联的目标地址，所述第二目标地址为所述第二设备感兴趣发送和/或接收的目标地址。
结合第五方面的一些实施例，在一些实施例中，所述第二设备还用于：
确定至少一个第二目标地址分别对应的第一属性。
结合第五方面的一些实施例，在一些实施例中，所述第一属性按照业务粒度配置；其中，一个第二业务对应一个第一属性，所述第二目标地址关联至少一个第二业务；所述第二业务包括广播业务和/或组播业务；或者
所述第一属性按照目标地址粒度配置；其中，所述第二目标地址对应一个第一属性。
结合第五方面的一些实施例，在一些实施例中，所述第二设备还用于：
所述第一属性按照业务粒度配置，基于所述第二目标地址关联的至少一个第二业务对应的第一属性确定所述第二目标地址对应的第一属性。
结合第五方面的一些实施例，在一些实施例中，所述第二设备还用于：
所述第二目标地址关联的所有第二业务对应的第一属性均指示以下至少之一：版本号为目标版本号、支持载波聚合、支持数据分流、不后向兼容，确定所述第二目标地址对应的第一属性为以下至少之一：所述第二目标地址的版本号为所述目标版本号、所述第二目标地址支持载波聚合、所述第二目标地址支持数据分流、所述第二目标地址不后向兼容。
结合第五方面的一些实施例，在一些实施例中，所述第二设备还用于：
所述第二目标地址不存在对应的第一属性，确定以下至少之一：所述第二目标地址的版本号不为目标版本号、所述第二目标地址不支持载波聚合、所述第二目标地址不支持数据分流、所述第二目标地址后向兼容。
结合第五方面的一些实施例，在一些实施例中，所述接收模块还用于：
至少一个第二目标地址满足第一预设条件，通过多载波接收所述至少一个第二目标地址关联的SL数据；其中，所述第一预设条件包括：所述第二目标地址与载波之间的映射关系为：所述第二目标地址映射到多个载波；和/或，所述第二目标地址对应的第一属性指示以下至少之一：所述第二目标地址的版本号为目标版本号、所述第二目标地址支持载波聚合、所述第二目标地址支持数据分流、所述第二目标地址不后向兼容。
结合第五方面的一些实施例，在一些实施例中，所述接收模块还用于：
全部第二目标地址满足第二预设条件，通过可实现后向兼容的现有载波接收所述至少一个第二目标地址关联的SL数据；其中，所述第二预设条件包括：所述第二目标地址与载波之间的映射关系为：所述第二目标地址映射到一个载波；和/或，所述第二目标地址对应的第一属性指示以下至少之一：所述第二目标地址的版本号不为目标版本号、所述第二目标地址不支持载波聚合、所述第二目标地址不支持数据分流、所述第二目标地址后向兼容；和/或，所述第二预设条件包括：所述第二目标地址与载波之间的映射关系为：所述第二目标地址映射到多个载波；和/或，所述第二目标地址对应的第一属性指示以下至少之一：所述第二目标地址的版本号不为目标版本号、所述第二目标地址不支持载波聚合、所述第二目标地址不支持数据分流、所述第二目标地址后向兼容。
结合第五方面的一些实施例，在一些实施例中，对于第二目标地址，所述第一设备与第二设备配置相 同的第一属性；其中，所述第一设备为所述第二目标地址的发送终端，所述第二设备为所述第二目标地址的接收终端。
第六方面，本公开实施例提出了通信设备，上述通信设备包括：一个或多个处理器；用于存储指令的一个或多个存储器；其中，上述处理器用于调用上述指令以使得上述通信设备执行如第一方面和第二方面、第一方面和第二方面的可选实现方式所描述的通信方法。
第七方面，本公开实施例提出了通信系统，上述通信系统包括：第一设备、第二设备；其中，上述第一设备被配置为执行如第一方面和第一方面的可选实现方式所描述的方法，上述第二设备被配置为执行如第二方面和第二方面的可选实现方式所描述的方法。
第八方面，本公开实施例提出了存储介质，上述存储介质存储有指令，当上述指令在通信设备上运行时，使得上述通信设备执行如第一方面、第一方面的可选实现方式、第二方面和第二方面的可选实现方式所描述的方法。
第九方面，本公开实施例提出了程序产品，上述程序产品被通信设备执行时，使得上述通信设备执行如第一方面、第一方面的可选实现方式、第二方面和第二方面的可选实现方式所描述的方法。
第十方面，本公开实施例提出了计算机程序，当其在计算机上运行时，使得计算机执行如第一方面、第一方面的可选实现方式、第二方面和第二方面的可选实现方式所描述的方法。
可以理解地，上述第一设备、第二设备、通信设备、通信系统、存储介质、程序产品、计算机程序均用于执行本公开实施例所提出的方法。因此，其所能达到的有益效果可以参考对应方法中的有益效果，此处不再赘述。
本公开实施例提出了发明名称。在一些实施例中，通信方法与信息处理方法、信息发送方法、信息接收方法等术语可以相互替换，通信装置与信息处理装置、信息发送装置、信息接收装置等术语可以相互替换，信息处理系统、通信系统、信息发送系统、信息接收系统等术语可以相互替换。
本公开实施例并非穷举，仅为部分实施例的示意，不作为对本公开保护范围的具体限制。在不矛盾的情况下，某一实施例中的每个步骤均可以作为独立实施例来实施，且各步骤之间可以任意组合，例如，在某一实施例中去除部分步骤后的方案也可以作为独立实施例来实施，且在某一实施例中各步骤的顺序可以任意交换，另外，某一实施例中的可选实现方式可以任意组合；此外，各实施例之间可以任意组合，例如，不同实施例的部分或全部步骤可以任意组合，某一实施例可以与其他实施例的可选实现方式任意组合。
在各本公开实施例中，如果没有特殊说明以及逻辑冲突，各实施例之间的术语和/或描述具有一致性，且可以互相引用，不同实施例中的技术特征根据其内在的逻辑关系可以组合形成新的实施例。
本公开实施例中所使用的术语只是为了描述特定实施例的目的，而并非作为对本公开的限制。
在本公开实施例中，除非另有说明，以单数形式表示的元素，如“一个”、“一种”、“该”、“上述”、“所述”、“前述”、“这一”等，可以表示“一个且只有一个”，也可以表示“一个或多个”、“至少一个”等。例如，在翻译中使用如英语中的“a”、“an”、“the”等冠词(article)的情况下，冠词之后的名词可以理解为单数表达形式，也可以理解为复数表达形式。
在本公开实施例中，“多个”是指两个或两个以上。
在一些实施例中，“至少一者(at least one of)”、“至少一项(at least one of)”、“至少一个(at least one of)”、“一个或多个(one or more)”、“多个(a plurality of)”、“多个(multiple)等术语可以相互替换。
本公开实施例中的如“A、B、C……中的至少一者”、“A和/或B和/或C……”等描述方式，包括了A、B、C……中任意一个单独存在的情况，也包括了A、B、C……中任意多个的任意组合情况，每种情况可以单独存在；例如，“A、B、C中的至少一者”包括单独A、单独B、单独C、A和B组合、A和C组合、B和C组合、A和B和C组合的情况；例如，A和/或B包括单独A、单独B、A和B的组合的情况。
在一些实施例中，“在一情况下A，在另一情况下B”、“响应于一情况A，响应于另一情况B”等记载方式，根据情况可以包括以下技术方案：与B无关地执行A，即，在一些实施例中A；与A无关地执行B，即，在一些实施例中B；A和B被选择性执行，即，在一些实施例中从A与B中选择执行；A和B都被执行，即，在一些实施例中A和B。当有A、B、C等更多分支时也类似上述。
本公开实施例中的“第一”、“第二”等前缀词，仅仅为了区分不同的描述对象，不对描述对象的位置、顺序、优先级、数量或内容等构成限制，对描述对象的陈述参见权利要求或实施例中上下文的描述，不应 因为使用前缀词而构成多余的限制。例如，描述对象为“字段”，则“第一字段”和“第二字段”中“字段”之前的序数词并不限制“字段”之间的位置或顺序，“第一”和“第二”并不限制其修饰的“字段”是否在同一个消息中，也不限制“第一字段”和“第二字段”的先后顺序。再如，描述对象为“等级”，则“第一等级”和“第二等级”中“等级”之前的序数词并不限制“等级”之间的优先级。再如，描述对象的数量并不受序数词的限制，可以是一个或者多个，以“第一装置”为例，其中“装置”的数量可以是一个或者多个。此外，不同前缀词修饰的对象可以相同或不同，例如，描述对象为“装置”，则“第一装置”和“第二装置”可以是相同的装置或者不同的装置，其类型可以相同或不同；再如，描述对象为“信息”，则“第一信息”和“第二信息”可以是相同的信息或者不同的信息，其内容可以相同或不同。
在一些实施例中，“包括A”、“包含A”、“用于指示A”、“携带A”，可以解释为直接携带A，也可以解释为间接指示A。
在一些实施例中，“响应于……”、“响应于确定……”、“在……的情况下”、“在……时”、“当……时”、“若……”、“如果……”等术语可以相互替换。
在一些实施例中，“大于”、“大于或等于”、“不小于”、“多于”、“多于或等于”、“不少于”、“高于”、“高于或等于”、“不低于”、“以上”等术语可以相互替换，“小于”、“小于或等于”、“不大于”、“少于”、“少于或等于”、“不多于”、“低于”、“低于或等于”、“不高于”、“以下”等术语可以相互替换。
在一些实施例中，装置等可以解释为实体的、也可以解释为虚拟的，其名称不限定于实施例中所记载的名称，“装置”、“设备(equipment)”、“设备(device)”、“电路”、“网元”、“节点”、“功能”、“单元”、“部件(section)”、“系统”、“网络”、“芯片”、“芯片系统”、“实体”、“主体”等术语可以相互替换。
在一些实施例中，“网络”可以解释为网络中包含的装置(例如，接入网设备、核心网设备等)。
在一些实施例中，“接入网设备(access network device，AN device)”、“无线接入网设备(radio access network device，RAN device)”、“基站(base station，BS)”、“无线基站(radio base station)”、“固定台(fixed station)”、“节点(node)”、“接入点(access point)”、“发送点(transmission point，TP)”、“接收点(reception point，RP)”、“发送接收点(transmission/reception point，TRP)”、“面板(panel)”、“天线面板(antenna panel)”、“天线阵列(antenna array)”、“小区(cell)”、“宏小区(macro cell)”、“小型小区(small cell)”、“毫微微小区(femto cell)”、“微微小区(pico cell)”、“扇区(sector)”、“小区组(cell group)”、“载波(carrier)”、“分量载波(component carrier)”、“带宽部分(bandwidth part，BWP)”等术语可以相互替换。
在一些实施例中，“终端(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)等术语可以相互替换。
在一些实施例中，接入网设备、核心网设备、或网络设备可以被替换为终端。例如，针对将接入网设备、核心网设备、或网络设备以及终端间的通信置换为多个终端间的通信(例如，也可以被称为设备对设备(device-to-device，D2D)、车联网(vehicle-to-everything，V2X)等)的结构，也可以应用本公开的各实施例。在该情况下，也可以设为终端具有接入网设备所具有的全部或部分功能的结构。此外，“上行”、“下行”等语言也可以被替换为与终端间通信对应的语言(例如，“侧行(side)”)。例如，上行信道、下行信道等可以被替换为侧行信道，上行链路、下行链路等可以被替换为侧行链路。
在一些实施例中，终端可以被替换为接入网设备、核心网设备、或网络设备。在该情况下，也可以设为接入网设备、核心网设备、或网络设备具有终端所具有的全部或部分功能的结构。
在一些实施例中，获取数据、信息等可以遵照所在地国家的法律法规。
在一些实施例中，可以在得到用户同意后获取数据、信息等。
此外，本公开实施例的表格中的每一元素、每一行、或每一列均可以作为独立实施例来实施，任意元 素、任意行、任意列的组合也可以作为独立实施例来实施。
本公开中各表所示的对应关系可以被配置，也可以是预定义的。各表中的信息的取值仅仅是举例，可以配置为其他值，本公开并不限定。在配置信息与各参数的对应关系时，并不一定要求必须配置各表中示意出的所有对应关系。例如，本公开中的表格中，某些行示出的对应关系也可以不配置。又例如，可以基于上述表格做适当的变形调整，例如，拆分，合并等等。上述各表中标题示出参数的名称也可以采用通信装置可理解的其他名称，其参数的取值或表示方式也可以通信装置可理解的其他取值或表示方式。上述各表在实现时，也可以采用其他的数据结构，例如可以采用数组、队列、容器、栈、线性表、指针、链表、树、图、结构体、类、堆、散列表或哈希表等。
本公开中的预定义可以理解为定义、预先定义、存储、预存储、预协商、预配置、固化、或预烧制。
为了便于理解，首先介绍本公开涉及的术语。
1、包数据汇聚协议(Packet Data ConvergenceProtocol，PDCP)复用(duplication)
PDCP复用也可称为Packet duplication，可以理解为：把一个PDCP数据包重复发送一次。这样做有两个目的：重复传输，提高数据包传输的可靠性；降低重复发送的时延，满足URLLC(高可靠低时延)要求。可选地，如果没有触发PDCP复用，那么终端会将一个PDCP数据包会传输给终端的一个无线链路控制(Radio Link Control，RLC)实体，RLC实体处理之后再发给终端的媒体接入控制(Medium Access Control，MAC)层，由MAC层完成数据的调度以将PDCP数据包发送至另一终端。如果开启了PDCP复用，那么终端会将一个PDCP数据包会传输给终端的两个RLC实体，分别为Primary RLC实体和Secondary RLC实体，该两个RLC实体会独自处理PDCP数据包并把处理后的数据包传输给终端的MAC层。在MAC层看来，两个RLC实体分别发送的数据包就是两个独立的数据包，MAC无法识别这是不是PDCP复用传过来的包，MAC层只需要按照算法完成数据的调度以将PDCP数据包发送至另一终端。
图1是根据本公开实施例示出的通信系统的架构示意图。如图1所示，通信系统100可以包括第一设备101、第二设备102中的至少之一。第一设备和第二设备分别可以为终端(terminal)、网络设备中的至少之一，可选地，当第一设备与第二设备均为终端时，第一设备与第二设备之间可以进行SL通信。可选地，该网络设备可以包括接入网设备、核心网设备中的至少之一。
在一些实施例中，终端例如包括手机(mobile phone)、可穿戴设备、物联网设备、具备通信功能的汽车、智能汽车、平板电脑(Pad)、带无线收发功能的电脑、虚拟现实(virtual reality，VR)终端设备、增强现实(augmented reality，AR)终端设备、工业控制(industrial control)中的无线终端设备、无人驾驶(self-driving)中的无线终端设备、远程手术(remote medical surgery)中的无线终端设备、智能电网(smart grid)中的无线终端设备、运输安全(transportation safety)中的无线终端设备、智慧城市(smart city)中的无线终端设备、智慧家庭(smart home)中的无线终端设备中的至少一者，但不限于此。
在一些实施例中，接入网设备例如是将终端接入到无线网络的节点或设备，接入网设备可以包括5G通信系统中的演进节点B(evolved NodeB，eNB)、下一代演进节点B(next generation eNB，ng-eNB)、下一代节点B(next generation NodeB，gNB)、节点B(node B，NB)、家庭节点B(home node B，HNB)、家庭演进节点B(home evolved nodeB，HeNB)、无线回传设备、无线网络控制器(radio network controller，RNC)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station，BTS)、基带单元(base band unit，BBU)、移动交换中心、6G通信系统中的基站、开放型基站(Open RAN)、云基站(Cloud RAN)、其他通信系统中的基站、无线保真(wireless fidelity，WiFi)系统中的接入节点中的至少一者，但不限于此。
在一些实施例中，本公开的技术方案可适用于Open RAN架构，此时，本公开实施例所涉及的接入网设备间或者接入网设备内的接口可变为Open RAN的内部接口，这些内部接口之间的流程和信息交互可以通过软件或者程序实现。
在一些实施例中，接入网设备可以由集中单元(central unit，CU)与分布式单元(distributed unit，DU)组成的，其中，CU也可以称为控制单元(control unit)，采用CU-DU的结构可以将接入网设备的协议层拆分开，部分协议层的功能放在CU集中控制，剩下部分或全部协议层的功能分布在DU中，由CU集中 控制DU，但不限于此。
在一些实施例中，核心网设备可以是一个设备，包括一个或多个网元，也可以是多个设备或设备群，分别包括一个或多个网元中的全部或部分。网元可以是虚拟的，也可以是实体的。核心网例如包括演进分组核心(Evolved Packet Core，EPC)、5G核心网络(5G Core Network，5GCN)、下一代核心(Next Generation Core，NGC)中的至少一者。或者，该核心网设备也可以是一种位置管理功能网元。示例性地，位置管理功能网元包括位置服务器(location server)，位置服务器可以实现为以下任意一项：位置管理功能(Location Management Function，LMF)、增强服务的流动定位中心(Enhanced Serving Mobile Location Centre，E-SMLC)、安全用户平面定位(Secure User Plane Location，SUPL)和安全用户平面定位平台(SUPL Location Platform，SUPLLP)。
可以理解的是，本公开实施例描述的通信系统是为了更加清楚的说明本公开实施例的技术方案，并不构成对于本公开实施例提出的技术方案的限定，本领域普通技术人员可知，随着系统架构的演变和新业务场景的出现，本公开实施例提出的技术方案对于类似的技术问题同样适用。
下述本公开实施例可以应用于图1所示的通信系统100、或部分主体，但不限于此。图1所示的各主体是例示，通信系统可以包括图1中的全部或部分主体，也可以包括图1以外的其他主体，各主体数量和形态为任意，各主体之间的连接关系是例示，各主体之间可以不连接也可以连接，其连接可以是任意方式，可以是直接连接也可以是间接连接，可以是有线连接也可以是无线连接。
本公开各实施例可以应用于长期演进(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(注册商标))、CDMA2000、超移动宽带(Ultra Mobile Broadband，UMB)、IEEE 802.11(Wi-Fi(注册商标))、IEEE 802.16(WiMAX(注册商标))、IEEE 802.20、超宽带(Ultra-WideBand，UWB)、蓝牙(Bluetooth(注册商标))、陆上公用移动通信网(Public Land Mobile Network，PLMN)网络、设备到设备(Device-to-Device，D2D)系统、机器到机器(Machine to Machine，M2M)系统、物联网(Internet of Things，IoT)系统、车联网(Vehicle-to-Everything，V2X)、利用其他通信方法的系统、基于它们而扩展的下一代系统等。此外，也可以将多个系统组合(例如，LTE或者LTE-A与5G的组合等)应用。
可选地，在通信系统中，能力受限终端(如：旧版本终端，例如：R16/17的终端)由于发送接收能力限制，可能只能在某一个或者某几个载波上发送或接收SL业务数据，则导致该能力受限终端不支持在多载波上的发送和/或接收，即：不支持载波聚合。因此，在进行SL载波聚合时，针对能力受限终端需要考虑到后向兼容，即：在运用SL载波聚合技术时，需要保证能力受限终端能成功接收到SL业务数据。其中，一种可选的方法为：发送终端基于高层配置的业务到载波/频带的映射来实现后向兼容，可选地，如果某个业务(如广播和/或组播业务)的目标终端(即：某个业务的接收终端)是不支持载波聚合的终端(或称为：能力受限终端)，则只将这个业务的业务数据映射到单载波/频带上(R16/17的载波/频带)进行发送，如果某个业务的目标终端是支持载波聚合的终端(例如R18/19终端)，就将这个业务的业务数据映射到多载波/频带上进行发送。
但是，上述的方法存在不合理处，具体的，在一些实施例之中，能力受限终端可能也需要接收映射到多载波/频带上的业务数据，并且，当能力受限终端接收映射到多载波/频带上的业务数据时，由于能力受限终端不支持载波聚合，则只能在传输该业务数据的多个载波/频带中的支持该能力受限终端接收的载波/频带(即R16/17的载波/频带)上接收业务数据，而无法在传输该业务的多个载波/频带上均接收该业务数据。但是，此时，发送终端可能并不知晓能力受限终端在接收该业务数据，发送终端可能直接在多个载波/频带上做数据分流，即：在多个载波/频带分别发送了该业务数据的不同部分，此时，由于能力受限终端无法在传输该业务数据的多个载波/频带上均接收该业务数据，则可能会造成能力受限终端丢失这个业务的部分数据，导致无法对该能力受限终端实现后向兼容，从而会影响SL通信的稳定性。
图2A是根据本公开实施例示出的通信方法的交互示意图。如图2A所示，本公开实施例涉及通信方法，用于通信系统100，上述方法包括：
步骤2101、第一设备确定至少一个第一目标地址分别对应的第一属性。
可选地，该第一目标地址例如可以为第一目标层2地址。以及，该第一目标地址可以为第一业务关联的目标地址，该第一业务可以为广播业务和/或组播业务。其中，该第一目标地址可以关联有至少一个第一业务，该第一目标地址还关联有SL数据，其中，第一目标地址关联的SL数据可以是第一目标地址关联的至少一个第一业务的SL数据。
可选地，在一些实施例之中，该第一目标地址可以为第一设备感兴趣发送的目标地址。其中，当第一目标地址为第一设备感兴趣发送的目标地址时，第一设备可以为第一目标地址的发送终端，以及，感兴趣接收第一目标地址的接收终端可以称为第二设备。第一设备可以广播和/或组播第一目标地址关联的SL数据。具体的，第一设备可以基于第一目标地址关联的SL数据生成数据包，并且将该数据包的目标地址置为第一目标地址，之后第一设备可以广播和/或组播该数据包，以及，当第二设备接收到该数据包后，通过确定该数据包的目标地址为第一目标地址，则第二设备确定该数据包是感兴趣接收的，从而可以接收并解析该数据包，则实现第一目标地址关联的SL数据的成功传输。
可选地，在另一些实施例之中，该第一目标地址也可以为第一设备感兴趣接收的目标地址。其中，当第一目标地址为第一设备感兴趣接收的目标地址时，第一设备可以为第一目标地址的接收终端，以及，第一目标地址的发送终端可以称为第二设备，该第二设备可以广播和/或组播第一目标地址关联的SL数据。具体的，第二设备会基于第一目标地址关联的SL数据生成数据包，并且将该数据包的目标地址置为第一目标地址，之后第二设备可以广播和/或组播该数据包，以及，当第一设备接收到该数据包后，通过确定该数据包的目标地址为第一目标地址，则第一设备确定该数据包是感兴趣接收的，从而可以接收并解析该数据包，则实现第一目标地址关联的SL数据的成功传输。
可选地，在一些实施例之中，上述的第一属性可以为发送属性(Tx profile)，该第一属性可以用于指示以下至少之一：第一目标地址的版本号、第一目标地址是否支持载波聚合、第一目标地址是否支持数据分流、第一目标地址是否后向兼容。由此可知，该第一目标地址对应的第一属性实质是用于指示第一目标地址是否兼容现有的R16/17终端设备，也就是用于指示现有的R16/17终端设备是否是该第一目标地址的接收终端。可选地，当第一目标地址对应的第一属性指示以下至少之一：第一目标地址的版本号为目标版本号(目标版本号例如为版本R18和/或R19)、第一目标地址支持载波聚合、第一目标地址支持数据分流、第一目标地址不后向兼容，则说明该第一目标地址不兼容现有的R16/17终端设备，也就是说现有的R16/17终端设备不是该第一目标地址的接收终端，此时，认为该第一目标地址的接收终端为支持载波聚合的终端(例如R18或R19终端)。当第一目标地址对应的第一属性指示以下至少之一：第一目标地址的版本号不为目标版本号(例如第一目标地址的版本号不为R18或R19)、第一目标地址不支持载波聚合、第一目标地址不支持数据分流、第一目标地址后向兼容，则说明该第一目标地址兼容现有的R16/17终端设备，也就是说现有的R16/17终端设备是该第一目标地址的接收终端，此时，认为该第一目标地址的接收终端为不支持载波聚合的终端(例如R16或R17终端)。
可选地，第一属性所指示的内容可以有其他命名形式，本公开不作具体限定。可选地，上述的“载波”也可以称为“频带”或者其他名称，本公开不做具体限定。
可选地，在一些实施例之中，当第一设备通过第一目标地址对应的第一属性确定出第一目标地址的接收终端是否为支持载波聚合的终端之后，则后续第一设备可以采用匹配于第一目标地址的接收终端的能力(即第一目标地址的接收终端是否支持载波聚合的能力)的发送方式来发送第一目标地址关联的SL数据，以确保后续第一目标地址的接收终端能够成功接收到第一目标地址关联的SL数据，由此，当第一目标地址的接收终端为不支持载波聚合的终端时，可以实现对于第一目标地址的接收终端的后向兼容，确保SL数据的成功发送，保证SL通信的稳定性。
可选地，在一些实施例之中，上述的第一属性可以是第一设备的高层配置的，例如可以是第一设备的车联网(Vehicle-to-Everything，V2X)层配置的。在一些实施例中，第一设备的高层将配置的第一属性指示至接入(Access Stratum，AS)层的。
可选地，在一些实施例之中，该第一属性可以是按照业务粒度配置；示例性的，第一终端的高层按照业务粒度配置第一属性，第一终端的高层将一个或者多个业务的第一属性指示给AS层。其中，一个第一业务对应一个第一属性，不同第一业务对应的第一属性可以相同或不同，一个第一目标地址可以关联至少一个第一业务。其中，当第一属性按照业务粒度配置时，第一设备可以基于第一目标地址关联的至少一个第一业务对应的第一属性确定第一目标地址对应的第一属性。具体的，当第一目标地址关联的所有第一业务对应的第一属性均指示以下至少之一：版本号为目标版本号、支持载波聚合、支持数据分流、不后向兼容，则第一设备确定第一目标地址对应的第一属性为以下至少之一：第一目标地址的版本号为目标版本号、第一目标地址支持载波聚合、第一目标地址支持数据分流、第一目标地址不后向兼容。当第一目标地址关联的至少一个第一业务对应的第一属性指示以下至少之一：版本号不为目标版本号、不支持载波聚合、不支持数据分流、后向兼容，则第一设备确定第一目标地址对应的第一属性为以下至少之一：第一目标地址的版本号不为目标版本号、第一目标地址不支持载波聚合、第一目标地址不支持数据分流、第一目标地址后向兼容。
可选地，在另一些实施例之中，第一属性可以是按照目标地址粒度配置的；示例性的，第一终端的高层按照目标地址粒度配置第一属性，第一终端的高层将一个或者多个目标地址的第一属性指示给AS层。其中，第一目标地址可以对应一个第一属性。可选地，当第一属性是按照目标地址粒度配置时，则可以认为第一目标地址对应的所有第一业务所关联的第一属性都相同，均为该第一目标地址对应的第一属性。
可选地，在一些实施例之中，也有可能未对第一目标地址配置第一属性，此时，第一目标地址没有关联的第一属性，则确定以下至少之一：第一目标地址的版本号不为目标版本号、第一目标地址不支持载波聚合、第一目标地址不支持数据分流、第一目标地址后向兼容。
可选地，在一些实施例之中，对于第一目标地址，第一设备与第二设备配置相同的第一属性；也即是，应当使得第一设备的高层配置的第一目标地址的第一属性与第二设备的高层配置的第一目标地址的第一属性相同，由此以统一第一设备和第二设备对于第一目标地址的第一属性的理解，从而可以确保第一设备与第二设备后续可以基于统一理解的第一目标地址的第一属性来在第一设备与第二设备之间成功传输第一目标地址关联的SL数据，确保SL通信的稳定性。
步骤2102、第一设备基于高层配置确定第一目标地址与载波之间的映射关系。
可选地，在一些实施例之中，高层可以配置业务与目标地址之间的关系和/或业务与载波之间的关系，则第一设备基于业务与目标地址之间的关系和/或业务与载波之间的关系即可确定出目标地址与载波之间的映射关系。具体的，第一设备基于高层配置的第一业务与第一目标地址之间的关系和/或第一业务与载波之间的关系，即可确定出第一目标地址与载波之间的映射关系。第一业务可以为广播业务和/或组播业务
可选地，在一些实施例之中，当第一目标地址与载波之间的映射关系为：第一目标地址映射到一个载波上时，说明第一目标地址支持单载波映射。
可选地，在另一些实施例之中，当第一目标地址与载波之间的映射关系为：第一目标地址映射到多个载波上时，说明第一目标地址支持多载波映射。
步骤2103、第一目标地址与载波之间的映射关系为：第一目标地址映射到多个载波；和/或，第一目标地址对应的第一属性指示以下至少之一：第一目标地址的版本号为目标版本号、第一目标地址支持载波聚合、第一目标地址支持数据分流、第一目标地址不后向兼容；通过多载波分流和/或包数据汇聚协议(Packet Data ConvergenceProtocol，PDCP)复用(duplication)发送第一目标地址关联的SL数据。
可选地，在一些实施例之中，当第一目标地址与载波之间的映射关系为：第一目标地址映射到多个载波；和/或，第一目标地址对应的第一属性指示以下至少之一：第一目标地址的版本号为目标版本号、第一目标地址支持载波聚合、第一目标地址支持数据分流、第一目标地址不后向兼容时，则说明第一目标地址支持多载波映射，且第一目标地址不兼容现有的R16/17终端设备，也就是说现有的R16/17终端设备不是该第一目标地址的接收终端，第二设备(即第一目标地址的接收终端)支持载波聚合(也即是支持多载波接收)，则第一设备可以通过多载波分流和/或PDCP复用来发送第一目标地址关联的SL数据。
可选地，以下对第一设备如何通过多载波分流和/或PDCP复用来发送第一目标地址关联的SL数据的方法进行介绍。
可选地，第一目标地址可以关联有至少一个侧行链路承载(Sidelink Radio Bearer，SLRB)，该SLRB 与一个或者多个第一业务关联，第一业务可以为广播业务和/或组播业务。其中，该SLRB还可以关联有SL数据，SLRB关联的SL数据可以为：第一目标地址关联的SL数据中对应于该SLRB的一个或者多个第一业务的数据。可选地，该SLRB可以用于传输SLRB关联的SL数据。
在一些实施例之中，第一目标地址关联的至少一个SLRB对应有SLRB配置，通过该SLRB配置可以指示对应的SLRB是否激活PDCP复用，具体的通过该SLRB配置中的PDCP配置指示对应的SLRB是否激活PDCP复用。其中，该SLRB配置可以是网络设备通过专用信令发送至第一设备的；或者，该SLRB配置可以是网络设备通过系统信息块(System Information Blocks，SIB)发送至第一设备的，或者，该SLRB配置可以是预配置的。其中，处于无线资源控制(Radio Resource Control，RRC)连接态的第一设备可以通过专用信令获取该SLRB配置，处于RRC空闲态(IDLE)或去激活态(INACTIVE)的第一设备可以通过SIB获取该SLRB配置，处于覆盖范围外(outofcoverage，OOC)的第一设备可以通过预配置获取该SLRB配置。可选地，第一目标地址关联的且被配置激活PDCP复用的SLRB可以为第一SLRB，第一SLRB可以为一个或者多个，第一目标地址关联的且被配置去激活PDCP复用的SLRB可以为第二SLRB，第二SLRB可以为一个或者多个。
可选地，针对第一SLRB，第一设备可以通过PDCP复用发送第一SLRB关联的SL数据。可选地，第一设备可以在第一目标地址映射的多个载波中选择2个载波分别发送第一SLRB关联的相同的SL数据。例如，第一设备可以在第一目标地址映射的多个载波中选择2个载波分别发送第一SLRB关联的相同的SL数据，示例性的，第一设备可以根据实现在多个载波中选择2个载波分别发送第一SLRB关联的相同的SL数据；或者，在第一目标地址映射的多个载波中选择质量最高的2个载波分别发送第一SLRB关联的相同的SL数据，示例性的，第一设备可以在多个载波中任意选择2个信道占用率(channel busy ratio，CBR)最低的载波分别发送第一SLRB关联的相同的SL数据。示例的，第一设备可以在载波1，2上均发送第一SLRB关联的SL数据A。
可选地，针对第二SLRB，第一设备可以通过多载波分流发送第二SLRB关联的SL数据。可选地，第一设备可以在第一目标地址映射的多个载波上发送第二SLRB关联的不同的SL数据，例如在载波1，2，3上分别发送第二SLRB关联的SL数据A、第二SLRB关联的SL数据B、第二SLRB关联的SL数据C。
本公开实施例所涉及的通信方法可以包括步骤S2101～步骤S2103中的至少一者。例如，步骤S2101可以作为独立实施例来实施，步骤S2102可以作为独立实施例来实施，步骤S2103可以作为独立实施例来实施，步骤S2101+S2102可以作为独立实施例来实施，但不限于此。
在本实施方式或实施例中，在不矛盾的情况下，各步骤可以独立、任意组合或交换顺序，可选方式或可选例可以任意组合，且可以与其他实施方式或其他实施例的任意步骤之间进行任意组合。
图2B是根据本公开实施例示出的通信方法的交互示意图。如图2B所示，本公开实施例涉及通信方法，用于通信系统100，上述方法包括：
步骤2201、第一设备确定至少一个第一目标地址分别对应的第一属性。
步骤2202、第一设备基于高层配置确定第一目标地址与载波之间的映射关系。
关于步骤2201-2202的详细介绍可以参考上述实施例描述。
步骤2203、第一目标地址与载波之间的映射关系为：第一目标地址映射到多个载波；和/或，第一目标地址对应的第一属性指示以下至少之一：第一目标地址的版本号不为目标版本号、第一目标地址不支持载波聚合、第一目标地址不支持数据分流、第一目标地址后向兼容；通过单载波和/或PDCP复用发送第一目标地址关联的SL数据。
可选地，在一些实施例之中，当第一目标地址与载波之间的映射关系为：第一目标地址映射到多个载波；和/或，第一目标地址对应的第一属性指示以下至少之一：第一目标地址的版本号不为目标版本号、第一目标地址不支持载波聚合、第一目标地址不支持数据分流、第一目标地址后向兼容时，说明第一目标地址支持多载波映射，且第一目标地址兼容现有的R16/17终端设备，也就是说现有的R16/17终端设备是该第一目标地址的接收终端，第二设备(即第一目标地址的接收终端)包含不支持载波聚合(也即是不支持多载波接收)的R16/17终端，则第一设备可以通过单载波和/或PDCP复用来发送第一目标地址关联的SL数据。
可选地，在一些实施例之中，针对第一SLRB，第一设备可以通过PDCP复用发送第一SLRB关联的 SL数据。可选地，第一设备可以在第一目标地址映射的多个载波中选择2个载波分别发送第一SLRB关联的相同的SL数据。例如，第一设备可以在第一目标地址映射的多个载波中选择可实现后向兼容的现有载波(如legacy载波，也就是R16/17终端支持的legacy载波)和一个其他载波分别发送第一SLRB关联的相同的SL数据。可选地，该其他载波可以为除可实现后向兼容的现有载波之外的一个载波，示例性的，第一设备可以根据实现在除现有载波之外的多个载波中选择一个载波；或者，可以为除可实现后向兼容的现有载波之外的质量最高的载波，示例性的，第一设备可以在除现有载波之外的多个载波中选择一个CBR最低的载波。
需要说明的是，在一些实施例之中，由前述的“PDCP复用”的解释内容可知，在PDCP复用时会将一个PDCP数据包传输给终端的两个RLC实体，分别为Primary RLC实体和Secondary RLC实体，该两个RLC实体会独自处理PDCP数据包并把处理后的数据包传输给终端的MAC层。其中，该两个RLC实体独自处理得到的两个PDCP数据包可以分别关联不同的逻辑信道标识(logical channel IDentity，LCID)，以通过该PDCP数据包所关联的LCID对应的逻辑信道来发送该PDCP数据包。可选地，在一些实施例之中，其中一个PDCP数据包可以关联现有的LCID(例如4-19)，以通过现有的LCID对应的逻辑信道来发送，另外一个PDCP数据包可以关联预留的LCID，以通过预留的逻辑信道来发送。
基于此，在一些实施例之中，当第一设备通过PDCP复用发送第一SLRB关联的SL数据时，第一设备可以将第一SLRB关联的SL数据所对应的关联现有的LCID的数据包在可实现后向兼容的现有载波(如legacy载波，也就是R16/17终端支持的legacy载波)上发送，将第一SLRB关联的SL数据对应的关联预留的LCID的数据包在上述的其他载波上发送。
可选地，针对第二SLRB，第一设备可以通过可实现后向兼容的现有载波发送第二SLRB关联的SL数据。
关于步骤2202-2203的其他详细介绍可以参考上述实施例描述。
本公开实施例所涉及的通信方法可以包括步骤S2201～步骤S2203中的至少一者。例如，步骤S2201可以作为独立实施例来实施，步骤S2202可以作为独立实施例来实施，步骤S2203可以作为独立实施例来实施，步骤S2201+S2202可以作为独立实施例来实施，但不限于此。
在本实施方式或实施例中，在不矛盾的情况下，各步骤可以独立、任意组合或交换顺序，可选方式或可选例可以任意组合，且可以与其他实施方式或其他实施例的任意步骤之间进行任意组合。
图2C是根据本公开实施例示出的通信方法的交互示意图。如图2C所示，本公开实施例涉及通信方法，用于通信系统100，上述方法包括：
步骤2301、第一设备确定至少一个第一目标地址分别对应的第一属性。
步骤2302、第一设备基于高层配置确定第一目标地址与载波之间的映射关系。
步骤2303、第一目标地址与载波之间的映射关系为：第一目标地址映射到一个载波；和/或，第一目标地址对应的第一属性指示以下至少之一：第一目标地址的版本号为目标版本号、第一目标地址支持载波聚合、第一目标地址支持数据分流、第一目标地址不后向兼容；通过单载波发送第一目标地址关联的SL数据。
可选地，在一些实施例之中，当第一目标地址与载波之间的映射关系为：第一目标地址映射到一个载波；和/或，第一目标地址对应的第一属性指示以下至少之一：第一目标地址的版本号为目标版本号、第一目标地址支持载波聚合、第一目标地址支持数据分流、第一目标地址不后向兼容时，则说明第一目标地址支持单载波映射，且第一目标地址不兼容现有的R16/17终端设备，也就是说现有的R16/17终端设备不是该第一目标地址的接收终端，第二设备(即第一目标地址的接收终端)是支持载波聚合的(也即是支持多载波接收的)终端。其中，虽然第一目标地址不后向兼容，但是，由于第一目标地址是支持单载波映射，不支持多载波映射，因此此时，第一设备不能通过多载波来发送第一目标地址关联的SL数据，而需通过单载波来发送第一目标地址关联的SL数据，例如，可以通过可实现后向兼容的现有载波(如legacy载波，也就是R16/17终端支持的legacy载波)发送第一目标地址关联的SL数据。
关于步骤2301-2303的其他详细介绍可以参考上述实施例描述。
本公开实施例所涉及的通信方法可以包括步骤S2301～步骤S2303中的至少一者。例如，步骤S2301可以作为独立实施例来实施，步骤S2302可以作为独立实施例来实施，步骤S2303可以作为独立实施例来 实施，步骤S2301+S2302可以作为独立实施例来实施，但不限于此。
在本实施方式或实施例中，在不矛盾的情况下，各步骤可以独立、任意组合或交换顺序，可选方式或可选例可以任意组合，且可以与其他实施方式或其他实施例的任意步骤之间进行任意组合。
图2D是根据本公开实施例示出的通信方法的交互示意图。如图2D所示，本公开实施例涉及通信方法，用于通信系统100，上述方法包括：
步骤2401、第一设备确定至少一个第一目标地址分别对应的第一属性。
步骤2402、第一设备基于高层配置确定第一目标地址与载波之间的映射关系。
步骤2403、第一目标地址与载波之间的映射关系为：第一目标地址映射到一个载波；和/或，第一目标地址对应的第一属性指示以下至少之一：第一目标地址的版本号不为目标版本号、第一目标地址不支持载波聚合、第一目标地址不支持数据分流、第一目标地址后向兼容；通过单载波发送第一目标地址关联的SL数据。
可选地，在一些实施例之中，当第一目标地址与载波之间的映射关系为：第一目标地址映射到一个载波；和/或，第一目标地址对应的第一属性指示以下至少之一：第一目标地址的版本号为目标版本号、第一目标地址支持载波聚合、第一目标地址支持数据分流、第一目标地址后向兼容时，则说明第一目标地址支持单载波映射，且第一目标地址兼容现有的R16/17终端设备，也就是说现有的R16/17终端设备是该第一目标地址的接收终端，第二设备(即第一目标地址的接收终端)包含不支持载波聚合的(也即是不支持多载波接收的)的R16/17终端，此时，第一设备可以通过单载波来发送第一目标地址关联的SL数据，例如，可以通过可实现后向兼容的现有载波(如legacy载波，也就是R16/17终端支持的legacy载波)发送第一目标地址关联的SL数据。
关于步骤2401-2403的其他详细介绍可以参考上述实施例描述。
本公开实施例所涉及的通信方法可以包括步骤S2401～步骤S2403中的至少一者。例如，步骤S2401可以作为独立实施例来实施，步骤S2402可以作为独立实施例来实施，步骤S2403可以作为独立实施例来实施，步骤S2401+S2402可以作为独立实施例来实施，但不限于此。
在本实施方式或实施例中，在不矛盾的情况下，各步骤可以独立、任意组合或交换顺序，可选方式或可选例可以任意组合，且可以与其他实施方式或其他实施例的任意步骤之间进行任意组合。
图3A是根据本公开实施例示出的通信方法的交互示意图。如图3A所示，本公开实施例涉及通信方法，用于第一设备101，上述方法包括：
步骤3101、第一设备确定至少一个第一目标地址分别对应的第一属性。
步骤3102、第一设备基于高层配置确定第一目标地址与载波之间的映射关系。
步骤3103、第一目标地址与载波之间的映射关系为：第一目标地址映射到多个载波；和/或，第一目标地址对应的第一属性指示以下至少之一：第一目标地址的版本号为目标版本号、第一目标地址支持载波聚合、第一目标地址支持数据分流、第一目标地址不后向兼容；通过多载波分流和/或PDCP复用发送第一目标地址关联的SL数据。
关于步骤3101-3103的详细介绍可以参考上述实施例描述。
本公开实施例所涉及的通信方法可以包括步骤S3101～步骤S3103中的至少一者。例如，步骤S3101可以作为独立实施例来实施，步骤S3102可以作为独立实施例来实施，步骤S3101+S3102可以作为独立实施例来实施，但不限于此。
在本实施方式或实施例中，在不矛盾的情况下，各步骤可以独立、任意组合或交换顺序，可选方式或可选例可以任意组合，且可以与其他实施方式或其他实施例的任意步骤之间进行任意组合。
图3B是根据本公开实施例示出的通信方法的交互示意图。如图3B所示，本公开实施例涉及通信方法，用于第一设备101，上述方法包括：
步骤3201、第一设备确定至少一个第一目标地址分别对应的第一属性。
步骤3202、第一设备基于高层配置确定第一目标地址与载波之间的映射关系。
步骤3203、第一目标地址与载波之间的映射关系为：第一目标地址映射到多个载波；和/或，第一目标地址对应的第一属性指示以下至少之一：第一目标地址的版本号不为目标版本号、第一目标地址不支持载波聚合、第一目标地址不支持数据分流、第一目标地址后向兼容；第一设备通过单载波和/或PDCP复用 发送所述第一目标地址关联的SL数据。
关于步骤3201-3203的详细介绍可以参考上述实施例描述。
本公开实施例所涉及的通信方法可以包括步骤S3201～步骤S3203中的至少一者。例如，步骤S3201可以作为独立实施例来实施，步骤S3202可以作为独立实施例来实施，但不限于此。
在本实施方式或实施例中，在不矛盾的情况下，各步骤可以独立、任意组合或交换顺序，可选方式或可选例可以任意组合，且可以与其他实施方式或其他实施例的任意步骤之间进行任意组合。
图3C是根据本公开实施例示出的通信方法的交互示意图。如图3C所示，本公开实施例涉及通信方法，用于第一设备101，上述方法包括：
步骤3301、第一设备确定至少一个第一目标地址分别对应的第一属性。
步骤3302、第一设备基于高层配置确定第一目标地址与载波之间的映射关系。
步骤3303、第一目标地址与载波之间的映射关系为：第一目标地址映射到一个载波；和/或，第一目标地址对应的第一属性指示以下至少之一：第一目标地址的版本号为目标版本号、第一目标地址支持载波聚合、第一目标地址支持数据分流、第一目标地址不后向兼容；第一设备通过单载波发送第一目标地址关联的SL数据。
关于步骤3301-3303的详细介绍可以参考上述实施例描述。
本公开实施例所涉及的通信方法可以包括步骤S3301～步骤S3303中的至少一者。例如，步骤S3301可以作为独立实施例来实施，步骤S3302可以作为独立实施例来实施，步骤S3301+S3302可以作为独立实施例来实施，但不限于此。
在本实施方式或实施例中，在不矛盾的情况下，各步骤可以独立、任意组合或交换顺序，可选方式或可选例可以任意组合，且可以与其他实施方式或其他实施例的任意步骤之间进行任意组合。
图3D是根据本公开实施例示出的通信方法的交互示意图。如图3D所示，本公开实施例涉及通信方法，用于第一设备101，上述方法包括：
步骤3401、第一设备确定至少一个第一目标地址分别对应的第一属性。
步骤3402、第一设备基于高层配置确定第一目标地址与载波之间的映射关系。
步骤3403、第一目标地址与载波之间的映射关系为：第一目标地址映射到一个载波；和/或，第一目标地址对应的第一属性指示以下至少之一：第一目标地址的版本号不为目标版本号、第一目标地址不支持载波聚合、第一目标地址不支持数据分流、第一目标地址后向兼容；第一设备通过单载波发送第一目标地址关联的SL数据。
关于步骤3401-3403的详细介绍可以参考上述实施例描述。
本公开实施例所涉及的通信方法可以包括步骤S3401～步骤S3403中的至少一者。例如，步骤S3401可以作为独立实施例来实施，步骤S3402可以作为独立实施例来实施，但不限于此。
在本实施方式或实施例中，在不矛盾的情况下，各步骤可以独立、任意组合或交换顺序，可选方式或可选例可以任意组合，且可以与其他实施方式或其他实施例的任意步骤之间进行任意组合。
图3E是根据本公开实施例示出的通信方法的交互示意图。如图3E所示，本公开实施例涉及通信方法，用于第一设备101，上述方法包括：
步骤3501、第一设备基于第一目标地址与载波之间的映射关系、第一目标地址对应的第一属性中的至少之一发送第一目标地址关联的SL数据。
可选地，所述第一目标地址对应的第一属性用于指示以下至少之一：所述第一目标地址的版本号、所述第一目标地址是否支持载波聚合、所述第一目标地址是否支持数据分流、所述第一目标地址是否后向兼容；其中，所述第一目标地址为广播业务和/或组播业务关联的目标地址，所述第一目标地址为所述第一设备感兴趣发送和/或接收的目标地址。
可选地，所述方法还包括：
第一设备确定至少一个第一目标地址分别对应的第一属性。
可选地，所述第一属性按照业务粒度配置；其中，一个第一业务对应一个第一属性，所述第一目标地址关联至少一个第一业务；所述第一业务包括广播业务和/或组播业务；或者
所述第一属性按照目标地址粒度配置；其中，所述第一目标地址对应一个第一属性。
可选地，所述确定至少一个第一目标地址分别对应的第一属性，包括：
所述第一属性按照业务粒度配置，基于所述第一目标地址关联的至少一个第一业务对应的第一属性确定所述第一目标地址对应的第一属性。
可选地，所述基于所述第一目标地址关联的至少一个第一业务对应的第一属性确定所述第一目标地址对应的第一属性，包括：
所述第一目标地址关联的所有第一业务对应的第一属性均指示以下至少之一：版本号为目标版本号、支持载波聚合、支持数据分流、不后向兼容，确定所述第一目标地址对应的第一属性为以下至少之一：所述第一目标地址的版本号为所述目标版本号、所述第一目标地址支持载波聚合、所述第一目标地址支持数据分流、所述第一目标地址不后向兼容。
可选地，所述方法还包括：
所述第一目标地址不存在对应的第一属性，确定以下至少之一：所述第一目标地址的版本号不为目标版本号、所述第一目标地址不支持载波聚合、所述第一目标地址不支持数据分流、所述第一目标地址后向兼容。
可选地，所述基于所述第一目标地址与载波之间的映射关系、所述第一目标地址对应的第一属性中的至少之一发送所述第一目标地址关联的SL数据，包括：
所述第一目标地址与载波之间的映射关系为：所述第一目标地址映射到多个载波；和/或，所述第一目标地址对应的第一属性指示以下至少之一：所述第一目标地址的版本号为目标版本号、所述第一目标地址支持载波聚合、所述第一目标地址支持数据分流、所述第一目标地址不后向兼容；通过多载波分流和/或包数据汇聚协议PDCP复用duplication发送所述第一目标地址关联的SL数据。
可选地，所述基于所述第一目标地址与载波之间的映射关系、所述第一目标地址对应的第一属性中的至少之一发送所述第一目标地址关联的SL数据，包括：
所述第一目标地址与载波之间的映射关系为：所述第一目标地址映射到多个载波；和/或，所述第一目标地址对应的第一属性指示以下至少之一：所述第一目标地址的版本号不为目标版本号、所述第一目标地址不支持载波聚合、所述第一目标地址不支持数据分流、所述第一目标地址后向兼容；通过单载波和/或PDCP复用发送所述第一目标地址关联的SL数据。
可选地，所述基于所述第一目标地址与载波之间的映射关系、所述第一目标地址对应的第一属性中的至少之一发送所述第一目标地址关联的SL数据，包括：
所述第一目标地址与载波之间的映射关系为：所述第一目标地址映射到一个载波；和/或，所述第一目标地址对应的第一属性指示以下至少之一：所述第一目标地址的版本号为目标版本号、所述第一目标地址支持载波聚合、所述第一目标地址支持数据分流、所述第一目标地址不后向兼容；通过单载波发送所述第一目标地址关联的SL数据。
可选地，所述基于所述第一目标地址与载波之间的映射关系、所述第一目标地址对应的第一属性中的至少之一发送所述第一目标地址关联的SL数据，包括：
所述第一目标地址与载波之间的映射关系为：所述第一目标地址映射到一个载波；和/或，所述第一目标地址对应的第一属性指示以下至少之一：所述第一目标地址的版本号不为目标版本号、所述第一目标地址不支持载波聚合、所述第一目标地址不支持数据分流、所述第一目标地址后向兼容；通过单载波发送所述第一目标地址关联的SL数据。
可选地，所述通过PDCP复用发送所述第一目标地址关联的SL数据，包括：
通过PDCP复用发送第一SLRB关联的SL数据；其中，所述第一SLRB为第一目标地址关联的且激活了PDCP复用的SLRB，所述第一SLRB为一个或者多个。
可选地，所述通过PDCP复用发送第一SLRB关联的SL数据，包括：
在所述第一目标地址映射的所述多个载波中选择2个载波分别发送所述第一SLRB关联的相同的SL数据。
可选地，所述在所述第一目标地址映射的所述多个载波中选择2个载波分别发送所述第一SLRB关联的相同的SL数据，包括：
在所述第一目标地址映射的多个载波中任意选择2个载波分别发送所述第一SLRB关联的相同的SL 数据。
可选地，所述通过多载波分流发送所述第一目标地址关联的SL数据，包括：
通过所述第一目标地址映射的所述多个载波分流发送第二SLRB关联的SL数据；其中，所述第二SLRB为第一目标地址关联的且去激活PDCP复用的SLRB，所述第二SLRB为一个或者多个。
可选地，所述通过多载波分流发送第二SLRB关联的SL数据，包括：
在所述第一目标地址映射的多个载波上发送所述第二SLRB关联的不同的SL数据。
可选地，所述通过PDCP复用发送所述第一目标地址关联的SL数据，包括：
通过PDCP复用发送第一SLRB关联的SL数据；其中，所述第一SLRB为第一目标地址关联的且激活了PDCP复用的SLRB，所述第一SLRB为一个或者多个。
可选地，所述通过PDCP复用发送第一SLRB关联的SL数据，包括：
在所述第一目标地址映射的所述多个载波中选择2个载波分别发送所述第一SLRB关联的相同的SL数据。
可选地，所述在所述第一目标地址映射的所述多个载波中选择2个载波分别发送所述第一SLRB关联的相同的SL数据，包括：
在所述第一目标地址映射的多个载波中选择可实现后向兼容的现有载波和任意一个其他载波分别发送所述第一SLRB关联的相同的SL数据。
可选地，所述通过单载波发送所述第一目标地址关联的SL数据，包括：
通过可实现后向兼容的现有载波发送第二SLRB关联的SL数据；其中，所述第二SLRB为第一目标地址关联的且去激活PDCP复用的SLRB，所述第二SLRB为一个或者多个。
可选地，所述通过单载波发送所述第一目标地址关联的SL数据，包括：
通过可实现后向兼容的现有载波发送所述第一目标地址关联的SL数据。
可选地，所述方法还包括：
确定至少一个第一SLRB和/或至少一个第二SLRB分别对应的SLRB配置，所述至少一个第一SLRB和/或至少一个第二SLRB分别对应的SLRB配置用于配置所述至少一个第一SLRB和/或至少一个第二SLRB是否激活PDCP复用；
根据所述至少一个第一SLRB和/或至少一个第二SLRB分别对应的SLRB配置确定所述第一目标地址关联的所述至少一个第一SLRB和/或至少一个第二SLRB是否激活PDCP复用。
可选地，所述确定至少一个第一SLRB和/或至少一个第二SLRB分别对应的SLRB配置，包括以下至少之一：
获取通过专用信令发送的所述至少一个第一SLRB和/或至少一个第二SLRB分别对应的SLRB配置；
获取通过系统信息块SIB发送的所述至少一个第一SLRB和/或至少一个第二SLRB分别对应的SLRB配置；
获取预配置的所述至少一个第一SLRB和/或至少一个第二SLRB分别对应的SLRB配置。
可选地，所述方法还包括：
基于高层配置确定所述第一目标地址与载波之间的映射关系。
可选地，对于第一目标地址，所述第一设备与第二设备配置相同的第一属性；其中，所述第一设备为所述第一目标地址的发送终端，所述第二设备所述第一目标地址的接收终端。
可选地，所述目标版本号为R18。
关于步骤3501的详细介绍可以参考上述实施例的内容。
在本实施方式或实施例中，在不矛盾的情况下，各步骤可以独立、任意组合或交换顺序，可选方式或可选例可以任意组合，且可以与其他实施方式或其他实施例的任意步骤之间进行任意组合。
图4A是根据本公开实施例示出的通信方法的交互示意图。如图4A所示，本公开实施例涉及通信方法，用于第二设备102，上述方法包括：
步骤4101、第二设备确定至少一个第二目标地址分别对应的第一属性。
可选地，该第二目标地址例如可以为第二目标层2地址。以及，该第二目标地址可以为第二业务关联的目标地址，该第二业务可以为广播业务和/或组播业务。其中，该第二目标地址可以关联有至少一个第二 业务，该第二目标地址还关联有SL数据，其中，第二目标地址关联的SL数据可以是第二目标地址关联的至少一个第二业务的SL数据。
可选地，在一些实施例之中，该第二目标地址可以为第二设备感兴趣发送和/或感兴趣接收的目标地址。其中，当第二目标地址为第二设备感兴趣发送的目标地址，或者，当第二目标地址为第二设备感兴趣接收的目标地址时，与前述的“第一目标地址为第一设备感兴趣发送的目标地址，或者，第一目标地址为第一设备感兴趣接收的目标地址”的原理相同，此处不再赘述。
以及，上述的第一目标地址的相关介绍同样适用于介绍第二目标地址，此处不再赘述。
步骤4102、第二设备基于高层配置确定第二目标地址与载波之间的映射关系。
关于步骤4102的详细介绍可以参考上述步骤2102描述。
步骤4103、至少一个第二目标地址满足第一预设条件，第二设备通过多载波接收至少一个第二目标地址关联的SL数据。
可选地，该第一预设条件可以包括：第二目标地址与载波之间的映射关系为：第二目标地址映射到多个载波；和/或，第二目标地址对应的第一属性指示以下至少之一：第二目标地址的版本号为目标版本号、第二目标地址支持载波聚合、第二目标地址支持数据分流、第二目标地址不后向兼容。
可选地，在一些实施例之中，第二设备在接收至少一个第二目标地址关联的SL数据时，若至少一个第二目标地址满足第一预设条件，则说明至少一个第二目标地址关联的SL数据是通过多个载波发送的，此时，第二设备也应相应的通过多载波接收至少一个第二目标地址关联的SL数据。
关于步骤4101-4103的详细介绍可以参考上述实施例的内容。
本公开实施例所涉及的通信方法可以包括步骤S4101～步骤S4103中的至少一者。例如，步骤S4101可以作为独立实施例来实施，步骤S4102可以作为独立实施例来实施，但不限于此。
在本实施方式或实施例中，在不矛盾的情况下，各步骤可以独立、任意组合或交换顺序，可选方式或可选例可以任意组合，且可以与其他实施方式或其他实施例的任意步骤之间进行任意组合。
图4B是根据本公开实施例示出的通信方法的交互示意图。如图4B所示，本公开实施例涉及通信方法，用于第二设备102，上述方法包括：
步骤4201、第二设备确定至少一个第二目标地址分别对应的第一属性。
步骤4102、第二设备基于高层配置确定第二目标地址与载波之间的映射关系。
步骤4203、全部第二目标地址满足第二预设条件，通过可实现后向兼容的现有载波接收至少一个第二目标地址关联的SL数据。
其中，第二预设条件包括：第二目标地址与载波之间的映射关系为：第二目标地址映射到一个载波；和/或，第二目标地址对应的第一属性指示以下至少之一：第一目标地址的版本号不为目标版本号、第二目标地址不支持载波聚合、第二目标地址不支持数据分流、第二目标地址后向兼容。和/或，第二预设条件包括：所述第二目标地址与载波之间的映射关系为：所述第二目标地址映射到多个载波；和/或，所述第二目标地址对应的第一属性指示以下至少之一：所述第二目标地址的版本号不为目标版本号、所述第二目标地址不支持载波聚合、所述第二目标地址不支持数据分流、所述第二目标地址后向兼容。
可选地，第二设备在接收至少一个第二目标地址关联的SL数据时，若全部第二目标地址满足第二预设条件，则说明全部第二目标地址关联的SL数据均是通过可实现后向兼容的现有载波发送的，此时，第二设备也应相应的通过可实现后向兼容的现有载波接收至少一个第二目标地址关联的SL数据。
关于步骤4201-4203的详细介绍可以参考上述实施例的内容。
本公开实施例所涉及的通信方法可以包括步骤S4201～步骤S4203中的至少一者。例如，步骤S4201可以作为独立实施例来实施，步骤S4202可以作为独立实施例来实施，但不限于此。
在本实施方式或实施例中，在不矛盾的情况下，各步骤可以独立、任意组合或交换顺序，可选方式或可选例可以任意组合，且可以与其他实施方式或其他实施例的任意步骤之间进行任意组合。
图4C是根据本公开实施例示出的通信方法的交互示意图。如图4C所示，本公开实施例涉及通信方法，用于第二设备102，上述方法包括：
步骤4301、第二设备基于第二目标地址与载波之间的映射关系、第二目标地址对应的第一属性中的至少之一在一个或多个载波上接收SL数据。
可选地，第二目标地址对应的第一属性用于指示以下至少之一：第二目标地址的版本号、第二目标地址是否支持载波聚合、第二目标地址是否支持数据分流、第二目标地址是否后向兼容；第二目标地址为广播业务和/或组播业务关联的目标地址，第二目标地址为所述第二设备感兴趣发送和/或接收的目标地址。
可选地，所述方法还包括：
第二设备确定至少一个第二目标地址分别对应的第一属性。
可选地，第一属性按照业务粒度配置；其中，一个第二业务对应一个第一属性，所述第二目标地址关联至少一个第二业务；所述第二业务包括广播业务和/或组播业务；或者
所述第一属性按照目标地址粒度配置；其中，所述第二目标地址对应一个第一属性。
可选地，所述确定至少一个第二目标地址分别对应的第一属性，包括：
所述第一属性按照业务粒度配置，基于所述第二目标地址关联的至少一个第二业务对应的第一属性确定所述第二目标地址对应的第一属性。
可选地，所述基于所述第二目标地址关联的至少一个第二业务对应的第一属性确定所述第二目标地址对应的第一属性，包括：
所述第二目标地址关联的所有第二业务对应的第一属性均指示以下至少之一：版本号为目标版本号、支持载波聚合、支持数据分流、不后向兼容，确定所述第二目标地址对应的第一属性为以下至少之一：所述第二目标地址的版本号为所述目标版本号、所述第二目标地址支持载波聚合、所述第二目标地址支持数据分流、所述第二目标地址不后向兼容。
可选地，所述方法还包括：
所述第二目标地址不存在对应的第一属性，确定以下至少之一：所述第二目标地址的版本号不为目标版本号、所述第二目标地址不支持载波聚合、所述第二目标地址不支持数据分流、所述第二目标地址后向兼容。
可选地，所述基于所述第二目标地址与载波之间的映射关系、所述第二目标地址对应的第一属性中的至少之一在一个或多个载波上接收SL数据，包括：
至少一个第二目标地址满足第一预设条件，通过多载波接收所述至少一个第二目标地址关联的SL数据；其中，所述第一预设条件包括：所述第二目标地址与载波之间的映射关系为：所述第二目标地址映射到多个载波；和/或，所述第二目标地址对应的第一属性指示以下至少之一：所述第二目标地址的版本号为目标版本号、所述第二目标地址支持载波聚合、所述第二目标地址支持数据分流、所述第二目标地址不后向兼容。
可选地，所述基于所述第二目标地址与载波之间的映射关系、所述第二目标地址对应的第一属性中的至少之一在一个或多个载波上接收SL数据，包括：
全部第二目标地址满足第二预设条件，通过可实现后向兼容的现有载波接收所述至少一个第二目标地址关联的SL数据；其中，所述第二预设条件包括：所述第二目标地址与载波之间的映射关系为：第二目标地址映射到一个载波；和/或，所述第二目标地址对应的第一属性指示以下至少之一：所述第二目标地址的版本号不为目标版本号、所述第二目标地址不支持载波聚合、所述第二目标地址不支持数据分流、所述第二目标地址后向兼容；和/或，所述第二预设条件包括：所述第二目标地址与载波之间的映射关系为：所述第二目标地址映射到多个载波；和/或，所述第二目标地址对应的第一属性指示以下至少之一：所述第二目标地址的版本号不为目标版本号、所述第二目标地址不支持载波聚合、所述第二目标地址不支持数据分流、所述第二目标地址后向兼容。
可选地，对于第二目标地址，所述第一设备与第二设备配置相同的第一属性；其中，所述第一设备为所述第二目标地址的发送终端，所述第二设备为所述第二目标地址的接收终端。
关于步骤4301的详细介绍可以参考上述实施例的内容。
在本实施方式或实施例中，在不矛盾的情况下，各步骤可以独立、任意组合或交换顺序，可选方式或可选例可以任意组合，且可以与其他实施方式或其他实施例的任意步骤之间进行任意组合。
图5是根据本公开实施例示出的通信方法的流程示意图。如图5所示，本公开实施例涉及通信方法，用于通信系统，该通信系统包括第一设备、第二设备，上述方法包括以下至少之一：
步骤5101、第一设备基于第一目标地址与载波之间的映射关系、第一目标地址对应的第一属性中的至 少之一发送所述第一目标地址关联的SL数据。
步骤5102、第二设备基于第二目标地址与载波之间的映射关系、第二目标地址对应的第一属性中的至少之一在一个或多个载波上接收SL数据。
步骤5101-步骤5102的可选实现方式可以参见上述实施例介绍。
在一些实施例中，上述方法可以包括上述通信系统侧、第一设备侧、第二设备侧等的实施例所述的方法，此处不再赘述。
本公开实施例所涉及的通信方法可以包括步骤S5101～步骤S5104中的至少一者。例如，步骤S5101可以作为独立实施例来实施，步骤S5102可以作为独立实施例来实施，但不限于此。
在本实施方式或实施例中，在不矛盾的情况下，各步骤可以独立、任意组合或交换顺序，可选方式或可选例可以任意组合，且可以与其他实施方式或其他实施例的任意步骤之间进行任意组合。
以下为对上述方法的示例性介绍。
可选示例：针对广播/组播业务定义一个业务类型粒度或者目标地址粒度的Tx profile，指示广播/组播业务是否支持载波聚合/数据分流/后向兼容。
可选示例1：针对广播/组播业务定义一个业务类型粒度或者目标地址粒度的Tx profile
实施例：如果Tx profile是按业务类型粒度定义的，不同业务类型关联的Tx profile不同，如果一个目标地址可以关联多个不同的业务类型，一个目标地址关联的Tx profile可能有多个；
实施例：如果Tx profile是按目标地址粒度定义的，一个目标地址关联的Tx profile只有一个，需要高层实现保证一个目标地址关联的所有业务类型关联的Tx profile都相同。实施例：Tx profile由高层指示AS层。
可选示例2：Tx profile用来指示广播/组播业务是否支持载波聚合/数据分流/后向兼容
实施例：所述Tx profile可以指示一个版本，例如Rel-18,也可以用来指示是否支持载波聚合/数据分流。示例性的，Tx profile具体指示的内容可以有其他命名形式，本公开不作具体限定。示例性的，Tx profile可以指示该业务是否后向兼容R16/17legacy终端。示例性的，终端根据Tx profile确定R16/17legacy终端是否是该业务/目标地址的接收终端。
实施例：如果Tx profile是按业务类型粒度定义的，一个目标地址关联的所有Tx profile指示支持载波聚合/数据分流，终端设备才认为这个目标地址支持载波聚合/数据分流。如果一个业务只映射到一个载波/频带上，这个业务关联的Tx profile不支持载波聚合/数据分流。如果一个业务映射到多个载波/频带上，这个业务关联的Tx profile可以支持载波聚合/数据分流，也可以不支持载波聚合/数据分流。如果一个目标地址没有关联的Tx profile,终端设备认为这个目标地址不支持载波聚合/数据分流。
实施例：如果Tx profile是按目标地址粒度定义的，如果这个目标地址只映射到一个载波/频带上，这个目标地址关联的Tx profile不支持载波聚合/数据分流。如果这个目标地址映射到多个载波/频带上，这个目标地址关联的Tx profile可以支持载波聚合/数据分流，也可以不支持载波聚合/数据分流。
可选示例3：对于一个广播/组播业务的目标地址，所有发送终端和接收终端需要配置相同的Tx profile(s)。
可选示例4：终端设备确定一个广播/组播业务目标地址支持载波聚合/数据分流/不支持后向兼容，终端设备可以在多个载波/频带上分流数据。
实施例：所述终端设备是发送终端。示例性的，所述终端在多个载波/频带上分流数据是指所述终端设备在多个载波/频带上分流数据(data split)，不同载波/频带上传输的数据属于这个目标地址，不同载波/频带上传输的数据不同。例如在载波1，2,3上分别发送packet A,B,C。终端设备也可以使能PDCP复用，具体的，根据网络设备的配置使能PDCP复用，例如对这个广播/组播业务目标地址关联的某些SL无线承载(SLRB radio bearer)如果网络设备配置使能了PDCP复用，终端设备就使能PDCP复用传输这些SLRB(终端设备在不同的2个载波上传输这个SLRB的相同的数据)，其中终端设备可以在支持聚合的多个载波中任意选择2个载波去做PDCP复用。
例如对于这个广播/组播业务目标地址关联的某些SL无线承载(SLRB radio bearer)如果网络设备配置去使能了PDCP复用，终端设备就通过数据分流传输这些SLRB(终端设备在不同的2个或者多个载波 上传输这个SLRB的不同的数据)
实施例：终端设备可以结合高层配置的广播/组播业务到载波/频带的映射和/或目广播/组播标地址关联的Tx profile判断广播/组播目标地址是否支持载波聚合/数据分流。示例性的，case a:如果一个广播/组播目标地址映射到多个载波/频带上，和目标地址关联的Tx profile支持载波聚合/数据分流，终端设备确定这个目标地址支持载波聚合/数据分流。示例性的，case b:如果一个广播/组播目标地址映射到多个载波/频带上，和目标地址关联的Tx profile不支持载波聚合/数据分流，终端设备确定这个目标地址不支持载波聚合/数据分流。示例性的，case c:如果一个广播/组播目标地址映射到一个载波/频带上，和目标地址关联的Tx profile支持载波聚合/数据分流，终端设备确定这个目标地址不支持载波聚合/数据分流。示例性的，case d:如果一个广播/组播目标地址映射到一个载波/频带上，和目标地址关联的Tx profile不支持载波聚合/数据分流，终端设备确定这个目标地址不支持载波聚合/数据分流。
可选示例5：终端设备确定一个广播/组播业务目标地址不支持载波聚合/数据分流/支持后向兼容，终端设备在单载波/频带上发送数据。
实施例：所述终端设备是发送终端。示例性的，所述单载波/频带是所述R16/17终端支持的载波/频带。上述case bcd均适用。示例性的，对于case b，一个广播/组播目标地址映射到多个载波/频带上，和目标地址关联的Tx profile不支持载波聚合/数据分流，也就是说该广播/组播目标地址后向兼容R16/17终端设备(R16/17终端设备需要接收该广播/组播地址关联的广播/组播业务)，对于这个广播/组播目标地址，终端设备也可以使能PDCP复用或者在单载波/频带上发送，具体的，终端设备根据网络设备的配置使能PDCP复用，例如对这个广播/组播业务目标地址关联的某些SL无线承载(SLRB radio bearer)如果网络设备配置使能了PDCP复用，终端设备就使能PDCP复用传输这些SLRB(终端设备在不同的2个载波上传输这个SLRB的相同的数据)，其中终端设备需要选择R16/17终端支持的legacy载波/频带作为其中一个载波，在支持聚合的多个载波中任意选择1个载波作为另外一个载波去做PDCP复用。
例如对于这个广播/组播业务目标地址关联的某些SL无线承载(SLRB radio bearer)如果网络设备配置去使能了PDCP复用，终端设备就通过单载波/频带传输这些SLRB的数据
可选示例6：终端设备确定一个广播/组播业务目标地址不支持载波聚合/数据分流，终端设备在多个载波/频带上PDCP duplication。
实施例：所述终端设备是发送终端。示例性的，上述case b适用。示例性的，所述终端在多个载波/频带上PDCP duplication是指所述终端设备在多个载波/频带上复用数据(data duplication)，不同载波/频带上传输的数据属于这个目标地址，不同载波/频带上传输的数据相同。例如在载波1，2,上均发送packet A。
实施例：所述终端设备将关联现有的LCID(例如4-19)的数据包通过R16/17终端支持的载波/频带上发。
可选示例7：终端设备确定一个广播/组播业务目标地址支持载波聚合/数据分流，终端设备在多个载波/频带上接收数据。
实施例：所述终端设备是接收终端。示例性的，所述终端设备支持载波聚合(R18/19终端)所述终端设备确定任意一个广播/组播业务的目标地址支持载波聚合/数据分流，终端设备在多个载波/频带上接收数据。示例性的，所述广播/组播业务的目标地址为所述终端设备感兴趣接收的广播/组播业务的目标地址；
本公开提供一种SL载波聚合后向兼容的方法，解决了NR sidelink载波聚合场景下R16/17的老版本终端可以收到R18支持载波聚合的终端发的广播/组播业务，保证后向兼容性的问题。
本公开实施例还提出用于实现以上任一方法的装置，例如，提出一装置，上述装置包括用以实现以上任一方法中第一设备所执行的各步骤的单元或模块。再如，还提出另一装置，包括用以实现以上任一方法中第二设备(例如接入网设备、核心网功能节点、核心网设备等)所执行的各步骤的单元或模块。
应理解以上装置中各单元或模块的划分仅是一种逻辑功能的划分，在实际实现时可以全部或部分集成到一个物理实体上，也可以物理上分开。此外，装置中的单元或模块可以以处理器调用软件的形式实现：例如装置包括处理器，处理器与存储器连接，存储器中存储有指令，处理器调用存储器中存储的指令，以实现以上任一方法或实现上述装置各单元或模块的功能，其中处理器例如为通用处理器，例如中央处理单元(Central Processing Unit，CPU)或微处理器，存储器为装置内的存储器或装置外的存储器。或者，装 置中的单元或模块可以以硬件电路的形式实现，可以通过对硬件电路的设计实现部分或全部单元或模块的功能，上述硬件电路可以理解为一个或多个处理器；例如，在一种实现中，上述硬件电路为专用集成电路(application-specific integrated circuit，ASIC)，通过对电路内元件逻辑关系的设计，实现以上部分或全部单元或模块的功能；再如，在另一种实现中，上述硬件电路为可以通过可编程逻辑器件(programmable logic device，PLD)实现，以现场可编程门阵列(Field Programmable Gate Array，FPGA)为例，其可以包括大量逻辑门电路，通过配置文件来配置逻辑门电路之间的连接关系，从而实现以上部分或全部单元或模块的功能。以上装置的所有单元或模块可以全部通过处理器调用软件的形式实现，或全部通过硬件电路的形式实现，或部分通过处理器调用软件的形式实现，剩余部分通过硬件电路的形式实现。
在本公开实施例中，处理器是具有信号处理能力的电路，在一种实现中，处理器可以是具有指令读取与运行能力的电路，例如中央处理单元(Central Processing Unit，CPU)、微处理器、图形处理器(graphics processing unit，GPU)(可以理解为微处理器)、或数字信号处理器(digital signal processor，DSP)等；在另一种实现中，处理器可以通过硬件电路的逻辑关系实现一定功能，上述硬件电路的逻辑关系是固定的或可以重构的，例如处理器为专用集成电路(application-specific integrated circuit，ASIC)或可编程逻辑器件(programmable logic device，PLD)实现的硬件电路,例如FPGA。在可重构的硬件电路中，处理器加载配置文档，实现硬件电路配置的过程，可以理解为处理器加载指令，以实现以上部分或全部单元或模块的功能的过程。此外，还可以是针对人工智能设计的硬件电路，其可以理解为ASIC，例如神经网络处理单元(Neural Network Processing Unit，NPU)、张量处理单元(Tensor Processing Unit，TPU)、深度学习处理单元(Deep learning Processing Unit，DPU)等。
图6A是本公开实施例提出的第一设备的结构示意图。如图6A所示，包括：
发送模块，用于基于第一目标地址与载波之间的映射关系、第一目标地址对应的第一属性中的至少之一发送所述第一目标地址关联的SL数据；其中，所述第一目标地址对应的第一属性用于指示以下至少之一：所述第一目标地址的版本号、所述第一目标地址是否支持载波聚合、所述第一目标地址是否支持数据分流、所述第一目标地址是否后向兼容；其中，所述第一目标地址为广播业务和/或组播业务关联的目标地址，所述第一目标地址为所述第一设备感兴趣发送和/或接收的目标地址。
可选地，上述发送模块用于执行以上任一方法中第一设备101执行的与发送有关的步骤，此处不再赘述。可选地，第二设备还包括接收模块、处理模块中的至少之一，上述接收模块用于执行以上任一方法中第一设备101执行的与接收有关的步骤，上述处理模块用于执行以上任一方法中第一设备101执行的与“处理”有关的步骤，，此处不再赘述。
图6B是本公开实施例提出的第二设备的结构示意图。如图6B所示，包括：
接收模块，用于基于所述第二目标地址与载波之间的映射关系、所述第二目标地址对应的第一属性中的至少之一在一个或多个载波上接收SL数据；其中，所述第二目标地址对应的第一属性用于指示以下至少之一：所述第二目标地址的版本号、所述第二目标地址是否支持载波聚合、所述第二目标地址是否支持数据分流、所述第二目标地址是否后向兼容；所述第二目标地址为广播业务和/或组播业务关联的目标地址，所述第二目标地址为所述第二设备感兴趣发送和/或接收的目标地址。
可选地，上述接收模块用于执行以上任一方法中第二设备102执行的与接收有关的步骤，此处不再赘述。可选地，第二设备还包括发送模块、处理模块中的至少之一，上述发送模块用于执行以上任一方法中第二设备102执行的与发送有关的步骤，上述处理模块用于执行以上任一方法中第二设备102执行的与“处理”有关的步骤，，此处不再赘述。
图7A是本公开实施例提出的通信设备7100的结构示意图。通信设备7100可以是网络设备(例如接入网设备、核心网设备等)，也可以是终端(例如用户设备等)，也可以是支持网络设备实现以上任一方法的芯片、芯片系统、或处理器等，还可以是支持终端实现以上任一方法的芯片、芯片系统、或处理器等。通信设备7100可用于实现上述方法实施例中描述的方法，具体可以参见上述方法实施例中的说明。
如图7A所示，通信设备7100包括一个或多个处理器7101。处理器7101可以是通用处理器或者专用处理器等，例如可以是基带处理器或中央处理器。基带处理器可以用于对通信协议以及通信数据进行处理，中央处理器可以用于对通信装置(如，基站、基带芯片，终端设备、终端设备芯片，DU或CU等)进行 控制，执行程序，处理程序的数据。处理器7101用于调用指令以使得通信设备7100执行以上任一方法。
在一些实施例中，通信设备7100还包括用于存储指令的一个或多个存储器7102。可选地，全部或部分存储器7102也可以处于通信设备7100之外。
在一些实施例中，通信设备7100还包括一个或多个收发器7103。在通信设备7100包括一个或多个收发器7103时，上述方法中的发送接收等通信步骤由收发器7103执行，其他步骤由处理器7101执行。
在一些实施例中，收发器可以包括接收器和发送器，接收器和发送器可以是分离的，也可以集成在一起。可选地，收发器、收发单元、收发机、收发电路等术语可以相互替换，发送器、发送单元、发送机、发送电路等术语可以相互替换，接收器、接收单元、接收机、接收电路等术语可以相互替换。
可选地，通信设备7100还包括一个或多个接口电路7104，接口电路7104与存储器7102连接，接口电路7104可用于从存储器7102或其他装置接收信号，可用于向存储器7102或其他装置发送信号。例如，接口电路7104可读取存储器7102中存储的指令，并将该指令发送给处理器7101。
以上实施例描述中的通信设备7100可以是网络设备或者终端，但本公开中描述的通信设备7100的范围并不限于此，通信设备7100的结构可以不受图7a的限制。通信设备可以是独立的设备或者可以是较大设备的一部分。例如所述通信设备可以是：1)独立的集成电路IC，或芯片，或，芯片系统或子系统；(2)具有一个或多个IC的集合，可选地，上述IC集合也可以包括用于存储数据，程序的存储部件；(3)ASIC，例如调制解调器(Modem)；(4)可嵌入在其他设备内的模块；(5)接收机、终端设备、智能终端设备、蜂窝电话、无线设备、手持机、移动单元、车载设备、网络设备、云设备、人工智能设备等等；(6)其他等等。
图7B是本公开实施例提出的芯片7200的结构示意图。对于通信设备7100可以是芯片或芯片系统的情况，可以参见图7B所示的芯片7200的结构示意图，但不限于此。
芯片7200包括一个或多个处理器7201，处理器7201用于调用指令以使得芯片7200执行以上任一方法。
在一些实施例中，芯片7200还包括一个或多个接口电路7202，接口电路7202与存储器7203连接，接口电路7202可以用于从存储器7203或其他装置接收信号，接口电路7202可用于向存储器7203或其他装置发送信号。例如，接口电路7202可读取存储器7203中存储的指令，并将该指令发送给处理器7201。可选地，接口电路、接口、收发管脚、收发器等术语可以相互替换。
在一些实施例中，芯片7200还包括用于存储指令的一个或多个存储器7203。可选地，全部或部分存储器7203可以处于芯片7200之外。
本公开还提出存储介质，上述存储介质上存储有指令，当上述指令在通信设备7100上运行时，使得通信设备7100执行以上任一方法。可选地，上述存储介质是电子存储介质。可选地，上述存储介质是计算机可读存储介质，但不限于此，其也可以是其他装置可读的存储介质。可选地，上述存储介质可以是非暂时性(non-transitory)存储介质，但不限于此，其也可以是暂时性存储介质。
本公开还提出程序产品，上述程序产品被通信设备7100执行时，使得通信设备7100执行以上任一方法。可选地，上述程序产品是计算机程序产品。
本公开还提出计算机程序，当其在计算机上运行时，使得计算机执行以上任一方法。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机程序。在计算机上加载和执行所述计算机程序时，全部或部分地产生按照本公开实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机程序可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机程序可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，高密度数字视频光盘(digital video disc，DVD))、或者半导体介质(例如，固态硬盘(solid state disk，SSD))等。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本公开的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
以上所述，仅为本公开的具体实施方式，但本公开的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本公开揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本公开的保护范围之内。因此，本公开的保护范围应以所述权利要求的保护范围为准。

Claims (40)

  1. 一种通信方法，其特征在于，所述方法包括：
    第一设备基于第一目标地址与载波之间的映射关系、第一目标地址对应的第一属性中的至少之一发送所述第一目标地址关联的侧行链路SL数据；其中，所述第一目标地址对应的第一属性用于指示以下至少之一：所述第一目标地址的版本号、所述第一目标地址是否支持载波聚合、所述第一目标地址是否支持数据分流、所述第一目标地址是否后向兼容；其中，所述第一目标地址为广播业务和/或组播业务关联的目标地址，所述第一目标地址为所述第一设备感兴趣发送和/或接收的目标地址。
  2. 如权利要求1所述的方法，其特征在于，所述方法还包括：
    所述第一设备确定至少一个第一目标地址分别对应的第一属性。
  3. 如权利要求1或2所述的方法，其特征在于，所述第一属性按照业务粒度配置；其中，一个第一业务对应一个第一属性，所述第一目标地址关联至少一个第一业务；所述第一业务包括广播业务和/或组播业务；或者
    所述第一属性按照目标地址粒度配置；其中，所述第一目标地址对应一个第一属性。
  4. 如权利要求2或3所述的方法，其特征在于，所述确定至少一个第一目标地址分别对应的第一属性，包括：
    所述第一属性按照业务粒度配置，基于所述第一目标地址关联的至少一个第一业务对应的第一属性确定所述第一目标地址对应的第一属性。
  5. 如权利要求4所述的方法，其特征在于，所述基于所述第一目标地址关联的至少一个第一业务对应的第一属性确定所述第一目标地址对应的第一属性，包括：
    所述第一目标地址关联的所有第一业务对应的第一属性均指示以下至少之一：版本号为目标版本号、支持载波聚合、支持数据分流、不后向兼容，确定所述第一目标地址对应的第一属性为以下至少之一：所述第一目标地址的版本号为所述目标版本号、所述第一目标地址支持载波聚合、所述第一目标地址支持数据分流、所述第一目标地址不后向兼容。
  6. 如权利要求1-5任一所述的方法，其特征在于，所述方法还包括：
    所述第一目标地址不存在对应的第一属性，确定以下至少之一：所述第一目标地址的版本号不为目标版本号、所述第一目标地址不支持载波聚合、所述第一目标地址不支持数据分流、所述第一目标地址后向兼容。
  7. 如权利要求1-6任一所述的方法，其特征在于，所述基于第一目标地址与载波之间的映射关系、第一目标地址对应的第一属性中的至少之一发送所述第一目标地址关联的SL数据，包括：
    所述第一目标地址与载波之间的映射关系为：所述第一目标地址映射到多个载波；和/或，所述第一目标地址对应的第一属性指示以下至少之一：所述第一目标地址的版本号为目标版本号、所述第一目标地址支持载波聚合、所述第一目标地址支持数据分流、所述第一目标地址不后向兼容；通过多载波分流和/或包数据汇聚协议PDCP复用duplication发送所述第一目标地址关联的SL数据。
  8. 如权利要求1-6任一所述的方法，其特征在于，所述基于第一目标地址与载波之间的映射关系、第一目标地址对应的第一属性中的至少之一发送所述第一目标地址关联的SL数据，包括：
    所述第一目标地址与载波之间的映射关系为：所述第一目标地址映射到多个载波；和/或，所述第一目标地址对应的第一属性指示以下至少之一：所述第一目标地址的版本号不为目标版本号、所述第一目标地址不支持载波聚合、所述第一目标地址不支持数据分流、所述第一目标地址后向兼容；通过单载波和/或PDCP复用发送所述第一目标地址关联的SL数据。
  9. 如权利要求1-6任一所述的方法，其特征在于，所述基于第一目标地址与载波之间的映射关系、第一目标地址对应的第一属性中的至少之一发送所述第一目标地址关联的SL数据，包括：
    所述第一目标地址与载波之间的映射关系为：所述第一目标地址映射到一个载波；和/或，所述第一目标地址对应的第一属性指示以下至少之一：所述第一目标地址的版本号为目标版本号、所述第一目标地址支持载波聚合、所述第一目标地址支持数据分流、所述第一目标地址不后向兼容；通过单载波发送所述第一目标地址关联的SL数据。
  10. 如权利要求1-6任一所述的方法，其特征在于，所述基于第一目标地址与载波之间的映射关系、第一目标地址对应的第一属性中的至少之一发送所述第一目标地址关联的SL数据，包括：
    所述第一目标地址与载波之间的映射关系为：所述第一目标地址映射到一个载波；和/或，所述第一目标地址对应的第一属性指示以下至少之一：所述第一目标地址的版本号不为目标版本号、所述第一目标地址不支持载波聚合、所述第一目标地址不支持数据分流、所述第一目标地址后向兼容；通过单载波发送所述第一目标地址关联的SL数据。
  11. 如权利要求7所述的方法，其特征在于，所述通过PDCP复用发送所述第一目标地址关联的SL数据，包括：
    通过PDCP复用发送第一SLRB关联的SL数据；其中，所述第一SLRB为第一目标地址关联的且激活了PDCP复用的SLRB，所述第一SLRB为一个或者多个。
  12. 如权利要求11所述的方法，其特征在于，所述通过PDCP复用发送第一SLRB关联的SL数据，包括：
    在所述第一目标地址映射的所述多个载波中选择2个载波分别发送所述第一SLRB关联的相同的SL数据。
  13. 如权利要求12所述的方法，其特征在于，所述在所述第一目标地址映射的所述多个载波中选择2个载波分别发送所述第一SLRB关联的相同的SL数据，包括：
    在所述第一目标地址映射的多个载波中任意选择2个载波分别发送所述第一SLRB关联的相同的SL数据。
  14. 如权利要求7所述的方法，其特征在于，所述通过多载波分流发送所述第一目标地址关联的SL数据，包括：
    通过所述第一目标地址映射的所述多个载波分流发送第二SLRB关联的SL数据；其中，所述第二SLRB为第一目标地址关联的且去激活PDCP复用的SLRB，所述第二SLRB为一个或者多个。
  15. 如权利要求14所述的方法，其特征在于，所述通过多载波分流发送第二SLRB关联的SL数据，包括：
    在所述第一目标地址映射的多个载波上发送所述第二SLRB关联的不同的SL数据。
  16. 如权利要求8所述的方法，其特征在于，所述通过PDCP复用发送所述第一目标地址关联的SL数据，包括：
    通过PDCP复用发送第一SLRB关联的SL数据；其中，所述第一SLRB为第一目标地址关联的且激活了PDCP复用的SLRB，所述第一SLRB为一个或者多个。
  17. 如权利要求16所述的方法，其特征在于，所述通过PDCP复用发送第一SLRB关联的SL数据，包括：
    在所述第一目标地址映射的所述多个载波中选择2个载波分别发送所述第一SLRB关联的相同的SL数据。
  18. 如权利要求17所述的方法，其特征在于，所述在所述第一目标地址映射的所述多个载波中选择2个载波分别发送所述第一SLRB关联的相同的SL数据，包括：
    在所述第一目标地址映射的多个载波中选择可实现后向兼容的现有载波和任意一个其他载波分别发送所述第一SLRB关联的相同的SL数据。
  19. 如权利要求8所述的方法，其特征在于，所述通过单载波发送所述第一目标地址关联的SL数据，包括：
    通过可实现后向兼容的现有载波发送第二SLRB关联的SL数据；其中，所述第二SLRB为第一目标地址关联的且去激活PDCP复用的SLRB，所述第二SLRB为一个或者多个。
  20. 如权利要求9或10所述的方法，其特征在于，所述通过单载波发送所述第一目标地址关联的SL数据，包括：
    通过可实现后向兼容的现有载波发送所述第一目标地址关联的SL数据。
  21. 如权利要求11-19任一所述的方法，其特征在于，所述方法还包括：
    确定至少一个第一SLRB和/或至少一个第二SLRB分别对应的SLRB配置，所述至少一个第一SLRB和/或至少一个第二SLRB分别对应的SLRB配置用于配置所述至少一个第一SLRB和/或至少一个第二SLRB是否激活PDCP复用；
    根据所述至少一个第一SLRB和/或至少一个第二SLRB分别对应的SLRB配置确定所述第一目标地址关联的所述至少一个第一SLRB和/或至少一个第二SLRB是否激活PDCP复用。
  22. 如权利要求21所述的方法，其特征在于，所述确定至少一个第一SLRB和/或至少一个第二SLRB分别对应的SLRB配置，包括以下至少之一：
    获取通过专用信令发送的所述至少一个第一SLRB和/或至少一个第二SLRB分别对应的SLRB配置；
    获取通过系统信息块SIB发送的所述至少一个第一SLRB和/或至少一个第二SLRB分别对应的SLRB配置；
    获取预配置的所述至少一个第一SLRB和/或至少一个第二SLRB分别对应的SLRB配置。
  23. 如权利要求1-22任一所述的方法，其特征在于，所述方法还包括：
    基于高层配置确定所述第一目标地址与载波之间的映射关系。
  24. 如权利要求1-23任一所述的方法，其特征在于，对于第一目标地址，所述第一设备与第二设备配置相同的第一属性；其中，所述第一设备为所述第一目标地址的发送终端，所述第二设备所述第一目标地址的接收终端。
  25. 如权利要求7-24任一所述的方法，其特征在于，所述目标版本号为R18。
  26. 一种通信方法，其特征在于，所述方法包括：
    第二设备基于第二目标地址与载波之间的映射关系、第二目标地址对应的第一属性中的至少之一在一个或多个载波上接收SL数据；其中，所述第二目标地址对应的第一属性用于指示以下至少之一：所述第二目标地址的版本号、所述第二目标地址是否支持载波聚合、所述第二目标地址是否支持数据分流、所述第二目标地址是否后向兼容；所述第二目标地址为广播业务和/或组播业务关联的目标地址，所述第二目标地址为所述第二设备感兴趣发送和/或接收的目标地址。
  27. 如权利要求26所述的方法，其特征在于，所述方法还包括：
    所述第二设备确定至少一个第二目标地址分别对应的第一属性。
  28. 如权利要求26或27所述的方法，其特征在于，所述第一属性按照业务粒度配置；其中，一个第二业务对应一个第一属性，所述第二目标地址关联至少一个第二业务；所述第二业务包括广播业务和/或组播业务；或者
    所述第一属性按照目标地址粒度配置；其中，所述第二目标地址对应一个第一属性。
  29. 如权利要求27或28所述的方法，其特征在于，所述确定至少一个第二目标地址分别对应的第一属性，包括：
    所述第一属性按照业务粒度配置，基于所述第二目标地址关联的至少一个第二业务对应的第一属性确定所述第二目标地址对应的第一属性。
  30. 如权利要求29所述的方法，其特征在于，所述基于所述第二目标地址关联的至少一个第二业务对应的第一属性确定所述第二目标地址对应的第一属性，包括：
    所述第二目标地址关联的所有第二业务对应的第一属性均指示以下至少之一：版本号为目标版本号、支持载波聚合、支持数据分流、不后向兼容，确定所述第二目标地址对应的第一属性为以下至少之一：所述第二目标地址的版本号为所述目标版本号、所述第二目标地址支持载波聚合、所述第二目标地址支持数据分流、所述第二目标地址不后向兼容。
  31. 如权利要求26-30任一所述的方法，其特征在于，所述方法还包括：
    所述第二目标地址不存在对应的第一属性，确定以下至少之一：所述第二目标地址的版本号不为目标版本号、所述第二目标地址不支持载波聚合、所述第二目标地址不支持数据分流、所述第二目标地址后向兼容。
  32. 如权利要求26-31任一所述的方法，其特征在于，所述基于所述第二目标地址与载波之间的映射关系、所述第二目标地址对应的第一属性中的至少之一在一个或多个载波上接收SL数据，包括：
    至少一个第二目标地址满足第一预设条件，通过多载波接收所述至少一个第二目标地址关联的SL数据；其中，所述第一预设条件包括：所述第二目标地址与载波之间的映射关系为：所述第二目标地址映射到多个载波；和/或，所述第二目标地址对应的第一属性指示以下至少之一：所述第二目标地址的版本号为目标版本号、所述第二目标地址支持载波聚合、所述第二目标地址支持数据分流、所述第二目标地址不后向兼容。
  33. 如权利要求26-31任一所述的方法，其特征在于，所述基于所述第二目标地址与载波之间的映射关系、所述第二目标地址对应的第一属性中的至少之一在一个或多个载波上接收SL数据，包括：
    全部第二目标地址满足第二预设条件，通过可实现后向兼容的现有载波接收所述至少一个第二目标地址关联的SL数据；其中，所述第二预设条件包括：所述第二目标地址与载波之间的映射关系为：所述第二目标地址映射到一个载波；和/或，所述第二目标地址对应的第一属性指示以下至少之一：所述第二目标地址的版本号不为目标版本号、所述第二目标地址不支持载波聚合、所述第二目标地址不支持数据分流、所述第二目标地址后向兼容；和/或，所述第二预设条件包括：所述第二目标地址与载波之间的映射关系为：所述第二目标地址映射到多个载波；和/或，所述第二目标地址对应的第一属性指示以下至少之一：所述第二目标地址的版本号不为目标版本号、所述第二目标地址不支持载波聚合、所述第二目标地址不支持数据分流、所述第二目标地址后向兼容。
  34. 如权利要求26-33任一所述的方法，其特征在于，对于第二目标地址，所述第一设备与第二设备配置相同的第一属性；其中，所述第一设备为所述第二目标地址的发送终端，所述第二设备为所述第二目标地址的接收终端。
  35. 一种通信方法，其特征在于，用于通信系统，所述通信系统包括第一设备、第二设备，所述方法包括以下至少之一：
    所述第一设备基于第一目标地址与载波之间的映射关系、第一目标地址对应的第一属性中的至少之一发送所述第一目标地址关联的SL数据；其中，所述第一目标地址对应的第一属性用于指示以下至少之一：所述第一目标地址的版本号、所述第一目标地址是否支持载波聚合、所述第一目标地址是否支持数据分流、所述第一目标地址是否后向兼容；其中，所述第一目标地址为广播业务和/或组播业务关联的目标地址，所述第一目标地址为所述第一设备感兴趣发送和/或接收的目标地址；
    所述第二设备基于第二目标地址与载波之间的映射关系、第二目标地址对应的第一属性中的至少之一在一个或多个载波上接收SL数据；其中，所述第二目标地址对应的第一属性用于指示以下至少之一：所述第二目标地址的版本号、所述第二目标地址是否支持载波聚合、所述第二目标地址是否支持数据分流、所述第二目标地址是否后向兼容；所述第二目标地址为广播业务和/或组播业务关联的目标地址，所述第二目标地址为所述第二设备感兴趣发送和/或接收的目标地址，所述至少一个第二目标地址为所述至少一个第一目标地址中的部分或全部目标地址。
  36. 一种第一设备，包括：
    发送模块，用于基于第一目标地址与载波之间的映射关系、第一目标地址对应的第一属性中的至少之一发送所述第一目标地址关联的SL数据；其中，所述第一目标地址对应的第一属性用于指示以下至少之一：所述第一目标地址的版本号、所述第一目标地址是否支持载波聚合、所述第一目标地址是否支持数据分流、所述第一目标地址是否后向兼容；其中，所述第一目标地址为广播业务和/或组播业务关联的目标地址，所述第一目标地址为所述第一设备感兴趣发送和/或接收的目标地址。
  37. 一种第二设备，包括：
    接收模块，用于基于所述第二目标地址与载波之间的映射关系、所述第二目标地址对应的第一属性中的至少之一在一个或多个载波上接收SL数据；其中，所述第二目标地址对应的第一属性用于指示以下至少之一：所述第二目标地址的版本号、所述第二目标地址是否支持载波聚合、所述第二目标地址是否支持数据分流、所述第二目标地址是否后向兼容；所述第二目标地址为广播业务和/或组播业务关联 的目标地址，所述第二目标地址为所述第二设备感兴趣发送和/或接收的目标地址。
  38. 一种通信设备，其特征在于，包括：
    一个或多处理器；
    其中，所述处理器用于调用指令以使得所述通信设备执行权利要求1-25、26-34中任一项所述的通信方法。
  39. 一种通信系统，其特征在于，包括第一设备、第二设备，其中，所述第一设备被配置为实现权利要求1-25中任一项所述的通信方法，所述第二设备被配置为实现权利要求26-34中任一项所述的通信方法。
  40. 一种存储介质，所述存储介质存储有指令，其特征在于，当所述指令在通信设备上运行时，使得所述通信设备执行如权利要求1-25、26-34中任一项所述的通信方法。
PCT/CN2023/112426 2023-08-11 2023-08-11 通信方法及装置、通信设备、通信系统、存储介质 WO2025035230A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/112426 WO2025035230A1 (zh) 2023-08-11 2023-08-11 通信方法及装置、通信设备、通信系统、存储介质

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/112426 WO2025035230A1 (zh) 2023-08-11 2023-08-11 通信方法及装置、通信设备、通信系统、存储介质

Publications (1)

Publication Number Publication Date
WO2025035230A1 true WO2025035230A1 (zh) 2025-02-20

Family

ID=94631912

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/112426 WO2025035230A1 (zh) 2023-08-11 2023-08-11 通信方法及装置、通信设备、通信系统、存储介质

Country Status (1)

Country Link
WO (1) WO2025035230A1 (zh)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3206321A1 (en) * 2016-02-15 2017-08-16 Panasonic Intellectual Property Corporation of America Improved uplink harq operation for prose-enabled ues participating in sidelink discovery operation
CN111866796A (zh) * 2019-04-30 2020-10-30 华为技术有限公司 用于获取无线承载配置的方法和装置
CN115669093A (zh) * 2020-08-06 2023-01-31 Oppo广东移动通信有限公司 节能的方法及设备
CN116158059A (zh) * 2020-07-23 2023-05-23 苹果公司 通过用户设备中继的通信的保护
EP4210370A1 (en) * 2022-01-07 2023-07-12 LG Electronics, Inc. Method and apparatus for revoking user equipment authentication in wireless communication system background of the invention
CN116458176A (zh) * 2020-11-26 2023-07-18 高通股份有限公司 一对一广播侧行链路通信协议车载通信

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3206321A1 (en) * 2016-02-15 2017-08-16 Panasonic Intellectual Property Corporation of America Improved uplink harq operation for prose-enabled ues participating in sidelink discovery operation
CN111866796A (zh) * 2019-04-30 2020-10-30 华为技术有限公司 用于获取无线承载配置的方法和装置
CN116158059A (zh) * 2020-07-23 2023-05-23 苹果公司 通过用户设备中继的通信的保护
CN115669093A (zh) * 2020-08-06 2023-01-31 Oppo广东移动通信有限公司 节能的方法及设备
CN116458176A (zh) * 2020-11-26 2023-07-18 高通股份有限公司 一对一广播侧行链路通信协议车载通信
EP4210370A1 (en) * 2022-01-07 2023-07-12 LG Electronics, Inc. Method and apparatus for revoking user equipment authentication in wireless communication system background of the invention

Similar Documents

Publication Publication Date Title
WO2025039168A1 (zh) 随机接入方法及装置、通信设备、通信系统、存储介质
WO2025035230A1 (zh) 通信方法及装置、通信设备、通信系统、存储介质
WO2025060013A1 (zh) 通信方法及装置、通信设备、通信系统、存储介质
WO2025030387A1 (zh) 通信方法及装置、通信设备、通信系统、存储介质
WO2025054798A1 (zh) 通信方法及装置、通信设备、通信系统、存储介质
WO2025039144A1 (zh) 路径建立方法及装置、通信设备、通信系统、存储介质
WO2025065452A1 (zh) 通信处理方法、终端、接入网设备
WO2025030292A1 (zh) 一种侧行链路通信方法及其装置
WO2025043728A1 (zh) 通信方法、第一终端、第二终端、通信系统
WO2025000407A1 (zh) 配置方法及装置、通信设备、通信系统、存储介质
WO2024244021A1 (zh) 通信方法及装置、通信设备、通信系统、存储介质
WO2025043567A1 (zh) 确定方法及装置、通信设备、通信系统、存储介质
WO2025050408A1 (zh) 卫星通信方法及装置、通信设备、通信系统、存储介质
WO2024259708A1 (zh) 处理方法及装置、通信设备、通信系统、存储介质
WO2025007260A1 (zh) 频率资源配置处理方法及终端、网络设备、通信系统
WO2025030432A1 (zh) 侧行链路数据包汇聚协议pdcp复用的方法及其装置
WO2025010727A1 (zh) 确定方法及装置、通信设备、通信系统、存储介质
WO2025025026A1 (zh) 信息处理方法、网络设备、终端、通信系统及存储介质
WO2025010687A1 (zh) Pdu会话处理方法及第一核心网功能、第二核心网功能
WO2025065368A1 (zh) 上报方法及装置、通信设备、通信系统、存储介质
WO2025020008A1 (zh) 资源确定方法及装置、通信设备、通信系统、存储介质
WO2025020061A1 (zh) 信息的传输方法、终端、第一实体及第二实体
WO2025000534A1 (zh) 上行传输的调度方法及装置、通信设备、通信系统、存储介质
WO2025030275A1 (zh) 通信方法及装置、通信设备、通信系统、存储介质
WO2025010691A1 (zh) 信息处理方法及网元、通信设备、通信系统及存储介质

Legal Events

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

Ref document number: 23948675

Country of ref document: EP

Kind code of ref document: A1