A sidelink communication method, apparatus, and communication device

Abstract

The present disclosure provides a sidelink communication method, a communication device and a communication apparatus. The method can include: determining that a first target address is compatible with carrier aggregation when all transmission attributes associated with the first target address correspond to compatible carrier aggregation; determining that the first target address is not compatible with carrier aggregation when at least one transmission attribute associated with the first target address corresponds to incompatible carrier aggregation; wherein the first target address is a target address of a first service, and the first service is a broadcast service or a groupcast service.

Description

Technical Field

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

[0002] With the development of wireless communication technology, sidelink (SL) communication was introduced to support direct communication between terminal devices. Terminal devices communicate with each other via the PC5 interface. Sidelink networks support multiple transmission modes, including unicast, multicast, and broadcast.

[0003] In vehicle-to-everything (V2X) networks based on Long Term Evolution (LTE) communication networks, sidelink carrier aggregation (CA) technology is already supported. Due to limitations in transmit and receive capabilities, terminal devices may only be able to receive sidelink services on one or a few carriers. Since LTE V2X only supports broadcast services, no carrier selection / reselection enhancement schemes have been introduced to address the limited receive capabilities of terminal devices.

[0004] Therefore, in the new radio (NR) sidelink carrier aggregation scenario, terminal devices of previous versions (such as those in Rel-16 or Rel-17 communication protocols) may not be able to receive broadcast or multicast services sent by terminal devices that support carrier aggregation (such as those in Rel-18 communication protocols), which means there is a backward incompatibility problem between sidelink terminal devices. Summary of the Invention

[0005] This disclosure provides a sidelink communication method, apparatus, and communication device to achieve backward compatibility of sidelink terminal devices, thereby improving the performance of terminal devices.

[0006] According to a first aspect of this disclosure, a sidelink communication method is provided, which can be applied to the transmitting device side of a sidelink communication system. The method may include: determining that the first target address is compatible with carrier aggregation when all transmission attributes associated with a first target address correspond to compatible carrier aggregation; or determining that the first target address is incompatible with carrier aggregation when at least one transmission attribute associated with the first target address corresponds to incompatible carrier aggregation; wherein the first target address is the target address of a first service, and the first service is a broadcast service or a multicast service.

[0007] In some possible implementations, the transmission attribute is used to indicate whether the broadcast or multicast service is compatible with carrier aggregation.

[0008] In some possible implementations, the sending attributes are set at the service type granularity or at the destination address granularity.

[0009] In some possible implementations, in response to the sending attribute being set at the service type granularity, a sending attribute is associated with a service type, and at least one service type is associated with a destination address.

[0010] In some possible implementations, all transmission attributes associated with the first destination address include: transmission attributes associated with all service types associated with the first destination address.

[0011] In some possible implementations, a send attribute is associated with a target address in response to the send attribute being set at the target address granularity.

[0012] In some possible implementations, one or more transmission attributes are associated with a target address, wherein the one or more transmission attributes include transmission attributes for indicating compatible carrier aggregation and / or transmission attributes for indicating incompatible carrier aggregation.

[0013] In some possible implementations, the method further includes: determining any first target address compatible carrier aggregation; and simultaneously transmitting data of one or more first services on multiple carriers.

[0014] In some possible implementations, the method further includes: determining that all first target addresses are incompatible with carrier aggregation; and transmitting data for one or more first services on a single carrier.

[0015] In some possible implementations, the above method further includes: determining all first target address compatible carrier aggregations; and simultaneously transmitting data of one or more first services on multiple carriers.

[0016] In some possible implementations, the method further includes: determining that any first target address is incompatible with carrier aggregation; and transmitting data for one or more first services on a single carrier.

[0017] According to a second aspect of this disclosure, a sidelink communication method is provided, which can be applied to the receiving device side of a sidelink 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 determining that the second target address is incompatible with carrier aggregation when at least one transmission attribute associated with the second target address corresponds to incompatible carrier aggregation; wherein the second target address is the target address of a second service of interest, and the second service is a broadcast service or a multicast service.

[0018] In some possible implementations, the transmission attribute is used to indicate whether the broadcast or multicast service is compatible with carrier aggregation.

[0019] In some possible implementations, the sending attributes are set at the service type granularity or at the destination address granularity.

[0020] In some possible implementations, in response to the sending attribute being set at the service type granularity, a sending attribute is associated with a service type, and at least one service type is associated with a destination address.

[0021] In some possible implementations, all transmission attributes associated with the second destination address include: transmission attributes associated with all service types associated with the second destination address.

[0022] In some possible implementations, a send attribute is associated with a target address in response to the send attribute being set at the target address granularity.

[0023] In some possible implementations, one or more transmission attributes are associated with a target address, wherein the one or more transmission attributes include transmission attributes for indicating compatible carrier aggregation and / or transmission attributes for indicating incompatible carrier aggregation.

[0024] In some possible implementations, the method further includes: determining any second target address compatible carrier aggregation; and simultaneously receiving data of one or more second services on multiple carriers.

[0025] In some possible implementations, the method further includes: determining that all second target addresses are incompatible with carrier aggregation; and receiving data for one or more second services on a single carrier.

[0026] In some possible implementations, the method further includes: determining all second target address compatible carrier aggregations; and simultaneously receiving data for one or more second services on multiple carriers.

[0027] In some possible implementations, the method further includes: determining that any second target address is incompatible with carrier aggregation; and receiving data for one or more second services on a single carrier.

[0028] According to a third aspect of this disclosure, a communication apparatus is provided. This communication apparatus can be a transmitting device in a sidelink communication system, a chip or system-on-a-chip in the transmitting device, or a functional module in the transmitting device for implementing the methods of the various embodiments described above. The communication apparatus can implement the functions performed by the transmitting device in the various embodiments described above, and these functions can be implemented by hardware executing corresponding software. This hardware or software includes one or more modules corresponding to the aforementioned functions. The communication apparatus 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, to determine that the first target address is incompatible with carrier aggregation when at least one transmission attribute associated with the first target address corresponds to incompatible carrier aggregation; wherein the first target address is the target address of a first service, and the first service is a broadcast service or a multicast service.

[0029] In some possible implementations, the transmission attribute is used to indicate whether the broadcast or multicast service is compatible with carrier aggregation.

[0030] In some possible implementations, the sending attributes are set at the service type granularity or at the destination address granularity.

[0031] In some possible implementations, in response to the sending attribute being set at the service type granularity, a sending attribute is associated with a service type, and at least one service type is associated with a destination address.

[0032] In some possible implementations, all transmission attributes associated with the first destination address include: transmission attributes associated with all service types associated with the first destination address.

[0033] In some possible implementations, a send attribute is associated with a target address in response to the send attribute being set at the target address granularity.

[0034] In some possible implementations, one or more transmission attributes are associated with a target address, wherein the one or more transmission attributes include transmission attributes for indicating compatible carrier aggregation and / or transmission attributes for indicating incompatible carrier aggregation.

[0035] In some possible implementations, the above apparatus further includes: a transmitting module; a processing module, further configured to determine any first target address compatible carrier aggregation; and a transmitting module, configured to simultaneously transmit data of one or more first services on multiple carriers.

[0036] In some possible implementations, the above apparatus further includes: a transmitting module; a processing module, further configured to determine that all first target addresses are incompatible with carrier aggregation; and a transmitting module, configured to transmit data of one or more first services on a single carrier.

[0037] In some possible implementations, the above apparatus further includes: a transmitting module; a processing module, further configured to determine all first target address compatible carrier aggregations; and a transmitting module, configured to simultaneously transmit data of one or more first services on multiple carriers.

[0038] In some possible implementations, the above apparatus further includes: a transmitting module; a processing module, further configured to determine that any first target address is incompatible with carrier aggregation; and a transmitting module, configured to transmit data of one or more first services on a single carrier.

[0039] According to a fourth aspect of this disclosure, a communication apparatus is provided. This communication apparatus can be a receiving device in a sidelink communication system, or a chip or system-on-a-chip within the receiving device. It can also be a functional module in the receiving device for implementing the methods of the various embodiments described above. The communication apparatus can implement the functions performed by the receiving device in the various embodiments described above, and these functions can be implemented by hardware executing corresponding software. This hardware or software includes one or more modules corresponding to the aforementioned functions. The communication apparatus includes: a processing module, configured to determine that a second target address is compatible with carrier aggregation when all transmission attributes associated with a second target address correspond to compatible carrier aggregation; or, to determine that a second target address is incompatible with carrier aggregation when at least one transmission attribute associated with a second target address corresponds to incompatible carrier aggregation; wherein the second target address is the target address of a second service of interest, and the second service is a broadcast service or a multicast service.

[0040] In some possible implementations, the transmission attribute is used to indicate whether the broadcast or multicast service is compatible with carrier aggregation.

[0041] In some possible implementations, the sending attributes are set at the service type granularity or at the destination address granularity.

[0042] In some possible implementations, in response to the sending attribute being set at the service type granularity, a sending attribute is associated with a service type, and at least one service type is associated with a destination address.

[0043] In some possible implementations, all transmission attributes associated with the second destination address include: transmission attributes associated with all service types associated with the second destination address.

[0044] In some possible implementations, a send attribute is associated with a target address in response to the send attribute being set at the target address granularity.

[0045] In some possible implementations, one or more transmission attributes are associated with a target address, wherein the one or more transmission attributes include transmission attributes for indicating compatible carrier aggregation and / or transmission attributes for indicating incompatible carrier aggregation.

[0046] In some possible implementations, the above apparatus further includes: a receiving module; a processing module, further configured to determine any second target address compatible carrier aggregation; and a receiving module configured to simultaneously receive data of one or more second services on multiple carriers.

[0047] In some possible implementations, the above apparatus 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 data of one or more second services on a single carrier.

[0048] In some possible implementations, the above apparatus further includes: a receiving module; a processing module, further configured to determine all second target address compatible carrier aggregations; and a receiving module configured to simultaneously receive data of one or more second services on multiple carriers.

[0049] In some possible implementations, the above apparatus 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 data of one or more second services on a single carrier.

[0050] According to a fifth aspect of this disclosure, a communication device, such as a transmitting device, is provided, comprising: an antenna; a memory; and a processor, respectively connected to the antenna and the memory, configured to execute computer-executable instructions stored in the memory, control the transmission and reception of the antenna, and be able to implement the method as described in any one of the first aspects of this disclosure and its possible embodiments.

[0051] According to a sixth aspect of this disclosure, a communication device, such as a receiving device, is provided, comprising: an antenna; a memory; and a processor, respectively connected to the antenna and the memory, configured to execute computer-executable instructions stored in the memory, control the transmission and reception of the antenna, and be able to implement the method as described in any one of the second aspects of this disclosure and its possible embodiments.

[0052] According to a seventh aspect of this disclosure, a computer storage medium is provided that stores computer-executable instructions, wherein the computer-executable instructions, when executed by a processor, can implement the method as described in any one of the first to second aspects of this disclosure and their possible embodiments.

[0053] According to the eighth aspect of this disclosure, a computer program or computer program product is provided that, when executed on a computer, causes the computer to perform the method as described in any one of the first to second aspects of this disclosure and their possible embodiments.

[0054] In this disclosure, the sidelink terminal device determines whether the target address of the first service is compatible with carrier aggregation based on the indication of the associated transmission attribute (Tx profile), that is, whether the associated receiving device supports carrier aggregation. Thus, in a sidelink carrier aggregation scenario, it ensures that terminal devices of previous versions (such as those in Rel-16 or Rel-17 communication protocols) can receive broadcast or multicast services from terminal devices of the latest versions (such as those supporting carrier aggregation in Rel-18 communication protocols), thereby achieving backward compatibility of the sidelink terminal device and improving its performance.

[0055] It should be understood that the third to eighth aspects of this disclosure are consistent with the technical solutions of the first to second aspects of this disclosure, and the beneficial effects achieved by each aspect and the corresponding feasible implementation are similar, so they will not be repeated here. Attached Figure Description

[0056] Figure 1 This is a schematic diagram of the architecture of a communication system in an embodiment of this disclosure;

[0057] Figure 2 This is a schematic diagram of another architecture of the communication system in an embodiment of this disclosure;

[0058] Figure 3 This is a schematic diagram illustrating the implementation process of a side-link communication method in an embodiment of this disclosure;

[0059] Figure 4 This is a schematic diagram illustrating the implementation process of a side-link communication method in an embodiment of this disclosure;

[0060] Figure 5 This is a schematic diagram illustrating the implementation process of a side-link communication method in an embodiment of this disclosure;

[0061] Figure 6 This is a schematic diagram illustrating the implementation process of a side-link communication method in an embodiment of this disclosure;

[0062] Figure 7 This is a schematic diagram illustrating the implementation process of a side-link communication method in an embodiment of this disclosure;

[0063] Figure 8 This is a schematic diagram illustrating the implementation process of a side-link communication method in an embodiment of this disclosure;

[0064] Figure 9This is a schematic diagram of the structure of a measurement reporting device according to an embodiment of this disclosure;

[0065] Figure 10 This is a schematic diagram of the structure of a communication device according to an embodiment of the present disclosure;

[0066] Figure 11 This is a schematic diagram of the structure of a terminal device according to an embodiment of the present disclosure;

[0067] Figure 12 This is a schematic diagram of the structure of a network device according to an embodiment of this disclosure. Detailed Implementation

[0068] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numerals in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with those of this disclosure. Rather, they are merely examples of apparatuses and methods consistent with some aspects of embodiments of this disclosure.

[0069] The terminology used in this disclosure is for the purpose of describing particular embodiments only and is not intended to be limiting of the embodiments of this disclosure. The singular forms “a” and “the” as used in this disclosure are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used herein refers to and includes any or all possible combinations of one or more of the associated listed items.

[0070] It should be understood that although the terms "first," "second," "third," etc., may be used to describe various information in embodiments of this disclosure, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, without departing from the scope of embodiments of this disclosure, "first information" may also be referred to as "second information," and similarly, "second information" may also be referred to as "first information." Depending on the context, the word "if," as used herein, may be interpreted as "when," "in response to a determination," or "when," or "in the event of a determination."

[0071] Furthermore, in the description of the embodiments of this disclosure, "and / or" is merely a way of describing the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Additionally, in the description of the embodiments of this disclosure, "multiple" can refer to two or more.

[0072] The technical solutions provided in this disclosure can be applied to wireless communication between communication devices. Wireless communication between communication devices can include: wireless communication between network devices and terminal devices, wireless communication between network devices, and wireless communication between terminal devices. In this disclosure, the term "wireless communication" can also be simply referred to as "communication," and the term "communication" can also be described as "data transmission," "information transmission," or "transmission."

[0073] This disclosure provides multiple embodiments to clearly illustrate the technical solutions of the embodiments of this disclosure. Of course, those skilled in the art will understand that the multiple embodiments provided in this disclosure can be executed individually, or in combination with the methods of other embodiments in this disclosure, or individually or in combination with some methods in other related technologies; this disclosure does not limit these aspects.

[0074] With the development of wireless communication technology, sidelink (SL) communication was introduced to support direct communication between terminal devices. Terminal devices communicate with each other via the PC5 interface. Sidelink networks support multiple transmission modes, including unicast, multicast, and broadcast.

[0075] In one embodiment, sidelink communication has two resource allocation methods: one is dynamic network scheduling (mode 1), and the other is autonomous selection by the terminal device from the network broadcast resource pool (mode 2). In mode 1, the network dynamically allocates SL transmission resources to the terminal device based on the cached data reported by the terminal device. In mode 2, the terminal device randomly selects SL transmission resources from the network broadcast or a pre-configured resource pool. Here, "pre-configured" can refer to resources obtained by the terminal device from network elements in the core network or resources pre-configured within the terminal device.

[0076] In practical applications, the specific resource allocation method used by the terminal device can be configured by the network side through higher-layer signaling (such as radio resource control (RRC) signaling). The transmitting device sends sidelink control information (SCI) on the physical sidelink control channel (PSCCH) and on the physical sidelink shared channel (PSSCH), which carries the resource location of the transmitted data, as well as source and destination identifiers. For packets with hybrid automatic repeat request (HARQ) enabled, the receiving device provides HARQ feedback to the PSSCH on the physical sidelink feedback channel (PSFCH).

[0077] In another embodiment, to meet the requirements of increased single-user peak data rate and system capacity, one of the most direct methods is to increase the system transmission bandwidth. Therefore, a technology to increase transmission bandwidth, carrier aggregation (CA), is introduced into the LTE-Advanced system. Here, CA technology can aggregate multiple component carriers (CCs) together, effectively improving uplink and downlink transmission rates.

[0078] In sidelink communication systems based on Long Term Evolution (LTE) networks, sidelink carrier aggregation (CA) technology is already supported. Due to limitations in transmit and receive capabilities, terminal devices may only be able to receive sidelink services on one or a few carriers. Since LTE-based sidelink communication systems only support broadcast services, no carrier selection / reselection enhancement schemes have been introduced to address the limited receive capabilities of terminal devices.

[0079] Therefore, in the new radio (NR) sidelink carrier aggregation scenario, terminal devices of previous versions (such as those in the 3GP Release-16 or Release-17 communication protocol) may not be able to receive broadcast or multicast services sent by terminal devices that support carrier aggregation (such as those in the Rel-18 communication protocol), which means there is a backward incompatibility problem between sidelink terminal devices.

[0080] To address the aforementioned technical problems, this disclosure provides a sidelink communication method. This method can be applied to a communication system, which can be a sidelink communication system adapted to fields such as vehicle-to-everything (V2X), intelligent connected vehicles, and autonomous vehicles. The aforementioned communication system may include at least one communication device. In one scenario, Figure 1 This is a schematic diagram of an architecture of the communication system in an embodiment of this disclosure. See also... Figure 1 The communication system 10 may include a network device 11 and a terminal device 12. In another scenario, Figure 2 This is a schematic diagram of another architecture of the communication system in this disclosure embodiment, see [link to diagram]. Figure 2 The communication system 10 may also include multiple terminal devices 12. Of course, in the disclosed embodiments, the types and number of network elements included in the communication system, as well as the connection relationships between the network elements, are not limited to this.

[0081] In this embodiment, the terminal device can communicate with the network device while also communicating with other terminal devices. The network device can configure, schedule, and coordinate resources for the side links between terminal devices to facilitate direct communication between them. The terminal device can also configure, schedule, and coordinate resources for the side links between other terminal devices on its own; this embodiment does not impose specific limitations on these aspects.

[0082] In some possible implementations, the aforementioned network equipment may be access network-side equipment used to support terminal equipment access to the wireless communication system. For example, it may be a next-generation NodeB (gNB), transmission reception point (TRP), relay node, access point (AP), roadside unit (RSU), etc., in a 5G access technology communication system.

[0083] The aforementioned terminal equipment can be a device that provides voice or data connectivity to users, and may also be referred to as user equipment (UE), mobile station, subscriber unit, station, or terminal equipment (TE). Communication equipment can be a cellular phone, personal digital assistant (PDA), modem, handheld vehicle-to-perdestination (V2P) device, laptop computer, cordless phone, wireless local loop (WLL) station, tablet computer, relay node, access point (AP), etc. With the development of wireless communication technology, any device that can access a wireless communication system, communicate with the network side of a wireless communication system, or communicate with other devices through a wireless communication system can be considered a terminal device in this application embodiment. Examples include terminal equipment in intelligent transportation systems, automobiles or RSUs, home appliances in smart homes, electricity meter reading instruments, voltage monitoring instruments, environmental monitoring instruments in smart grids, video surveillance instruments in smart security networks, and cash registers. Communication equipment can be statically fixed or mobile.

[0084] Furthermore, in sidelink transmission scenarios, the aforementioned communication devices (which may include terminal devices and / or network devices) can be categorized into transmitting devices and receiving devices according to the data transmission direction. The transmitting device (also referred to as the sending end device) may include sending end network devices, sending end terminal devices, sending end user equipment, etc.; the receiving device (also referred to as the receiving end device) may include receiving end network devices, receiving end terminal devices, receiving end user equipment, etc.

[0085] It should be noted that the aforementioned transmitting devices (also referred to as transmitting network devices, transmitting terminal devices, transmitting user equipment, etc.) and receiving devices (also referred to as receiving network devices, receiving terminal devices, receiving user equipment, etc.) are specific to a particular sidelink connection. For example, a communication device (or network device, terminal device, user equipment, etc.) can be a transmitting device (or transmitting network device, transmitting terminal device, transmitting user equipment, etc.) for sidelink connection A; while for sidelink connection B, the communication device (or network device, terminal device, user equipment, etc.) can be a receiving device (receiving network device, receiving terminal device, receiving user equipment, etc.).

[0086] The side-link communication method provided in the embodiments of this disclosure will be described below in conjunction with the above-described communication system.

[0087] First, it should be noted that in this embodiment of the disclosure, for broadcast services or multicast services (hereinafter referred to as "broadcast / multicast services"), associated transmission attributes (Tx profiles) are set (or "defined"). Here, "transmission attributes" can also be described as "transmission configuration", "transmission configuration file", "transmission file", etc.

[0088] In one embodiment, a Tx profile is introduced to ensure compatibility of broadcast or multicast transmissions between terminal devices that are compatible with or incompatible with carrier aggregation. It is understood that the Tx profile indicates whether a broadcast / multicast service is compatible with carrier aggregation; that is, it indicates whether a broadcast or multicast service is compatible with or incompatible with carrier aggregation. For example, the Tx profile may indicate a version of a communication standard (such as Rel-18) or whether carrier aggregation is enabled (e.g., carrier aggregation compatible (ca-compatible) or carrier aggregation incompatible (ca-incompatible)).

[0089] It should be noted that the above question of "whether broadcast / multicast services are compatible with carrier aggregation" can be understood as: for a certain broadcast / multicast service, whether sidelink resources on multiple carriers can be used simultaneously to transmit data of the target address associated with the service. Here, the target address can be identified using a destination ID.

[0090] In some possible implementations, the Tx profile can be set at the service type granularity or at the target address granularity.

[0091] In one embodiment, if Tx profiles are set at the service type granularity, then one Tx profile is associated with one service type, meaning there is a one-to-one correspondence between Tx profiles and service types, and different service types are associated with different Tx profiles. Furthermore, at least one service type is associated with one target address, meaning one target address can be associated with multiple different service types. Therefore, a target address may be associated with one or more Tx profiles. For example, if the destination ID corresponding to the first target address is A, and the service types associated with the first target address are type A, type B, and type C, with Tx profile 1 corresponding to type A, Tx profile 2 corresponding to type B, and Tx profile 3 corresponding to type C, then the Tx profiles associated with the first target address are Tx profile 1, Tx profile 2, and Tx profile 3.

[0092] In another embodiment, if the Tx profile is set according to the target address granularity, then one Tx profile is associated with one target address. That is, there is only one Tx profile associated with a target address, and the upper layer needs to ensure that all service types associated with a target address have the same Tx profile. For example, the destination ID corresponding to the first target address is A, and the Tx profile associated with the first target address is Txprofile 1.

[0093] As described above, in this embodiment of the disclosure, one or more Tx profiles are associated with a target address. These one or more Tx profiles include Tx profiles indicating compatible carrier aggregation and / or Tx profiles indicating incompatible carrier aggregation. That is, for a single target address, one or more Tx profiles can be associated, including Tx profiles corresponding to compatible carrier aggregation and Tx profiles corresponding to incompatible carrier aggregation. Of course, the association between Tx profiles and target addresses can also exist in other ways, and this embodiment of the disclosure does not specifically limit this.

[0094] In some possible implementations, 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 groups(s).

[0095] In one embodiment, the higher layer can indicate the Tx profile to the AS in the form of a list of Tx profiles. Of course, the higher layer can also indicate the Tx profile to the AS in other forms such as linked lists or indexes, and this disclosure does not specifically limit this method.

[0096] For example, if Tx profiles are set at the service type granularity, higher layers can indicate Tx profiles to the AS in the form of a list of Tx profiles. This list can include Tx profiles associated with different service types, or it can include service types associated with different target addresses and the Tx profiles associated with those service types.

[0097] For example, if the Tx profile is set according to the target address granularity, the higher layer can also indicate the Tx profile to the AS in the form of a Tx profile list, which can include Tx profiles associated with different target addresses.

[0098] In some possible implementations, the Tx profile settings described above can be understood as pre-configured by the sidelink system (or specified in the communication protocol). Each network element in the sidelink system executes according to the Tx profile settings described above.

[0099] The following describes a sidelink communication method provided by an embodiment of this disclosure.

[0100] In some possible implementations, embodiments of this disclosure provide a sidelink communication method that can be applied to the transmitting device side of a sidelink communication system. Figure 3 This is a schematic diagram illustrating the implementation process of a sidelink communication method according to an embodiment of this disclosure. See also... Figure 3 For setting Tx profiles at the business type granularity, the above methods can include:

[0101] S301, The transmitting device determines the first target address of the first service.

[0102] Here, the first service can be broadcast / multicast service.

[0103] Understandably, in the transmitting device, the higher layer triggers the first service, determines the first destination address associated with the first service, and instructs the AS. The AS then determines the Tx profile associated with the first destination address based on one or more Tx profiles associated with the destination address indicated by the higher layer. These one or more Tx profiles correspond to multiple service types.

[0104] In this embodiment of the disclosure, since the Tx profile is set at the service type granularity, one or more Tx profiles associated with the first target address can be understood as Tx profiles corresponding to one or more service types associated with the first target address. Different Tx profiles can indicate whether services of different service types are compatible with carrier aggregation.

[0105] Next, after S301, the transmitting device can execute S302 or S303.

[0106] S302, when all Tx profiles associated with the first target address correspond to compatible carrier aggregation, the transmitting device determines the first target address compatible carrier aggregation.

[0107] Understandably, the AS can determine the Tx profile associated with the first target address based on instructions from higher layers, and then determine whether each Tx profile corresponds to compatible carrier aggregation or incompatible carrier aggregation. If the AS determines that all Tx profiles associated with the first target address correspond to compatible carrier aggregation (or, in other words, all Tx profiles associated with the first target address indicate compatible carrier aggregation), then the AS determines that the first target address is compatible with carrier aggregation. At this point, the transmitting device assumes (or assumes, presupposes, etc.) that the first target address is compatible with carrier aggregation.

[0108] S303, when at least one Tx profile associated with the first target address corresponds to incompatible carrier aggregation, the transmitting device determines that the first target address is incompatible with carrier aggregation.

[0109] Understandably, if the AS determines that at least one service type associated with the first destination address corresponds to incompatible carrier aggregation (or, in other words, at least one Tx profile associated with the first destination address indicates incompatible carrier aggregation), then the AS determines that the first destination address is incompatible with carrier aggregation. In this case, the transmitting device assumes (or may be described as assuming, hypothesizing, etc.) that the first destination address is incompatible with carrier aggregation.

[0110] It should be noted that the above statement "at least one Tx profile associated with the first target address corresponds to incompatible carrier aggregation" can also be understood as any Tx profile associated with the first target address (i.e., any Tx profile associated with the first target address) corresponds to incompatible carrier aggregation, or it can also be understood as any Tx profile associated with the first target address indicating incompatible carrier aggregation.

[0111] For example, let the first destination address be destination A, and the service types associated with the first destination address be type A, type B, and type C. Type A corresponds to Tx profile 1, type B to Tx profile 2, and type C to Tx profile 3. Then, 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, the AS can determine that all Tx profiles associated with destination A correspond to compatible carrier aggregation. In this case, the AS determines that destination A is compatible with carrier aggregation. Conversely, if at least one of Tx profiles 1, 2, and 3 indicates that the broadcast / multicast service is incompatible with carrier aggregation, the AS can determine that at least one Tx profile associated with destination A corresponds to incompatible carrier aggregation. In this case, the AS determines that destination A is incompatible with carrier aggregation.

[0112] In some possible implementations, the transmitting device can trigger one or more broadcast / multicast services, i.e., trigger one or more first services. Then, the transmitting device can execute S301 to S303 as described above for each of the one or more first services, 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 transmitting device can choose to enable or disable carrier aggregation, thereby transmitting the data of one or more first services on multiple carriers or on a single carrier.

[0113] In one embodiment, Figure 4 This is a schematic diagram illustrating the implementation process of a sidelink communication method according to an embodiment of this disclosure. See also... Figure 4 After S302 or S303, the transmitting device may execute S401 to S402 (as shown by solid lines) or S403 to S404 (as shown by dashed lines).

[0114] S401, The transmitting device determines that all first target addresses are compatible with carrier aggregation.

[0115] S402, The transmitting device simultaneously transmits one or more first service data on multiple carriers.

[0116] Understandably, in S401 to S402, the AS determines that all first target addresses among one or more first target addresses are compatible with carrier aggregation. At this time, the AS enables carrier aggregation and transmits data of one or more first services simultaneously on multiple carriers.

[0117] S403, The transmitting device determines that any of the first target addresses is incompatible with carrier aggregation.

[0118] It should be noted that the above "any first target address is incompatible with carrier aggregation" can be understood as at least one of one or more first target addresses being incompatible with carrier aggregation.

[0119] S404, The transmitting device transmits one or more first service data on a single carrier.

[0120] Here, a single carrier can be a default carrier, such as the sidelink carrier in the Rel-16 or Rel-17 version of the communication protocol.

[0121] Understandably, in S403 to S404, if the AS determines that any one of the first target addresses is incompatible with carrier aggregation, the AS will disable carrier aggregation and transmit one or more first service data on a single carrier.

[0122] For example, the target addresses of multiple first services can be destination A, destination B, and destination C. For each target address, the transmitting device executes S301 to S303 as described above to determine whether destination A, destination B, and destination C are compatible with carrier aggregation. If it is determined that destination A, destination B, and destination C are compatible with carrier aggregation, the AS enables carrier aggregation, and transmits the data of multiple first services simultaneously on multiple carriers. Alternatively, if it is determined that any of the target addresses of destination A, destination B, and destination C are not compatible with carrier aggregation, the AS disables carrier aggregation, and transmits the data of multiple first services on a single carrier.

[0123] In another embodiment, Figure 5 This is a schematic diagram illustrating the implementation process of a sidelink communication method according to an embodiment of this disclosure. See also... Figure 5 After S302 or S303, the transmitting device may execute S501 to S502 (as shown by solid lines) or S503 to S504 (as shown by dashed lines).

[0124] S501, the transmitting device determines any first target address compatible with carrier aggregation.

[0125] It should be noted that the above "any first target address compatible carrier aggregation" can be understood as at least one first target address compatible carrier aggregation among one or more first target addresses.

[0126] S502, the transmitting device simultaneously transmits one or more first service data on multiple carriers.

[0127] Understandably, in S501 to S502, the AS determines that any one of the first target addresses is compatible with carrier aggregation. At this time, the AS enables carrier aggregation and transmits data of one or more first services simultaneously on multiple carriers.

[0128] S503, the transmitting device determines that all first destination addresses are incompatible with carrier aggregation.

[0129] S504, The transmitting device transmits one or more first service data on a single carrier.

[0130] Understandably, in S503 to S504, if the AS determines that all first target addresses among one or more first target addresses are incompatible with carrier aggregation, then the AS disables carrier aggregation and transmits one or more first service data on a single carrier.

[0131] For example, the target addresses of multiple first services can be destination A, destination B, and destination C. For each target address, the transmitting device executes S301 to S303 as described above to determine whether destination A, destination B, and destination C are compatible with carrier aggregation. If it is determined that any one of the target addresses, destination A, destination B, and destination C, is compatible with carrier aggregation, the AS enables carrier aggregation, and multiple first service data are transmitted simultaneously on multiple carriers. Alternatively, if it is determined that destination A, destination B, and destination C are not compatible with carrier aggregation, the AS deactivates carrier aggregation, and multiple first service data are transmitted on a single carrier.

[0132] In some possible implementations, Figure 6 This is a schematic diagram illustrating the implementation process of a sidelink communication method according to an embodiment of this disclosure. See also... Figure 6For setting Tx profiles at the target address granularity, the above methods can include:

[0133] S601, The transmitting device determines the first target address of the first service.

[0134] Here, the first service can be broadcast / multicast service.

[0135] Understandably, in the transmitting device, the higher layer triggers the first service, determines the first destination address associated with the first service, and instructs the AS. The AS determines the Tx profile associated with the first destination address based on the Tx profile associated with the destination address of the first service indicated by the higher layer. One first destination address is associated with one Tx profile.

[0136] Next, after S601, the transmitting device can execute S602 or S603.

[0137] S603, when the Tx profile associated with the first target address (i.e., a Tx profile) corresponds to a compatible carrier aggregation, the transmitting device determines the first target address compatible carrier aggregation.

[0138] Understandably, the AS can determine a Tx profile associated with the first destination address based on instructions from higher layers, and then determine whether this Tx profile corresponds to compatible carrier aggregation or incompatible carrier aggregation. If the AS determines that the Tx profile associated with the first destination address corresponds to compatible carrier aggregation (or, in other words, the Tx profile associated with the first destination address indicates compatible carrier aggregation), then the AS determines that the first destination address is compatible with carrier aggregation. At this point, the transmitting device (such as the AS) assumes that the first destination address is compatible with carrier aggregation.

[0139] It should be noted that the above statement "the Tx profile associated with the first target address corresponds to compatible carrier aggregation" can also be understood as the unique Tx profile associated with the first target address corresponding to compatible carrier aggregation, or all Tx profiles associated with the first target address corresponding to compatible carrier aggregation.

[0140] S603, when the Tx profile associated with the first target address (i.e., a Tx profile) corresponds to incompatible carrier aggregation, the transmitting device determines that the first target address is incompatible with carrier aggregation.

[0141] Understandably, if the AS determines that the Tx profile associated with the first destination address corresponds to incompatible carrier aggregation (or, in other words, the Tx profile associated with the first destination address indicates incompatible carrier aggregation), then the AS determines that the first destination address is incompatible with carrier aggregation. At this point, the transmitting device (such as the AS) assumes (or can be described as assuming, hypothesizing, etc.) that the first destination address is incompatible with carrier aggregation.

[0142] It should be noted that the above statement "the Tx profile associated with the first target address corresponds to incompatible carrier aggregation" can also be understood as the unique Tx profile associated with the first target address corresponding to incompatible carrier aggregation, or it can also be understood as a Tx profile associated with the first target address indicating incompatible carrier aggregation.

[0143] For example, the first destination address is destination A, and the Tx profile associated with the first destination address is Txprofile 1. If Tx profile 1 indicates that the broadcast / multicast service is compatible with carrier aggregation, the AS can determine that all Tx profiles associated with destination A correspond to compatible carrier aggregation, and in this case, the AS determines that destination A is compatible with carrier aggregation. Conversely, if Tx profile 1 indicates that the broadcast / multicast service is incompatible with carrier aggregation, the AS can determine that one Tx profile associated with destination A corresponds to incompatible carrier aggregation, and in this case, the AS determines that destination A is incompatible with carrier aggregation.

[0144] In some possible implementations, the transmitting device may also trigger one or more broadcast / multicast services, i.e., trigger one or more first services. In this case, the transmitting device may execute S601 to S603 as described above for each of the one or more first services, thereby determining whether one or more first target addresses are compatible with carrier aggregation. Next, after S602 or S603, the transmitting device may also execute, but is not limited to, S401 to S404 or S501 to S504 as described above, which will not be elaborated further here.

[0145] This completes the sidelink communication process on the sending device side.

[0146] In some possible implementations, embodiments of this disclosure also provide a sidelink communication method, which can be applied to the receiving device side of a sidelink communication system. Figure 7 This is a schematic diagram illustrating the implementation process of a sidelink communication method according to an embodiment of this disclosure. See also... Figure 7 For setting Tx profiles at the business type granularity, the above methods can include:

[0147] S701, the receiving device determines the second target address of the second service.

[0148] Here, the second service can be a broadcast / multicast service that the receiving device is interested in.

[0149] Understandably, in the receiving device, the higher layer identifies the second service of interest and instructs the AS (Application System) on the second target address of the second service. The AS then determines one or more Tx profiles associated with the second target address through one or more Tx profiles associated with the target address of the second service instructing the higher layer. These one or more Tx profiles correspond to multiple service types.

[0150] Next, after S701, the transmitting device can execute S702 or S703.

[0151] S702, when all Tx profiles associated with the second target address correspond to compatible carrier aggregation, the receiving device determines the second target address compatible carrier aggregation.

[0152] S703, when at least one Tx profile associated with the second target address corresponds to incompatible carrier aggregation, the second target address is determined to be incompatible with carrier aggregation.

[0153] It should be noted that the execution process of S701 to S703 described above can be referred to Figure 3 The detailed descriptions of S301 to S303 are omitted here for the sake of brevity.

[0154] In some possible implementations, the receiving device may also be interested in one or more broadcast / multicast services, i.e., there are one or more second services. In this case, the receiving device can execute S701 to S703 as described above for each of the one or more second services, thereby determining whether the one or more second target addresses are compatible with carrier aggregation. After determining whether the 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 from one or more second services on multiple carriers or on a single carrier.

[0155] In one embodiment, Figure 8 This is a schematic diagram illustrating the implementation process of a sidelink communication method according to an embodiment of this disclosure. See also... Figure 8 After S302 or S303, the transmitting device may execute S801 to S802 (as shown by solid lines) or S803 to S804 (as shown by dashed lines).

[0156] S801, the receiving device determines all second target address compatible carrier aggregations.

[0157] S802, the receiving device simultaneously receives data from one or more second services on multiple carriers.

[0158] S803, the receiving device determines that any second target address is incompatible with carrier aggregation.

[0159] It should be noted that the above "any second target address is incompatible with carrier aggregation" can be understood as at least one of one or more second target addresses being incompatible with carrier aggregation.

[0160] S804, the receiving device receives data from one or more second services on a single carrier.

[0161] Here, a single carrier can be a default carrier, such as the sidelink carrier in the Rel-16 or Rel-17 version of the communication protocol.

[0162] In another embodiment, after S302 or S303, the transmitting device may execute S805 to S806 (as shown by solid lines) or S807 to S808 (as shown by dashed lines).

[0163] S805, the receiving device determines any second target address compatible carrier aggregation.

[0164] S806, the receiving device simultaneously receives data from one or more second services on multiple carriers.

[0165] S807, the receiving device determines that all second target addresses are incompatible with carrier aggregation.

[0166] S808, the receiving device determines to receive data for one or more second services on a single carrier.

[0167] It should be noted that the execution process of S801 to S808 described above can be referred to Figure 4 S401 to S404 and Figure 5 The detailed descriptions of S501 to S504 are omitted here for the sake of brevity.

[0168] This completes the sidelink communication process on the receiving device side.

[0169] In this embodiment, the sidelink terminal device determines whether the target address of the first service is compatible with carrier aggregation based on the indication of the associated Tx profile; that is, it determines whether the associated receiving device supports carrier aggregation. Thus, in a sidelink carrier aggregation scenario, it ensures that terminal devices of previous versions (such as those in Rel-16 or Rel-17 communication protocols) can receive broadcast or multicast services from terminal devices of the latest versions (such as those supporting carrier aggregation in Rel-18 communication protocols), thereby achieving backward compatibility of the sidelink terminal device and improving its performance.

[0170] Based on the same inventive concept, embodiments of this disclosure provide a sidelink communication device. Figure 9 This is a schematic diagram of the structure of a communication device according to an embodiment of this disclosure. See also... Figure 9 As shown, the communication device 900 may include a processing module 901 and a transmission module 902.

[0171] In some possible embodiments, the communication device 900 can be a transmitting device in a sidelink communication system, or a chip or system-on-a-chip within the transmitting device. It can also be a functional module within the transmitting device for implementing the methods of the various embodiments described above. This communication device can implement the functions performed by the transmitting device in the various embodiments described above, and these functions can be implemented by hardware executing corresponding software. This hardware or software includes one or more modules corresponding to the aforementioned functions. See also... Figure 9 As shown by the solid line, the transmission module 902 can be understood as the sending module 902a.

[0172] Accordingly, the processing module 901 is used 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, to determine that the first target address is incompatible with carrier aggregation when at least one transmission attribute associated with the first target address corresponds to incompatible 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.

[0173] In some possible implementations, the transmission attribute is used to indicate whether the broadcast or multicast service is compatible with or incompatible with carrier aggregation.

[0174] In some possible implementations, the sending attributes are set at the service type granularity or at the destination address granularity.

[0175] In some possible implementations, in response to the sending attribute being set at the service type granularity, a sending attribute is associated with a service type, and at least one service type is associated with a destination address.

[0176] In some possible implementations, all transmission attributes associated with the first destination address include: transmission attributes associated with all service types associated with the first destination address.

[0177] In some possible implementations, a send attribute is associated with a target address in response to the send attribute being set at the target address granularity.

[0178] In some possible implementations, one or more transmission attributes are associated with a target address, wherein the one or more transmission attributes include transmission attributes for indicating compatible carrier aggregation and / or transmission attributes for indicating incompatible carrier aggregation.

[0179] In some possible implementations, the processing module 901 is further configured to determine any first target address compatible carrier aggregation; the transmission module 902a is configured to simultaneously transmit data of one or more first services on multiple carriers.

[0180] In some possible implementations, the processing module 901 is further configured to determine that all first target addresses are incompatible with carrier aggregation; the transmission module 902a is configured to transmit data of one or more first services on a single carrier.

[0181] In some possible implementations, the processing module 901 is further configured to determine all first target address compatible carrier aggregations; the transmission module 902a is configured to simultaneously transmit data of one or more first services on multiple carriers.

[0182] In some possible implementations, the processing module 901 is further configured to determine that any first target address is incompatible with carrier aggregation; the transmission module 902a is configured to transmit data of one or more first services on a single carrier.

[0183] In some possible implementations, the communication device described above can be a receiving device in a sidelink communication system, or a chip or system-on-a-chip within the receiving device. It can also be a functional module within the receiving device for implementing the methods of the various embodiments described above. This communication device can implement the functions performed by the receiving device in the various embodiments described above, and these functions can be implemented by hardware executing corresponding software. This hardware or software includes one or more modules corresponding to the aforementioned functions. At this point, see... Figure 9 As shown by the dashed line, the transmission module 902 can be understood as the receiving module 902b.

[0184] Accordingly, the processing module 901 is used 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, to determine that the second target address is incompatible with carrier aggregation when at least one transmission attribute associated with the second target address corresponds to incompatible 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.

[0185] In some possible implementations, the transmission attribute is used to indicate whether the broadcast or multicast service is compatible with or incompatible with carrier aggregation.

[0186] In some possible implementations, the sending attributes are set at the service type granularity or at the destination address granularity.

[0187] In some possible implementations, in response to the sending attribute being set at the service type granularity, a sending attribute is associated with a service type, and at least one service type is associated with a destination address.

[0188] In some possible implementations, all transmission attributes associated with the second destination address include: transmission attributes associated with all service types associated with the second destination address.

[0189] In some possible implementations, a send attribute is associated with a target address in response to the send attribute being set at the target address granularity.

[0190] In some possible implementations, one or more transmission attributes are associated with a target address, wherein the one or more transmission attributes include transmission attributes for indicating compatible carrier aggregation and / or transmission attributes for indicating incompatible carrier aggregation.

[0191] In some possible implementations, the processing module 901 is further configured to determine any second target address compatible carrier aggregation; the receiving module 902b is configured to simultaneously receive data of one or more second services on multiple carriers.

[0192] In some possible implementations, the processing module 901 is further 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.

[0193] In some possible implementations, the processing module 901 is further configured to determine all second target address compatible carrier aggregations; the receiving module 902b is configured to simultaneously receive data of one or more second services on multiple carriers.

[0194] In some possible implementations, the processing module 901 is further configured to determine that any second target address is incompatible with carrier aggregation; the receiving module 902b is configured to receive data of one or more second services on a single carrier.

[0195] It should be noted that the specific implementation process of processing module 901 and transmission module 902 can be found in [reference needed]. Figures 3 to 8 The detailed descriptions of the transmitting and receiving devices in the embodiments are omitted here for the sake of brevity.

[0196] The receiving module 902b mentioned in this embodiment can be a receiving interface, receiving circuit or receiver, etc.; the transmitting module 902a can be a transmitting interface, transmitting circuit or transmitter, etc.; the processing module 901 can be one or more processors.

[0197] Based on the same inventive concept, this disclosure provides a communication device, which can be the transmitting device and / or receiving device described in one or more of the above embodiments. Figure 10 This is a schematic diagram of the structure of a communication device according to an embodiment of this disclosure. See also... Figure 10 As shown, the communication device 100 uses general-purpose computer hardware, including a processor 101, a memory 102, a bus 103, an input device 104, and an output device 105.

[0198] In some possible implementations, 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 operating systems, applications, other program modules, executable code, program data, user data, etc.

[0199] Input device 104 can be used to input commands and information to communication devices. Input device 104 may be a keyboard or pointing device, such as a mouse, trackball, touchpad, microphone, joystick, gamepad, satellite TV antenna, scanner, or similar device. These input devices can be connected to processor 101 via bus 103.

[0200] Output device 105 can be used to output information for communication devices. In addition to monitors, output device 105 can also be used for other peripheral output devices, such as speakers and / or printing devices. These output devices can also be connected to processor 101 via bus 103.

[0201] Communication devices can be connected to a network, such as a local area network (LAN), via antenna 106. In a networked environment, computer execution instructions stored in the control unit can be stored in a remote storage device, not just locally.

[0202] When the processor 101 in the communication device executes the executable code or application stored in the memory 102, the communication device executes the mobility management configuration method on the terminal device side or network device side in the above embodiments. For the specific execution process, please refer to the above embodiments, which will not be repeated here.

[0203] Furthermore, the aforementioned memory 102 stores information for implementing... Figure 9 The computer executes instructions to perform the functions of the processing module 901 and the transmission module 902. Figure 9 The functions / implementation processes of the processing module 901 and the transmission module 902 can be understood through... Figure 10 The processor 101 in the memory calls the computer execution instructions stored in the memory 102 to implement the function. For the specific implementation process and function, please refer to the above-mentioned related embodiments.

[0204] Based on the same inventive concept, this disclosure provides a terminal device that is consistent with the terminal devices described in one or more of the above embodiments, such as a sending terminal device, a sending user device, a receiving terminal device, and a receiving user device. Optionally, the terminal device may be a mobile phone, a computer, a digital broadcasting terminal device, a messaging device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, etc.

[0205] Figure 11 This is a schematic diagram of the structure of a terminal device according to an embodiment of this disclosure. See also... Figure 11 The terminal device 110 may include one or more of the following components: processing component 111, memory 112, power supply component 113, multimedia component 114, audio component 115, input / output (I / O) interface 116, sensor component 117, and communication component 118.

[0206] Processing component 111 typically controls the overall operation of terminal device 110, such as operations related to display, telephone calls, data communication, camera operation, and recording. Processing component 111 may include one or more processors 1111 to execute instructions to complete all or part of the steps of the methods described above. Furthermore, processing component 111 may include one or more modules to facilitate interaction between processing component 111 and other components. For example, processing component 111 may include a multimedia module to facilitate interaction between multimedia component 114 and processing component 111.

[0207] Memory 112 is configured to store various types of data to support operation on terminal device 110. Examples of this data include instructions for any application or method operating on terminal device 110, contact data, phonebook data, messages, pictures, videos, etc. Memory 112 can 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 (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk.

[0208] Power supply component 113 provides power to various components of 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 terminal device 110.

[0209] Multimedia component 114 includes a screen that provides an output interface between terminal device 110 and the user. In some embodiments, 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 touchscreen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensors may sense not only the boundaries of touch or swipe actions but also the duration and pressure associated with the touch or swipe operation. In some embodiments, multimedia component 114 includes a front-facing camera and / or a rear-facing camera. When terminal device 110 is in an operating mode, such as a shooting mode or a video mode, the front-facing camera and / or rear-facing camera may receive external multimedia data. Each front-facing camera and rear-facing camera may be a fixed optical lens system or have focal length and optical zoom capabilities.

[0210] Audio component 115 is configured to output and / or input audio signals. For example, audio component 115 includes a microphone (MIC) configured to receive external audio signals when terminal device 110 is in an operating mode, such as call mode, recording mode, and voice recognition mode. The received audio signals may be further stored in memory 112 or transmitted via communication component 118. In some embodiments, audio component 115 also includes a speaker for outputting audio signals.

[0211] I / O interface 116 provides an interface between processing component 111 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to, home buttons, volume buttons, power buttons, and lock buttons.

[0212] Sensor assembly 117 includes one or more sensors for providing status assessments of various aspects of terminal device 110. For example, sensor assembly 117 can monitor the on / off state of terminal device 110, the relative positioning of components (e.g., the display and keypad of terminal device 110), changes in position of terminal device 110 or a component of terminal device 110, the presence or absence of user contact with terminal device 110, the orientation or acceleration / deceleration of terminal device 110, and temperature changes of 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. In some embodiments, sensor assembly 117 may also include an accelerometer, a gyroscope, a magnetometer, a pressure sensor, or a temperature sensor.

[0213] Communication component 118 is configured to facilitate wired or wireless communication between terminal device 110 and other devices. Terminal device 110 can access wireless networks employing communication standards such as Wi-Fi, 2G, 3G, 4G, or 5G, or combinations thereof. In one exemplary embodiment, communication component 118 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, communication component 118 also includes a near-field communication (NFC) module to facilitate short-range communication. For example, the NFC module may employ radio frequency identification (RFID) technology, Infrared Data Association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.

[0214] In an exemplary embodiment, the terminal device 110 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the methods described above.

[0215] Based on the same inventive concept, this disclosure provides a network device that is consistent with the network devices such as the transmitting network device and the receiving network device in one or more of the above embodiments.

[0216] Figure 12 This is a schematic diagram of the structure of a network device according to an embodiment of this disclosure. See also... Figure 12The network device 120 may include a processing component 121, which further includes one or more processors, and memory resources represented by memory 122 for storing instructions, such as application programs, that can be executed by the processing component 121. The application programs stored in memory 122 may include one or more modules, each corresponding to a set of instructions. Furthermore, the processing component 121 is configured to execute instructions to perform any of the methods described above applied to the network device.

[0217] 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 on an operating system stored in memory 122, such as Windows Server™, Mac OS X™, Unix™, Linux™, FreeBSD™, or similar.

[0218] Based on the same inventive concept, such as a terminal device, it includes: an antenna; a memory; and a processor, which are respectively connected to the antenna and the memory, and are configured to execute computer-executable instructions stored in the memory to control the transmission and reception of the antenna, and to implement the method on the transmitting device side as described in one or more of the above embodiments.

[0219] Based on the same inventive concept, such as a network device, it includes: an antenna; a memory; and a processor, which are respectively connected to the antenna and the memory, and are configured to execute computer-executable instructions stored in the memory to control the transmission and reception of the antenna, and to implement the method on the receiving device side as described in one or more of the above embodiments.

[0220] Based on the same inventive concept, this disclosure also provides a computer-readable storage medium storing instructions; when the instructions are executed on a computer, they are used to perform the methods of the transmitting device side or the receiving device side in one or more of the above embodiments.

[0221] Based on the same inventive concept, this disclosure also provides a computer program or computer program product that, when executed on a computer, causes the computer to implement the methods of the transmitting device side or the receiving device side in one or more of the above embodiments.

[0222] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not disclosed herein.

[0223] It should be understood that this disclosure is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope.

Claims

1. A sidelink communication method, applied to a transmitting device, the method comprising: When all transmission attributes associated with the first target address correspond to compatible carrier aggregation, the first target address is determined to be compatible carrier aggregation; When at least one transmission attribute associated with the first target address corresponds to incompatible carrier aggregation, the first target address is determined to be incompatible with carrier aggregation. Wherein, the first target address is the target address of the first service; the first service is a broadcast service or a multicast service; When it is determined that all the first target addresses are compatible with carrier aggregation, one or more data of the first service are transmitted simultaneously on multiple carriers; when it is determined that any of the first target addresses are incompatible with carrier aggregation, one or more data of the first service are transmitted on a single carrier. Alternatively, when it is determined that any of the first target addresses are compatible with carrier aggregation, one or more data of the first service are transmitted simultaneously on multiple carriers; when it is determined that all the first target addresses are incompatible with carrier aggregation, one or more data of the first service are transmitted on a single carrier.

2. The method according to claim 1, wherein, The transmission attribute is used to indicate whether the broadcast or multicast service is compatible with carrier aggregation.

3. The method according to claim 1 or 2, wherein, The sending attributes are set according to the service type granularity, or the sending attributes are set according to the target address granularity.

4. The method according to claim 3, wherein, In response to the sending attributes being set at the service type granularity, one sending attribute is associated with one service type, and at least one service type is associated with one destination address.

5. The method according to claim 4, wherein, All sending attributes associated with the first target address include: sending attributes associated with all service types associated with the first target address.

6. The method according to claim 3, wherein, The sending attributes are set according to the target address granularity, and one sending attribute is associated with one target address.

7. The method according to claim 1, wherein, One or more transmission attributes are associated with a target address, wherein the one or more transmission attributes include transmission attributes for indicating compatible carrier aggregation and / or transmission attributes for indicating incompatible carrier aggregation.

8. A sidelink communication method applied to a receiving device, the method comprising: When all transmission attributes associated with the second target address correspond to compatible carrier aggregation, the second target address is determined to be compatible carrier aggregation; When at least one transmission attribute associated with the second target address corresponds to incompatible carrier aggregation, the second target address is determined to be incompatible 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; When all second target addresses are determined to be compatible with carrier aggregation, one or more data of the second service are received simultaneously on multiple carriers; when any second target address is determined to be incompatible with carrier aggregation, one or more data of the second service are received on a single carrier. Alternatively, when any second target address is determined to be compatible with carrier aggregation, one or more data of the second service are received simultaneously on multiple carriers; when all second target addresses are determined to be incompatible with carrier aggregation, one or more data of the second service are received on a single carrier.

9. The method according to claim 8, wherein, The transmission attribute is used to indicate whether the broadcast or multicast service is compatible with carrier aggregation.

10. The method according to any one of claims 8 or 9, wherein, The sending attributes are set according to the service type granularity, or the sending attributes are set according to the target address granularity.

11. The method according to claim 10, wherein, In response to the sending attributes being set at the service type granularity, one sending attribute is associated with one service type, and at least one service type is associated with one destination address.

12. The method according to claim 11, wherein, All sending attributes associated with the second target address include: sending attributes associated with all service types associated with the second target address.

13. The method according to claim 10, wherein, In response to the sending attribute being set at the target address granularity, one sending attribute is associated with one target address.

14. The method according to claim 8, wherein, One or more transmission attributes are associated with a target address, wherein the one or more transmission attributes include transmission attributes for indicating compatible carrier aggregation and / or transmission attributes for indicating incompatible carrier aggregation.

15. A communication apparatus applied to a transmitting device, the apparatus comprising: The processing module is used to determine the compatible carrier aggregation of the first target address when all transmission attributes associated with the first target address correspond to compatible carrier aggregation; When at least one transmission attribute associated with the first target address corresponds to incompatible carrier aggregation, the first target address is determined to be incompatible with carrier aggregation; wherein, the first target address is the target address of a first service, and the first service is a broadcast service or a multicast service; The transmitting module is configured to transmit one or more data of the first service simultaneously on multiple carriers when it is determined that all the first target addresses are compatible with carrier aggregation, and to transmit one or more data of the first service on a single carrier when it is determined that any of the first target addresses are incompatible with carrier aggregation; or, when it is determined that any of the first target addresses are compatible with carrier aggregation, to transmit one or more data of the first service simultaneously on multiple carriers, and to transmit one or more data of the first service on a single carrier when it is determined that all the first target addresses are incompatible with carrier aggregation.

16. A side-link receiving device, applied to a receiving equipment, the device comprising: The processing module is used to determine the compatible carrier aggregation of the second target address when all transmission attributes associated with the second target address correspond to compatible carrier aggregation; When at least one transmission attribute associated with the second target address corresponds to incompatible carrier aggregation, the second target address is determined to be incompatible 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 receiving module is configured to simultaneously receive one or more data of the second service on multiple carriers when all the second target addresses are determined to be compatible with carrier aggregation, and to receive one or more data of the second service on a single carrier when any of the second target addresses are determined to be incompatible with carrier aggregation; or, when any of the second target addresses are determined to be compatible with carrier aggregation, simultaneously receive one or more data of the second service on multiple carriers, and to receive one or more data of the second service on a single carrier when all the second target addresses are determined to be incompatible with carrier aggregation.

17. A communication device, characterized in that, include: antenna; Memory; The processor, connected to the antenna and the memory respectively, is configured to execute computer-executable instructions stored in the memory to control the transmission and reception of the antenna and to implement the method as described in any one of claims 1 to 14.

18. A computer storage medium, characterized in that, The computer-readable storage medium stores instructions that, when executed on a computer, are used to perform the method as described in any one of claims 1 to 14.

Images