WO2024055317A1 - 一种侧链路通信方法、装置及通信设备 - Google Patents

一种侧链路通信方法、装置及通信设备 Download PDF

Info

Publication number
WO2024055317A1
WO2024055317A1 PCT/CN2022/119434 CN2022119434W WO2024055317A1 WO 2024055317 A1 WO2024055317 A1 WO 2024055317A1 CN 2022119434 W CN2022119434 W CN 2022119434W WO 2024055317 A1 WO2024055317 A1 WO 2024055317A1
Authority
WO
WIPO (PCT)
Prior art keywords
carrier aggregation
target address
compatible
service
sending
Prior art date
Application number
PCT/CN2022/119434
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/CN2022/119434 priority Critical patent/WO2024055317A1/zh
Priority to CN202280003581.7A priority patent/CN115669140A/zh
Publication of WO2024055317A1 publication Critical patent/WO2024055317A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0453—Resources in frequency domain, e.g. a carrier in FDMA
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/30—Resource management for broadcast services
    • 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 wireless communication technology, and in particular, to a side-link communication method, device and communication equipment.
  • Side-link networks support multiple transmission modes such as unicast, multicast, and broadcast.
  • V2X vehicle to everything
  • LTE long term evolution
  • CA side-link carrier aggregation
  • terminal devices of previous versions may not receive support for carrier aggregation.
  • the broadcast service or multicast service sent by the terminal equipment (such as the terminal equipment in the Rel-18 version of the communication protocol) has the problem of backward incompatibility of the side link terminal equipment.
  • the present disclosure provides a side-link communication method, device and communication equipment to achieve backward compatibility of side-link terminal equipment, thereby improving the performance of the terminal equipment.
  • a side link communication method which method can be applied to a sending device side in a side link communication system.
  • the method may include: determining that the first target address is compatible with carrier aggregation when all transmission attributes associated with the first target address correspond to compatible carrier aggregation; or, when at least one transmission attribute associated with the first target address corresponds to incompatible carrier aggregation When , it is determined that the first target address is not compatible with carrier aggregation; wherein the first target address is the target address of the first service, and the first service is a broadcast service or a multicast service.
  • the transmission attribute is used to indicate whether the broadcast service or the multicast service is compatible with carrier aggregation.
  • the sending attributes are set according to the service type granularity, or the sending attributes are set according to the target address granularity.
  • one sending attribute in response to the sending attributes being set according to service type granularity, one sending attribute is associated with one service type, and at least one service type is associated with one target address.
  • all sending attributes associated with the first target address include: sending attributes associated with all service types associated with the first target address.
  • a send attribute is associated with a target address in response to the send attributes being set at target address granularity.
  • one or more transmission attributes are associated with a target address, wherein the one or more transmission attributes include a transmission attribute indicating compatible carrier aggregation and/or a transmission indicating incompatible carrier aggregation. Attributes.
  • the above method further includes: determining that any first target address is compatible with carrier aggregation; and simultaneously sending data of one or more first services on multiple carriers.
  • the above method further includes: determining that all first target addresses are incompatible with carrier aggregation; and sending data of one or more first services on a single carrier.
  • the above method further includes: determining that all first target addresses are compatible with carrier aggregation; and simultaneously sending data of one or more first services on multiple carriers.
  • the above method further includes: determining that any first target address is incompatible with carrier aggregation; and sending data of one or more first services on a single carrier.
  • a side link communication method which method can be applied to a receiving device side in a side link communication system.
  • the method may include: determining that the second target address is compatible with carrier aggregation when all transmission attributes associated with the second target address correspond to compatible carrier aggregation; or, when at least one transmission attribute associated with the second target address corresponds to incompatible carrier aggregation When , it is determined that the second target address is not compatible with carrier aggregation; wherein the second target address is the target address of the second service of interest, and the second service is a broadcast service or a multicast service.
  • the transmission attribute is used to indicate whether the broadcast service or the multicast service is compatible with carrier aggregation.
  • the sending attributes are set according to the service type granularity, or the sending attributes are set according to the target address granularity.
  • one sending attribute in response to the sending attributes being set according to service type granularity, one sending attribute is associated with one service type, and at least one service type is associated with one target address.
  • all sending attributes associated with the second target address include: sending attributes associated with all service types associated with the second target address.
  • one sending attribute is associated with one target address in response to the sending attributes being set at target address granularity.
  • one or more transmission attributes are associated with a target address, wherein the one or more transmission attributes include a transmission attribute indicating compatible carrier aggregation and/or a transmission indicating incompatible carrier aggregation. Attributes.
  • the above method further includes: determining that any second target address is compatible with carrier aggregation; and simultaneously receiving data of one or more second services on multiple carriers.
  • the above method further includes: determining that all second target addresses are incompatible with carrier aggregation; and receiving data of one or more second services on a single carrier.
  • the above method further includes: determining that all second target addresses are compatible with carrier aggregation; and simultaneously receiving data of one or more second services on multiple carriers.
  • the above method further includes: determining that any second target address is incompatible with carrier aggregation; and receiving data of one or more second services on a single carrier.
  • a communication device can be a sending device in a side-link communication system or a chip or system-on-chip in the sending device. It can also be a sending device used to implement the above embodiments.
  • the communication device can realize the functions performed by the sending device in the above embodiments, and these functions can be realized by hardware executing corresponding software. These hardware or software include one or more modules corresponding to the above functions.
  • the communication device includes: a processing module configured to determine that the first target address is compatible with carrier aggregation when all transmission attributes associated with the first target address correspond to compatible carrier aggregation; or, when at least one transmission attribute associated with the first target address corresponds to When carrier aggregation is not compatible, it is determined that the first target address is not compatible with carrier aggregation; wherein the first target address is a target address of the first service, and the first service is a broadcast service or a multicast service.
  • the transmission attribute is used to indicate whether the broadcast service or the multicast service is compatible with carrier aggregation.
  • the sending attributes are set according to the service type granularity, or the sending attributes are set according to the target address granularity.
  • one sending attribute in response to the sending attributes being set according to service type granularity, one sending attribute is associated with one service type, and at least one service type is associated with one target address.
  • all sending attributes associated with the first target address include: sending attributes associated with all service types associated with the first target address.
  • one sending attribute is associated with one target address in response to the sending attributes being set at target address granularity.
  • one or more transmission attributes are associated with a target address, wherein the one or more transmission attributes include a transmission attribute indicating compatible carrier aggregation and/or a transmission indicating incompatible carrier aggregation. Attributes.
  • the above device further includes: a sending module; a processing module, further configured to determine that any first target address is compatible with carrier aggregation; and a sending module, configured to simultaneously send one or more first target addresses on multiple carriers.
  • a sending module configured to simultaneously send one or more first target addresses on multiple carriers.
  • the above device further includes: a sending module; a processing module, further configured to determine that all first target addresses are incompatible with carrier aggregation; and a sending module, configured to send one or more first services on a single carrier The data.
  • the above device further includes: a sending module; a processing module, further configured to determine that all first target addresses are compatible with carrier aggregation; and a sending module, configured to simultaneously send one or more first target addresses on multiple carriers.
  • a sending module configured to simultaneously send one or more first target addresses on multiple carriers.
  • the above device further includes: a sending module; a processing module, further configured to determine that any first target address is not compatible with carrier aggregation; and a sending module, configured to send one or more first destination addresses on a single carrier.
  • a sending module configured to send one or more first destination addresses on a single carrier.
  • a communication device may be a receiving device in a side-link communication system or a chip or system-on-chip in the receiving device. It may also be a receiving device used to implement the above embodiments.
  • the communication device can realize the functions performed by the receiving devices in the above embodiments, and these functions can be realized by hardware executing corresponding software. These hardware or software include one or more modules corresponding to the above functions.
  • the communication device includes: a processing module configured to determine that the second target address is compatible with carrier aggregation when all transmission attributes associated with the second target address correspond to compatible carrier aggregation; or, when at least one transmission attribute associated with the second target address corresponds to When carrier aggregation is not compatible, it is determined that the second target address is not compatible with carrier aggregation; wherein the second target address is the target address of the second service of interest, and the second service is a broadcast service or a multicast service.
  • the transmission attribute is used to indicate whether the broadcast service or the multicast service is compatible with carrier aggregation.
  • the sending attributes are set according to the service type granularity, or the sending attributes are set according to the target address granularity.
  • one sending attribute in response to the sending attributes being set according to service type granularity, one sending attribute is associated with one service type, and at least one service type is associated with one target address.
  • all sending attributes associated with the second target address include: sending attributes associated with all service types associated with the second target address.
  • one sending attribute is associated with one target address in response to the sending attributes being set at target address granularity.
  • one or more transmission attributes are associated with a target address, wherein the one or more transmission attributes include a transmission attribute indicating compatible carrier aggregation and/or a transmission indicating incompatible carrier aggregation. Attributes.
  • the above device further includes: a receiving module; a processing module, further configured to determine that any second target address is compatible with carrier aggregation; and a receiving module configured to simultaneously receive one or more third destination addresses on multiple carriers.
  • the above device further includes: a receiving module; a processing module, further configured to determine that all second target addresses are incompatible with carrier aggregation; and a receiving module, configured to receive one or more second services on a single carrier The data.
  • the above device further includes: a receiving module; a processing module, further configured to determine that all second target addresses are compatible with carrier aggregation; and a receiving module, configured to simultaneously receive one or more second target addresses on multiple carriers.
  • a receiving module further includes: a receiving module; a processing module, further configured to determine that all second target addresses are compatible with carrier aggregation; and a receiving module, configured to simultaneously receive one or more second target addresses on multiple carriers.
  • the above device further includes: a receiving module; a processing module, further configured to determine that any second target address is incompatible with carrier aggregation; and a receiving module, configured to receive one or more second destination addresses on a single carrier.
  • a receiving module further includes: a receiving module; a processing module, further configured to determine that any second target address is incompatible with carrier aggregation; and a receiving module, configured to receive one or more second destination addresses on a single carrier.
  • a communication device such as a transmitting device, including: an antenna; a memory; and a processor, respectively connected to the antenna and the memory, and configured to control the antenna by executing computer-executable instructions stored in the memory.
  • Transceiver and can implement the method described in any one of the first aspect of the present disclosure and its possible implementations.
  • a communication device such as a receiving device, including: an antenna; a memory; and a processor, respectively connected to the antenna and the memory, and configured to control the antenna by executing computer-executable instructions stored in the memory. Transmission and reception, and can implement the method described in any one of the second aspect of the present disclosure and its possible implementations.
  • a computer storage medium stores computer-executable instructions.
  • the computer-executable instructions after being executed by a processor, can implement the first to second aspects of the present disclosure and their possibilities. The method according to any one of the embodiments.
  • a computer program or computer program product is provided.
  • the computer program product When the computer program product is executed on a computer, the computer can implement any one of the first to second aspects of the present disclosure and its possible implementations. method described in the item.
  • the side link terminal device determines whether the target address of the first service is compatible with carrier aggregation according to the indication of the associated transmission attribute (Tx profile), that is, determines whether the associated receiving device supports carrier aggregation.
  • Tx profile the indication of the associated transmission attribute
  • the side-link carrier aggregation scenario it is guaranteed that terminal equipment of previous versions (such as terminal equipment in the Rel-16 or Rel-17 version of the communication protocol) can receive the latest version of the terminal equipment (such as the Rel-18 version of the communication protocol). Broadcast services or multicast services sent by terminal equipment that supports carrier aggregation in the communication protocol, thereby achieving backward compatibility of side-link terminal equipment and thereby improving terminal equipment performance.
  • Figure 1 is an architectural schematic diagram of a communication system in an embodiment of the present disclosure
  • Figure 2 is another architectural schematic diagram of a communication system in an embodiment of the present disclosure
  • Figure 3 is a schematic flowchart of the implementation of a side-link communication method in an embodiment of the present disclosure
  • Figure 4 is a schematic flowchart of the implementation of a side-link communication method in an embodiment of the present disclosure
  • Figure 5 is a schematic flowchart of the implementation of a side-link communication method in an embodiment of the present disclosure
  • Figure 6 is a schematic flowchart of the implementation of a side-link communication method in an embodiment of the present disclosure
  • Figure 7 is a schematic flowchart of the implementation of a side-link communication method in an embodiment of the present disclosure
  • Figure 8 is a schematic flowchart of the implementation of a side-link communication method in an embodiment of the present disclosure
  • FIG9 is a schematic diagram of the structure of a measurement reporting device in an embodiment of the present disclosure.
  • Figure 10 is a schematic structural diagram of a communication device in an embodiment of the present disclosure.
  • Figure 11 is a schematic structural diagram of a terminal device in an embodiment of the present disclosure.
  • Figure 12 is a schematic structural diagram of a network device in an embodiment of the present disclosure.
  • first, second, third, etc. may be used to describe various information in the embodiments of the present disclosure, the information should not be limited to these terms. These terms are only used to distinguish information of the same type from each other. For example, without departing from the scope of the embodiments of the present disclosure, “first information” may also be called “second information”, and similarly, “second information” may also be called “first information”. Depending on the context, the word “if” as used herein may be interpreted as “when” or “when” or “in response to determining.”
  • Wireless communication between communication devices may include: wireless communication between network devices and terminal devices, wireless communication between network devices and network devices, and wireless communication between terminal devices.
  • wireless communication may also be referred to as “communication”
  • communication may also be described as "data transmission”, “information transmission” or “transmission”.
  • Side-link networks support multiple transmission modes such as unicast, multicast, and broadcast.
  • the network dynamic scheduling method i.e., mode 1
  • the terminal device's independent selection in the network broadcast resource pool i.e., mode 1). That is mode 2).
  • mode1 the network dynamically allocates SL transmission resources to the terminal device based on the cached data reported by the terminal device
  • the terminal device randomly selects SL transmission resources from network broadcasts or preconfigured resource pools.
  • the "preconfiguration" may be obtained by the terminal device from the network element of the core network, or may be preset in the terminal device.
  • the specific resource allocation method used by the terminal device can be configured by the network side through high-level signaling (such as radio resource control (RRC) signaling).
  • the sending device sends sidelink control information (SCI) on the physical sidelink control channel (PSCCH) and sends SCI on the physical sidelink shared channel (PSSCH). , which carries the resource location of the transmitted data as well as source and target identifiers, etc.
  • SCI sidelink control information
  • PSSCH physical sidelink shared channel
  • the receiving device performs HARQ feedback on the PSSCH on the physical sidelink feedback channel (PSFCH).
  • HARQ hybrid automatic repeat request
  • CA carrier aggregation
  • LTE long-term evolution
  • CA side-link carrier aggregation
  • terminal devices of previous versions may not be able to receive terminals that support carrier aggregation.
  • the broadcast service or multicast service sent by the equipment (such as the terminal equipment in the Rel-18 version of the communication protocol) has the problem of backward incompatibility of the side link terminal equipment.
  • FIG. 1 is an architectural schematic diagram of a communication system in an embodiment of the present disclosure.
  • the communication system 10 may include: a network device 11 and a terminal device 12 .
  • FIG. 2 is another architectural schematic diagram of a communication system in an embodiment of the present disclosure.
  • the communication system 10 may also include multiple terminal devices 12 .
  • the type and number of network elements included in the communication system, and the connection relationship between the network elements are not limited thereto.
  • the terminal device while the terminal device communicates with the network device, it can also communicate with other terminal devices.
  • Network equipment can configure, schedule, coordinate resources, etc. for side links for communication between terminal devices to assist direct communication between terminal devices.
  • Terminal devices can also perform resource configuration, scheduling, coordination, etc. on their own for side links for communication between other terminal devices, which are not specifically limited in the embodiments of this disclosure.
  • the above-mentioned network device may be a device on the access network side used to support terminal devices to access the wireless communication system.
  • it may be a next generation base station (next generation NodeB, gNB), transmission reception point (TRP), relay node (relay node), access point (AP), roadside device (road site unit, RSU), etc.
  • the above terminal device may be a device that provides voice or data connectivity to users, and may also be called user equipment (UE), mobile station, subscriber unit, or STAtion. Or terminal (terminal equipment, TE), etc.
  • the communication device can be a cellular phone, a personal digital assistant (PDA), a wireless modem, a handheld vehicle to perdestrian, a laptop computer, a cordless phone ( cordless phone), wireless local loop (WLL) station or tablet (pad), relay node, AP, etc.
  • PDA personal digital assistant
  • WLL wireless local loop
  • devices that can access the wireless communication system, communicate with the network side of the wireless communication system, or communicate with other devices through the wireless communication system can be terminal devices in the embodiments of the present application.
  • Communication equipment can be static or mobile.
  • the above communication devices may be divided into sending devices and receiving devices according to data transmission directions.
  • the sending device may also be called a sending device
  • the sending device may include a sending network device, a sending terminal device, a sending user device, etc.
  • the receiving device may include a receiving network device, a receiving device, etc. end terminal equipment, receiving end user equipment, etc.
  • the above-mentioned sending device (may also be called a sending network device, a sending terminal device, a sending user device, etc.) and a receiving device (may also be called a receiving network device, a receiving terminal device, a receiving user device, etc.) equipment, etc.) is for a certain sidelink connection.
  • a communication device (or network device, terminal device, user equipment, etc.) for side link connection A can be a sending device (or sending end network device, sending end terminal equipment, sending end user equipment, etc.); and
  • the communication device (or network device, terminal device, user device, etc.) may be a receiving device, a receiving network device, a receiving terminal device, a receiving user device, etc.).
  • the associated transmission is set (also referred to as “defined”).
  • Properties Tx profile
  • the "send attribute” can also be described as “send configuration”, “send configuration file”, “send file”, etc.
  • the Tx profile is introduced to ensure the compatibility of broadcast or multicast transmission between terminal devices that are compatible or incompatible with the carrier aggregation function. It can be understood that the Tx profile is used to indicate whether the broadcast/multicast service is compatible with carrier aggregation, that is, the Tx profile is used to indicate whether the broadcast service or multicast service is compatible with carrier aggregation or is not compatible with carrier aggregation.
  • the Tx profile can indicate the version of a communication standard (such as Rel-18), or whether carrier aggregation is enabled (such as carrier aggregation compatible (ca-compatible), carrier aggregation incompatible (ca-incompatible)).
  • the above "whether the broadcast/multicast service is compatible with carrier aggregation" can be understood as: for a certain broadcast/multicast service, whether the side link resources on multiple carriers can be used simultaneously to transmit the target associated with the service Address data.
  • the destination address can be identified by destination ID.
  • the Tx profile can be set according to the service type granularity or according to the target address granularity.
  • one Tx profile is associated with one service type, that is to say, the Tx profile corresponds to the service type one-to-one, and different service types are associated with different Tx profiles.
  • at least one service type is associated with one target address, which means that one target address can be associated with multiple different service types, so there may be one or more Tx profiles associated with one target address.
  • the destination ID corresponding to the first destination address is A
  • the service types associated with the first destination address are type A, type B, and type C.
  • Type A corresponds to Tx profile 1
  • type B corresponds to Tx profile 2
  • type C corresponds to Tx profile 3.
  • the Tx profiles associated with the first target address are Tx profile 1, Tx profile 2 and Tx profile 3.
  • one Tx profile is associated with one target address, that is, there is only one Tx profile associated with one target address, and it needs to be implemented by the upper layer. Ensure that all service types associated with a target address have the same Tx profile. For example, the destination ID corresponding to the first destination address is A, and the Tx profile associated with the first destination address is Tx profile 1.
  • one or more Tx profiles are associated with a target address, where one or more Tx profiles include a Tx profile used to indicate compatible carrier aggregation and/or used to indicate incompatible carriers. Aggregated Tx profile.
  • one or more Tx profiles can be associated with a target address, including Tx profiles corresponding to compatible carrier aggregation and Tx profiles corresponding to incompatible carrier aggregation.
  • the association between the Tx profile and the target address may also exist in other situations, and this embodiment of the present disclosure does not specifically limit this.
  • the Tx profile associated with the target address is provided to the access stratum (AS) by a higher layer (such as the V2X layer), and identifies one or more sidelink feature group(s) ).
  • the higher layer may indicate the Tx profile to the AS in the form of a Tx profile list.
  • the higher layer can also indicate the Tx profile to the AS in other forms such as a linked list, an index, etc. This is not specifically limited in the embodiment of the present disclosure.
  • the higher layer can indicate the Tx profile to the AS in the form of a Tx profile list.
  • the list can include Tx profiles associated with different service types, or the list can include different targets.
  • the higher layer can also indicate the Tx profile to the AS in the form of a Tx profile list, and the list can include Tx profiles associated with different target addresses.
  • the above Tx profile settings can be understood as preconfigured by the side link system (or specified in the communication protocol). Each network element in the side link system is executed according to the above Tx profile settings.
  • a side-link communication method provided by an embodiment of the present disclosure will be described below.
  • embodiments of the present disclosure provide a side link communication method, which can be applied to the sending device side in the side link communication system.
  • Figure 3 is a schematic flowchart of the implementation of a side-link communication method in an embodiment of the present disclosure. Referring to Figure 3, for Tx profile settings based on service type granularity, the above method may include:
  • the sending device determines the first target address of the first service.
  • the first service may be a broadcast/multicast service.
  • the higher layer triggers the first service, and the higher layer determines the first target address associated with the first service and instructs the AS.
  • the AS uses one or more Tx profiles associated with the target address of the first service indicated by the higher layer, Determine the Tx profile associated with the first target address. This one or more Tx profiles correspond to multiple business types.
  • one or more Tx profiles associated with the first target address can be understood as Tx corresponding to one or more service types associated with the first target address. profile. Different Tx profiles can indicate whether services of different service types are compatible with carrier aggregation.
  • the sending device may perform S302 or S303.
  • the AS can determine the Tx profile associated with the first target address according to instructions from the higher layer, and then determine whether each Tx profile corresponds to compatible carrier aggregation or incompatible carrier aggregation.
  • the AS determines that the Tx profiles associated with all task types associated with the first target address correspond to compatible carrier aggregation (it can also be understood that all Tx profiles associated with the first target address indicate compatible carrier aggregation).
  • the AS determines that the first target address is compatible with carrier aggregation. Carrier aggregation.
  • the sending device assumes (can also be described as assuming, supposing, etc.) that the first target address is compatible with carrier aggregation.
  • the AS determines that at least one Tx profile associated with the service type associated with the first target address corresponds to incompatible carrier aggregation (it can also be understood that at least one Tx profile associated with the first target address indicates incompatible carrier aggregation).
  • the AS determines that the first target address is not compatible with carrier aggregation.
  • the sending device believes (can also be described as assuming, supposing, etc.) that the first target address is not compatible with carrier aggregation.
  • the above "at least one Tx profile associated with the first target address corresponds to incompatible carrier aggregation” can also be understood as any Tx profile in the Tx profile associated with the first target address (that is, any Tx profile associated with the first target address).
  • a Tx profile) corresponds to incompatible carrier aggregation, or it can also be understood that any Tx profile associated with the first target address indicates incompatible carrier aggregation.
  • the first destination address is destination A.
  • the service types associated with the first destination address are type A, type B and type C.
  • Type A corresponds to Tx profile 1
  • type B corresponds to Tx profile 2
  • type C corresponds to Tx profile 1.
  • the Tx profiles associated with destination A are Tx profile 1, Tx profile 2 and Tx profile 3. If Tx profile 1 indicates that the broadcast/multicast service of type A is compatible with carrier aggregation, Tx profile 2 indicates that the broadcast/multicast service of type B is compatible with carrier aggregation, and Tx profile 3 indicates that the broadcast/multicast service of type C is compatible with carrier aggregation, AS It can be determined that all Tx profiles associated with destination A correspond to compatible carrier aggregation.
  • the AS determines that destination A is compatible with carrier aggregation.
  • the AS can determine that at least one Tx profile associated with destination A corresponds to incompatible carrier aggregation. This , the AS determines that destination A is not compatible with carrier aggregation.
  • the sending device can trigger one or more broadcast/multicast services, that is, trigger one or more first services. Then, the sending device can target each of the one or more first services. A service performs the above-mentioned S301 to S303 respectively, thereby determining whether one or more first target addresses are compatible with carrier aggregation. After determining whether one or more first target addresses are compatible with carrier aggregation, the sending device may choose to enable or disable carrier aggregation, thereby sending data of one or more first services on multiple carriers or on multiple carriers. Data of one or more first services is sent on a single carrier.
  • Figure 4 is a schematic flowchart of an implementation of a side-link communication method in an embodiment of the present disclosure.
  • the sending device can perform S401 to S402 (as shown by the solid line) Or S403 to S404 (shown as dotted lines).
  • the sending device determines that all first target addresses are compatible with carrier aggregation.
  • the sending device simultaneously sends data of one or more first services on multiple carriers.
  • the AS determines that all first target addresses in one or more first target addresses are compatible with carrier aggregation. At this time, the AS enables carrier aggregation and sends one or more first target addresses on multiple carriers simultaneously. First business data.
  • the sending device determines that any first target address is not compatible with carrier aggregation.
  • any first target address is not compatible with carrier aggregation can be understood to mean that at least one of the one or more first target addresses is not compatible with carrier aggregation.
  • the sending device sends data of one or more first services on a single carrier.
  • the single carrier may be a default carrier, such as a sidelink carrier in the Rel-16 or Rel-17 version of the communication protocol.
  • the AS determines that any one of the one or more first target addresses is not compatible with carrier aggregation. At this time, the AS disables carrier aggregation and sends one or more first target addresses on a single carrier. data of the first business.
  • the destination addresses of multiple first services may be destination A, destination B, and destination C.
  • the sending device executes the above S301 to 304 to determine whether destination A, destination B, and destination C are compatible. Carrier aggregation. If it is determined that destination A is compatible with carrier aggregation, destination B is compatible with carrier aggregation, and destination C is compatible with carrier aggregation, the AS enables carrier aggregation and sends data of multiple first services on multiple carriers at the same time. Or, if it is determined that any of the destination addresses in destination A, destination B, and destination C is not compatible with carrier aggregation, the AS disables carrier aggregation and sends multiple first service data on a single carrier.
  • Figure 5 is a schematic flowchart of an implementation of a side-link communication method in an embodiment of the present disclosure.
  • the sending device can perform S501 to S502 (as shown by the solid line ) or S503 to S504 (shown as dotted lines).
  • the sending device determines that any first target address is compatible with carrier aggregation.
  • any first target address is compatible with carrier aggregation can be understood to mean that at least one first target address among one or more first target addresses is compatible with carrier aggregation.
  • the sending device simultaneously sends data of one or more first services on multiple carriers.
  • the AS determines that any one of the one or more first target addresses is compatible with carrier aggregation. At this time, the AS enables carrier aggregation and sends one or more first target addresses on multiple carriers simultaneously. data of the first business.
  • S503 The sending device determines that all first target addresses are not compatible with carrier aggregation.
  • the sending device sends data of one or more first services on a single carrier.
  • the AS determines that all first target addresses in one or more first target addresses are not compatible with carrier aggregation. At this time, the AS disables carrier aggregation and sends one or more first target addresses on a single carrier. First business data.
  • the destination addresses of multiple first services may be destination A, destination B, and destination C.
  • the sending device executes the above S301 to 304 to determine whether destination A, destination B, and destination C are compatible. Carrier aggregation. If it is determined that any of the destination addresses in destination A, destination B, and destination C is compatible with carrier aggregation, the AS enables carrier aggregation and sends data of multiple first services on multiple carriers at the same time. Or, if it is determined that destination A is not compatible with carrier aggregation, destination B is not compatible with carrier aggregation, and destination C is not compatible with carrier aggregation, the AS disables carrier aggregation and sends multiple first service data on a single carrier.
  • Figure 6 is a schematic flowchart of the implementation of a side-link communication method in an embodiment of the present disclosure.
  • the above method may include:
  • the sending device determines the first target address of the first service.
  • the first service may be a broadcast/multicast service.
  • the higher layer triggers the first service, and the higher layer determines the first target address associated with the first service and indicates the AS.
  • the AS determines the Tx profile associated with the first target address through the Tx profile associated with the target address of the first service indicated by the higher layer.
  • a first destination address is associated with a Tx profile.
  • the sending device may perform S602 or S603.
  • the AS can determine a Tx profile associated with the first target address according to instructions from the higher layer, and then determine whether the Tx profile corresponds to compatible carrier aggregation or incompatible carrier aggregation.
  • the AS determines that the Tx profile associated with the first target address corresponds to compatible carrier aggregation (it can also be understood that the Tx profile associated with the first target address indicates compatible carrier aggregation).
  • the AS determines that the first target address is compatible with carrier aggregation.
  • the sending device (such as AS) assumes (can also be described as assuming, assuming, etc.) that the first target address is compatible with carrier aggregation.
  • Tx profile associated with the first target address corresponds to compatible carrier aggregation
  • Tx profile associated with the first target address can also be understood as the only Tx profile associated with the first target address corresponds to compatible carrier aggregation, or all Tx profiles associated with the first target address profile corresponds to compatible carrier aggregation.
  • the AS determines that the Tx profile associated with the first target address corresponds to incompatible carrier aggregation (it can also be understood that the Tx profile associated with the first target address indicates incompatible carrier aggregation). At this time, the AS determines that the first target address is not compatible with carrier aggregation. Compatible with carrier aggregation. At this time, the sending device (such as the AS) believes (can also be described as assuming, supposing, etc.) that the first target address is not compatible with carrier aggregation.
  • Tx profile associated with the first target address corresponds to incompatible carrier aggregation
  • Tx profile associated with the first target address can also be understood as the only Tx profile associated with the first target address corresponds to incompatible carrier aggregation, or it can also be understood as the first Tx profile associated with the first target address corresponds to incompatible carrier aggregation.
  • a Tx profile associated with the target address indicates incompatibility with carrier aggregation.
  • the first target address is destination A
  • the Tx profile associated with the first target address is Tx profile 1.
  • AS can determine that all Tx profiles associated with destination A correspond to compatible carrier aggregation. At this time, AS determines that destination A is compatible with carrier aggregation.
  • Tx profile 1 indicates that the broadcast/multicast service is incompatible with carrier aggregation
  • AS can determine that a Tx profile associated with destination A corresponds to incompatible carrier aggregation. At this time, AS determines that destination A is incompatible with carrier aggregation.
  • the sending device can also trigger one or more broadcast/multicast services, that is, trigger one or more first services. Then, the sending device can target each of the one or more first services. The first service performs the above-mentioned S601 to S603 respectively, thereby determining whether one or more first target addresses are compatible with carrier aggregation. Next, after S602 or S603, the sending device may also, but is not limited to, perform the above-mentioned S401 to S404 or S501 to S504, which will not be described again here.
  • embodiments of the present disclosure also provide a side-link communication method, which can be applied to the receiving device side in the side-link communication system.
  • Figure 7 is a schematic flowchart of the implementation of a side-link communication method in an embodiment of the present disclosure. Referring to Figure 7, for Tx profile settings based on service type granularity, the above method may include:
  • the receiving device determines the second target address of the second service.
  • the second service may be a broadcast/multicast service that the receiving device is interested in.
  • the higher layer determines the second service of interest and indicates the second target address of the second service to the AS.
  • the AS associates one or more Txs with the target address of the second service indicated by the higher layer. profile, determine one or more Tx profiles associated with the second target address. This one or more Tx profiles correspond to multiple business types.
  • the sending device may perform S702 or S703.
  • the receiving device may also be interested in one or more broadcast/multicast services, that is, there are one or more second services. Then, the receiving device may target one or more second services. Each second service performs the above-mentioned S701 to S703 respectively, thereby determining whether one or more second target addresses are compatible with carrier aggregation. After determining whether one or more second target addresses are compatible with carrier aggregation, the receiving device can choose to enable or disable carrier aggregation, thereby receiving data of one or more second services on multiple carriers or on multiple carriers. Receive data of one or more second services on a single carrier.
  • Figure 8 is a schematic flowchart of an implementation of a side-link communication method in an embodiment of the present disclosure.
  • the sending device can perform S801 to S802 (as shown by the solid line) Or S803 to S804 (shown as dotted lines).
  • the receiving device determines that all second target addresses are compatible with carrier aggregation.
  • S802 The receiving device simultaneously receives data of one or more second services on multiple carriers.
  • S803 The receiving device determines that any second target address is not compatible with carrier aggregation.
  • any second target address is not compatible with carrier aggregation can be understood to mean that at least one of the one or more second target addresses is not compatible with carrier aggregation.
  • the receiving device receives data of one or more second services on a single carrier.
  • the single carrier may be a default carrier, such as a sidelink carrier in the Rel-16 or Rel-17 version of the communication protocol.
  • the sending device may perform S805 to S806 (shown as a solid line) or S807 to S808 (shown as a dotted line).
  • S805 The receiving device determines that any second target address is compatible with carrier aggregation.
  • S806 The receiving device simultaneously receives data of one or more second services on multiple carriers.
  • S807 The receiving device determines that all second target addresses are incompatible with carrier aggregation.
  • the receiving device determines to receive data of one or more second services on a single carrier.
  • the side link terminal device determines whether the target address of the first service is compatible with carrier aggregation according to the indication of the associated Tx profile, that is, determines whether the associated receiving device supports carrier aggregation.
  • terminal equipment of previous versions such as terminal equipment in the Rel-16 or Rel-17 version of the communication protocol
  • the latest version of the terminal equipment such as the Rel-18 version of the communication protocol.
  • Broadcast services or multicast services sent by terminal equipment that supports carrier aggregation in the communication protocol thereby achieving backward compatibility of side-link terminal equipment and thereby improving terminal equipment performance.
  • FIG. 9 is a schematic structural diagram of a communication device in an embodiment of the present disclosure.
  • the communication device 900 may include: processing module 901 and transmission module 902.
  • the communication device 900 can be a sending device in a side-link communication system or a chip or system-on-chip in the sending device, or can also be a functional module in the sending device for implementing the methods of the above embodiments.
  • the communication device can realize the functions performed by the sending device in the above embodiments, and these functions can be realized by hardware executing corresponding software. These hardware or software include one or more modules corresponding to the above functions.
  • the transmission module 902 can be understood as the sending module 902a.
  • the processing module 901 is configured to determine that the first target address is compatible with carrier aggregation when all transmission attributes (Tx profiles) associated with the first target address correspond to compatible carrier aggregation; or, when at least one of the Tx profiles associated with the first target address When the sending attribute corresponds to incompatible carrier aggregation, it is determined that the first destination address is incompatible with carrier aggregation; wherein the first destination address is the destination address of the first service, and the first service is a broadcast service or a multicast service.
  • Tx profiles transmission attributes
  • the transmission attribute is used to indicate that the broadcast service or multicast service is compatible with carrier aggregation or is incompatible with carrier aggregation.
  • the sending attributes are set according to the service type granularity, or the sending attributes are set according to the target address granularity.
  • one sending attribute in response to the sending attributes being set according to service type granularity, one sending attribute is associated with one service type, and at least one service type is associated with one target address.
  • all sending attributes associated with the first target address include: sending attributes associated with all service types associated with the first target address.
  • one sending attribute is associated with one target address in response to the sending attributes being set at target address granularity.
  • one or more transmission attributes are associated with a target address, wherein the one or more transmission attributes include a transmission attribute indicating compatible carrier aggregation and/or a transmission indicating incompatible carrier aggregation. Attributes.
  • the processing module 901 is also configured to determine that any first target address is compatible with carrier aggregation; the sending module 902a is configured to simultaneously send data of one or more first services on multiple carriers.
  • the processing module 901 is also configured to determine that all first target addresses are not compatible with carrier aggregation; the sending module 902a is configured to send data of one or more first services on a single carrier.
  • the processing module 901 is also configured to determine that all first target addresses are compatible with carrier aggregation; the sending module 902a is configured to simultaneously send data of one or more first services on multiple carriers.
  • the processing module 901 is also configured to determine that any first target address is not compatible with carrier aggregation; the sending module 902a is configured to send data of one or more first services on a single carrier.
  • the communication device may be a receiving device in a side link communication system or a chip or system on chip in a receiving device, or may be a functional module in a receiving device for implementing the methods of the above-mentioned various embodiments.
  • the communication device may implement the functions performed by the receiving device in the above-mentioned embodiments, and these functions may be implemented by hardware executing corresponding software. These hardware or software include one or more modules corresponding to the above-mentioned functions.
  • the transmission module 902 may be understood as the receiving module 902 b.
  • the processing module 901 is configured to determine that the second target address is compatible with carrier aggregation when all transmission attributes associated with the second target address correspond to compatible carrier aggregation; or, when at least one transmission attribute associated with the second target address corresponds to When carrier aggregation is not compatible, it is determined that the second target address is not compatible with carrier aggregation; wherein the second target address is the target address of the second service of interest, and the second service is a broadcast service or a multicast service.
  • the transmission attribute is used to indicate that the broadcast service or multicast service is compatible with carrier aggregation or is incompatible with carrier aggregation.
  • the sending attributes are set according to the service type granularity, or the sending attributes are set according to the target address granularity.
  • one sending attribute in response to the sending attributes being set according to service type granularity, one sending attribute is associated with one service type, and at least one service type is associated with one target address.
  • all sending attributes associated with the second target address include: sending attributes associated with all service types associated with the second target address.
  • one sending attribute is associated with one target address in response to the sending attributes being set at target address granularity.
  • one or more transmission attributes are associated with a target address, wherein the one or more transmission attributes include a transmission attribute indicating compatible carrier aggregation and/or a transmission indicating incompatible carrier aggregation. Attributes.
  • the processing module 901 is also configured to determine that any second target address is compatible with carrier aggregation; the receiving module 902b is configured to simultaneously receive data of one or more second services on multiple carriers.
  • the processing module 901 is also configured to determine that all second target addresses are incompatible with carrier aggregation; the receiving module 902b is configured to receive data of one or more second services on a single carrier.
  • the processing module 901 is also configured to determine that all second target addresses are compatible with carrier aggregation; the receiving module 902b is configured to simultaneously receive data of one or more second services on multiple carriers.
  • the processing module 901 is also configured to determine that any second target address is not compatible with carrier aggregation; the receiving module 902b is configured to receive data of one or more second services on a single carrier.
  • the receiving module 902b mentioned in the embodiment of the present disclosure may be a receiving interface, a receiving circuit or a receiver, etc.
  • the sending module 902a may be a transmitting interface, a transmitting circuit or a transmitter, etc.
  • the processing module 901 may be one or more processors.
  • FIG. 10 is a schematic structural diagram of a communication device in an embodiment of the present disclosure.
  • the communication device 100 uses general computer hardware, including a processor 101, a memory 102, a bus 103, an input device 104 and an output Device 105.
  • memory 102 may include computer storage media in the form of volatile and/or non-volatile memory, such as read-only memory and/or random access memory.
  • Memory 102 may store an operating system, application programs, other program modules, executable code, program data, user data, and the like.
  • Input device 104 may be used to input commands and information to a communication device, such as a keyboard or pointing device such as a mouse, trackball, touch pad, microphone, joystick, game pad, satellite television antenna, scanner, or similar device. These input devices may be connected to processor 101 via bus 103 .
  • a communication device such as a keyboard or pointing device such as a mouse, trackball, touch pad, microphone, joystick, game pad, satellite television antenna, scanner, or similar device.
  • the output device 105 can be used for a communication device to output information.
  • the output device 105 can also be other peripheral output devices, such as speakers and/or printing devices. These output devices can also be connected to the processor 101 through the bus 103 .
  • the communication device may be connected to a network through the antenna 106, such as a local area network (LAN).
  • LAN local area network
  • the computer execution instructions stored in the control device can be stored in a remote storage device and are not limited to local storage.
  • the communication device executes the mobility management configuration method on the terminal device side or the network device side in the above embodiments.
  • the specific execution process refer to the above. The embodiments will not be described again here.
  • the above-mentioned memory 102 stores computer execution instructions for realizing the functions of the processing module 901 and the transmission module 902 in FIG. 9 .
  • the functions/implementation processes of the processing module 901 and the transmission module 902 in Figure 9 can be realized by the processor 101 in Figure 10 calling the computer execution instructions stored in the memory 102.
  • specific implementation processes and functions refer to the above-mentioned related embodiments.
  • embodiments of the present disclosure provide a terminal device, which is similar to the sending terminal device, sending user device, receiving terminal device, receiving user device, etc. in one or more of the above embodiments.
  • the terminal equipment is consistent.
  • the terminal device can be a mobile phone, a computer, a digital broadcast terminal device, a messaging device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, etc.
  • Figure 11 is a schematic structural diagram of a terminal device in an embodiment of the present disclosure.
  • the terminal device 110 may include one or more of the following components: a processing component 111, a memory 112, a power supply component 113, a multimedia component 114, and an audio component.
  • a processing component 111 may include one or more of the following components: a memory 112, a power supply component 113, a multimedia component 114, and an audio component.
  • I/O Input/output (I/O) interface 116, sensor component 117 and communication component 118.
  • the processing component 111 generally controls the overall operations of the terminal device 110, such as operations related to display, phone calls, data communications, camera operations, and recording operations.
  • the processing component 111 may include one or more processors 1111 to execute instructions to complete all or part of the steps of the above method.
  • processing component 111 may include one or more modules to facilitate interaction between processing component 111 and other components.
  • processing component 111 may include a multimedia module to facilitate interaction between multimedia component 114 and processing component 111 .
  • the memory 112 is configured to store various types of data to support operations at the terminal device 110 . Examples of such data include instructions for any application or method operating on the terminal device 110, contact data, phonebook data, messages, pictures, videos, etc.
  • Memory 112 may be implemented by any type of volatile or non-volatile storage device, or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EEPROM), Programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disk.
  • SRAM static random access memory
  • EEPROM electrically erasable programmable read-only memory
  • EEPROM erasable programmable read-only memory
  • EPROM Programmable read-only memory
  • PROM programmable read-only memory
  • ROM read-only memory
  • magnetic memory flash memory
  • flash memory magnetic or optical disk.
  • the power supply component 113 provides power to various components of the terminal device 110 .
  • Power supply component 113 may include a power management system, one or more power supplies, and other components related to generating, managing, and distributing power to end device 110 .
  • Multimedia component 114 includes a screen that provides an output interface between terminal device 110 and the user.
  • the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from the user.
  • the touch panel includes one or more touch sensors to sense touches, slides, and gestures on the touch panel. A touch sensor can not only sense the boundaries of a touch or swipe action, but also detect the duration and pressure associated with the touch or swipe action.
  • multimedia component 114 includes a front-facing camera and/or a rear-facing camera.
  • the front camera and/or the rear camera may receive external multimedia data.
  • Each front-facing camera and rear-facing camera can be a fixed optical lens system or have a focal length and optical zoom capabilities.
  • Audio component 115 is configured to output and/or input audio signals.
  • the audio component 115 includes a microphone (MIC) configured to receive external audio signals when the terminal device 110 is in an operating mode, such as a call mode, a recording mode, and a voice recognition mode.
  • the received audio signals may be further stored in memory 112 or sent via communications component 118 .
  • audio component 115 also includes a speaker for outputting audio signals.
  • the I/O interface 116 provides an interface between the processing component 111 and a peripheral interface module.
  • the peripheral interface module may be a keyboard, a click wheel, a button, etc. These buttons may include, but are not limited to: Home button, Volume buttons, Start button, and Lock button.
  • the sensor component 117 includes one or more sensors for providing various aspects of status assessment for the terminal device 110 .
  • the sensor component 117 can monitor the open/closed state of the terminal device 110 and the relative positioning of components, such as the display and keypad of the terminal device 110.
  • the sensor component 117 can also detect the status of the terminal device 110 or a component of the terminal device 110. Position changes, presence or absence of user contact with the terminal device 110 , orientation or acceleration/deceleration of the terminal device 110 and temperature changes of the terminal device 110 .
  • Sensor assembly 117 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact.
  • Sensor assembly 117 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications.
  • the sensor component 117 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
  • the communication component 118 is configured to facilitate wired or wireless communication between the terminal device 110 and other devices.
  • the terminal device 110 may access a wireless network using a communication standard, such as Wi-Fi, 2G, 3G, 4G or 5G, or a combination thereof.
  • communication component 118 receives broadcast signals or broadcast related information from an external broadcast management system via a broadcast channel.
  • communications component 118 also includes a near field communications (NFC) module to facilitate short-range communications.
  • NFC near field communications
  • the NFC module can be implemented using radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology and other technologies.
  • RFID radio frequency identification
  • IrDA infrared data association
  • UWB ultra-wideband
  • Bluetooth Bluetooth
  • the terminal device 110 may be configured by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable A programmable gate array (FPGA), controller, microcontroller, microprocessor or other electronic component implementation is used to perform the above method.
  • ASICs application specific integrated circuits
  • DSPs digital signal processors
  • DSPDs digital signal processing devices
  • PLDs programmable logic devices
  • FPGA field programmable A programmable gate array
  • controller microcontroller, microprocessor or other electronic component implementation is used to perform the above method.
  • embodiments of the present disclosure provide a network device that is consistent with network devices such as the sending network device and the receiving network device in one or more of the above embodiments.
  • Figure 12 is a schematic structural diagram of a network device in an embodiment of the present disclosure.
  • the network device 120 may include a processing component 121, which further includes one or more processors, and memory resources represented by memory 122.
  • a processing component 121 For storing instructions executable by the processing component 121, such as application programs.
  • An application program stored in memory 122 may include one or more modules, each of which corresponds to a set of instructions.
  • the processing component 121 is configured to execute instructions to perform any of the foregoing methods applied to the network device.
  • Network device 120 may also include a power supply component 123 configured to perform power management of network device 120, a wired or wireless network interface 124 configured to connect network device 120 to a network, and an input-output (I/O) interface 125 .
  • Network device 120 may operate using an operating system stored in memory 122, such as Windows ServerTM, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, or the like.
  • a terminal device includes: an antenna; a memory; and a processor, which is connected to the antenna and the memory respectively, and is configured to control the transmission and reception of the antenna by executing computer-executable instructions stored in the memory, and can implement the following: The method on the sending device side in one or more of the above embodiments.
  • a network device including: an antenna; a memory; and a processor, which are connected to the antenna and the memory respectively, and are configured to control the transmission and reception of the antenna by executing computer-executable instructions stored in the memory, and can implement the following: The method on the receiving device side in one or more of the above embodiments.
  • embodiments of the present disclosure also provide a computer-readable storage medium. Instructions are stored in the computer-readable storage medium; when the instructions are run on the computer, they are used to execute the instructions sent in one or more of the above embodiments.
  • Device side or receiving device side method are stored in the computer-readable storage medium; when the instructions are run on the computer, they are used to execute the instructions sent in one or more of the above embodiments.
  • embodiments of the present disclosure also provide a computer program or computer program product.
  • the computer program product When the computer program product is executed on a computer, the computer implements the sending device side or the receiving device side in one or more of the above embodiments. Methods.

Landscapes

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

Abstract

本公开提供了一种侧链路通信方法、通信装置及通信设备。该方法可以包括：当第一目标地址关联的所有发送属性对应于兼容载波聚合时，确定所述第一目标地址兼容载波聚合；当所述第一目标地址关联的至少一个发送属性对应于不兼容载波聚合时，确定所述第一目标地址不兼容载波聚合；其中，所述第一目标地址为第一业务的目标地址，所述第一业务为广播业务或者组播业务。

Description

一种侧链路通信方法、装置及通信设备 技术领域
本公开涉及无线通信技术领域，尤其涉及一种侧链路通信方法、装置及通信设备。
背景技术
随着无线通信技术的发展，为了支持终端设备与终端设备之间的直连通信，引入了侧链路(sidelink，SL)通信方式，终端设备与终端设备之间通过PC5接口进行通信。侧链路网络支持单播、组播以及广播等多种传输模式。
在基于长期演进(long term evolution，LTE)通信网络的车联网(vehicle to everything，V2X)中，已经支持侧链路载波聚合(carrier aggregation，CA)技术。终端设备由于发送接收能力限制，可能只能在某一个或者某几个载波上接收侧行链路业务。由于LTE V2X只支持广播业务，所以，针对终端设备受限的接收能力并没有引入任何载波选择/重选的增强方案。
那么，在新无线(new radio，NR)侧链路载波聚合场景中，之前版本的终端设备(如Rel-16或Rel-17版本的通信协议中的终端设备)可能会接收不到支持载波聚合的终端设备(如Rel-18版本的通信协议中的终端设备)发送的广播业务或组播业务，即存在侧链路终端设备后向不兼容的问题。
发明内容
本公开提供了一种侧链路通信方法、装置及通信设备，以实现侧链路终端设备的后向兼容性，进而提升终端设备性能。
根据本公开的第一方面提供一种侧链路通信方法，该方法可以应用于侧链路通信系统中的发送设备侧。该方法可以包括：当第一目标地址关联的所有发送属性对应于兼容载波聚合时，确定第一目标地址兼容载波聚合；或，当第一目标地址关联的至少一个发送属性对应于不兼容载波聚合时，确定第一目标地址不兼容载波聚合；其中，第一目标地址为第一业务的目标地址，第一业务为广播业务或者组播业务。
在一些可能的实施方式中，发送属性用于指示广播业务或者组播业务是否兼容载波聚合。
在一些可能的实施方式中，发送属性按照业务类型粒度设置，或发送属性按照目标地址粒度设置。
在一些可能的实施方式中，响应于发送属性按照业务类型粒度设置，一个发送属性与一个业务类型关联，至少一个业务类型与一个目标地址关联。
在一些可能的实施方式中，第一目标地址关联的所有发送属性包括：第一目标地址关联的所有业务类型关联的发送属性。
在一些可能的实施方式中，响应于发送属性按照目标地址粒度设置，一个发送属性与一个目标地 址关联。
在一些可能的实施方式中，一个或者多个发送属性关联于一个目标地址，其中，一个或者多个发送属性包括用于指示兼容载波聚合的发送属性和/或用于指示不兼容载波聚合的发送属性。
在一些可能的实施方式中，上述方法还包括：确定任一第一目标地址兼容载波聚合；在多个载波上同时发送一个或者多个第一业务的数据。
在一些可能的实施方式中，上述方法还包括：确定所有第一目标地址不兼容载波聚合；在单个载波上发送一个或者多个第一业务的数据。
在一些可能的实施方式中，上述方法还包括：确定所有第一目标地址兼容载波聚合；在多个载波上同时发送一个或者多个第一业务的数据。
在一些可能的实施方式中，上述方法还包括：确定任一第一目标地址不兼容载波聚合；在单个载波上发送一个或者多个第一业务的数据。
根据本公开的第二方面提供一种侧链路通信方法，该方法可以应用于侧链路通信系统中的接收设备侧。该方法可以包括：当第二目标地址关联的所有发送属性对应于兼容载波聚合时，确定第二目标地址兼容载波聚合；或，当第二目标地址关联的至少一个发送属性对应于不兼容载波聚合时，确定第二目标地址不兼容载波聚合；其中，第二目标地址为感兴趣的第二业务的目标地址，第二业务为广播业务或者组播业务。
在一些可能的实施方式中，发送属性用于指示广播业务或者组播业务是否兼容载波聚合。
在一些可能的实施方式中，发送属性按照业务类型粒度设置，或发送属性按照目标地址粒度设置。
在一些可能的实施方式中，响应于发送属性按照业务类型粒度设置，一个发送属性与一个业务类型关联，至少一个业务类型与一个目标地址关联。
在一些可能的实施方式中，第二目标地址关联的所有发送属性包括：第二目标地址关联的所有业务类型关联的发送属性。
在一些可能的实施方式中，响应于发送属性按照目标地址粒度设置，一个发送属性与一个目标地址关联。
在一些可能的实施方式中，一个或者多个发送属性关联于一个目标地址，其中，一个或者多个发送属性包括用于指示兼容载波聚合的发送属性和/或用于指示不兼容载波聚合的发送属性。
在一些可能的实施方式中，上述方法还包括：确定任一第二目标地址兼容载波聚合；在多个载波上同时接收一个或者多个第二业务的数据。
在一些可能的实施方式中，上述方法还包括：确定所有第二目标地址不兼容载波聚合；在单个载波上接收一个或者多个第二业务的数据。
在一些可能的实施方式中，上述方法还包括：确定所有第二目标地址兼容载波聚合；在多个载波上同时接收一个或者多个第二业务的数据。
在一些可能的实施方式中，上述方法还包括：确定任一第二目标地址不兼容载波聚合；在单个载波上接收一个或者多个第二业务的数据。
根据本公开的第三方面提供一种通信装置，该通信装置可以为侧链路通信系统中发送设备或者发送设备中的芯片或者片上系统，还可以为发送设备中用于实现上述各个实施例的方法的功能模块。该通信装置可以实现上述各实施例中发送设备所执行的功能，这些功能可以通过硬件执行相应的软件实现。这些硬件或软件包括一个或者多个上述功能相应的模块。该通信装置包括：处理模块，用于当第一目标地址关联的所有发送属性对应于兼容载波聚合时，确定第一目标地址兼容载波聚合；或，当第一目标地址关联的至少一个发送属性对应于不兼容载波聚合时，确定第一目标地址不兼容载波聚合；其中，第一目标地址为第一业务的目标地址，第一业务为广播业务或者组播业务。
在一些可能的实施方式中，发送属性用于指示广播业务或者组播业务是否兼容载波聚合。
在一些可能的实施方式中，发送属性按照业务类型粒度设置，或发送属性按照目标地址粒度设置。
在一些可能的实施方式中，响应于发送属性按照业务类型粒度设置，一个发送属性与一个业务类型关联，至少一个业务类型与一个目标地址关联。
在一些可能的实施方式中，第一目标地址关联的所有发送属性包括：第一目标地址关联的所有业务类型关联的发送属性。
在一些可能的实施方式中，响应于发送属性按照目标地址粒度设置，一个发送属性与一个目标地址关联。
在一些可能的实施方式中，一个或者多个发送属性关联于一个目标地址，其中，一个或者多个发送属性包括用于指示兼容载波聚合的发送属性和/或用于指示不兼容载波聚合的发送属性。
在一些可能的实施方式中，上述装置还包括：发送模块；处理模块，还用于确定任一第一目标地址兼容载波聚合；发送模块，用于在多个载波上同时发送一个或者多个第一业务的数据。
在一些可能的实施方式中，上述装置还包括：发送模块；处理模块，还用于确定所有第一目标地址不兼容载波聚合；发送模块，用于在单个载波上发送一个或者多个第一业务的数据。
在一些可能的实施方式中，上述装置还包括：发送模块；处理模块，还用于确定所有第一目标地址兼容载波聚合；发送模块，用于在多个载波上同时发送一个或者多个第一业务的数据。
在一些可能的实施方式中，上述装置还包括：发送模块；处理模块，还用于确定任一第一目标地址不兼容载波聚合；发送模块，用于在单个载波上发送一个或者多个第一业务的数据。
根据本公开的第四方面提供一种通信装置，该通信装置可以为侧链路通信系统中接收设备或者接收设备中的芯片或者片上系统，还可以为接收设备中用于实现上述各个实施例的方法的功能模块。该通信装置可以实现上述各实施例中接收设备所执行的功能，这些功能可以通过硬件执行相应的软件实现。这些硬件或软件包括一个或者多个上述功能相应的模块。该通信装置包括：处理模块，用于当第二目标地址关联的所有发送属性对应于兼容载波聚合时，确定第二目标地址兼容载波聚合；或，当第二目标地址关联的至少一个发送属性对应于不兼容载波聚合时，确定第二目标地址不兼容载波聚合；其中，第二目标地址为感兴趣的第二业务的目标地址，第二业务为广播业务或者组播业务。
在一些可能的实施方式中，发送属性用于指示广播业务或者组播业务是否兼容载波聚合。
在一些可能的实施方式中，发送属性按照业务类型粒度设置，或发送属性按照目标地址粒度设 置。
在一些可能的实施方式中，响应于发送属性按照业务类型粒度设置，一个发送属性与一个业务类型关联，至少一个业务类型与一个目标地址关联。
在一些可能的实施方式中，第二目标地址关联的所有发送属性包括：第二目标地址关联的所有业务类型关联的发送属性。
在一些可能的实施方式中，响应于发送属性按照目标地址粒度设置，一个发送属性与一个目标地址关联。
在一些可能的实施方式中，一个或者多个发送属性关联于一个目标地址，其中，一个或者多个发送属性包括用于指示兼容载波聚合的发送属性和/或用于指示不兼容载波聚合的发送属性。
在一些可能的实施方式中，上述装置还包括：接收模块；处理模块，还用于确定任一第二目标地址兼容载波聚合；接收模块，用于在多个载波上同时接收一个或者多个第二业务的数据。
在一些可能的实施方式中，上述装置还包括：接收模块；处理模块，还用于确定所有第二目标地址不兼容载波聚合；接收模块，用于在单个载波上接收一个或者多个第二业务的数据。
在一些可能的实施方式中，上述装置还包括：接收模块；处理模块，还用于确定所有第二目标地址兼容载波聚合；接收模块，用于在多个载波上同时接收一个或者多个第二业务的数据。
在一些可能的实施方式中，上述装置还包括：接收模块；处理模块，还用于确定任一第二目标地址不兼容载波聚合；接收模块，用于在单个载波上接收一个或者多个第二业务的数据。
根据本公开的第五方面提供一种通信设备，如发送设备，包括：天线；存储器；处理器，分别与天线及存储器连接，被配置为通执行存储在存储器上的计算机可执行指令，控制天线的收发，并能够实现如本公开第一方面及其可能的实施方式中任一项所述的方法。
根据本公开的第六方面提供一种通信设备，如接收设备，包括：天线；存储器；处理器，分别与天线及存储器连接，被配置为通执行存储在存储器上的计算机可执行指令，控制天线的收发，并能够实现如本公开第二方面及其可能的实施方式中任一项所述的方法。
根据本公开的第七方面提供一种计算机存储介质，计算机存储介质存储有计算机可执行指令，其中，计算机可执行指令被处理器执行后能够实现如本公开第一方面至第二方面及其可能的实施方式中任一项所述的方法。
根据本公开的第八方面提供一种计算机程序或计算机程序产品，当计算机程序产品在计算机上被执行时，使得计算机实现如本公开第一方面至第二方面及其可能的实施方式中任一项所述的方法。
在本公开中，侧链路终端设备根据关联的发送属性(Tx profile)的指示，确定第一业务的目标地址是否兼容载波聚合，也就是说，确定关联的接收设备是否支持载波聚合。如此，在侧链路载波聚合场景下，保证之前版本的终端设备(如Rel-16或Rel-17版本的通信协议中的终端设备)能够收到最新版本的终端设备(如Rel-18版本的通信协议中支持载波聚合的终端设备)发送的广播业务或组播业务，从而实现侧链路终端设备的后向兼容性，进而提升终端设备性能。
应当理解的是，本公开的第三方面至第七方面与本公开的第一方面至第二方面的技术方案一致，各方面及对应的可行实施方式所取得的有益效果相似，不再赘述。
附图说明
图1为本公开实施例中的通信系统的一种架构示意图；
图2为本公开实施例中的通信系统的另一种架构示意图；
图3为本公开实施例中的一种侧链路通信方法的实施流程示意图；
图4为本公开实施例中的一种侧链路通信方法的实施流程示意图；
图5为本公开实施例中的一种侧链路通信方法的实施流程示意图；
图6为本公开实施例中的一种侧链路通信方法的实施流程示意图；
图7为本公开实施例中的一种侧链路通信方法的实施流程示意图；
图8为本公开实施例中的一种侧链路通信方法的实施流程示意图；
图9为本公开实施例中的一种测量上报装置的结构示意图；
图10为本公开实施例中的一种通信设备的结构示意图；
图11为本公开实施例中的一种终端设备的结构示意图；
图12为本公开实施例中的一种网络设备的结构示意图。
具体实施方式
这里将详细地对示例性实施例进行说明，其示例表示在附图中。下面的描述涉及附图时，除非另有表示，不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本公开实施例相一致的所有实施方式。相反，它们仅是与如本公开实施例的一些方面相一致的装置和方法的例子。
在本公开实施例使用的术语是仅仅出于描述特定实施例的目的，而非旨在限制本公开实施例。在本公开实施例中所使用的单数形式的“一种”和“该”也旨在包括多数形式，除非上下文清楚地表示其他含义。还应当理解，本文中使用的术语“和/或”是指并包含一个或者多个相关联的列出项目的任何或所有可能组合。
应当理解，尽管在本公开实施例可能采用术语“第一”、“第二”、“第三”等来描述各种信息，但这些信息不应限于这些术语。这些术语仅用来将同一类型的信息彼此区分开。例如，在不脱离本公开实施例范围的情况下，“第一信息”也可以被称为“第二信息”，类似地，“第二信息”也可以被称为“第一信息”。取决于语境，如在此所使用的词语“如果”可以被解释成为“在……时”或“当……时”或“响应于确定”。
进一步地，在本公开实施例的描述中，“和/或”仅仅是一种描述关联对象的关联关系，表示可以存在三种关系。例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，在本公开实施例的描述中，“多个”可以指两个或多于两个。
本公开实施例提供的技术方案可以应用于通信设备间的无线通信。通信设备间的无线通信可以包括：网络设备和终端设备间的无线通信、网络设备和网络设备间的无线通信以及终端设备和终端设备间的无线通信。在本公开实施例中，术语“无线通信”还可以简称为“通信”，术语“通信”还可以描 述为“数据传输”、“信息传输”或“传输”。
本公开实施例列举了多个实施方式以对本公开实施例的技术方案进行清晰地说明。当然，本领域内技术人员可以理解，本公开实施例提供的多个实施例，可以被单独执行，也可以与本公开实施例中其他实施例的方法结合后一起被执行，还可以单独或结合后与其他相关技术中的一些方法一起被执行；本公开实施例并不对此作出限定。
随着无线通信技术的发展，为了支持终端设备与终端设备之间的直连通信，引入了侧链路(sidelink，SL)通信方式，终端设备与终端设备之间通过PC5接口进行通信。侧链路网络支持单播、组播以及广播等多种传输模式。
在一实施例中，侧链路通信有两种发送资源分配方式，一种是网络动态调度的方式(即mode 1)，另一种是终端设备在网络广播的资源池中自主选择的方式(即mode 2)。其中，在mode1下，网络根据终端设备的缓存数据上报，动态给终端设备分配SL传输资源，而在mode2下，终端设备自行在网络广播或者预配置的资源池中随机选择SL传输资源。这里，“预配置”可以是终端设备从核心网的网元处获取，也可以是预置在终端设备内的。
在实际应用中，终端设备具体使用哪种资源分配方式可以可以由网络侧通过高层信令(如无线资源控制(radio resource control，RRC)信令)配置的。发送设备在物理侧链路控制信道(physical sidelink control channel，PSCCH)上发送侧链路控制信息(sidelink control information，SCI)以及在物理侧链路共享信道(physical sidelink shared channel，PSSCH)上发送SCI，其中携带传输数据的资源位置以及源和目标标识等。对于混合自动重传请求(hybrid automatic repeat request，HARQ)使能(即HARQ-enable)的数据包，接收设备在物理侧链路反馈信道(physical sidelink feedback channel，PSFCH)上对PSSCH进行HARQ反馈。
在另一实施例中，为了满足单用户峰值速率和系统容量提升的要求，一种最直接的办法就是增加系统传输带宽。因此，在LTE-Advanced系统引入一项增加传输带宽的技术，也就是载波聚合(carrier aggregation，CA)技术。这里，CA技术可以将多个载波(component carrier，CC)聚合在一起，有效提高了上下行传输速率。
在基于长期演进(long term evolution，LTE)通信网络的侧链路通信系统中，已经支持侧链路载波聚合(carrier aggregation，CA)技术。终端设备由于发送接收能力限制，可能只能在某一个或者某几个载波上接收侧行链路业务。由于基于LTE的侧链路通信系统只支持广播业务，所以，针对终端设备受限的接收能力并没有引入任何载波选择/重选的增强方案。
那么，在新无线(NR)侧链路载波聚合场景中，之前版本的终端设备(如3GPP Release-16或Release-17版本的通信协议中的终端设备)可能会接收不到支持载波聚合的终端设备(如Rel-18版本的通信协议中的终端设备)发送的广播业务或组播业务，即存在侧链路终端设备后向不兼容的问题。
为了解决上述技术问题，本公开实施例提供一种侧链路通信方法，该通信方法可以应用于一通信系统，该通信系统可以为侧链路通信系统，侧链路通信系统可以适应于车联网(vehicle to everything，V2X)、智能网联汽车及自动驾驶汽车等领域。上述通信系统中可以包括至少一个通信设备。在一种场景下，图1为本公开实施例中的通信系统的一种架构示意图，参见图1，该通信系统10中可以包括： 网络设备11和终端设备12。在另一种场景下，图2为本公开实施例中的通信系统的另一种架构示意图，参见图2，该通信系统10还可以包括多个终端设备12。当然，在公开实施例中，通信系统包含的网元的类型、数量，以及网元之间的连接关系不限于此。
在本公开实施例中，终端设备与网络设备通信的同时，还可以与其他终端设备通信。网络设备可以对终端设备之间通信的侧链路进行资源的配置、调度、协调等，以辅助终端设备之间直接进行通信。终端设备也可以自行对于其他终端设备之间通信的侧链路进行资源的配置、调度、协调等，本公开实施例不做具体限定。
在一些可能的实施方式中，上述网络设备可以是接入网侧用于支持终端设备接入无线通信系统的设备，例如，可以是5G接入技术通信系统中的下一代基站(next generation NodeB，gNB)、发送接收点(transmission reception point，TRP)、中继节点(relay node)、接入点(access point，AP)、路边装置(road site unit，RSU)等。
上述终端设备可以是一种向用户提供语音或者数据连通性的设备，例如也可以称为用户设备(user equipment，UE)、移动台(mobile station)、用户单元(subscriber unit)、站点(STAtion)或者终端(terminal equipment，TE)等。通信设备可以为蜂窝电话(cellular phone)、个人数字助理(personal digital assistant，PDA)、无线调制解调器(modem)、手持V2P设备(handheld vehicle to perdestrian)、膝上型电脑(laptop computer)、无绳电话(cordless phone)、无线本地环路(wireless local loop，WLL)台或者平板电脑(pad)、中继节点、AP等。随着无线通信技术的发展，可以接入无线通信系统、可以与无线通信系统的网络侧进行通信，或者通过无线通信系统与其它设备进行通信的设备都可以是本申请实施例中的终端设备，譬如，智能交通中的终端设备、汽车或RSU、智能家居中的家用设备、智能电网中的电力抄表仪器、电压监测仪器、环境监测仪器、智能安全网络中的视频监控仪器、收款机等。通信设备可以是静态固定的，也可以是移动的。
进一步地，在侧链路传输场景中，上述通信设备(可以包括终端设备和/或网络设备)按照数据传输方向可以分为发送设备和接收设备。其中，发送设备(也可以称为发送端设备)可以包括发送端网络设备、发送端终端设备、发送端用户设备等；接收设备(也可以称为接收端设备)可以包括接收端网络设备、接收端终端设备、接收端用户设备等。
需要说明的是，上述发送设备(也可以称为发送端网络设备、发送端终端设备、发送端用户设备等)以及接收设备(也可以称为接收端网络设备、接收端终端设备、接收端用户设备等)是针对某一条侧链路连接(sidelink connection)而言的。例如，一个通信设备(或者网络设备、终端设备、用户设备等)对于侧链路连接A来说，可以为发送设备(或者发送端网络设备、发送端终端设备、发送端用户设备等)；而对于侧链路连接B来说，该通信设备(或者网络设备、终端设备、用户设备等)可以为接收设备接收端网络设备、接收端终端设备、接收端用户设备等)。
下面结合上述通信系统，对本公开实施例提供的侧链路通信方法进行说明。
首先，需要说明的是，在本公开实施例中，针对于广播业务或者组播业务(在下文中简述为“广播/组播业务”)，设置(也可以称为“定义”)关联的发送属性(Tx profile)。这里，“发送属性”也可以描述为“发送配置”、“发送配置文件”、“发送文件”等。
在一实施例中，引入Tx profile是为了确保兼容或者不兼容载波聚合功能的的终端设备之间的广播或者组播传输的兼容性。可以理解的，Tx profile用于指示广播/组播业务是否兼容载波聚合，即Tx profile用于指示广播业务或者组播业务兼容载波聚合或者不兼容载波聚合。示例性的，Tx profile可以指示一个通信标准的版本(如Rel-18)，也可以指示载波聚合是否使能(如载波聚合兼容(ca-compatible)、载波聚合不兼容(ca-incompatible))。
需要说明的是，上述“广播/组播业务是否兼容载波聚合”可以理解为：针对于某一广播/组播业务，是否可以同时使用多个载波上的侧链路资源传输该业务关联的目标地址的数据。这里，目标地址可以采用destination ID标识。
在一些可能的实施方式中，Tx profile可以按照业务类型粒度设置或者按照目标地址粒度设置。
在一实施例中，如果Tx profile按业务类型粒度设置，此时，一个Tx profile与一个业务类型关联，也就是说Tx profile与业务类型一一对应，不同的业务类型关联的Tx profile不同。并且，至少一个业务类型与一个目标地址关联，也就是说一个目标地址可以关联多个不同的业务类型，由此一个目标地址关联的Tx profile可能有一个或者多个。示例性的，第一目标地址对应的destination ID为A，第一目标地址关联的业务类型为类型A、类型B和类型C，类型A对应的Tx profile 1，类型B对应的Tx profile 2，类型C对应的Tx profile 3。那么，第一目标地址关联的Tx profile为Tx profile 1、Tx profile 2和Tx profile 3。
在另一实施例中，如果Tx profile按照目标地址粒度设置，此时，一个Tx profile与一个目标地址关联，也就是说，一个目标地址关联的Tx profile只有一个，并且需要高层(upper layer)实现保证一个目标地址关联的所有业务类型关联的Tx profile相同。示例性的，第一目标地址对应的destination ID为A，第一目标地址关联的Tx profile为Tx profile 1。
由上述可知，在本公开实施例中，一个或者多个Tx profile关联于一个目标地址，其中，一个或者多个Tx profile包括用于指示兼容载波聚合的Tx profile和/或用于指示不兼容载波聚合的Tx profile。也就是说，针对于一个目标地址，可以关联一个或者多个Tx profile，这其中包括对应于兼容载波聚合的Tx profile，也包括对应于不兼容载波聚合的Tx profile。当然，Tx profile与目标地址的关联关系还可以存在其他情况，本公开实施例对此不做具体限定。
在一些可能的实施方式中，目标地址关联的Tx profile由高层(如V2X层)提供给接入层(access stratum，AS)，并标识一个或者多个侧链特征组(sidelink feature group(s))。
在一实施例中，高层可以以Tx profile列表的形式向AS指示Tx profile。当然，高层还可以以链表、索引(index)等其他的形式向AS指示Tx profile，本公开实施例对此不做具体限定。
示例性的，如果Tx profile按业务类型粒度设置，高层可以以Tx profile列表的形式向AS指示Tx profile，该列表里中可以包括不同业务类型关联的Tx profile，或者在该列表中可以包括不同目标地址关联的业务类型以及该业务类型关联的Tx profile。
示例性的，如果Tx profile按照目标地址粒度设置，高层也可以以Tx profile列表的形式向AS指示Tx profile，该列表中可以包括不同目标地址关联的Tx profile。
在一些可能的实施方式中，上述Tx profile的设置可以理解为侧链路系统预配置的(或者通信协议 中规定的)。侧链路系统中的各个网元均按照上述Tx profile设置执行。
下面对本公开实施例提供的一种侧链路通信方法进行说明。
在一些可能的实施方式中，本公开实施例提供一种侧链路通信方法，该方法可以应用于侧链路通信系统中的发送设备侧。图3为本公开实施例中的一种侧链路通信方法的实施流程示意图，参见图3，针对于Tx profile按业务类型粒度设置，上述方法可以包括：
S301，发送设备确定第一业务的第一目标地址。
这里，第一业务可以为广播/组播业务。
可以理解的，在发送设备中，高层触发第一业务，高层确定第一业务关联的第一目标地址并指示AS，AS通过高层指示的第一业务的目标地址关联的一个或者多个Tx profile，确定第一目标地址关联的Tx profile。这一个或者多个Tx profile与多个业务类型对应。
在本公开实施例中，由于Tx profile是按照业务类型粒度设置的，那么，第一目标地址关联的一个或者多个Tx profile可以理解为第一目标地址关联的一个或者多个业务类型对应的Tx profile。不同Tx profile可以指示不同业务类型的业务是否兼容载波聚合。
接下来，在S301之后，发送设备可以执行S302或S303。
S302，当第一目标地址关联的所有Tx profile对应于兼容载波聚合时，发送设备确定第一目标地址兼容载波聚合。
可以理解的，AS可以根据高层的指示确定第一目标地址关联的Tx profile，进而确定每一个Tx profile是对应于兼容载波聚合还是对应于不兼容载波聚合。AS确定第一目标地址关联的所有任务类型关联的Tx profile对应于兼容载波聚合(也可以理解为第一目标地址关联的所有Tx profile指示兼容载波聚合)，此时，AS确定第一目标地址兼容载波聚合。此时，发送设备认为(assume)(也可以描述为假定、假设等)第一目标地址兼容载波聚合。
S303，当第一目标地址关联的至少一个Tx profile对应于不兼容载波聚合时，发送设备确定第一目标地址不兼容载波聚合。
可以理解的，AS确定第一目标地址关联的至少一个业务类型关联的Tx profile对应于不兼容载波聚合(也可以理解为第一目标地址关联的至少一个Tx profile指示不兼容载波聚合)，此时，AS确定第一目标地址不兼容载波聚合。此时，发送设备认为(也可以描述为假定、假设等)第一目标地址不兼容载波聚合。
需要说明的是，上述“第一目标地址关联的至少一个Tx profile对应于不兼容载波聚合”也可以理解为第一目标地址关联的Tx profile中任一Tx profile(即第一目标地址关联的任一Tx profile)对应于不兼容载波聚合，或者还可以理解为第一目标地址关联的任一Tx profile指示不兼容载波聚合。
示例性的，第一目标地址为destination A，第一目标地址关联的业务类型为类型A、类型B和类型C，类型A对应的Tx profile 1，类型B对应的Tx profile 2，类型C对应的Tx profile 3。那么，destination A关联的Tx profile为Tx profile 1、Tx profile 2和Tx profile 3。如果Tx profile 1指示类型A的广播/组播业务兼容载波聚合，Tx profile 2指示类型B的广播/组播业务兼容载波聚合，Tx profile 3指示类型C的广播/组播业务兼容载波聚合，AS可以确定destination A关联的所有Tx profile对应于兼 容载波聚合，此时，AS确定destination A兼容载波聚合。反之，如果Tx profile 1、Tx profile 2和Tx profile 3中的至少一个Tx profile指示广播/组播业务不兼容载波聚合，AS可以确定destination A关联的至少一个Tx profile对应于不兼容载波聚合，此时，AS确定destination A不兼容载波聚合。
在一些可能的实施方式中，发送设备可以触发一个或者多个广播/组播业务，即触发一个或者多个第一业务，那么，发送设备可以针对一个或者多个第一业务中的每一个第一业务分别执行上述S301至S303，由此确定出一个或者多个第一目标地址是否兼容载波聚合。发送设备在确定出一个或者多个第一目标地址是否兼容载波聚合之后，可以选择使能载波聚合还是去使能载波聚合，从而在多个载波上发送一个或者多个第一业务的数据还是在单个载波上发送一个或者多个第一业务的数据。
在一实施例中，图4为本公开实施例中的一种侧链路通信方法的实施流程示意图，参见图4，在S302或S303之后，发送设备可以执行S401至S402(如实线所示)或者S403至S404(如虚线所示)。
S401，发送设备确定所有第一目标地址兼容载波聚合。
S402，发送设备在多个载波上同时发送一个或者多个第一业务的数据。
可以理解的，在S401至S402中，AS确定一个或者多个第一目标地址中所有第一目标地址兼容载波聚合，此时，AS使能载波聚合，在多个载波上同时发送一个或者多个第一业务的数据。
S403，发送设备确定任一第一目标地址不兼容载波聚合。
需要说明的是，上述“任一第一目标地址不兼容载波聚合”可以理解为一个或者多个第一目标地址中至少一个第一目标地址不兼容载波聚合。
S404，发送设备在单个载波上发送一个或者多个第一业务的数据。
这里，单个载波可以为默认载波，如Rel-16或者Rel-17版本的通信协议中的侧行链路载波。
可以理解的，在S403至S404中，AS确定一个或者多个第一目标地址中任一第一目标地址不兼容载波聚合，此时，AS去使能载波聚合，在单个载波上发送一个或者多个第一业务的数据。
示例性的，多个第一业务的目标地址可以为destination A、destination B、destination C，针对于每一个目标地址，发送设备执行上述S301至304，分别确定destination A、destination B、destination C是否兼容载波聚合。如果确定出destination A兼容载波聚合、destination B兼容载波聚合和destination C兼容载波聚合，AS使能载波聚合，在多个载波上同时发送多个第一业务的数据。或者，如果确定出destination A、destination B和destination C中的任一目标地址不兼容载波聚合，AS去使能载波聚合，在单个载波上发送多个第一业务的数据。
在另一实施例中，图5为本公开实施例中的一种侧链路通信方法的实施流程示意图，参见图5，在S302或S303之后，发送设备可以执行S501至S502(如实线所示)或者S503至S504(如虚线所示)。
S501，发送设备确定任一第一目标地址兼容载波聚合。
需要说明的是，上述“任一第一目标地址兼容载波聚合”可以理解为一个或者多个第一目标地址中至少一个第一目标地址兼容载波聚合。
S502，发送设备在多个载波上同时发送一个或者多个第一业务的数据。
可以理解的，在S501至S502中，AS确定一个或者多个第一目标地址中任一第一目标地址兼容载波聚合，此时，AS使能载波聚合，在多个载波上同时发送一个或者多个第一业务的数据。
S503，发送设备确定所有第一目标地址不兼容载波聚合。
S504，发送设备在单个载波上发送一个或者多个第一业务的数据。
可以理解的，在S503至S504中，AS确定一个或者多个第一目标地址中所有第一目标地址不兼容载波聚合，此时，AS去使能载波聚合，在单个载波上发送一个或者多个第一业务的数据。
示例性的，多个第一业务的目标地址可以为destination A、destination B、destination C，针对于每一个目标地址，发送设备执行上述S301至304，分别确定destination A、destination B、destination C是否兼容载波聚合。如果确定出destination A、destination B和destination C中的任一目标地址兼容载波聚合，AS使能载波聚合，在多个载波上同时发送多个第一业务的数据。或者，如果确定出destination A不兼容载波聚合、destination B不兼容载波聚合和destination C不兼容载波聚合，AS去使能载波聚合，在单个载波上发送多个第一业务的数据。
在一些可能的实施方式中，图6为本公开实施例中的一种侧链路通信方法的实施流程示意图，参见图6，针对于Tx profile按目标地址粒度设置，上述方法可以包括：
S601，发送设备确定第一业务的第一目标地址。
这里，第一业务可以为广播/组播业务。
可以理解的，在发送设备中，高层触发第一业务，高层确定第一业务关联的第一目标地址并指示AS。AS通过高层指示的第一业务的目标地址关联的Tx profile，确定第一目标地址关联的Tx profile。一个第一目标地址与一个Tx profile关联。
接下来，在S601之后，发送设备可以执行S602或S603。
S603，当第一目标地址关联的Tx profile(即一个Tx profile)对应于兼容载波聚合时，发送设备确定第一目标地址兼容载波聚合。
可以理解的，AS可以根据高层的指示确定第一目标地址关联的一个Tx profile，进而确定该Tx profile是对应于兼容载波聚合还是对应于不兼容载波聚合。AS确定第一目标地址关联的Tx profile对应于兼容载波聚合(也可以理解为第一目标地址关联的Tx profile指示兼容载波聚合)，此时，AS确定第一目标地址兼容载波聚合。此时，发送设备(如AS)认为(assume)(也可以描述为假定、假设等)第一目标地址兼容载波聚合。
需要说明的是，上述“第一目标地址关联的Tx profile对应于兼容载波聚合”也可以理解为第一目标地址关联的唯一一个Tx profile对应于兼容载波聚合，或者第一目标地址关联的所有Tx profile对应于兼容载波聚合。
S603，当第一目标地址关联的Tx profile(即一个Tx profile)对应于不兼容载波聚合时，发送设备确定第一目标地址不兼容载波聚合。
可以理解的，AS确定第一目标地址关联的Tx profile对应于不兼容载波聚合(也可以理解为第一目标地址关联的Tx profile指示不兼容载波聚合)，此时，AS确定第一目标地址不兼容载波聚合。此时，发送设备(如AS)认为(也可以描述为假定、假设等)第一目标地址不兼容载波聚合。
需要说明的是，上述“第一目标地址关联的Tx profile对应于不兼容载波聚合”也可以理解为第一目标地址关联的唯一一个Tx profile对应于不兼容载波聚合，或者还可以理解为第一目标地址关联的一个Tx profile指示不兼容载波聚合。
示例性的，第一目标地址为destination A，第一目标地址关联的Tx profile为Tx profile 1。如果Tx profile 1指示广播/组播业务兼容载波聚合，AS可以确定destination A关联的所有Tx profile对应于兼容载波聚合，此时，AS确定destination A兼容载波聚合。反之，如果Tx profile 1指示广播/组播业务不兼容载波聚合，AS可以确定destination A关联的一个Tx profile对应于不兼容载波聚合，此时，AS确定destination A不兼容载波聚合。
在一些可能的实施方式中，发送设备还可以触发一个或者多个广播/组播业务，即触发一个或者多个第一业务，那么，发送设备可以针对一个或者多个第一业务中的每一个第一业务分别执行上述S601至S603，由此确定出一个或者多个第一目标地址是否兼容载波聚合。接下来，在S602或S603之后，发送设备还可以且不限于执行上述S401至S404或者S501至S504，在此不再赘述。
至此，便完成了发送设备侧的侧链路通信过程。
在一些可能的实施方式中，本公开实施例还提供一种侧链路通信方法，该方法可以应用于侧链路通信系统中的接收设备侧。图7为本公开实施例中的一种侧链路通信方法的实施流程示意图，参见图7，针对于Tx profile按业务类型粒度设置，上述方法可以包括：
S701，接收设备确定第二业务的第二目标地址。
这里，第二业务可以为接收设备感兴趣的广播/组播业务。
可以理解的，在接收设备中，高层在确定感兴趣的第二业务，并向AS指示第二业务的第二目标地址，AS通过高层指示的第二业务的目标地址关联的一个或者多个Tx profile，确定第二目标地址关联的一个或者多个Tx profile。这一个或者多个Tx profile与多个业务类型对应。
接下来，在S701之后，发送设备可以执行S702或S703。
S702，当第二目标地址关联的所有Tx profile对应于兼容载波聚合时，接收设备确定第二目标地址兼容载波聚合。
S703，当第二目标地址关联的至少一个Tx profile对应于不兼容载波聚合时，确定第二目标地址不兼容载波聚合。
需要说明的是，上述S701至S703的执行过程可以参考图3中S301至S303的具体描述，为了说明书简洁，在此不做赘述。
在一些可能的实施方式中，接收设备还可以对一个或者多个广播/组播业务感兴趣，即存在一个或者多个第二业务，那么，接收设备可以针对一个或者多个第二业务中的每一个第二业务分别执行上述S701至S703，由此确定出一个或者多个第二目标地址是否兼容载波聚合。接收设备在确定出一个或者多个第二目标地址是否兼容载波聚合之后，可以选择使能载波聚合还是去使能载波聚合，从而在多个载波上接收一个或者多个第二业务的数据还是在单个载波上接收一个或者多个第二业务的数据。
在一实施例中，图8为本公开实施例中的一种侧链路通信方法的实施流程示意图，参见图8，在S302或S303之后，发送设备可以执行S801至S802(如实线所示)或者S803至S804(如虚线所 示)。
S801，接收设备确定所有第二目标地址兼容载波聚合。
S802，接收设备在多个载波上同时接收一个或者多个第二业务的数据。
S803，接收设备确定任一第二目标地址不兼容载波聚合。
需要说明的是，上述“任一第二目标地址不兼容载波聚合”可以理解为一个或者多个第二目标地址中至少一个第二目标地址不兼容载波聚合。
S804，接收设备在单个载波上接收一个或者多个第二业务的数据。
这里，单个载波可以为默认载波，如Rel-16或者Rel-17版本的通信协议中的侧行链路载波。
在另一实施例中，在S302或S303之后，发送设备可以执行S805至S806(如实线所示)或者S807至S808(如虚线所示)。
S805，接收设备确定任一第二目标地址兼容载波聚合。
S806，接收设备在多个载波上同时接收一个或者多个第二业务的数据。
S807，接收设备确定所有第二目标地址不兼容载波聚合。
S808，接收设备确定在单个载波上接收一个或者多个第二业务的数据。
需要说明的是，上述S801至S808的执行过程可以参考图4中S401至S404以及图5中S501至S504的具体描述，为了说明书简洁，在此不做赘述。
至此，便完成了接收设备侧的侧链路通信过程。
在本公开实施例中，侧链路终端设备根据关联的Tx profile的指示，确定第一业务的目标地址是否兼容载波聚合，也就是说，确定关联的接收设备是否支持载波聚合。如此，在侧链路载波聚合场景下，保证之前版本的终端设备(如Rel-16或Rel-17版本的通信协议中的终端设备)能够收到最新版本的终端设备(如Rel-18版本的通信协议中支持载波聚合的终端设备)发送的广播业务或组播业务，从而实现侧链路终端设备的后向兼容性，进而提升终端设备性能。
基于相同的发明构思，本公开实施例提供一种侧链路通信装置，图9为本公开实施例中的一种通信装置的结构示意图，参见图9所示，该通信装置900可以包括：处理模块901以及传输模块902。
在一些可能的实施例中，该通信装置900可以为侧链路通信系统中发送设备或者发送设备中的芯片或者片上系统，还可以为发送设备中用于实现上述各个实施例的方法的功能模块。该通信装置可以实现上述各实施例中发送设备所执行的功能，这些功能可以通过硬件执行相应的软件实现。这些硬件或软件包括一个或者多个上述功能相应的模块。此时，参见图9中实线所示，传输模块902可以理解为发送模块902a。
相应的，处理模块901，用于当第一目标地址关联的所有发送属性(Tx profile)对应于兼容载波聚合时，确定第一目标地址兼容载波聚合；或，当第一目标地址关联的至少一个发送属性对应于不兼容载波聚合时，确定第一目标地址不兼容载波聚合；其中，第一目标地址为第一业务的目标地址，第一业务为广播业务或者组播业务。
在一些可能的实施方式中，发送属性用于指示广播业务或者组播业务兼容载波聚合或者不兼容载波聚合。
在一些可能的实施方式中，发送属性按照业务类型粒度设置，或发送属性按照目标地址粒度设置。
在一些可能的实施方式中，响应于发送属性按照业务类型粒度设置，一个发送属性与一个业务类型关联，至少一个业务类型与一个目标地址关联。
在一些可能的实施方式中，第一目标地址关联的所有发送属性包括：第一目标地址关联的所有业务类型关联的发送属性。
在一些可能的实施方式中，响应于发送属性按照目标地址粒度设置，一个发送属性与一个目标地址关联。
在一些可能的实施方式中，一个或者多个发送属性关联于一个目标地址，其中，一个或者多个发送属性包括用于指示兼容载波聚合的发送属性和/或用于指示不兼容载波聚合的发送属性。
在一些可能的实施方式中，处理模块901，还用于确定任一第一目标地址兼容载波聚合；发送模块902a，用于在多个载波上同时发送一个或者多个第一业务的数据。
在一些可能的实施方式中，处理模块901，还用于确定所有第一目标地址不兼容载波聚合；发送模块902a，用于在单个载波上发送一个或者多个第一业务的数据。
在一些可能的实施方式中，处理模块901，还用于确定所有第一目标地址兼容载波聚合；发送模块902a，用于在多个载波上同时发送一个或者多个第一业务的数据。
在一些可能的实施方式中，处理模块901，还用于确定任一第一目标地址不兼容载波聚合；发送模块902a，用于在单个载波上发送一个或者多个第一业务的数据。
在一些可能的实施方式中，上述通信装置可以为侧链路通信系统中接收设备或者接收设备中的芯片或者片上系统，还可以为接收设备中用于实现上述各个实施例的方法的功能模块。该通信装置可以实现上述各实施例中接收设备所执行的功能，这些功能可以通过硬件执行相应的软件实现。这些硬件或软件包括一个或者多个上述功能相应的模块。此时，参见图9中虚线所示，传输模块902可以理解为接收模块902b。
相应的，处理模块901，用于当第二目标地址关联的所有发送属性对应于兼容载波聚合时，确定第二目标地址兼容载波聚合；或，当第二目标地址关联的至少一个发送属性对应于不兼容载波聚合时，确定第二目标地址不兼容载波聚合；其中，第二目标地址为感兴趣的第二业务的目标地址，第二业务为广播业务或者组播业务。
在一些可能的实施方式中，发送属性用于指示广播业务或者组播业务兼容载波聚合或者不兼容载波聚合。
在一些可能的实施方式中，发送属性按照业务类型粒度设置，或发送属性按照目标地址粒度设置。
在一些可能的实施方式中，响应于发送属性按照业务类型粒度设置，一个发送属性与一个业务类型关联，至少一个业务类型与一个目标地址关联。
在一些可能的实施方式中，第二目标地址关联的所有发送属性包括：第二目标地址关联的所有业务类型关联的发送属性。
在一些可能的实施方式中，响应于发送属性按照目标地址粒度设置，一个发送属性与一个目标地址关联。
在一些可能的实施方式中，一个或者多个发送属性关联于一个目标地址，其中，一个或者多个发送属性包括用于指示兼容载波聚合的发送属性和/或用于指示不兼容载波聚合的发送属性。
在一些可能的实施方式中，处理模块901，还用于确定任一第二目标地址兼容载波聚合；接收模块902b，用于在多个载波上同时接收一个或者多个第二业务的数据。
在一些可能的实施方式中，处理模块901，还用于确定所有第二目标地址不兼容载波聚合；接收模块902b，用于在单个载波上接收一个或者多个第二业务的数据。
在一些可能的实施方式中，处理模块901，还用于确定所有第二目标地址兼容载波聚合；接收模块902b，用于在多个载波上同时接收一个或者多个第二业务的数据。
在一些可能的实施方式中，处理模块901，还用于确定任一第二目标地址不兼容载波聚合；接收模块902b，用于在单个载波上接收一个或者多个第二业务的数据。
需要说明的是，处理模块901和传输模块902的具体实现过程可参考图2至图8实施例中对发送设备和接收设备的详细描述，为了说明书的简洁，这里不再赘述。
本公开实施例中提到的接收模块902b可以为接收接口、接收电路或者接收器等，发送模块902a可以为发送接口、发送电路或者发送器等；处理模块901可以为一个或者多个处理器。
基于相同的发明构思，本公开实施例提供一种通信设备，该通信设备可以为上述一个或者多个实施例中所述的发送设备和/或接收设备。图10为本公开实施例中的一种通信设备的结构示意图，参见图10所示，通信设备100，采用了通用的计算机硬件，包括处理器101、存储器102、总线103、输入设备104和输出设备105。
在一些可能的实施方式中，存储器102可以包括以易失性和/或非易失性存储器形式的计算机存储媒体，如只读存储器和/或随机存取存储器。存储器102可以存储操作系统、应用程序、其他程序模块、可执行代码、程序数据、用户数据等。
输入设备104可以用于向通信设备输入命令和信息，输入设备104如键盘或指向设备，如鼠标、轨迹球、触摸板、麦克风、操纵杆、游戏垫、卫星电视天线、扫描仪或类似设备。这些输入设备可以通过总线103连接至处理器101。
输出设备105可以用于通信设备输出信息，除了监视器之外，输出设备105还可以为其他外围输出设各，如扬声器和/或打印设备，这些输出设备也可以通过总线103连接到处理器101。
通信设备可以通过天线106连接到网络中，例如连接到局域网(local area network，LAN)。在联网环境下，控制备中存储的计算机执行指令可以存储在远程存储设备中，而不限于在本地存储。
当通信设备中的处理器101执行存储器102中存储的可执行代码或应用程序时，通信设备以执行以上实施例中的终端设备侧或者网络设备侧的移动性管理配置方法，具体执行过程参见上述实施例，在此不再赘述。
此外，上述存储器102中存储有用于实现图9中的处理模块901和传输模块902的功能的计算机执行指令。图9中的处理模块901和传输模块902的功能/实现过程均可以通过图10中的处理器101 调用存储器102中存储的计算机执行指令来实现，具体实现过程和功能参考上述相关实施例。
基于相同的发明构思，本公开实施例提供一种终端设备，该终端设备与上述一个或者多个实施例中的如发送端终端设备、发送端用户设备、接收端终端设备、接收端用户设备等终端设备一致。可选的，终端设备可以为移动电话，计算机，数字广播终端设备，消息收发设备，游戏控制台，平板设备，医疗设备，健身设备，个人数字助理等。
图11为本公开实施例中的一种终端设备的结构示意图，参见图11，终端设备110可以包括以下一个或者多个组件：处理组件111、存储器112、电源组件113、多媒体组件114、音频组件115、输入/输出(I/O)的接口116、传感器组件117以及通信组件118。
处理组件111通常控制终端设备110的整体操作，诸如与显示，电话呼叫，数据通信，相机操作和记录操作相关的操作。处理组件111可以包括一个或者多个处理器1111来执行指令，以完成上述的方法的全部或部分步骤。此外，处理组件111可以包括一个或者多个模块，便于处理组件111和其他组件之间的交互。例如，处理组件111可以包括多媒体模块，以方便多媒体组件114和处理组件111之间的交互。
存储器112被配置为存储各种类型的数据以支持在终端设备110的操作。这些数据的示例包括用于在终端设备110上操作的任何应用程序或方法的指令，联系人数据，电话簿数据，消息，图片，视频等。存储器112可以由任何类型的易失性或非易失性存储设备或者它们的组合实现，如静态随机存取存储器(SRAM)，电可擦除可编程只读存储器(EEPROM)，可擦除可编程只读存储器(EPROM)，可编程只读存储器(PROM)，只读存储器(ROM)，磁存储器，快闪存储器，磁盘或光盘。
电源组件113为终端设备110的各种组件提供电力。电源组件113可以包括电源管理系统，一个或者多个电源，及其他与为终端设备110生成、管理和分配电力相关的组件。
多媒体组件114包括在终端设备110和用户之间的提供一个输出接口的屏幕。在一些实施例中，屏幕可以包括液晶显示器(LCD)和触摸面板(TP)。如果屏幕包括触摸面板，屏幕可以被实现为触摸屏，以接收来自用户的输入信号。触摸面板包括一个或者多个触摸传感器以感测触摸、滑动和触摸面板上的手势。触摸传感器可以不仅感测触摸或滑动动作的边界，而且还检测与触摸或滑动操作相关的持续时间和压力。在一些实施例中，多媒体组件114包括一个前置摄像头和/或后置摄像头。当终端设备110处于操作模式，如拍摄模式或视频模式时，前置摄像头和/或后置摄像头可以接收外部的多媒体数据。每个前置摄像头和后置摄像头可以是一个固定的光学透镜系统或具有焦距和光学变焦能力。
音频组件115被配置为输出和/或输入音频信号。例如，音频组件115包括一个麦克风(MIC)，当终端设备110处于操作模式，如呼叫模式、记录模式和语音识别模式时，麦克风被配置为接收外部音频信号。所接收的音频信号可以被进一步存储在存储器112或经由通信组件118发送。在一些实施例中，音频组件115还包括一个扬声器，用于输出音频信号。
I/O接口116为处理组件111和外围接口模块之间提供接口，上述外围接口模块可以是键盘，点击轮，按钮等。这些按钮可包括但不限于：主页按钮、音量按钮、启动按钮和锁定按钮。
传感器组件117包括一个或者多个传感器，用于为终端设备110提供各个方面的状态评估。例 如，传感器组件117可以监听到终端设备110的打开/关闭状态，组件的相对定位，例如组件为终端设备110的显示器和小键盘，传感器组件117还可以检测终端设备110或终端设备110一个组件的位置改变，用户与终端设备110接触的存在或不存在，终端设备110方位或加速/减速和终端设备110的温度变化。传感器组件117可以包括接近传感器，被配置用来在没有任何的物理接触时检测附近物体的存在。传感器组件117还可以包括光传感器，如CMOS或CCD图像传感器，用于在成像应用中使用。在一些实施例中，该传感器组件117还可以包括加速度传感器，陀螺仪传感器，磁传感器，压力传感器或温度传感器。
通信组件118被配置为便于终端设备110和其他设备之间有线或无线方式的通信。终端设备110可以接入采用通信标准的无线网络，如Wi-Fi、2G、3G、4G或5G，或它们的组合。在一个示例性实施例中，通信组件118经由广播信道接收来自外部广播管理系统的广播信号或广播相关信息。在一个示例性实施例中，通信组件118还包括近场通信(NFC)模块，以促进短程通信。例如，在NFC模块可采用射频识别(RFID)技术，红外数据协会(IrDA)技术，超宽带(UWB)技术，蓝牙(BT)技术和其他技术来实现。
在示例性实施例中，终端设备110可以被一个或者多个应用专用集成电路(ASIC)、数字信号处理器(DSP)、数字信号处理设备(DSPD)、可编程逻辑器件(PLD)、现场可编程门阵列(FPGA)、控制器、微控制器、微处理器或其他电子元件实现，用于执行上述方法。
基于相同的发明构思，本公开实施例提供一种网络设备，该网络设备与上述一个或者多个实施例中的如发送端网络设备、接收端网络设备等网络设备一致。
图12为本公开实施例中的一种网络设备的结构示意图，参见图12，网络设备120可以包括处理组件121，其进一步包括一个或者多个处理器，以及由存储器122所代表的存储器资源，用于存储可由处理组件121的执行的指令，例如应用程序。存储器122中存储的应用程序可以包括一个或一个以上的每一个对应于一组指令的模块。此外，处理组件121被配置为执行指令，以执行上述方法前述应用在所述网络设备的任一方法。
网络设备120还可以包括一个电源组件123被配置为执行网络设备120的电源管理，一个有线或无线网络接口124被配置为将网络设备120连接到网络，和一个输入输出(I/O)接口125。网络设备120可以操作采用存储在存储器122的操作系统，例如Windows Server TM，Mac OS XTM，UnixTM，LinuxTM，FreeBSDTM或类似。
基于相同的发明构思，如终端设备，包括：天线；存储器；处理器，分别与天线及存储器连接，被配置为通执行存储在存储器上的计算机可执行指令，控制天线的收发，并能够实现如上述一个或者多个实施例中发送设备侧的方法。
基于相同的发明构思，如网络设备，包括：天线；存储器；处理器，分别与天线及存储器连接，被配置为通执行存储在存储器上的计算机可执行指令，控制天线的收发，并能够实现如上述一个或者多个实施例中接收设备侧的方法。
基于相同的发明构思，本公开实施例还提供一种计算机可读存储介质，计算机可读存储介质中存储有指令；当指令在计算机上运行时，用于执行上述一个或者多个实施例中发送设备侧或者接收设备 侧的方法。
基于相同的发明构思，本公开实施例还提供一种计算机程序或计算机程序产品，当计算机程序产品在计算机上被执行时，使得计算机实现上述一个或者多个实施例中发送设备侧或者接收设备侧的方法。
本领域技术人员在考虑说明书及实践这里公开的发明后，将容易想到本公开的其它实施方案。本公开旨在涵盖本公开的任何变型、用途或者适应性变化，这些变型、用途或者适应性变化遵循本公开的一般性原理并包括本公开未公开的本技术领域中的公知常识或惯用技术手段。
应当理解的是，本公开并不局限于上面已经描述并在附图中示出的精确结构，并且可以在不脱离其范围进行各种修改和改变。

Claims (26)

  1. 一种侧链路通信方法，应用于发送设备，所述方法包括：
    当第一目标地址关联的所有发送属性对应于兼容载波聚合时，确定所述第一目标地址兼容载波聚合；
    当所述第一目标地址关联的至少一个发送属性对应于不兼容载波聚合时，确定所述第一目标地址不兼容载波聚合；
    其中，所述第一目标地址为第一业务的目标地址，所述第一业务为广播业务或者组播业务。
  2. 根据权利要求1所述的方法，其中，所述发送属性用于指示广播业务或者组播业务是否兼容载波聚合。
  3. 根据权利要求1或2所述的方法，其中，所述发送属性按照业务类型粒度设置，或所述发送属性按照目标地址粒度设置。
  4. 根据权利要求3所述的方法，其中，响应于所述发送属性按照业务类型粒度设置，一个发送属性与一个业务类型关联，至少一个业务类型与一个目标地址关联。
  5. 根据权利要求4所述的方法，其中，所述第一目标地址关联的所有发送属性包括：所述第一目标地址关联的所有业务类型关联的发送属性。
  6. 根据权利要求3所述的方法，其中，响应于所述发送属性按照目标地址粒度设置，一个发送属性与一个目标地址关联。
  7. 根据权利要求1所述的方法，其中，一个或者多个发送属性关联于一个目标地址，其中，所述一个或者多个发送属性包括用于指示兼容载波聚合的发送属性和/或用于指示不兼容载波聚合的发送属性。
  8. 根据权利要求1或2所述的方法，其中，所述方法还包括：
    确定任一所述第一目标地址兼容载波聚合；
    在多个载波上同时发送一个或者多个第一业务的数据。
  9. 根据权利要求8所述的方法，其中，所述方法还包括：
    确定所有所述第一目标地址不兼容载波聚合；
    在单个载波上发送一个或者多个第一业务的数据。
  10. 根据权利要求1或2所述的方法，其中，所述方法还包括：
    确定所有所述第一目标地址兼容载波聚合；
    在多个载波上同时发送一个或者多个第一业务的数据。
  11. 根据权利要求10所述的方法，其中，所述方法还包括：
    确定任一所述第一目标地址不兼容载波聚合；
    在单个载波上发送一个或者多个第一业务的数据。
  12. 一种侧链路通信方法，应用于接收设备，所述方法包括：
    当第二目标地址关联的所有发送属性对应于兼容载波聚合时，确定所述第二目标地址兼容载波聚合；
    当所述第二目标地址关联的至少一个发送属性对应于不兼容载波聚合时，确定所述第二目标地址不兼容载波聚合；
    其中，所述第二目标地址为感兴趣的第二业务的目标地址，所述第二业务为广播业务或者组播业务。
  13. 根据权利要求12所述的方法，其中，所述发送属性用于指示广播业务或者组播业务是否兼容载波聚合。
  14. 根据权利要求12或13所述的方法，其中，所述发送属性按照业务类型粒度设置，或所述发送属性按照目标地址粒度设置。
  15. 根据权利要求14所述的方法，其中，响应于所述发送属性按照业务类型粒度设置，一个发送属性与一个业务类型关联，至少一个业务类型与一个目标地址关联。
  16. 根据权利要求15所述的方法，其中，所述第二目标地址关联的所有发送属性包括：所述第二目标地址关联的所有业务类型关联的发送属性。
  17. 根据权利要求14所述的方法，其中，响应于所述发送属性按照目标地址粒度设置，一个发送属性与一个目标地址关联。
  18. 根据权利要求12所述的方法，其中，一个或者多个发送属性关联于一个目标地址，其中，所述一个或者多个发送属性包括用于指示兼容载波聚合的发送属性和/或用于指示不兼容载波聚合的发送属性。
  19. 根据权利要求12或13所述的方法，其中，所述方法还包括：
    确定任一所述第二目标地址兼容载波聚合；
    在多个载波上同时接收一个或者多个第二业务的数据。
  20. 根据权利要求19所述的方法，其中，所述方法还包括：
    确定所有所述第二目标地址不兼容载波聚合；
    在单个载波上接收一个或者多个第二业务的数据。
  21. 根据权利要求12或13所述的方法，其中，所述方法还包括：
    确定所有所述第二目标地址兼容载波聚合；
    在多个载波上同时接收一个或者多个第二业务的数据。
  22. 根据权利要求21所述的方法，其中，所述方法还包括：
    确定任一所述第二目标地址不兼容载波聚合；
    在单个载波上接收一个或者多个第二业务的数据。
  23. 一种通信装置，应用于发送设备，所述装置包括：
    处理模块，用于当第一目标地址关联的所有发送属性对应于兼容载波聚合时，确定所述第一目标地址兼容载波聚合；或，当所述第一目标地址关联的至少一个发送属性对应于不兼容载波聚合时，确定所述第一目标地址不兼容载波聚合；其中，所述第一目标地址为第一业务的目标地址，所述第一业务为广播业务或者组播业务。
  24. 一种侧链接收装置，应用于接收设备，所述装置包括：
    处理模块，用于当第二目标地址关联的所有发送属性对应于兼容载波聚合时，确定所述第二目标地址兼容载波聚合；或，当所述第二目标地址关联的至少一个发送属性对应于不兼容载波聚合时，确定所述第二目标地址不兼容载波聚合；其中，所述第二目标地址为感兴趣的第二业务的目标地址，所述第二业务为广播业务或者组播业务。
  25. 一种通信设备，其特征在于，包括：天线；存储器；处理器，分别与所述天线及存储器连接，被配置为通执行存储在所述存储器上的计算机可执行指令，控制所述天线的收发，并能够实现如权利要求1至22任一项所述的方法。
  26. 一种计算机存储介质，其特征在于，所述计算机可读存储介质存储有指令，当所述指令在计算机上运行时，用于执行如权利要求1至22任一项所述的方法。
PCT/CN2022/119434 2022-09-16 2022-09-16 一种侧链路通信方法、装置及通信设备 WO2024055317A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2022/119434 WO2024055317A1 (zh) 2022-09-16 2022-09-16 一种侧链路通信方法、装置及通信设备
CN202280003581.7A CN115669140A (zh) 2022-09-16 2022-09-16 一种侧链路通信方法、装置及通信设备

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/119434 WO2024055317A1 (zh) 2022-09-16 2022-09-16 一种侧链路通信方法、装置及通信设备

Publications (1)

Publication Number Publication Date
WO2024055317A1 true WO2024055317A1 (zh) 2024-03-21

Family

ID=85022523

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/119434 WO2024055317A1 (zh) 2022-09-16 2022-09-16 一种侧链路通信方法、装置及通信设备

Country Status (2)

Country Link
CN (1) CN115669140A (zh)
WO (1) WO2024055317A1 (zh)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110972116A (zh) * 2018-09-28 2020-04-07 华为技术有限公司 一种通信方法及设备
CN113039820A (zh) * 2018-11-20 2021-06-25 高通股份有限公司 用于5g新无线电(nr)的侧向链路传输简档管理
US20210211850A1 (en) * 2018-07-24 2021-07-08 Innovative Technology Lab Co., Ltd. Method and apparatus for performing wireless communication in wireless communication system supporting vehicle communication

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210211850A1 (en) * 2018-07-24 2021-07-08 Innovative Technology Lab Co., Ltd. Method and apparatus for performing wireless communication in wireless communication system supporting vehicle communication
CN110972116A (zh) * 2018-09-28 2020-04-07 华为技术有限公司 一种通信方法及设备
CN113039820A (zh) * 2018-11-20 2021-06-25 高通股份有限公司 用于5g新无线电(nr)的侧向链路传输简档管理

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
SHARP: "Summary of [POST114-e][704][V2X/SL] How to make sure Rel-16 UEs not supporting SL DRX are not involved in SL communication in DRX manner (Sharp)", 3GPP DRAFT; R2-2107303, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. electronic; 20210816 - 20210827, 6 August 2021 (2021-08-06), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP052034029 *

Also Published As

Publication number Publication date
CN115669140A (zh) 2023-01-31

Similar Documents

Publication Publication Date Title
WO2022141405A1 (zh) 资源集合配置方法、装置及存储介质
WO2022126345A1 (zh) Drx配置方法及装置、通信设备和存储介质
WO2022183456A1 (zh) 信息传输方法、装置、通信设备和存储介质
US20220394704A1 (en) Feedback method, feedback apparatus and storage medium
WO2021232439A1 (zh) 频率资源授权方法、装置及计算机可读存储介质
WO2020243886A1 (zh) 控制信道发送、接收方法、装置及存储介质
WO2023240573A1 (zh) 信道状态信息的处理方法、装置及通信设备
WO2023184455A1 (zh) 一种通信方法、通信装置及通信设备
US20220346083A1 (en) Methods and apparatuses for determining network allocation vector, and storage media
WO2020164052A1 (zh) 资源确定方法及装置
WO2024055317A1 (zh) 一种侧链路通信方法、装置及通信设备
WO2023123123A1 (zh) 一种频域资源确定方法、装置及存储介质
WO2023050350A1 (zh) Cfr的确定方法、装置、通信设备及存储介质
WO2022110057A1 (zh) 无线传输的方法、装置、通信设备及存储介质
WO2021077266A1 (zh) 网络接入方法、装置、通信设备及存储介质
WO2023184558A1 (zh) 一种确定功率等级的方法、装置信设备
WO2020206640A1 (zh) 资源指示方法及装置
WO2023226044A1 (zh) 一种移动性管理配置方法、移动性管理配置装置及通信设备
WO2023206504A1 (zh) 系统消息处理方法及装置、通信设备及存储介质
WO2024031704A1 (zh) 回传链路的波束指示方法、装置及存储介质
WO2023206549A1 (zh) 一种中继通信方法、通信装置及通信设备
WO2024031458A1 (zh) 资源配置方法、装置、存储介质以及终端
WO2022217428A1 (zh) 一种波束管理方法、波束管理装置及存储介质
WO2024055313A1 (zh) 一种目标终端确定方法、装置、通信设备及存储介质
WO2023035273A1 (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: 22958507

Country of ref document: EP

Kind code of ref document: A1